gnome-keyring not automatically unlocked on login

Bug #1817128 reported by Edson José dos Santos
98
This bug affects 19 people
Affects Status Importance Assigned to Milestone
gnome-keyring (Ubuntu)
Fix Released
High
Sebastien Bacher

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

Revision history for this message
Edson José dos Santos (serial.com) wrote :
Jeremy Bícha (jbicha)
affects: gnome-software (Ubuntu) → gnome-keyring (Ubuntu)
Changed in gnome-keyring (Ubuntu):
importance: Undecided → High
status: New → Confirmed
summary: - After Login screen filled in - Ubuntu Disco 19.04.2
+ gnome-keyring not automatically unlocked on login
tags: added: disco
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Thank you for taking the time to file this bug and help make Ubuntu better.

I have reported this to GNOME at
https://gitlab.gnome.org/GNOME/gnome-keyring/issues/26

Changed in gnome-keyring (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Edson José dos Santos (serial.com) wrote :

Hi Jeremy

Thank you

tags: added: rls-dd-incoming
Changed in gnome-keyring (Ubuntu):
assignee: nobody → Sebastien Bacher (seb128)
Revision history for this message
Edson José dos Santos (serial.com) wrote :

The problem still continues, see attachment

Thanks Sebastian

*************
O problema ainda continua, vide anexo

Obrigado Sebastian

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-keyring - 3.31.91-1ubuntu1

---------------
gnome-keyring (3.31.91-1ubuntu1) disco; urgency=medium

  * Sync with Debian. Remaining changes:
    - debian/user/*, debian/gnome-keyring.links, debian/gnome-keyring.install:
      + Install units to start gnome-keyring with systemd if the session
        is using it

gnome-keyring (3.31.91-1) experimental; urgency=medium

  * New upstream development release
    - Fix loging keyring not automatically unlocked on log in (LP: #1817128)

 -- Jeremy Bicha <email address hidden> Sat, 02 Mar 2019 08:15:13 -0500

Changed in gnome-keyring (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Edson José dos Santos (serial.com) wrote :

Hello guys

Perfect!

Many thanks to all involved for the prompt resolution of the problem.

Revision history for this message
Edson José dos Santos (serial.com) wrote :

Hello guys

The problem returned, see attachment

Your Considerations

***********
Olá Pessoal

O problema retornou, vide anexo

Suas Considerações

Revision history for this message
Fernando Racca (fracca) wrote :

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

Revision history for this message
Fernando Racca (fracca) wrote :

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.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This bug was closed in comment #5. If you have any ongoing issues then please open new bugs.

Revision history for this message
Fernando Racca (fracca) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.