GNOME Bugzilla – Bug 360534
crash in Evolution: I get this crash everyti...
Last modified: 2006-10-09 17:34:18 UTC
What were you doing when the application crashed? I get this crash everytime I start the evolution mail component, thus it is at the moment unusuable for me. The mail account highlighted on the side pane at startup is connected to via secure IMAP. Maybe the crash is related to the account not yet being connected when evolution tries to display INBOX contents? Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 309690368 vsize: 309690368 resident: 32288768 share: 18833408 rss: 32288768 rss_rlim: -1 CPU usage: start_time: 1160269153 rtime: 159 utime: 142 stime: 17 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution-2.8' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47076352769312 (LWP 25992)] [New Thread 1149274448 (LWP 26017)] [New Thread 1140881744 (LWP 26016)] [New Thread 1132489040 (LWP 26015)] [New Thread 1124096336 (LWP 26011)] [New Thread 1115703632 (LWP 26010)] [New Thread 1107310928 (LWP 26009)] [New Thread 1098918224 (LWP 26007)] [New Thread 1090525520 (LWP 26006)] [New Thread 1082132816 (LWP 26005)] (no debugging symbols found) 0x00002ad0ccfcb5cf in waitpid () from /lib/libc.so.6
+ Trace 75163
Thread 4 (Thread 1132489040 (LWP 26015))
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Please install debugging packages for evolution, evolution-data-server and gtkhtml, plus debugging packages for some basic GNOME libs. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions
Ok, I installed debugging packages. Here is a new stack trace, hope it tells you more: Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 301985792 vsize: 301985792 resident: 33099776 share: 19247104 rss: 33099776 rss_rlim: -1 CPU usage: start_time: 1160301159 rtime: 154 utime: 141 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47918527110432 (LWP 7631)] [New Thread 1115703632 (LWP 7642)] [New Thread 1124096336 (LWP 7640)] [New Thread 1107310928 (LWP 7638)] [New Thread 1098918224 (LWP 7636)] [New Thread 1090525520 (LWP 7635)] [New Thread 1082132816 (LWP 7634)] 0x00002b94e27d55cf in waitpid () from /lib/libc.so.6
+ Trace 75196
Thread 1 (Thread 47918527110432 (LWP 7631))
Thanks for the feedback and the good stacktrace, ramon. :) 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 359520 ***