Bug 13223

Summary:	Lenovo Essential G500 (59-370358) display not working
Product:	Mageia	Reporter:	akash sharan <akashsharan13>
Component:	Installer	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description akash sharan 2014-04-16 15:03:50 CEST

i have installed mageia 3 as well mageia 4 but this bug has not been remove....
Lenovo Essential G500 (59-370358) is capable of installing mageia but mageia showing bug in display the interface....
i had selected plug n play option as well lenovo g500 display option but it is showing the same problem


Reproducible: 

Steps to Reproduce:

Comment 1 Samuel Verschelde 2015-05-02 20:53:09 CEST

Sorry that your bug report was overlooked.

Please provide the output of: lspcidrake -v

Please also provide a screenshot or photograph of the display problem.

Please also test Mageia 5RC, maybe it's been fixed now.

Keywords: (none) => NEEDINFO

Samuel Verschelde 2015-05-02 20:53:19 CEST

Summary: Lenovo Essential G500 (59-370358) display not working!!!!! => Lenovo Essential G500 (59-370358) display not working

Comment 2 Marja Van Waes 2015-09-21 10:51:32 CEST

Installer and Release bugs should always be set to cauldron, because once the isos for a stable version have been created, they cannot be changed.

This bug was filed very long ago, for Mageia 4. Was this bug still valid for Mageia 5?

(If so, please do _not_ set the version to "5". Only asking because if it was still valid for Mageia 5, that then we'll know we'll have to pay attention to this issue when testing the 6 alpha's and later).

Please close this bug report if the problem was solved in Mageia 5hhhh

Version: 4 => Cauldron

Comment 3 Rémi Verschelde 2015-09-21 11:25:04 CEST

What do you mean by "display not working"? Is it not working while in the installer, or are you able to install properly but it does not work on reboot?

Comment 4 Marja Van Waes 2016-02-17 20:31:11 CET

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD