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 485200 - crash in Tasks: Closing the Evolution.
crash in Tasks: Closing the Evolution.
Status: RESOLVED DUPLICATE of bug 405646
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-09 21:18 UTC by Grzegorz Witkowski
Modified: 2007-10-10 08:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Grzegorz Witkowski 2007-10-09 21:18:12 UTC 
Version: 2.10

What were you doing when the application crashed?
Closing the Evolution.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks_Cairo-Human-In-Blue
Icon Theme: nuoveXT.2.2

Memory status: size: 141414400 vsize: 141414400 resident: 58691584 share: 34390016 rss: 58691584 rss_rlim: 4294967295
CPU usage: start_time: 1191962745 rtime: 7713 utime: 6856 stime: 857 cutime:117 cstime: 38 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 -1208776992 (LWP 2751)]
[New Thread -1330312304 (LWP 3118)]
[New Thread -1242514544 (LWP 2852)]
[New Thread -1297568880 (LWP 2764)]
[New Thread -1263494256 (LWP 2762)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 169126

Thread 5 (Thread -1263494256 (LWP 2762))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_mutex_lock_79
    from /lib/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 ??
  • #5 <signal handler called>
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 ??
    from /lib/libglib-2.0.so.0
  • #9 __nptl_deallocate_tsd
    from /lib/libpthread.so.0
  • #10 start_thread
    from /lib/libpthread.so.0
  • #11 clone
    from /lib/libc.so.6 


----------- .xsession-errors (6 sec old) ---------------------
(evolution:2751): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x92a56c0'
/usr/share/themes/Clearlooks_Cairo-Human-In-Blue/gtk-2.0/gtkrc:53: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks_Cairo-Human-In-Blue/gtk-2.0/gtkrc:54: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks_Cairo-Human-In-Blue/gtk-2.0/gtkrc:55: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.
(evolution:2751): gtkhtml-WARNING **: Selection retrieval failed
(evolution:2751): gtkhtml-WARNING **: Selection retrieval failed
(evolution:2751): e-data-server-ui-WARNING **: Key file does not have key 'smtp:__geslinux;auth_PLAIN@smtp.gmail.com_'
/usr/share/themes/Clearlooks_Cairo-Human-In-Blue/gtk-2.0/gtkrc:53: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks_Cairo-Human-In-Blue/gtk-2.0/gtkrc:54: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.
/usr/share/themes/Clearlooks_Cairo-Human-In-Blue/gtk-2.0/gtkrc:55: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.
--------------------------------------------------
Comment 1 Tobias Mueller 2007-10-10 08:37:37 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 405646 ***