Description of problem: After a clean install of LXDE X86_64 only DE on real hardware, on first login, if you pause desktop activity for a period of time, sufficient for the screen saver slideshow to start, moving the mouse or tapping the keyboard invokes the screen-locker dialogue window. enter the user password and the desktop is presented. if you then pause desktop activity for another period of time, sufficient for the screen saver slideshow to start again, moving the mouse or tapping keyboard presents the desktop. no screen-locker dialogue box is presented. If you wait for such time that the monitor is powered down, sometimes the screen-locker is presented, sometimes not. Version-Release number of selected component (if applicable): Mageia-6-dev1-x86_64-DVD.iso DATE.txt: Wed Mar 16 23:02:20 CET 2016 How reproducible:every time Steps to Reproduce: 1.install LXDE only DE from above .iso 2.reboot, choose LXDE as DE at login, and login do DE 3.wait for screen saver slideshow 4.move mouse or tap a keyboard key to invoke screen-locker
Created attachment 7631 [details] install report
Whiteboard: (none) => 6-dev1
Created attachment 7632 [details] lspcidrake -v output
Not sure which packages is the culprit, but Nicolas will know and reassign if needed :-)
Keywords: (none) => 6dev1CC: (none) => marja11Assignee: bugsquad => nicolas.salgueroWhiteboard: 6-dev1 => (none)
It is xscreensaver so it is for me :-)
Source RPM: (none) => xscreensaver
@Ben Hi, I forgot to ask for some precision: can you give me the duration in minutes of the different periods of time you talk about? I need to verify them with our default configuration of xscreensaver (for the last part of the bug report: "If you wait for such time that the monitor is powered down, sometimes the screen-locker is presented, sometimes not.", I wonder if it is not because we have configured xscreensaver to power off the screen after the same duration as to lock the screen; maybe this particular configuration causes a race condition).
Hi, I have made available version 5.35 in core/updates_testing and in tainted/updates_testing for Cauldron. Does that version corrects the problem? Best regards, Nico.
Hi, In fact, the version 5.35 is in core/release for Cauldron. Best regards, Nico.
forgot about this one, no longer an issue
Resolution: (none) => FIXEDStatus: NEW => RESOLVED