← Back to team overview

touch-packages team mailing list archive

Re: [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

 

You need to enable accessibility (e.g. on screen keyabord) from the control
center.

2014-12-09 14:56 GMT+01:00 msp3k <peek@xxxxxxxxxxx>:

> 1) Maybe I'm just derping, but how do I run gnome-screensaver?
>
> $ ps -ef | grep -i screensaver
> peek     24604 24163  0 08:51 pts/47   00:00:00 grep -i screensaver
> $ gnome-screensaver
>
> ** (gnome-screensaver:24665): WARNING **: screensaver already running in
> this session
>
> 2) If this is an LDAP issue, then why does it only affect 1 out of my
> 110 users?
>
>
> I thank you guys for your hard work on this, and if there is anything I
> can do to help track down the source of the problem let me know.
>
>
> Michael Peek
>
> On 12/08/2014 01:57 PM, Andrea Azzarone wrote:
> >> All these services (login, lightdm, polkit-1, sudo, sshd) are working
> > fine.
> >
> > They run as root that's why.  Try to lock using gnome-screensaver
> > (without running it as root!) and let me know if you can unlock the
> > screen.
> >
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1311316
>
> Title:
>   After locking screen there is no input field to type password for
>   unlock
>
> Status in Unity:
>   Confirmed
> Status in Unity 7.2 series:
>   Confirmed
> Status in unity package in Ubuntu:
>   Fix Released
>
> Bug description:
>   Sometimes (but not always) after locking the screen there is the
>   situation not having any input field where I can type the password to
>   unlock the session again. The shaded gray area simply does not have
>   the input field. I can't do anything, I have to switch to text console
>   and stop/start lightdm service to cure the problem loosing all of my
>   session :(
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: unity 7.2.0+14.04.20140416-0ubuntu1
>   ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
>   Uname: Linux 3.13.0-24-generic i686
>   ApportVersion: 2.14.1-0ubuntu3
>   Architecture: i386
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CurrentDesktop: Unity
>   Date: Tue Apr 22 22:17:57 2014
>   InstallationDate: Installed on 2012-03-03 (780 days ago)
>   InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386
> (20110427.1)
>   SourcePackage: unity
>   UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions
>


-- 
Andrea Azzarone
http://launchpad.net/~andyrock
http://wiki.ubuntu.com/AndreaAzzarone


** Description changed:

+ *** IMPORTANT **
+ If you can reproduce this bug please be sure to provide the following info:
+ 1. Do you use a multi-head setup?
+ 2. Can you reproduce all the time?
+ 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that?
+ 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information)
+ 5. Please specify the unity version 
+ *** END IMPORTANT **
+ 
  Sometimes (but not always) after locking the screen there is the
  situation not having any input field where I can type the password to
  unlock the session again. The shaded gray area simply does not have the
  input field. I can't do anything, I have to switch to text console and
  stop/start lightdm service to cure the problem loosing all of my session
  :(
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 22 22:17:57 2014
  InstallationDate: Installed on 2012-03-03 (780 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1311316

Title:
  After locking screen there is no input field to type password for
  unlock

Status in Unity:
  Confirmed
Status in Unity 7.2 series:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  *** IMPORTANT **
  If you can reproduce this bug please be sure to provide the following info:
  1. Do you use a multi-head setup?
  2. Can you reproduce all the time?
  3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that?
  4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information)
  5. Please specify the unity version 
  *** END IMPORTANT **

  Sometimes (but not always) after locking the screen there is the
  situation not having any input field where I can type the password to
  unlock the session again. The shaded gray area simply does not have
  the input field. I can't do anything, I have to switch to text console
  and stop/start lightdm service to cure the problem loosing all of my
  session :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 22 22:17:57 2014
  InstallationDate: Installed on 2012-03-03 (780 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions


Follow ups

References