Discussion:
[Ltsp-discuss] fat clients with samba home, mate, gnome-keyring and other problems
Jan Kowalsky
2017-04-07 16:44:16 UTC
Permalink
Hi all,

we run a lot of ltsp-thin-client environments in the past. Now, the
first time I'm working on a fat-client environment and run in to
serveral problems.

Environment ist debian jessie and ltsp 5.5.4-4

1. Mate-Session with ldm

I set up a standard fat-client environment with mate desktop and ldm.
After login every looks fine at the first glance, but: caja seems not to
recognize correct mime times of files - or has any other problems. So
while trying to open text files the user is asked if he want's to open
or execute the file - just as if the file had an executional bit (but it
doesn't).

Since there is no problem with local file systems (e.g. on usb) but the
same problem with other file systems mounted as sshfs I make the latter
responsible.

2. Mate-Session with ldm and nfs

switching to nfs as /home everything seems fine.

But this is not an option due to security.

3. Mate-Session with samba through pam_mount and lightdm

So I tried to use home over samba with pam_mount:

<volume options="uid=%(USER),gid=30000,nodev,nosuid,noexec" user="*"
mountpoint="/home/%(USER)" path="%(USER)" server="server" fstype="cifs" />

Since with ldm the samba home isn't mounted on login I switched to
lightdm (in ltsp.conf:DEFAULT_DISPLAY_MANAGER=""). No the samba home is
mounted on login. But mate doesn't start.

The reason seems to be the gnome-keyring. It can not be started because of:

gnome-keyring-daemon: insufficient process capabilities, unsecure memory
might get used
** Message: couldn't connect to control socket at:
/run/user/30002/keyring/control: Connection refused

General Question:

Ho do you mount /home and other shared directories in fat client setup
and which desktop environment do you use?

Thanks and best regards!
Jan
Alkis Georgopoulos
2017-04-07 18:03:19 UTC
Permalink
Post by Jan Kowalsky
So
while trying to open text files the user is asked if he want's to open
or execute the file - just as if the file had an executional bit (but it
doesn't).
You have an sshfs version that has this bug, I reported it and it was
fixed 5 years ago:
https://bugs.launchpad.net/ubuntu/+source/sshfs-fuse/+bug/1017870

...try to find a newer sshfs version.
Jan Kowalsky
2017-04-10 08:10:34 UTC
Permalink
Hi Alkis,
Post by Alkis Georgopoulos
You have an sshfs version that has this bug, I reported it and it was
https://bugs.launchpad.net/ubuntu/+source/sshfs-fuse/+bug/1017870
...try to find a newer sshfs version.
thanks for this information.

The version of sshfs in debian jessie is 2.5-1. I installed sshfs_2.8-1
from debian testing and now it works.

But why this bug in debian is still in version 2.5.1?

Thanks!
Jan
Alkis Georgopoulos
2017-04-10 08:23:55 UTC
Permalink
Post by Jan Kowalsky
Hi Alkis,
thanks for this information.
The version of sshfs in debian jessie is 2.5-1. I installed sshfs_2.8-1
from debian testing and now it works.
But why this bug in debian is still in version 2.5.1?
I reported the fix upstream to sshfs. They fixed it.
Then I requested an "SRU", a backport of the fix to previous Ubuntu
versions, that's why the 2.4-1ubuntu1 version had the fix.

Noone requested a backport of the fix for Debian Jessie.
It's up to you to do that.

Loading...