Ubuntu
gnome-screensaver package

16.04.1 LTS: using "screen lock" requires reboot to use computer

Bug #1611162 reported by Promptjock on 2016-08-09

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gnome-screensaver (Ubuntu)	New	Undecided	Unassigned

Bug Description

Updated from v. 14.04 to 16.04.1 via Software Update. When I activate Screen Lock and leave it alone, I have to reboot my system to make it active (i.e., the system "goes to sleep"). I didn't have this problem with v. 14.04. Otherwise, things seem to be OK...

Processor: AMD Athlon(tm) 64 Processor 3500+
Memory: 4G
Hard Drive: 250G Samsung SSD

Additional info: if I have my machine sitting at a "normal" login (i.e., after reboot), I have no problems. It's only when I activate "screen lock" that I have to reboot my machine via hardware "reset" button or power cycle.

Tags:

Revision history for this message

Ubuntu Foundations Team Bug Bot (crichton) wrote on 2016-08-09:

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1611162/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags:

added: bot-comment

Revision history for this message

Promptjock (promptjock) wrote on 2016-08-09:

I updated my system via "Software Update" that informed me ver. 16.04LTS (64-bit) was available. It was after the update the "screen lock" issue was discovered. I'm sorry I can't provide any further information on a specific "package" as I'm not a software developer....

Revision history for this message

Promptjock (promptjock) wrote on 2016-08-09:

Regarding the "package" information: I believe the "package" is the 64-bit "AMD64" version of Ubuntu 16.04.1LTS. As I've already related, this update occurred via the "Software Update" feature of the 14.04LTS installation I had when it informed me that "ver. 16.04 was available".

Revision history for this message

Promptjock (promptjock) wrote on 2016-08-10:

OK, after some more "rooting around" @ the Ubuntu site (https://wiki.ubuntu.com/Bugs/FindRightPackage#Finding_the_Package_Name), I (finally) found the page with the information pertaining to my problem: https://wiki.ubuntu.com/DebuggingScreenLocking/HowScreenLockingWorks. I sincerely apologize for the "wasted bandwidth"....

affects:

ubuntu → gnome-screensaver (Ubuntu)

Revision history for this message

Promptjock (promptjock) wrote on 2016-08-11:

"Brightness & Lock" settings resulting in reported problem Edit (30.3 KiB, image/png)

UPDATE: I think I discovered the "root problem"! it looks like the "Screen Off after xx minutes" function, combined with the "Require password when waking from suspend" option checked (System Settings, Brightness & Lock) is causing the problem. The attached screen capture shows the relevant settings. DATA: I DISABLED the "Screen off" function ("Never" option) and un-checked the "Require password when waking..." option, then activated the Screen Lock and "let it sit". I was able to exit Screen Lock via my password. I then re-enabled the aforementioned "Brightness & Lock" options (see the attached Screen Capture picture for the settings) and THE PROBLEM CAME BACK! when I enabled Screen Lock, the screen "faded out" then the monitor went into "power save" mode (i.e., "no input signal detected"). I then moved my mouse/"worked" the keyboard, and the display NEVER CAME BACK - I had to reboot (via RESET button) to regain functionality.

For the record, BEFORE the upgrade from 14.04 LTS, the system was set to use the aforementioned "Screen off..." and "Require password when waking..." functions and there were no problems in coming out of Screen Lock by moving the mouse/"working" the keyboard.

Revision history for this message

Promptjock (promptjock) wrote on 2016-08-11:

UPDATE II: more details for the previous UPDATE.

It seems that when I activate screen lock VIA THE KEYBOARD (Ctrl+Alt+L), I DO NOT get the "go to sleep and reboot" phenomenon to occur. When I use THE MOUSE to click on the "services" icon (upper-right of screen, next to the "Date/Time" display), scroll down to the "Lock Ctrl+Alt+L" line and click on it, the screen lock activates THEN within 10 seconds the display DIMS, then BLANKS, my display shows "Entering power save mode - no signal detected", then the "go to sleep and reboot" phenomenon occurs. NOTE: when I moved the mouse Just As The Screen Started To Dim, the display returned to normal brightness and the phenomenon did not occur.

AGAIN: I have DISABLED the "Screen Off after xx minutes" and "Require password when waking from suspend" function/option in "System Settings, Brightness & Lock".

Right now, my "workaround" for using Screen Lock is to USE THE KEYBOARD, not the mouse, to enable the function.