Bug 24632

Summary:	black screen after the screen saver
Product:	Mageia	Reporter:	Jean-Marc AUBRY <jm.81000>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	minor
Priority:	Normal	CC:	lewyssmith, marja11, matteo.pasotti
Version:	6	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Jean-Marc AUBRY 2019-04-07 11:03:52 CEST

Description of problem:

I have black screen after the  screen saver !!!
I can't use mouse or keyboard.
I must use the button on/off to restart the machine.

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

motherboard ASUS prime B450M-A
Video : RV710 [Radeon HD 4350/4550] 

How reproducible:


Steps to Reproduce:
1.
2.
3.

Comment 1 Marja Van Waes 2019-04-09 10:22:27 CEST

Which Desktop environment and wich Display manager do you use?

Please, after having needed to restart the machine because of this issue:

* Open a konsole/terminal
* Become root
* run
   
    journalctl -ab -1 > log.txt

* attach log.txt to this bug report.

Thanks :-)

CC: (none) => marja11
Keywords: (none) => NEEDINFO

Matteo Pasotti 2019-11-25 19:49:19 CET

CC: (none) => matteo.pasotti

Comment 2 Lewis Smith 2020-01-29 11:54:02 CET

Jean-Marc

What is your current situation on this bug? Have you, for example, disabled the screensaver ? Are you still interested? If you are...
---
You must tell us what Desktop and Display Manager you are using.
Another thing to look out for is whether there is more than one screensaver running. Do:
 $ ps ax | grep saver
and post the result. The problem can sometimes be cured by removing the 'extras'.

> I have black screen after the  screen saver !!!
> I can't use mouse or keyboard.
Before re-booting, can you reach a virtual console with Ctl/Alt/F2-6 ?
If you can, login there and do:
 $ journalctl -ab > log.txt
then logout. This saves the journal for the current session.

If you have to re-boot to do anything at all, do as already asked; open a terminal, and do:
 $ journalctl -ab -1 > log.txt
This saves the journal from the previous (blocked) session.

In either case, attach log.txt to this bug report.

CC: (none) => lewyssmith

Comment 3 Marja Van Waes 2020-08-02 13:01:08 CEST

Over a year later and half a year after the requests for information, no reply
Besides, this report was filed against Mageia 6

So, closing as OLD

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

Comment 4 Jean-Marc AUBRY 2020-08-02 13:24:18 CEST

Hello

I solved the problem. It’s not from the distribution but from the BIOS.
I just turned off the Global C-States in the bios.