September 2018 - desktop - Fedora Mailing-Lists

F29: power notification on gnome lock screen, no journal messages

by Chris Murphy

Crossposting test@ desktop@ Hi, I keep getting this weird behavior on Fedora 29 for which there are no journal messages at all. This is the setup: 1. on battery power 2. Settings>Power>Blank Power = 5 minutes 3. Settings>Power>Dim Screen when inactive = On 4. Settings>Power>Automatic Suspend>Battery = On, 15 minutes --- 5. Use is inactive for more than 5 minutes, and less than 15. (At 15 minutes it definitely goes into suspend successfully). 6. I look up and see the GNOME lock screen with multiple yakyak notifications, and also see a power notification (international stop sign symbol). The power notification doesn't itself make the display come on, it's yakyak. If I don't receive an incoming message on yakyak, I have no idea the power notification is present. And if I take a screenshot while the display is off, the screenshot file is all black. 7. The instant I click on any key or the trackpad, only the power notification vanishes. The yakyak message remain in the list, and once I log back into my user session, the power notification is not in the drop down list of notifications when clicking on the time. And yet all the yakyak notifications are in the list. 8. Nothing in the journal related to power https://paste.fedoraproject.org/paste/p1Y-B8Sq3446sM4H5FtvgQ/raw Is there a way to make the environment spit out more verbose messages into the journal? I don't see a debug or verbose option with gnome-shell -h gnome-shell-3.30.0-7.fc29.x86_64 -- Chris Murphy

5 years, 2 months

5
8
0 / 0

Disabling kernel's hibernate support by default, allow re-enabling it with a kernel cmdline option

by Hans de Goede

Hello Fedora kernel team, On the Fedora desktop list there has been a discussion about systemd now offering a new suspend-then-hibernate option and gnome-settings-daemon's media-keys plugin using this when the power-button gets pressed and systemd saying this is available on the system. What this does is suspend the system normally and set a RTC wakeup 3 hours in the future, then when the RTC wake happens it hibernates the system. As discussed on the desktop list this is not really desirable as default behavior for F29 (and later) since the hibernate code is not really something which gets used enough to be well tested and is really not something which we can support. So after that the discussion has gone in the direction of how to disable the new suspend-then-hibernate behavior. Lennart made a really interesting observation here, systemd is just proxying if "cat /sys/power/disk" indicates that hibernate is supported. So if we really don't want to support hibernation as a normal option, while still allowing adventurous user to use it, what really should happen is for the kernel to stop advertising hibernate support. Thinking about this I agree, if we say that we cannot support it, the kernel really should not be advertising support for it by default. So Bastien suggested to change the nohibernate setting in kernel/power/hibernate.c which can be set from the kernel commandline to default to 1, and allow setting it back to 0 by adding "hibernate=yes" to the kernel commandline. I kinda like this idea and I'm willing to spend some time to write a patch for this and submit it upstream, which allows selecting nohibernate=1 as the default through Kconfig. But before I spend (some) time on this, I wonder what the kernel team's opinion on this is ? My own 2 cents on this are: Pro: Not advertising hibernate by default means users will not accidentally try to use it (through e.g gnome-tweaks) and if they do use it by specifying the kernel commandline option we can easily explain that using that commandline option is not supported by Fedora and kindly request them to file bugs upstream. TL;DR: less kernel issues for Fedora to deal with, good. Against: Currently we do have some users using hibernation without adding any options to the kernel commandline. These users will have to now add "hibernate=yes" to their kernel commandline. I'm thinking that yes we want this, but maybe this needs to go through the change process for proper communication, so for F29 we need another fix, and we can do this for F30? Regards, Hans

5 years, 2 months

11
29
0 / 0

Disable (or make configurable and default to off) suspend-then-hibernate behavior in GNOME-3.30

by Hans de Goede

