Evolution doesn't quit properly

Bug #27396 reported by Stéphane Marguet
8
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

When quitting (or closing) evolution, most of the time it's still there in
system monitor.
And then, when I try to quit Ubuntu, it doesn't work.

Breezy 2.6.12-10-686
Evolution 2.4.1-0ubuntu7

Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report. The next time you notice it still running could you
follow the steps 3-6 from https://wiki.ubuntu.com/DebuggingProgramCrash and post
the output here? Instead of gdb evolution you will have to run gdb -p `pidof
evolution`?

Revision history for this message
Stéphane Marguet (stemp) wrote :

Created an attachment (id=5534)
gdb evolution crash

Here is the exit using gdb evolution (I can see evolution on the system-monitor
--> evolution stopped)

Revision history for this message
Stéphane Marguet (stemp) wrote :

Created an attachment (id=5535)
Complete list

here is the list from the beginning

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

The gdb logs have no backtrace. If you still have some evolution process running
could you attach them (using "gdb -p PID" where PID is the PID of the processus,
you can get it with the ID column of gnome-system-monitor (not configured by
default) or with ps/top)?

Revision history for this message
Daniel Holbach (dholbach) wrote :

In addition to what Sébastien said, which architecture are you on?

Revision history for this message
Stéphane Marguet (stemp) wrote :

Kernel 2.6.12-10-686

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

could you reply to comment #4?

Revision history for this message
Stéphane Marguet (stemp) wrote :

I can't :( using with gdb, evolution crash sometimes (mainly when trying to save
attachements) but nearly never crash when quitting.
But when using evolution without gdb, I still have the bug. And I don't know
what to do.

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

Maybe the crash is less frequent. If you get a backtrace please copy it to the
bug. Or maybe try again with bug-buddy it'll have a better one

Revision history for this message
Stéphane Marguet (stemp) wrote :

(In reply to comment #9)
> Maybe the crash is less frequent. If you get a backtrace please copy it to the
> bug. Or maybe try again with bug-buddy it'll have a better one

I will copy a backtrace as soon as possible.

Thanks for your help

Revision history for this message
Daniel Holbach (dholbach) wrote :

This might be bug 38455.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Your bug lacks information we would need to investigate further. We
are now going to close the bug - please reopen if you have more
information at hand.

Changed in evolution:
assignee: seb128 → desktop-bugs
status: Needs Info → Rejected
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.