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 483711 - crash in Tasks: I was not using evolutio...
crash in Tasks: I was not using evolutio...
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-10-05 12:52 UTC by lars.nylander
Modified: 2007-10-07 15:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description lars.nylander 2007-10-05 12:52:52 UTC
Version: 2.10

What were you doing when the application crashed?
I was not using evolution however it is alwasy running and popping every 10minutes. The apparent crash coincides fairly well with the 14:50 poptime


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.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Lila

Memory status: size: 730169344 vsize: 730169344 resident: 103563264 share: 34381824 rss: 103563264 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191396559 rtime: 25397 utime: 22602 stime: 2795 cutime:31 cstime: 45 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 46912496492688 (LWP 3529)]
[New Thread 1126189392 (LWP 11491)]
[New Thread 1147435344 (LWP 11488)]
[New Thread 1168415056 (LWP 11486)]
[New Thread 1136945488 (LWP 6602)]
[New Thread 1126455632 (LWP 3558)]
[New Thread 1115699536 (LWP 3554)]
(no debugging symbols found)
0x0000003fab80d97f in waitpid () from /lib64/libpthread.so.0

Thread 4 (Thread 1168415056 (LWP 11486))

  • #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 ---------------------
(evolution:3529): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x2d986a0'
WARNING: Remote desktop does not support colour depth 24; falling back to 16
warning: .dynamic section for "/usr/lib64/libgnomeprintui-2-2.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib64/libaspell.so.15" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib64/libstdc++.so.6" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/lib64/libgcc_s.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 Suman Manjunath 2007-10-07 15:33:36 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 ***