GNOME Bugzilla – Bug 513016
crash in Volume Control: Upgraded Linux from 2.6....
Last modified: 2008-01-30 10:54:39 UTC
What were you doing when the application crashed? Upgraded Linux from 2.6.23 to 2.6.24 Distribution: Debian (sid) Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.24-1-686 #1 SMP Mon Jan 28 01:33:13 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 36110336 vsize: 36110336 resident: 13832192 share: 10289152 rss: 13832192 rss_rlim: 4294967295 CPU usage: start_time: 1201674128 rtime: 24 utime: 20 stime: 4 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 0xb6e046b0 (LWP 5371)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 187324
Thread 1 (Thread 0xb6e046b0 (LWP 5371))
----------- .xsession-errors --------------------- ** (devilspie:4685): CRITICAL **: e_sexp_eval: assertion `f->tree != NULL' failed ** (devilspie:4685): CRITICAL **: e_sexp_eval: assertion `f->tree != NULL' failed ** (devilspie:4685): CRITICAL **: e_sexp_eval: assertion `f->tree != NULL' failed ** (devilspie:4685): CRITICAL **: e_sexp_eval: assertion `f->tree != NULL' failed ** (devilspie:4685): CRITICAL **: e_sexp_eval: assertion `f->tree != NULL' failed ** (devilspie:4685): CRITICAL **: e_sexp_eval: assertion `f->tree != NULL' failed ** (devilspie:4685): CRITICAL **: e_sexp_eval: assertion `f->tree != NULL' failed ** (devilspie:4685): CRITICAL **: e_sexp_eval: assertion `f->tree != NULL' failed --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 512924 ***