Hi Benjamin, Carlos, I'm mailing you 2 because you maintain g-s-d now. As discussed on the Fedora desktop mailinglist in the "system now hibernates automatically 3 hours after suspend ?" thread, the suspend-then-hibernate behavior is not really ready for mainstream use yet (according to the systemd folks). Also from a kernel pov all of a sudden using hibernate is a huge change and involves code paths which no other major distro has been using sofar. So we really need to disable this for Fedora 29. And as mentioned in the thread when we decide to enable this for a future release, it really needs to go through the changes process so that it is well document we are changing this and people will have a clue what is the likely culprit if leaving their laptop suspend for > 3h all of a sudden breaks. Regards, Hans

5 years, 2 months

18
78
0 / 0

2018-09-24 @ 16:00 UTC - Fedora 29 Blocker Review Meeting

by Adam Williamson

# F29 Blocker Review meeting # Date: 2018-10-01 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.freenode.net Hi folks! We have 7 proposed Final blockers and 2 proposed Final freeze exceptions to review, so let's have a review meeting tomorrow. Again we have GNOME and grub2 bugs on the list, along with a couple in anaconda and cron. If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F29 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good night and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

5 years, 2 months

1
0
0 / 0

[Fedocal] Reminder meeting : Silverblue

by sanja＠redhat.com

Dear all, You are kindly invited to the meeting: Silverblue on 2018-10-01 from 09:00:00 to 10:00:00 US/Eastern At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Fedora Silverblue IRC meeting in #fedora-meeting-2 on Freenode. Fedora Silverblue is an rpm-ostree-based Fedora desktop edition. Source: https://apps.fedoraproject.org/calendar/meeting/9304/

5 years, 2 months

1
0
0 / 0

[Fedocal] Reminder meeting : Workstation WG

by stickster＠gmail.com

Dear all, You are kindly invited to the meeting: Workstation WG on 2018-09-24 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: * Monday Jun 18 - Michael Catanzaro * Monday Jul 02 - (deferred) * Monday Jul 16 - Matthias Clasen * Monday Jul 30 - Rex Dieter * Monday Aug 13 - (deferred, Flock) * Monday Aug 27 - Paul Frields * Monday Sep 10 - Kalev Lember * Monday Sep 24 - Ryan Lerch * Monday Oct 08 - Jens Petersen * Monday Oct 22 - Christian Schaller * Monday Nov 05 - Owen Taylor More information available at: https://fedoraproject.org/wiki/Workstation Source: https://apps.fedoraproject.org/calendar/meeting/6411/

5 years, 2 months

2
1
0 / 0

2018-09-24 @ 16:00 UTC - Fedora 29 Blocker Review Meeting

by Adam Williamson

# F29 Blocker Review meeting # Date: 2018-09-24 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.freenode.net Hi folks! We have 9 proposed Final blockers and 3 proposed Final freeze exceptions to review, so let's have a review meeting tomorrow. Most proposed blockers are in GNOME, there is also one each in (lib)dnf and grub2, so CCing dmach and pjones. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F29 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good night and see you tomorrow! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

5 years, 2 months

1
0
0 / 0

Fedora 29 Beta status: RC5 incoming, purpose

by Adam Williamson

Hi, folks! So, Beta RC4 is out there and being tested (thanks for all the testing so far). There is an RC5 coming too: here's why. We haven't found any blockers in RC4 yet, but we did find several not- quite-blockers that seemed bad. First of all, the Silverblue (formerly known as Atomic Workstation) installer image build failed due to a network blip, so RC4 does not have that image. If we ship RC4 as the Beta, we wouldn't have a Silverblue installer for the Beta at all (unless we did some ugly hack to stuff some other image in), and that seems bad - the image isn't release-blocking, but it is a major area of development and we really ought to include it in Beta. Beyond that, we happened to run into and find fixes for quite a slew of bugs in gnome-shell, plus a couple in gtk+ and mesa that are quite visible too. Here's a list of all the bugs in question: https://bugzilla.redhat.com/show_bug.cgi?id=1630134 https://gitlab.gnome.org/GNOME/gnome-shell/issues/574 https://gitlab.gnome.org/GNOME/gnome-shell/issues/539 https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/227 https://gitlab.gnome.org/GNOME/gnome-shell/issues/523 https://bugzilla.redhat.com/show_bug.cgi?id=1631068 https://bugzilla.redhat.com/show_bug.cgi?id=1628462 So nirik, mboddu and I agreed it'd be reasonable to run a Beta RC5 to give us at least the option of shipping a compose with the Silverblue image and fixes for all those bugs, if everything goes well. As there aren't any outright blockers in it, Beta RC4 is still a candidate for release too. Beta RC5 should complete in ten hours or so. There should be no difference between Beta RC4 and Beta RC5 outside of GNOME and the mesa fix, so most RC4 tests should be valid for RC5 too. So, please continue testing RC4. Once RC5 arrives, go ahead and test that too, prioritizing smoke tests, tests of GNOME, and any Basic / Beta tests not yet run against RC4. It is not a high priority to run tests on RC5 that have already been run on RC4, unless they're basic smoke tests or GNOME tests. Thanks a lot, everyone! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

