Leap 16.0 and KDE with LDAP and NFS

English Install/Boot/Login
,
1

Hello,
we have problems with Leap 16.0 and KDE and NFSv3 and LDAP.
In Leap 15.6 our setup in the company works fine.
The Login-Process works via console, also automounting the home of the user via console after login.

But the login with sddm fails with KDE.
We tried Wayland and X11, no difference.
Using gnome or XFCE, there are no problems to log in with user-homes on NFS.
We mount NFS with no_root_squash to start.

Has anyone a working sddm and KDE with user-homes on NFS with Leap 16?

Greetings, Nina

ps. for Logs see https://bugzilla.suse.com/show_bug.cgi?id=1262231

2

For openSUSE folks, please be aware of the Leap 16.0 Release Notes section <3.3 Support statement for openSUSE Leap>.

@cseegkwkg:

Please be aware that, there are more than a few issues with Leap 16.0 and the associated, shipped, version of KDE Plasma which have been discussed in these Forums.

And yes, GTK based desktops such as GNOME and XFCE seem to be executing without any issues on Leap 16.0.

3

Where can we buy support for OpenSUSE Leap? Our NFS-Server is SLES 15 SP7, should we file a bugreport there? But i think the problem is on the client side.

4

Just create a bug report… There is a link in the Forum side panel for Bug Reporting.

5

Yes, thank you, as i mentioned in the first post we made a bugreport at bugzilla already. We were hoping here to find people who have a working NFS with KDE and Leap 16.

6

I have that, but I did not answer until now because you mention LDAP, which I have not.

7

would you mind sharing your nfs (and possible autofs) config on leap? is it NVFSv3 or NFSv4?
we mount nfsv3 with the options nfsvers=3,local_lock=flock now. and we open the corresponding ports nfsnfs3,rpc-bind and 21003(tcp/udp), 21002(tcp/udp) in the firewall.

8

Of course.

On the server:

henk@boven:~> cat /etc/exports
/home/wij       *.henm.xs4all.nl(rw,no_root_squash,sync,no_subtree_check)
henk@boven:~>

On the client:

mgi@beneden:~> grep nfs /etc/fstab
boven.henm.xs4all.nl:/home/wij             /home/wij  nfs   nfsvers=3,noauto,nofail,x-systemd.automount,x-systemd.mount-timeout=10,x-systemd.idle-timeout=5min  0  0
mgi@beneden:~>

You see that I use the systemd way of doing automount. I is even easier to configure then the automount of old time.

I have no idea why you mention KDE somewhere in your posts, because this is of course DE agnostic.

BTW this worked in Leap 15.6 (and maybe already) earlier). No problems on switching to Leap 16.0 (except that the upgrade switched the firewall on, but that blocked of course much more then just NFS).

9

@cseegkwkg:

The Bug Report you raised is on the SUSE Bug reporting – therefore your SLE support is allowing you to raise Leap 16.0 Bug Reports there and, it seems that SUSE staff are working on the issue you’ve reported there.

  • The Support statement in the Leap 16.0 Release Notes seems to supply some explanations with respect to what’s happening here.

You could simply ask via your SLES 15 SP7 Support agreement for clarification of your current support status.

10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.