GNOME Bugzilla – Bug 751563
Ghost Wacom tablet causes assertion failures and (maybe) gnome-session exit
Last modified: 2015-06-30 15:28:19 UTC
Created attachment 306184 [details] session.log I'm experiencing random forced logouts from my session due to gnome-session exiting, and the logs contain this (see attached file): (gnome-settings-daemon:1759): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed gnome-session[1573]: CRITICAL: gsm_manager_set_phase: assertion `GSM_IS_MANAGER (manager)' failed I don't have any Wacom device, so I don't know why this happens. This is very similar to this bug: https://bugzilla.redhat.com/show_bug.cgi?id=962351 I'm not sure that's related at all to the gnome-session exit, but that's probably worth fixing anyway. About gnome-session exiting, the system log contains this: juin 26 20:21:13 milan gdm-password][31268]: pam_unix(gdm-password:session): session closed for user milan juin 26 20:21:13 milan polkitd[1055]: Unregistered Authentication Agent for unix-session:3 (system bus name :1.149, object path /org/freedesktop/Poli juin 26 20:21:13 milan gnome-session[31381]: WARNING: App 'gnome-settings-daemon.desktop' exited with code 1 juin 26 20:21:13 milan gnome-session[31381]: WARNING: Lost name on bus: org.gnome.SessionManager This is on Fedora 22 with gnome-settings-daemon 3.16.2.
Created attachment 306185 [details] /proc/bus/input/devices
Created attachment 306186 [details] Xorg log
Do you have a stack trace for the crash in ABRT perhaps? That would help
I don't have any stack trace, as gnome-session exits with code 1 instead of crashing (as you can see in the log excerpt above). But I have no idea why it behaves that way...
nm-applet and gnome-shell are falling over themselves because of NetworkManager errors. You should double-check the installation of its related packages. gnome-session and co. exit because the X server dies. This isn't too good either: "failed to create drawable"
Wait, I must be dumb. That session.log is completely outdated, it was left behind when the logs were moved to elsewhere in... 2013. The other logs are correct, though. You say it's expected that gnome-session exits because of the X failure? Good to know. I'll investigate the bug on the X side next time I see it. I'm closing this, sorry for the confusion.