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 322037 - Terminal crashed after multiple clicks and selections
Terminal crashed after multiple clicks and selections
Status: RESOLVED DUPLICATE of bug 167202
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-11-21 15:18 UTC by dan.track
Modified: 2005-11-27 12:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8


Description dan.track 2005-11-21 15:19:00 UTC 
Distribution: Red Hat Enterprise Linux WS release 4 (Nahant Update 1)
Package: gnome-terminal
Severity: normal
Version: GNOME2.8.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: Terminal crashed after multiple clicks and selections
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
While right clicking  and selecting and deselecting text in the
terminals (while I was on the phone and bored) the terminal crash window
appeared

Steps to reproduce the crash:
1. highlight and deselect text + right clicking a few times on the same
terminal
2. crash
3. 

Expected Results:
Should not crash

How often does this happen?
Only happened once

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 -1208109376 (LWP 22348)]
[New Thread -1223803984 (LWP 22351)]
(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)
0x005a07a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2

+ Trace 64170

Thread 1 (Thread -1208109376 (LWP 22348))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #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 gtk_widget_set_sensitive
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 terminal_screen_get_text_selected
  • #6 terminal_screen_get_text_selected
  • #7 gtk_marshal_VOID__UINT_STRING
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_has_handler_pending
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #12 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gdk_event_get_graphics_expose
    from /usr/lib/libgdk-x11-2.0.so.0
  • #16 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_context_acquire
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #19 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 main 




------- Bug moved to this database by unknown@gnome.bugs 2005-11-21 15:19 UTC -------


The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@gnome.bugs.
   Previous reporter was dan.track@gmail.com.
Comment 1 Teppo Turtiainen 2005-11-27 12:39:42 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 167202 ***