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 123656 - gnome-terminal crashed when typing in window
gnome-terminal crashed when typing in window
Status: RESOLVED DUPLICATE of bug 121735
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-10-01 19:40 UTC by tami
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description tami 2003-10-01 19:40:35 UTC 
Package: gnome-terminal
Severity: normal
Version: 2.2.1
Synopsis: gnome-terminal crashed when typing in window
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
The gnome-terminal crashed when I was simply typing a command in the
window. The following programs were running: xemacs, 2 terminal windows,
CD player.

Steps to reproduce the problem:
1. I'm don't know
2. 
3. 

Actual Results:
Terminal window is still visible on the screen, but crashed. Second
terminal window is also crashed.


Expected Results:


How often does this happen?
This is the second time this has happened - once yesterday and now
today. Similar configuration yesterday except only one terminal window
open.

Additional Information:




Debugging Information:

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

(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)...[New
Thread 1087417344 (LWP 1399)]
0xffffe002 in ??
    ()

+ Trace 40570

Thread 1 (Thread 1087417344 (LWP 1399))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gtk_widget_get_toplevel
    from /usr/lib/libgtk-x11-2.0.so.0
  • #4 gtk_false
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main
  • #13 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ?? 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-10-01 15:40 -------

Reassigning to the default owner of the component, gnome-terminal-maint@bugzilla.gnome.org.
Comment 1 Mariano Suárez-Alvarez 2003-10-01 20:37:40 UTC 
You need to update GTK+ to 2.2.3.

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