evolution hangs when opening multiple notes
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-
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-
(evolution:10798): GLib-CRITICAL **: g_once_init_leave: assertion `initialization
(evolution:10798): calendar-
[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
ProcVersionSign
SourcePackage: evolution
Uname: Linux 2.6.31-9-generic i686
Related branches
Changed in evolution (Ubuntu): | |
milestone: | none → ubuntu-9.10-beta |
description: | updated |
Changed in evolution: | |
status: | Unknown → New |
Changed in evolution: | |
importance: | Unknown → Medium |
Changed in evolution: | |
status: | New → Won't Fix |
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.