Bug 420094 – crash in Evolution: - Kalender auf Datenträg...

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 420094 - crash in Evolution: - Kalender auf Datenträg...


Summary:	crash in Evolution: - Kalender auf Datenträg...


Status:	RESOLVED DUPLICATE of bug 334966

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.8.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-03-19 12:45 UTC by sssgorchfock
Modified:	2007-03-21 22:01 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description sssgorchfock 2007-03-19 12:45:48 UTC

What were you doing when the application crashed?
- Kalender auf Datenträger gespeichert (.ics Format)
- Kalenderdaten veröffentlicht
- EVOLUTION geschlossen (mittels anklicken des x im Fenster links oben


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 599789568 vsize: 599789568 resident: 23695360 share: 24915968 rss: 48611328 rss_rlim: 894858240
CPU usage: start_time: 1174310864 rtime: 2716 utime: 2582 stime: 134 cutime:24 cstime: 15 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/evolution-2.8'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47718694304976 (LWP 4960)]
[New Thread 1166059840 (LWP 14091)]
[New Thread 1149540672 (LWP 5014)]
[New Thread 1149274432 (LWP 5008)]
[New Thread 1140881728 (LWP 5007)]
[New Thread 1132489024 (LWP 5006)]
[New Thread 1124096320 (LWP 5005)]
[New Thread 1115703616 (LWP 5004)]
[New Thread 1082132800 (LWP 5003)]
[New Thread 1107310912 (LWP 4971)]
[New Thread 1098918208 (LWP 4970)]
[New Thread 1090525504 (LWP 4969)]
(no debugging symbols found)
0x00002b665d5d2c5f in waitpid () from /lib64/libpthread.so.0

+ Trace 120013

Thread 1 (Thread 47718694304976 (LWP 4960))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /opt/gnome/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 strcmp
from /lib64/libc.so.6
#4 e_shell_window_set_title
#5 e_shell_view_get_type
#6 GNOME_Evolution_ShellView_setTitle
from /opt/gnome/lib64/evolution/2.8/libeshell.so.0
#7 e_component_view_set_title
from /opt/gnome/lib64/evolution/2.8/libeshell.so.0
#8 mail_component_peek_local_store
from /opt/gnome/lib64/evolution/2.8/components/libevolution-mail.so
#9 g_source_get_current_time
from /opt/gnome/lib64/libglib-2.0.so.0
#10 g_main_context_dispatch
from /opt/gnome/lib64/libglib-2.0.so.0
#11 g_main_context_prepare
from /opt/gnome/lib64/libglib-2.0.so.0
#12 g_main_loop_run
from /opt/gnome/lib64/libglib-2.0.so.0
#13 bonobo_main
from /opt/gnome/lib64/libbonobo-2.so.0
#14 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Susana 2007-03-21 22:01:50 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 334966 ***