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 473244 - crash in Tasks: tying to use evolution e...
crash in Tasks: tying to use evolution e...
Status: RESOLVED DUPLICATE of bug 460409
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-09-03 17:25 UTC by sean.mcguffee
Modified: 2007-09-29 17:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description sean.mcguffee 2007-09-03 17:25:53 UTC
Version: 2.10

What were you doing when the application crashed?
tying to use evolution email thing


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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 723902464 vsize: 723902464 resident: 73654272 share: 38879232 rss: 73654272 rss_rlim: 18446744073709551615
CPU usage: start_time: 1188817585 rtime: 1801 utime: 1415 stime: 386 cutime:1 cstime: 8 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 46912514827024 (LWP 3965)]
[New Thread 1126455632 (LWP 4398)]
[New Thread 1115965776 (LWP 4170)]
[New Thread 1094719824 (LWP 4168)]
[New Thread 1084229968 (LWP 4134)]
(no debugging symbols found)
0x000000346160d97f in waitpid () from /lib64/libpthread.so.0

Thread 2 (Thread 1126455632 (LWP 4398))

  • #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 (51 sec old) ---------------------
(evolution:3965): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xcab9b0'
(evolution:3965): e-data-server-ui-WARNING **: Key file does not have key 'pop:__sean.mcguffee%40gmail.com@pop.gmail.com_'
(evolution:3965): 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:3965): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x171a6e0'
(evolution:3965): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xcaa1b0'
(evolution:3965): 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:3965): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x171b0e0'
(evolution:3965): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x171aee0'
--------------------------------------------------
Comment 1 Suman Manjunath 2007-09-29 17:52:35 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 460409 ***