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 467047 - crash in Tasks: I had just send an email...
crash in Tasks: I had just send an email...
Status: RESOLVED DUPLICATE of bug 447591
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-15 18:49 UTC by dvelias02
Modified: 2007-11-30 18:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description dvelias02 2007-08-15 18:49:57 UTC
Version: 2.10

What were you doing when the application crashed?
I had just send an email. About 30 seconds afterwards the bug buddy dialog box popped up.


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:21:43 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: ifog-xp
Icon Theme: Clearlooks

Memory status: size: 705826816 vsize: 705826816 resident: 70213632 share: 46895104 rss: 70213632 rss_rlim: 18446744073709551615
CPU usage: start_time: 1187202470 rtime: 296 utime: 260 stime: 36 cutime:3 cstime: 12 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 46912496431248 (LWP 3381)]
[New Thread 1168148816 (LWP 3678)]
[New Thread 1084229968 (LWP 3677)]
[New Thread 1094719824 (LWP 3676)]
[New Thread 1094986064 (LWP 3452)]
[New Thread 1115699536 (LWP 3450)]
[New Thread 1126189392 (LWP 3411)]
(no debugging symbols found)
0x000000380860d97f in waitpid () from /lib64/libpthread.so.0

Thread 2 (Thread 1168148816 (LWP 3678))

  • #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 (602 sec old) ---------------------
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:3381): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3381): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:3381): e-data-server-DEBUG: Loading categories from "/home/elias/.evolution/categories.xml"
(evolution:3381): e-data-server-DEBUG: Loaded 29 categories
BBDB spinning up...
(evolution:3381): 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:3381): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8a6d40'
(evolution:3381): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8a6f40'
--------------------------------------------------
Comment 1 Suman Manjunath 2007-11-30 18:03:55 UTC
(evolution:3133): GLib-GObject-WARNING **: gsignal.c:1669: signal
`source_selected' is invalid for instance `0xaa6c008'
(evolution:3133): GLib-GObject-WARNING **: gsignal.c:1669: signal
`source_selected' is invalid for instance `0xaa6c128'

This is bug #447591, which is fixed now.

*** This bug has been marked as a duplicate of 447591 ***