| 2015-04-07 12:34:31 |
Laércio de Sousa |
bug |
|
|
added bug |
| 2015-04-07 12:34:43 |
Laércio de Sousa |
tags |
|
multiseat |
|
| 2015-04-09 20:54:20 |
Laércio de Sousa |
summary |
Timed autologin sometimes fails for some seats |
[Timed] Autologin fails if user is selected in user list |
|
| 2015-04-09 20:56:44 |
Laércio de Sousa |
description |
I work with a computer lab consisting of 9 CPUs with 2 seats each one. I have used Ubuntu 14.04 LTS on them and now I'm trying Ubuntu 15.04. In both cases, I set autologin as guest in all seats with a timeout of 60 seconds.
After some reboots, I've noticed that one of the seats stops performing autologin after the timeout. However, if I set autologin timeout to 0 on that seats, they perform autologin as expected.
Once timed autologin starts to fail on some seats, it won't go back to normal, even if I reboot or power off the computer. It only goes back to normal if I reinstall lightdm. |
I work with a computer lab consisting of 9 CPUs with 2 seats each one. I have used Ubuntu 14.04 LTS on them and now I'm trying Ubuntu 15.04. In both cases, I set autologin as guest in all seats with a timeout of 60 seconds.
After some reboots, I've noticed that one of the seats stops performing autologin after the timeout. However, if I set autologin timeout to 0 on that seats, they perform autologin as expected.
Once timed autologin starts to fail on some seats, it won't go back to normal, even if I reboot or power off the computer. It only goes back to normal if I reinstall lightdm.
[UPDATE] I realised that timed autologin actually fails if user in question (also applies for guest) is selected in user list when timeout reaches 0. However, if I select another user before timeout reaches 0, autologin for configured user works as expected.
Verified with lightdm-gtk-greeter. Not sure if it also happens with other greeters. |
|
| 2015-04-09 20:57:01 |
Laércio de Sousa |
bug task added |
|
lightdm-gtk-greeter |
|
| 2015-04-09 20:58:10 |
Laércio de Sousa |
description |
I work with a computer lab consisting of 9 CPUs with 2 seats each one. I have used Ubuntu 14.04 LTS on them and now I'm trying Ubuntu 15.04. In both cases, I set autologin as guest in all seats with a timeout of 60 seconds.
After some reboots, I've noticed that one of the seats stops performing autologin after the timeout. However, if I set autologin timeout to 0 on that seats, they perform autologin as expected.
Once timed autologin starts to fail on some seats, it won't go back to normal, even if I reboot or power off the computer. It only goes back to normal if I reinstall lightdm.
[UPDATE] I realised that timed autologin actually fails if user in question (also applies for guest) is selected in user list when timeout reaches 0. However, if I select another user before timeout reaches 0, autologin for configured user works as expected.
Verified with lightdm-gtk-greeter. Not sure if it also happens with other greeters. |
I work with a computer lab consisting of 9 CPUs with 2 seats each one. I have used Ubuntu 14.04 LTS on them and now I'm trying Ubuntu 15.04. In both cases, I set autologin as guest in all seats with a timeout of 60 seconds.
After some reboots, I've noticed that one of the seats stops performing autologin after the timeout. However, if I set autologin timeout to 0 on that seats, they perform autologin as expected.
Once timed autologin starts to fail on some seats, it won't go back to normal, even if I reboot or power off the computer. It only goes back to normal if I reinstall lightdm.
[UPDATE] I realised that timed autologin actually fails if user in question (also applies for guest) is selected in user list when timeout reaches 0. However, if I select another user before timeout reaches 0, autologin for configured user works as expected. Got hint from https://bugs.launchpad.net/lightdm/+bug/854261/comments/5
Verified with lightdm-gtk-greeter. Not sure if it also happens with other greeters. |
|
| 2015-04-14 18:09:18 |
Laércio de Sousa |
marked as duplicate |
|
854261 |
|
