Crash Evolution

Bug #578864 reported by Tizianub
90
This bug affects 19 people
Affects Status Importance Assigned to Milestone
evolution-data-server (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: evolution

With Lucid Evolution crash but I don't understand because, the error in the teminal is:

***MEMORY-ERROR***: evolution[3570]: GSlice: assertion failed: sinfo->n_allocated > 0

or

***MEMORY-ERROR***: evolution[2367]: GSlice: assertion failed: sinfo->n_allocated > 0
Aborted

or

ERROR:gkr-operation.c:392:gkr_operation_block: code should not be reached
Aborted

or other.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: evolution 2.28.3-0ubuntu9
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Tue May 11 17:49:23 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
 PATH=(custom, user)
 LANG=it_IT.utf8
 SHELL=/bin/bash
SourcePackage: evolution

Revision history for this message
Tizianub (tizianub) wrote :
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 backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

affects: evolution (Ubuntu) → gnome-keyring (Ubuntu)
Changed in gnome-keyring (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Frédéric CORNU (fcornu) wrote :

Same issue here on a freshly upgraded system, from Karmic to Lucid.

I'm attaching a backtrace generated with gdb as suggested.

Evolution crashes even without any specific action from me, except scheduled account checks (5 POP & 2 IMAP)

Revision history for this message
happyisland (david-meteoric) wrote :

I have the same setup and symptoms as Frederic CORNU above. Backtrace attached.

Revision history for this message
Jesse Raleigh (j-jraleigh) wrote :

I have been having the same exact problem, I noticed that evolution was just dying in the background, so I ran it from a console for a while until it crashed again.

As soon as it tried to fetch mail, it died. Upon re-starting evolution, it was able to fetch the message fine. I've noticed it dying with a manual "send and receive" as well as with the scheduled mail check.

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

After upgrade to Ubuntu 10.04 LTS Lucid from Ubuntu Karmic I noticed that Evolution died silently for several times. Starting it from console gives following error message (it works but then its suddenly gone):

ERROR:gkr-operation.c:392:gkr_operation_block: code should not be reached
Aborted

Revision history for this message
Michele (mikelito) wrote :

Why is this still marked as invalid? aren't the two backtraces attached sufficient?

Revision history for this message
Jesse Raleigh (j-jraleigh) wrote :

Does this need to be reported against the Gnome Key Ring to get traction on this bug? I would think that a bug that kills the Gnome flagship productivity app would be rather high priority. Evolution has been dying on me a dozen times a day at least.

this is pretty annoying for me, as I've been using evolution since it's pre 1.0 days, and it's always been very stable.

Revision history for this message
happyisland (david-meteoric) wrote :

Unfortunately, according to at least one commenter on ubuntuforums, the bug is also present in evolution 2.30, which means there's no quick fix way out of this one.

I second what Jesse Raleigh says above. Evolution (Ubuntu's centerpiece productivity app) crashes at least a dozen times a day on my work computer. Very poor.

Revision history for this message
Jesse Raleigh (j-jraleigh) wrote :

happyisland, I suspect that this bug is not in evolution, but in the gnome keyring manager itself.

I've noticed a few apps crashing randomly, but haven't yet managed to catch get one to crash in a way I can duplicate and isolate.

Revision history for this message
Christoffer Kjølbæk (ostehamster) wrote :

Got this error too, but Apport did not catch it.

Revision history for this message
Jesse Raleigh (j-jraleigh) wrote :

What is needed to take this bug report from incomplete to something that can be acted upon?

Revision history for this message
Nick Marks (nickmarks) wrote :

Here's my terminal output to throw into the mix, hope its of some use. FYI, Apport didn't show anything.

Ubuntu Lucid Lynx (upgrade)
Evolution 2.28.3

Evolution ran for about 25 mins before crashing,

nickm@nickm-laptop:~$ evolution &
[1] 3651
nickm@nickm-laptop:~$ ** (evolution:3651): DEBUG: mailto URL command: evolution %s
** (evolution:3651): DEBUG: mailto URL program: evolution
Created new window in existing browser session.

[1]+ Segmentation fault evolution

Revision history for this message
Bill Phillips (phillipswilliama) wrote : Re: [Bug 578864] Re: Crash Evolution

Thank you Nick - Hopefully they can resolve this...It's very
frustrating...I don't know enough about Linux to make changes.
Bill Phillips

On Fri, 2010-06-11 at 09:17 +0000, Nick Marks wrote:

> Here's my terminal output to throw into the mix, hope its of some use.
> FYI, Apport didn't show anything.
>
> Ubuntu Lucid Lynx (upgrade)
> Evolution 2.28.3
>
>
> Evolution ran for about 25 mins before crashing,
>
>
> nickm@nickm-laptop:~$ evolution &
> [1] 3651
> nickm@nickm-laptop:~$ ** (evolution:3651): DEBUG: mailto URL command: evolution %s
> ** (evolution:3651): DEBUG: mailto URL program: evolution
> Created new window in existing browser session.
>
> [1]+ Segmentation fault evolution
>

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

@maintainer: Why is it still marked as 'Incomplete'? Please give us a hint what information is requiered to work on this issue.

This is a major and critical bug (especially in a LTS version).

Revision history for this message
happyisland (david-meteoric) wrote :

"This is a major and critical bug (especially in a LTS version)."

True words. I've been using Ubuntu since 6.06, and this is the most show-stopping bug I've run up against. Maybe I've been lucky, but this really seems like an embarrassing bug for a LTS release in 2010.
[/rant]

I, too, would be interested in knowing how I could help get work on this bug started.

Revision history for this message
Bill Phillips (phillipswilliama) wrote :

I appreciate you all working on this...I brag about how stable Ubuntu is all the time and it is annoying and time consuming to have this Evolution bug continually rear it's head by either erasing a message I am in the process of working on or nearly eliminating the message by coming up with a "Restore" or "Discard" option. I now continually copy my work. Thank you for taking this so seriously. I wish I could be of more help.

 Sincerely Yours,
Bill Phillips

Cedar Key Transit,LLC
www.cedarkeytransit.com
Office: 352-376-0690
cell: 352-949-1380

________________________________
From: happyisland <email address hidden>
To: <email address hidden>
Sent: Tue, June 15, 2010 11:14:46 AM
Subject: [Bug 578864] Re: Crash Evolution

"This is a major and critical bug (especially in a LTS version)."

True words. I've been using Ubuntu since 6.06, and this is the most show-stopping bug I've run up against. Maybe I've been lucky, but this really seems like an embarrassing bug for a LTS release in 2010.
[/rant]

I, too, would be interested in knowing how I could help get work on this
bug started.

--
Crash Evolution
https://bugs.launchpad.net/bugs/578864
You received this bug notification because you are a direct subscriber
of the bug.

Status in “gnome-keyring” package in Ubuntu: Incomplete

Bug description:
Binary package hint: evolution

With Lucid Evolution crash but I don't understand because, the error in the teminal is:

***MEMORY-ERROR***: evolution[3570]: GSlice: assertion failed: sinfo->n_allocated > 0

or

***MEMORY-ERROR***: evolution[2367]: GSlice: assertion failed: sinfo->n_allocated > 0
Aborted

or

ERROR:gkr-operation.c:392:gkr_operation_block: code should not be reached
Aborted

or other.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: evolution 2.28.3-0ubuntu9
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Tue May 11 17:49:23 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
PATH=(custom, user)
LANG=it_IT.utf8
SHELL=/bin/bash
SourcePackage: evolution

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/578864/+subscribe

Revision history for this message
Jesse Raleigh (j-jraleigh) wrote :

This is getting to be pretty tiresome. None of us can help in any way without some FEEDBACK.

What do you folks need to move this from incomplete to something that can be acted upon?

Revision history for this message
Pedro Villavicencio (pedro) 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.

Revision history for this message
Christoffer Kjølbæk (ostehamster) wrote :

Pedro > Valgrind is memory error debugger, does that mean that the log files can/will contain private information? (username, password etc.)

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

ostehamster, no is not going to show that info there.

Revision history for this message
Frédéric CORNU (fcornu) wrote :

HI,

I generated a valgrind log as asked.
It's a 30MB file.

Any hint of what I could filter out of it ?
Or do you guys still want such a big file ?

--
Fred

Revision history for this message
Jesse Raleigh (j-jraleigh) wrote :

I've been running evolution in valgrind for several hours now and it's yet to crash, but is very very slow during the debug run.

Revision history for this message
Tizianub (tizianub) wrote :

Even I used valgrid for some time and evolution is very slow, the log file is 342 MB, what should I do?

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

If you manage to reproduce the crash with valgrind please compress it and attach the log to the report, thanks folks!.

Revision history for this message
Frédéric CORNU (fcornu) wrote :

Hi,

Here is my Valgrind log. Evolution ran for 3+ hours before same usual crash.

Hope it can help solve the issue

Revision history for this message
Tizianub (tizianub) wrote :

My valgrid log

Revision history for this message
happyisland (david-meteoric) wrote :

Attached is my valgrind log. Hope it helps - this bug makes working with evolution impossible.

Revision history for this message
Michele (mikelito) wrote :

I am experiencing the same problem, and I am pretty sure that
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/584183
is just the same bug as this one. It would be helpful to the devs to mark
one as a duplicate of the other, so that efforts can be joined.
Before doing so, I'd like to hear if any of you feels that this is a wrong decision
and someone has clues that the two bugs are not related.

Cheers

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

could you install libgnome-keyring0-dbgsym libdbus-1-3-dbgsym libedataserverui1.2-8-dbgsym and get a new stacktrace?

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

seems the log on comment #26 has quite some detailed stacktrace, is the issue specific to evolution? do you use some sort of special setting for login or normal password login?

Revision history for this message
Frédéric CORNU (fcornu) wrote :

@Sebastien Bacher

Hi Sebastien,

1) I don't experience similar issue with any other package/program at the moment, so I qould guess this is an evolution specific issue.
2) I'm logging into Gnome as I always did, that is the regular (password) way.

Let me know if I can be of any help, as I'd really lova to see my evolution behave nicely again.

Thanx

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

According to this screenshot - It looks like version 2.30 resolves this
issue...Is that true? I am currently running ver 2.28.

I am not an Ubuntu authority or any thing close...But I love the speed
of Ubuntu over windows and want to again convert disappointed and upset
Windows users to try Ubuntu. Evolution is a big part of my Ubuntu
experience, because it had done such a great job of duplicating
"Outlook". It is very important that we get Evolution working reliably.

See Screenshot below

Bill Phillips

On Mon, 2010-06-21 at 12:21 +0000, Sebastien Bacher wrote:

> the issue seems similar to
> https://bugzilla.gnome.org/show_bug.cgi?id=612596
>
> ** Bug watch added: GNOME Bug Tracker #612596
> https://bugzilla.gnome.org/show_bug.cgi?id=612596
>

affects: gnome-keyring (Ubuntu) → evolution-data-server (Ubuntu)
Changed in evolution-data-server (Ubuntu):
status: Incomplete → Fix Committed
affects: evolution-data-server (Ubuntu) → evolution (Ubuntu)
affects: evolution (Ubuntu) → evolution-data-server (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (4.3 KiB)

This bug was fixed in the package evolution-data-server - 2.32.0-0ubuntu1

---------------
evolution-data-server (2.32.0-0ubuntu1) natty; urgency=low

  [ Mathieu Trudel-Lapierre ]
  * Upstream release 2.32.0
    - [groupwise] EDS crashed when checking contacts (LP: #623794)
    - Do not expose off_t in public API, use goffset instead (LP: #584536)
    - Allow normal, non-vFolder, Trash and Junk folder (LP: #13983, #64762)
      (LP: #135485, #280325, #365270)
    - Corruption of mailbox and can't expunge trash (LP: #281093, #287811)
      (LP: #360667, #410723, #483058)
    - Allow change of signature hash algorithm (LP: #381290, #381295, #635937)
    - Evolution forgets password on any error (LP: #245589, #272414)
    - EContact/EVCard can re-order phone and email attributes (LP: #460255)
    - Crash in gnome_keyring_item_info_free from e-passwords.c (LP: #530760)
      (LP: #578864)
    - Properly free unused message infos periodically (LP: #507972)
    - Crash in imap_body_decode at camel-imap-utils.c:979 (LP: #554367)
    - Be able to disallow selection of a certain ESource (LP: #198392)
    - assertion failed: (reply == msg) in cs_waitinfo() (LP: #455020, #475147)
    - Use thread safe G_DEFINE_TYPE/G_DEFINE_TYPE_EXTENDED (LP: #477186)
    - Always ref returned info from message_info_from_uid (LP: #341909)
  * debian/patches/01_build_with_deprecated_symbols.patch: dropped,
    applied upstream.
  * debian/patches/01_imapx_lockup.patch: dropped, applied upstream.
  * debian/patches/60_google_backend_lookup.patch: dropped, applied upstream.
  * debian/patches/65_evolution-color.patch: seems it's no longer needed;
    color setting has been overhauled upstream and this patch won't apply
    anymore anyway.
  * debian/patches/108-git-fix-eproxy-and-https.patch: dropped, applied upstream
  * debian/patches/107-git-consider-local-inbox-as-inbox.patch: refreshed.
  * Additional dropped cherry-picked patches (now in source):
    - 102-Bug-630135-No-UI-feedback-when-imapx-connection-fail.patch
    - 103-Bug-630150-imapx-attempts-to-connect-to-server-when-.patch
    - 104-Bug-630152-imapx_parser_thread-registers-wrong-opera.patch
    - 105-Bug-629916-imapx-fails-to-handle-errors-in-imapx_com.patch
    - 106-Bug-630149-imapx_sync-never-returns-error.patch
  * update to correctly install to evolution-data-server-2.32 instead of 2.30
    in various paths:
    - debian/evolution-data-server-common.install
    - debian/libcamel1.2-dev.install
    - debian/libebackend1.2-dev.install
    - debian/libebook1.2-dev.install
    - debian/libecal1.2-dev.install
    - debian/libedata-book1.2-dev.install
    - debian/libedata-cal1.2-dev.install
    - debian/libedataserver1.2-dev.install
    - debian/libedataserverui1.2-dev.install
    - debian/libegroupwise1.2-dev.install
    - debian/libgdata1.2-dev.install
    - debian/libgdata-google1.2-dev.install
  * debian/control: the gdata stuff was moved to an external library, so
    dropping the creation of the libgdata* packages and adding Build-Depends
    and Depends for libgdata7/libgdata-dev >= 0.6.3.
  * removed debian/libgdata*.install: since it's not being built in e-d-s
    anymore, dropping these unnecessar...

Read more...

Changed in evolution-data-server (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Bill Phillips (phillipswilliama) wrote : Hi
Revision history for this message
Bill Phillips (phillipswilliama) wrote :

Smoking kills your beauty.. http://arcaade.fr/page.php?goSID=18a6

Revision history for this message
Bill Phillips (phillipswilliama) wrote : Re:7

Baby! This wonderful site which can really change you life!. http://www.colegiomigueldecervantes.cl/page.php?qGIS=11oc6

Revision history for this message
Bill Phillips (phillipswilliama) wrote :
Revision history for this message
Bill Phillips (phillipswilliama) wrote : Fw:
Revision history for this message
Bill Phillips (phillipswilliama) wrote :
Revision history for this message
Bill Phillips (phillipswilliama) wrote :
Revision history for this message
Bill Phillips (phillipswilliama) wrote :
Revision history for this message
Bill Phillips (phillipswilliama) wrote :
Revision history for this message
Bill Phillips (phillipswilliama) wrote : Fwd:
Revision history for this message
Bill Phillips (phillipswilliama) wrote :
Revision history for this message
Bill Phillips (phillipswilliama) wrote :
Revision history for this message
Bill Phillips (phillipswilliama) wrote :
Revision history for this message
Bill Phillips (phillipswilliama) wrote : Fwd:
Revision history for this message
Bill Phillips (phillipswilliama) wrote :
Revision history for this message
Bill Phillips (phillipswilliama) wrote :
Revision history for this message
Bill Phillips (phillipswilliama) wrote : Fw:
Revision history for this message
Bill Phillips (phillipswilliama) wrote :
Revision history for this message
Bill Phillips (phillipswilliama) wrote : Fw:
Revision history for this message
Bill Phillips (phillipswilliama) wrote : Fwd:
Revision history for this message
Bill Phillips (phillipswilliama) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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