Bug 480781 – crash in Tasks: Opening calendar event i...

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 480781 - crash in Tasks: Opening calendar event i...


Summary:	crash in Tasks: Opening calendar event i...


Status:	RESOLVED DUPLICATE of bug 451144

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-09-26 23:09 UTC by npiacentine
Modified:	2007-12-19 03:45 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description npiacentine 2007-09-26 23:09:15 UTC

Version: 2.10

What were you doing when the application crashed?
Opening calendar event in evolution		


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 154628096 vsize: 154628096 resident: 58294272 share: 41316352 rss: 58294272 rss_rlim: 4294967295
CPU usage: start_time: 1190826816 rtime: 4748 utime: 4447 stime: 301 cutime:82 cstime: 46 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208961312 (LWP 30740)]
[New Thread -1231840368 (LWP 13158)]
[New Thread -1275475056 (LWP 30763)]
[New Thread -1254495344 (LWP 30761)]
[New Thread -1243612272 (LWP 30760)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 165780

Thread 1 (Thread -1208961312 (LWP 30740))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 g_object_ref
from /lib/libgobject-2.0.so.0
#6 e_cal_model_copy_component_data
from /usr/lib/evolution/2.10/components/libevolution-calendar.so
#7 calendar_control_sensitize_calendar_commands
from /usr/lib/evolution/2.10/components/libevolution-calendar.so
#8 ??
from /usr/lib/evolution/2.10/components/libevolution-calendar.so
#9 g_cclosure_marshal_VOID__BOOLEAN
from /lib/libgobject-2.0.so.0
#10 g_closure_invoke
from /lib/libgobject-2.0.so.0
#11 ??
from /lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#13 gtk_signal_emit
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib/evolution/2.10/components/libevolution-calendar.so
#15 ??
from /usr/lib/libgtk-x11-2.0.so.0
#16 g_closure_invoke
from /lib/libgobject-2.0.so.0
#17 ??
from /lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#19 g_signal_emit
from /lib/libgobject-2.0.so.0
#20 ??
from /usr/lib/libgtk-x11-2.0.so.0
#21 ??
from /usr/lib/libgtk-x11-2.0.so.0
#22 ??
from /usr/lib/libgtk-x11-2.0.so.0
#23 ??
from /usr/lib/libgtk-x11-2.0.so.0
#24 ??
from /usr/lib/libgtk-x11-2.0.so.0
#25 ??
from /lib/libgobject-2.0.so.0
#26 g_closure_invoke
from /lib/libgobject-2.0.so.0
#27 ??
from /lib/libgobject-2.0.so.0
#28 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#29 g_signal_emit
from /lib/libgobject-2.0.so.0
#30 ??
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#32 ??
from /usr/lib/libgdk-x11-2.0.so.0
#33 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#34 ??
from /lib/libglib-2.0.so.0
#35 g_main_loop_run
from /lib/libglib-2.0.so.0
#36 bonobo_main
from /usr/lib/libbonobo-2.so.0
#37 main
#0 __kernel_vsyscall



----------- .xsession-errors (3342 sec old) ---------------------
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 André Klapper 2007-12-19 03:45:36 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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