Bugzilla – Bug 147076
gnome-volume-manager crashes during login after upgrade from 10.1beta1 to 10.1beta2
Last modified: 2006-02-02 11:19:39 UTC
After upgrading from SuSE 10.1beta1 to 10.1beta2, 3 warnings appear every time I try to log into desktop regarding gnome-volume-manager crashing. I hit the "restart application" button on each window, and no more errors appear. The following lines are in my ~/.xsession-errors: (gnome-volume-manager:4243): GnomeUI-CRITICAL **: gnome_client_set_id: assertion `!GNOME_CLIENT_CONNECTED (client)' failed Bonobo-ERROR **: file bonobo-ui-init-gtk.c: line 74 (add_gtk_arg_callback): assertion failed: (init_info != NULL) aborting... (gnome-volume-manager:4241): GnomeUI-CRITICAL **: gnome_client_set_id: assertion `!GNOME_CLIENT_CONNECTED (client)' failed Bonobo-ERROR **: file bonobo-ui-init-gtk.c: line 74 (add_gtk_arg_callback): assertion failed: (init_info != NULL) aborting...
So - I can reproduce this too every time, Some more details: /proc/<pid>/cmdline is: gnome-volume-manager --sm-disable ie. no particularly funky args. No idea what --sm-disable, prolly SM related; so odd that it's then trying to connect to the session mgr. That is - unless the argument stuff has got really twisted ;-) Also /proc/<pid>/environ shows no SESSION_MANAGER value no idea if that's normal.
Interestingly gnome-power-manager also crashes for me with the same symptoms on login (B2). Amazingly you can re-run gnome-volume-manager just fine from the console subsequently; even unset SESSION_MANAGER; gnome-volume-manager --sm-disable works fine.
Hmm - the power-manager failure is a red-herring, xsession-errors shows it's related to failing to launch dbus - perhaps a 2nd display problem. strace shows the real crashing command line is: /opt/gnome/bin/gnome-volume-manager \ --sm-config-prefix /gnome-volume-manager-QpjctG/ \ --sm-client-id 117f0000020001129023848000001173 --screen 0 which exhibits the error for me (with unset SESSION_MANAGER)
We were starting in previous versions gnome-*-manager without --sm-disable, which made them be saved to the session. Now we start them with --sm-disable, but the old ones are still in the session. Could you remove all gnome-*-manager processes from the sessions capplet, except the ones with --sm-disable, and see if they still crash?
Created attachment 66031 [details] my ~/.gnome2/session file JP asked for this - perhaps it helps :-)
I had 3 entries at the top of ~/.gnome2/session containing gnome-volume-manager, which I removed, leaving 1 entry at the bottom of my config for gnome-volume-manager with --sm-disable. After making the change and logging out without "save current setup" checked, then logging back in again, the problem is no longer present.
#0 0xb7392827 in raise () from /lib/libc.so.6 #1 0xb7393f19 in abort () from /lib/libc.so.6 #2 0xb76e5e94 in g_logv () from /opt/gnome/lib/libglib-2.0.so.0 #3 0xb76e5ed5 in g_log () from /opt/gnome/lib/libglib-2.0.so.0 #4 0xb76e5f57 in g_assert_warning () from /opt/gnome/lib/libglib-2.0.so.0 #5 0xb7e335b7 in add_gtk_arg_callback (con=0x805df78, reason=3085312463, opt=0xb7e6de6c, arg=0x80615f8 "0", data=0xb7e621ea) at bonobo-ui-init-gtk.c:74 #6 0xb7cbc017 in invokeCallbacksOPTION (con=0x805df78, opt=0xb7e6de6c, myOpt=0xb7e6de6c, myData=0xb7e621ea, shorty=0) at popt.c:159 #7 0xb7cbc052 in invokeCallbacksOPTION (con=0x805df78, opt=0x805c6fc, myOpt=0xb7e6de6c, myData=0xb7e621ea, shorty=0) at popt.c:139 #8 0xb7cbce1e in poptGetNextOpt (con=0x805df78) at popt.c:974 #9 0x0804d85b in main ()
*** Bug 146299 has been marked as a duplicate of this bug. ***
Fix submitted be Jeff.