Bug 601434 – crash in Evolution: I'd just created an appo...

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 601434 - crash in Evolution: I'd just created an appo...


Summary:	crash in Evolution: I'd just created an appo...


Status:	RESOLVED DUPLICATE of bug 597648

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	1.5.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:	2009-11-10 19:30 UTC by David Ronis
Modified:	2009-11-11 04:01 UTC

See Also:
GNOME target:	---
GNOME version:	2.27/2.28

Description David Ronis 2009-11-10 19:30:54 UTC

Version: 2.30.x

What were you doing when the application crashed?
I'd just created an appointment entry in a local calendar.  I'd right-clicked and copied it, and then moved forward 1 month in order to enter it at a later date as well.   

I'm running today's git master



Distribution: Slackware Slackware 12.2.0
Gnome Release: 2.28.0 2009-10-22 (GARNOME)
BugBuddy Version: 2.28.0

System: Linux 2.6.31.5 #46 SMP PREEMPT Mon Oct 26 17:31:19 EDT 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10799002
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: gnomebreakpad

Memory status: size: 221208576 vsize: 221208576 resident: 62906368 share: 29671424 rss: 62906368 rss_rlim: 18446744073709551615
CPU usage: start_time: 1257881049 rtime: 3339 utime: 3056 stime: 283 cutime:33 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/garnome-svn-2.28/bin/evolution'

[Thread debugging using libthread_db enabled]
[New Thread 0xb57b3a20 (LWP 3375)]
[New Thread 0xab70eb90 (LWP 3614)]
[New Thread 0xaef0eb90 (LWP 3409)]
[New Thread 0xaf772b90 (LWP 3408)]
[New Thread 0xb0a88b90 (LWP 3390)]
[New Thread 0xb1288b90 (LWP 3389)]
[New Thread 0xb2620b90 (LWP 3388)]
[New Thread 0xb2e20b90 (LWP 3387)]
0xb58be01d in poll () from /lib/libc.so.6

+ Trace 218989

Thread 2 (Thread 0xab70eb90 (LWP 3614))

#0 waitpid
from /lib/libpthread.so.0
#1 IA__g_spawn_sync
at gspawn.c line 386
#2 IA__g_spawn_command_line_sync
at gspawn.c line 700
#3 run_bug_buddy
at gnome-breakpad.cc line 369
#4 bugbuddy_segv_handle
at gnome-breakpad.cc line 440
#5 <signal handler called>
#6 IA__g_logv
at gmessages.c line 555
#7 IA__g_log
at gmessages.c line 569
#8 dbus_g_proxy_begin_call_internal
at dbus-gproxy.c line 2232
#9 dbus_g_proxy_call
at dbus-gproxy.c line 2586
#10 e_cal_dispose
at e-data-cal-bindings.h line 107
#11 IA__g_object_unref
at gobject.c line 2441
#12 e_cal_view_finalize
at e-cal-view.c line 272
#13 IA__g_object_unref
at gobject.c line 2472
#14 update_query_async
at gnome-cal.c line 1015
#15 message_proxy
at gnome-cal.c line 185
#16 g_thread_pool_thread_proxy
at gthreadpool.c line 265
#17 g_thread_create_proxy
at gthread.c line 635
#18 start_thread
from /lib/libpthread.so.0
#19 clone
from /lib/libc.so.6



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

** Gdk **: gdk_drawable_get_colormap: assertion `GDK_IS_DRAWABLE (drawable)' failed 
** Gdk **: gdk_window_set_background: assertion `GDK_IS_WINDOW (window)' failed 
** calendar-modules **: file e-cal-shell-content.c: line 697 (e_cal_shell_content_copy_clipboard): should not be reached 
** evolution **: Out of memory

Comment 1 Akhil Laddha 2009-11-11 04:01:05 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 bug 597648 ***