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 158238 - gnome-terminal crash when using gnopernicus
gnome-terminal crash when using gnopernicus
Status: RESOLVED DUPLICATE of bug 389538
Product: vte
Classification: Core
Component: general
0.10.x
Other other
: Normal normal
: ---
Assigned To: VTE Maintainers
VTE Maintainers
AP1
Depends on:
Blocks:
 
 
Reported: 2004-11-14 02:32 UTC by John Spray
Modified: 2007-01-22 17:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description John Spray 2004-11-14 02:33:17 UTC
Distribution: Debian testing/unstable
Package: gnome-terminal
Severity: normal
Version: GNOME2.8.1 2.7.3
Gnome-Distributor: Ubuntu
Synopsis: gnome-terminal crash when using gnopernicus
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Bugzilla-Version: 2.7.3
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
Had just activated gnopernicus, logged out+in, opened a gnome-terminal. 
Started checking something out of cvs, and in the middle of listing the
files as they were checked out, this crash happened.  Wasn't pressing
any keys at time of crash, just watching output.


How often does this happen?
This is a one-off, I haven't tried reproducing it.


Debugging Information:

Backtrace was generated from '/usr/bin/gnome-terminal'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...[Thread debugging using
libthread_db enabled]
[New Thread 1088326240 (LWP 22392)]
[New Thread 1119255472 (LWP 22399)]
[Thread debugging using libthread_db enabled]
[New Thread 1088326240 (LWP 22392)]
[New Thread 1119255472 (LWP 22399)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...[Thread debugging using libthread_db enabled]
[New Thread 1088326240 (LWP 22392)]
[New Thread 1119255472 (LWP 22399)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...0xffffe410 in __kernel_vsyscall
()

Thread 1 (Thread 1088326240 (LWP 22392))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 memcpy
    from /lib/tls/i686/cmov/libc.so.6
  • #5 vte_terminal_accessible_new
    from /usr/lib/libvte.so.4
  • #6 atk_text_get_text
    from /usr/lib/libatk-1.0.so.0
  • #7 spi_table_get_type
    from /usr/lib/libspi.so.0
  • #8 _ORBIT_skel_small_Accessibility_Text_getText
    from /usr/lib/libspi.so.0
  • #9 ORBit_POA_setup_root
    from /usr/lib/libORBit-2.so.0
  • #10 ORBit_OAObject_invoke
    from /usr/lib/libORBit-2.so.0
  • #11 ORBit_small_invoke_adaptor
    from /usr/lib/libORBit-2.so.0
  • #12 ORBit_recv_buffer_return_sys_exception
    from /usr/lib/libORBit-2.so.0
  • #13 ORBit_recv_buffer_return_sys_exception
    from /usr/lib/libORBit-2.so.0
  • #14 ORBit_recv_buffer_return_sys_exception
    from /usr/lib/libORBit-2.so.0
  • #15 ORBit_handle_request
    from /usr/lib/libORBit-2.so.0
  • #16 giop_connection_handle_input
    from /usr/lib/libORBit-2.so.0
  • #17 link_connection_set_max_buffer
    from /usr/lib/libORBit-2.so.0
  • #18 link_servers_move_io_T
    from /usr/lib/libORBit-2.so.0
  • #19 g_main_depth
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #21 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #22 g_main_context_iteration
    from /usr/lib/libglib-2.0.so.0
  • #23 link_main_iteration
    from /usr/lib/libORBit-2.so.0
  • #24 giop_recv_buffer_get
    from /usr/lib/libORBit-2.so.0
  • #25 ORBit_small_invoke_stub
    from /usr/lib/libORBit-2.so.0
  • #26 ORBit_small_invoke_stub_n
    from /usr/lib/libORBit-2.so.0
  • #27 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #28 Accessibility_EventListener_notifyEvent
    from /usr/lib/libspi.so.0
  • #29 gnome_accessibility_module_shutdown
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #30 gnome_accessibility_module_shutdown
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #31 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #33 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #34 _vte_terminal_accessible_ref
    from /usr/lib/libvte.so.4
  • #35 _vte_terminal_accessible_ref
    from /usr/lib/libvte.so.4
  • #36 _vte_terminal_accessible_ref
    from /usr/lib/libvte.so.4
  • #37 g_cclosure_marshal_VOID
    from /usr/lib/libgobject-2.0.so.0
  • #38 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #39 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #40 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #41 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #42 _vte_trie_print
    from /usr/lib/libvte.so.4
  • #43 vte_terminal_set_size
    from /usr/lib/libvte.so.4
  • #44 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #45 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #46 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #47 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #48 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #49 gtk_adjustment_value_changed
    from /usr/lib/libgtk-x11-2.0.so.0
  • #50 gtk_adjustment_set_value
    from /usr/lib/libgtk-x11-2.0.so.0
  • #51 vte_terminal_match_check
    from /usr/lib/libvte.so.4
  • #52 vte_terminal_forkpty
    from /usr/lib/libvte.so.4
  • #53 g_main_context_wakeup
    from /usr/lib/libglib-2.0.so.0
  • #54 g_main_depth
    from /usr/lib/libglib-2.0.so.0
  • #55 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #56 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #57 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #58 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #59 main
  • #0 __kernel_vsyscall




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-13 21:33 -------


Unknown version 2.7.3 in product gnome-terminal.  Setting version to "2.7.x".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-terminal".
   Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Mariano Suárez-Alvarez 2004-11-14 21:22:38 UTC
this is vte's a11y. Moving...
Comment 2 padraig.obriain 2004-11-15 08:50:03 UTC
I assume that you are using vte 0.11.11.

I would like to know whether this problem occurs with patches for bugs #113590,
#153415 and #156161 applied.

This is probably a duplicate of bug #153415.
Comment 3 bill.haneman 2005-03-01 12:12:54 UTC
I believe Padraig meant bug 153405 instead of 153415 above.
Comment 4 Calum Benson 2006-04-26 17:50:59 UTC
Apologies for spam... marking as AP1 to reflect accessibility impact.
Comment 5 André Klapper 2006-09-29 19:42:41 UTC
guys, any news on this?
john, do you still face this issue nowadays? if so, which version are you running?
Comment 6 John Spray 2006-10-01 11:23:09 UTC
Have tried to reproduce with gnopernicus 1.1.2-0ubuntu1 and libvte 0.14.0-0ubuntu,  by starting gnome-terminal and doing "ls -R /", it does not crash.  This seems pretty old, so I'd go ahead and close it.
Comment 7 Chris Wilson 2007-01-22 17:02:08 UTC
I *think* this a dup of Bug 389538. Those incomplete stack traces make it impossible to be sure... But with the accessibility_get_text() and the severe bug occassionally hit there...

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