Main menu:

Sponsoring

Please consider a small donation:

 

 

Or you can donate bitcoin:

 

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

Page Rank

Fame

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.

Search

Subscribe to Blog via Email

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

Join 322 other subscribers

My Favourites

Slackware

Calendar

September 2017
M T W T F S S
« Aug    
 123
45678910
11121314151617
18192021222324
252627282930  

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

RSS Slackware64-current

Meta

Plasma 5 for Slackware – KDE 5_17.09

For some time now, no news about Plasma 5 for Slackware appeared on this blog. I just have been too occupied with family life and the demands of my day job.

But the configuration of my new server, the one I bought last month, finally is at a point where I can use it for running virtual machines and compiling packages. And it is fast… compiling LibreOffice in 90 minutes where in the past it would take me 10 times as long. Therefore I was able to create a new release of Plasma 5 packages while at the same time working on new LibreOffice packages.

I have uploaded the September ’17 set of Plasma 5 packages for Slackware 14.2 and -current to the ‘ktown’ repository. KDE 5_17.09 contains: KDE Frameworks 5.38.0, Plasma 5.10.5 and Applications 17.08.1. All based on Qt 5.9.1 for Slackware-current and Qt 5.7.1 for Slackware 14.2.
NOTE: I will no longer be releasing Plasma 5 packages for 32bit Slackware 14.2.

What’s new this time

Well, the good news is that ‘qt5‘ for Slackware-current is now at version 5.9.1. I did not want to risk waiting any longer for the 5.9.2 release which should be imminent but who knows what new bugs that will bring. Several of the other “deps” have been updated as well.
I added MP3 support to ‘kwave‘, and updated ‘digikam‘ and ‘krita‘ to their latest releases. Although… on Slackware 14.2 I had to stick with digikam 5.6.0. The newest digikam requires ‘exiv2‘ version 0.26. I did not want to risk breaking other (non-KDE) programs by adding a binary incompatible ‘exiv2‘ package to my ktown repository.
Other than that, it’s mainly stability and bugfix updates in the KDE software collection.

Installing or upgrading Frameworks 5, Plasma 5 and Applications

As always, the accompanying README file contains full installation & upgrade instructions.

Recommended reading material

There have been several posts now about KDE 5 for Slackware-current. All of them contain useful information, tips and gotchas. If you want to read them, here they are: http://alien.slackbook.org/blog/tag/kde5/

Where to get the new packages for Plasma 5

Package download locations are listed below (you will find the sources in ./source/5/ and packages in /current/5/ and  /14.2/5/ subdirectories). Only “bear” has the packages for now, the mirrors should follow within 24 hours. If you are interested in the development of KDE 5 for Slackware, you can peek at my git repository too.

Live ISO of PLASMA5

A new Plasma5 Live ISO image will follow shortly on http://bear.alienbase.nl/mirrors/slackware-live/latest/ in case you want to try it out first (check the timestamp of the ISO on the web page).

Have fun! Eric

Comments

Comment from Eduardo
Posted: September 11, 2017 at 22:05

Thank you Eric. Glad to know that the new box is helping. Downloading now!

Comment from LoneStar
Posted: September 12, 2017 at 00:54

Hello Eric,

still there is no fix for the issue with Akonadi and MariaDB 10.2.8, right?

Comment from LoneStar
Posted: September 12, 2017 at 00:59

I wonder if the patch referred in https://www.linuxquestions.org/questions/slackware-14/akonadi-and-mariadb-10-2-8-a-4175612895/page2.html#post5754254 could apply also on Akonadi 17.08.1

Comment from Cuetz
Posted: September 12, 2017 at 03:23

That’s awesome Erik, glad to hear your new box is running marathonic compiling sessions.
I’ll a try the Slackware live, and of course upgrade my system soon.

Comment from Deny Dias
Posted: September 12, 2017 at 06:46

Eric, I have just upgraded to your new KDE 5_17.09. All good except for Akonadi not working with MariaDB 10.2.

https://www.linuxquestions.org/questions/slackware-14/akonadi-and-mariadb-10-2-8-a-4175612895/page2.html#post5757837

