GNOME Bugzilla – Bug 524291
crash in Evolution: svn head build, File/Qui...
Last modified: 2008-04-03 13:56:31 UTC
What were you doing when the application crashed? svn head build, File/Quit, --force-shutdown, startup 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: 92954624 vsize: 92954624 resident: 27353088 share: 10395648 rss: 27353088 rss_rlim: 4294967295 CPU usage: start_time: 1206446679 rtime: 186 utime: 160 stime: 26 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/evolution-exchange-storage' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb622c6f0 (LWP 17295)] [New Thread 0xb56feb90 (LWP 24605)] [New Thread 0xb2eb8b90 (LWP 18508)] [New Thread 0xb605db90 (LWP 17298)] 0xb7fd1410 in __kernel_vsyscall ()
+ Trace 193284
Thread 3 (Thread 0xb2eb8b90 (LWP 18508))
----------- .xsession-errors (55442 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) --------------------------------------------------
not sure about target milestone. SVN head 20080324.
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 522931 ***