I do have of course, ‘semantic desktop’ enabled… (BTW I don’t know what speakers of other languages make of it, but as a native english speaker, the word ‘semantic’ makes me reach for my gun, being ironically an more-or-less meaningless word in this context, but still…)
Anyhow, and despite Knurpht’s kind and patient advice, this is still a daily, or every boot/log-in problem:
As I mentioned in the thread, I am not expert enough to present a meaningful bug-report on this, and it seems that I am in a very small group who have the problem.
Also during the last week, Facebook’s sidebar stopped working, leaving me unable to use messaging… this suddenly started working again after a number of updates from Chromium (chromium repo)
Folks on IRC #chromium-support tell me that the version supplied by Index of /repositories/network:/chromium/openSUSE_12.2 is, in fact ‘canary’ ie a pre-beta unstable, testing only release. I was surprised to learn this. Should I be using chromium from a different source?
Do you have Nepomuk set to index Email, Files and of course the top check box Semantic Desktop? Also, is your Akonadi Server actually configured and running. I had a problem after upgrading to KDE 4.10 that the mysql.service was not set to start up at login, I had to enable it in Yast system services, maybe this will help.
The kmail problem from your other thread seems to be the new normal. What I mean is Kwallet will ask me at every boot for the master password for the Kmail account so it can check my mail in the background. I never see a Kwallet window etc… either but all seems to be working fine. I find it annoying that it has to ask every time I reboot but I guess there is no better way at the moment.
@Both: there’s loads of posts in the forums explaining how to avoid this. Simply activate the wallet, but don’t enter a password. This way, wallet will avoid storage of passwords as plain text in config files, yet doesn’t ask for the wallet password on login. Yes, I’m aware that this breaks the wallet security, but you cannot have both the security and not having to enter a password. Choice to the user. If you already have a password on the wallet, you can change that from the walletmanager itself.
@Both: there’s loads of posts in the forums explaining how to avoid this. Simply activate the wallet, but don’t enter a password. This way, wallet will avoid storage of passwords as plain text in config files, yet doesn’t ask for the wallet password on login. Yes, I’m aware that this breaks the wallet security, but you cannot have both the security and not having to enter a password. Choice to the user. If you already have a password on the wallet, you can change that from the walletmanager itself.
I also enabled mysql in yast>system services… I still get the error message when sending mail…
AFAIR Anika, it has always been this way, ie enter a pass to open the wallet on first use per session, and is not really a problem, my situation, as detailed above is more broken !