GNOME Bugzilla – Bug 373327
crash in Evolution: When I browse into sever...
Last modified: 2006-11-14 15:57:41 UTC
What were you doing when the application crashed? When I browse into several pictures attached to an email, Evolution appears very unstable and close when manipulating these pictures (with the hide and display arrow). Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 219992064 vsize: 0 resident: 219992064 share: 0 rss: 35840000 rss_rlim: 0 CPU usage: start_time: 1163153034 rtime: 0 utime: 772 stime: 0 cutime:737 cstime: 0 timeout: 35 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 -1232755024 (LWP 7175)] [New Thread -1413682272 (LWP 7199)] [New Thread -1404871776 (LWP 7198)] [New Thread -1319302240 (LWP 7193)] [New Thread -1344619616 (LWP 7190)] [New Thread -1336226912 (LWP 7188)] [New Thread -1310504032 (LWP 7187)] [New Thread -1327707232 (LWP 7186)] [New Thread -1302111328 (LWP 7182)] [New Thread -1293718624 (LWP 7181)] [New Thread -1285325920 (LWP 7180)] [New Thread -1276933216 (LWP 7179)] [New Thread -1268413536 (LWP 7178)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 85005
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Could you please install some debugging packages [1] and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the "details", now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks! [1] 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
Thank you for your answer. I set up the debug packages, but I have not been able to reproduce the bug since I rebooted. Weired...
It happened again. Here is a more complete trace : Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 220246016 vsize: 0 resident: 220246016 share: 0 rss: 39092224 rss_rlim: 0 CPU usage: start_time: 1163449720 rtime: 0 utime: 502 stime: 0 cutime:471 cstime: 0 timeout: 31 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 -1233094992 (LWP 21024)] [New Thread -1313879136 (LWP 21048)] [New Thread -1339458656 (LWP 21042)] [New Thread -1347851360 (LWP 21037)] [New Thread -1331061856 (LWP 21034)] [New Thread -1322665056 (LWP 21033)] [New Thread -1305449568 (LWP 21031)] [New Thread -1297056864 (LWP 21030)] [New Thread -1288664160 (LWP 21029)] [New Thread -1280271456 (LWP 21028)] [New Thread -1271751776 (LWP 21027)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 86178
Thread 1 (Thread -1233094992 (LWP 21024))
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. Pleas ask your vendor (Ubuntu) for updates, as this issue has been already fixed in the code base. *** This bug has been marked as a duplicate of 333864 ***