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 342 other subscribers

My Favourites

Slackware

Calendar

November 2017
M T W T F S S
« Oct    
 12345
6789101112
13141516171819
20212223242526
27282930  

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.

Comment from Eduardo
Posted: September 25, 2017 at 17:42

Thanks Richard and Gérard. Today I went to the office and I was surprised with my printer refusing to talk to the computer. Now it prints correctly again.

Comment from Gérard Monpontet
Posted: September 26, 2017 at 11:22

Obsolete deps packages with current now:

ninja
PyQt
sip
sni-qt (hplip applet work without this, now)
poppler need update to 0.59.0

plasma5, packages need rebuild:
okular need rebuild with poppler-0.59.0
kfilemetada5, also
krita,also

Comment from Gérard Monpontet
Posted: September 26, 2017 at 12:54

Today krita is updated:

https://download.kde.org/stable/krita/3.3.0/

Comment from Gérard Monpontet
Posted: September 26, 2017 at 15:34

Kdeconnect-kde is also updated (1.2):

work here 😉

Comment from alienbob
Posted: September 27, 2017 at 14:38

I have uploaded a couple of updated packages

current/deps/ sip, PyQt, ninja: removed from the ktown -current repository
because the stock Slackware packages can again be used.
current/deps/ phonon-vlc: rebuilt.
current/deps/ poppler: updated (added python3 support).
current/kde/applications/ kig, okular: rebuilt.
current/kde/applications-extra/ calligra, kdevelop, kile: rebuilt
current/kde/applications-extra/ krita: updated.
current/kde/frameworks/kfilemetadata5: rebuilt.
current/kde/kde4/ qtruby, smokeqt: rebuilt.
current/kde/plasma-extra/kdeconnect-framework: updated.
current/kde/plasma/plasma5-nm: rebuilt.

Comment from Eduardo
Posted: September 28, 2017 at 16:15

Thank you Eric for these updates!

Comment from Gérard Monpontet
Posted: October 1, 2017 at 14:15

HI, Eric, i have tested, a new cmake option on my buildscript for two personnal package here:(partitionmanager and digikam)

this option is:
-DHTML_INSTALL_DIR=/usr/doc/$NAME-$VERSION/HTML

this option work perfectly here for this two package,

and this option make obsolet this line in the buildscrip,
mkdir -p $PKG/usr/doc/$NAME-$VERSION
because it’s create before.

I will try on other packages, to see 😉

Comment from CapEnt
Posted: October 1, 2017 at 20:32

Hi Eric,

Great build!!

But i do have a question: is Dolphin is being compiled without baloo-widgets, or even baloo itself?
See this screenshot from current ktown dolphin: https://imgur.com/a/Y6BxW
Now, compare with this screenshot from current KDE Neon: https://imgur.com/a/E1BHt

There is a lot of information missing from the places and information panel on Dolphin in the current build. Taking a peek at the executable, i saw this:
slack@CapEnt:/var/log/packages# ldd /usr/bin/dolphin | grep -i baloo
slack@CapEnt:/var/log/packages#

While on Neon, i have that: https://imgur.com/a/FmIlT

Is that on purpose? I know that a lot of people hates the metadata framework and the desktop search features of Baloo integrated on Dolphin.

Tks!

Comment from alienbob
Posted: October 1, 2017 at 22:28

CapEnt indeed, my dolphin gets built after baloo5-widgets and the cmake does complain about not finding it. It’s likely the reason for the difference you are seeing.
I have updated the build order so that next time dolphin will be built after baloo5-widgets. Let’s see what that does for its search capability.
Thanks for notifying me about this discrepancy!

Comment from Mario
Posted: October 2, 2017 at 17:39

Hi Eric,
since your last upgrade, plasma is literally eating up my laptop! In less than one hour, plasmashell process grows till more than 10G of ram usage (laptop have 15G) !!! How is it possible?
Please help me, my laptop is unusable!
thx a lot

Mario

Comment from alienbob
Posted: October 2, 2017 at 21:17

Mario please debug your issue if you can and tell me where the root cause is. It’s not my computer so I can not tell you what to do.

Also, what do you call “last upgrade”? The 5_17.09 release on Sep 11 or the rebuilt packages on Sep 27?

Comment from Mario
Posted: October 3, 2017 at 09:54

Eric,
my last upgrde was last sunday, so I’ve the rebuilded packages installed. The I didn’t install the ones of Sep 11.
Can you provide me some methods to debug plasmashell process?
Thanks a lot!
Mario

Comment from Mario
Posted: October 3, 2017 at 10:44

Ok… maybe I found the problem… I removed all plasmoids on the desktop (cpu monitor, clock and a launcher), restarted plasmashell and now the memory usage seems to be stable. I’ll keep you update…
thanks a lot!
Mario

