Bug 150324 – when vim the terminal crashes

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 150324 - when vim the terminal crashes


Summary:	when vim the terminal crashes


Status:	RESOLVED DUPLICATE of bug 139542

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2004-08-17 05:42 UTC by john.chen
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	2.5/2.6

Description john.chen 2004-08-17 05:41:10 UTC

Distribution: Fedora Core release 2 (Tettnang)
Package: gnome-terminal
Severity: blocker
Version: GNOME2.6. unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: when vim the terminal crashes
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:

when using vim, the terminal crashes

Steps to reproduce the crash:
1. open the terminal
2. ssh to a remote machine
3.  type vi

Expected Results:

crash
How often does this happen?

almost 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)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...[Thread debugging using libthread_db enabled]
[New Thread -151035776 (LWP 4302)]
(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)...0x00a4d402 in ?? ()

+ Trace 49385

Thread 1 (Thread -151035776 (LWP 4302))

#0 ??
#1 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
#5 raise
from /lib/tls/libc.so.6
#6 abort
from /lib/tls/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_string_erase
from /usr/lib/libglib-2.0.so.0
#10 _g_log_fallback_handler
from /usr/lib/libglib-2.0.so.0
#11 g_log_default_handler
from /usr/lib/libglib-2.0.so.0
#12 g_logv
from /usr/lib/libglib-2.0.so.0
#13 g_log
from /usr/lib/libglib-2.0.so.0
#14 vte_terminal_set_default_colors
from /usr/lib/libvte.so.4
#15 vte_terminal_fork_command
from /usr/lib/libvte.so.4
#16 g_main_context_wakeup
from /usr/lib/libglib-2.0.so.0
#17 g_main_depth
from /usr/lib/libglib-2.0.so.0
#18 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#19 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#20 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#21 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#22 main
#0 ??





------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-08-17 01:41 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-terminal".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was john.chen@net263.com.
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 Vincent Noel 2004-09-21 15:12:53 UTC

Marking as a dup of bug 139542 via bug 146217.

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