Arch Linux

Please read this before reporting a bug:

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
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Description: 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 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:

Steps to reproduce:
* Plug in Logitec USB dongle.
* Attempt to start gnome-shell session.
This task depends upon

Closed by  Jan de Groot (JGC)
Friday, 03 June 2016, 15:42 GMT
Reason for closing:  Fixed
Comment by Jan de Groot (JGC) - Friday, 12 June 2015, 09:04 GMT
Can you add info from dmesg about this one?
gnome-settings-[1294]: segfault at 20 ip 00007f0086facf78 sp 00007ffe303aa7d0 error 6 in li

Crash in libinput?
Comment by richard parris (arpee) - Monday, 15 June 2015, 02:38 GMT
I have updated the Gist with dmesg output.

It does look like something failing on a null value in the USB devices internal information.