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 478190 - crash in Tasks: Stopping evolution
crash in Tasks: Stopping evolution
Status: RESOLVED DUPLICATE of bug 455329
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-18 22:09 UTC by bill
Modified: 2007-09-26 23:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description bill 2007-09-18 22:09:43 UTC 
Version: 2.10

What were you doing when the application crashed?
Stopping evolution


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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 186011648 vsize: 186011648 resident: 94470144 share: 40919040 rss: 94470144 rss_rlim: 4294967295
CPU usage: start_time: 1190120359 rtime: 10320 utime: 9529 stime: 791 cutime:61 cstime: 90 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 -1208760608 (LWP 17731)]
[New Thread -1303938160 (LWP 21106)]
[New Thread -1324917872 (LWP 17900)]
[New Thread -1262892144 (LWP 17783)]
[New Thread -1229517936 (LWP 17781)]
[New Thread -1252009072 (LWP 17780)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 163860

Thread 2 (Thread -1303938160 (LWP 21106))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 camel_message_info_ptr
    from /usr/lib/libcamel-provider-1.2.so.10
  • #5 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #6 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #7 camel_folder_summary_save
    from /usr/lib/libcamel-provider-1.2.so.10
  • #8 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #9 camel_folder_sync
    from /usr/lib/libcamel-provider-1.2.so.10
  • #10 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #11 camel_store_sync
    from /usr/lib/libcamel-provider-1.2.so.10
  • #12 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #13 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #14 ??
    from /lib/libglib-2.0.so.0
  • #15 ??
    from /lib/libglib-2.0.so.0
  • #16 start_thread
    from /lib/libpthread.so.0
  • #17 clone
    from /lib/libc.so.6 


----------- .xsession-errors ---------------------
(evolution:17731): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed
Reading file:///home/bill/.evolution/cache/tmp/evolution-tmp-58RKH3/RAT_Bugs-2007-09-17.xls
Excel 97 +
(evolution:17731): libecal-WARNING **: e-cal.c:317: Unexpected response
** Message: Response 1
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
Xlib: unexpected async reply (sequence 0x1e2655)!
--------------------------------------------------
Comment 1 Tobias Mueller 2007-09-26 23:10: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 455329 ***