touch-packages team mailing list archive

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

To: touch-packages@xxxxxxxxxxxxxxxxxxx
From: Andrea Azzarone <1311316@xxxxxxxxxxxxxxxxxx>
Date: Tue, 17 Feb 2015 16:19:18 -0000
Reply-to: Bug 1311316 <1311316@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
It was a login or a lock/unlock?
On 17 Feb 2015 16:21, "Burko" <rs205@xxxxxx> wrote:

> I updated my machine recently to the current Unity 7.2.4 and  this
> solved this issue for some time.
>
> BUT: Now I am experiencing it again, exactly 50 % ( that is actually 25 %
> of time, see below) of times I log into my maschine. My case if different,
> though. When my Laptop wakes up from sleep I always have to log in two
> times each time. Meaning I enter my passphrase, the screen unlocks, I see
> my screen 1-2 seconds, the screen starts flickering  and then it locks
> again, this time without the input field. I then close my lid so that the
> machine hibernates again. I wake it up again, and have again to unlock the
> machine  two times. This time I have in both cases an input field.
> So, you could say I have to log in four times every time I want to use my
> machine. This is always reproducable, btw.
>
> I did not reboot the machine so far, meaning it is up for some days now,
> where in the beginning it had it prefectly working with just one needed
> attempt to unlock the machine.
>
>
> I attach the Auth.log entry from the last login, which seems a bit weird...
>
>
> Feb 17 15:58:43 ubuntu-sklave systemd-logind[520]: Lid opened.
> Feb 17 15:58:43 ubuntu-sklave systemd-logind[520]: Operation finished.
> Feb 17 15:58:44 ubuntu-sklave gnome-keyring-daemon[16581]: couldn't set
> environment variable in session: Keine derartige Methode »Setenv«
> Feb 17 15:58:44 ubuntu-sklave gnome-keyring-daemon[16581]: keyring alias
> directory: /var/lib/lightdm/.local/share/keyrings
> Feb 17 15:58:47 ubuntu-sklave lightdm: pam_unix(lightdm:auth):
> authentication failure; logname= uid=0 euid=0 tty=:1 ruser= rhost=
> user=gameaccount
> Feb 17 15:58:47 ubuntu-sklave lightdm: pam_winbind(lightdm:auth): getting
> password (0x00000388)
> Feb 17 15:58:47 ubuntu-sklave lightdm: pam_winbind(lightdm:auth):
> pam_get_item returned a password
> Feb 17 15:58:47 ubuntu-sklave lightdm: pam_winbind(lightdm:auth): request
> wbcLogonUser failed: WBC_ERR_AUTH_ERROR, PAM error: PAM_USER_UNKNOWN (10),
> NTSTATUS: NT_STATUS_NO_SUCH_USER, Error message was: No such user
> Feb 17 15:58:47 ubuntu-sklave dbus[400]: [system] Rejected send message, 7
> matched rules; type="method_return", sender=":1.15" (uid=0 pid=1169
> comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground")
> interface="(unset)" member="(unset)" error name="(unset)"
> requested_reply="0" destination=":1.5" (uid=0 pid=964 comm="NetworkManager
> ")
> Feb 17 15:58:49 ubuntu-sklave lightdm: pam_succeed_if(lightdm:auth):
> requirement "user ingroup nopasswdlogin" not met by user "gameaccount"
> Feb 17 15:58:53 ubuntu-sklave lightdm: pam_kwallet(lightdm:auth):
> pam_sm_authenticate
> Feb 17 15:58:54 ubuntu-sklave lightdm: pam_kwallet(lightdm:setcred):
> pam_sm_setsecred
> Feb 17 15:58:54 ubuntu-sklave lightdm: pam_unix(lightdm-greeter:session):
> session closed for user lightdm
> Feb 17 15:58:54 ubuntu-sklave lightdm:
> pam_kwallet(lightdm-greeter:session): pam_sm_close_session
> Feb 17 15:58:54 ubuntu-sklave lightdm:
> pam_kwallet(lightdm-greeter:setcred): pam_sm_setsecred
> Feb 17 15:58:59 ubuntu-sklave lightdm:
> pam_kwallet(lightdm-greeter:setcred): pam_sm_setsecred
> Feb 17 15:58:59 ubuntu-sklave lightdm: pam_unix(lightdm-greeter:session):
> session opened for user lightdm by (uid=0)
> Feb 17 15:58:59 ubuntu-sklave systemd-logind[520]: New session c39 of user
> lightdm.
> Feb 17 15:58:59 ubuntu-sklave lightdm:
> pam_ck_connector(lightdm-greeter:session): nox11 mode, ignoring PAM_TTY :1
> Feb 17 15:58:59 ubuntu-sklave lightdm:
> pam_kwallet(lightdm-greeter:session): pam_sm_open_session
> Feb 17 15:58:59 ubuntu-sklave lightdm:
> pam_kwallet(lightdm-greeter:session): pam_kwallet: open_session called
> without kwallet_key
> Feb 17 15:58:59 ubuntu-sklave systemd-logind[520]: Lid closed.
> Feb 17 15:58:59 ubuntu-sklave systemd-logind[520]: Suspending...
> Feb 17 15:59:00 ubuntu-sklave dbus[400]: [system] Rejected send message, 7
> matched rules; type="method_return", sender=":1.15" (uid=0 pid=1169
> comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground")
> interface="(unset)" member="(unset)" error name="(unset)"
> requested_reply="0" destination=":1.5" (uid=0 pid=964 comm="NetworkManager
> ")
> Feb 17 15:59:00 ubuntu-sklave lightdm: pam_succeed_if(lightdm:auth):
> requirement "user ingroup nopasswdlogin" not met by user "gameaccount"
> Feb 17 15:59:04 ubuntu-sklave systemd-logind[520]: Delay lock is active
> but inhibitor timeout is reached.
> Feb 17 15:59:14 ubuntu-sklave systemd-logind[520]: Lid opened.
> Feb 17 15:59:14 ubuntu-sklave systemd-logind[520]: Operation finished.
> Feb 17 15:59:16 ubuntu-sklave gnome-keyring-daemon[17579]: couldn't set
> environment variable in session: Keine derartige Methode »Setenv«
> Feb 17 15:59:16 ubuntu-sklave gnome-keyring-daemon[17579]: keyring alias
> directory: /var/lib/lightdm/.local/share/keyrings
> Feb 17 15:59:16 ubuntu-sklave lightdm: pam_kwallet(lightdm:auth):
> pam_sm_authenticate
> Feb 17 15:59:17 ubuntu-sklave lightdm: pam_kwallet(lightdm:setcred):
> pam_sm_setsecred
> Feb 17 15:59:18 ubuntu-sklave lightdm: pam_unix(lightdm-greeter:session):
> session closed for user lightdm
> Feb 17 15:59:18 ubuntu-sklave lightdm:
> pam_kwallet(lightdm-greeter:session): pam_sm_close_session
> Feb 17 15:59:18 ubuntu-sklave lightdm:
> pam_kwallet(lightdm-greeter:setcred): pam_sm_setsecred
> Feb 17 15:59:19 ubuntu-sklave dbus[400]: [system] Rejected send message, 7
> matched rules; type="method_return", sender=":1.15" (uid=0 pid=1169
> comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground")
> interface="(unset)" member="(unset)" error name="(unset)"
> requested_reply="0" destination=":1.5" (uid=0 pid=964 comm="NetworkManager
> ")
> Feb 17 15:59:24 ubuntu-sklave lightdm:
> pam_kwallet(lightdm-greeter:setcred): pam_sm_setsecred
> Feb 17 15:59:24 ubuntu-sklave lightdm: pam_unix(lightdm-greeter:session):
> session opened for user lightdm by (uid=0)
> Feb 17 15:59:24 ubuntu-sklave systemd-logind[520]: New session c40 of user
> lightdm.
> Feb 17 15:59:24 ubuntu-sklave lightdm:
> pam_ck_connector(lightdm-greeter:session): nox11 mode, ignoring PAM_TTY :1
> Feb 17 15:59:24 ubuntu-sklave lightdm:
> pam_kwallet(lightdm-greeter:session): pam_sm_open_session
> Feb 17 15:59:24 ubuntu-sklave lightdm:
> pam_kwallet(lightdm-greeter:session): pam_kwallet: open_session called
> without kwallet_key
> Feb 17 15:59:24 ubuntu-sklave lightdm: pam_succeed_if(lightdm:auth):
> requirement "user ingroup nopasswdlogin" not met by user "gameaccount"
> Feb 17 15:59:28 ubuntu-sklave lightdm: pam_kwallet(lightdm:auth):
> pam_sm_authenticate
> Feb 17 15:59:30 ubuntu-sklave lightdm: pam_kwallet(lightdm:setcred):
> pam_sm_setsecred
> Feb 17 15:59:30 ubuntu-sklave lightdm: pam_unix(lightdm-greeter:session):
> session closed for user lightdm
> Feb 17 15:59:30 ubuntu-sklave lightdm:
> pam_kwallet(lightdm-greeter:session): pam_sm_close_session
> Feb 17 15:59:30 ubuntu-sklave lightdm:
> pam_kwallet(lightdm-greeter:setcred): pam_sm_setsecred
> Feb 17 16:10:57 ubuntu-sklave smbd[19025]: pam_unix(samba:session):
> session closed for user nobody
>
> --
> 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:
>   Fix Released
> Status in Unity 7.2 series:
>   In Progress
> Status in unity package in Ubuntu:
>   Fix Released
>
> Bug description:
>   *** IMPORTANT **
>
>   *** The fix is not included in TRUSTY. Will be included with next SRU.
>   ***
>
>   If you can reproduce this bug please be sure to provide the following
> info:
>   1. Do you use a multi-head setup? If yes, using just one monitor fixes
> the issue?
>   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
>

-- 
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:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  *** IMPORTANT **

  *** The fix is not included in TRUSTY. Will be included with next SRU.
  ***

  If you can reproduce this bug please be sure to provide the following info:
  1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue?
  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
References

[Bug 1311316] Re: After locking screen there is no input field to type password for unlock
From: Burko, 2015-02-17