Version-Release number of selected component (if applicable): bolt-0.8-4.fc32.x86_64 How reproducible: Always Steps to Reproduce: 1. Install Fedora 31 on a fresh Lenovo X1; dnf update; then upgrade it to rawhide 2. Boot machine Actual results: From "journalctl -b -u bolt", repeating five times: > systemd[1]: Starting Thunderbolt system service... > boltd[951]: bolt 0.8 starting up > boltd[951]: Failed to set scheduler settings: Permission denied > systemd[1]: bolt.service: Main process exited, code=killed, status=5/TRAP > systemd[1]: bolt.service: Failed with result 'signal'. > systemd[1]: Failed to start Thunderbolt system service. > systemd[1]: bolt.service: Scheduled restart job, restart counter is at 1. > systemd[1]: Stopped Thunderbolt system service. Expected results: No issues. Or more useful error messages how to fix "Permission denied".
Ah, I was too fast. This looks like a glib2 issue and that bolt was just the first service to run into this. I saw a similar error later for ModemManager on my machine, and I also found https://bugzilla.mozilla.org/show_bug.cgi?id=1611712 now. This very problem went away after downgrading from glib2-2.63.5-1 (and ModemManager-1.10.8-2) to glib2-2.63.3-1 (and ModemManager-1.10.8-1). Not sure what to do with this ticket - change component?
(In reply to Andre Klapper from comment #1) > Ah, I was too fast. This looks like a glib2 issue and that bolt was just the > first service to run into this. > I saw a similar error later for ModemManager on my machine, and I also found > https://bugzilla.mozilla.org/show_bug.cgi?id=1611712 now. > > This very problem went away after downgrading from glib2-2.63.5-1 (and > ModemManager-1.10.8-2) to glib2-2.63.3-1 (and ModemManager-1.10.8-1). > > Not sure what to do with this ticket - change component? Yeah, sounds good to me.
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
This can be closed.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 '32'. 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 32 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 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.