Bug 37863

Summary: Configuration of X corrupts screen, and install lacks wrapper.
Product: Base System Reporter: Ashley Penney <ashp>
Component: miscAssignee: freebsd-qa (Nobody) <qa>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description Ashley Penney 2002-05-08 20:10:04 UTC 
	During installation of the 4.6 snapshots, my console was corrupted
upon exiting the X configuration (xf86cfg).  I was forced to run vidcontrol
80x25 to fix it afterwards.

It's unlikely that the problem could be diagnosed in time, and patched, and
so forth, so a workaround would be to simply call 'vidcontrol 80x25' after
running the X server, to repair the broken console.

[I have an Nvidia Geforce3 card, so this may be required to repeat this.]

Also, after the installation was done, I noted that 'wrapper' had not been
installed.  I run X by the old fashioned 'startx', and this will fail post
installation.  This should be added to the list of installed packages, when
X is selected in the installation.

Fix: 

Add wrapper to the package list.  Call 'vidcontrol 80x25' after X
configuration (on i386, at least).
How-To-Repeat: 	Install X from the 4.6 snapshots from snapshots.jp.freebsd.org,
attempt to configure X via the xf86cfg option.  Also, simply try to start
X once the installation is finished.
Comment 1 Makoto Matsushita 2002-05-09 18:50:12 UTC 
Sorry I don't have any idea how to fix screen corruption.

ashp> Also, after the installation was done, I noted that 'wrapper'
ashp> had not been installed.  I run X by the old fashioned 'startx',
ashp> and this will fail post installation.  This should be added to
ashp> the list of installed packages, when X is selected in the
ashp> installation.

However, some users does *not* want to install wrapper since they
doesn't use startx.  It would be better that

	* If you want to install Xwrapper, do it yourself.  sysinstall
	  does have a menu for installing packages.
	* When installing XFree86 package, a pop-up message "if you
	  want to start X with startx(1), please install wrapper
	  program from package." is shown.

How do you think about this?

-- -
Makoto `MAR' Matsushita
Comment 2 Dmitry Morozovsky 2002-05-09 19:37:00 UTC 
On Thu, 9 May 2002, Makoto Matsushita wrote:

MM>  However, some users does *not* want to install wrapper since they
MM>  doesn't use startx.  It would be better that
MM>
MM>  	* If you want to install Xwrapper, do it yourself.  sysinstall
MM>  	  does have a menu for installing packages.
MM>  	* When installing XFree86 package, a pop-up message "if you
MM>  	  want to start X with startx(1), please install wrapper
MM>  	  program from package." is shown.
MM>
MM>  How do you think about this?

Well, then what about adding additional checkbox with the comment like

[ ] xwrapper	Needed for startx script, not with xdm

Furthermore, another checkbox may be added to enable xdm, with the
following action:

And auto-comment xdm line in /etc/ttys if it is checked, and uncomment
otherwise.

I suppose it is more consistent.

Sincerely,
D.Marck                                   [DM5020, DM268-RIPE, DM3-RIPN]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------
Comment 3 Makoto Matsushita 2002-05-10 15:09:16 UTC 
marck> Well, then what about adding additional checkbox with the comment like

How many checkboxes do we need (imagine KDE, GNOME, sub-packages of
XFree86 itself, X font packages, other tools live in ports/x11, etc,
etc, etc...).

Are there any criterion that a package should be listed in the
separate menu?

-- -
Makoto `MAR' Matsushita
Comment 4 Tilman Keskinoz freebsd_committer freebsd_triage 2004-04-23 17:02:03 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-qa

Sysinstall issue
Comment 5 Mark Linimon freebsd_committer freebsd_triage 2004-08-29 05:55:12 UTC 
State Changed
From-To: open->closed

The new consensus seems to be that removing X configuration from 
sysinstall is the solution to many problems.  This will make this 
PR obsolete.