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 360220 - crash in Evolution: I closed the main window...
crash in Evolution: I closed the main window...
Status: RESOLVED DUPLICATE of bug 334966
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: 2006-10-06 16:59 UTC by barrera
Modified: 2006-10-06 23:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description barrera 2006-10-06 16:59:41 UTC
What were you doing when the application crashed?
I closed the main window and the program crushed. This happens sometimes but I haven't been able to trace exactly when it does happend. 


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

Memory status: size: 58892288 vsize: 0 resident: 253685760 share: 0 rss: 253685760 rss_rlim: 0
CPU usage: start_time: 9736 rtime: 0 utime: 1160153047 stime: 0 cutime:13459 cstime: 0 timeout: 12843 it_real_value: 0 frequency: 616

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

(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 805590304 (LWP 17670)]
[New Thread 933426416 (LWP 17974)]
[New Thread 933692656 (LWP 17695)]
[New Thread 924435696 (LWP 17681)]
[New Thread 916042992 (LWP 17678)]
[New Thread 870147312 (LWP 17676)]
[New Thread 861742320 (LWP 17675)]
[New Thread 852960496 (LWP 17673)]
0x0ea20220 in __waitpid_nocancel () from /lib/libc.so.6

Thread 8 (Thread 852960496 (LWP 17673))

  • #0 ___newselect_nocancel
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 start_thread
    from /lib/libpthread.so.0

Thread 7 (Thread 861742320 (LWP 17675))

  • #0 ___newselect_nocancel
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 start_thread
    from /lib/libpthread.so.0

Thread 6 (Thread 870147312 (LWP 17676))

  • #0 ___newselect_nocancel
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 start_thread
    from /lib/libpthread.so.0

Thread 5 (Thread 916042992 (LWP 17678))

  • #0 ___newselect_nocancel
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 start_thread
    from /lib/libpthread.so.0

Thread 4 (Thread 924435696 (LWP 17681))

  • #0 ___newselect_nocancel
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 start_thread
    from /lib/libpthread.so.0

Comment 1 Karsten Bräckelmann 2006-10-06 17:21:25 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 barrera 2006-10-06 17:33:03 UTC
After install the symbols, I opened evolution several times, change from one folder to another and quit. After some tries evolution crashed again. The new bug-buddy traces are:

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

Memory status: size: 42180608 vsize: 0 resident: 182661120 share: 0 rss: 182661120 rss_rlim: 0
CPU usage: start_time: 756 rtime: 0 utime: 1160155697 stime: 0 cutime:593 cstime: 0 timeout: 567 it_real_value: 0 frequency: 26

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 805590304 (LWP 5871)]
[New Thread 924443888 (LWP 5881)]
[New Thread 861754608 (LWP 5880)]
[New Thread 878535920 (LWP 5876)]
[New Thread 870147312 (LWP 5875)]
[New Thread 852960496 (LWP 5873)]
0x0ea20220 in __waitpid_nocancel () from /lib/libc.so.6

Thread 1 (Thread 805590304 (LWP 5871))

  • #0 __waitpid_nocancel
    from /lib/libc.so.6
  • #1 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 segv_redirect
    at main.c line 426
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/libc.so.6
  • #5 e_shell_window_set_title
    at e-shell-window.c line 1240
  • #6 impl_ShellView_setTitle
    at e-shell-view.c line 48
  • #7 _ORBIT_skel_small_GNOME_Evolution_ShellView_setTitle
    at Evolution-common.c line 24
  • #8 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #9 GNOME_Evolution_ShellView_setTitle
    at Evolution-stubs.c line 27
  • #10 e_component_view_set_title
    at e-component-view.c line 136
  • #11 view_changed_timeout
    at mail-component.c line 582
  • #12 g_source_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #16 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #17 main
    at main.c line 615
  • #0 __waitpid_nocancel
    from /lib/libc.so.6


HTH
Comment 3 Karsten Bräckelmann 2006-10-06 23:33:51 UTC
Thanks for your efforts and the good stacktrace, barrera. :)

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 334966 ***