Bug 644810 – crash in Evolution: I've tried to open an ad...

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 644810 - crash in Evolution: I've tried to open an ad...


Summary:	crash in Evolution: I've tried to open an ad...


Status:	RESOLVED DUPLICATE of bug 633386

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.30.x (obsolete)
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2011-03-15 10:56 UTC by tim.gruenberg
Modified:	2011-03-15 11:06 UTC

See Also:
GNOME target:	---
GNOME version:	2.29/2.30

Description tim.gruenberg 2011-03-15 10:56:50 UTC

What were you doing when the application crashed?
I've tried to open an adobe PDF


Distribution: Debian 6.0
Gnome Release: 2.30.2 2010-11-12 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.32.9 #2 SMP Mon May 31 15:01:19 CEST 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Glider
Icon Theme: gnome
GTK+ Modules: gnomebreakpad, gail:atk-bridge, gail-gnome, canberra-gtk-module

Memory status: size: 313933824 vsize: 313933824 resident: 61218816 share: 26226688 rss: 61218816 rss_rlim: 18446744073709551615
CPU usage: start_time: 1300176301 rtime: 4553 utime: 4143 stime: 410 cutime:84 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

[Thread debugging using libthread_db enabled]
[New Thread 0xb22fab70 (LWP 13645)]
[New Thread 0xa8a1eb70 (LWP 8077)]
[New Thread 0xa921fb70 (LWP 8076)]
[New Thread 0xad6fdb70 (LWP 8069)]
[New Thread 0xadefeb70 (LWP 8068)]
[New Thread 0xae6ffb70 (LWP 8067)]
[New Thread 0xaf0fab70 (LWP 8066)]
[New Thread 0xb18ffb70 (LWP 8065)]
[New Thread 0xaf8fbb70 (LWP 8064)]
[New Thread 0xb00fcb70 (LWP 8063)]
[New Thread 0xb08fdb70 (LWP 8062)]
[New Thread 0xb10feb70 (LWP 8061)]
[New Thread 0xb2afbb70 (LWP 8058)]
[New Thread 0xb3afdb70 (LWP 8056)]
[New Thread 0xb42feb70 (LWP 8055)]
[New Thread 0xb4affb70 (LWP 8054)]
[New Thread 0xb543db70 (LWP 8053)]
0xffffe424 in __kernel_vsyscall ()

+ Trace 226331

Thread 1 (Thread 0xb5eb4770 (LWP 8026))

#0 __kernel_vsyscall
#1 waitpid
at ../sysdeps/unix/syscall-template.S line 82
#2 g_spawn_sync
from /lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
#6 <signal handler called>
#7 ??
from /usr/lib/evolution/2.30/libetable.so.0
#8 ??
from /usr/lib/evolution/2.30/libetable.so.0
#9 atk_object_get_name
from /usr/lib/libatk-1.0.so.0
#10 ??
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#11 ??
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#12 ??
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#13 atk_focus_tracker_notify
from /usr/lib/libatk-1.0.so.0
#14 ??
from /usr/lib/gtk-2.0/modules/libgail.so
#15 ??
from /usr/lib/libgdk-x11-2.0.so.0
#16 ??
from /lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#18 ??
from /lib/libglib-2.0.so.0
#19 g_main_loop_run
from /lib/libglib-2.0.so.0
#20 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#21 ??
#22 __libc_start_main
at libc-start.c line 228
#23 ??

A debugging session is active.

	Inferior 1 [process 8026] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


---- Critical and fatal warnings logged during execution ----

** libecal **: e_cal_util_parse_ics_string: assertion `string != NULL' failed

Comment 1 Akhil Laddha 2011-03-15 11:06:26 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 bug 633386 ***