On Mon, 13 May 2013 23:52:34 +0200
Gian Carlo Stagni wrote:
> Il 11/05/2013 21:13, sp113438 ha scritto:
>
> > I already did upgrade the chroot
> On my servers I usually chroot to "/opt/ltsp/i386" and then set root
> password ad install dropbear, a thin ssh server.
> This way you can investigate
Alkis Georgopoulos wrote:
> Στις 13/05/2013 08:04 μμ, ο/η Thomas Boehm έγραψε:
>> When a user logs in on a client, the login keyring does not get automatically
>> unlocked.
>
> Indeed, the LTSP display manager, LDM, doesn't have the ability to
> unlock the login keyring like other display managers
Il 11/05/2013 21:13, sp113438 ha scritto:
> I already did upgrade the chroot
On my servers I usually chroot to "/opt/ltsp/i386" and then set root
password ad install dropbear, a thin ssh server.
This way you can investigate "/tmp/Xorg..." (on the client) and
"/var/log/syslog" (on the server) for
I am out of the office until 05/20/2013.
Note: This is an automated response to your message "Re: [Ltsp-discuss]
"The login keyring did not get unlocked..."" sent on 5/13/2013 2:52:41 PM.
This is the only notification you will receive while this person is away.--
Στις 13/05/2013 08:04 μμ, ο/η Thomas Boehm έγραψε:
> When a user logs in on a client, the login keyring does not get automatically
> unlocked.
Indeed, the LTSP display manager, LDM, doesn't have the ability to
unlock the login keyring like other display managers.
In LTSP 6, LDM is planned to be r
Thomas Boehm wrote:
> after hours of googling I'm non the wiser where the problem lies. When a
> user logs in on a client, the login keyring does not get automatically
> unlocked. It works fine when the same user logs in on the LTSP server
> itself. I tried different flavours of fat-client-desktop
