Bug 841678

Summary:	Installation GUI does not start/work, text install cannot change packages
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Mario Guzman <mario_bz>
Component:	Installation	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Major
Priority:	P5 - None
Version:	13.1 Beta 1
Target Milestone:	---
Hardware:	Macintosh
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Mario Guzman 2013-09-21 18:31:31 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0

I am reporting this as an installation problem since it is occurring right at the start of the install. I have already reported this as an xorg problem but do not think it is related to xorg and there is no more activity on that problem (bug 835975) where logs, etc. can be found. i apologize if this should not be reported again. I do not know if the installation problem and xorg problem should be reported separately since different people may work on them. I do think this is not an xorg issue but an issue with the hardware not being detected correctly.See the above bug for info and let me know if more is needed, although I have no idea how to get the log of the system at such an early stage of installation. BTW, the GUI is required since I find customizing packages in text mode does not work (at least what I wanted to do).

I thought this is important since it prevents installation and may affect others when GA is released. I would like to convert to 13.1 but this is a show stopper.

Reproducible: Always

Steps to Reproduce:
1.Installation - no GUI
2.
3.
Actual Results:  
No install GUI

Expected Results:  
Install GUI can be used.

Comment 1 Martin Vidner 2013-10-01 11:36:48 UTC

As we see in the other bug, Stefan has already acknowledged that it is likely a problem with the X server. In recent releases, YaST does not configure X anymore.

*** This bug has been marked as a duplicate of bug 835975 ***