GNOME Bugzilla – Bug 329263
Critical warning crash after expunging emails (camel_object_is at camel-object.c:1034)
Last modified: 2013-09-10 14:04:44 UTC
Distribution: Red Hat Enterprise Linux AS release 4 (Nahant Update 2) Package: Evolution Severity: critical Version: GNOME2.13.90 2.5.x Gnome-Distributor: JHBuild Synopsis: Critical warning crash after expunging some emails from my INBOX Bugzilla-Product: Evolution Bugzilla-Component: Shell Bugzilla-Version: 2.5.x BugBuddy-GnomeVersion: 2.0 (2.13.90) Description: Description of the crash: I had just expunged a couple emails from my inbox when I got this crash. I've expunged emails lots of times without problems and have no idea what might have been different this time from all the others. Hopefully the stack trace helps; I'm running CVS HEAD if the version matters. Debugging Information: Backtrace was generated from '/opt/gnome2/bin/evolution-2.6' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208142144 (LWP 10115)] [New Thread 18111408 (LWP 10124)] [New Thread -1212154960 (LWP 10122)] [New Thread 77884336 (LWP 10121)] [New Thread 120204208 (LWP 10120)] [New Thread 45657008 (LWP 10118)] [New Thread 32807856 (LWP 10116)] 0x006c37a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 65760
Thread 1 (Thread -1208142144 (LWP 10115))
2688187, 0, 3220178624, 3220178416, 2688092, 3220178288, 19406804, 19350852, 3067336, 145892448, 19406804}}, sa_flags = 19350852, sa_restorer = 0x9} pid = ------- Bug created by bug-buddy at 2006-01-30 21:03 -------
Just got this again, this time with evolution-2.5.90 (actual tarball, not CVS).
*** Bug 331725 has been marked as a duplicate of this bug. ***
Can confirm on Evolution 2.5.91. See bug 331725 for some details. Just happened 3 out of 2 times with the given scenario. Last marked-for-deletion mail selected when Expunging. Elijah, could this be the difference that triggered this for you, too?
Adjusting summary. Not related to the mail folder.
Camel. Component Mailer, not Shell. :)
Good news everyone! Not related to having the last mail in the folder selected, when expunging. Neither related to expunging the last mail in the folder. Looks like this is reproducible for me. At least with this particular mail folder. Didn't see it yet with other folders...
OK, just tried twice using Empty Trash while displaying a different folder. No crash so far. The mails in that particluar folder are being deleted just fine. HTH, and I am not confusing you guys...
Just triggered this very same crash by expunging some mails that happen to be at the top of the list. Raising Priority.
can someone get me steps to reproduce (and a mbox to reproduce with?)
seems i can confirm this on evolution 2.6.1 when expunging trash on exit (not sure if you guys call this a confirm). details: Distribution: Ubuntu 6.06 (dapper) Package: Evolution Severity: major Version: GNOME2.14.1 2.6.x Gnome-Distributor: Ubuntu Bugzilla-Product: Evolution Bugzilla-Version: 2.6.x Description of the crash: with evolution set to expunge trash on exit and one or more items in trashbox, program crashes on exit. no noticeable corruption after restart. Steps to reproduce the crash: 1. set 'empty trash folders on exit" 2. delete one or more e-mail(s) 3. exit program Expected Results: dialog box appears saying something like "evolution 2.6 has crashed unexpectedly" How often does this happen? about 2 in every 3 times Debugging Information: Backtrace was generated from '/usr/bin/evolution-2.6' Using host libthread_db library "/lib/libthread_db.so.1". [..] [Thread debugging using libthread_db enabled] [New Thread 46912630333024 (LWP 10849)] [New Thread 1115969888 (LWP 10915)] [New Thread 1107577184 (LWP 10860)] [New Thread 1107310944 (LWP 10859)] [New Thread 1090525536 (LWP 10858)] [New Thread 1098918240 (LWP 10856)] [New Thread 1082132832 (LWP 10853)] [..] 0x00002aaaaef490fa in waitpid () from /lib/libc.so.6
+ Trace 69128
removing old target milestone.
*** Bug 373441 has been marked as a duplicate of this bug. ***
*** Bug 374921 has been marked as a duplicate of this bug. ***
*** Bug 412565 has been marked as a duplicate of this bug. ***
*** Bug 412582 has been marked as a duplicate of this bug. ***
Is this still an issue?
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME 2.22.3.1, thanks.