On Tuesday 19 May 2015 18:08:52 Wolfgang Bauer wrote:

Am Montag, 18. Mai 2015, 19:49:46 schrieb ianseeks:

...

i had to create a new user because of a kded problem killed access to my previous user i used for mailing lists. So when i moved as much of the email structure across to the new user (so i still had my history) i recreated the kmail user accounts and thats when kwallet decided to make istself known. I googled a way to stop it and had to edit the kwalletrc file to set enabled to no and now its gone away.

But if kwallet is disabled, KMail will not be able to store any passwords. That was certainly the case, i have to enter each account password before it goes to get email. The kwalletmanager says its V 2.0 from Help menu but Yast says its 5.10.0-1.1 , not sure if i'm running the correct version?

Maybe just the file permissions for the wallet are wrong? Would probably explain why you couldn't save the settings in kwalletmanager. Before i upgraded to Plasma, i didn't use kwallet (well, i don't think so) Kmail held the passwords for each account without accessing kwallet. If it was accessing kwallet, it never prompted me for the kwallet access to get teh passwords for the email accounts.

...

...

That sounds like the cause of your problem. Is your user session registered properly with logind? loginctl should tell.

It doesn;t show any errors

It shouldn't show any errors. But it should show your user session. Does it do that?

Yes it shows the session fine.

...

...

Maybe you have a wrong PAM configuration too? Please check whether there are .rpmnew files in /etc/pam.d/, and also check that you are not using the deprecated pam_unix2.so any more. I'm not sure whether this could cause such a problem though.

I've never touched pam at all, just used what comes out of the box but there is a rpmnew in the directory dated 25 Sept 2014

Well, in earlier openSUSE releases, pam_unix2.so was used by default. And as those are configuration files, they might not get changed on updates/upgrades. But Plasma5 has problems with pam_unix2, in particular the lock screen cannot be unlocked. So again, check that the 4 common-* files in /etc/pam.d/ (common-account, common-auth, common-password,common-session) contain "pam_unix.so", not "pam_unix2.so". Not sure whether that could cause your problem too, though.

...

So its just that some of the menu entries are pointing to the wrong version? No, the menu entries should be fine. But the Favorites entries might point to the now non-existing KDE4 versions, in particular if they have been migrated from KDE4 (as Kickoff does on first login).

Kind Regards, Wolfgang

Thanks for the replies. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org