Comment from Mario
Posted: October 3, 2017 at 11:16

Finally I got it… the problem appears for sure when I try to switch between activities. Here the debug of plasmashell:

SwitcherBackend: FAILED to get the thumbnail “Codice di errore sconosciuto: 0\n\nPer piacere, invia una segnalazione dettagliata di bug a http://bugs.kde.org.” (“Errore non documentato”, “Errore non documentatoCodice di errore sconosciuto: 0\n\nPer piacere, invia una segnalazione dettagliata di bug a http://bugs.kde.org.”, “Dettagli della richiesta:URL: (sconosciuto)Data e ora: martedì 3 ottobre 2017 11:12:09 CESTInformazioni aggiuntive: “)
SwitcherBackend: FAILED to get the thumbnail “Codice di errore sconosciuto: 0\n\nPer piacere, invia una segnalazione dettagliata di bug a http://bugs.kde.org.” (“Errore non documentato”, “Errore non documentatoCodice di errore sconosciuto: 0\n\nPer piacere, invia una segnalazione dettagliata di bug a http://bugs.kde.org.”, “Dettagli della richiesta:URL: (sconosciuto)Data e ora: martedì 3 ottobre 2017 11:12:09 CESTInformazioni aggiuntive: “)
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:365: TypeError: Cannot read property ‘padding’ of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:364: TypeError: Cannot read property ‘padding’ of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:363: TypeError: Cannot read property ‘padding’ of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:362: TypeError: Cannot read property ‘padding’ of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property of null
file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:54:39: Unable to assign [undefined] to int

The part in italian is the content of the bug request. After this, RAM consumption grows fast and infinitely. I don’t know if there are other behaviours like this. May I’m missing some packages?

Comment from alienbob
Posted: October 3, 2017 at 14:47

Mario, how do you upgrade the Plasma5 packages? If you tell me how I can hopefully answer if you missed any of the updates.

Comment from Mario
Posted: October 3, 2017 at 14:59

Hi Eric,
simply with a “slackpkg upgrade ktown”…

Comment from Mario
Posted: October 3, 2017 at 20:01

The RAM consumption grows also when there is a slideshow as desktop background… in less the 3 minutes, ram consumption grows of 1 GB, with lot of lines like this in debug:
No metadata file in the package, expected it at: “/path/to/images/folder”

Comment from alienbob
Posted: October 3, 2017 at 20:54

Mario, with a simple “slackpkg upgrade ktown” you are not doing enough. That command will not install any of the packages I add to the repository, it only upgrades packages you already have installed.
And in this case, “slackpkg upgrade ktown” should be followed by “”slackpkg upgrade-all” to replace my deleted sip, PyQt and ninja packages with the originals from slackware-current.

Try the command “slackpkg install ktown” and see if that shows any new packages you still have to install.

And please file a bug on the KDE bugtracker if you can reproduce the memory leak.

Comment from Mario
Posted: October 4, 2017 at 15:20

It’s a bug… https://bugs.kde.org/show_bug.cgi?id=381000
There is a workaround in the bugtraker, if anyone like me has experiencing the bug issue. I hope they’ll fix soon.
Thanks a lot!
Mario

Comment from Pete Christy
Posted: October 4, 2017 at 19:46

First of all, a big thanks to Eric for his untiring efforts in support of Slackware and KDE5 in particular!

I’m having a problem that has me stumped, and I’m hoping someone has an answer. I have two machines running Slackware-current and Eric’s KDE5, all up to date and running well – except in one respect, namely kdenlive!

My old desktop machine (now relegated to my workshop) has an AMD Bulldozer processor, 8GB of RAM and an AMD/ATI Gfx card using the kernel (open source) drivers and vdpau.

The new machine has an Intel I7 quad core, 16GB of RAM and uses Intel graphics and va-api.

Kdenlive works fine on the old machine. On the new one it crashes all the time, with the most frequent error being:

