Bug 107864 – gnome-terminal suffered a fatal error (/abort)

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 107864 - gnome-terminal suffered a fatal error (/abort)


Summary:	gnome-terminal suffered a fatal error (/abort)


Status:	RESOLVED DUPLICATE of bug 94509

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other other

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Havoc Pennington
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-03-08 09:07 UTC by Gerry
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Gerry 2003-03-08 09:07:26 UTC

Package: gnome-terminal
Severity: major
Version: 2.0.1
Synopsis: gnome-terminal suffered a fatal error (/abort)
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:
gnome-terminal aborted while reading <man 8 mount>

Steps to reproduce the problem:
1. Open terminal
2. Open manual
3. page down two or three times.

Actual Results:
terminal program aborts, error message as described in Summary

Expected Results:
continue paging down to read.

How often does this happen?
nearly every time

Additional Information:
Backtrace was generated from '/usr/bin/gnome-terminal'

(no debugging symbols found)...[New Thread 8192 (LWP 4502)]
0x420ae169 in wait4 () from /lib/i686/libc.so.6

+ Trace 34656

Thread 1 (Thread 8192 (LWP 4502))

#0 wait4
from /lib/i686/libc.so.6
#1 __DTOR_END__
from /lib/i686/libc.so.6
#2 waitpid
from /lib/i686/libpthread.so.0
#3 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#4 __pthread_sighandler
from /lib/i686/libpthread.so.0
#5 <signal handler called>
#6 kill
from /lib/i686/libc.so.6
#7 raise
from /lib/i686/libpthread.so.0
#8 abort
from /lib/i686/libc.so.6
#9 g_logv
from /usr/lib/libglib-2.0.so.0
#10 g_log
from /usr/lib/libglib-2.0.so.0
#11 vte_terminal_ensure_cursor
from /usr/lib/libvte.so.2
#12 vte_sequence_handler_ce
from /usr/lib/libvte.so.2
#13 vte_terminal_handle_sequence
from /usr/lib/libvte.so.2
#14 vte_terminal_process_incoming
from /usr/lib/libvte.so.2
#15 g_idle_dispatch
from /usr/lib/libglib-2.0.so.0
#16 g_main_dispatch
from /usr/lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#18 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#19 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#20 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#21 main
#22 __libc_start_main
from /lib/i686/libc.so.6
#0 wait4
from /lib/i686/libc.so.6
#0 wait4
from /lib/i686/libc.so.6
#1 __DTOR_END__
from /lib/i686/libc.so.6
#2 waitpid
from /lib/i686/libpthread.so.0
#3 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#4 __pthread_sighandler
from /lib/i686/libpthread.so.0
#5 <signal handler called>
#6 kill
from /lib/i686/libc.so.6
#7 raise
from /lib/i686/libpthread.so.0
#8 abort
from /lib/i686/libc.so.6
#9 g_logv
from /usr/lib/libglib-2.0.so.0
#10 g_log
from /usr/lib/libglib-2.0.so.0
#11 vte_terminal_ensure_cursor
from /usr/lib/libvte.so.2
#12 vte_sequence_handler_ce
from /usr/lib/libvte.so.2
#13 vte_terminal_handle_sequence
from /usr/lib/libvte.so.2
#14 vte_terminal_process_incoming
from /usr/lib/libvte.so.2
#15 g_idle_dispatch
from /usr/lib/libglib-2.0.so.0
#16 g_main_dispatch
from /usr/lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#18 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#19 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#20 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#21 main
#22 __libc_start_main
from /lib/i686/libc.so.6





------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-03-08 04:07 -------

Reassigning to the default owner of the component, hp@redhat.com.

Comment 1 Elijah Newren 2003-03-08 15:33:03 UTC


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