As far as I can see from

http://bear.alienbase.nl/mirrors/alien-kde/source/5/kde/patch/akonadi/

you haven’t applied any of the patches suggested by Gerard here:

https://www.linuxquestions.org/questions/slackware-14/akonadi-and-mariadb-10-2-8-a-4175612895/#post5753877

Comment from Eduardo
Posted: September 12, 2017 at 07:12

Hi Eric, so far it runs ok here. Thanks!

Comment from Helios
Posted: September 12, 2017 at 11:29

Thank you very much !

There are some small problems :

/usr/bin/kile : libpoppler.so.67 => not found

/usr/lib64/qt5/plugins/libplasmanetworkmanagement_openconnectui.so: libopenconnect.so.5 => not found

Pingback from Links 12/9/2017: Linux 4.13.1, digiKam 5.7.0 | Techrights
Posted: September 12, 2017 at 18:26

[…] Plasma 5 for Slackware – KDE 5_17.09 […]

Comment from alienbob
Posted: September 12, 2017 at 20:54

Helios yes I think I will have to recompile kile to let it pick up the new poppler library. About the openconnect library: the README informs you that you have to install the openconnect package separately, it is not part of the ‘ktown’ repository.

Comment from alienbob
Posted: September 12, 2017 at 20:56

Lonestar, Deny, the issue is not with Akonadi but with Qt: https://bugs.kde.org/show_bug.cgi?id=383991 leads to https://bugreports.qt.io/browse/QTBUG-63108 (reported by our own Slackware friend pprkut).

Comment from Deny Dias
Posted: September 12, 2017 at 22:05

Oh, Eric! I see… Looks like we’re need to downgrade MariaDB again, as QTBUG-63108 as not even evaluated for a fix yet.

Thank your for your feedback.

Comment from alienbob
Posted: September 12, 2017 at 22:19

No, I will just use that patch and release updates for akonadi and kile. Eventually the Qt bug will be fixed and then the akonadi patch can go.
See http://bear.alienbase.nl/cgit/ktown/commit/?id=6f1fae6fa57584669ac297402f28d7a1e3203605

Comment from alienbob
Posted: September 12, 2017 at 23:13

FYI, kile and akonadi package updates are now available on bear.

Comment from Richard Herbert
Posted: September 12, 2017 at 23:22

AlienBob – Thanks so much. Akonadi is back, Baby!

Comment from Deny Dias
Posted: September 12, 2017 at 23:52

Oh! Eric! Your’re so sweet!!!!!! I’m going to update later today and let you know. Thanks for this!

Comment from LoneStar
Posted: September 13, 2017 at 00:05

Thank you Eric! Hopefully a proper patch for QT will come out soon

Comment from Deny Dias
Posted: September 13, 2017 at 00:33

Eric, akonadi-17.08.1-x86_64-2alien.txz worked like a charm! Thanks a lot, again!

As a side note, slackpkg complained about your ktown GPG key:

‘/media/nas/mirrors/alienbob/ktown/latest/CHECKSUMS.md5.asc’ -> ‘/dev/shm/slackpkg.eCmJCi/CHECKSUMS.md5-ktown.asc’

ERROR: Verification of the gpg signature on CHECKSUMS.md5
failed! This could mean that the file is out of date
or has been tampered with.

This has happened only after this most recent update (akonadi and kile). It was clean on yesterday’s update.

Comment from ArTourter
Posted: September 17, 2017 at 00:14

I have had a problem on the two machines I am running -current and ktown (one laptop, one desktop, both with intel GPUs) whereby if I suspend the display or change to one of the console TTYs while in a logged in session, the screen doesn’t wake up. And the only way to restore is to kill the X session and restart it.
It doesn’t happen before login (sddm login screen).
I cannot find anything in the logs I know of but I may not be looking in the right place.
Any pointer would be helpful.

Comment from alienbob
Posted: September 17, 2017 at 01:05

