Bug 588194

Summary: Gnome desktop crashes when left alone for a while (KVM involvement?)
Product: [openSUSE] openSUSE 11.2 Reporter: John Beranek <john>
Component: GNOMEAssignee: E-mail List <gnome-bugs>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Critical    
Priority: P5 - None CC: zbycho
Version: Final   
Target Milestone: ---   
Hardware: x86   
OS: openSUSE 11.2   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Text from .xsession-errors including a gnome-session backtrace

Description John Beranek 2010-03-13 20:46:48 UTC 
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8

When I leave my GNOME desktop alone for a while (frequently because I switch away from it with a KVM, so this may have a bearing) the desktop session crashes and I end back up at the GDM login screen.

I've looked in my .xsession-errors and theirs a suspicious snippet, which I've attached as a file.


Reproducible: Sometimes

Steps to Reproduce:
1.Login to GNOME desktop
2.Leave it alone for a bit, possibly switching away from the desktop

Actual Results:  
Desktop stays running

Expected Results:  
Desktop crashes


$ rpm -q gnome-power-manager
gnome-power-manager-2.28.2-1.1.1.i586
$ rpm -q gnome-screensaver
gnome-screensaver-2.28.3-0.1.1.i586
$ rpm -q gnome-session
gnome-session-2.28.0-3.5.i586
$ uname -a
Linux linda 2.6.31.12-0.1-pae #1 SMP 2010-01-27 08:20:11 +0100 i686 athlon i386 GNU/Linux

I've now tried uninstalling gnome-power-manager and gnome-screensaver to see if that stops the desktop crashing.
Comment 1 John Beranek 2010-03-13 20:48:42 UTC 
Created attachment 348333 [details]
Text from .xsession-errors including a gnome-session backtrace

The attachment mentioned in the bug report that I forgot to add.
Comment 2 Mr Pingwin 2010-05-15 10:19:57 UTC 
I have similar problem, whole Gnome destop crashes. I always end up with GDM.
It occurs often while pluging in the power cord. Gnome-power-manager bug?
KVM not in use.



May 14 22:16:51 kryton gnome-session[2678]: devkit-power-gobject-CRITICAL: dkp_device_get_object_path: assertion `DKP_IS_DEVICE (device)' failed
May 14 22:16:51 kryton gnome-session[2678]: ******************* START ********************************
May 14 22:16:51 kryton gnome-session[2678]: Frame 0: /usr/bin/gnome-session [0x805f924]
May 14 22:16:51 kryton gnome-session[2678]: Frame 1: /usr/bin/gnome-session [0x805fac9]
May 14 22:16:51 kryton gnome-session[2678]: Frame 2: [0xffffe400]
May 14 22:16:51 kryton gnome-session[2678]: Frame 3: /usr/lib/libglib-2.0.so.0(g_str_hash+0x5) [0xb7104c55]
May 14 22:16:51 kryton gnome-session[2678]: Frame 4: /usr/lib/libglib-2.0.so.0 [0xb70d3016]
May 14 22:16:51 kryton gnome-session[2678]: Frame 5: /usr/lib/libdevkit-power-gobject.so.1 [0xb71ecc22]
May 14 22:16:51 kryton gnome-session[2678]: Frame 6: /usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__STRING+0x93) [0xb71bd583]
May 14 22:16:51 kryton gnome-session[2678]: Frame 7: /usr/lib/libdbus-glib-1.so.2 [0xb72643e0]
May 14 22:16:51 kryton gnome-session[2678]: Frame 8: /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x1e2) [0xb71b0192]
May 14 22:16:51 kryton gnome-session[2678]: Frame 9: /usr/lib/libgobject-2.0.so.0 [0xb71c5d16]
May 14 22:16:51 kryton gnome-session[2678]: Frame 10: /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x736) [0xb71c70e6]
May 14 22:16:51 kryton gnome-session[2678]: Frame 11: /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x27) [0xb71c7567]
May 14 22:16:51 kryton gnome-session[2678]: Frame 12: /usr/lib/libdbus-glib-1.so.2 [0xb726566f]
May 14 22:16:51 kryton gnome-session[2678]: Frame 13: /lib/libdbus-1.so.3(dbus_connection_dispatch+0x353) [0xb7221a53]
May 14 22:16:51 kryton gnome-session[2678]: Frame 14: /usr/lib/libdbus-glib-1.so.2 [0xb725bc0d]
May 14 22:16:51 kryton gnome-session[2678]: Frame 15: /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x212) [0xb70e14c2]
May 14 22:16:51 kryton gnome-session[2678]: Frame 16: /usr/lib/libglib-2.0.so.0 [0xb70e4d98]
May 14 22:16:51 kryton gnome-session[2678]: Frame 17: /usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1bf) [0xb70e51ef]
May 14 22:16:51 kryton gnome-session[2678]: Frame 18: /usr/lib/libgtk-x11-2.0.so.0(gtk_main+0xb9) [0xb7517b49]
May 14 22:16:51 kryton gnome-session[2678]: Frame 19: /usr/bin/gnome-session [0x806148b]
May 14 22:16:51 kryton gnome-session[2678]: Frame 20: /lib/libc.so.6(__libc_start_main+0xfe) [0xb6e15ace]
May 14 22:16:51 kryton gnome-session[2678]: Frame 21: /usr/bin/gnome-session [0x8050621]
May 14 22:16:51 kryton gnome-session[2678]: ******************* END **********************************
May 14 22:16:51 kryton kernel: [15208.375204] compiz[2894]: segfault at 28 ip 080568ac sp bf916f40 error 4 in compiz[8048000+3c000]
Comment 3 Mr Pingwin 2010-06-07 18:11:15 UTC 
It seems the bug is somewhere in DeviceKit-power. I have installed new version from obs://build.opensuse.org/Base (It's called UPower now) and I have seen NO problem since there. 
It's possible to make an official update for that? 
So more people who have the same problem could test it.

kryton:/home/pingwin # LANG=C zypper if devicekit-power:

Information for package devicekit-power:

Repository: @System
Name: DeviceKit-power
Version: 0.9.1-1.1
Arch: i586
Vendor: obs://build.opensuse.org/Base
Installed: Yes
Status: up-to-date
Installed Size: 0 B
Summary: Power Device Enumeration Framework
Description: 
UPower is an abstraction for enumerating power devices, listening to
device events and querying history and statistics. Any application or
service on the system can access the org.freedesktop.UPower service
via the system message bus. Some operations (such as suspending the
system) are restricted using PolicyKit.

This package provides a compatibily layer between upower and
DeviceKit-power.

kryton:/home/pingwin # LANG=C zypper se upower
Loading repository data...
Reading installed packages...

S | Name            | Summary                                      | Type   
--+-----------------+----------------------------------------------+--------
i | libupower-glib1 | Power Device Enumeration Framework - Library | package
i | upower          | Power Device Enumeration Framework           | package
i | upower-lang     | Languages for package upower                 | package
Comment 4 Mr Pingwin 2010-06-07 18:13:33 UTC 
The same problem is also reported and triaged here: https://qa.mandriva.com/show_bug.cgi?id=56286
Comment 5 John Beranek 2010-09-13 10:35:04 UTC 
Still happening, and even more frequently - even though I've removed gnome-power-manager.

Looked to remove DeviceKit-power, but too many things depend on it. :(

Latest crash:

gnome-session[4168]: devkit-power-gobject-CRITICAL: dkp_device_get_object_path:
assertion `DKP_IS_DEVICE (device)' failed
gnome-session[4168]: ******************* START ********************************
gnome-session[4168]: Frame 0: /usr/bin/gnome-session [0x805f924]
gnome-session[4168]: Frame 1: /usr/bin/gnome-session [0x805fac9]
gnome-session[4168]: Frame 2: [0xffffe400]
gnome-session[4168]: Frame 3: /usr/lib/libglib-2.0.so.0(g_str_hash+0x5) [0xb7145c55]
gnome-session[4168]: Frame 4: /usr/lib/libglib-2.0.so.0 [0xb7114016]
gnome-session[4168]: Frame 5: /usr/lib/libdevkit-power-gobject.so.1 [0xb722dc22]
gnome-session[4168]: Frame 6: /usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__STRING+0x93) [0xb71fe583]
gnome-session[4168]: Frame 7: /usr/lib/libdbus-glib-1.so.2 [0xb72a53e0]
gnome-session[4168]: Frame 8: /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x1e2) [0xb71f1192]
gnome-session[4168]: Frame 9: /usr/lib/libgobject-2.0.so.0 [0xb7206d16]

