There are two bugs in the new KDE SC 4.10.0, which I was compelled to fix without waiting for a 4.10.1 release.
The first concerns the new “simple locker” which can be chosen instead of the normal screensaver. In KDE 4.10.0, this new screenlocker has the annoying behaviour that it will activate even if you selected the normal “legacy” screensaver and have explicitly configured KDE not to ask for a password when killing the screensaver. There is a patch on KDE ReviewBoard which attempts to fix this. This does provide a partial fix in my patched “kde-workspace” package: a password is no longer asked if you did not configure one, which takes away the annoyance. But the “simple locker” still manages to run on top of the configured screensaver occasionally. I guess we will have to wait for a better patch.
The second fix has been applied to the “nepomuk-core” package. On the kde-packager mailing list, Vishesh Handa announced a patch today for the broken “recursive file indexing“. This regression accidentally slipped into Nepomuk’s code when the developers attempted to reduce the memory usage of the file indexer.
Both packages (kde-workspace and nepomuk-core) are available in my ktown repository:
- http://alien.slackbook.org/ktown/ (the master repository), rsync URI: rsync://alien.slackbook.org/alien/ktown/
- http://taper.alienbase.nl/mirrors/alien-kde/ (my fast mirror), rsync URI: rsync://taper.alienbase.nl/mirrors/alien-kde/
- http://repo.ukdw.ac.id/alien-kde/ (willysr’s Indonesian mirror), rsync URI: rsync://repo.ukdw.ac.id/alien-kde/
Pingback: [SOLVED] KDE 4.10 screensaver locks screen even if it is configured not to!
Just for your information, the recently released openssl 1.0.1d security fix for slackware breaks kopete in your packages for kde4.9.5. kde4.10 doesn’t seem affected but I was forced to downgrade since I have multiple plasma crashes per day on kde4.10 even though I completely wiped my preferences and settings …
Sorry I went to fast to kopete (and your packages) and didn’t see it was slackware openssl 1.0.1d package that has a problem (or maybe upstream ?). I have a Xeon1230v2 with AES-NI and just saw that : http://www.linuxquestions.org/questions/slackware-14/openssl-1-0-1d-aes-ni-4175449585/
Hopefully Pat will fix that soon !
Pingback: KDE 4.10.0 no Slackware 14/Current » slack user…
I upgraded using Alien’s SlackBuild, Dolphin wouldn’t work, so I went from 14.0 release to -current, and Dolphin still doesn’t work. I get an error when I try to run Dolphin at the CLI:
dolphin: error while loading shared libraries: libnepomukwidgets.so.4: cannot open shared object file: No such file or directory
That library you mention nepomuk-widgets-4.10.0-x86_64-1 package. Do you have that one installed?
It is a package which was added to KDE in 4.10, therefore it has also been added to slackware-current yesterday.
If you use slackpkg for your package management, did you run “slackpkg install-new” in order to install all packages which have the status “Added” in the slackware-current ChangeLog.txt ?
for : owengreaves
you need install nepomuk-core and nepomuk-widget, it’s solved my problems thank’s, sory my bad english, download from alien’s repo