Created attachment 1482005 [details] screencast Description of problem: As shown in the attached screencast,I have done a default installation with Fedora-Workstation-Live-x86_64-29-20180909.n.0.iso,after I choose logout in the right-up list,the system hang there for a long time,and I see lots of "Error getting active session: No data available" in the journal,and sometimes gnome-shell coredump happens.This makes both login and logout take pretty longer time than before. Version-Release number of selected component (if applicable): gnome-shell-3.29.91-1.fc29.x86_64 kernel-4.18.5-300.fc29.x86_64 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 1482006 [details] journal
Proposed as a Blocker for 29-beta by Fedora user lnie using the blocker tracking app because: Seems a little affects: Shutting down, logging out and rebooting must work using standard console commands and the mechanisms offered (if any) by all release-blocking desktops. I propose this as a blocker as it's really annoying,you have to wait a long time everytime
(In reply to Fedora Blocker Bugs Application from comment #2) > Proposed as a Blocker for 29-beta by Fedora user lnie using the blocker > tracking app because: > > Seems a little affects: > Shutting down, logging out and rebooting must work using standard console > commands and the mechanisms offered (if any) by all release-blocking > desktops. > I propose this as a blocker as it's really annoying,you have to wait a long > time everytime I'd be +1 FE, but a long shutdown time is an annoyance, not a blocking issue in my opinion. I wouldn't delay Beta to address this. -1 Beta Blocker. We can argue over whether it should be a GA blocker under the "polish" criteria though.
Is this still an issue with GNOME 3.30.0 that just got pushed to stable? It should be in today's F29 Beta RC1 and nightly compose.
There was also a related selinux-policy update yesterday that fixed slow log in; might fix this as well. This is also in stable and should be in today's compose.
Yeah, please try with the RC1 compose and let us know. The selinux-policy changes definitely make a huge difference to startup times, may well be affecting shutdown also.
Much better,though logout still takes several seconds longer than before and there is still plenty of"localhost-live spice-vdagentd[1105]: Error getting active session: No data available" in journal
I think the error message isn't terribly important, it's probably just vdagent throwing a fit because it notices the session is going down. Perhaps it should be stopped sooner in the teardown process so it doesn't do that, but it doesn't seem like a big deal.
Discussed at 2018-09-13 Fedora 29 Beta Go/No-Go meeting, acting as a blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2018-09-13/f29-beta-go_no_go-meeting.2018-09-13-17.00.html . Rejected as a Beta blocker: per current description this clearly does not meet any of the criteria.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.