Bug 25445 - Black screen (dark gray) after end running screensaver on Mageia 7.0 and 7.1 after RPM updates
Summary: Black screen (dark gray) after end running screensaver on Mageia 7.0 and 7.1 ...
Status: RESOLVED DUPLICATE of bug 25008
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-15 20:13 CEST by ed hoeven
Modified: 2019-09-15 21:41 CEST (History)
1 user (show)

See Also:
Source RPM: https://bugs.mageia.org/page.cgi?id=fields.html#cf_rpmpkg
CVE:
Status comment:

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

Description ed hoeven 2019-09-15 20:13:30 CEST 
1 - Description of problem:

Black screen (dark gray) after end running screensaver.
When dark screen started I can't get back to normal screen with hit any buttons.

When I turn off the system the screen goose black before the system is really off from power. 
 


After first update I get after screensaver started and running after longer time a black screen and when this is going on I can't get turn black screen on active screen.
Anything I do on keyboard there is no response. Keyboard works well, I can turn off on my WiFi, and when I use keyboard I see my mouse icon and moving when I use my mouse.

My PC info.
Dell Inspiron | 6400

Mageia 7.1

CPU intel(R) CPU T2050 @ 1.60GHz
RAM 1990176 KiB

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

I have totally clean installed 
Mageia 7.0 and also 
totally clean install again 
Mageia 7.1 ...
 
Desktop XFCE on x11

bugs starting after updates from RPM packages ... 



How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Lewis Smith 2019-09-15 21:41:16 CEST 
This looks like a continuation of bug 25008.

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

Resolution: (none) => DUPLICATE
CC: (none) => lewyssmith
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.