Bug 442499 – crash in Evolution: creating a new callendar...

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 442499 - crash in Evolution: creating a new callendar...


Summary:	crash in Evolution: creating a new callendar...


Status:	RESOLVED DUPLICATE of bug 354513

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-05-31 03:32 UTC by ashton_clemens_747
Modified:	2007-06-15 17:57 UTC

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

Description ashton_clemens_747 2007-05-31 03:32:28 UTC

What were you doing when the application crashed?
creating a new callendar



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

Memory status: size: 433786880 vsize: 433786880 resident: 9306112 share: 19402752 rss: 28708864 rss_rlim: 1793720320
CPU usage: start_time: 1180564137 rtime: 293 utime: 276 stime: 17 cutime:0 cstime: 0 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 46961195982032 (LWP 5904)]
[New Thread 1082399040 (LWP 5909)]
(no debugging symbols found)
0x00002ab5fef20c5f in waitpid () from /lib64/libpthread.so.0

+ Trace 136949

Thread 1 (Thread 46961195982032 (LWP 5904))

#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 raise
from /lib64/libc.so.6
#4 abort
from /lib64/libc.so.6
#5 g_logv
from /opt/gnome/lib64/libglib-2.0.so.0
#6 g_log
from /opt/gnome/lib64/libglib-2.0.so.0
#7 g_assert_warning
from /opt/gnome/lib64/libglib-2.0.so.0
#8 e_cal_model_set_default_client
from /opt/gnome/lib64/evolution/2.8/components/libevolution-calendar.so
#9 gnome_calendar_discard_view_menus
from /opt/gnome/lib64/evolution/2.8/components/libevolution-calendar.so
#10 g_closure_invoke
from /opt/gnome/lib64/libgobject-2.0.so.0
#11 g_signal_override_class_closure
from /opt/gnome/lib64/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /opt/gnome/lib64/libgobject-2.0.so.0
#13 g_signal_emit
from /opt/gnome/lib64/libgobject-2.0.so.0
#14 e_cal_free_alarms
from /opt/gnome/lib64/libecal-1.2.so.7
#15 g_main_context_dispatch
from /opt/gnome/lib64/libglib-2.0.so.0
#16 g_main_context_prepare
from /opt/gnome/lib64/libglib-2.0.so.0
#17 g_main_loop_run
from /opt/gnome/lib64/libglib-2.0.so.0
#18 bonobo_main
from /opt/gnome/lib64/libbonobo-2.so.0
#19 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 palfrey 2007-05-31 15:36:51 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!

Comment 2 André Klapper 2007-06-15 17:57:12 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 354513 ***