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 464531 - crash in Tasks: Closing Evolution (X in ...
crash in Tasks: Closing Evolution (X in ...
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-08-07 23:43 UTC by lee
Modified: 2007-10-07 18:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description lee 2007-08-07 23:43:20 UTC
Version: 2.10

What were you doing when the application crashed?
Closing Evolution (X in top right corner). No other apps running. Had just changed mail prefs to always load images from the internet.


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-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 125779968 vsize: 125779968 resident: 52916224 share: 39059456 rss: 52916224 rss_rlim: 4294967295
CPU usage: start_time: 1186529968 rtime: 561 utime: 529 stime: 32 cutime:3 cstime: 5 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 -1208301856 (LWP 2706)]
[New Thread -1251103856 (LWP 2823)]
[New Thread -1271424112 (LWP 2822)]
[New Thread -1282307184 (LWP 2768)]
[New Thread -1240220784 (LWP 2744)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 5 (Thread -1240220784 (LWP 2744))

  • #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 (24 sec old) ---------------------
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:2099): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:2099): DEBUG: mailto URL program: evolution
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:2706): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:2706): DEBUG: mailto URL program: evolution
(evolution:2706): 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?)
BBDB spinning up...
(evolution:2706): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa57a020'
(evolution:2706): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa57a140'
--------------------------------------------------
Comment 1 Tobias Mueller 2007-08-18 14:42:38 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 lee 2007-08-19 22:23:06 UTC
Hi, no problems, glad to help when/if I can. Unfortunately (well, sorta!) this bug has not reappeared since that day. I will provide a full stack trace next time. Just replying to let you know I got (and acknowledged) your message. Thanks for taking the time to reply. As I say, if it recurs, I'll be back with better info.
Comment 3 Tobias Mueller 2007-10-07 18:22:04 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 ***