kde 15.04.3-1.1 When I lock the screen as user X, the screen unlock window appears and offers to unlock the session (or to start a new session). When I enter the correct password for user X, the detection fails and "Aufheben der Sperre fehlgeschlagen" (unlock fails) appears. I double-checked and expressly set the password for the user. The same: unlock fails. Reproducible: Always
it works for user root with the root password (after having started a new session for user root).
See here: https://bugzilla.opensuse.org/show_bug.cgi?id=931816 Does this help?
Indeed, I upgraded from 13.2 to Tumbleweed. However, the thread you posted, is long. What do I have to do exactly?
I need help. Threads are long, have a lot of information, but what exactly has to be done to fix the problem that a (correct!) password is not accepted ? How can such a severe and security-related bug find its way into Tumbleweed ?
(In reply to Tom from comment #3) > Indeed, I upgraded from 13.2 to Tumbleweed. However, the thread you posted, > is long. The problem is not in upgrading from 13.2 to Tumbleweed, but upgrading from earlier versions. Unlocking does not work when pam_unix2.so is used in the PAM config. Since 13.1 pam_unix.so is the default, but if you upgraded from earlier versions at some point you might still use pam_unix2.so. > What do I have to do exactly? There are two possibilities: - change the PAM config in /etc/pam.d/ to use pam_unix.so instead of pam_unix2.so. Actually you should have some *.rpmnew files in there, overwrite the original files with those. OR: - make /usr/lib64/lib64/libexec/kcheckpass suid root: sudo chmod +s /usr/lib64/lib64/libexec/kcheckpass It then has the necessary privileges for checking the password in any case. The latter has been declined by the security team though, and the former cannot be fixed really, as updates/upgrades should not change user (or administrator) configs. (In reply to Tom from comment #4) > How can such a severe and security-related bug find its way into Tumbleweed ? This is no sever and security-related bug. Actually on a fresh Tumbleweed installation (as well as on a fresh 13.1 or 13.2 installation), it should work as intended. The problem is an outdated configuration, caused by upgrading.
PS: (In reply to Tom from comment #4) > Threads are long, have a lot of information The answer is in the first reply (https://bugzilla.opensuse.org/show_bug.cgi?id=931816#c1) anyway.
I do have five *.rpmnew files in /etc/pam.d . * common-account.rpmnew * common-auth.rpmnew * common-password.rpmnew * common-session.rpmnew * login.rpmnew I do not have any pam_* file. The bugzilla is silent about what to do with the .rpmnew files. Pls assist.
(In reply to Tom from comment #7) > The bugzilla is silent about what to do with the .rpmnew files. Pls assist. Copy or move the .rpmnew files over the corresponding common-xxx-pc files, or modify the common-xxx-pc files to have the same content as the .rpmnew files. (actually the config is in common-xxx itself, but those are just symlinks to the common-xxx-pc files, better change the latter) I.e.: > * common-account.rpmnew -> common-account-pc > * common-auth.rpmnew -> common-auth-pc > * common-password.rpmnew -> common-password-pc > * common-session.rpmnew -> common-session-pc The login.rpmnew is irrelevant for this, but you might do the same. In this case the regular file is "login".
ok, copying the four files helped and solved the problem. Many thanks. Problem should be corrected in the software (kde? Tumbleweed??). Somehow.
(In reply to Tom from comment #9) > ok, copying the four files helped and solved the problem. Fine. > Problem should be corrected in the software (kde? Tumbleweed??). Somehow. It's an openSUSE (downstream) problem. As I tried to explain already, it's not a problem in Tumbleweed either, but rather in the upgrade process from earlier versions (before 13.1). The same happens if you upgrade your system from e.g. 12.3 to 13.1/13.2 and then install/use Plasma5. In KDE4 this was no problem as kcheckpass was installed as suid root. For Plasma5 the security team declined that unfortunately. But this is the wrong place to discuss this. If you want to, add a comment to the openSUSE bug report.
Ok, will do so (report downstream). Just a final point, as I am very unhappy with the new desktop (e.g. mixed of languages, taskbar/Task tray issues, missing Gadgets etc.), where is the _correct_ place to discuss this issue?
(In reply to Tom from comment #11) > Ok, will do so (report downstream). It is already reported. I pointed you to the bug report (it has been marked as duplicate of another one meanwhile though). > Just a final point, as I am very unhappy with the new desktop (e.g. mixed of > languages, taskbar/Task tray issues, missing Gadgets etc.), where is the > _correct_ place to discuss this issue? If you find a bug in KDE, open a bug report here in KDE's bugzilla. If it is an openSUSE packaging problem, report it there. Although it's not always obvious. If you're not sure, you can also ask/discuss your problems in the KDE or openSUSE forums first. Missing widgets is no bug though, not all have been ported yet, and some have been dropped on purpose... There are known problems with the translations in Tumbleweed at the moment, some have been fixed recently (one particular fix is on the way but it has to go through review and testing first before it becomes available in the standard repo) and the rest is being discussed. See here e.g.: http://bugzilla.opensuse.org/show_bug.cgi?id=932158 http://bugzilla.opensuse.org/show_bug.cgi?id=904524 No need to report this.