GNOME Bugzilla – Bug 325168
GTK theme (clearlooks) calendar crash
Last modified: 2006-02-12 04:41:05 UTC
Distribution: Ubuntu 5.10 (breezy) Package: Evolution Severity: blocker Version: GNOME2.12.1 2.4.x Gnome-Distributor: Ubuntu Synopsis: Calendar component chrash Bugzilla-Product: Evolution Bugzilla-Component: Calendar Bugzilla-Version: 2.4.x BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: Evolution shrashes when start with calendar component. Steps to reproduce the crash: 1. Start Evolution with Calendar component How often does this happen? Everytime Debugging Information: Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208247488 (LWP 23321)] [New Thread -1240466512 (LWP 23335)] [New Thread -1222050896 (LWP 23324)] [New Thread -1212961872 (LWP 23323)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x48ac2a01 in waitpid () from /lib/tls/libc.so.6
+ Trace 64846
Thread 1 (Thread -1208247488 (LWP 23321))
------- Bug created by bug-buddy at 2005-12-28 20:40 -------
Thanks for this report, but the description of this bug is not complete. Please can you complete this one ?
are you able to start evolution in another view, e.g. by "evolution -c mail"?
(In reply to comment #2) > are you able to start evolution in another view, e.g. by "evolution -c mail"? Yes, but when starting Evolution with 'evolution -c calendar' or clicking on 'Calendar' button in Evolution gives me "The Application "evolution" has quit unexpectedly" dialog. Same chrash occurs if I run Calendar component from gdeskcal or from clock applet in Gnome panel.
This bug dissapears when I changed my GTK theme. With Ubuntu default Human theme and Clearlooks theme Calendar component crash, but I installed Bluecurve theme and problem is gone.
hmm... so another theme crash. sigh... but thanks for the answer and trying. :-) reopening.
crashes in clearlooks_rc_style_register_type () which is from the clearlooks theme engine. assigning to them. unique stack trace. svakak, Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. we need debug sybols for clearlooks and gtk+ (libgtk)
Created attachment 56599 [details] [review] patch to fix this, and other similar bugs Clearlooks sometimes does look at the parent of the widget without checking whether the widget exists. The patch fixes all of the cases that I found. This patch fixes the bug for me.
2005-12-31 Benjamin Berg <benjamin@sipsolutions.net> * engines/clearlooks/src/clearlooks_style.c: (draw_box_gap), (draw_box): Fix some possible NULL dereferenciations.
*** Bug 323616 has been marked as a duplicate of this bug. ***
*** Bug 323906 has been marked as a duplicate of this bug. ***
*** Bug 329322 has been marked as a duplicate of this bug. ***
*** Bug 330848 has been marked as a duplicate of this bug. ***