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 459958 - crash in Tasks: Exiting the program
crash in Tasks: Exiting the program
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
: 463143 479207 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-07-24 16:37 UTC by sean
Modified: 2007-10-07 18:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description sean 2007-07-24 16:37:32 UTC
Version: 2.10

What were you doing when the application crashed?
Exiting the program


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.1-27.fc7 #1 SMP Tue Jul 17 17:19:58 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 639746048 vsize: 639746048 resident: 68476928 share: 40984576 rss: 68476928 rss_rlim: 18446744073709551615
CPU usage: start_time: 1185292953 rtime: 2659 utime: 2500 stime: 159 cutime:5 cstime: 14 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496386192 (LWP 3143)]
[New Thread 1168148816 (LWP 3488)]
[New Thread 1115699536 (LWP 3315)]
[New Thread 1074006352 (LWP 3221)]
[New Thread 1094719824 (LWP 3179)]
(no debugging symbols found)
0x00000038fd60d97f in waitpid () from /lib64/libpthread.so.0

Thread 5 (Thread 1094719824 (LWP 3179))

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


----------- .xsession-errors (23 sec old) ---------------------
which: no gwget in (/usr/lib64/qt-3.3/bin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/home/sean/bin:/usr/java/jdk1.6.0_02/bin)
which: no d4x in (/usr/lib64/qt-3.3/bin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/home/sean/bin:/usr/java/jdk1.6.0_02/bin)
which: no nt in (/usr/lib64/qt-3.3/bin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/home/sean/bin:/usr/java/jdk1.6.0_02/bin)
which: no aria in (/usr/lib64/qt-3.3/bin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/home/sean/bin:/usr/java/jdk1.6.0_02/bin)
BBDB spinning up...
(evolution:3143): e-data-server-DEBUG: Loading categories from "/home/sean/.evolution/categories.xml"
(evolution:3143): e-data-server-DEBUG: Loaded 28 categories
(evolution:3143): Gtk-CRITICAL **: gtk_toggle_button_get_active: assertion `GTK_IS_TOGGLE_BUTTON (toggle_button)' failed
(evolution:3143): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib64/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
(evolution:3143): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9794c0'
(evolution:3143): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9792c0'
--------------------------------------------------
Comment 1 Susana 2007-07-29 19:00:26 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. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

[1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
Comment 2 Iestyn Pryce 2007-08-04 09:38:01 UTC
*** Bug 463143 has been marked as a duplicate of this bug. ***
Comment 3 Suman Manjunath 2007-09-23 14:44:29 UTC
*** Bug 479207 has been marked as a duplicate of this bug. ***
Comment 4 Tobias Mueller 2007-10-07 18:22:33 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 ***