Bug 425768 – Crashed for no apparent reason

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 425768 - Crashed for no apparent reason


Summary:	Crashed for no apparent reason


Status:	RESOLVED DUPLICATE of bug 157945

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	2.8.x
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	GNOME Terminal Maintainers
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-04-03 07:38 UTC by robi-enh
Modified:	2007-04-26 17:26 UTC

See Also:
GNOME target:	---
GNOME version:	2.7/2.8

Description robi-enh 2007-04-03 07:38:49 UTC

Distribution: Debian 3.1
Package: gnome-terminal
Severity: normal
Version: GNOME2.8.3 2.8.2
Gnome-Distributor: Debian
Synopsis: Crashed for no apparent reason
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Bugzilla-Version: 2.8.2
BugBuddy-GnomeVersion: 2.0 (2.8.1)
Description:
Description of the crash:
Terminal exits

Steps to reproduce the crash:
1. started pico
2. did nothing

Expected Results:
That I still be in the terminal

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/i686/cmov/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 -1493088096 (LWP 6825)]
[New Thread -1499882576 (LWP 6828)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 124546

Thread 1 (Thread -1493088096 (LWP 6825))

#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 re_exec
from /lib/tls/i686/cmov/libc.so.6
#5 re_exec
from /lib/tls/i686/cmov/libc.so.6
#6 re_exec
from /lib/tls/i686/cmov/libc.so.6
#7 re_exec
from /lib/tls/i686/cmov/libc.so.6
#8 re_exec
from /lib/tls/i686/cmov/libc.so.6
#9 re_exec
from /lib/tls/i686/cmov/libc.so.6
#10 regexec
from /lib/tls/i686/cmov/libc.so.6
#11 _vte_regex_exec
from /usr/lib/libvte.so.4
#12 vte_terminal_match_set_cursor_type
from /usr/lib/libvte.so.4
#13 vte_terminal_is_word_char
from /usr/lib/libvte.so.4
#14 vte_terminal_get_cursor_position
from /usr/lib/libvte.so.4
#15 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#16 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_by_name
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#21 gtk_widget_send_expose
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#24 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#25 g_main_depth
from /usr/lib/libglib-2.0.so.0
#26 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#27 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#28 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#29 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#30 main
#0 __kernel_vsyscall





------- Bug created by bug-buddy at 2007-04-03 07:38 -------


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

Comment 1 palfrey 2007-04-26 17:26:22 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 157945 ***