Hide Forgot
Created attachment 1511674 [details] Systemd-Journal with crash-log from tracker Description of problem: The shutdown in Fedora 29 takes about 90 seconds. It seems, that the tracker for the file-indexing in gnome crashes on shutdown. This prevents a fast shutdown. Version-Release number of selected component (if applicable): Fedora 29 with Gnome 3.30 How reproducible: I can reproduce this on two machines regularly. Steps to Reproduce: 1. start fedora 29 2. login to gnome 3. work a little time with the system 4. shutdown Actual results: The system hangs with the following message "A stop job is running for User Manager with UID 1000" for about 90 seconds Expected results: Fast shutdown. Additional info: I attached an extract of the systemd-journal and a foto of the message.
Created attachment 1511675 [details] Foto
Created attachment 1511676 [details] complete system-d journal
I do have the exact same bug! Didn't know it was because gnome-search-tool. I did open a bug for it: https://bugzilla.redhat.com/show_bug.cgi?id=1664491 But I think this one is better.
*** Bug 1664491 has been marked as a duplicate of this bug. ***
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.
I still have the bug under Fedora 30.
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.
I can't reopen this issue, but I definitively had this bug on Fedora 30. If the owner of this bug could simply change the affected version, that would be nice. I'm on Fedora 31 now, and waiting to see if the bug if still here (to reproduce it, I need to shutdown my pc, which I don't do very often ;)).
Sorry for double posting, there's been an issue with the server (internal error) and it ended up like that.