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     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to