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 475457 - crash in Tasks:
crash in Tasks:
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-10 12:55 UTC by ken.jones
Modified: 2007-09-21 18:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description ken.jones 2007-09-10 12:55:11 UTC
Version: 2.10

What were you doing when the application crashed?



Distribution: redhat-4
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 771727360 vsize: 771727360 resident: 121298944 share: 42995712 rss: 121298944 rss_rlim: 18446744073709551615
CPU usage: start_time: 1189089708 rtime: 9816 utime: 9071 stime: 745 cutime:4 cstime: 17 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 46912636065344 (LWP 20252)]
[New Thread 1084229968 (LWP 18551)]
[New Thread 1094719824 (LWP 20301)]
[New Thread 1147435344 (LWP 20299)]
(no debugging symbols found)
0x00002aaaacdc397f in waitpid () from /lib64/libpthread.so.0

Thread 2 (Thread 1084229968 (LWP 18551))

  • #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 (2767 sec old) ---------------------
(evolution:20252): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x3159790'
(evolution:20252): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x3f447c0'
(evolution:20252): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Host lookup failed: exch1-bllon@uk.easynet.corp: Name or service not known
(evolution:20252): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Host lookup failed: exch1-bllon@uk.easynet.corp: Name or service not known
(evolution:20252): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Host lookup failed: exch1-bllon@uk.easynet.corp: Name or service not known
(evolution:20252): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Host lookup failed: exch1-bllon@uk.easynet.corp: Name or service not known
--------------------------------------------------
Comment 1 Lucky Wankhede 2007-09-17 08:36:49 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug.

You'll also need to add a stack trace; please see http://live.gnome.org/GettingTraces for more information about how to do so. Thanks in advance!
Comment 2 Suman Manjunath 2007-09-21 17:38:34 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 ***