KCrash: crashing… crashRecursionCounter = 2
KCrash: Application Name = kdenlive path = /usr/bin pid = 3479
KCrash: Arguments: /usr/bin/kdenlive
*** Error in `kdenlive’: malloc(): memory corruption: 0x00007f0474419180 ***

All other applications work fine. As far as I can tell, the only major difference between the machines is the AMD vs Intel graphics.

Does anyone have any ideas what might be causing this, or any other bug-hunting ideas?

Many thanks!


Pete

Comment from Gérard Monpontet
Posted: October 6, 2017 at 20:05

Just for info (qt5-5.9 is LTS version now :

https://www1.qt.io/qt5-9/

qt-everywhere-opensource-src-5.9.2.tar.xz is ready 😉

Comment from Myk267
Posted: October 7, 2017 at 05:30

Hey Eric. I’m enjoying your KDE5 builds!

In your README instructions (http://bear.alienbase.nl/mirrors/alien-kde/current/latest/README), you refer to rsync commands ending with a “dot” (ctrl+f for it), but each of them end in a ”5/”. Could you clarify what is meant here?

I appreciate it, and thanks for all of your help!

Comment from Gérard Monpontet
Posted: October 7, 2017 at 11:22

I have build qt-everywhere-opensource-src-5.9.2, with your script, Eric, no problem here 😉

Comment from alienbob
Posted: October 7, 2017 at 12:02

Myk267 – indeed that bit of text needs to be removed. The commands that follow that remark used to end in a dot. That was not too obvious to some, so I modified the commands to end with a (sub-) directoryname instead.
I’ll update the README for the next package release, thanks for reporting.

Comment from alienbob
Posted: October 7, 2017 at 12:53

Gérard since I will probably be building Plasma5 packages for some more months (at some point I assume that Patrick will take over) I do want to update the qt5 package to 5.9.2. I am not certain when that will happen – last half of october I will probably be too busy to work on Slackware.

Comment from Gérard Monpontet
Posted: October 7, 2017 at 13:42

Ok, Eric, if i can help, I would, i have time 😉

Comment from Gérard Monpontet
Posted: October 7, 2017 at 15:48

plasma-5.11 beta, run here, since 15 days without major problem 😉

Comment from Thorn Inurcide
Posted: October 8, 2017 at 18:56

Thanks for all you do Eric. Loving plasma 5

Comment from Moun
Posted: October 9, 2017 at 14:48

Thanks for all your work.

I’ve updated kde5 to 17.09, but since 17.07 I noticed that Firefox freezes some seconds at startup before becoming usable.

Also – but maybe it’s not related to kde5 since I’m not using it often- hp-toolbox offers a beautiful segfault. It seems related to python-2.7. Here’s gdb back trace (last lines)
(gdb) backtrace
#0 0x00007ffff6d52ff6 in strlen () at /lib64/libc.so.6
#1 0x00007ffff7a6b657 in PyString_FromFormatV () at /usr/lib64/libpython2.7.so.1.0
#2 0x00007ffff7ad6c0f in PyErr_Format () at /usr/lib64/libpython2.7.so.1.0
#3 0x00007fffe9ea51c7 in () at /usr/lib64/python2.7/site-packages/sip.so
#4 0x00007fffee576826 in initQtGui () at /usr/lib64/python2.7/site-packages/PyQt4/QtGui.so

Comment from Moun
Posted: October 9, 2017 at 18:21

Alien,
You can ignore what I said about Firefox : it’s more an extension issue (maybe noscript or requestpolicy) issue. Firefox runs fine without all theses extensions activated.

Comment from Moun
Posted: October 9, 2017 at 21:30

Alien,

I’ve recompiled hplib with qt5 support and now it works. Seems like it was a PyQt issue.

Comment from Gérard Monpontet
Posted: October 10, 2017 at 07:52

hplip on current is compiled with python3 now, pyqt and sip also 😉

Comment from Gérard Monpontet
Posted: October 10, 2017 at 17:19

Cosmetic, package ddcutils have doc in /usr/doc/-0.8.4 and also in /usr/doc/ddcutil-0.8.4 😉

Comment from Gérard Monpontet
Posted: October 10, 2017 at 17:53

In dep, json-glib-1.4.2 can be updated (need meson and ninja for build now, no problem here)

xapian-core-1.4.4 can be updated (no problem here)

new other:

cftiso-3.420
libburn-1.4.8
libpwquality-1.4.0
qtav-1.12.0

Also new version of krita, sddm, kpmcore, partitionmanager, are available.

just build plasma-5.11.0 with qt5-5.9.2, compil and work fine 😉

Comment from montagdude
Posted: October 30, 2017 at 20:20

Thanks very much for your work. Pretty much everything is working well here, except for the aforementioned bug with System Settings (thanks for the workaround). Plasma 5 is really nice to use.

There is one bug that has been around for a long time with Plasma 5, which causes down-sampled images to appear blurry when used as a background:

https://bugs.kde.org/show_bug.cgi?id=338506

The latest on the bug tracker indicates that it is an upstream Qt bug, fixed in 5.9.1. I see you already have that version in your packages for current, but a rebuild for 14.2 would be nice in the future.

Thanks again!

Comment from alienbob
Posted: October 30, 2017 at 22:25

Hi montagdude – I will probably never upgrade my qt5 package for Slackware 14.2, instead I keep it in sync with the version on slackbuilds.org. If that moves up to 5.9 then so will my version of the package.

Comment from montagdude
Posted: October 31, 2017 at 02:14

Okay, no big deal. Thanks again!

Write a comment