| Summary: | Plasma wayland: Only black screen with cursor when using NFS $HOME mounted with sec=krb5i | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Stefan <sstaeglich> |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | CC: | nate, p.r.worrall, plasma-bugs-null |
| Priority: | NOR | Keywords: | wayland-only |
| Version First Reported In: | 5.22.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Stefan
2021-06-08 16:40:44 UTC
I have my home directory on an NFS server and can use Plasma on Wayland OK. My software versions are the same, except I've got Frameworks 5.83.0, not likely to be that though. Can you switch to a terminal (e.g. Ctrl-Alt-F2) and log in that way? @Paul Starting it on terminal via startplasma-wayland doesn't make a difference. Can you describe your setup in more detail (e.g. NFS version, linux distribution, mount options)? In my current setup it's NFS 4.2 with sec=krb5i and cachefilesd. I'll try it with sec=sys and without cachefilesd again. @Stefan I'm using KDE Neon user edition, updated today. My fstab entry is: 192.168.0.2:homes /home nfs defaults 0 0 And the exports file on the server has: /srv/nfs4 192.168.0.0/24(rw,async,fsid=root,crossmnt,no_subtree_check) /srv/nfs4/homes 192.168.0.0/24(rw,async,no_subtree_check,no_root_squash) nfsstat -m says version is 4.2 cachefilesd is not installed and I'm not using kerberos Ok I'm quite sure that I made other experiences in past: But now I can get plasma wayland running when I disable the use of kerberos (sec=sys). This makes sense somehow because I made similar experiences with Ubuntu snap packages. There was still a statement "export KWIN_DRM_USE_EGL_STREAMS=1" in $HOME/.profile (there is still a /etc/profile.d/kwin.sh). After removing the statement plasma-wayland is starting. But the performance and stability is horrible (nvidia GPU). Thanks, looks like this was caused by a setup problem, so nothing for Plasma to do. :) |