FS#37719 - [gdm] Login in chromium when is active autologin of Gnome
Attached to Project:
Arch Linux
Opened by Isaac Gallart (igallart) - Sunday, 10 November 2013, 14:52 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Saturday, 08 February 2014, 00:28 GMT
Opened by Isaac Gallart (igallart) - Sunday, 10 November 2013, 14:52 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Saturday, 08 February 2014, 00:28 GMT
|
Details
Description: I updated gnome, when I open chromium and with
autologin from GDM from gnome, always is show the popup to
that enter the password of login.
Additional info: Chromium: 30.0.1599.114-1 Seahorse: 3.10.1-1 Steps to reproduce: Activate autologin from gnome and enter in chromium |
This task depends upon
Closed by Gerardo Exequiel Pozzi (djgera)
Saturday, 08 February 2014, 00:28 GMT
Reason for closing: Not a bug
Saturday, 08 February 2014, 00:28 GMT
Reason for closing: Not a bug
Comment by
Jelle van der Waa (jelly) - Monday,
11 November 2013, 14:43 GMT
I really don't get the bugreport. You autologin in GNOME and then
launch chromium??
Comment by
Isaac Gallart (igallart) - Monday,
11 November 2013, 18:27 GMT
I have enabled in account users Automatic Login. And when I open
Chromium, is showed the windows to enter the password login.
Comment by Ionut Biru (wonder) -
Monday, 11 November 2013, 18:51 GMT
of course is doing that, the passwords are stored in the keyring
and you need to type your password in order to unlock the keyring.
Comment by
Isaac Gallart (igallart) - Monday,
11 November 2013, 21:39 GMT
Before upgrading gnome, that was not shown
Comment by
Gerardo Exequiel Pozzi (djgera) -
Friday, 07 February 2014, 00:59 GMT
- Field changed: Summary (Login in chromium when is active autologin of Gnome → [gdm] Login in chromium when is active autologin of Gnome)
- Field changed: Status (Unconfirmed → Waiting on Response)
- Task assigned to Jan de Groot (JGC)
status?
Comment by
Isaac Gallart (igallart) - Friday,
07 February 2014, 08:22 GMT
Well, I set the password in seahorse a empty and it was resolved.
I suspect it was a failure of seahorse...
Captura de pantalla de 2013-1...
(69.3 KiB)