can't un-lock screen

[Michael Dooley]

MATE 17.10 alpha. When I use System, Lock Screen after logging on and updating the system, the only way out is to select Switch User. Otherwise, I am unable to enter anything in the dialog box. After I wait a couple of minutes (undeterminant) Lock Screen works as expected.

[Michael Dooley (mdooley)]

Similar behavior in MATE 17.04. I expect lock screen will work one I finish adding this comment.

[Michael Dooley (mdooley)]

I waited 8 minutes and gave up. I had to log out and back in before 17.04 lock screen would work as expected. Similar behavior here in MATE 16.04.3. Is this a feature??

[Michael Dooley (mdooley)]

I now think that this involves Synaptic. To replicate this bug, I logged out and then back in to MATE 17.10 and used System, Administration, Synaptic Package Manager to load Synaptic. I refreshed Synaptic by clicking on the Reload icon and after the refresh, no possible updates were offered. I then closed Synaptic and used System, Lock Screen. Pressing the space bar or moving a fingertip on the touchpad displayed the expected dialog box but with no means of unlocking. I swirched user. After waiting a few minutes, Lock Screen works as expected.

(It is quite possible that the same behavior can be duplicated in MATE 17.04 and MATE 16.04.3.)

[Martin Wimpress  (flexiondotorg)]

I don't use Synaptic, but I can't reproduce this.

[Michael Dooley (mdooley)]

On 08/15/2017 03:41 PM, Martin Wimpress wrote:

> I don't use Synaptic, but I can't reproduce this.
>
> ** Changed in: ubuntu-mate
> Status: New => Incomplete
>
I installed 17.10 daily build bare metal on two systems this morning and
reported bug does not exist (can't reproduce). I used Software updater
instead of synaptic. If I can reproduce the bug later today or more
likely tomorrow, I'll let you know.

Thanks Martin.

--
Michael

[Michael Dooley (mdooley)]

After installing a fix for caja, see - https://ubuntu-mate.community/t/help-test-a-critical-bug-fix-in-ubuntu-mate-16-04/14624, I could not reproduce this behavior in MATE 16.04.3. I recommend changing this bug to fixed.