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 170177 - terminal crash with selected text in the terminal
terminal crash with selected text in the terminal
Status: RESOLVED DUPLICATE of bug 162433
Product: gnome-terminal
Classification: Core
Component: general
2.8.x
Other Linux
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-03-13 13:33 UTC by loott33
Modified: 2005-03-13 21:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8


Description loott33 2005-03-13 13:33:26 UTC 
Distribution: Fedora Core release 3 (Heidelberg)
Package: gnome-terminal
Severity: major
Version: GNOME2.8.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: terminal crash with selected text in the terminal
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
The terminal crashed when i selected text with the mouse and i think i
pressed a key (i don't know which) 

Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?
rarely

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 -151181088 (LWP 3868)]
[New Thread -157639760 (LWP 3871)]
[Thread debugging using libthread_db enabled]
[New Thread -151181088 (LWP 3868)]
[New Thread -157639760 (LWP 3871)]
[Thread debugging using libthread_db enabled]
[New Thread -151181088 (LWP 3868)]
[New Thread -157639760 (LWP 3871)]
(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)...0x0020d7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2

+ Trace 56792

Thread 1 (Thread -151181088 (LWP 3868))

  • #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 strcmp
    from /lib/tls/libc.so.6
  • #5 vte_terminal_get_text_range
    from /usr/lib/libvte.so.4
  • #6 g_main_context_wakeup
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_acquire
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #10 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 main 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-13 08:33 -------


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 loott33@hotmail.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 Yaron Tausky 2005-03-13 21:31:24 UTC 
Thanks for the bug report. Unfortunately, that stack trace is not very useful in
determining the cause of the crash. Please make sure that the package was
compiled with debugging symbols and see
http://bugzilla.gnome.org/getting-traces.cgi for more information about useful
stack traces.
Comment 2 Yaron Tausky 2005-03-13 21:57:03 UTC 

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