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 491672 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 405497
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-30 12:06 UTC by Pete Gillis
Modified: 2007-12-21 15:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Pete Gillis 2007-10-30 12:06:50 UTC
Version: 2.10

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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 106414080 vsize: 106414080 resident: 49438720 share: 32718848 rss: 49438720 rss_rlim: 4294967295
CPU usage: start_time: 1193745825 rtime: 470 utime: 452 stime: 18 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 -1208842528 (LWP 3115)]
[New Thread -1228493936 (LWP 4361)]
[New Thread -1224217712 (LWP 4335)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1228493936 (LWP 4361))

  • #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 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #7 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #8 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #9 ??
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /lib/libglib-2.0.so.0
  • #11 start_thread
    from /lib/libpthread.so.0
  • #12 clone
    from /lib/libc.so.6


----------- .xsession-errors ---------------------
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libpng12.so.0/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2)
(evolution:3115): e-data-server-DEBUG: Loading categories from "/home/pgillis/.evolution/categories.xml"
(evolution:3115): e-data-server-DEBUG: Loaded 29 categories
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x40000de (Java - RT/)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
camel-groupwise-provider-Message: Purged deleted items in Trash
camel-groupwise-provider-Message: Purged deleted items in Sent Items
camel-groupwise-provider-Message: Purged deleted items in Mailbox
camel-groupwise-provider-Message: Purged deleted items in Checklist
camel-groupwise-provider-Message: Purged deleted items in Documents
camel-groupwise-provider-Message: Purged deleted items in Junk Mail
camel-groupwise-provider-Message: Purged deleted items in Default Library
camel-groupwise-provider-Message: Purged deleted items in Work In Progress
camel-groupwise-provider-Message: Purged deleted items in Cabinet
camel-groupwise-provider-Message: Purged deleted items in Authored
--------------------------------------------------
Comment 1 André Klapper 2007-12-19 03:31:49 UTC
Thanks for taking the time to report this bug.
Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash.

Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

[1] Please install debug packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution).

More details can be found here: http://live.gnome.org/GettingTraces
Comment 2 Pete Gillis 2007-12-21 15:29:59 UTC
I have since upgraded to Fedora 8, but the crash is still there.  It seems to be related somehow to saved search folders.  When I had removed them, it went away.  I have recreated the folders and it crashes more often than not when closing the application.  I have added the debuginfo you requested along with others that seemed to be referenced...


Distribution: Fedora release 8 (Werewolf)
Gnome Release: 2.20.2 2007-11-27 (Red Hat, Inc)
BugBuddy Version: 2.20.1

System: Linux 2.6.23.9-85.fc8 #1 SMP Fri Dec 7 15:49:59 EST 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: 159068160 vsize: 159068160 resident: 37236736 share: 18509824 rss: 37236736 rss_rlim: 4294967295
CPU usage: start_time: 1198250579 rtime: 656 utime: 647 stime: 9 cutime:1 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

[?1034hUsing host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1209161968 (LWP 8071)]
[New Thread -1292899440 (LWP 8136)]
[New Thread -1282409584 (LWP 8095)]
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1292899440 (LWP 8136))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_lock_88
    from /lib/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 segv_redirect
    at main.c line 422
  • #5 <signal handler called>
  • #6 IA__g_list_find
    at glist.c line 386
  • #7 folder_changed_change
    at camel-vee-folder.c line 1224
  • #8 session_thread_proxy
    at camel-session.c line 532
  • #9 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #10 g_thread_create_proxy
    at gthread.c line 635
  • #11 start_thread
    from /lib/libpthread.so.0
  • #12 clone
    from /lib/libc.so.6


----------- .xsession-errors (53 sec old) ---------------------
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/e4/70c82d225d914fa1df17955c78444c7642ed58.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/c5/359ced128e04271ac8f6cedd4ff60f6ccb970d.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/3f/ba93bfbd5c76107bbe70c550f944cafce0c266.debug
warning: Missing the separate debug info file: /usr/lib/debug/.build-id/d4/68ff7b305f6335f4b42937ce21d252c1aa76cc.debug
keybinding-properties-Message: title: Sound
keybinding-properties-Message: title: Desktop
keybinding-properties-Message: title: Desktop
keybinding-properties-Message: title: Window Management
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
--------------------------------------------------
Comment 3 André Klapper 2007-12-21 15:53:40 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 405497 ***