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 326319 - terminal window crashes after 1 or 2 minutes
terminal window crashes after 1 or 2 minutes
Status: RESOLVED DUPLICATE of bug 157945
Product: vte
Classification: Core
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-01-09 16:35 UTC by vince.van
Modified: 2006-01-09 17:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description vince.van 2006-01-09 16:35:23 UTC
Distribution: Debian 3.1
Package: gnome-terminal
Severity: normal
Version: GNOME2.8.3 2.8.2
Gnome-Distributor: Debian
Synopsis: terminal window crashes after 1 or 2 minutes
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Bugzilla-Version: 2.8.2
BugBuddy-GnomeVersion: 2.0 (2.8.1)
Description:
Description of the crash:


Steps to reproduce the crash:
1. open terminal
2. su
3. do some operation

Expected Results:


How often does this happen?
every time

Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1088848864 (LWP 13475)]
[New Thread 1105918896 (LWP 13478)]
(no debugging symbols found)
0x407c7561 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

Thread 1 (Thread 1088848864 (LWP 13475))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 re_exec
    from /lib/tls/libc.so.6
  • #4 re_exec
    from /lib/tls/libc.so.6
  • #5 re_exec
    from /lib/tls/libc.so.6
  • #6 re_exec
    from /lib/tls/libc.so.6
  • #7 re_exec
    from /lib/tls/libc.so.6
  • #8 re_exec
    from /lib/tls/libc.so.6
  • #9 regexec
    from /lib/tls/libc.so.6
  • #10 _vte_regex_exec
    from /usr/lib/libvte.so.4
  • #11 vte_terminal_match_set_cursor_type
    from /usr/lib/libvte.so.4
  • #12 vte_terminal_is_word_char
    from /usr/lib/libvte.so.4
  • #13 vte_terminal_get_cursor_position
    from /usr/lib/libvte.so.4
  • #14 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #20 gtk_widget_send_expose
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #24 g_main_depth
    from /usr/lib/libglib-2.0.so.0
  • #25 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #26 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #27 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #28 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 main
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0




------- Bug created by bug-buddy at 2006-01-09 16:35 -------


Unknown version 2.8.2 in product gnome-terminal.  Setting version to "2.8.x".

Comment 1 Guilherme de Siqueira Pastore 2006-01-09 16:39:16 UTC
This belongs in VTE. Reassigning.
Comment 2 Guilherme de Siqueira Pastore 2006-01-09 16:42:02 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.

Also, could you please try that on a possibly more up-to-date environment, such as Debian unstable or CVS HEAD?

Thanks.
Comment 3 Michele Baldessari 2006-01-09 16:47:11 UTC

*** This bug has been marked as a duplicate of 157945 ***
Comment 4 Guilherme de Siqueira Pastore 2006-01-09 17:06:12 UTC
OK, no need to provide anything, I already know what this is. Thanks anyway.