evolution crashed with SIGSEGV in camel_object_trigger_event()

Bug #270186 reported by Sebastian Urban
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

Was closing Evolution. Happened after long wait.

ProblemType: Crash
Architecture: amd64
Disassembly: 0x19200000000:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/evolution
Package: evolution 2.23.91-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: evolution --component=mail
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? ()
 camel_object_trigger_event ()
 ?? ()
 camel_folder_sync ()
 ?? () from /usr/lib/libcamel-provider-1.2.so.13
Title: evolution crashed with SIGSEGV in camel_object_trigger_event()
Uname: Linux 2.6.27-3-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin mythtv netdev plugdev powerdev scanner tape vboxusers video

Revision history for this message
Sebastian Urban (surban) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
camel_object_trigger_event (vo=0x1e70c70, name=<value optimized out>, event_data=0x1fae920)
local_sync (folder=0x1e70c70, expunge=0, ex=<value optimized out>) at camel-local-folder.c:517
camel_folder_sync (folder=0x1e70c70, expunge=0, ex=0x45874f90) at camel-folder.c:325
store_sync (store=<value optimized out>, expunge=0, ex=0x2b53200) at camel-store.c:704

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

thanks for the report, is this still an issue with evolution 2.24.0 ?

Changed in evolution:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Sebastian Urban (surban) wrote :

I have not tested with 2.24.0, but it did not happen again with 2.22.3.1.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Yes it probably doens't happen with a previous version, could you test with 2.24.0 and report back? thanks for your help!.

Revision history for this message
Sebastian Urban (surban) wrote :

I was not able to reproduce this bug with 2.24.0.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

great, thanks for the feedback, marking this as fixed then, thanks again.

Changed in evolution:
status: Incomplete → Fix Released
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.