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 105408 - GNOME-Terminal crash
GNOME-Terminal crash
Status: RESOLVED FIXED
Product: vte
Classification: Core
Component: general
0.10.x
Other other
: High critical
: ---
Assigned To: VTE Maintainers
VTE Maintainers
: 105465 105781 106592 106855 107250 107553 107667 108310 108692 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-02-06 15:37 UTC by benedikt
Modified: 2005-01-06 11:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description benedikt 2003-02-06 15:33:45 UTC
Package: gnome-terminal
Severity: normal
Version: 2.0.1
Synopsis: GNOME-Terminal crash
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:
If I try to start the gnome-terminal (Redhat 8.0 / GNOME 2.0) I get this
Bug

Application "gnome-terminal" (process 1458) has crashed
due to a fatal error.
(Segmentation fault)

so I could only klick "close" or send bug. How I could repair this

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

Actual Results:


Expected Results:


How often does this happen?
Everytime if I want to start GNOME Terminal

Additional Information:
if you know anything benedikt@redhat-faq.de




Debugging Information:

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

(no debugging symbols found)...[New Thread 8192 (LWP 1445)]
0x420ae169 in wait4 () from /lib/i686/libc.so.6

Thread 1 (Thread 8192 (LWP 1445))

  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    from /lib/i686/libpthread.so.0
  • #3 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #4 __pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #5 <signal handler called>
  • #6 vte_terminal_open_font_xft
    from /usr/lib/libvte.so.2
  • #7 vte_terminal_init
    from /usr/lib/libvte.so.2
  • #8 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_object_constructor
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #13 vte_terminal_new
    from /usr/lib/libvte.so.2
  • #14 terminal_widget_new
  • #15 terminal_screen_init
  • #16 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_object_constructor
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #21 terminal_screen_new
  • #22 terminal_app_new_terminal
  • #23 new_terminal_with_options
  • #24 main
  • #25 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 wait4
    from /lib/i686/libc.so.6




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-06 10:33 -------

The original reporter (benedikt@gnome-de.org) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, hp@redhat.com.

Comment 1 Elijah Newren 2003-02-06 15:55:47 UTC
Apparently a unique stack trace.  Setting version->2.0.x, marking
priority->high & severity->critical (it's a crasher), adding
GNOMEVER2.0 and bugsquad keywords and marking as new.
Comment 2 Michael Chan 2003-02-06 17:52:46 UTC
I am experiencing a similar crash.  Output from .xsession-errors:

** (gnome-terminal:1509): WARNING **: Failed to load Xft font pattern
".fulldir-9:slant=0:weight=100:pixelsize=12:antialias=True:hintstyle=2:hinting=True:verticallayout=False:autohint=False:globaladvance=True:dpi=96:rgba=0:scale=1:lang=en-US",
falling back to default font.

** (gnome-terminal:1509): WARNING **: Failed to load default Xft font.
Comment 3 Michael Chan 2003-02-06 18:55:00 UTC
It seems (re?)restoring preferred font selection through preferences:
fonts fixed problem, though I do not know why it "forgot" preferred
font to begin with.
Comment 4 Alex Duggan 2003-02-07 04:16:50 UTC
*** Bug 105465 has been marked as a duplicate of this bug. ***
Comment 5 pajones57 2003-02-07 17:41:57 UTC
Where is gnome-terminal pulling it's font information from?  I've 
deleted everything in the home directory AND changed all the system 
font settings.

I am using gnome-terminal-2.2.0

from .xsession-errors
** (gnome-terminal:22058): WARNING **: Failed to load Xft font 
pattern "Sans 10.000000", falling back to default font.

** (gnome-terminal:22058): WARNING **: Failed to load default Xft 
font.
Comment 6 Elijah Newren 2003-02-11 05:19:29 UTC
*** Bug 105781 has been marked as a duplicate of this bug. ***
Comment 7 John Fleck 2003-02-20 14:22:28 UTC
*** Bug 106592 has been marked as a duplicate of this bug. ***
Comment 8 Paul Jenner 2003-02-22 11:19:48 UTC
See exactly the same crash after running GNOME terminal 2.2.0 (Red Hat
8.1 beta build) then returning to GNOME terminal 2.0.1 (Red hat 8.0
build) on the same machine. I did not manually change settings between
- i.e. any settings change was automatic.
Comment 9 John Fleck 2003-02-23 15:51:42 UTC
*** Bug 106855 has been marked as a duplicate of this bug. ***
Comment 10 Owen Taylor 2003-02-24 13:49:26 UTC
Note that Michael Chan and Paul Jenner's problem 
(https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=84863)
may not be related to pajone's problems, or the bugs marked
as duplicates. Any sort of font system problem that causes
a complete failure to load a font will cause a crash here.

Reassigning to vte, though there's not all that much
that can be done. Actually, it looks like vte might not
segfault in this circumstance any more, though without
symbols on the backtraces, it's hard to tell.
Comment 11 Elijah Newren 2003-02-28 15:53:57 UTC
*** Bug 107250 has been marked as a duplicate of this bug. ***
Comment 12 Elijah Newren 2003-03-04 16:04:39 UTC
*** Bug 107553 has been marked as a duplicate of this bug. ***
Comment 13 Elijah Newren 2003-03-05 20:20:54 UTC
*** Bug 107667 has been marked as a duplicate of this bug. ***
Comment 14 John Fleck 2003-03-14 14:41:51 UTC
*** Bug 108310 has been marked as a duplicate of this bug. ***
Comment 15 Elijah Newren 2003-03-18 19:26:42 UTC
*** Bug 108692 has been marked as a duplicate of this bug. ***
Comment 16 Kjartan Maraas 2005-01-06 11:57:36 UTC
No duplicates in almost a year. Closing as fixed.