Gnome volume-manager quits just before Desktop shows

Bug #28841 reported by Frank McCormick
10
Affects Status Importance Assigned to Milestone
gnome-volume-manager (Ubuntu)
Fix Released
Critical
Martin Pitt

Bug Description

Ever since the update(s) on January 16th, I get a warning the Gnome volume-manager has quit unexpectedly just before the desktop displays.
CPU usgae goes to 100% ( top reports X is using half that with the update notifier sucking up the rest. A killall gnome-panel restores most thing to normal.

Revision history for this message
Frank McCormick (fmccormick) wrote :
Download full text (5.1 KiB)

From: <>
To: <email address hidden>
X-Mailer: bug-buddy 2.13.0
Subject: On boot , gnome volume-manager quits unexpectedly

Distribution: Ubuntu 6.04 (dapper)
Package: gnome-volume-manager
Severity: Normal
Version: GNOME2.13.5 unspecified
Gnome-Distributor: Ubuntu
Synopsis: On boot , gnome volume-manager quits unexpectedly
Bugzilla-Product: gnome-volume-manager
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.13.0)
Description:
Description of the crash:

Steps to reproduce the crash:

1.Boot the machine!
2.
3.

Expected Results:

How often does this happen?

Additional Information:

Debugging Information:

Backtrace was generated from '/usr/bin/gnome-volume-manager'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224034624 (LWP 4330)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb74b7463 in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7f11226 in libgnomeui_module_info_get ()
  ...

Read more...

Revision history for this message
Martin Pitt (pitti) wrote :

Linked upstream bug report. I'm puzzled with that, it triggers an assertion in poptGetNextOpt().

Changed in gnome-volume-manager:
assignee: nobody → pitti
status: Unconfirmed → Confirmed
Revision history for this message
calimarno (calimarno) wrote :

I'm having the same problem:

Debugging Information:

Backtrace was generated from '/usr/bin/gnome-volume-manager'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1223772480 (LWP 7740)]
0xb74f600e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
#0 0xb74f600e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
#1 0xb7f41592 in libgnomeui_module_info_get ()
   from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 0xb7527957 in g_logv () from /usr/lib/libglib-2.0.so.0
#4 0xb7527c14 in g_log () from /usr/lib/libglib-2.0.so.0
#5 0xb7527c80 in g_assert_warning () from /usr/lib/libglib-2.0.so.0
#6 0xb7e97f40 in bonobo_dock_layout_parse_string ()
   from /usr/lib/libbonoboui-2.so.0
#7 0xb7d037e4 in poptSetExecPath () from /lib/libpopt.so.0
#8 0xb7d0384f in poptSetExecPath () from /lib/libpopt.so.0
#9 0xb7d04d0e in poptGetNextOpt () from /lib/libpopt.so.0
#10 0x0804fc7f in ?? ()
#11 0x08062db0 in ?? ()
#12 0x08051a50 in _IO_stdin_used ()
#13 0xbfd95f98 in ?? ()
#14 0x00000000 in ?? ()

Thread 1 (Thread -1223772480 (LWP 7740)):
#0 0xb74f600e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
No symbol table info available.
#1 0xb7f41592 in libgnomeui_module_info_get ()
   from /usr/lib/libgnomeui-2.so.0
No symbol table info available.
#2 <signal handler called>
No symbol table info available.
#3 0xb7527957 in g_logv () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#4 0xb7527c14 in g_log () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#5 0xb7527c80 in g_assert_warning () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#6 0xb7e97f40 in bonobo_dock_layout_parse_string ()
   from /usr/lib/libbonoboui-2.so.0
No symbol table info available.
#7 0xb7d037e4 in poptSetExecPath () from /lib/libpopt.so.0
No symbol table info available.
#8 0xb7d0384f in poptSetExecPath () from /lib/libpopt.so.0
No symbol table info available.
#9 0xb7d04d0e in poptGetNextOpt () from /lib/libpopt.so.0
No symbol table info available.
#10 0x0804fc7f in ?? ()
No symbol table info available.
#11 0x08062db0 in ?? ()
No symbol table info available.
#12 0x08051a50 in _IO_stdin_used ()
No symbol table info available.
#13 0xbfd95f98 in ?? ()
No symbol table info available.
#14 0x00000000 in ?? ()
No symbol table info available.
#0 0xb74f600e in __waitpid_nocancel () from /lib/tls/libpthread.so.0

Revision history for this message
Dani Alonso (dalonso) wrote :

Same here. Starting gnome-session from a terminal shows this:

(gnome-volume-manager:4500): GnomeUI-CRITICAL **: gnome_client_set_id: assertion `!GNOME_CLIENT_CONNECTED (client)' failed

Bonobo-ERROR **: file bonobo-ui-init-gtk.c: line 87 (add_gtk_arg_callback): assertion failed: (init_info != NULL)

Revision history for this message
Martin Pitt (pitti) wrote :

 gnome-volume-manager (1.5.9-0ubuntu2) dapper; urgency=low
 .
   * Add debian/patches/05_goption.patch:
     - Fix crash in popt option processing by replacing the obsolete popt with
       GOption.
     - Patch taken from CVS head.
     - Malone #28841

Changed in gnome-volume-manager:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.