desktop April 2019

desktop@lists.fedoraproject.org

16 participants
16 discussions

high contrast terminal icon does not fit in
by Matthew Miller 11 Apr '19

11 Apr '19

I just updated to the F30 beta. I'm pretty sensitive to color, so I use the high-contrast black and white theme. In F29 and previous, this resulted in a matching icon in the dash (well, dock, as I am using that extension). However, in F30, I get a high-res icon which does not match. -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

3 4

Fedora 30 Final blocker bug 1690429 needs priority fix
by Adam Williamson 09 Apr '19

09 Apr '19

Hi folks! Just wanted to draw your attention to this F30 bug: https://bugzilla.redhat.com/show_bug.cgi?id=1690429 It is the same as this upstream bug: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1053 which has been filed and acknowledged for some time, but not yet fixed. The downstream bug is accepted as an F30 Final blocker. Final freeze is scheduled for 2019-04-16, so we are getting to the end of the cycle. It would be great if a fix for this could be worked out ASAP, so we can knock it out of the blocker list. Thanks a lot! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

[Fedocal] Reminder meeting : Workstation WG
by stickster＠gmail.com 06 Apr '19

06 Apr '19

Dear all, You are kindly invited to the meeting: Workstation WG on 2019-04-08 from 09:00:00 to 10:00:00 America/New_York At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Regular meeting for the Workstation Working Group. Agenda: https://pagure.io/fedora-workstation/issues?status=Open&tags=meeting Chair: * Dec 03 - Michael Catanzaro * Dec 17 - Matthias Clasen * Jan 14 - Rex Dieter * Jan 28 - (devconf) * Feb 11 - Paul Frields * Feb 25 - Kalev Lember * Mar 11 - Ryan Lerch * Mar 25 - Jens Petersen * Apr 08 - Christian Schaller * Apr 22 - Owen Taylor More information available at: https://fedoraproject.org/wiki/Workstation Source: https://apps.fedoraproject.org/calendar/meeting/6411/

1 0

f30-backgrounds updated with animated wallpapers
by Luya Tshimbalanga 04 Apr '19

04 Apr '19

Hello team, New version of f30-backgrounds is available with animated default wallpapers ready for testing. See https://bodhi.fedoraproject.org/updates/f30-backgrounds-30.1.0-1.fc30 Regards, Luya

1 0

"Basic graphics mode" feature and criterion discussion
by Adam Williamson 03 Apr '19

03 Apr '19

Hi folks! So at last week's Fedora 30 Beta Go/No-Go meeting, it was decided that the Basic release criterion: "Boot menu contents The boot menu for all supported installer and live images should include an entry which causes both installation and the installed system to use a generic, highly compatible video driver (such as 'vesa'). This mechanism should work correctly, launching the installer or desktop and attempting to use the generic driver." should no longer apply to Beta - i.e. that it should no longer be a Basic or Beta criterion. The justification for this is, I hope I am correctly representing all views here (please say so if not), that this mechanism is both less necessary (due to a general reduction in the amount of 'weird' graphics hardware out there, and general improvement in the reliability and coverage of the major drivers for the major graphics hardware manufacturers) and inherently less likely to work (due to the general trend of work on kernel modesetting and Wayland) than it used to be. For context, it is worth noting that the *feature* predates the introduction of both kernel modesetting *and* Wayland to Fedora. What the feature initially did was tell anaconda to write an X config file specifying the 'vesa' driver (instead of working out the correct 'native' driver for the adapter and writing a config file specifying that). After KMS was introduced in Fedora 10, the mechanism was tweaked to also pass the 'nomodeset' kernel parameter to disable KMS. Around 2012 (https://bugzilla.redhat.com/show_bug.cgi?id=858270) we noticed that the X config file mechanism was a bit superfluous as 'nomodeset' alone could basically be relied on to force some sort of 'fallback mechanism', and so the feature was simplified to *only* specify the 'nomodeset' kernel parameter (this is all it does now). The *criterion* dates to 2010, in the Fedora 15 release cycle: it appears in the Fedora 15 Alpha criteria but not the Fedora 14 Alpha criteria. It was added on 2010-08-16: https://fedoraproject.org/w/index.php?title=Fedora_15_Alpha_Release_Criteri… The group at the meeting did not, however, make any further decisions, so this leaves us with some open questions: 0) Do we generally agree with the decision made at the meeting? If anyone (especially a subject matter expert) strongly believes the decision was wrong and this should still be a Basic/Beta requirement, please say so. 1) Should the criterion be modified somehow, but some requirement in relation to some kind of fallback graphical mode be kept at Basic or Beta? 2) Should the criterion be moved to Final, unchanged or changed somehow? 3) Should the requirement just basically be dropped entirely as no longer useful? 4) (This one mainly for ajax and airlied) to what extent does the concept of a 'fallback option' for our supported desktop environments and graphical servers still actually make sense? Could a different implementation of the same basic idea be envisaged, and would it be useful? If so, should we do that, and what would be the consequences for the criteria? I realize this is quite a big and fuzzy topic, but I'm hoping the responses to this mail will clarify our path :) So if you have any kind of useful information or strong opinions on the general area here, please do contribute them, and hopefully a clearer way forward will emerge. Thanks everyone! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

6 10

Audio downmixing and normalization
by Michael Cronenworth 02 Apr '19

02 Apr '19

Updating my audio collection has introduced a few new issues into the wrench. Adding multi-channel audio has proven to be a little problematic. - ReplainGain support for multi-channel audio is lacking in Fedora. I've poked one upstream about it. [1] - Downmixing multi-channel audio to stereo results in poor output out of the box with Fedora defaults. The rear channels are basically dropped. Attempting to use a PulseAudio virtual surround sink results in muddy, soft audio. Using a remap sink to send rear channels to their respective front channels results in clear, soft audio. No normalization appears to happen. My multi-channel setup: Kodi -> HDMI -> 5.1 receiver -> speakers My stereo setup: Rhythmbox -> analog jack -> speakers FFmpeg and other audio processing libraries and players (including Kodi) have proper downmixing that includes normalization with their defaults. Even my Pixel 3 appears to do it right if I send a 5.1 track to it and play it out of its stereo speakers when I played a 5.1 track and its stereo duplicate track back-to-back. I find it a little disappointing that PulseAudio isn't doing it and would love to fix it. Who would be the best candidate to go after supporting a proper downmix + normalization path? PulseAudio? Gnome? Rhythmbox? If you haven't experienced a multi-channel audio track I highly recommend it. Thanks, Michael [1] https://github.com/xiph/flac/issues/96

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

desktop April 2019