GNOME Bugzilla – Bug 513204
crash in Volume Control: Plantage au lancement de...
Last modified: 2008-01-30 18:12:51 UTC
What were you doing when the application crashed? Plantage au lancement de l'applet en début de session. Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-2-k7 #1 SMP Fri Aug 31 01:02:37 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Indubstrial Icon Theme: Nuovo Memory status: size: 43229184 vsize: 43229184 resident: 15532032 share: 11075584 rss: 15532032 rss_rlim: 4294967295 CPU usage: start_time: 1201716113 rtime: 40 utime: 34 stime: 6 cutime:2 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/mixer_applet2' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6f146b0 (LWP 4044)] (no debugging symbols found) 0xb786f321 in waitpid () from /lib/libpthread.so.0
+ Trace 187432
Thread 1 (Thread 0xb6f146b0 (LWP 4044))
----------- .xsession-errors (80 sec old) --------------------- /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/LadyMac:/tmp/.ICE-unix/3733 Initializing gnome-mount extension xrdb: "*Label.background" on line 220 overrides entry on line 150 xrdb: "*Text.background" on line 226 overrides entry on line 191 xrdb: "*Label.foreground" on line 232 overrides entry on line 151 xrdb: "*Text.foreground" on line 238 overrides entry on line 192 ** Message: failed to load session from /home/flamm/.nautilus/saved-session-RTPNZT (gnome-panel:3794): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 31 --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 513018 ***