Main menu:


Please consider a small donation:



Or you can donate bitcoin:


Thanks to TekLinks in Birmingham, AL, for providing colocation and bandwidth.

Page Rank


FOSS Force Best Blog--2013 Award

Recent posts

Recent comments

About this blog

I am Eric Hameleers, and this is where I think out loud.
More about me.


Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 426 other subscribers

My Favourites

Online me



May 2019
« Apr    

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

RSS Slackware64-current



KDE 5 (Plasma 5.2.0) available for Slackware -current

qt-kde-620x350And yes – let me get this clear right from the start: this Plasma 5.2.0 desktop environment will replace the KDE 4 packages you have installed.

What is this new ‘Plasma 5’

Plasma 5 is the “next-gen” KDE desktop. It has been in development for a long long time, with the goal of providing a gradual migration path away from the well-known KDE 4 desktop. All of this with the KDE 4.0 “debacle” in mind. You may recall that the KDE community released KDE 4.0 as a “tech preview” i.e. not ready for production, however some distributions upgraded their KDE from 3.x to 4.0 regardless of that. The backlash from the user community was understandable of course, because they went from a stable KDE 3 desktop to a buggy and crippled KDE 4 desktop. This was often blamed upon KDE itself, but that does the developers and their software grave injustice – it was the distros who forced their users to a non production-ready version of KDE,so it should be those distros who should be criticized for their bad judgement. Still, even to this day, harsh words about KDE 4.0 are targeted at its developers, not at the distros who made a strategic error.

Nevertheless, here we are, with a shiny KDE 5 desktop environment!

KDE 5 makes a switch from Qt 4 to Qt 5 as the base graphical toolkit. The old KDE 4 libraries have been ported to become the Frameworks: Qt 5 modules with no dependencies except Qt 5 and optionally, other Frameworks. This allows non-KDE developers to adopt the Frameworks in order to provide an expanded Qt 5 feature set. This porting effort has been going on for a long time now (its first technology preview for Frameworks was little more than one year ago) and the Frameworks are mature technology now. Plasma 5 is the set of packages that provide the core Desktop experience, built on top of the Frameworks.

The release of Plasma 5.2.0 earlier this week was the turning point for me – this release is the first one that I actually consider ready for prime-time, capable of replacing the KDE 4 Workspace. The KDE Applications (currently at version 14.12.1) are the collection of software which used to be grouped in meta-packages like kdebase, kdeedu, kdegraphics, kdemultimedia etcetera. The Applications currently get huge attention from the developers, because that is where the hard work is being done the coming year. Slowly, all individual Applications are being ported away from Qt 4 and the KDE 4 libraries, to Qt 5 and the Frameworks. In Applications 14.12.1, the only ported apps to date are kate, konsole, analitza, gwenview, kalgebra, kanagram, khangman, kig, parley, kapptemplate,  and okteta. As you can see, still a long way to go.

These KDE 5 packages of mine are going to be your only KDE desktop. The “kde-workspace” package which provided the well-known KDE 4 workspace has been replaced by “plasma-workspace” and the good old KDM graphical login manager has been retired and replaced with SDDM. While you will be presented with a pretty Plasma 5 workspace, most of the KDE applications you’ll be using are the familiar KDE 4 versions (with updates and bugfixes), nicely blending in to the new Breeze theme.

Some Plasma 5 highlights I mentioned in last year’s preview: Plasma 5 improves support for high-DPI displays and comes with a “converged shell”, i.e. one Plasma codebase for different target devices like desktop computers, laptops, tablet, phones etc. Plasma 5 uses a new fully hardware-accelerated OpenGL(ES) graphics stack. And with the Breeze themed artwork and its own Oxygen font, this desktop looks clean and modern.

Plasma 5 follows the same trend you can also witness in Android 5, Windows 8 and OS X: gone are the colourful, exuberant 3D-ish icons, buttons and other graphical design elements.  Flat and monochrome is the new dogma. The result is too clean in some regards, is my personal opinion: the monochrome system tray icons are just plain ugly and I get flashbacks of Windows 3.1 sometimes. Judge for yourself.

What to expect from these Slackware packages

These packages are only going to be useful if installed on top of Slackware -current. They are replacing the KDE 4 packages (plus adding/upgrading a lot of dependencies) that you might have installed. There is no co-installable option. Therefore if you rely on your KDE desktop for your daily productive work, please consider your upgrade carefully. The upgrade/migration should be painless if you follow the README instructions, but I can not guarantee that there will be no deal-breakers for you (missing functionality or persistent crashes).


  • Lots of packages in the ‘deps’ department which are completely new to Slackware. Since KDE 5 is built on Qt5 (KDE 4 had Qt4 as its base) you’ll find many Qt5 related packages. Also, in order for Qt4 and GTK based applications to dock into the Plasma 5 system tray, more dependencies were needed. So, apart from updates to regular Slackware packages, these are the new ones (some of them will be familiar if you are already running my KDE 4.14.3):
    LibRaw, OpenAL, akonadi-qt5, eigen3, gst1-plugins-base, gst1-plugins-good, gstreamer1, json-glib, libappindicator, libdbusmenu-gtk, libdbusmenu-qt5, libepoxy, libfakekey, libindicator, orc, polkit-qt5-1, qca-qt5, qt-gstreamer, qt-gstreamer1, qt5, sni-qt, wayland and xapian-core.
  • Qt 4.8.6 of Slackware was patched to support the docking of Qt 4 application icons into the Plasma 5 system tray (and the ‘sni-qt’ package actually implements this support). While I was at it, I also added some patches which Libreoffice requires for native KDE file-open dialog support.
  • Note for users of multilib Slackware64 and also using Skype: you will have to grab the 32-bit version of Slackware’s “libdbusmenu-qt” and my “sni-qt” packages and run “convertpkg-compat32” on them and then install both “libdbusmenu-qt-compat32” and “sni-qt-compat32”, or else Skype won’t be able to dock its icon in the Plasma 5 systray.
  • A bit sneakily, I built phonon-vlc for you. You will also need a VLC package to be able to use phonon-vlc though.
  • I added the latest Calligra 2.8.7 office suite.
  • Even though I compile a ‘kde-workspace’ package as part of the whole set (otherwise kdeartwork refuses to compile), I do not actually ship that package. It conflicts with the new plasma-workspace package.
  • Several source tarballs in Plasma 5.2.0 have not been compiled to Slackware packages: libbluedevil and bluedevil (they need BlueZ 5 which is not part of Slackware), muon (a debian/ubuntu package manager), libkface (needs opencv which I was not willing to add as a dependency).
  • One dependency which you’ll probably find curious, is wayland. It is required in order to compile KWin’s X11 driver, but it is apparently not needed at runtime. Nevertheless, I left the package in, just in case you want or need to recompile kwin.
  • Graphical login: KDM has been replaced with SDDM. Installation of the sddm-qt5 package triggers the creation of a “sddm” user and group. The “sddm” user is then also added to the “video” group. If you already have a local “sddm” account, then all of that will be skipped. You’ll have to add the “sddm” user to the “video” group manually if you experience graphical glitches.

