GNOME Bugzilla – Bug 356582
crash in Evolution: crashed when closing evo...
Last modified: 2006-09-19 20:23:52 UTC
What were you doing when the application crashed? crashed when closing evolution. happens everytime i'm closing it :/ Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 155111424 vsize: 0 resident: 155111424 share: 0 rss: 31023104 rss_rlim: 0 CPU usage: start_time: 1158598749 rtime: 0 utime: 2170 stime: 0 cutime:2039 cstime: 0 timeout: 131 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution-2.8' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1232939344 (LWP 4881)] [New Thread -1347445856 (LWP 4918)] [New Thread -1276740704 (LWP 4899)] [New Thread -1285133408 (LWP 4898)] [New Thread -1293526112 (LWP 4892)] [New Thread -1268348000 (LWP 4887)] [New Thread -1259955296 (LWP 4886)] [New Thread -1251562592 (LWP 4885)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 72668
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.
(In reply to comment #1) > 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. Hello! First - excuse me if i do something wrong. First time submitting bug here... OK, installed dbg package and here is what bugbuddy has to say now. If I can be helpfull in any other way - please tell me. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 124542976 vsize: 0 resident: 124542976 share: 0 rss: 27426816 rss_rlim: 0 CPU usage: start_time: 1158642179 rtime: 0 utime: 295 stime: 0 cutime:279 cstime: 0 timeout: 16 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1232591184 (LWP 6009)] [New Thread -1301607520 (LWP 6023)] [New Thread -1293214816 (LWP 6020)] [New Thread -1276429408 (LWP 6019)] [New Thread -1284822112 (LWP 6018)] [New Thread -1267999840 (LWP 6013)] [New Thread -1259607136 (LWP 6012)] [New Thread -1251214432 (LWP 6011)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 72714
Thread 1 (Thread -1232591184 (LWP 6009))
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 349521 ***
Thanks for the fast response and the good stacktrace, Costa. :) (In reply to comment #2) > First - excuse me if i do something wrong. First time submitting bug here... > OK, installed dbg package and here is what bugbuddy has to say now. If I can > be helpfull in any other way - please tell me. Costa, you're not doing anything wrong. Actually, you're quite fast, responsive and accurate. :) The initial report just happened to have a stacktrace, that doesn't show the real cause of the crash -- which definitely is not your fault. You reported the crash, and we do appreciate that. Since you asked if you still can provide even more help -- actually, yes. It would be great, if you can install the debug package for evolution-data-server as well. Then reproduce the crash again, gather the stacktrace with bug-buddy and paste it here. You can see the difference yourself: Just have a look at the stacktrace, right below the top-most "<signal handler called>" (highlighted green in your last stacktrace). The function calls right below will have more verbose information added, which will help us track down and fix this issue. Thanks again for your help!
Hello Karsten! I'm glad I can help in any way. Evolution is my favourite mail software and I want it to work just like it should work :). So if I can provide You with any more info, please keep telling me what I have to do. Maybe it will be of use. Ok, I installed the package You mentioned and below goes everything BugBuddy has to say now. I don't really know how You guys understand any of this :). Respect and keep the good work! Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 148697088 vsize: 0 resident: 148697088 share: 0 rss: 27586560 rss_rlim: 0 CPU usage: start_time: 1158694586 rtime: 0 utime: 436 stime: 0 cutime:411 cstime: 0 timeout: 25 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1232521552 (LWP 10549)] [New Thread -1276372064 (LWP 10566)] [New Thread -1293157472 (LWP 10563)] [New Thread -1284764768 (LWP 10561)] [New Thread -1301550176 (LWP 10560)] [New Thread -1267942496 (LWP 10555)] [New Thread -1259549792 (LWP 10554)] [New Thread -1251157088 (LWP 10553)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 72767
Thread 1 (Thread -1232521552 (LWP 10549))
(In reply to comment #5) > I'm glad I can help in any way. Evolution is my favourite mail software and I > want it to work just like it should work :). So if I can provide You with any > more info, please keep telling me what I have to do. Maybe it will be of use. > > Ok, I installed the package You mentioned and below goes everything BugBuddy > has to say now. I don't really know how You guys understand any of this :). > Respect and keep the good work! Great, thanks a lot, Costa! With that last stacktrace, now it turns out that bug 349521 and all its duplicates (including this one) actually is the very same issue as bug 330157. This really did help in tracking down these bugs. Thanks for your efforts.