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 323906 - Selecting calendar crashes the app
Selecting calendar crashes the app
Status: RESOLVED DUPLICATE of bug 325168
Product: evolution
Classification: Applications
Component: Calendar
2.4.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-12-12 17:43 UTC by Andrés Suárez
Modified: 2006-01-01 13:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description Andrés Suárez 2005-12-12 17:43:07 UTC
Steps to reproduce:
1. Open evolution
2. Select calendar
3. Crash!

1. Open evolution
2. Select tasks
3. New Task (or edit)
4. Open the mini calendar (like start date)
5. Crash!

Stack trace:
 gdb evolution
GNU gdb 6.3-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

(gdb)
(gdb) r
Starting program: /usr/bin/evolution
(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)
---Type <return> to continue, or q <return> to quit---
(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)
---Type <return> to continue, or q <return> to quit---
(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 -1230234816 (LWP 10957)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(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)
---Type <return> to continue, or q <return> to quit---
(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)
---Type <return> to continue, or q <return> to quit---
(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)
adding hook target 'source'
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

(evolution:10957): camel-WARNING **: camel_exception_get_id called with NULL
parameter.
[New Thread -1236599888 (LWP 11053)]
[New Thread -1244992592 (LWP 11054)]
(no debugging symbols found)
[Thread -1244992592 (LWP 11054) exited]
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)

(evolution:10957): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion `GDK_IS_GC
(gc)' failed
[New Thread -1253995600 (LWP 11183)]
[New Thread -1244992592 (LWP 11184)]
[New Thread -1254655056 (LWP 11188)]
[New Thread -1263047760 (LWP 11190)]
[Thread -1254655056 (LWP 11188) exited]
[New Thread -1254655056 (LWP 11193)]
[New Thread -1271440464 (LWP 11194)]
[Thread -1254655056 (LWP 11193) exited]
[Thread -1271440464 (LWP 11194) exited]
[Thread -1263047760 (LWP 11190) exited]
[Thread -1244992592 (LWP 11184) exited]

(evolution:10957): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion `GDK_IS_GC
(gc)' failed

(evolution:10957): GLib-GObject-WARNING **: gsignal.c:1716: signal `toggled' is
invalid for instance `0x81ee0d8'

(evolution:10957): GLib-GObject-WARNING **: gsignal.c:1716: signal `toggled' is
invalid for instance `0x81ee0d8'

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1230234816 (LWP 10957)]
0xb694fdb0 in clearlooks_rc_style_register_type ()
   from /usr/lib/gtk-2.0/2.4.0/engines/libclearlooks.so
(gdb)
(gdb) quit
The program is running.  Exit anyway? (y or n) y


Other information:
Happens since today, no upgrades or anything installed
Comment 1 Chenthill P 2005-12-14 11:47:21 UTC
It might be specific to clear looks theme.
Comment 2 André Klapper 2005-12-14 23:10:40 UTC
hi andres, thanks for reporting. is this reproducible?
also, the stacktrace is not very useful. can you get us a new one? please take a
look at section "Debugging Evolution's Crashes" at
http://www.gnome.org/projects/evolution/bugs.shtml and submit the "debugging
info" (that is the gdb stacktrace) here again.

setting to NEEDINFO, please REOPEN the bug when answering. thanks in advance.
Comment 3 Andrés Suárez 2005-12-15 00:44:17 UTC
It was, but i fixed it somehow, i use ubuntu breezy, and i used to have the new
cairo enabled clearlooks, removed them and it works fine now, i'll ckeck if
installking again causes the problem to re-appear on the weekend
Comment 4 André Klapper 2005-12-15 11:00:08 UTC
there are quite a few bugs around with clearlocks theme, yeah :-/

thanks in advance for checking this again
Comment 5 André Klapper 2006-01-01 13:00:42 UTC
clearlooks issues should be mostly fixed now by bug 325168 fixed.  marking as duplicate. thanks for reporting.

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