GNOME Bugzilla – Bug 488304
crash in Volume Control: From gnome-panel, right ...
Last modified: 2007-10-20 16:15:29 UTC
Version: 2.18.0 What were you doing when the application crashed? From gnome-panel, right clicking on the icon of a speaker in the upper-right corner and select "Open Volume Control". Always reproducable. Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 32030720 vsize: 32030720 resident: 12439552 share: 9224192 rss: 12439552 rss_rlim: 4294967295 CPU usage: start_time: 1192806686 rtime: 20 utime: 15 stime: 5 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-volume-control' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6ebe6b0 (LWP 4127)] [New Thread 0xb6c76b90 (LWP 4129)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 171437
Thread 1 (Thread 0xb6ebe6b0 (LWP 4127))
----------- .xsession-errors (19 sec old) --------------------- /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/unix-petur:/tmp/.ICE-unix/3965 Window manager warning: Failed to read saved session file /home/petur/.metacity/sessions/default0.ms: Failed to open file '/home/petur/.metacity/sessions/default0.ms': No such file or directory ** Message: Not starting remote desktop server Initializing gnome-mount extension (gnome-panel:4032): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 24 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 441641 ***