evolution crashed with signal 5 in camel_pop3_delete_old()

Bug #187759 reported by Niels Abspoel
8
Affects Status Importance Assigned to Milestone
Evolution
Expired
Critical
evolution (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

Just logged in gnome, start evolution, it showed gui, but only reading maps, and then crashed.

couldn't kill evolution process anymore, and restart showed evolution crashed, and can't repare or ignore,

so evolution won't start that session.

ProblemType: Crash
Architecture: amd64
Date: Thu Jan 31 18:33:52 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/evolution
NonfreeKernelModules: nvidia
Package: evolution 2.21.90-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: evolution --component=mail
ProcCwd: /home/aboe
ProcEnviron:
 LANGUAGE=nl_NL:nl
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: evolution
StacktraceTop:
 ?? () from /usr/lib/libcamel-provider-1.2.so.11
 camel_pop3_delete_old ()
 ?? ()
 camel_folder_sync ()
 ?? ()
Title: evolution crashed with signal 5 in camel_pop3_delete_old()
Uname: Linux desktop 2.6.24-5-generic #1 SMP Thu Jan 24 19:29:14 UTC 2008 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Niels Abspoel (aboe) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:get_message_info (folder=<value optimized out>, uid=<value optimized out>)
camel_pop3_delete_old (folder=0x965d10, days_to_delete=7, ex=0x0)
pop3_sync (folder=0x965d10, expunge=<value optimized out>, ex=0x0)
camel_folder_sync (folder=0x965d10, expunge=0, ex=0x0) at camel-folder.c:276
fetch_mail_exec (m=<value optimized out>) at mail-ops.c:342

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in evolution:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=513502

Changed in evolution:
assignee: nobody → desktop-bugs
status: New → Triaged
Revision history for this message
Niels Abspoel (aboe) wrote :

new update from evolution-webcal 2.13.90-0ubuntu1 fixed the problem.

I can now open evolution again, and work with it.

Changed in evolution:
status: Unknown → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

That's probably because now gnome-session isn't enabling the G_DEBUG=fatal-criticals variable, try running evolution as G_DEBUG=fatal_criticals and you should get the crash again, thanks.

Revision history for this message
Niels Abspoel (aboe) wrote :

Pedro you are right:
aboe@desktop:~$ G_DEBUG=fatal_criticals evolution
evolution-shell-Message: Killing old version of evolution-data-server...

camel-CRITICAL **: camel_object_is: assertion `o != NULL' failed
aborting...
Traceer/breekpunt-instructie (core dumped)

so the bug isn't fixed.

Revision history for this message
ebnf (eric-zeitler) wrote :

still happening in intrepid

evolution-2.23.4-0ubuntu1

Changed in evolution:
status: New → Incomplete
Changed in evolution:
status: Incomplete → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

could you try if that's still an issue in intrepid or jaunty?

Changed in evolution (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in evolution (Ubuntu):
status: Incomplete → Invalid
Changed in evolution:
importance: Unknown → Critical
status: Invalid → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.