Bug 1085493

Created attachment 884178 [details]
File: backtrace

Created attachment 884179 [details]
File: cgroup

Created attachment 884180 [details]
File: core_backtrace

Created attachment 884181 [details]
File: dso_list

Created attachment 884182 [details]
File: environ

Created attachment 884183 [details]
File: exploitable

Created attachment 884184 [details]
File: limits

Created attachment 884185 [details]
File: maps

Created attachment 884186 [details]
File: open_fds

Created attachment 884187 [details]
File: proc_pid_status

Created attachment 884188 [details]
File: var_log_messages

#2  0x00007fffdf960a48 in wacom_set_property (device=device@entry=0x7fffcc004ce0, property=property@entry=0x7fffffffd3f0)
    at gsd-wacom-manager.c:263
263		device_set_property (xdev, gsd_wacom_device_get_tool_name (device), property);
(gdb) list
258			    PropertyHelper *property)
259	{
260		XDevice *xdev;
261	
262		xdev = open_device (device);
263		device_set_property (xdev, gsd_wacom_device_get_tool_name (device), property);
264		XCloseDevice (GDK_DISPLAY_XDISPLAY (gdk_display_get_default ()), xdev);
265	}
266

It tries to open the device but doesn't check for NULL before setting the property.  I think when the wacom goes to sleep it disconnects from usb.  So this crash happens pretty much every time the lock screen is on for a while.

Having gnome-settings-daemon not running breaks a lot of things.

This must be related to the the wacom disconnecting because every time I lock the screen it crashes because gnome-shell immediately turns off the monitors.  So every time I want to unlock the screen I have to switch to a console and kill gnome-shell and then restart gnome-settings-daemon in a terminal window.

This must be caused by a fairly recent change because I certainly would have noticed if this had been happening earlier.  I will check tomorrow if an older version works and also determine if it crashes on turning the monitor off or turning it back on.

Some interesting information from the log.  It appears that when the screen is turned off, the usb device disconnects for a few seconds, reconnects for a few seconds, then disconnects until turned back on.  The crash appears to happen around the same time that colord detects the monitors going away, so perhaps it's related to notifications from udev (or similar).  By the time it receives the message that the device is connected, the device is already gone again.

Apr  9 10:29:45 siebs kernel: [77583.203119] usb 3-1: USB disconnect, device number 11
Apr  9 10:29:45 siebs kernel: usb 3-1: USB disconnect, device number 11
Apr  9 10:29:48 siebs kernel: [77585.892038] usb 3-1: new full-speed USB device number 12 using uhci_hcd
Apr  9 10:29:48 siebs kernel: usb 3-1: new full-speed USB device number 12 using uhci_hcd
Apr  9 10:29:48 siebs kernel: [77586.250064] usb 3-1: New USB device found, idVendor=056a, idProduct=003f
Apr  9 10:29:48 siebs kernel: [77586.250071] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr  9 10:29:48 siebs kernel: [77586.250074] usb 3-1: Product: DTZ-2100
Apr  9 10:29:48 siebs kernel: [77586.250078] usb 3-1: Manufacturer: Tablet
Apr  9 10:29:48 siebs kernel: usb 3-1: New USB device found, idVendor=056a, idProduct=003f
Apr  9 10:29:48 siebs kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr  9 10:29:48 siebs kernel: usb 3-1: Product: DTZ-2100
Apr  9 10:29:48 siebs kernel: usb 3-1: Manufacturer: Tablet
Apr  9 10:29:48 siebs kernel: [77586.253225] input: Wacom Cintiq 21UX as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/input/input25
Apr  9 10:29:48 siebs kernel: input: Wacom Cintiq 21UX as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/input/input25
Apr  9 10:29:48 siebs mtp-probe: checking bus 3, device 12: "/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1"
Apr  9 10:29:48 siebs mtp-probe: bus: 3, device: 12 was not an MTP device
Apr  9 10:29:52 siebs kernel: [77589.453101] usb 3-1: USB disconnect, device number 12
Apr  9 10:29:52 siebs kernel: usb 3-1: USB disconnect, device number 12
Apr  9 10:30:38 siebs kernel: [77636.333675] gnome-settings-[9575]: segfault at 0 ip 000000313060447d sp 00007fffec478c70 error 4 in libXi.so.6.1.0[3130600000+f000]
Apr  9 10:30:38 siebs kernel: gnome-settings-[9575]: segfault at 0 ip 000000313060447d sp 00007fffec478c70 error 4 in libXi.so.6.1.0[3130600000+f000]
Apr  9 10:30:39 siebs abrt-hook-ccpp: Saved core dump of pid 9575 (/usr/libexec/gnome-settings-daemon) to /var/tmp/abrt/ccpp-2014-04-09-10:30:38-9575 (83107840 bytes)
Apr  9 10:30:39 siebs colord: Automatic remove of icc-e93b12061bfe228d4e7377873d870ac4 from xrandr-Wacom Tech-Cintiq21UX-7ICM00291
Apr  9 10:30:39 siebs colord: Profile removed: icc-e93b12061bfe228d4e7377873d870ac4
Apr  9 10:30:39 siebs colord: Automatic remove of icc-2ee82cb47cba89f962f7d3156955b5cc from xrandr-ViewSonic Corporation-VG920-PT1062361513
Apr  9 10:30:39 siebs colord: Profile removed: icc-2ee82cb47cba89f962f7d3156955b5cc
Apr  9 10:30:39 siebs colord: Profile removed: icc-17bc42e453717a6b9bd7c294e811c0ae
Apr  9 10:30:39 siebs colord: device removed: xrandr-Wacom Tech-Cintiq21UX-7ICM00291
Apr  9 10:30:39 siebs colord: device removed: xrandr-ViewSonic Corporation-VG920-PT1062361513

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.