GNOME Bugzilla – Bug 513430
crash in Volume Control: nix
Last modified: 2008-01-31 18:58:37 UTC
What were you doing when the application crashed? nix Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: SphereCrystal Memory status: size: 34918400 vsize: 34918400 resident: 13864960 share: 9723904 rss: 13864960 rss_rlim: 4294967295 CPU usage: start_time: 1201781181 rtime: 50 utime: 40 stime: 10 cutime:2 cstime: 3 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6e226b0 (LWP 3823)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187576
Thread 1 (Thread 0xb6e226b0 (LWP 3823))
----------- .xsession-errors (52 sec old) --------------------- /etc/gdm/Xsession: Beginning session setup... can't lock memory: Cannot allocate memoryWARNING: not using secure memory for passwords SESSION_MANAGER=local/t23arbeitmichael:/tmp/.ICE-unix/3584 Fenstermanager-Warnung:Gespeicherte Sitzungsdatei /home/mik/.metacity/sessions/default0.ms konnte nicht gelesen werden: Failed to open file '/home/mik/.metacity/sessions/default0.ms': Datei oder Verze seahorse nautilus module initialized Initializing gnome-mount extension (gnome-panel:3651): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -15 and height 25 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 --------------------------------------------------
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 ***