Lockscreen problems in Ubuntu 16.04

[Or Schiro]

Dear all,

Since my upgrade to 16.04 I am presented with a second lock-screen which I would like to get rid of.

The steps to reproduce are as follows:

1. Close the lid of my laptop (Thinkpad X230)
2. Laptop turns into standby
3. Open the lid
4. I am shown with this second lock-screen as shown in the attached image
5. After entering my password, I am presented with the default Ubuntu 16.04 lock-screen

Is anybody else able to reproduce it?

Thankfully,

~Robert

[Marco Trevisan (Treviño) (3v1n0)]

Before suspending, can you launch these in two terminals:
  gdbus monitor --session --dest org.gnome.ScreenSaver & gdbus monitor --session --dest com.canonical.Unity

and
  dbus-monitor --session "interface='org.gnome.ScreenSaver'"

Also, to get the screenshot, you can just launch:
  sleep 20 && gnome-screenshot

If you suspend and resume and wait 20 secs maximum, you should get a pic of it.

[Or Schiro (orschiro)]

Dear Marco,

Thank you for your guidance!

Here is your requested input:

orschiro@x230:~$ dbus-monitor --session "interface='org.gnome.ScreenSaver'"
signal time=1462200234.659151 sender=org.freedesktop.DBus -> destination=:1.861 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
   string ":1.861"
signal time=1462200234.659314 sender=org.freedesktop.DBus -> destination=:1.861 serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
   string ":1.861"
method call time=1462200248.835400 sender=:1.99 -> destination=org.gnome.ScreenSaver serial=1399 path=/org/gnome/ScreenSaver; interface=org.gnome.ScreenSaver; member=GetActive
method call time=1462200261.132195 sender=:1.99 -> destination=org.gnome.ScreenSaver serial=1403 path=/org/gnome/ScreenSaver; interface=org.gnome.ScreenSaver; member=GetActive

orschiro@x230:~$ gdbus monitor --session --dest org.gnome.ScreenSaver & gdbus monitor --session --dest com.canonical.Unity
[1] 11481
Monitoring signals from all objects owned by org.gnome.ScreenSaver
Monitoring signals from all objects owned by com.canonical.Unity
The name org.gnome.ScreenSaver is owned by :1.22
The name com.canonical.Unity is owned by :1.22
/org/gtk/gio/DesktopAppInfo: org.gtk.gio.DesktopAppInfo.Launched (b'', '', int64 11488, @as [], {'startup-id': <'compiz-1624-x230-gnome-terminal-35_TIME27245428'>, 'origin-prgname': <b'compiz'>, 'origin-pid': <int64 1624>})
/org/gtk/gio/DesktopAppInfo: org.gtk.gio.DesktopAppInfo.Launched (b'', '', int64 11488, @as [], {'startup-id': <'compiz-1624-x230-gnome-terminal-35_TIME27245428'>, 'origin-prgname': <b'compiz'>, 'origin-pid': <int64 1624>})
/org/gtk/gio/DesktopAppInfo: org.gtk.gio.DesktopAppInfo.Launched (b'', '', int64 11521, @as [], {'startup-id': <'compiz-1624-x230-gnome-terminal-36_TIME27259178'>, 'origin-prgname': <b'compiz'>, 'origin-pid': <int64 1624>})
/org/gtk/gio/DesktopAppInfo: org.gtk.gio.DesktopAppInfo.Launched (b'', '', int64 11521, @as [], {'startup-id': <'compiz-1624-x230-gnome-terminal-36_TIME27259178'>, 'origin-prgname': <b'compiz'>, 'origin-pid': <int64 1624>})
/com/canonical/Unity/Session: com.canonical.Unity.Session.LockRequested ()
/com/canonical/Unity/Session: com.canonical.Unity.Session.LockRequested ()
/com/canonical/Unity/Session: com.canonical.Unity.Session.Locked ()
/com/canonical/Unity/Session: com.canonical.Unity.Session.Locked ()
/com/canonical/Unity/Session: com.canonical.Unity.Session.UnlockRequested ()
/com/canonical/Unity/Session: com.canonical.Unity.Session.UnlockRequested ()
/com/canonical/Unity/Session: com.canonical.Unity.Session.Unlocked ()
/com/canonical/Unity/Session: com.canonical.Unity.Session.Unlocked ()

[Or Schiro (orschiro)]

Dear all,

Problem solved by https://askubuntu.com/questions/794052/what-is-this-second-login-screen?noredirect=1#comment1195290_794052.

> Try removing your .Xauthority. Go to a TTY (Ctrl+Alt+F1) and type mv .Xauthority .Xauthority_2016-07-02. Then run sudo service lightdm restart and see if it fixes the issue

[Or Schiro (orschiro)]

Hello again,

Sadly the problem was only solved temporarily and re-occurred.

Thus is this problem a bug or a problem on just my system?

Warmly,

~Robert

[Andrea Azzarone (azzar1)]

Do you have on screen keyboard active?

[Or Schiro (orschiro)]

Dear Andrea,

Thank you for your reply!

In the meantime, the problem disappeared.

We can close this issue.

Thankfully,

-Robert

[Galvani (jan-kozak)]

Actually it didn't at all, the problem is certainly multiple screens. You can see the windows that were open and even worse you can freely click aything you see!!! Keyboard input is redirected to lock screen. At least. I believe it comes mainly if put in standby with second screen connected and resuming with second screen disconnected or another one connected.

Output of the above mentioned before standby+after resuming:

 dbus-monitor --session "interface='org.gnome.ScreenSaver'"
signal time=1474962360.370328 sender=org.freedesktop.DBus -> destination=:1.179 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
   string ":1.179"
signal time=1474962360.370400 sender=org.freedesktop.DBus -> destination=:1.179 serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameLost
   string ":1.179"

Even text is garbled.
Jan

[Or Schiro (orschiro)]

Dear all,

For me the issue returned as well, recently.

-Robert

[roemer2201 (roemer2201)]

I have the same problem as well. I'm using two screens, but I think running a virtual machine (virtual box for me) where the mouse cursor is caught inside, might also be related to the problems.

[roemer2201 (roemer2201)]

I have the same problem as well. I'm using two screens, but I think running a virtual machine (virtual box for me) where the mouse cursor is caught inside, might also be related to the problems.

When the monitor goes to sleep (after 10 minutes) and I come back to my pc later, I press a key or move the mouse to wake it up. I see the desktop, where I left it and as soon as I do the first click, the lockscreen appears and instantly fades without asking for the password. So my pc is not protected, if I do not manually lock it. On a bad day the desktop session crashed completely and all unsaved work in gone and running vm's are killed

[Tobias Volfing (tobiasvv)]

I'm experiencing the lock screen not working as well. Sometimes when I return to my computer, after moving the mouse the screen turns on and I can see all the windows the way they were before I locked it, and after clicking the first time the lock screen appears.

The click is registered, and as such my computer is not protected in anyway. I mostly have virtual machines running (possibly with the mouse captured), and I don't know if it happens without.

I have also experienced a complete system freeze in the above situation, where instead of the lock screen returning, it just freezes the entire system.