[Bug 1292217] Re: lightdm screen lock has triggered but keyboard is still connected to the main session

2014-04-08 Thread Sebastien Bacher
The issue initially reported has been fixed in that update https://launchpad.net/ubuntu/+source/unity/7.1.2+14.04.20140313-0ubuntu1 @Nelson: can you describe exactly what you did and what happened? the lock again issue is another bug as pointed in the previous comment ** Changed in: unity

[Bug 1292217] Re: lightdm screen lock has triggered but keyboard is still connected to the main session

2014-04-03 Thread Jamie Strandboge
** Tags added: rls-t-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292217 Title: lightdm screen lock has triggered but keyboard is still connected to the main session To manage

[Bug 1292217] Re: lightdm screen lock has triggered but keyboard is still connected to the main session

2014-03-31 Thread Nelson Elhage
This also just affected me. Possibly-relevant detail from my environment: If I explicitly lock the screen and then also wait for a lock timeout, I somehow end up with two lock screens -- I unlock the machine, I can interact with the desktop for a few seconds, and then a second lock screen pops

[Bug 1292217] Re: lightdm screen lock has triggered but keyboard is still connected to the main session

2014-03-31 Thread Seth Arnold
Nelson, thanks; I believe the double-lock bug is tracked here: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1292451 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292217 Title:

[Bug 1292217] Re: lightdm screen lock has triggered but keyboard is still connected to the main session

2014-03-20 Thread Alberto Salvia Novella
** Changed in: unity (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292217 Title: lightdm screen lock has triggered but keyboard is still connected to the

[Bug 1292217] Re: lightdm screen lock has triggered but keyboard is still connected to the main session

2014-03-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292217 Title:

[Bug 1292217] Re: lightdm screen lock has triggered but keyboard is still connected to the main session

2014-03-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292217 Title:

[Bug 1292217] Re: lightdm screen lock has triggered but keyboard is still connected to the main session

2014-03-14 Thread Donarsson
** Changed in: unity (Ubuntu) Status: Confirmed = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292217 Title: lightdm screen lock has triggered but keyboard is still connected to the

[Bug 1292217] Re: lightdm screen lock has triggered but keyboard is still connected to the main session

2014-03-13 Thread Sebastien Bacher
the screen locking is done by unity, not lightdm. How do you notice that the keybinding are active, is there any visible effect? Does it happen every time? ** Package changed: lightdm (Ubuntu) = unity (Ubuntu) ** Tags added: lockscreen -- You received this bug notification because you are a

[Bug 1292217] Re: lightdm screen lock has triggered but keyboard is still connected to the main session

2014-03-13 Thread Andy Whitcroft
I am unsure if it is reproducible as yet. I noticed when the *'s did not appear on unlock attempt. I then noticed ALT-Tab was working, when it should not be. Then I sleected my IRC client and blind selected a private channel and sent myself a message, which I received on another machine. --