Testing Repository URL

I still consider KDE 4.14.3 the “latest stable” version for Slackware-current, and therefore the repository URLs (for 64-bit) and (for 32-bit) will keep pointing to KDE 4.14.3. You can use this repository URL for slackpkg+ or slapt-get or whatever package manager you use.

The URL (for 64-bit) and (for 32-bit) is pointing to my KDE 5 testing ground. I consider Plasma 5.2.0 as a “testing” release, with potential to be your next stable desktop, but with some caveats and reservations. The URL itself will remain permanent, even when the versions of the software components get updated. Currently “testing” points to version “5” in the repository because versions of Frameworks, Plasma and Applications are not co-ordinated and package updates may appear in the next months for these sub-sets. The “5” is a good middle ground. You should use this “testing” URL when you configure slackpkg+ or slapt-get if you want to upgrade to Plasma 5.

You must use only one of these URLs! I remind you that the KDE 5 preview I released last August was meant to be installed in parallel with KDE 4.14… but these new KDE 5 packages I am releasing today are going to replace the majority of KDE 4 packages. Therefore, the upgrade from KDE 4 to KDE 5 must be done manually, by closely following the provided README . Reading that README is even more important than before!

Enabling SDDM in runlevel 4 instead of KDM

Runlevel 4

If you want to see the new graphical session (login) manager SDDM in action, add the following lines to the Slackware file “/etc/rc.d/rc.4” right after the line: echo “Starting up X11 session manager…”

# — 8< ————————————–
if [ -x /usr/bin/sddm ]; then
exec /usr/bin/sddm
# — 8< ————————————–

… and then switch to runlevel 4 by typing at the command prompt (as root):

# init 4

Select “Plasma” from the SDDM session dropdown. Alternatively, if you prefer good old runlevel 3, you can type this at the command prompt (logged in under your own regular user account):

$ xwmconfig

… and select “xinitrc.plasma” as your default window manager for X11. Then run:

$ startx

To enter your desktop session.

Installing or upgrading Frameworks 5, Plasma 5 and Applications

As always, the accompanying README file contains full installation & upgrade instructions. Note that the packages are available in three subdirectories below “kde”, instead of directly in “kde”. This makes it easier for me to do partial updates of packages. The subdirectories are “kde4”, “frameworks” “plasma”,  “plasma-extra” and “applications”.

Upgrading to this KDE 5 is non-trivial. You will have to remove old KDE packages manually. If you do not have KDE installed at all, you will have to install some of Slackware’s own KDE 4 packages manually.

Where to get the new packages for Plasma 5

Download locations are listed below (you will find the sources in ./source/5/ and packages in /current/5/ subdirectories). Using a mirror is preferred because you get more bandwidth from a mirror and it’s friendlier to the owners of the master server!


  • In earlier preview release, HPlip would show an error message about not finding a system tray area. The reason is because the Plasma 5 workspace does not implement the X11 “Xembed” protocol. The system tray area works differently now. Not just HPlip, but all other applications that are not part of  Plasma  5, would have this issue, but only HPlip shows an error. Therefore some additional work was required to make the icons for Dropbox, Skype, Chromium, etc show in the Plasma 5 systray. This was done in the form of several notification support packages in the “deps/” directory and a patched Qt 4.
    • There is a solution for applications like SCIM who still can’t show a systray icon even with these added packages –  which is not elegant, but it works. Use a third-party Xembed system tray implementations like stalonetray or wmsystemtray . I have stalonetray and wmsystemtray in my own repository (I like wmsystemtray better). Both are also available at SBo.
  • Certain conditions may crash your Plasma Shell. I noticed this in a QEMU virtual machine where it was reliably reproducible: The crash occurs every time you move your mouse pointer into an Application Window placeholder in the taskbar. A crash of plasmashell makes your desktop go black and you are left with only the application windows that were currently open. Automatic restart should happen, but not for me unfortunately. You can fix it if you had a Konsole window open at the time of the crash. Type “plasmashell –shut-up &” and your desktop will re-appear.
  • The updated harfbuzz package breaks the library’s ABI. As a result, LibreOffice 4 will no longer work (error looks like “symbol lookup error: undefined symbol: hb_icu_script_to_script“).
    • Solution: Downgrading to the original Slackware harfbuzz package solves it, which is a pity because I thought I had taken care of the ABI breakage by applying a patch which re-adds that missing symbol.
  • The hardware keys for altering volume and mute still do not work on a global level (at least on my Lenovo T400 laptop). They seem to work for some applications – VLC is one of them. Sound is working fine though.
    • Solution: How dumb of me… just run “kmix” and a systray icon will appear, and the support for on-screen display of your hardware volume buttons will be enabled.
  • KRunner (Alt-F2) will still not save your command history.
  • When you try SDDM in runlevel 4 and the screen stays black with a blinking cursor in the upper left, this is probably caused by a missing homedirectory for the “sddm” user.
    • Solution: Check the output of command, it should return “/var/lib/sddm” and that directory must exist and be owned by the “sddm” user:

      $ getent passwd sddm | awk -F ‘:’ ‘{print $6}’

  • Even though you’ve selected “Plasma” as your desktop in the SDDM dropdown or in “xwmconfig”, the KDE 4 desktop is still starting up instead of the Plasma 5 desktop.
    • Solution: Remove the kde-workspace package and re-install the plasma-workspace package.
  • I have installed slackpkg+ and configured it as instructed. After installing KDE 5, when I run “slackpkg upgrade-all” it tries to pull in or upgrade all sorts of original Slackware packages. What’s up?
    • Solution: none yet… you’ll have to be careful for a while until I figure out what to do with all those packages.
  • The shutdown and reboot options are missing from the Leave menu.
    • Solution: a simple patch which removes the use of “kwrapper5” to start the KDE services will bring back both options. Kwrapper is meant to speed up the start of the Desktop Workspace and be a bit friendlier on resource usage but if you really do need shutdown and reboot options present, then apply the following patch to “/usr/bin/startkde”:
    • --- /usr/bin/startkde.orig       2015-01-31 18:09:25.744173291 +0000
      +++ /usr/bin/startkde    2015-01-31 17:49:18.938578280 +0000
      @@ -380,7 +380,7 @@
       # lock now and do the rest of the KDE startup underneath the locker.
       test -n "$dl" && KSMSERVEROPTIONS=" --lockscreen"
      -kwrapper5 ksmserver $KDEWM $KSMSERVEROPTIONS
       if test $? -eq 255; then
         # Startup error
         echo 'startkde: Could not start ksmserver. Check your installation.'  1>&2
  • Please report any other issue you encounter and I will add it here if it is serious enough.

Have fun! Eric


Comment from Hygor Hernane
Posted: January 28, 2015 at 17:55

Testing it right now. Looking good so far. Quiet and stable CPU so far( the last version was around 10% non-stop).

I had installed in kde 4.14.3 that module to configure the touchpad in the input sources config( kcm_touchpad) and its not working anymore…but its not that important.

Sound not working. I had both gstreamer and gstreamer1 with everything(good,bad,ugly) installed in the 4.14.3. Do you think i need to remove one? probably the one old? VLC backend dont work too.

The konsole inside Dolphin not opening. When i hit F4 dolphin opens

Bumblebee working normally. Wine too.

Comment from Hygor Hernane
Posted: January 28, 2015 at 17:57

sorry, hand stomped in the “submit”….anyway…

…When i hit F4 dolphins opens the “space” but the terminal dont show up.

Comment from Ben
Posted: January 28, 2015 at 18:30

> …When i hit F4 dolphins opens the “space” but the terminal dont show up.

I just built Yakuake and the embedded Konsole doesn’t appear there either.

Comment from Hygor Hernane
Posted: January 28, 2015 at 18:43

Krita asking for

Comment from alienbob
Posted: January 28, 2015 at 18:54

Hi Hygor Hernane, it looks like I updated the exiv2 package after I had compiled the 64-bit calligra package. Will have to recompile that one.

Comment from alienbob
Posted: January 28, 2015 at 19:00

Hi Hygor Hernane,

The kcm_touchpad version which can be found on SBo is only for KDE 4.
A ported version usable with Frameworks 5 is in KDE’s own git repository:

Comment from Eduardo
Posted: January 28, 2015 at 19:33

Thank you Eric! Will test it right now. The biggest issue now would be LibreOffice. Hope it gets solved soon.

Comment from Hygor Hernane
Posted: January 28, 2015 at 23:39

Dolphin was crashing when i tried to open some files in the context menu. After some testing, turning things on and off, i figured it out that the option to blame is “Send file via KDE Connect Service”

I failed to compile kcm_touchpad correctly btw. Not sure if its about the –prefix or something else.

Ill install the kde5 on my desktop too, so i can do some better testing. I always have problem with some things like audio and touchpad in this laptop.

At your service for more testing if u need Eric. And thx for all your work with Slackware .

Comment from Hygor Hernane
Posted: January 28, 2015 at 23:48

Just a thought after reading that guys post in Linux Questions, and u asked him to come to here:

– “xmconfig” still shows kde 4 options, besides the new option for plasma. Both starts the same things, the plasma.
– not using a login manager like kdm or sddm could have something related with the gstreamer service not working, at least for me, on kde5 ?

Comment from alienbob
Posted: January 29, 2015 at 00:09

Hygor I already aded the solution above: “Remove the kde-workspace package and re-install the plasma-workspace package”,
I also updated the README for this.
And a rebuilt 64-bit calligra package was uploaded which fixes the krita library error.

Comment from cwizardone
Posted: January 29, 2015 at 00:10

Thanks for all your hard work. It is installed and running and no problems so far.
Have to agree about the “retro look,” it is bone ugly!! Can’t remember ever seeing a worst looking desktop. Very “vga.”

Comment from Isaac Gomez
Posted: January 29, 2015 at 04:13


Another USA mirror:

Please note it is only for slackware-current since I dont have space for the whole repo.
For the issue with slackpkg+ I do this:

PKGS_PRIORITY=( ktown:.* )
REPOPLUS=( slackpkgplus ktown restricted alienbob )

So the alien pkgs take priority when updating. I also blacklist this
So is easy to see the updates.

I hope this works.

Comment from lucius.cornelius
Posted: January 29, 2015 at 06:37

gone are the colourful, exuberant 3D-ish icons, buttons and other graphical design elements. Flat and monochrome is the new dogma

Is this down to choice of default icons/themes and can that be changed back to more familiar icon sets, or is this a more permanent change?

Comment from Willy Sudiarto Raharjo
Posted: January 29, 2015 at 07:46

For those who installed previous KDE 5 and having a blank desktop when running startx for the first time after upgrading, try to remove (or rename) .kde5 and retry again.

This fixed the blank desktop screen. Probably due to configuration changes made by the new version which is incompatible with older release.

Other than that, it worked nicely here on my workstation 🙂

Big Thanks Eric!!

Comment from Willy Sudiarto Raharjo
Posted: January 29, 2015 at 07:52

Uh oh…
forgot to mention a bug here: i can’t set my time according to my timezone. It’s always set to UTC even though i set the timezone and disabled the UTC option.

Comment from lems
Posted: January 29, 2015 at 10:02

Hello Eric,

thanks a lot for your KDE5 packages. I’m sure it was a lot of work. I’ve installed it in a VM and it’s looking fine so far, except for a crash while browsing widgets. Will test some more.


Comment from Hygor Hernane
Posted: January 29, 2015 at 10:36

Sorry about before, didn’t see u updated the README. Moving on…

The kdevelop dont start. Trying to run from terminal shows “Cannot load library /usr/lib64/kde4/ ” and “Cannot load library /usr/lib64/kde4/”.

A windows pops up with:System COnfiguration Error “Could not find KTextEditor::Factory, check your installation: Make sure that Kate is installed, KDEDIRS is set properly and that you run kbuildsycoca4

Comment from Eduardo
Posted: January 29, 2015 at 14:53

I am afraid the READMEs are confusing. There is one README at

and another at

They give differing upgrade instructions (e.g., the /testing README gives less packages to remove).

Comment from alienbob
Posted: January 29, 2015 at 15:33

Eduardo, please refresh the pages in your browser. They are the same file. If one of them shows the older version it is because Akamai caches it.
Refreshing the browser helped here at work.

Comment from cwizardone
Posted: January 29, 2015 at 16:55

The only problem I’ve found, so far, is tiny fonts on panels, menus, etc. I haven’t been able to increase the size via the system settings.
Also, is there a way, as there is in KDE 4.14.x (and earlier) to go back to a “classic” menu vs. the default XP style menu. Also, can’t change the application menu default icon.
Whoever thought the day would come that the default KDE desktop would make the Xfce default desktop pretty by comparison. The appearance of KDE 5x reminds of the early days when I bought my first computer almost 30 years ago (and I was a late boomer). My Gawd is this thing ugly!

Comment from Eduardo
Posted: January 29, 2015 at 17:09

Alien: thank you. They are now the same.

cwizardone: for the tiny fonts, in System Settings, in Appearance > Fonts, check “Force fonts DPI” and put a sensible value, such as 96 (for non-retina monitors, for example).

For the classic menu: add the “Application Menu” to the panel and remove the “Application Launcher”.

Comment from Eduardo
Posted: January 29, 2015 at 17:13

Alien, thanks once more. This thing is beautiful and stable.

My biggest issue is Kwin. KDE5 was initially unusable, because Kwin got stuck in startup at 100% CPU usage. I got to work around the issue by killing KWin, then invoking systemsettings5 (without any window manager!), and in Compositor, selecting XRender as rendering engine. Picking any of the OpenGL variations would get me back to 100% usage and no display.

With XRender I get an usable environment, but I cannot change the window decorations. I just get a black square in the corresponding KCM module.

Thank you again and let’s hope KDE keeps improving from this start.

Comment from Willy Arana
Posted: January 29, 2015 at 17:21

Hi erick, thank you, this kde is really cool, but i have a trouble with yakuake, show me this message ” Yakuake was unable to load the Konsole component “, on the terminal i found this plugins should not have a ‘lib’ prefix: “” , any ideas?

Comment from cwizardone
Posted: January 29, 2015 at 17:26

> Posted: January 29, 2015 at 17:09
> for the tiny fonts, in System Settings, in Appearance > > Fonts, check “Force fonts DPI” and put a sensible value, > such as 96 (for non-retina monitors, for example).

Already tried that, but no joy. However, thanks for the suggestion.

Whoever said, “Beauty is in the eyes of the beholder,” was right!

Comment from Ben
Posted: January 29, 2015 at 17:37

Right click K icon, Alternatives->Application Menu for a Win 95 style start menu.

Comment from alexsson
Posted: January 29, 2015 at 22:20

Thank you Eric!

It seems my autostart scripts doesnt work anymore. It does not matter if I put them in ~/.kde/Autostart or ~/.kde/share/autostart.

I tried to add the script via Settings in “Startup and Shutdown”, but it does not work. I assume something change on how to write the autostart script?

Comment from alexsson
Posted: January 29, 2015 at 22:48

Also, the systray is not on my panel. I installed both sni-qt and sni-qt-compat32.

Cannot find systray as widget either.

Comment from alexsson
Posted: January 29, 2015 at 23:11

Ignore my last comment, I have the systray on my panel but a lot of apps does not show they systray icons.

I guess I have to try wmsystemtray.

Comment from fabio
Posted: January 29, 2015 at 23:20

so far so good. Brightness and volume control ok. disable touchpad fn key not working. asus laptop. Thank you very much. As for “Alice in flatland” style, i agree about being ugly.

Comment from noryungi
Posted: January 29, 2015 at 23:47

I am not going to install KDE5 right now on my Slackware machine, but I just wanted to thank you for all the hard work, and time invested in these packages!

Thanks Eric, keep up the good work!

Comment from cwizardone
Posted: January 30, 2015 at 00:07

It doesn’t remember the selected wallpaper. Log out and then log back in and the default wallpaper is presented.

Looks like there isn’t anyone on the KDE development team old enough to remember windows 3.1.

Comment from Willy Sudiarto Raharjo
Posted: January 30, 2015 at 07:15

@alexsson :
try to put the autostart in .kde5 instead of .kde

Comment from alexsson
Posted: January 30, 2015 at 10:09


Thank you. You mean that I should move everything to ./kde5 – directory?

I try to find documentations on things like where to put the config files, autostart scripts, themes e.t.c. Does anyone know of such documentation, I would appreciate it!

Comment from lems
Posted: January 30, 2015 at 10:25

Not sure if related to Slackware (Arch’ sddm was able to reboot and shutdown): I can’t seem to be able to reboot or shutdown via sddm. Instead, when the countdown reaches zero, it starts counting via negative numbers, i.e. -1, -2, etc. Pressing the Shut down or Reboot button has no effect. I also have no shutdown option from within KDE (my user is member of `power’ and other groups).

Comment from Willy Sudiarto Raharjo
Posted: January 30, 2015 at 12:19


No, KDE 5 will automatically use .kde5 by default
personally, i will not move everything to .kde5 since they may be incompatible, so it’s safer to start fresh 🙂

Comment from alienbob
Posted: January 30, 2015 at 14:02

Willy, actually I changed that for Plasma 5.2.0. The old preview release was meant to be temporary and not touching your KDE 4 installation, that is why the configurations would be written to .kde5 , .local5 , .config5 subdirectories in your homedirectory. Witl the new Plasma 5.2.0, the standard directories are used: .kde , .local and .config …

Comment from alienbob
Posted: January 30, 2015 at 14:09

lems. the shutdown and reboot in the SDDM main window are working on my computer and in my VM.

I do not have a shutdown or reboot option any longer in Plasma 5 (only a “switch user” courtesy of ConsoleKit), and I believe that is one of the drawbacks of not supporting systemd.

Comment from alienbob
Posted: January 30, 2015 at 14:16

Willy Arana, Are you using the “frameworks” branch of Yakuake? See

The master branch is for KDE 4.

Comment from cwizardone
Posted: January 30, 2015 at 15:01

KDE 5x is something only a mother could love, based on outward appearances, 🙂 so I’ve removed it by running removepkg on every single package that was downloaded and installed. I then reinstalled all the 4.14.3 packages and dependencies and qt-4 and harfbuzz from -current, and your OpenAL-1.15.1 package, deleted all the kde configuration files I could find, and rebooted.
No joy. KDE 4.14.3 won’t start. The spash page is seen for a moment then it falls back to a prompt. On the left side of the page it looks like memories addresses and on the right are references to various daemons, most all in /lib64 or /usr/lib64, for example,, and, etc., etc., etc.
Any suggestions would be appreciated. It would appear I missed a package somewhere, but I’ve done the re-install twice.
Oh, Xfce fires up just fine.
Many Thanks.

Comment from alienbob
Posted: January 30, 2015 at 15:16

I would doublecheck all of the packages in KDE 5’s “deps” directory and see if by removing those, you actually removed a package which Slackware installed at one time.
Also, try a fresh user account to see if this is caused by a configuration file.

Comment from Willy Arana
Posted: January 30, 2015 at 15:32

@Eric: Yes, i compile this branch but still not working, i change to tilda while find more documentation, i find this problem is also on dolphin, i think this get work with the futures version on kde

Comment from cwizardone
Posted: January 30, 2015 at 15:58

Thanks! I was missing strigi and downloaded and installed a copy from -current.

Comment from Michelino
Posted: January 30, 2015 at 18:44

Dropbox icon is not shown in systemtray.
Has anyone else got the same?

Comment from Phil
Posted: January 30, 2015 at 18:55

I have the same problem as lems. Have to wait for 30 secs to logout and from the main SDDM screen it counts down to zero and then negative numbers from then on. Had to hit the power button to shutdown.

Comment from Willy Arana
Posted: January 30, 2015 at 19:56

Yakuake is working! , i downlaod the git branch framework but i need create a link to /usr/lib64/plugins/ at /usr/lib64/qt5/plugins and work , 🙂

Pingback from Alien Pastures » Multilib glibc patched for GHOST vulnerability (CVE-2015-0235)
Posted: January 30, 2015 at 23:51

[…] KDE 5 (Plasma 5.2.0) available for Slackware -current […]

Comment from alienbob
Posted: January 30, 2015 at 23:56

Hi Willy Arana

I think that the need to create that symlink can be fixed when you add this definition to the cmake command in the SlackBuild:



Comment from Ben
Posted: January 31, 2015 at 01:43

Willy Arana,

> link to /usr/lib64/plugins/ at /usr/lib64/qt5/plugins and work

Thanks for the tip!

Comment from Willy Sudiarto Raharjo
Posted: January 31, 2015 at 01:48


Thanks for the clarification about the move .kde5 -> .kde again.

About the dropbox icon, i can confirm that indeed the icon is not showing, but it still works in the background and sync process still running

Comment from Widya Walesa
Posted: January 31, 2015 at 02:04

kwin_x11 crashed on my machine. Looks like it hits an old bug of AMD/ATI OpenGL Extension. Here is the complete output from kwin_x11 –replace:
QXcbConnection: XCB error: 3 (BadWindow), sequence: 170, resource id: 35651592, major code: 20 (GetProperty), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 183, resource id: 35651592, major code: 20 (GetProperty), minor code: 0
kf5.kiconthemes: “Theme tree: (Breeze)”
kwin_core: Extensions: shape: 0x “11” composite: 0x “4” render: 0x “b” fixes: 0x “50” randr: 0x “14” sync: 0x “31” damage: 0x “11”

Constructing a KPluginInfo object from old style JSON. Please use kcoreaddons_desktop_to_json() instead of kservice_desktop_to_json() in your CMake code.
Constructing a KPluginInfo object from old style JSON. Please use kcoreaddons_desktop_to_json() instead of kservice_desktop_to_json() in your CMake code.
Trying to load decoration plugin: “/usr/lib64/qt5/plugins/org.kde.kdecoration2/”
kwin_core: screens: 2 desktops: 1
kwin_core: Done.
kwin_core: User timestamp, ASN: 1161839
kwin_core: User timestamp, final: ‘ID: 39845895 ;WMCLASS: “konsole” : “konsole” ;Caption: “walecha : kwin_x11” ‘ : 1161839
kwin_core: Activation: No client active, allowing
kwin_core: screens: 2 desktops: 1
kwin_core: Done.
kwin_core: screens: 2 desktops: 1
kwin_core: Done.
kwin_core: screens: 2 desktops: 1
kwin_core: Done.
kwin_core: Initializing OpenGL compositing
kwin_core: Choosing GLXFBConfig 0xa0 X visual 0xc6 depth 24 RGBA 8:8:8:8 ZS 0:0
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD BONAIRE
OpenGL version string: 3.3 (Core Profile) Mesa 10.4.3
OpenGL shading language version string: 3.30
Driver: Unknown
GPU class: Unknown
OpenGL version: 3.3
GLSL version: 3.30
Mesa version: 10.4.3
X server version: 1.16.3
Linux kernel version: 3.18.2
Requires strict binding: yes
GLSL shaders: yes
Texture NPOT support: yes
Virtual Machine: no
Direct rendering: true

kwin_core: 0x0: OpenGL debug output initialized
kwin_core: Color correction: false
kwin_core: OpenGL 2 compositing successfully initialized
kwin_core: Vertical Refresh rate 60 Hz
kf5.kservice.sycoca: Trying to open ksycoca from “/home/walecha/.cache/ksycoca5”
Using FBConfig 0xa1 for visual 0xc7
No provider of glXBindTexImageEXT found. Requires one of:
GLX extension “GLX_EXT_texture_from_pixmap”
Application::crashHandler() called with signal 6; recent crashes: 1
KCrash: crashing… crashRecursionCounter = 2
KCrash: Application Name = kwin_x11 path = /usr/bin pid = 4027
KCrash: Arguments: /usr/bin/kwin_x11 –replace
KCrash: Attempting to start /usr/lib64/drkonqi from kdeinit
kwin: unable to claim manager selection, another wm running? (try using –replace)
Searching ‘No provider of glXBindTexImageEXT found’ on the internet, got several reports from 2010 (including one from freebsd to kwin developer) about it, like this one:

– plasmashell runs fine, even without WM, but no desktop
– I’m using hybridgpu, Intel+AMD with opensource driver.
– I’m using Mesa 10.4.x because mesa 10.3.x was not working well with vga switcheroo system (artefact, tearing, blank display, crashed, etc), particularly on the gpu switching event.

I’ll try to rebuild kwin and reporting back the results.

Any idea?

Comment from Widya Walesa
Posted: January 31, 2015 at 05:53

I’m back and now using KDE5 🙂
Rebuilding Qt5, kwayland, kwin, and plasma-workspace against mesa 10.4.3 solves the problem. Before, I was not able to choose EGL as OpenGL Interface.

Regarding kwayland and kwin, AFAIK kwin requires kwayland. But in your plasma modules list, the KDE.SlackBuild builds kwin before kwayland.

Comment from Widya Walesa
Posted: January 31, 2015 at 08:01

UPDATE and possible fix about KDE 5 on hybridgpu. Forgot to mention that I was using environment variable DRI_PRIME=1 in my ~/.profile, so KDE kwin_x11 will always using AMD GPU for primary. Unset the variable solves almost every crash related to ‘glXBindTexImageEXT’ I had before because right now KDE is using Intel GPU for primary. And also GPU auto switching via vga_switcheroo runs normally without the DRI_PRIME environment variable, unlike in KDE4 🙂 .

PS: Sorry for lots of noise 🙂

Comment from alienbob
Posted: January 31, 2015 at 13:37

Hi Widya, don’t apologize for the noise, your posts contain relevant and valuable information for other people.
And yes, I think you are right and kwayland needs to be built before kwin. I checked my 64-bit and 32-bit build logs. The 64-bit build was my development build, and was done incrementally. Apparently kwin there was built using a package of kwayland that I had built during an earlier increment. The 32-bit build on the other hand was done in one straight run, using the SlackBuild and there the logfile showed that kwin was unable to find KF5Wayland (provided by kwayland).

I fixed this in the git repository already, thanks for the hint.

I also saw that kwin was missing wayland_egl and apparently – as you found out – this needs a newer mesa than what’s available in Slackware-current.
That is a danger in itself, because KDE 5 is pretty bleeding edge, and the possibility exists that at some point in future, KDE 5 components will want stuff whose Slackware version is too old. And I am not prepared to add the whole X.Org stack to my KDE 5 dependencies… so there is a chance that I have to stop with my KDE 5 experiment then.

For now however, I am glad that you solved your issues with the newer mesa and also glad that the KDE.SlackBuild is easy enough that you found out how to use it and rebuild some of the packages 🙂

Comment from Ricardo J. Barberis
Posted: February 1, 2015 at 00:39

Bookmarking this entry, great job as usual, Eric!

Comment from LoneStar
Posted: February 1, 2015 at 14:50

Installed on a clean current64 in virtualbox. I can testify the same issue of @Phil and @lems: countdown for reboot and shutdown in SDDM goes to 0 and then goes on with negative numbers with no other chance than power off.

ps: the lack of wobbly windows is a show stopper 😛

ps2: also the systray issues due to the dropping of XEmbed are rather annoying, with wmsystemtray being a workaround but not really a good looking one. An embeddable widget for all xembed-dependant software should really be introduced.

Comment from Michelino Chionchio
Posted: February 1, 2015 at 17:38

About youkuake, adding:

in the SlackBuild didn’t solve in my case.
Any suggestion different from the softlink?

Comment from alienbob
Posted: February 1, 2015 at 21:17

Hi Lone Star,
Wobbly windows are configurable, I have it enabled on this laptop. It may be that your VM does not support it though.

About the shutdown counter that does not stop at zero but keps counting to negative values… I did not experience that here. There’s also nothing to find about it on the Internet. Perhaps wise to report it on the SDDM bug tracker?

Comment from alienbob
Posted: February 1, 2015 at 21:18

Hi Michelino,
No further tips here. I do not use yakuake.

Comment from Michelino
Posted: February 1, 2015 at 22:54

Thanks all the same Eric,
You already did too much for us!!!

Comment from Sam Albuquerque
Posted: February 2, 2015 at 13:48

@Hygor Hernane: Did you manage to get the embedded terminal working in Dolphin?

Would like to know if you found a solution.

Comment from alienbob
Posted: February 2, 2015 at 15:12

Sam, Hygor,
I think I have figured out what’s wrong with the and why the symlink was needed.
It is something I have to fix in my KDE.SlackBuild – for every tarball in Applications that has been ported to Qt5/Frameworks.
The Applications 14.12.2 are almost ready for release, and when they get released I will grab the opportunity to fix the dolphin/konsole issue.

Comment from Michelino
Posted: February 2, 2015 at 17:54

Happy to hear Eric!

We”ll wait for the update.

Comment from Michelino
Posted: February 2, 2015 at 18:18

(just to follow the post, I forgot to subscribe, sorry)

Comment from Skaendo
Posted: February 3, 2015 at 00:24

I have had 1 of the same issue as LoneStar, after logging out of KDE then trying to shutdown the timer continues past 0 into negative numbers. The only way I can shutdown is to press the power button from that point.

Thanks for building this for us, much appreciated!

Comment from dolphin77
Posted: February 3, 2015 at 07:04

Hi all.

First of all: Eric thank you very much. For all the hard work you have done and for shearing the results of it.

A question. Does anybody use touchscreen? General interface improved much for touchscreens, but I cannot find on screen keyboard. Used to be plasma board widget in Accessability section in the previous builds. What on screen keyboard is supposed to be used with KDE 5?

Best regards,

Comment from Sam Albuquerque
Posted: February 3, 2015 at 10:57

Thanks for looking into it Eric. Happy to wait till the next release.

Comment from Eduardo
Posted: February 5, 2015 at 12:26

Kwin’s 100% CPU usage with NVidia 304 legacy driver is a known issue:

I filed a (duplicate) bug, and a KWin developer supplied a great workaround. See it here:

Comment from Robby
Posted: February 6, 2015 at 09:29

Hi Eric, first thanks very much for the kde5 packages. I’m a little on the fence about the look … but we’ll see. My issues for interest:

1. amarok docks in the tray however I can’t see the main window ( there seems to be something called media tray as well in the system tray now ). right-clicking on the icon takes about 10 secs before the context menu shows and then there is only minimise and some play options

2. gwenview will not start when clicking an image file. It does start if I run it manually from krunner or the cli

3. it takes about 20 secs after hitting alt-f2 and starting krunner before it shows what you have typed

4. I had the libreoffice issue and downgraded harfbuzz

5. ksshaskpass is not working as expected – it does not seem to autostart and if you start it manually, you pop your pwd in, but it still does not seem to pass the passphrase through to the ssh-agent

6. I’ve got no idea where konsole is keeping it’s profiles now but it is not using those from .kde/share/apps/konsole – I’ve create some new profiles and searched for them by name but can’t find them

Note that I did not start on a fresh kde profile and use my profile ( .kde ) from kde4. I’ll see if I can get solutions to some of these otherwise I may revert to kde4 for a while.

Thanks for the packages Eric.

Comment from Robby
Posted: February 6, 2015 at 10:31

Further to my post above, I have some more info:

5, ksshaskpass works if you run .kde/Autostart/ manually so this seems to be an issue of the script not autostarting

7. darktable relies on /usr/lib64/ but /usr/lib64/ is now shipped; I’ve created a symlink for the moment

8. I’m having some problems with teamviewer seemingly not starting; it is shown as a running process but there is no visual indication that it is running

Comment from Willy Sudiarto Raharjo
Posted: February 6, 2015 at 11:09

try to recompile darktable and it should have linked to the correct libexiv2 library

about teamviewer: i just built it here and it’s working fine on my workstation. Have you started the rc.teamviewerd ?

Comment from Robby
Posted: February 6, 2015 at 11:14

@Willy yes I stop and then start tv:

/etc/rc.d/rc.teamviewerd stop | start

No visual indications that it is running. ps aux shows:

4337 0.0 0.2 143308 33464 ? Sl 11:30 0:01 /opt/teamviewer/tv_bin/teamviewerd –daemon start

Comment from alienbob
Posted: February 6, 2015 at 11:18

Hi Robby

There is a great write-up about changes in Autostart functionality for Plasma 5 (including a link to a bug report to get some of the now missing functionality back) here:

Basically, Plasma 5 looks for .desktop files in ~/.config/autostart/ now (you can create these using the “Autostart” control module in System Settings), and it will run these after the Plasma Workspace started. It will also source (not execute) any file it finds in ~/.config/plasma-workspace/env/ – this happens _before_ the Plasma Workspace is started.

Comment from alienbob
Posted: February 6, 2015 at 11:43

Robby, I did not experience these long delays with Krunner. n fact, I was amazed at how fast it returns results, from all kinds of “unexpected” but very useful places.

I hope that Applications 14.12.2 (just released last week) fixes some of the issues you are mentioning (gwenview etc). I had some big issues with getting the new tarballs compiled, so after a few days of failures I gave up for now. I am working on new Chromium packages, I pushed out new Flash Player updates yesterday and I have wasted 4 days in trying to fix the harfbzuz issue in Libreoffice on slackware-current with Plasma 5. No success.

So, I felt a bit down, and needed something working, hence the Chromium package build.

I will probably recompile Applications 14.12.2 after the weekend, hoping that the KDE distro packagers list will give an answer to my question about kde-workspace (it conflicts with plasma-workspace but on the other hand it is required by kget and kdeartwork at least).

Comment from Robby
Posted: February 6, 2015 at 18:35

Thanks Eric, I started with a fresh profile and Amarok is working now as is Teamviewer. Gwenview will still not execute from clicking on an image file. Still need to have a look at the autostart stuff for ksshaskpass.

Comment from Robby
Posted: February 6, 2015 at 18:36

Oh and krunner seems to be behaving normally as well now.

Comment from Owen Greaves
Posted: February 7, 2015 at 02:10

I am having one issue (rather large issue) with 5 – it installs as per your instructions just fine, it loads up the desktop, but all menu’s except for one do not work, they load a blank box or the contents of the menu is blank / transparent. But if I run the mouse over where menu items are, some show up and then go away. Any ideas on what I should be looking for?

Comment from LoneStar
Posted: February 7, 2015 at 15:36

@Eric, just for the sake of information, I realized that wobbly windows are not showing as available effect (among many others) because inside VirtualBox the rendering is on XRender instead of OpenGL, and the whole 3D accel functions are problematic inside a VirtualBox VM, also due to the fact that my laptop is a system with Nvidia Optimum. Long story short, all should work in a physical installation.

For the shutdown counter issue, I wonder if all others having the same problem are all using a VM like me or not?

Comment from Michelino
Posted: February 7, 2015 at 16:04

Same down counter “bug” here, in two different Pc, not VM

Comment from LoneStar
Posted: February 7, 2015 at 15:38

Btw, is it only me or the whole Dark Breeze theme is messed up? I’ve been told it’s the same also on Kubuntu.
When selecting Dark Breeze, the K menu is almost unreadable.

Comment from susu
Posted: February 7, 2015 at 19:31

Hi all,
I’ve installed all packages but something is not working… I think that als issues are linked together:
1) starting with init 4, sddm show a blank screen (I’ve checked the sddm home folder and it seems ok)
2) running startx with init 3 from the “root” user, it hangs with a blank screen (no cursor, nothing!) with no errors!
3) running startx with init 3 from a user it works.
4) from systemsettings5 (runned as user or with kdesu) in the startup section –> sddm options, when apply, it hangs!

Could you please help me?

Thanks a lot!

Comment from Owen Greaves
Posted: February 7, 2015 at 22:22

I should also mention, when I can open something, say like Kconsole – I can’t resize it or drag to another part of the desktop….for anything I am able to open. All dragging fails, and resizing anything fails.

Comment from Skaendo
Posted: February 7, 2015 at 23:33

I’ve noticed the same thing with the dark theme. I tried (unsuccessfully) to try and find a simple setting to change the font color.

Comment from susu
Posted: February 8, 2015 at 09:32

I’ve found my error, but I don’t know ho to solve it:

/usr/lib/kauth/kcmsddm_authhelper segmantation fault

Comment from LoneStar
Posted: February 8, 2015 at 13:47

Seems it has been addressed

Comment from Owen Greaves
Posted: February 8, 2015 at 21:38

I also get a blank Desktop, no clock or a taskbar, nothing, just the nice background image : )

Comment from Porobu
Posted: February 8, 2015 at 22:24

Just installed KDE5, everything works except for one thing. I dont get a suspend option and closing the lid only locks the screen. Any way to fix it?

Also thanks for the hard work 🙂

Comment from Ryan P.C. McQuen
Posted: February 8, 2015 at 22:52

Hi Eric,

Thanks for providing these packages. I cannot seem to get them working though. 🙁

Perhaps you can point me in the right direction. I am getting the following error:

ksplashqml: error while loading shared libraries: cannot open shared object file: No such file or directory

Full startx log here:

Comment from lems
Posted: February 9, 2015 at 10:57

Sorry for the late reply, Eric, but I now had time to set up another VM — using QEMU this time –, and I was able to reboot/shutdown via sddm. So seems to be virtualbox-related or so. I’m also happily running this now on my laptop.

What I noticed: some apps, like dolphin or okular, are missing translations, their menus are still in english even though I selected a language other than english.

I selected “double click” in dolphin and Mouse/Keyboard settings, but a desktop launcher regardlessly requires a single click only. This was different in KDE 4.

Other than that, amazing job on packaging this, Eric. (I really like sddm’s look.)


Comment from alienbob
Posted: February 9, 2015 at 22:39

Ryan, the missing library is part of the phonon-4.8.3-x86_64-1alien package.

Comment from alienbob
Posted: February 9, 2015 at 22:43

lems, the developers are apparently not yet organized enough to provide a full set of translations for the Applications tarballs.

Comment from Owen Greaves
Posted: February 9, 2015 at 22:46

Eric, is it possible my issue with blank menu’s and no taskbar are video driver related….I’m reaching here : )

Comment from alienbob
Posted: February 9, 2015 at 23:34

Owen, I have no idea. Can be video driver related, or you are missing a package, or… who knows.
Check the X session error log for more clues.
Remember, these packages are called “testing”… meaning I expect _you_ to do the testing.

Comment from Ryan P.C. McQuen
Posted: February 9, 2015 at 23:39

Thanks Eric. I guess I’ll try `slackpkg install phonon`.

I already did `slackpkg install ktown-testing`, is there some reason I wouldn’t be getting things from the deps folder?

Here are the important parts of slackpkgplus.conf:

PKGS_PRIORITY=( multilib:.* ktown-testing:.* restricted-current:.* alienbob-current:.* )


I do not have the kde group installed but I did install bluedevil, polkit-kde-agent and polkit-kde-kcmodules. I installed it all in init 3 and X was not running.

Thanks again!

Comment from Owen Greaves
Posted: February 9, 2015 at 23:46

Hey Eric, thanks….that’s what I’m doing….thought you might have some insight to save time : ) Sorry to bother you. Thanks for your work, I truly appreciate it.

Comment from alienbob
Posted: February 10, 2015 at 00:06

Owen, no need to apologize. If I had an answer I would write it down, but I am a simple Slackware package creator, not a KDE developer. For the real bugs (not related to packaging and installing) you might want to create KDE bug reports.

Comment from alienbob
Posted: February 10, 2015 at 00:08

Ryan, to my understanding “slackpkg install ” will only install packages that you currently do not have installed. It will not upgrade packages which you already have installed, like phonon. What happens when you run “slackpkg upgrade ktown-testing” afterwards?

Comment from Owen Greaves
Posted: February 10, 2015 at 00:10

No worries. I have been doing different install combinations to see if there are any differences, so far none….I’m on my last clean install – with NO KDE files installed – so a clean -current without KDE : )

Anyway, thanks for your response, and keep up the great packaging work – most of the time your packages install without incident, so I’ve been lucky. Later.

Comment from Ryan P.C. McQuen
Posted: February 10, 2015 at 03:46

Thank you Eric!!! `slackpkg upgrade ktown-testing` worked!

I guess I am a bit confused though. Should I run upgrade first or install first? When I install your multilib repo I just do a `slackpkg upgrade-all` and `slackpkg install multilib`, and that always works.

P.S. KDE5 looks so good!!!!!!!!

Comment from Owen Greaves
Posted: February 10, 2015 at 06:24

I am having the same problem with 4.13.3 – so there must be something specific to my machine : ( Although I’m still going thru the error log to find a common denominator.

Comment from Owen Greaves
Posted: February 11, 2015 at 07:15

Good News! Well, I told ya I wasn’t to bright…after checking the logs, finding a xset error with fonts (not a show stopper), I couldn’t find any errors in Xorg.0.log or see anything when I export startx to a file. Frustrated, I then went to Google many times, I guess I wasn’t entering the right keywords to find a hint of what to look for, I finally entered this phrase ” [B][I]KDE 5 can’t see menus[/I][/B] “. Anyway, I stumbled upon an old Forum post at, it suggested using the key strokes [B]Alt+Shift+F12[/B] to enable Desktop effects….so I tried it, and my blank menu problems went away, along with crappy dialogue boxes and even Konsole behaved properly. I am now trying everything in KDE 5, to see if something doesn’t work….it’s a bit clunky, but so far so good.

Thanks for putting up with me : )

Comment from Davide
Posted: February 12, 2015 at 02:48

Did someone had strange issues with polkit and networkmanager? I can’t have permissions on normal user nor read previous config.

Comment from susu
Posted: February 14, 2015 at 11:39

Ok… now is a mystery! On first init 4 launch at startup I’ve a black screen with a cursor (like the sddm home error). But if I do an init 3 and then init 4 another time it works! I’ve non error or warning in any logs…

Comment from Eduardo
Posted: February 16, 2015 at 23:07

KDE’s flexibility gave me a great workaround/stopgap replacement for Yakuake without any compilation:

1. Launch Konsole and customize it to your heart’s content.

2. Create a new virtual desktop or set aside one already available for the terminal. I set Desktop 4 apart for this purpose.

3. Move Konsole to said Desktop.

4. Maximize Konsole. In Konsole’s Kwin menu (Alt+F3) select More Actions > No Border.

There you are. Now, pressing Ctrl+F4 gives me an instant terminal, even with a sliding effect. Not exactly Yakuake, but it can do.

Pingback from Alien Pastures » KDE 5_15.02 release for Slackware-current
Posted: February 18, 2015 at 00:27

[…] Eduardo on KDE 5 (Plasma 5.2.0) available for Slackware -current […]

Comment from zrdc28
Posted: February 26, 2015 at 09:34

Thanks, eric for the hard work on this, I have only been running it for about 10 days. I have run many of the programs and checked it out pretty well.
The only real problem that I have is with trying to add widgets, it will crash on me every time. Dropbox works well but it does not have the usual icon in the taskbar. The cpu usage is about 2 to 3% and memory usage is about 350 to 400 m with just the desktop up. It seems to be much more stable than version 4 when it was introduced.

Comment from alienbob
Posted: February 26, 2015 at 11:07

Hi zrdc28,
If you want the dropbox icon, you will have to install wmsystemtray and follow directions as written in

Pingback from Alien Pastures » Updated KDE 5 packages for Slackware (release 5_15.02_02)
Posted: February 27, 2015 at 14:45

[…] are completely new to KDE 5 for Slackware, I urge you to also read my previous posts about KDE 5_15.01 and KDE 5_15.02 in its entirety, as well as the follow-up article about  the changes in system […]

Pingback from Reparar el problema con la terminal en Dolphin en Plasma 5
Posted: February 27, 2015 at 17:45

[…] Entonces pensé que se trataba de algún problema en algún paquete que use Dolphin para este fin, por lo que busqué en Internet y encontré esta página que hablaba acerca de Plasma 5: […]

Pingback from Reparar el problema con la terminal en Dolphin, en Plasma 5 – Noticias de Tecnología, Noticias de Tecnología en México, Noticias de Tecnología en el mundoNoticias de Tecnología, Noticias de Tecnología en México, Noticias de Tecnología en el mundo
Posted: March 5, 2015 at 17:02

[…] Entonces pensé que se trataba de algún problema en algún paquete que use Dolphin para este fin, por lo que busqué en Internet y encontré esta página que hablaba acerca de Plasma 5: […]

Comment from Thiago Melo
Posted: March 23, 2015 at 17:43

Installed kde5 and everything is running fine, but i got a problem with accents between konsole and dolphin.

If i create a file with accent in dolphin like testçãó.txt in konsole he reads “test���.txt”

if i create a file in konsole like kóóção.txt i got kókóção.txt in dolphin.

using pt_BR lang in kde and bash
declare -x LANG=”pt_BR”
declare -x LANGUAGE=””
declare -x LC_COLLATE=”C”

tryied to swithc to utf-8 and iso but no dice.

Comment from alienbob
Posted: March 24, 2015 at 14:53

Hi Thiago,

If there is not yet a bug report for your issue, perhaps it would be a good idea to create one now, on

Comment from Robinspi
Posted: November 27, 2015 at 20:22

So, is KDE 5 (in slackware-current) stable enough for pretty much seamless usage? I will be making a computer for my grandparents with Slackware 14.1 on it, and I hope to use KDE 5 as it looks to be one of the most user-friendly DEs out there… In the opinion of whoever reads/responds to this, would it be feasible for me to set it all up, give it to them, for web-streaming/surfing, and occasional picture/video download? My system specs are powerful enough, I pretty much know that already…

So far it sounds like a yes. 😉

Comment from alienbob
Posted: November 27, 2015 at 22:08

Robinspi – why are you commenting to a 10 month old article? In the meantime, I have written many more posts about Plasma 5 and it would have made more sense to add your comments there.

Additionally, my Plasma 5 packages are for Slackware -current, not for 14.1. Do not burden your old folk with Slackware development version, topped with an experimental desktop environment. This is a configuration which will not be straight-forward to maintain except for Slackware veterans.

Comment from Mark
Posted: November 11, 2016 at 18:59

I was having some minor issues with a KDE 4.14.21 on a recently installed Slackware 14.2. I posted a bug report on and was informed that KDE is no longer supported and that all major distro have updated to Plasma 5.8.

Here’s my question … if you have some inside info: Do you have any idea when Slackware will have Plasma 5 as a standard part of the distro? This blog of yours appears to be a year or more old, and Chris Feck of said the switch to Plasma 4 from KDE 4x was announced 3 years ago. I can and likely will follow your procedures to test Plasma, but for production use I prefer using “official” distro update. THX

Comment from alienbob
Posted: November 11, 2016 at 21:47

Mark, as I tell everyone who asks me this question: you really have to ask Patrick. If it were up to me, KDE 4 would have been replaced by now. But Pat will have his reasons for holding back on the migration.
I will tell you this: I will be mighty relieved if he finally decides to move on to Plasma 5. Maintaining the ‘ktown’ repository has brought me to the breaking point, and that is one of the reasons for the recent 3 month hiatus inbetween my package releases.

Comment from alienbob
Posted: November 11, 2016 at 21:49

Also Mark, why the hell are you replying to an almost two-year old article? The most recent Plasma 5 post was earlier this week. If you want to ask stuff, use the comments section below the relevant *recent* posts please.

Comment from Mark
Posted: November 14, 2016 at 05:47

alienbob: “why the hell are you replying to an almost two-year old article?” I knew you were going to mention that given your similar comment to Robinspi (which I miss initially). The reason is that when I was googling for some insight on this problem, this particular article popped up, not the more recent ones. So I signed up and commented, simple as that. I promise to be more timely … now that I know.

Write a comment