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 456669 - crash in Tasks: Sitting around waiting f...
crash in Tasks: Sitting around waiting f...
Status: RESOLVED DUPLICATE of bug 455180
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-07-13 17:45 UTC by Raul Acevedo
Modified: 2007-08-17 12:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Raul Acevedo 2007-07-13 17:45:03 UTC 
Version: 2.10

What were you doing when the application crashed?
Sitting around waiting for Evolution to collect headers from a large folder.  I was doing nothing whatsoever with Tasks.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 131203072 vsize: 131203072 resident: 51683328 share: 33177600 rss: 51683328 rss_rlim: 4294967295
CPU usage: start_time: 1184348049 rtime: 677 utime: 645 stime: 32 cutime:0 cstime: 0 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 -1208793376 (LWP 11256)]
[New Thread -1294230640 (LWP 11402)]
[New Thread -1304720496 (LWP 11356)]
[New Thread -1274455152 (LWP 11268)]
[New Thread -1219519600 (LWP 11261)]
(no debugging symbols found)
0x0075d402 in __kernel_vsyscall ()

+ Trace 147841

Thread 1 (Thread -1208793376 (LWP 11256))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 ??
    from /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 g_slice_free1
    from /lib/libglib-2.0.so.0
  • #9 g_slist_free_1
    from /lib/libglib-2.0.so.0
  • #10 g_slist_remove
    from /lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #15 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (85558 sec old) ---------------------
aefbe000-aefbf000 rwxs 00254000 fd:00 16613476   /tmp/ffi6UAh3L (deleted)
aefbf000-aefc0000 rwxs 00253000 fd:00 16613476   /tmp/ffi6UAh3L (deleted)
aefc0000-aefc1000 rwxs 00252000 fd:00 16613476   /tmp/ffi6UAh3L (deleted)
aefc1000-aefc2000 rwxs 00251000 fd:00 16613476   /tmp/ffi6UAh3L (deleted)
aefc2000-aefc3000 rwxs 00250000 fd:00 16613476   /tmp/ffi6UAh3L (deleted)
aefc3000-aefc4000 rwxs 0024f000 fd:00 16613476   /tmp/ffi6UAh3L (deleted)
aefc4000-aefc5000 rwxp aefc4000 00:00 0 
aefc5000-aefc6000 rwxs 0024e000 fd:00 16613476   /tmp/ffi6UAh3L (deleted)
aefc6000-aefc7000 rwxs 0024d000 fd:00 16613476   /tmp/ffi6UAh3L (deleted)
aefc7000-aefc8000 rwxs 0024c000 fd:00 16613476   /tmp/ffi6UAh3L (deleted)
aefc8000-aefc9000 rwxs 0024b000 fd:00 16613476   /tmp/ffi6UAh3L (deleted)
aefc9000-aefca000 rwxs 0024a000 fd:00 16613476   /tmp/ffi6UAh3L (deleted)
aefca000-aefcb000 rwxs 00249000 fd:00 16613476   /tmp/ffi6UAh3L (deleted)
aefcb000-aefcc000 rwxs 00248000 fd:00 16613476   /tmp/ffi6UAh3
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 palfrey 2007-08-17 12:54:16 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

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