Bug 814

Summary: Linux conf requires a higher bit depth than standard VGA to run
Product: [Retired] Red Hat Linux Reporter: mfranz
Component: linuxconfAssignee: David Lawrence <dkl>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-04-10 02:50:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description mfranz 1999-01-13 04:55:46 UTC
I was shocked to find out that linuxconf would not run with
a generic VGA driver (16 color VGA) for X installed. If
Linux is to get easier to use, all the utils should work at
any bit depth from within X.

I was running on an AMD K6-350
3Dfx Banshee 16MB running generic VGA X drivers
clean install - No other programs other than "server" Linux
installed.

Comment 1 David Lawrence 1999-01-19 21:38:59 UTC
I have been able to replicate this problem in the test lab. Linuxconf
when run from an xterm, complains by saying:

remadmin (GUI frontend) exiting abnormally

Also, the usermode utilities such usermount, userinfo, and userpasswd
will not work correctly in 4 bit color. The complain:

** ERROR **: unable to find a usable color depth
Aborted (core dumped)

Since these all rely on gtk then it is possible gtk is causing the
problem in low color situations.

Comment 2 Michael K. Johnson 1999-02-10 18:36:59 UTC
There are no intrinsic limitations in the gnome-linuxconf front
end for 16-bit color, so this must be a Gtk (or slightly possibly
GNOME) limitation.  This may have been improved with recent
development versions of Gtk.

This bug has been reassigned to QA for testing with latest
development Gtk/GNOME.

Comment 3 Michael K. Johnson 1999-04-10 02:50:59 UTC
I have verified that this is fixed with the latest Gtk and GNOME.
We can't back-port this to 5.2 as an errata item, but as a
workaround, you can run gnome-linuxconf in terminal mode with either
linuxconf --text
or
DISPLAY= linuxconf
(note, the space after the = is important)