GNOME Bugzilla – Bug 513311
crash in Volume Control: Just after log in. It c...
Last modified: 2008-01-31 11:30:20 UTC
What were you doing when the application crashed? Just after log in. It crashed when gnome session was opened. 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: MurrinaAquaIsh Icon Theme: Neu Memory status: size: 50995200 vsize: 50995200 resident: 13467648 share: 9908224 rss: 13467648 rss_rlim: 4294967295 CPU usage: start_time: 1201735283 rtime: 22 utime: 18 stime: 4 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6e766b0 (LWP 6658)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 187499
Thread 1 (Thread 0xb6e766b0 (LWP 6658))
----------- .xsession-errors (8 sec old) --------------------- [DEBUG]: File: /usr/lib/tomboy/addins/WebDavSyncService.dll [DEBUG]: AddinManager.OnAddinLoaded: Tomboy.FileSystemSyncServiceAddin [DEBUG]: Name: Local Directory Sync Service Add-in [DEBUG]: Description: Synchronize Tomboy Notes to a local file system path [DEBUG]: Namespace: Tomboy [DEBUG]: Enabled: True [DEBUG]: File: /usr/lib/tomboy/addins/FileSystemSyncService.dll [DEBUG]: Unable to locate 'gnomesu' in your PATH [DEBUG]: Using '/usr/bin/gksu' as GUI 'su' tool [DEBUG]: Successfully found all system tools [DEBUG]: Unable to locate 'wdfs' in your PATH [DEBUG]: Tomboy remote control active. [DEBUG]: EnableDisable Called: enabling... True [DEBUG]: Binding key '<Control><Alt>N' for '/apps/tomboy/global_keybindings/open_start_here' [DEBUG]: Binding key '<Alt>F12' for '/apps/tomboy/global_keybindings/open_recent_changes' --------------------------------------------------
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 ***