Bug 15517 - M5rc-dual, XFCE: just after 1st login, screen locker starts
Summary: M5rc-dual, XFCE: just after 1st login, screen locker starts
Status: RESOLVED DUPLICATE of bug 15460
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-18 09:56 CET by Ben McMonagle
Modified: 2015-03-26 07:18 CET (History)
2 users (show)

See Also:
Source RPM: Mageia-5-RC-dual-DVD. 16 08:18:18 CET 2015
CVE:
Status comment:

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

Description Ben McMonagle 2015-03-18 09:56:31 CET 
Description of problem: just after 1st login, screen locker starts, enter password as required and back to desktop.


Version-Release number of selected component (if applicable):
Mageia-5-RC-dual-DVD.  16 08:18:18 CET 2015



How reproducible:


Steps to Reproduce:
1.install from dvd or usb
2.reboot and login
3.I had enough time to open MCC before issue occurred.
4.leave system for long enough for screen power saver to activate, screen locker doesn't activate


Reproducible: 

Steps to Reproduce:
Ben McMonagle 2015-03-18 09:57:21 CET

Summary: M5rc just after 1st login, screen locker starts => M5rc-dual, LXDE: just after 1st login, screen locker starts

Ben McMonagle 2015-03-18 09:58:06 CET

Summary: M5rc-dual, LXDE: just after 1st login, screen locker starts => M5rc-dual, XFCE: just after 1st login, screen locker starts

David Walser 2015-03-18 22:57:58 CET

CC: sysadmin-bugs => ennael1, jani.valimaa
Component: Release (media or process) => RPM Packages

Comment 1 Jani Välimaa 2015-03-25 16:16:23 CET 
Xscreensaver's or lightdm's lock screen?
Comment 2 Ben McMonagle 2015-03-26 07:18:46 CET 
xscreensaver 5.29

thank you for looking into this

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

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