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 355538 - crash in Evolution: Closing the application
crash in Evolution: Closing the application
Status: RESOLVED DUPLICATE of bug 334966
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Harish Krishnaswamy
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-09-12 06:52 UTC by Hidde Brugmans
Modified: 2006-09-15 12:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Hidde Brugmans 2006-09-12 06:52:04 UTC
What were you doing when the application crashed?
Closing the application


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 117325824 vsize: 0 resident: 117325824 share: 0 rss: 27869184 rss_rlim: 0
CPU usage: start_time: 1158043804 rtime: 0 utime: 553 stime: 0 cutime:519 cstime: 0 timeout: 34 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 -1232492880 (LWP 22050)]
[New Thread -1307681888 (LWP 22087)]
[New Thread -1299289184 (LWP 22063)]
[New Thread -1290896480 (LWP 22062)]
[New Thread -1259603040 (LWP 22057)]
[New Thread -1251165280 (LWP 22055)]
0xffffe410 in __kernel_vsyscall ()

Comment 1 André Klapper 2006-09-12 09:32:32 UTC
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.
Comment 2 Hidde Brugmans 2006-09-13 16:33:45 UTC
I got this after installing the evo-dbg packages on ubuntu-edgy, hope it helps:

Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 130023424 vsize: 0 resident: 130023424 share: 0 rss: 31133696 rss_rlim: 0
CPU usage: start_time: 1158163971 rtime: 0 utime: 1114 stime: 0 cutime:846 cstime: 0 timeout: 268 it_real_value: 0 frequency: 7

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 -1232083280 (LWP 5373)]
[New Thread -1316533344 (LWP 5793)]
[New Thread -1308140640 (LWP 5790)]
[New Thread -1298834528 (LWP 5388)]
[New Thread -1290441824 (LWP 5385)]
[New Thread -1267954784 (LWP 5384)]
[New Thread -1259168864 (LWP 5381)]
[New Thread -1250735200 (LWP 5379)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1232083280 (LWP 5373))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libc.so.6
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 segv_redirect
    at main.c line 426
  • #4 <signal handler called>
  • #5 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #6 e_shell_window_set_title
    at e-shell-window.c line 1223
  • #7 impl_ShellView_setTitle
    at e-shell-view.c line 48
  • #8 _ORBIT_skel_small_GNOME_Evolution_ShellView_setTitle
    at Evolution-common.c line 24
  • #9 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #10 GNOME_Evolution_ShellView_setTitle
    at Evolution-stubs.c line 27
  • #11 e_component_view_set_title
    at e-component-view.c line 136
  • #12 view_changed_timeout
    at mail-component.c line 582
  • #13 g_timeout_dispatch
    at gmain.c line 3422
  • #14 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #15 g_main_context_iterate
    at gmain.c line 2677
  • #16 IA__g_main_loop_run
    at gmain.c line 2881
  • #17 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #18 main
    at main.c line 615
  • #0 __kernel_vsyscall

Comment 3 Karsten Bräckelmann 2006-09-15 12:21:59 UTC
Thanks for the debugging symbols, Hidde. :)


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