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 350752 - Evolution crashes
Evolution crashes
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Calendar
2.6.x (obsolete)
Other other
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 350757 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-08-10 15:02 UTC by John.Ata
Modified: 2006-11-28 22:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description John.Ata 2006-08-10 15:01:54 UTC
Distribution: Fedora Core release 5 (Bordeaux)
Package: Evolution
Severity: blocker
Version: GNOME2.14.2 2.6.x
Gnome-Distributor: Red Hat, Inc
Synopsis: Evolution crashes
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: 2.6.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Just trying to read email

Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208781120 (LWP 4447)]
[New Thread -1325954144 (LWP 4486)]
[New Thread -1340081248 (LWP 4485)]
[New Thread -1327498336 (LWP 4471)]
[New Thread -1314927712 (LWP 4457)]
[New Thread -1304437856 (LWP 4456)]
[New Thread -1293948000 (LWP 4454)]
[New Thread -1283458144 (LWP 4453)]
[New Thread -1246049376 (LWP 4451)]
[New Thread -1235559520 (LWP 4449)]
(no debugging symbols found)
0x00143402 in __kernel_vsyscall ()

Thread 1 (Thread -1208781120 (LWP 4447))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 POA_GNOME_Evolution_DataServer_InterfaceCheck__fini
  • #4 <signal handler called>
  • #5 camel_message_info_free
    from /usr/lib/libcamel-provider-1.2.so.8
  • #6 camel_vee_store_new
    from /usr/lib/libcamel-provider-1.2.so.8
  • #7 camel_message_info_free
    from /usr/lib/libcamel-provider-1.2.so.8
  • #8 camel_folder_summary_clear
    from /usr/lib/libcamel-provider-1.2.so.8
  • #9 camel_folder_summary_new
    from /usr/lib/libcamel-provider-1.2.so.8
  • #10 camel_object_unref
    from /usr/lib/libcamel-1.2.so.0
  • #11 camel_folder_construct
    from /usr/lib/libcamel-provider-1.2.so.8
  • #12 camel_object_unref
    from /usr/lib/libcamel-1.2.so.0
  • #13 mail_get_folder
    from /usr/lib/evolution/2.6/components/libevolution-mail.so
  • #14 mail_msg_free
    from /usr/lib/evolution/2.6/components/libevolution-mail.so
  • #15 mail_call_main
    from /usr/lib/evolution/2.6/components/libevolution-mail.so
  • #16 g_io_channel_unix_get_fd
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #20 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #21 POA_GNOME_Evolution_DataServer_InterfaceCheck__fini
  • #22 __libc_start_main
    from /lib/libc.so.6
  • #23 ??




------- Bug created by bug-buddy at 2006-08-10 15:02 -------

Comment 1 Christian Kirbach 2006-08-10 20:42:39 UTC
*** Bug 350757 has been marked as a duplicate of this bug. ***
Comment 2 André Klapper 2006-08-10 22:05:16 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 is very likely the same bug as bug 324168.

*** This bug has been marked as a duplicate of 324168 ***
Comment 3 John.Ata 2006-08-10 22:36:48 UTC
>> This is very likely the same bug as bug 324168

Are you sure?  Bug 324168 (Evolution crashed when disabled configured IMAP account) deals with a disabled configured IMAP server - I never configured an IMAP server.  I am running with the standard Unix mail.

-- John
Comment 4 Christian Kirbach 2006-08-11 09:54:12 UTC
The traces are quite different



Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

please install libcamel package at least
Comment 5 Christian Kirbach 2006-11-15 22:55:35 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 6 John.Ata 2006-11-15 23:25:12 UTC
Sorry folks, I don't have time to debug this by running a special version with symbols - I use my Linux workstation to perform work.  As a result, I don't use evolution that often.  The bug report was submitted for your benefit, not mine. 
Comment 7 Christian Kirbach 2006-11-19 11:34:04 UTC
It is as easy as we can arrange it; running a debug version should not affect your productivity at all, and you may deinstall it afterwards if you wish.
Given the lack of (unpaid) manpower of volunteers we are really happy if users help us improve free software. Besides, we have no instructions on how to trigger the crash. If we could, somebody will produce a detailed trace that will tremendously help fixing the problem.

Thank you for your efforts.
Comment 8 John.Ata 2006-11-28 22:29:48 UTC
(In reply to comment #7)

> Given the lack of (unpaid) manpower of volunteers we are really happy if users
> help us improve free software.

Of course, but my employer doesn't pay me to debug someone else's software - if this was my home computer, it would be a different story.

> Besides, we have no instructions on how to
> trigger the crash. If we could, somebody will produce a detailed trace that
> will tremendously help fixing the problem.
> Thank you for your efforts.

This was right after installing Evolution and using the Exchange mail store for the first time.  I have a very large inbox (over 5K mail items) on the Exchange Server - I think since then, I've I've installed an updated Exchange plugin - maybe that helped... in any case, with my limited use, I haven't duplicated this problem myself in a while.

-- John