evolution hangs when opening multiple notes

Bug #425621 reported by quantenemitter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evolution
Won't Fix
Medium
evolution (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

Evolution hangs when trying to open multiple notes.

Steps to reproduce:
1. start evolution
2. go to "notes" (or whatever that is: I have "Notizen")
3. Ensure you have at least two notes inside.
4. Open the first note via double-click
5. close it again
6. try to open the second note: Evolution stops responding

Perhaps I should mention: The notes got into evolution vial gpilot synchronization with my palm os. But when adding a new note from evolution, the same problem occurs.

Using ubuntu karmic
evolution 2.27.91-0ubuntu1
gnome-pilot 2.0.17-0ubuntu2
gnome-pilot-conduits 2.0.15-1.2

apport doesn't report no crash.
I don't know how to use gdb. When starting "gdb evolution" (and then "run"), I get these messages after opening and closing the first note:

===
[New Thread 0xb36f8b70 (LWP 10824)]

(evolution:10798): GLib-GObject-WARNING **: cannot register existing type `CompEditor'

(evolution:10798): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

(evolution:10798): calendar-gui-CRITICAL **: e_comp_editor_registry_add: assertion `IS_COMP_EDITOR (editor)' failed
[Thread 0xb36f8b70 (LWP 10824) exited]
===

And those while trying to open the second note:
===
[Thread 0xb36f8b70 (LWP 10824) exited]
[New Thread 0xb36f8b70 (LWP 10826)]
[Thread 0xb36f8b70 (LWP 10826) exited]
[Thread 0xb4769b70 (LWP 10819) exited]
[Thread 0xb4fabb70 (LWP 10810) exited]
[Thread 0xb5bfdb70 (LWP 10809) exited]
[Thread 0xb63feb70 (LWP 10808) exited]
[Thread 0xb755cb70 (LWP 10806) exited]
[Thread 0xb7d5db70 (LWP 10805) exited]
[Thread 0xb4f6ab70 (LWP 10817) exited]

Program terminated with signal SIGKILL, Killed.
The program no longer exists.
(gdb) bt
No stack.
===

As you can see, I had to terminate evolution after the second attempt. Gnome grayed it out and informed me evolution was not responding any more.

I'd love to add any useful information if you request it.

ProblemType: Bug
Architecture: i386
Date: Mon Sep 7 12:19:52 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/evolution
Package: evolution 2.27.91-0ubuntu1
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
SourcePackage: evolution
Uname: Linux 2.6.31-9-generic i686

Related branches

Revision history for this message
quantenemitter (quantenemitter) wrote :
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. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in evolution (Ubuntu):
status: New → Invalid
Revision history for this message
quantenemitter (quantenemitter) wrote :

Thank you for your quick response. I need to clarify:

= apport doesn't report nothing relevant, but it _is_ activated. =
= Evolution does not crash, it hangs up. =

I'd really love to give you the valuable information given by apport, but when evolution hangs up, it is grayed out (not responding) and even after leaving the gray program alone for an hour or so, no corresponding crash report can be found in /var/crash (There already were some inside. To ensure it's the right one, I deleted the one having "evolution" in it, rebooted and reproduced the hangup - with no result). I don't know when a .crash file will be created, but this bug does not seem to trigger apport.

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

Confirmed using the steps described, that's not a crash though the title is confusing. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

Changed in evolution (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Medium
status: Invalid → Confirmed
summary: - evolution crashes when opening multiple notes
+ evolution hangs when opening multiple notes
Changed in evolution (Ubuntu):
milestone: none → ubuntu-9.10-beta
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in evolution (Ubuntu):
status: Confirmed → Triaged
Changed in evolution:
importance: Undecided → Unknown
status: New → Unknown
Changed in evolution:
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package evolution - 2.27.92-0ubuntu2

---------------
evolution (2.27.92-0ubuntu2) karmic; urgency=low

  * debian/patches/91_git_change_fix_calendar_reminders.patch:
    - upstream change to fix an issue with calendar (lp: #424912)
  * debian/rules:
    - don't use -Bsymbolic-functions to workaround memos crashing
      (lp: #425621)

 -- Sebastien Bacher <email address hidden> Tue, 08 Sep 2009 19:08:38 +0200

Changed in evolution (Ubuntu):
status: Triaged → Fix Released
Changed in evolution:
importance: Unknown → Medium
Changed in evolution:
status: New → Won't Fix
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.