In data venerdì 3 aprile 2015 15:09:01, Achim Gratz ha scritto: Hello,
Lock screen can't be unlocked because kdecheckpass can't read the password database. That's a packaging bug according to upstream and has been known for almost a year.
This is caused by PAM, not by KDE packaging, FTR: pam_unix2 is used instead of pam_unix, and the former doesn't allow kcheckpass to access passwd. Check if you have rpmnew files in /etc/pam.d/.
Where to start? There is apparently absolutely no migration of settings
Applications need to opt-in for this (there is a specific functionality that can be used). Plasma won't be able to migrate settings as it changed too much on that regard. Please file bugs upstream where apps do not migrate their settings from 4.x.
from KDE4. I'm not sure if it uses its own settings since I didn't try to go back to 4.12 yet.
No, they don't. KF5 based apps finally use the XDG specification (~/.config, ~/.local, ~/.cache) rather than .kde[4].
No CPU/Temp/Network monitor, really? No visual feedback on when/where I can resize windows (might be a theme issue, but I'd consider it a bug).
CPU/Temp/Network monitors are back in Plasma 5.3, *really*.
It always seems to fall back to XRender backend no matter what else I set (it seems to accept the new setting but when you reopen the window it's back to XRender).
Compositing needs OpenGL 2 at least. If your driver does not provide that, it will automatically fall back to XRender. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79