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 495353 - crash in Tasks: closing the program afte...
crash in Tasks: closing the program afte...
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-11-09 17:58 UTC by linuxman
Modified: 2007-11-11 12:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description linuxman 2007-11-09 17:58:40 UTC
Version: 2.10

What were you doing when the application crashed?
closing the program after adjusting preference


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.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 115712000 vsize: 115712000 resident: 44376064 share: 32382976 rss: 44376064 rss_rlim: 4294967295
CPU usage: start_time: 1194630765 rtime: 1199 utime: 1108 stime: 91 cutime:1 cstime: 4 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 -1208235280 (LWP 2957)]
[New Thread -1230980208 (LWP 3006)]
[New Thread -1274365040 (LWP 2985)]
[New Thread -1241470064 (LWP 2976)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 4 (Thread -1241470064 (LWP 2976))

  • #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 (250 sec old) ---------------------
(evolution:2863): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9e15138'
(evolution:2863): e-data-server-CRITICAL **: e_source_get_uri: assertion `E_IS_SOURCE (source)' failed
(evolution:2863): GConf-CRITICAL **: gconf_client_set_string: assertion `val != NULL' failed
CalDAV Eplugin starting up ...
** (evolution:2957): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:2957): DEBUG: mailto URL program: evolution
(evolution:2957): 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:2957): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8cf7010'
(evolution:2957): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8cf7130'
--------------------------------------------------
Comment 1 Tobias Mueller 2007-11-11 12:49:23 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 ***