Bug 230066 - wireshark-gnome should depend on fonts-xorg-base
wireshark-gnome should depend on fonts-xorg-base
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gtk2 (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Cosimo Cecchi
Depends On:
  Show dependency treegraph
Reported: 2007-02-26 08:16 EST by Miroslav Suchý
Modified: 2013-04-30 18:54 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 11:52:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Miroslav Suchý 2007-02-26 08:16:30 EST
Description of problem:
I have vmware machine and wanted run wireshark-gnome there, but I got this error:
# wireshark
No fonts found; this probably means that the fontconfig
library is not correctly configured. You may need to
edit the fonts.conf configuration file. More information
about fontconfig can be found in the fontconfig(3) manual
page and on http://fontconfig.org

When I install fonts-xorg-base it run smoothly. So wireshark-gnome should depend
on fonts-xorg-base or sine font virtual package.

Version-Release number of selected component (if applicable):
# rpm -q wireshark-gnome

How reproducible:
Comment 1 Miroslav Suchý 2007-02-26 08:48:01 EST
This should be handled by some package on which wireshark-gnome depends on. I
assume GTK2, maybe some lower. Same error do gtk-demo without fonts.
Comment 2 Eric Harney 2007-08-18 01:33:36 EDT
Same problem exists in Fedora 7.
Comment 3 Jiri Pallich 2012-06-20 11:52:48 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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