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 475514 - 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 15:59 UTC by info
Modified: 2007-10-07 15:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description info 2007-09-10 15:59:28 UTC
What were you doing when the application crashed?



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-27.fc7 #1 SMP Tue Jul 17 17:13:26 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 127107072 vsize: 127107072 resident: 49090560 share: 35426304 rss: 49090560 rss_rlim: 4294967295
CPU usage: start_time: 1189439479 rtime: 360 utime: 311 stime: 49 cutime:31 cstime: 18 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 -1208457504 (LWP 31654)]
[New Thread -1326945392 (LWP 31790)]
[New Thread -1305965680 (LWP 31787)]
[New Thread -1269642352 (LWP 31685)]
[New Thread -1245987952 (LWP 31680)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 3 (Thread -1305965680 (LWP 31787))

  • #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 (209798 sec old) ---------------------
(evolution:3825): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3825): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3825): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3825): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3825): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3825): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3825): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3825): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3825): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3825): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3825): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3825): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3825): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Lucky Wankhede 2007-09-17 10:47:35 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-10-07 15:48:27 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 ***