I have an Intel GPU in this laptop I am typing on (Lenovo 460): an “Intel Corporation HD Graphics 520 (rev 07)” using the i915 kernel driver. I have never experienced this issue you are describing. I can switch to a console from within this Plasma5 desktop session using Alt-Ctrl-F1 and then switch back later to the X session using Ctrl-F7 without any problem.

Comment from Arief JR
Posted: September 17, 2017 at 17:45

Dear eric, i have a small problem. after update kde plasma, then i try to take screenshot in rectangular region with spectacle the shortcut key won\’t launch. the shortcut key still default, has been not changed. Thanks

Comment from alienbob
Posted: September 17, 2017 at 17:51

Arief, you are experiencing this bug: https://bugs.kde.org/show_bug.cgi?id=384597
Updated source tarball for kglobalaccel are supposed to fix this: https://download.kde.org/stable/frameworks/5.38/kglobalaccel-5.38.1.tar.xz
I have not had time to create updated packages, also nobody reported this bug to me yet.

Comment from alienbob
Posted: September 17, 2017 at 23:12

I have uploaded a new ‘kglobalaccel’ package which fixes the bug Arief mentioned. I also refreshed the ‘akonadi’ package by applying the official patch to make it work with the new mariadb.

Also note that as of now, the packages in the “ktown” repository are signed with my new GPG key “769EE011” –
see https://pgp.mit.edu/pks/lookup?op=get&search=0x883EC63B769EE011

Users of slackpkg+ may want to run the command “slackpkg update gpg” to obtain the new gpg key.

Comment from Geremia
Posted: September 18, 2017 at 18:42

I ran \”slackpkg update\” and \”slackpkg upgrade-all\” today, and it downgraded many KDE apps from 17.08.1 to 4.14.3. Why would this be? My slackpkgplus.conf has this:

PKGS_PRIORITY=( multilib:.* ktown:.* restricted_current:.* alienbob_current:.* slackpkgplus:.* ponce:.* )
MIRRORPLUS[\’ktown\’]=https://bear.alienbase.nl/mirrors/alien-kde/current/latest/x86_64/
MIRRORPLUS[\’alienbob_current\’]=https://bear.alienbase.nl/mirrors/people/alien/sbrepos/current/x86_64/
MIRRORPLUS[\’restricted_current\’]=https://bear.alienbase.nl/mirrors/people/alien/restricted_sbrepos/current/x86_64/
MIRRORPLUS[\’ponce\’]=https://ponce.cc/slackware/slackware64-current/packages/
MIRRORPLUS[\’slackpkgplus\’]=https://slakfinder.org/slackpkg+/
MIRRORPLUS[\’multilib\’]=https://bear.alienbase.nl/mirrors/people/alien/multilib/current/

Is this not configured correctly?

Comment from alienbob
Posted: September 18, 2017 at 19:32

Geremia you seem to be missing the REPOPLUS definition which tells slackpkg which 3rd party repositories to use. Without the REPOPLUS variable, no 3rd party repository will be used at all.
From /etc/slackpkg/slackpkgplus.conf:

# List repositories you want to use (defined below)
# remember to launch ‘slackpkg update’ if you modify that row.
#REPOPLUS=( slackpkgplus restricted alienbob slacky )
#REPOPLUS=( slackpkgplus )

Comment from bam
Posted: September 19, 2017 at 01:48

Hi Eric,
thank you for openconnect support!
Could you please rebuild plasma5-nm against openconnect for Slackware 14.2 also?
Thanks

Comment from bam
Posted: September 19, 2017 at 02:13

Since update to this KDE in Slackware 14.2, no longer see hibernation/suspend option in kickstart menu.
Anyone else experienced this problem?
No idea where to dig so far..

Comment from Deny Dias
Posted: September 19, 2017 at 04:09

Eric, looks like your keys are somewhat invalid to slackpkg+. After run ‘slackpkg update gpg’ with no errors, ‘slackpkg update’ complains with:

ERROR: Verification of the gpg signature on CHECKSUMS.md5
failed! This could mean that the file is out of date
or has been tampered with.

The keys I have for your repos are:

