GNOME Bugzilla – Bug 360261
crash in Evolution: enlarged a picture (JPG)...
Last modified: 2006-10-07 21:56:38 UTC
What were you doing when the application crashed? enlarged a picture (JPG) that was attached to the mail. After i pressed the button with the thumbnail and right arrow on, evolution crashed. That behaviour is reproducable, whenever i try this, evolution crash. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 179560448 vsize: 0 resident: 179560448 share: 0 rss: 45240320 rss_rlim: 0 CPU usage: start_time: 1160165340 rtime: 0 utime: 2054 stime: 0 cutime:1894 cstime: 0 timeout: 160 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 -1232882000 (LWP 8869)] [New Thread -1353213024 (LWP 8889)] [New Thread -1312654432 (LWP 8888)] [New Thread -1278592096 (LWP 8885)] [New Thread -1304261728 (LWP 8879)] [New Thread -1295856736 (LWP 8878)] [New Thread -1287054432 (LWP 8877)] [New Thread -1270162528 (LWP 8874)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 74979
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.
used package evolution-dbg, hope it helps. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 179343360 vsize: 0 resident: 179343360 share: 0 rss: 45510656 rss_rlim: 0 CPU usage: start_time: 1160215922 rtime: 0 utime: 1853 stime: 0 cutime:1677 cstime: 0 timeout: 176 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 -1232582992 (LWP 22144)] [New Thread -1335903328 (LWP 22203)] [New Thread -1354769504 (LWP 22202)] [New Thread -1346376800 (LWP 22201)] [New Thread -1337984096 (LWP 22177)] [New Thread -1295582304 (LWP 22176)] [New Thread -1286726752 (LWP 22170)] [New Thread -1278334048 (LWP 22169)] [New Thread -1269867616 (LWP 22166)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 75052
Thread 1 (Thread -1232582992 (LWP 22144))
Yes, it helps. Thanks for the stacktrace and feedback, rean. :) 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 333864 ***