evolution crashed with SIGSEGV in g_object_unref()

Bug #358593 reported by Tiefflieger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Incomplete
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

Prior to this, I started evolution from a console. I deleted some files in junk folder, then evolution crashed, the first attachment is copy & paste of console output.

After that, I started evolution from console again and deleted mails in junk folder, then it crashed again, this time apport showed up.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/evolution
NonfreeKernelModules: nvidia
Package: evolution 2.26.0-0ubuntu3
ProcCmdline: evolution
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.UTF-8
Signal: 11
SourcePackage: evolution
StacktraceTop:
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgnomeui-2.so.0
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
Title: evolution crashed with SIGSEGV in g_object_unref()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Tiefflieger (tiefflieger) wrote :
Revision history for this message
Tiefflieger (tiefflieger) wrote :

This is the console output of the second crash

Revision history for this message
Tiefflieger (tiefflieger) wrote :

After this, Bug #358734 appeared

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in evolution (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

those recent crashers could be the same cause, there is http://bugzilla.gnome.org/show_bug.cgi?id=578685 open already about a crash

Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue is probably bug #358223, closing as duplicate, you can reopen if you still get the issue once the other bug is closed

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.