Fix released in LDM 2.2.15.
** Changed in: ltsp
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316320
Title:
Screen Lock does not prompt for password
** Changed in: ltsp
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316320
Title:
Screen Lock does not prompt for password
To manage notifications about this bug
The no tray issue was fix-committed in
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1457730
The no lock screen issue was fix-committed with LDM_PASSWORD_HASH.
** Changed in: ltsp
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of
Seems like it's something wanted:
ltsp-5.5.1/client/Debian/share/ltsp/init-ltsp.d/50-gsettings-overrides:disable-lock-screen=true
So marking unity as invalid.
** Also affects: ltsp
Importance: Undecided
Status: New
** Changed in: unity
Status: Incomplete = Invalid
** Changed
LDM uses `ssh user@server` to authenticate users.
It then copies the user /etc/passwd information from the server to the client,
but it doesn't copy the /etc/shadow part, i.e. the user password hash.
So fat client and localapps users do not have a password set, and thus
cannot use `sudo`, cannot
** Changed in: ltsp
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316320
Title:
Screen Lock does not prompt for password
To manage notifications about this bug go to:
In my environment, I wanted users to authenticate with thick clients
using their LDAP binding credentials.
I was able to enable SSSD authentication and add my LDAP cn to the
sudoers file on the fat client image. After doing an ltsp-update-image,
I am able to use the sudo command with the fat
The panel part might be because gnome-settings-daemon gets loaded before
unity-settings-daemon, and thus unity-panel-service doesn't start at all.
Try manually running /usr/lib/unity/unity-panel-service, if then the panel
applets get loaded, yeah file a separate bug against Unity*.
I don't know
Ah! Alkis you're the best. That was exactly the issue! Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316320
Title:
Screen Lock does not prompt for password
To manage notifications about
Hmm... I see, the Unity Panel allows the User to enable the gnome screen
lock, which is not using SSSD (even though I have it installed) so it
just hangs in a loop when trying to unlock the screen.
Also the keyring seems to have the same problem, generating hundreds of
thousands of keyring.temp
I can confirm the issue. Thin clients look fine, fat clients don't.
** Changed in: unity
Status: New = Confirmed
** Changed in: unity (Ubuntu)
Status: New = Confirmed
** Changed in: unity
Importance: Undecided = High
--
You received this bug notification because you are a
I've noticed some errors that may be related inside the ~/.Xsession-
errors file:
Xsession: X session started for cott at Thu May 15 10:10:22 EDT 2014
localuser:cott being added to access control list
Script for ibus started at run_im.
Script for auto started at run_im.
Script for default
Ok i managed to reproduce it on a VM. Btw does not look like a unity bug to me.
Can you execute on the fat client this command:
gsettings get org.gnome.desktop.lockdown disable-lock-screen
It's true here and this explains why lockscreen is not working. Also
unity does not control the value of
** Tags added: lockscreen
** Also affects: unity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316320
Title:
Screen Lock does not prompt for password
I think the issue here is that since users on the Terminal server are
authenticated with sssd/ldap the client images need to be able to
authenticate as well.
As a temporary work around I have installed xscreensaver and sssd. With
the same sssd.conf from the server, the xscreensaver lock works
Installed using DVD for Ubuntu 14.04 Server Edition.
Intalled ltsp-server-standalone (with dhcpd) package using apt.
Hardware is an HP ProLiant DL380 G7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
16 matches
Mail list logo
