[Desktop-packages] [Bug 1849081] Re: ZSH shells break Login screen
More updates. There was an issue with Powerlevel, at least as documented here. https://github.com/romkatv/powerlevel10k/issues/280 However, the issue seems to be lower level. An important issue seems to happen here: include this line at the top of .bashrc when using zsh ``` exec zsh ``` It seems this somehow breaks the login shell. I was able to reproduce this on my other laptop with 18.04. As long as that line is not there, the latest version of ZSH + oh_my_zsh + Powerlevel10k are working fine. This bug may be closed at your discretion, but it seems that there is benefit in somehow find out how to avoid this breaking in such case . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1849081 Title: ZSH shells break Login screen Status in gnome-keyring package in Ubuntu: New Bug description: There's a bug that affects gnome-keyring, and i'll describe the steps i've done to reproduce it twice, although i don't have full details as to what exactly is causing it. Issue can be summarized as follows: On Ubuntu 19.10, but not at least 18.04 (another computer i have using the older release), there's an issue that prevents the user to login to a gnome session The issue shows up when checking the session manager: ``` service gdm3 status Process: ExecStartPre: /usr/share/gdm/generate-config (code=exited,status=0/SUCCESS) Process: ExecStartPre: /usr/lib/gdm3/gdm-wait-for-drm (code=exited,status=0/SUCCESS) ... gdm-password: gkr-pam: unable to local control file ``` Relevant components: * gdm3 3.34.1-1 * gnome-shell 3.34.1-1 * gnome-keyring 3.34.0-1 * zsh 5.77.1-ubuntu2 This does not occur on a fresh installation of Ubuntu. It only happens once some of these tools are installed: * zsh (ubuntu package https://packages.ubuntu.com/eoan/zsh , manually change shell for user) - https://askubuntu.com/questions/131823/how-to-make-zsh-the-default-shell * oh-my-zsh (brings in lots of plugins, although only git was sourced) - https://github.com/robbyrussell/oh-my-zsh/wiki/Installing-ZSH * powerlevel10k (shell theme ) - https://github.com/romkatv/powerlevel10k The tools would appear to work fine, until you reboot the machine, and are asked to login, at which point gkr-pam complains that it can't locate control file. Unfortunately i don't have better details because eventually i broke so much my login that i decided to reinstall the system from scratch. Upon installation, i started from fresh, with no zsh, and everything worked. Once zsh was installed, it will no longer work. A fix for this was to revert to bash shell. The key change was to no include this line at the top of .bashrc ``` #exec zsh ``` So i can confirm the issue is there, but that's as far as i got after several hours of investigations. I appreciate that this bug may not be a gnome-keyring specific bug, but seems that its the one been affected anyways. https://gitlab.gnome.org/GNOME/gnome-keyring/issues/28 https://gitlab.gnome.org/GNOME/gnome-keyring/issues/26 https://github.com/GNOME/gnome-keyring/blob/master/pam/gkr-pam-module.c#L676 https://github.com/GNOME/gnome-keyring/blob/master/pam/gkr-pam-module.c#L847 https://github.com/GNOME/gnome-keyring/commit/443a821cba105e8f277828a67b3d019b67f1324a https://github.com/GNOME/gnome-keyring/commit/b22d058a055ec3e0f31ae16417f16b42baadb42f https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128 https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1818616 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1849081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818616] Re: gnome-keyring is not unlocked upon gdm login in disco
*** This bug is a duplicate of bug 1817128 *** https://bugs.launchpad.net/bugs/1817128 I've summarized my investigation so far in this new bug report: It seems a combination of ZSH, Oh-My-Zsh and possibly Powerlevel10k break the login screen somehow. https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1849081 https://github.com/robbyrussell/oh-my-zsh/issues/8296 https://github.com/romkatv/powerlevel10k/issues/280 ** Bug watch added: github.com/robbyrussell/oh-my-zsh/issues #8296 https://github.com/robbyrussell/oh-my-zsh/issues/8296 ** Bug watch added: github.com/romkatv/powerlevel10k/issues #280 https://github.com/romkatv/powerlevel10k/issues/280 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1818616 Title: gnome-keyring is not unlocked upon gdm login in disco Status in gdm3 package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Status in pam package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or local configuration. As far as I recall, I should be running just "stock" configs. I did not install system with disco, but upgraded to disco throughout development series. Upon booting, and logging in through gdm3, I get a pop-up from gnome- keyring instructing me that gnome-keyring was not unlocked upon logging, and I have to re-enter the password again. The password for the account and the gnome-keyring are the same, and the keyring should be auto-unlocked. Looking at the journal, there is a red warning from gdm: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor XDG_RUNTIME_DIR are set. The messages after it are: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory /run/user/1000... Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox. Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory /run/user/1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000... Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for Ubuntu Report. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate management daemon. Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System. Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000. Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default. Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms. Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox. I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see that XDG_RUNTIME_DIR to be created and set by logind. From the above logs I can see that it happens _after_ gdm-password is done. So It seems like something has changed in the stack, and gdm login / libpam-gnome-keyring no longer use systemd-logind PAM module to be part of the PAM session. But I'm not sure what has changed to cause this (gdm, gnome-keyring, pam, systemd). Am I the only one with this issue? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 Cu
[Desktop-packages] [Bug 1817128] Re: gnome-keyring not automatically unlocked on login
Thanks, I've raised several issues to try to fix this problem: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1849081 https://github.com/robbyrussell/oh-my-zsh/issues/8296 https://github.com/romkatv/powerlevel10k/issues/280 ** Bug watch added: github.com/robbyrussell/oh-my-zsh/issues #8296 https://github.com/robbyrussell/oh-my-zsh/issues/8296 ** Bug watch added: github.com/romkatv/powerlevel10k/issues #280 https://github.com/romkatv/powerlevel10k/issues/280 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1817128 Title: gnome-keyring not automatically unlocked on login Status in gnome-keyring package in Ubuntu: Fix Released Bug description: Hi After initializing and filling the login screen, at the start screen prompts for password to unlock the session keyring. Is this normal on Ubuntu disk 19.04.02? Note: When filling the login screen to start the micro, should it not be unlocked automatically? Attached the image of the request I fired it. Thank you ** Hi Após inicialização e preenchimento da tela de login, ao iniciar a tela pede senha para desbloqueio do chaveiro de sessão. Isso é normal no Ubuntu disco 19.04.02? Obs: Quando do preenchimento da tela de login para iniciar o micro o desbloqueio não deveria ser automático? Em anexo a imagem da solicitação de desboquei-o. Obrigado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849081] Re: ZSH shells break Login screen
I've cross-posted this issue in the related tools since it's unclear which one causes it, but it's severe enough to make it worth triaging it. https://github.com/robbyrussell/oh-my-zsh/issues/8296 https://github.com/romkatv/powerlevel10k/issues/280 ** Bug watch added: github.com/robbyrussell/oh-my-zsh/issues #8296 https://github.com/robbyrussell/oh-my-zsh/issues/8296 ** Bug watch added: github.com/romkatv/powerlevel10k/issues #280 https://github.com/romkatv/powerlevel10k/issues/280 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1849081 Title: ZSH shells break Login screen Status in gnome-keyring package in Ubuntu: New Bug description: There's a bug that affects gnome-keyring, and i'll describe the steps i've done to reproduce it twice, although i don't have full details as to what exactly is causing it. Issue can be summarized as follows: On Ubuntu 19.10, but not at least 18.04 (another computer i have using the older release), there's an issue that prevents the user to login to a gnome session The issue shows up when checking the session manager: ``` service gdm3 status Process: ExecStartPre: /usr/share/gdm/generate-config (code=exited,status=0/SUCCESS) Process: ExecStartPre: /usr/lib/gdm3/gdm-wait-for-drm (code=exited,status=0/SUCCESS) ... gdm-password: gkr-pam: unable to local control file ``` Relevant components: * gdm3 3.34.1-1 * gnome-shell 3.34.1-1 * gnome-keyring 3.34.0-1 * zsh 5.77.1-ubuntu2 This does not occur on a fresh installation of Ubuntu. It only happens once some of these tools are installed: * zsh (ubuntu package https://packages.ubuntu.com/eoan/zsh , manually change shell for user) - https://askubuntu.com/questions/131823/how-to-make-zsh-the-default-shell * oh-my-zsh (brings in lots of plugins, although only git was sourced) - https://github.com/robbyrussell/oh-my-zsh/wiki/Installing-ZSH * powerlevel10k (shell theme ) - https://github.com/romkatv/powerlevel10k The tools would appear to work fine, until you reboot the machine, and are asked to login, at which point gkr-pam complains that it can't locate control file. Unfortunately i don't have better details because eventually i broke so much my login that i decided to reinstall the system from scratch. Upon installation, i started from fresh, with no zsh, and everything worked. Once zsh was installed, it will no longer work. A fix for this was to revert to bash shell. The key change was to no include this line at the top of .bashrc ``` #exec zsh ``` So i can confirm the issue is there, but that's as far as i got after several hours of investigations. I appreciate that this bug may not be a gnome-keyring specific bug, but seems that its the one been affected anyways. https://gitlab.gnome.org/GNOME/gnome-keyring/issues/28 https://gitlab.gnome.org/GNOME/gnome-keyring/issues/26 https://github.com/GNOME/gnome-keyring/blob/master/pam/gkr-pam-module.c#L676 https://github.com/GNOME/gnome-keyring/blob/master/pam/gkr-pam-module.c#L847 https://github.com/GNOME/gnome-keyring/commit/443a821cba105e8f277828a67b3d019b67f1324a https://github.com/GNOME/gnome-keyring/commit/b22d058a055ec3e0f31ae16417f16b42baadb42f https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128 https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1818616 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1849081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849081] [NEW] ZSH shells break Login screen
Public bug reported: There's a bug that affects gnome-keyring, and i'll describe the steps i've done to reproduce it twice, although i don't have full details as to what exactly is causing it. Issue can be summarized as follows: On Ubuntu 19.10, but not at least 18.04 (another computer i have using the older release), there's an issue that prevents the user to login to a gnome session The issue shows up when checking the session manager: ``` service gdm3 status Process: ExecStartPre: /usr/share/gdm/generate-config (code=exited,status=0/SUCCESS) Process: ExecStartPre: /usr/lib/gdm3/gdm-wait-for-drm (code=exited,status=0/SUCCESS) ... gdm-password: gkr-pam: unable to local control file ``` Relevant components: * gdm3 3.34.1-1 * gnome-shell 3.34.1-1 * gnome-keyring 3.34.0-1 * zsh 5.77.1-ubuntu2 This does not occur on a fresh installation of Ubuntu. It only happens once some of these tools are installed: * zsh (ubuntu package https://packages.ubuntu.com/eoan/zsh , manually change shell for user) - https://askubuntu.com/questions/131823/how-to-make-zsh-the-default-shell * oh-my-zsh (brings in lots of plugins, although only git was sourced) - https://github.com/robbyrussell/oh-my-zsh/wiki/Installing-ZSH * powerlevel10k (shell theme ) - https://github.com/romkatv/powerlevel10k The tools would appear to work fine, until you reboot the machine, and are asked to login, at which point gkr-pam complains that it can't locate control file. Unfortunately i don't have better details because eventually i broke so much my login that i decided to reinstall the system from scratch. Upon installation, i started from fresh, with no zsh, and everything worked. Once zsh was installed, it will no longer work. A fix for this was to revert to bash shell. The key change was to no include this line at the top of .bashrc ``` #exec zsh ``` So i can confirm the issue is there, but that's as far as i got after several hours of investigations. I appreciate that this bug may not be a gnome-keyring specific bug, but seems that its the one been affected anyways. https://gitlab.gnome.org/GNOME/gnome-keyring/issues/28 https://gitlab.gnome.org/GNOME/gnome-keyring/issues/26 https://github.com/GNOME/gnome-keyring/blob/master/pam/gkr-pam-module.c#L676 https://github.com/GNOME/gnome-keyring/blob/master/pam/gkr-pam-module.c#L847 https://github.com/GNOME/gnome-keyring/commit/443a821cba105e8f277828a67b3d019b67f1324a https://github.com/GNOME/gnome-keyring/commit/b22d058a055ec3e0f31ae16417f16b42baadb42f https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128 https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1818616 ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1849081 Title: ZSH shells break Login screen Status in gnome-keyring package in Ubuntu: New Bug description: There's a bug that affects gnome-keyring, and i'll describe the steps i've done to reproduce it twice, although i don't have full details as to what exactly is causing it. Issue can be summarized as follows: On Ubuntu 19.10, but not at least 18.04 (another computer i have using the older release), there's an issue that prevents the user to login to a gnome session The issue shows up when checking the session manager: ``` service gdm3 status Process: ExecStartPre: /usr/share/gdm/generate-config (code=exited,status=0/SUCCESS) Process: ExecStartPre: /usr/lib/gdm3/gdm-wait-for-drm (code=exited,status=0/SUCCESS) ... gdm-password: gkr-pam: unable to local control file ``` Relevant components: * gdm3 3.34.1-1 * gnome-shell 3.34.1-1 * gnome-keyring 3.34.0-1 * zsh 5.77.1-ubuntu2 This does not occur on a fresh installation of Ubuntu. It only happens once some of these tools are installed: * zsh (ubuntu package https://packages.ubuntu.com/eoan/zsh , manually change shell for user) - https://askubuntu.com/questions/131823/how-to-make-zsh-the-default-shell * oh-my-zsh (brings in lots of plugins, although only git was sourced) - https://github.com/robbyrussell/oh-my-zsh/wiki/Installing-ZSH * powerlevel10k (shell theme ) - https://github.com/romkatv/powerlevel10k The tools would appear to work fine, until you reboot the machine, and are asked to login, at which point gkr-pam complains that it can't locate control file. Unfortunately i don't have better details because eventually i broke so much my login that i decided to reinstall the system from scratch. Upon installation, i started from fresh, with no zsh, and everything worked. Once zsh was installed, it will no longer work. A fix for this was to revert to bash shell. The key change was to no include this line at the top of .bashrc ```
[Desktop-packages] [Bug 1817128] Re: gnome-keyring not automatically unlocked on login
Checking service status indicates the failures: ``` service gdm3 status Process: ExecStartPre: /usr/share/gdm/generate-config (code=exited,status=0/SUCCESS) Process: ExecStartPre: /usr/lib/gdm3/gdm-wait-for-drm (code=exited,status=0/SUCCESS) ... gdm-password: gkr-pam: unable to local control file ``` Relevant components: * gdm3 3.34.1-1 * gnome-shell 3.34.1-1 * gnome-keyring 3.34.0-1 Also tried: /etc/gdm/custom.conf # Enable automatic login for user [daemon] AutomaticLogin=username AutomaticLoginEnable=True but this lead to a either a black screen with a mouse pointer, or after resetting the dconf ``` dconf reset -f / ``` it would eventually crash and had to be hard rebooted. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1817128 Title: gnome-keyring not automatically unlocked on login Status in gnome-keyring package in Ubuntu: Fix Released Bug description: Hi After initializing and filling the login screen, at the start screen prompts for password to unlock the session keyring. Is this normal on Ubuntu disk 19.04.02? Note: When filling the login screen to start the micro, should it not be unlocked automatically? Attached the image of the request I fired it. Thank you ** Hi Após inicialização e preenchimento da tela de login, ao iniciar a tela pede senha para desbloqueio do chaveiro de sessão. Isso é normal no Ubuntu disco 19.04.02? Obs: Quando do preenchimento da tela de login para iniciar o micro o desbloqueio não deveria ser automático? Em anexo a imagem da solicitação de desboquei-o. Obrigado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818616] Re: gnome-keyring is not unlocked upon gdm login in disco
*** This bug is a duplicate of bug 1817128 *** https://bugs.launchpad.net/bugs/1817128 Filed report as well on Gnome: https://gitlab.gnome.org/GNOME/gnome-keyring/issues/28 Relevant components: * gdm3 3.34.1-1 * gnome-shell 3.34.1-1 * gnome-keyring 3.34.0-1 So, no lightdm, unlike this similar issue: https://github.com/canonical/lightdm/issues/70 they also suggested that the dconf may have become corrupted. I've tried as well: ``` mv .config/dconf/user ~/.config/dconf/user.bak ``` But didn't work. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-keyring/issues #28 https://gitlab.gnome.org/GNOME/gnome-keyring/issues/28 ** Bug watch added: github.com/canonical/lightdm/issues #70 https://github.com/canonical/lightdm/issues/70 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1818616 Title: gnome-keyring is not unlocked upon gdm login in disco Status in gdm3 package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Status in pam package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or local configuration. As far as I recall, I should be running just "stock" configs. I did not install system with disco, but upgraded to disco throughout development series. Upon booting, and logging in through gdm3, I get a pop-up from gnome- keyring instructing me that gnome-keyring was not unlocked upon logging, and I have to re-enter the password again. The password for the account and the gnome-keyring are the same, and the keyring should be auto-unlocked. Looking at the journal, there is a red warning from gdm: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor XDG_RUNTIME_DIR are set. The messages after it are: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory /run/user/1000... Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox. Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory /run/user/1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000... Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for Ubuntu Report. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate management daemon. Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System. Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000. Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default. Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms. Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox. I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see that XDG_RUNTIME_DIR to be created and set by logind. From the above logs I can see that it happens _after_ gdm-password is done. So It seems like something has changed in the stack, and gdm login / libpam-gnome-keyring no longer use systemd-logind PAM module to be part of the PAM session. But I'm not sure what has changed to cause this (gdm, gnome-keyring, pam, systemd). Am I the only one with this issue? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl
[Desktop-packages] [Bug 1817128] Re: gnome-keyring not automatically unlocked on login
I can see that this problem is still present on eoan-ermine. I upgraded from a development version to the latest 19.10 After several configurations of my shell, including zsh, oh-my-ssh and others, after trying to login this morning, the issue appeared. no system update, but a few small installations. I'm unable to login via graphical interface, but able to do so on a separate terminal (CTRL+ALT+F2) directly to the terminal. service gdm3 status shows the service active but shows errors: gdm3: GDMDisplay: Session never registered, failing gdm-password: gkr-pam: unable to locate daemon control file gdm-password: pam_unix(gdm-password: session): session opened for user x by uid=0 and continues with the same error How to solve this? at the moment i can only use terminal based login, no UI -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1817128 Title: gnome-keyring not automatically unlocked on login Status in gnome-keyring package in Ubuntu: Fix Released Bug description: Hi After initializing and filling the login screen, at the start screen prompts for password to unlock the session keyring. Is this normal on Ubuntu disk 19.04.02? Note: When filling the login screen to start the micro, should it not be unlocked automatically? Attached the image of the request I fired it. Thank you ** Hi Após inicialização e preenchimento da tela de login, ao iniciar a tela pede senha para desbloqueio do chaveiro de sessão. Isso é normal no Ubuntu disco 19.04.02? Obs: Quando do preenchimento da tela de login para iniciar o micro o desbloqueio não deveria ser automático? Em anexo a imagem da solicitação de desboquei-o. Obrigado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818616] Re: gnome-keyring is not unlocked upon gdm login in disco
*** This bug is a duplicate of bug 1817128 *** https://bugs.launchpad.net/bugs/1817128 I've reproduced this bug on eoan-ermine. See my comments on the related bug report #1817128 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1818616 Title: gnome-keyring is not unlocked upon gdm login in disco Status in gdm3 package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Status in pam package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or local configuration. As far as I recall, I should be running just "stock" configs. I did not install system with disco, but upgraded to disco throughout development series. Upon booting, and logging in through gdm3, I get a pop-up from gnome- keyring instructing me that gnome-keyring was not unlocked upon logging, and I have to re-enter the password again. The password for the account and the gnome-keyring are the same, and the keyring should be auto-unlocked. Looking at the journal, there is a red warning from gdm: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor XDG_RUNTIME_DIR are set. The messages after it are: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory /run/user/1000... Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox. Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory /run/user/1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000... Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for Ubuntu Report. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate management daemon. Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System. Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000. Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default. Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms. Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox. I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see that XDG_RUNTIME_DIR to be created and set by logind. From the above logs I can see that it happens _after_ gdm-password is done. So It seems like something has changed in the stack, and gdm login / libpam-gnome-keyring no longer use systemd-logind PAM module to be part of the PAM session. But I'm not sure what has changed to cause this (gdm, gnome-keyring, pam, systemd). Am I the only one with this issue? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 5 08:22:01 2019 InstallationDate: Installed on 2016-01-26 (1134 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2019-01-15 (48 days ago) To manage notifications about this bug go to: https://bugs.launchpad.ne