GNOME Bugzilla – Bug 513358
crash in Volume Control: i think i don't use my s...
Last modified: 2008-01-31 11:34:04 UTC
What were you doing when the application crashed? i think i don't use my soud card yesterday... but, an update for this come yesterday. 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: Clearlooks Icon Theme: gnome Memory status: size: 33517568 vsize: 33517568 resident: 12890112 share: 9666560 rss: 12890112 rss_rlim: 4294967295 CPU usage: start_time: 1201763647 rtime: 14 utime: 12 stime: 2 cutime:0 cstime: 2 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 0xb6ec46b0 (LWP 4836)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187535
Thread 1 (Thread 0xb6ec46b0 (LWP 4836))
----------- .xsession-errors --------------------- /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/laptop-ths:/tmp/.ICE-unix/4656 Avertissement du gestionnaire de fenêtres : La lecture du fichier de session enregistré /home/ths/.metacity/sessions/default0.ms a échoué : Failed to open file '/home/ths/.metacity/sessions/defa 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 (gnome-panel:4714): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed --------------------------------------------------
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 ***