GNOME Bugzilla – Bug 524293
Bug 524291 – crash in Evolution: svn head build, File/Quit, startup
Last modified: 2008-05-26 07:29:09 UTC
Steps to reproduce: 1. 2. 3. Stack trace: Distribution: Gentoo Base System release 1.12.11.1 Gnome Release: 2.20.3 2008-01-17 (Gentoo) BugBuddy Version: 2.20.1 System: Linux 2.6.24-gentoo-r3 #2 SMP PREEMPT Fri Mar 14 12:55:56 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: marble-look Icon Theme: gnome Memory status: size: 144703488 vsize: 144703488 resident: 38174720 share: 19247104 rss: 38174720 rss_rlim: 4294967295 CPU usage: start_time: 1206446673 rtime: 362 utime: 312 stime: 50 cutime:31 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/evo/bin/evolution' [?1034hUsing host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb67b76d0 (LWP 17278)] [New Thread 0xafe37b90 (LWP 17367)] [New Thread 0xb2fcbb90 (LWP 17304)] [New Thread 0xb37ccb90 (LWP 17303)] [New Thread 0xb3fd9b90 (LWP 17302)] 0xb7f98410 in __kernel_vsyscall ()
+ Trace 193285
Thread 1 (Thread 0xb67b76d0 (LWP 17278))
----------- .xsession-errors (55445 sec old) --------------------- compiz (core) - Warn: pixmap 0x10b7443 can't be bound to texture (gnome-terminal:31572): Vte-WARNING **: No handler for control sequence `device-control-string' defined. stop id=21 "Fruth appliance config"-"Setup appliances for messaging" 1:07:35 00-58-48 hours=1 min=67 secs=4055 No running windows found ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) -------------------------------------------------- Other information:
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 531739 ***