Bug 19354

Summary:	No graphics after update
Product:	Mageia	Reporter:	Jan Pihlgren <jan>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	Pictures that describe the error Pictures that describe the error Picture that describe the error Next picture Next picture Error-picture Error picture

Description Jan Pihlgren 2016-09-14 09:42:00 CEST

I use VirtualBox Version 5.1.2_OSE r108956.
Description of problem:
When update Mageia6sta1 and restarted get a black window with 3 small icons then ended with a messages that tell me that there has been a problem when starting the graphical display.
Trying to follow the instruction failed.
Running drakx11 but the error still occur when I change  parameters. 
No luck. I have to restore a backup to have the possibility to run Mageia6sta1.

I want to add pictures to the report that show the problem but don't know how.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Comment 1 Samuel Verschelde 2016-09-14 11:01:51 CEST

You can use the "Add an attachement" link to add the picture.

Comment 2 Jan Pihlgren 2016-09-14 11:25:09 CEST

Created attachment 8404 [details]
Pictures that describe the error

Comment 3 Jan Pihlgren 2016-09-14 11:25:52 CEST

Created attachment 8405 [details]
Pictures that describe the error

Comment 4 Jan Pihlgren 2016-09-14 11:26:40 CEST

Created attachment 8406 [details]
Picture that describe the error

Comment 5 Jan Pihlgren 2016-09-14 11:27:14 CEST

Created attachment 8407 [details]
Next picture

Comment 6 Jan Pihlgren 2016-09-14 11:27:38 CEST

Created attachment 8408 [details]
Next picture

Comment 7 Jan Pihlgren 2016-09-14 11:28:15 CEST

Created attachment 8409 [details]
Error-picture

Comment 8 Jan Pihlgren 2016-09-14 11:28:46 CEST

Created attachment 8410 [details]
Error picture

Comment 9 David Walser 2016-09-14 16:55:39 CEST

You can fix this by adding "nomodeset" to the kernel command line.

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

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE