kblankscrn.kss
 

I have Slackware 14.1, 64-bit, with KDE 4.10.5.

Occasionally I get one or more blank popup windows titled "kblankscrn.kss". They are quite annoying and would like to permanently get rid of them.

It has been suggested to run
before logging out, but I would like to see if somebody can suggest a permanent fix.

I think(!) I read somewhere it is a KDE-bug, you might want to search there on the KDE bug-tracker. This is a little bit contradicted by the openSuSE KDE 4.10.5 "release 1" moniker for the KDE-version I use mostly without trouble. But then KDE.org says they released 4.12.1 recently, perhaps you can simply upgrade...

Alien Bob has 4.11.5 for 14.1, if you feel like upgrading. See here:
http://alien.slackbook.org/blog/kde-...lackware-14-1/

when you install KDE from console (by using apt-get install or aptitude cron.*, it will upstream /dev/hdpi.
But when you install it with your distribution (eg. iLinux) it will install without creating /dev/hdpi.
Strange but dev know already.

You can even install my KDE 4.12.1 on Slackware 14.1 - http://taper.alienbase.nl/mirrors/al...urrent/4.12.1/ . Even though it has been compiled on Slackware-current, it works perfectly on Slackware 14.1 as well.

And if you wait another day, you will find KDE 4.12.2 there instead of 4.12.1 and that version was compiled on Slackware 14.1 for maximum compatibility (will work perfectly on -current too, which is where I am typing this).

Eric

Thanks, Eric. Last time I looked I thought 4.12.1 was only for -current. I'll grab 4.12.2 as soon as it's ready. :)

Forgive me for asking this but I am relatively new to Linux: If I install the program from your repository am I then responsible to check periodically for new versions or will slackpkg take care of that every time that I run it? I think I know the answer but one never knows...

Hi

If you are new to Slackware and are willing to experiment, then you could read a bit about slackpkg+ which is an extension to slackpkg.
See http://alien.slackbook.org/blog/intr...-repositories/ which explains how slackpkg+ makes it a lot easier to maintain Slackware if you have 3rd party software installed from SLackware-compatible repositories (like my KDE repository).

Also if you installed multilib on top of your 64-bit Slackware, then slackpkg+ will make your life so much easier.
Slackware does not have an automatic update service, you are the admin and it leaves you full control, including the decision to perform upgrades... or not. You can schedule something like "slackpkg check-updates" as a regular cron job to get notified of updates per email.

Don't forget that there is a lot of Slackware documentation in http://docs.slackware.com/ and we have our own forum here at LQ: http://www.linuxquestions.org/questions/slackware-14/ . Don't be afraid to ask your 'newbie' questions there... everybody in that forum was a newbie themselves, one day.

Eric

In my Slackware 14.1 (64-bit) I have already installed the multilib package that you offer, so slackpkg+ is definitely something that I am interested in. While I have not yet installed slackpkg+, I did read and re-read the instructions, including your "Introducing slackpkg+, an extensions to slackpkg for 3rd party repositories". I am a little bit confused as to how to set up /etc/slackpkg/slackpkgplus.conf.

Assuming that I have installed:
* The multilib for running 32-bit programs and KDE 4.12.1 packages, and
* Several packages from SlackBuilds.org
...I am not too sure what I need to enter in the PKGS_PRIORITY, REPOPLUS, and MIRRORPLUS sections of slackpkgplus.conf.

I think things should be this way:
PKGS_PRIORITY=(multilib:.* restricted:.* alienbob:.* ktown:.* slackbuilds:.*)
REPOPLUS=(slackpkgplus multilib ktown alienbob alienbob_current restricted)
MIRRORPLUS['multilib']=http://taper.alienbase.nl/mirrors/people/alien/multilib/14.1
MIRRORPLUS['restricted']=http://taper.alienbase.nl/mirrors/people/alien/restricted_sbrepos/14.1/x86_64
MIRRORPLUS['alienbob']=http://taper.alienbase.nl/mirrors/people/alien/sbrepos/14.1/x86_64
MIRRORPLUS['ktown']=http://taper alienbase.nl/mirrors/alien-kde/14.1/latest/x86_64
MIRRORPLUS['slackbuilds']=http://http://slackbuilds.org/repository/14.1/

Did I get anything right??

SlackBuilds.org does not have a package repository, they just have build scripts. Therefore it can be removed from the slackpkgplus.conf - you will only get errors as long as you have it.

This should work I guess:
It's all in the README - with explicit examples for multilib and ktown.

Eric

Thanks for the help.
For multilib maintenance I also have to set in /etc/slackpkg/slackpkgplus.conf, correct?

No, for multilib you do not have to set . Multilib packages will be installed and maintained just fine without that flag.
The "ALLOW32BIT=on" will allow you to install 32-bit packages on a 64-bit Slackware computer using slackpkg. Note that this is a possibly unsafe operation because it can bring you into situations where you overwrite a 64-bit Slackware package (ARCH=x86_64) with a 32-bit Slackware package (ARCH=i486). The correct way of installing a 32-bit package in a multilib system us to use the "convertpkg-compat32" script on the package and create a "compat32" version of the 32-bit package which you can then install on your multilib computer. A "compat32" package is created in such a way that it will not overwrite important stuff from a 64-bit package.

Eric