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 140761 - Gnome Terminal crashed while "cat"ing gzipped file
Gnome Terminal crashed while "cat"ing gzipped file
Status: RESOLVED DUPLICATE of bug 107262
Product: gnome-terminal
Classification: Core
Component: general
2.4.x
Other other
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-04-04 06:25 UTC by Derek Chen-Becker
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4


Description Derek Chen-Becker 2004-04-21 18:31:25 UTC 
Distribution: Red Hat Linux release 9 (Shrike)
Package: gnome-terminal
Severity: major
Version: GNOME2.4.0 2.4.x
Gnome-Distributor: GNOME.Org
Synopsis: Gnome Terminal crashed while "cat"ing gzipped file
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Bugzilla-Version: 2.4.x
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:
I downloaded an html file from the web that turned out to be gzipped. I
didn't realize it and when I "cat"ed the file, gnome-terminal crashed

Steps to reproduce the crash:
1. I can't reproduce it. I have tried "cat"ing the file again and again
and it won't crash.

Expected Results:
Not crashing :)

How often does this happen?
Once, so far.



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 -1084943712 (LWP 15494)]

(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)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...0x00f0ec32 in _dl_sysinfo_int80 ()
   from /lib/ld-linux.so.2

+ Trace 46267

Thread 1 (Thread -1084943712 (LWP 15494))

  • #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 pango_layout_iter_get_char_extents
    from /usr/lib/libpango-1.0.so.0
  • #5 eel_pango_layout_set_font_desc_from_string
  • #6 eel_pango_layout_set_font_desc_from_string
  • #7 eel_pango_layout_set_text_ellipsized
  • #8 eel_ellipsizing_label_set_text
  • #9 g_cclosure_marshal_VOID__BOXED
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-04-22 04:31 -------


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 bugs@chen-becker.org.
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 Mariano Suárez-Alvarez 2004-04-22 00:15:20 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 107262 ***