Bug 116229 - yast and X11 configuration from command line
Summary: yast and X11 configuration from command line
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: RC 1
Hardware: All Other
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-09 19:03 UTC by Sacha Kerres
Modified: 2008-06-25 09:52 UTC (History)
0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sacha Kerres 2005-09-09 19:03:34 UTC 
When you launch the X11 configuration from the terminal (tty1) with 'yast x11',
it will quit without a message, when X11 is running (runlevel 5). If you switch
to runlevel 3 (init 3) then everything works fine.
Comment 1 Martin Lasarsch 2005-09-12 10:44:28 UTC 
works for me, please provide more information: 
 
y2logs: 
http://www.opensuse.org/index.php/Bug_Reporting_FAQ#YaST 
 
and /var/log/SaX.log
Comment 2 Michael Gross 2005-09-20 10:09:10 UTC 
Closed as a reminder. If you're willing to provide the needed information, feel
free to reopen this.
Comment 3 Stephan Kulow 2008-06-25 09:33:12 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 4 Stephan Kulow 2008-06-25 09:34:51 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 5 Stephan Kulow 2008-06-25 09:41:04 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 6 Stephan Kulow 2008-06-25 09:52:42 UTC 
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(