Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#45301 - [gnome-settings-daemon] cannot start with some USB devices plugged in.
Attached to Project:
Arch Linux
Opened by richard parris (arpee) - Friday, 12 June 2015, 05:25 GMT
Last edited by Jan de Groot (JGC) - Friday, 03 June 2016, 15:42 GMT
Opened by richard parris (arpee) - Friday, 12 June 2015, 05:25 GMT
Last edited by Jan de Groot (JGC) - Friday, 03 June 2016, 15:42 GMT
|
DetailsDescription: Gnome Shell fails to start with 'Oh, no something has gone wrong." message if Logitec USB Headset dongle is plugged in.
I have raised this bug separately from https://bugs.archlinux.org/task/44548#comment136079 as it has similar symptoms, but is unrelated to the Nvidia/dual monitor configuration issue dealt with there. I can replicate this bug each time. Without the dongle gnome shell starts without incident. With the dongle in, the issue occurs every time. Ever other periferal has been removed and a single monitor was plugged in to test this. The problem can be traced to Gnome settings daemon strating in both systemd journal output and by inserting the dongle, stopping gnome-settings-daemon, then attempting a restart. Additional info: Journal and console output at: https://gist.githubusercontent.com/arpee/9bb21e29fe817dc375c0/raw/851cdf8cb4ee4b83c67edd5f3d3b8029b06b105f/Arch%20Bug%20Report%20-%20gnome-settings-daemon Steps to reproduce: * Plug in Logitec USB dongle. * Attempt to start gnome-shell session. |
This task depends upon
gnome-settings-[1294]: segfault at 20 ip 00007f0086facf78 sp 00007ffe303aa7d0 error 6 in li
Crash in libinput?
It does look like something failing on a null value in the USB devices internal information.