|
Bugzilla – Full Text Bug Listing |
| Summary: | yast in text mode can't load Graphics Card & Monitor module | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Jason Wallwork <dsp6q3t02> |
| Component: | YaST2 | Assignee: | Marcus Schaefer <ms> |
| Status: | RESOLVED WORKSFORME | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | yast2 ncurses version log | ||
|
Description
Jason Wallwork
2005-08-21 06:38:25 UTC
Created attachment 46778 [details]
yast2 ncurses version log
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 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. 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. >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.
|