šumski schrieb:
On Friday 27 of March 2015 15:37:56 Luiz Fernando Ranghetti wrote:
2015-03-25 18:51 GMT-03:00 Robert Kaiser <kairo@kairo.at>:
Robert Kaiser schrieb:
šumski schrieb:
On Tuesday 24 of March 2015 20:14:03 Robert Kaiser wrote:
šumski schrieb: > On Tuesday 24 of March 2015 19:27:39 Robert Kaiser wrote: >> Will password-unlock from the lock screen actually work in 5.3? In >> the 5.2.x versions I have installed on my openSUSE 13.2 via the >> Frameworks5 >> repo, it never accepts the unlock password, so there is no way to >> get back from a locked screen, which is pretty bad. > > It works fine since 5.0. It doesn't work fine if you have cruft in > pam config (/etc/pam.d) from previous openSUSE versions...
That's surely possible. What kind of "cruft" would I be looking for?
Check the above mentioned directory, you'll most likely find quite a few rpmnew files in there.
sudo rm -rf /etc/pam.d/common-* /etc/pam.d/login* and then reinstalling (forced updating) pam, pam-config, and util-linux did help.
As a note to whoever tries this, you need to reinstall any package that (installs pam modules and) puts stuff into the pam configs after this, most importantly systemd.
Hi,
Yesterday I installed the patterns-openSUSE-plasma5_basis package and switched to Plasma5, so far so good, but I got this lock screen problem as well.
What's the workaroung I should use?
If you're having troubles unlocking, and you've upgraded from some earlier openSUSE release, best would be imo to merge the changes in rpmnew files into the config files. https://en.opensuse.org/SDB:Offline_upgrade#Stale_configuration_files
In my case, I didn't see any useful differences between the rpmnew and the config files, other than the rpmnew for example missing systemd - if I would have merged that removal, I'd had the same issue (things like bluetooth and network manager widgets not working) as I had when deleting the config files and reinstalling pam and pam-config. I actually would recommend to do what I did, do this hard removal and reinstall (forced update) all packages listed by this command: rpm -q -f /lib64/security/pam_* | sort | uniq Ideally, you'll make a copy of the files you are deleting, diff them to the new ones once done, and then tell us what it actually is that causes the issue. I *really* hope someone will find out what the actual thing is that needs to be added/removed in the config and that the openSUSE KDE/Plasma maintainers will put something in the packages to automatically detect and correct this issue, as I fear it will leave many people locked out of their own sessions otherwise. KaiRo -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org