GNOME Bugzilla – Bug 354824
crash in Evolution: Just attempting to read ...
Last modified: 2013-09-13 12:25:43 UTC
What were you doing when the application crashed? Just attempting to read my email while evolution was scanning IMAP folders for new mail, a few minutes after startup. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 170307584 vsize: 0 resident: 170307584 share: 0 rss: 67104768 rss_rlim: 0 CPU usage: start_time: 1157651462 rtime: 0 utime: 3236 stime: 0 cutime:3054 cstime: 0 timeout: 182 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 -1232279888 (LWP 9549)] [New Thread -1318773856 (LWP 9777)] [New Thread -1310381152 (LWP 9776)] [New Thread -1277969504 (LWP 9751)] [New Thread -1287345248 (LWP 9687)] [New Thread -1268921440 (LWP 9685)] [New Thread -1260528736 (LWP 9683)] [New Thread -1252136032 (LWP 9682)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 71823
Thread 1 (Thread -1232279888 (LWP 9549))
strange trace matches Bug 215344 which is ancient...
etable bug.
*** Bug 357369 has been marked as a duplicate of this bug. ***
Bug 357369 is the same reporter, perfectly matching stacktrace. However, the description is interesting: > I believe I was just switching windows using compiz, because I wasn't > directly interacting with evo itself. Possible cause?
*** Bug 357639 has been marked as a duplicate of this bug. ***
*** Bug 358765 has been marked as a duplicate of this bug. ***
*** Bug 359401 has been marked as a duplicate of this bug. ***
*** Bug 359907 has been marked as a duplicate of this bug. ***
we're getting more and more duplicates of this one here, targetting to 2.8.1.
I haven't yet seen it with 2.8.1 (just got it a day or two from Edgy)...
*** Bug 362594 has been marked as a duplicate of this bug. ***
Note: Bug 363839 possibly is another duplicate. However, there's one notable difference in the stacktrace, namely a NULL filename argument in the gal_view_load() call in bug 363839.
*** Bug 375394 has been marked as a duplicate of this bug. ***
*** Bug 378547 has been marked as a duplicate of this bug. ***
Ubuntu bug about that: https://launchpad.net/distros/ubuntu/+source/evolution/+bug/73478
*** Bug 377989 has been marked as a duplicate of this bug. ***
*** Bug 386084 has been marked as a duplicate of this bug. ***
*** Bug 413132 has been marked as a duplicate of this bug. ***
*** Bug 420225 has been marked as a duplicate of this bug. ***
*** Bug 424105 has been marked as a duplicate of this bug. ***
*** Bug 424404 has been marked as a duplicate of this bug. ***
*** Bug 363600 has been marked as a duplicate of this bug. ***
*** Bug 363839 has been marked as a duplicate of this bug. ***
*** Bug 433621 has been marked as a duplicate of this bug. ***
I'd say this one has missed it's target milestone by quite a bit. Is it fixed? Can we close it if so? If not, perhaps a new target milestone? Does somebody not actually do any of this bookkeeping when a release is made? When a milestone is reached, somebody should look for all of the said milestone targets that did not make it and re-target them. The only thing left on a milestone at a release should be closed items. Anyway...
> I'd say this one has missed it's target milestone by quite a bit. Is it fixed? > Can we close it if so? If not, perhaps a new target milestone? if it was fixed, it would be closed. ;-) imo, evolution does not use the milestone settings anymore.
No new duplicats for nearly 18 months. Closing as OBSOLETE.