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 473508 - crash in Tasks: closing evolution
crash in Tasks: closing 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-09-04 10:02 UTC by rjdsgomes
Modified: 2007-10-07 18:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description rjdsgomes 2007-09-04 10:02:15 UTC 
Version: 2.10

What were you doing when the application crashed?
closing 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 126197760 vsize: 126197760 resident: 49274880 share: 30949376 rss: 49274880 rss_rlim: 4294967295
CPU usage: start_time: 1188899645 rtime: 1097 utime: 1028 stime: 69 cutime:33 cstime: 13 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 -1208457504 (LWP 3808)]
[New Thread -1247630448 (LWP 4104)]
[New Thread -1224291440 (LWP 3949)]
[New Thread -1300079728 (LWP 3947)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 160344

Thread 2 (Thread -1247630448 (LWP 4104))

  • #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 (91 sec old) ---------------------
(evolution:3808): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed
(evolution:3808): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed
(evolution:3808): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed
(evolution:3808): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed
(evolution:3808): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail'
(evolution:3808): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
(evolution:3808): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa3415b8'
(evolution:3808): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa3416d8'
--------------------------------------------------
Comment 1 Johnny Jacob 2007-09-04 13:23:49 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Tobias Mueller 2007-10-07 18:19:42 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 ***