‘/mirrors/alienbob/ktown/latest/GPG-KEY’ -> ‘/dev/shm/slackpkg.lpzcMF/gpgkey-tmp-ktown’
pub 4096R/769EE011 2016-08-21 Eric Hameleers (Alien BOB)

URL:http://bear.alienbase.nl/mirrors/people/alien/restricted_sbrepos/current/x86_64/GPG-KEY [17332/17332] -> “/dev/shm/slackpkg.lpzcMF/gpgkey-tmp-restricted” [1]
pub 1024D/A75CBDA0 2003-01-17 Eric Hameleers

‘/mirrors/alienbob/multilib/GPG-KEY’ -> ‘/dev/shm/slackpkg.lpzcMF/gpgkey-tmp-multilib’
pub 1024D/A75CBDA0 2003-01-17 Eric Hameleers (IBM Linux)

URL:http://bear.alienbase.nl/mirrors/people/alien/sbrepos/current/x86_64/GPG-KEY [17332/17332] -> “/dev/shm/slackpkg.lpzcMF/gpgkey-tmp-alienbob” [1]
pub 1024D/A75CBDA0 2003-01-17 Eric Hameleers

Maybe you’ve forgot to update CHECKSUMS.md5?

Comment from bam
Posted: September 19, 2017 at 05:06

Just sorted out problem with hibernation/suspend option.
Turned out it was due absent upowerd dependencies which gone for some mystical reason..

Comment from alienbob
Posted: September 19, 2017 at 15:45

Deny, what repository causes that error “Verification of the gpg signature on CHECKSUMS.md5 failed”? I did not see that error when I ran an update yesterday evening.

Comment from Deny Dias
Posted: September 19, 2017 at 18:23

Eric, unfortunately slackpkg+ does not provide a clear indication on which repository triggers a checksum error (maybe there’s room for improvements).

Anyway, I just ran it again and there was no error. Whichever was the culprit, it’s now fixed.

Comment from Gérard Monpontet
Posted: September 21, 2017 at 09:36

Just for info Eric, i have ‘pcre2’ and ‘pcre’ installed here:
and by default ‘qt5’ prefer pcre2 for build, if this two version are installed

Comment from Isaac Gómez
Posted: September 22, 2017 at 03:39

Hi, thank you for the update.

I installed this update on current however the login is very slow, the desktop takes like 3 minutes to show the background image, I checked with htop and iotop but there is no system overloading (cpu is like 10%). I tried to check the .xsession-errors file but kde5 is not creating it.

Do you know how can I debug the loading?

Thank you!

Comment from alienbob
Posted: September 22, 2017 at 17:15

Isaac, some people have initial issues with baloo (file indexer), try disabling that.
Otherwise you could try bootchart (https://slackbuilds.org/slackbuilds/14.2/system/bootchart/) to find out what causes the slowness.

Comment from Eduardo
Posted: September 23, 2017 at 17:39

Today Pat issued some major Python3 updates. Can anyone tell if these work OK with Alien’s last KDE5?

Comment from Gérard Monpontet
Posted: September 23, 2017 at 18:44

No problem, python-2.7* is always present.

Comment from Eduardo
Posted: September 23, 2017 at 19:14

Thanks Gérard!

Comment from Gérard Monpontet
Posted: September 23, 2017 at 21:03

Just the new ‘boost’ package, breaks libreoffice, no other problem, for the moment 😉

Comment from Gérard Monpontet
Posted: September 23, 2017 at 21:35

Eric, krita, need rebuild also, with new ‘boost’.

Comment from Richard Herbert
Posted: September 23, 2017 at 21:54

Slackware-current’s hplip-3.17.9-x86_64-1 isn’t compatible with Alien’s PyQt and sip packages:

hp-systray[2185]: error: No module named ‘PyQt4.QtCore’
hp-systray[2185]: error: Unable to load Qt4/Qt5 support. Is it installed?

Installing Slackware-current’s latest PyQt and sip packages corrects it.

Comment from Gérard Monpontet
Posted: September 23, 2017 at 22:07

It need pyqt and sip slackware-current version, because hplip is compiled on python3 now, it work here.

Write a comment