Bug 588049 - gnome-terminal required libgnome, but there is no package dependency
Summary: gnome-terminal required libgnome, but there is no package dependency
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gnome-terminal
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Behdad Esfahbod
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: 599016
TreeView+ depends on / blocked
 
Reported: 2010-05-02 11:50 UTC by Gordan Bobic
Modified: 2010-11-10 20:34 UTC (History)
3 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-11-10 20:34:32 UTC


Attachments (Terms of Use)

Description Gordan Bobic 2010-05-02 11:50:46 UTC
Description of problem:

gnome-terminal doesn't work unless libgnome is installed. It fails with:
ERROR:terminal-app.c:1445:terminal_app_init: assertion failed:
(app->system_font_desc != NULL)

Steps to Reproduce:
1. Do a minimal RHEL6b install
2. yum install xterm and gnome-terminal
3. startx
4. xterm starts, gnome-terminal does not. Running gnome-terminal in xterm returns the above error.
  
Actual results:
ERROR:terminal-app.c:1445:terminal_app_init: assertion failed:
(app->system_font_desc != NULL)

Expected results:
gnome-terminal should start

Additional info:
"yum install libgnome" fixes the problem.

Comment 2 RHEL Product and Program Management 2010-05-02 13:25:33 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 5 Tomas Pelka 2010-05-10 08:54:59 UTC
Reproducer in description. Giving qa_ack.

Comment 6 Radek Lat 2010-08-24 12:30:31 UTC
Tested and Verified on gnome-terminal-2.31.3-4.el6.x86_64.

Comment 7 releng-rhel@redhat.com 2010-11-10 20:34:32 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.