Bug 447553 – crash in Calendar: evolution

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 447553 - crash in Calendar: evolution


Summary:	crash in Calendar: evolution


Status:	RESOLVED DUPLICATE of bug 442949

Product:	evolution
Classification:	Applications
Component:	Calendar
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-06-14 14:33 UTC by melonever
Modified:	2007-06-15 17:29 UTC

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

Description melonever 2007-06-14 14:33:07 UTC

What were you doing when the application crashed?
evolution



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 183545856 vsize: 183545856 resident: 75235328 share: 52678656 rss: 75235328 rss_rlim: 4294967295
CPU usage: start_time: 1181830731 rtime: 982 utime: 931 stime: 51 cutime:0 cstime: 0 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 -1208453408 (LWP 4114)]
[New Thread -1252029552 (LWP 4200)]
[New Thread -1241138288 (LWP 4125)]
(no debugging symbols found)
0x0085e402 in __kernel_vsyscall ()

+ Trace 140947

Thread 1 (Thread -1208453408 (LWP 4114))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 pango_font_description_free
from /usr/lib/libpango-1.0.so.0
#6 pango_context_set_font_description
from /usr/lib/libpango-1.0.so.0
#7 ??
from /usr/lib/libgtk-x11-2.0.so.0
#8 ??
from /usr/lib/libgtk-x11-2.0.so.0
#9 ??
from /usr/lib/libgtk-x11-2.0.so.0
#10 ??
from /usr/lib/libgtk-x11-2.0.so.0
#11 ??
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#13 ??
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#16 ??
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_widget_reset_rc_styles
from /usr/lib/libgtk-x11-2.0.so.0
#18 ??
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_rc_reparse_all_for_settings
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_rc_reparse_all
from /usr/lib/libgtk-x11-2.0.so.0
#21 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#22 ??
from /usr/lib/libgconf-2.so.4
#23 gconf_listeners_notify
from /usr/lib/libgconf-2.so.4
#24 ??
from /usr/lib/libgconf-2.so.4
#25 ??
from /usr/lib/libgconf-2.so.4
#26 ??
from /lib/libglib-2.0.so.0
#27 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#28 ??
from /lib/libglib-2.0.so.0
#29 g_main_loop_run
from /lib/libglib-2.0.so.0
#30 bonobo_main
from /usr/lib/libbonobo-2.so.0
#31 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
(evolution:4114): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9a9c6e0'
(evolution:4114): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9a9c800'
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x45
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x184025d
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x184025d
--------------------------------------------------

Comment 1 André Klapper 2007-06-15 17:29:10 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 442949 ***