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 156627 - impossible to launch gnome-terminal for unknown reasons
impossible to launch gnome-terminal for unknown reasons
Status: RESOLVED NOTGNOME
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-10-27 19:39 UTC by yirkoon
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description yirkoon 2004-10-27 19:32:40 UTC
Distribution: Fedora Core release 2 (Tettnang)
Package: gnome-terminal
Severity: blocker
Version: GNOME2.6. unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: impossible to launch gnome-terminal for unknown reasons
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.6.0)
Description:
Description of the crash:


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

Expected Results:
launch terminal window

How often does this happen?
always

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 -151132320 (LWP 3952)]
(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)...0x003bd7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2

Thread 1 (Thread -151132320 (LWP 3952))

  • #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 ??
  • #5 FcConfigParseAndLoad
    from /usr/lib/libfontconfig.so.1
  • #6 FcInitLoadConfig
    from /usr/lib/libfontconfig.so.1
  • #7 FcInitLoadConfigAndFonts
    from /usr/lib/libfontconfig.so.1
  • #8 FcInit
    from /usr/lib/libfontconfig.so.1
  • #9 FcConfigGetCurrent
    from /usr/lib/libfontconfig.so.1
  • #10 FcConfigSubstituteWithPat
    from /usr/lib/libfontconfig.so.1
  • #11 FcConfigSubstitute
    from /usr/lib/libfontconfig.so.1
  • #12 _vte_fc_patterns_from_pango_font_desc
    from /usr/lib/libvte.so.4
  • #13 _vte_termcap_find_string_length
    from /usr/lib/libvte.so.4
  • #14 _vte_termcap_find_string_length
    from /usr/lib/libvte.so.4
  • #15 _vte_draw_set_text_font
    from /usr/lib/libvte.so.4
  • #16 vte_terminal_set_font
    from /usr/lib/libvte.so.4
  • #17 vte_terminal_get_emulation
    from /usr/lib/libvte.so.4
  • #18 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #23 vte_terminal_new
    from /usr/lib/libvte.so.4
  • #24 terminal_widget_new
  • #25 terminal_screen_get_type
  • #26 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #31 terminal_screen_new
  • #32 terminal_app_new_terminal
  • #33 terminal_skey_do_popup
  • #34 main
  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-10-27 15:32 -------


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 yirkoon@free.fr.
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-10-31 22:11:20 UTC
This happened deep inside fontconfig, which is odd. Can you try
updating/reinstalling the fontconfig you are using, and or try to get a full
stack trace for this crash---instructions on how to do that (you'll need to use
gdb) can be found at http://bugzilla.gnome.org/getting-traces.cgi

This is in the spirit of bug 122088...
Comment 2 Joachim Sauer 2004-11-12 13:14:55 UTC
simple dupe finder lead me here and I believe this is the same bug. I'm running
Fedora Core 3 and nothing self-compiled.

Version information of things I see in the stacktrace are:

gnome-terminal 2.7.3-1
fontconfig-2.2.3-5
libxml2 2.6.16-3
vte 0.11.11-6
glib2 2.4.7-1.1


I can reproduce it easily but I'm afraid I can't tell what caused this. Earlier
today everything worked. I didn't update any gnome/fontconfig/gtk related stuff
during that time (only iptables was updated by yum).

Initially only gnome-terminal failed to start but now not a single gnome program
runs (other gtk2 programs like Firefox & gaim run just fine).

I assume that this is not a problem in gnome-terminal but somewhere in the
libraries (be it the gnome libs, fontconfig or even libxml2 ...) but I can't
reassign this.

Thread 1 (Thread 182894218688 (LWP 3711))

  • #0 convbuf.0
    from /usr/lib64/libxml2.so.2
  • #1 FcConfigParseAndLoad
    at fcxml.c line 1898
  • #2 FcInitLoadConfig
    at fcinit.c line 64
  • #3 FcInitLoadConfigAndFonts
    at fcinit.c line 79
  • #4 FcInit
    at fcinit.c line 101
  • #5 FcConfigGetCurrent
    at fccfg.c line 271
  • #6 FcConfigSubstituteWithPat
    at fccfg.c line 1168
  • #7 _vte_fc_patterns_from_pango_font_desc
    from /usr/lib64/libvte.so.4
  • #8 _vte_termcap_find_string_length
    from /usr/lib64/libvte.so.4
  • #9 vte_terminal_set_font_full
    from /usr/lib64/libvte.so.4
  • #10 vte_terminal_set_font_full
    from /usr/lib64/libvte.so.4
  • #11 g_type_create_instance
    from /usr/lib64/libgobject-2.0.so.0
  • #12 g_object_new_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #13 g_object_newv
    from /usr/lib64/libgobject-2.0.so.0
  • #14 g_object_new_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #15 g_object_new
    from /usr/lib64/libgobject-2.0.so.0
  • #16 vte_terminal_new
    from /usr/lib64/libvte.so.4
  • #17 terminal_widget_new
  • #18 terminal_screen_edit_title
  • #19 g_type_create_instance
    from /usr/lib64/libgobject-2.0.so.0
  • #20 g_object_new_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #21 g_object_newv
    from /usr/lib64/libgobject-2.0.so.0
  • #22 g_object_new_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #23 g_object_new
    from /usr/lib64/libgobject-2.0.so.0
  • #24 terminal_screen_new
  • #25 terminal_app_new_terminal
  • #26 terminal_app_new_terminal
  • #27 main

Comment 3 Joachim Sauer 2004-11-12 13:38:57 UTC
I tried un-prelinking my system (prelink is installed by default on FC3) and
then it works again! So add the following step to "How to reproduce":

0. Run prelink on your whole system (haven't tried to narrow it down)

(btw, this all happens on x86_64)
Comment 4 Mariano Suárez-Alvarez 2004-11-12 13:53:13 UTC
Hm. I guess this is NOTGNOME, then. Joachim, could you report this on the FC
bugzilla?
Comment 5 Joachim Sauer 2004-11-12 14:01:53 UTC
I've reported it to FC Buzilla (one number too late, 'though ;-)

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=139001

It seems I may not set it to NOTGNOME, so I'll have to leave that to you.