Bug 106036 - yast in text mode can't load Graphics Card & Monitor module
Summary: yast in text mode can't load Graphics Card & Monitor module
Status: RESOLVED WORKSFORME
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 2
Hardware: i686 All
: P5 - None : Normal
Target Milestone: ---
Assignee: Marcus Schaefer
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-21 06:38 UTC by Jason Wallwork
Modified: 2005-08-23 09:40 UTC (History)
0 users

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
yast2 ncurses version log (230.42 KB, application/x-gzip)
2005-08-21 06:39 UTC, Jason Wallwork
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Wallwork 2005-08-21 06:38:25 UTC
If I'm in a virtual console then yast seems unable to load the module pertaining
go graphics card & monitor. It doesn't hang - nothing happens. With Konsole, it
loads the graphical program as expected.
Comment 1 Jason Wallwork 2005-08-21 06:39:55 UTC
Created attachment 46778 [details]
yast2 ncurses version log
Comment 2 Marcus Schaefer 2005-08-22 08:09:16 UTC
what happens if you call sax2 from the console instead of yast ? 
Does the program start there ? Are you sure there is no other X-Server 
which you have access to ? If there is another X-Server currently running 
the program will start there even if you are working on the console 
 
Please check. Thanks 
Comment 3 Jason Wallwork 2005-08-23 07:41:21 UTC
I did have X server running. Once I shut it down by changing to runlevel 3 then
sax ended up starting up whether called by yast or directly.

I had thought it didn't work in the console because previously I had installed
beta 2 and chose to install nvidia drivers via the YOU script. X wouldn't work
after that and neither would yast or sax2.

In the past I though I could change graphics setup without an x server though.
Comment 4 Marcus Schaefer 2005-08-23 08:26:56 UTC
Ok, so this seems to be working as expected if I understand things 
correctly. SaX is always trying to detect if there is a X-Server running 
which the user calling sax has access to. This is because the user may 
want to change the settings of the X-Server he has access to and if that 
server is running SaX will load it's configuration and provide it to the 
user. If there is no X-Server running or the user has no access to it sax 
will start its own X-Server and will NOT read the current configuration 
because it may be broken because of the fact that no X-Server is running 
using that configuration. 
Comment 5 Jason Wallwork 2005-08-23 09:40:34 UTC
>If there is no X-Server running or the user has no access to it sax  
will start its own X-Server and will NOT read the current configuration  
because it may be broken because of the fact that no X-Server is running  
using that configuration. 
 
That's what it is doing now. But on the previous install (also beta 2) where 
the X configuration was broken, *nothing* happened. That's what I thought was 
weird. There was no way to re-configure the graphics setting using the sax 
tool. I didn't post that as a bug because I read that if you weren't supposed 
to if you used the nvidia installer. So..... not sure. I guess since I can't 
reproduce it, might as well close this one.