5 years, 2 months

1
0
0 / 0

Fedora 29 Beta status: RC4 incoming

by Adam Williamson

Hi, folks! Just a quick mail to let everyone know where we are with F29 Beta. We managed to throw together fixes for all the currently-accepted blockers (thanks to the dnf team for help there), so an RC4 (aka Beta- 1.4) is currently composing. Compared to RC3 it contains a newer libdnf with a fix for https://bugzilla.redhat.com/show_bug.cgi?id=1629340 . It also includes a newer gnome-shell with fixes for FE bug https://bugzilla.redhat.com/show_bug.cgi?id=1628263 and also https://gitlab.gnome.org/GNOME/gnome-shell/issues/140 (which kinda snuck in there), new builds of dnfdragora and dnfdaemon that fix two significant bugs for users of those - https://bugzilla.redhat.com/show_bug.cgi?id=1624652 and https://bugzilla.redhat.com/show_bug.cgi?id=1629378 - and an updatedgnome-documents which actually works (that was https://bugzilla.redhat.com/show_bug.cgi?id=1628244 ). The second Go/No-Go meeting will be on Thursday, so it would be awesome if folks could pitch in and help get as much testing done as possible on Beta-1.4 when it arrives. There will be an announcement mail sent to test-announce@, so look out for that. It will have links to the validation pages, which have the download links at the top. General exploratory testing would also be great to find any significant issues not specifically covered in the validation tests. It should arrive in around 8-9 hours, assuming the compose takes about as long as the previous one. Some of the media will actually be available from Koji a little sooner than that, for anyone who wants to get a head start on testing; to find the live images, for instance, go to this URL: https://koji.fedoraproject.org/koji/tasks?state=closed&view=flat&method=c... and look for tasks with the string 'Fedora-29-20180919.0' in them (*not* 'Fedora-29-20180919.n.0', those would be nightlies, which don't have the extra fixed packages). Thanks a lot, everyone! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

5 years, 2 months

1
0
0 / 0

Silverblue APAC Meeting Minutes 2018-09-18

by Sinny Kumari

Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-09-18/team_silver... Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2018-09-18/team_silver... Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-09-18/team_silver... ======================================= #fedora-meeting-1: Team Silverblue APAC ======================================= Meeting started by ksinny at 05:31:11 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2018-09-18/team_silver... . Meeting summary --------------- * roll call (ksinny, 05:31:28) * Fedora 29 Silverblue Test Day (ksinny, 05:33:24) * LINK: https://pagure.io/teamsilverblue/issue/28 (ksinny, 05:33:38) * LINK: https://fedoramagazine.org/give-fedora-silverblue-a-test-drive/ (sumantro, 05:34:09) * Silverblue Test Day wiki page is available - https://fedoraproject.org/wiki/Test_Day:2018-09-20_Silverblue_Testday (ksinny, 05:34:27) * Test Cases which we will be testing are available at http://testdays.fedorainfracloud.org/events/47 (ksinny, 05:35:23) * How to Contribute (ksinny, 05:41:24) * LINK: https://silverblue.fedoraproject.org/contribute (ksinny, 05:41:34) * Open Floor (ksinny, 05:49:01) Meeting ended at 05:59:03 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * ksinny (48) * zodbot (12) * sumantro (10) * prakashmishra (7) * siddharthvipul (7) * mzee1000 (6) * bhavin192 (5) * paragan (1) * juhp (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

5 years, 2 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

desktop September 2018