GNOME Bugzilla – Bug 513649
crash in Volume Control: Starting session
Last modified: 2008-02-01 11:57:05 UTC
What were you doing when the application crashed? Starting session Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.23-1-686 #1 SMP Fri Dec 21 13:57:07 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Nuvola Memory status: size: 35905536 vsize: 35905536 resident: 14647296 share: 10395648 rss: 14647296 rss_rlim: 4294967295 CPU usage: start_time: 1201861324 rtime: 22 utime: 16 stime: 6 cutime:1 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 0xb6e8e6b0 (LWP 3991)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187717
Thread 1 (Thread 0xb6e8e6b0 (LWP 3991))
----------- .xsession-errors --------------------- Avertissement du gestionnaire de fenêtres : La lecture du fichier de session enregistré /home/xavier/.metacity/sessions/default0.ms a échoué : Failed to open file '/home/xavier/.metacity/session Checking for Xgl: not present. Detected PCI ID for VGA: 01:00.0 0300: 10de:0298 (rev a1) (prog-if 00 [VGA controller]) Checking for texture_from_pixmap: present. Checking for non power of two support: present. Checking for Composite extension: present. Comparing resolution (1440x900) to maximum 3D texture size (4096): Passed. Checking for nVidia: present. Checking for FBConfig: present. Checking for Xgl: not present. Starting gtk-window-decorator seahorse nautilus module initialized Initializing gnome-mount extension (gnome-panel:3847): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -15 and height 24 --------------------------------------------------
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 ***