Bug 26692

Summary:	login screen bug on mageia 7.1 i586 xfce
Product:	Mageia	Reporter:	A G <pixymg>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	fri, lewyssmith
Version:	7
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description A G 2020-05-27 13:40:50 CEST

Description of problem: after the system goes to standby, the login screen tends not to display the password and remains frozen.


Version-Release number of selected component (if applicable):
Mageia 7.1 I586 Xfce


How reproducible: after the system is on standby, when entering password


Steps to Reproduce:
1.Wait a system standby
2.try to login 
3.the bug can occur

Comment 1 Lewis Smith 2020-05-27 21:20:18 CEST

This looks like yet another duplicate of bug 25008, which is enormously long & confused. See especially https://bugs.mageia.org/show_bug.cgi?id=25008#c33
The main points were:
- 32-bit Xfce
- having more than 1 screensaver running. To investigate this, do:
 $ ps ax | grep saver

Disable every screensaver you can find! Please report back if you think your problem is the same as the other one(s), see 'Duplicates' in the bug header. And whether you had multiple screensavers, and whether getting rid of them solves your problem.

CC: (none) => lewyssmith

Comment 2 Morgan Leijström 2020-05-27 22:11:17 CEST

I noticed somethign along the lines on our 32bit mga7 on Thinkpad T40 with xfce last week.
The login name was invisible, but the dropdown worked, with all entries looking just white.  I did fiddle around, switched ti text terminal Ctrl-Alt-F3 and back and tried clicking somewhere and suddenly i could log in.  Sorry i dont remember details more.

CC: (none) => fri

Comment 3 Aurelien Oudelet 2020-08-27 11:34:53 CEST

Since 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 our 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
Resolution: (none) => OLD