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 395730 - crash in Evolution: trying to reload after a...
crash in Evolution: trying to reload after a...
Status: RESOLVED DUPLICATE of bug 363576
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-01-12 10:31 UTC by eric
Modified: 2007-01-27 21:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description eric 2007-01-12 10:31:13 UTC
What were you doing when the application crashed?
trying to reload after a previous crash.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 101564416 vsize: 0 resident: 101564416 share: 0 rss: 26140672 rss_rlim: 0
CPU usage: start_time: 1168597843 rtime: 0 utime: 231 stime: 0 cutime:214 cstime: 0 timeout: 17 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233254736 (LWP 5699)]
[New Thread -1301922912 (LWP 5711)]
[New Thread -1260495968 (LWP 5710)]
[New Thread -1279263840 (LWP 5707)]
[New Thread -1268925536 (LWP 5706)]
[New Thread -1252103264 (LWP 5703)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1233254736 (LWP 5699))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libc.so.6
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 874
  • #3 main
  • #0 __kernel_vsyscall

Comment 1 palfrey 2007-01-12 22:16:59 UTC
Thanks for taking the time to report this bug.
Unfortunately, that 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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 eric 2007-01-13 00:45:00 UTC
I renamed the Evolution data directory with my email from .evolution to evolution-old, then rebooted Evolution and that resolved the problem. I used the Import function to pull in the old email from the evolution-old directory structure with no problem and have not had a crash since then.

My email account had reached its quota on my host's mail server. I don't know if that related to the crash.

I'll try to get a trace. I still have the original directory structure untouched and can mess with the names to reproduce the problem.

Eric
Comment 3 eric 2007-01-14 20:37:40 UTC
I installed debug symbols for Evolution and gtk, etc. I hope I've got it all. Please let me know if there is more you need.

The new trace is below.

Eric 

Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 111947776 vsize: 0 resident: 111947776 share: 0 rss: 27668480 rss_rlim: 0
CPU usage: start_time: 1168806804 rtime: 0 utime: 387 stime: 0 cutime:345 cstime: 0 timeout: 42 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233234256 (LWP 25502)]
[New Thread -1301644384 (LWP 25519)]
[New Thread -1260479584 (LWP 25518)]
[New Thread -1279263840 (LWP 25514)]
[New Thread -1268876384 (LWP 25513)]
[New Thread -1252050016 (LWP 25510)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1233234256 (LWP 25502))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libc.so.6
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 874
  • #3 segv_redirect
    at main.c line 426
  • #4 <signal handler called>
  • #5 IA__g_main_context_check
    at gmain.c line 2523
  • #6 g_main_context_iterate
    at gmain.c line 2674
  • #7 IA__g_main_loop_run
    at gmain.c line 2881
  • #8 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #9 main
    at main.c line 615
  • #0 __kernel_vsyscall

Comment 4 Christian Kirbach 2007-01-27 21:59:07 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 363576 ***