(gpk-update-icon:4465): devkit-power-gobject-CRITICAL **: dkp_device_get_object_path: assertion `DKP_IS_DEVICE (device)' failed
gnome-session[4168]: Frame 10: /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x736) [0xb72080e6]
gnome-session[4168]: Frame 11: /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x27) [0xb7208567]
gnome-session[4168]: Frame 12: /usr/lib/libdbus-glib-1.so.2 [0xb72a666f]
gnome-session[4168]: Frame 13: /lib/libdbus-1.so.3(dbus_connection_dispatch+0x353) [0xb7262a53]
gnome-session[4168]: Frame 14: /usr/lib/libdbus-glib-1.so.2 [0xb729cc0d]
gnome-session[4168]: Frame 15: /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x212) [0xb71224c2]
gnome-session[4168]: Frame 16: /usr/lib/libglib-2.0.so.0 [0xb7125d98]
gnome-session[4168]: Frame 17: /usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1bf) [0xb71261ef]
gnome-session[4168]: Frame 18: /usr/lib/libgtk-x11-2.0.so.0(gtk_main+0xb9) [0xb7558b49]
gnome-session[4168]: Frame 19: /usr/bin/gnome-session [0x806148b]
gnome-session[4168]: Frame 20: /lib/libc.so.6(__libc_start_main+0xfe) [0xb6e56ace]
gnome-session[4168]: Frame 21: /usr/bin/gnome-session [0x8050621]
gnome-session[4168]: ******************* END **********************************
/usr/bin/compiz-manager: line 439:  4435 Segmentation fault      ${COMPIZ_BIN_PATH}${COMPIZ_NAME} $COMPIZ_OPTIONS "$@" $COMPIZ_PLUGINS
Comment 6 John Beranek 2010-09-13 10:58:10 UTC 
FWIW, I'm going to see if an online upgrade to 11.3 fixes it.
Comment 7 John Beranek 2010-09-22 22:08:39 UTC 
Also FWIW, the upgrade to 11.3 _does_ appear to have fixed the crashes.
Comment 8 Vincent Untz 2012-05-16 12:20:51 UTC 
Closing as per last comment.