Hi Markus,
Gesendet: Montag, 15. Juli 2019 um 10:40 Uhr; Von: "Markus Feilner"
I also think it's about networking issues. Maybe some caches or tmp directories hold bad / wrong information, that has happened here several times over the last years.
So the issue is with a new installed client (mount of /home and NIS on the client via YaST) very similar. Old ones mount with same /etc/fstab stable new ones hangs and need to unmount and mount manually again before I can start the user! This is OK for me - but my Family can't start a PC anymore with proper working system.
1) Maybe I missed it, but which display-manager are you using? Kdm? SDDM? Try switching to the simplest possible and see if the problem persists.
So it looks like tumbleweed uses sddm if KDE was selected during installation. Inside them I select "Plasma" as desktop environment (if I select "Plasma Wayland" the client hangs anyway hours on a blank screen).
2) Does the problem also occur when you start a single X session from a console? Try (as root) service display-manager stop (kills all X sessions!) Then login as unpriv. user and type startx and see what happens Repeat the same as root (I know, but for testing permission problems that's helpful).
seems that the system hangs as unpriv. user but I will wate . But during parallel using of a second client, I see that the system hangs (nicer a plasma action nor a keyboard entry possible) if I do an action on firefox :-( - I don't know if this relays to the problem but also in journalctl -x I can find kwin_x11[2931]: qt.qpa.xcb: Unhandled client message: "_NET_CURRENT_DESKTOP" ??? which tells me nothing. Regards Ulf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org