GNOME Bugzilla – Bug 623544
crash in Evolution: I was switching from the...
Last modified: 2010-07-05 01:49:51 UTC
Version: 3.0.x What were you doing when the application crashed? I was switching from the main window, where a mail were just rendered, and a compose window. Perhaps the crash was due the rendering of the message, which just apparently ended some millisecond before. Distribution: Gentoo Base System release 2.0.1 Gnome Release: 2.30.2 2010-06-23 (Gentoo) BugBuddy Version: 2.30.0 System: Linux 2.6.31-sabayon #1 SMP Sat May 1 18:55:35 UTC 2010 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10707000 Selinux: No Accessibility: Enabled GTK+ Theme: Inverted Icon Theme: gnome GTK+ Modules: canberra-gtk-module, gnomebreakpad, gail:atk-bridge Memory status: size: 1151381504 vsize: 1151381504 resident: 450138112 share: 34480128 rss: 450138112 rss_rlim: 18446744073709551615 CPU usage: start_time: 1278264779 rtime: 13277 utime: 12205 stime: 1072 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/local/bin/evolution' [?1034hTraceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2400.1-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace [Thread debugging using libthread_db enabled] [New Thread 0x7f6a9de8b910 (LWP 10465)] [New Thread 0x7f6aa57fa910 (LWP 7182)] [New Thread 0x7f6aa5ffb910 (LWP 7181)] [New Thread 0x7f6aa67fc910 (LWP 7180)] [New Thread 0x7f6aa6ffd910 (LWP 7179)] [New Thread 0x7f6aa77fe910 (LWP 7178)] [New Thread 0x7f6aa7fff910 (LWP 7177)] [New Thread 0x7f6aae792910 (LWP 7173)] [New Thread 0x7f6aaef93910 (LWP 7172)] [New Thread 0x7f6aaf9c0910 (LWP 7171)] [New Thread 0x7f6ab0669910 (LWP 7170)] 0x00007f6abb57d57d in waitpid () from //lib/libpthread.so.0
+ Trace 222693
Thread 1 (Thread 0x7f6ac9486780 (LWP 7159))
Inferior 1 [process 7159] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (5121 sec old) --------------------- (tracker-miner-fs:7019): Tracker-WARNING **: Could not add monitor for path:'/home/madbob/backup_vps_madserver/usr/src/kernels/2.6.18-53.1.13.el5-xen-i686/include/config/new' Adding INotify watch:: No space left on device (tracker-miner-fs:7019): Tracker-WARNING **: Could not add monitor for path:'/home/madbob/backup_vps_madserver/usr/src/kernels/2.6.18-53.1.13.el5-xen-i686/include/config/nfs' Adding INotify watch:: No space left on device (tracker-miner-fs:7019): Tracker-WARNING **: Could not add monitor for path:'/home/madbob/backup_vps_madserver/usr/src/kernels/2.6.18-53.1.13.el5-xen-i686/include/config/nfsd' Adding INotify watch:: No space left on device (tracker-miner-fs:7019): Tracker-WARNING **: Could not add monitor for path:'/home/madbob/backup_vps_madserver/usr/src/kernels/2.6.18-53.1.13.el5-xen-i686/include/config/nftl' Adding INotify watch:: No space left on device (tracker-miner-fs:7019): Tracker-WARNING **: Could not add monitor for path:'/home/madbob/backup_vps_madserver/usr/src/kernels/2.6.18-53.1.13.el5-xen-i686/include/config/nls' ...Too much output, ignoring rest... --------------------------------------------------
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 bug 330728 ***