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

My Favourites

Slackware

Calendar

September 2018
M T W T F S S
« Aug    
 12
3456789
10111213141516
17181920212223
24252627282930

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

RSS Slackware64-current

RSS SBo

Meta

Qt 5.11.1 and Plasma 5.13.1 in ktown ‘testing’ repository

A couple of days ago I recompiled ‘poppler’ and the packages in ‘ktown’ that depend on it, and uploaded them into the repository as promised in my previous post.
I did that because Slackware-current updated its own poppler package and mine needs to be kept in sync to prevent breakage in other parts of your Slackware computer. I hear you wonder, what is the difference between the Slackware poppler package and this ‘ktown’ package? Simple: my ‘poppler’ package contains support for Qt5 (in addition to the QT4 support in the original package) and that is required by other packages in the ‘ktown’ repository.

But that was not all I updated this week. I have refreshed my ‘testing’ repository on ktown  with bugfix releases for Qt and Plasma. Both were introduced earlier this month in my repository with their ‘point releases’ 5.11.0 and 5.13.0 respectively, and within a week updates became available to squash reported bugs. Both releases are according to their schedules, so nothing alarming there. Business as usual. But since stability is a good thing, I decided not to adhere to my usual montly cycle of pushing updates to my repository.

Therefore I have built new packages for ‘qt5’ version 5.11.1 and for the full ‘plasma’ set (version 5.13.1) and uploaded them to my ‘testing‘ repository.

On this occasion I took the plunge myself and upgraded my laptop’s Plasma Desktop to these ‘testing’ packages. Works well!

I also took the opportunity to check how dependent the Frameworks would be on the new Qt5 release, since I have rebuilt all of the Frameworks packages in ‘testing’ against this 5.11 release of Qt5. As it turns out, there is only one Frameworks package that needs a recompilation when switching from Qt 5.9 to 5.11 and that is the ‘kdeclarative‘ package. If you use all the Frameworks package from ‘latest‘ repository instead of ‘testing’ then the Plasma Shell will not start and you will end up with a black desktop and only the application windows that were started because of session-restore will be visible. As you may know, the Plasma Shell can be restarted from the commandline in case of issues (crashes, graphical artefacts etc) with the command “plasmashell –replace” at a terminal command prompt. What happens if your kdelarative package is compiled against the wrong Qt5 is this:

eha@baxter:~$ plasmashell –replace
org.kde.kwindowsystem: Loaded plugin “/usr/lib64/qt5/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemX11Plugi
n.so” for platform “xcb”
org.kde.plasmaquick: Applet preload policy set to 1
plasmashell: relocation error: /usr/lib64/libKF5Declarative.so.5: symbol _ZN15QQmlPropertyMap15allocatePrivateEv version
Qt_5 not defined in file libQt5Qml.so.5 with link time reference

This can be fixed by replacing the ‘kdelarative’ package in Frameworks with a version that was compiled against the Qt5 your system is using.

So, in future Frameworks updates I will likely only have to recompile ‘kdeclarative’ for the ‘testing’ repository and create hard-links for all the other packages. I already am using hard-linking for all the packages that are identical in both ‘latest’ ad ‘testing’ to conserve space.

And with my laptop’s upgrade to ‘testing’, my Chromium browser stops complaining about missing browser integration support. Remember that Plasma 5.13 has a new package ‘plasma-browser-integration’ which introduces desktop controls (in your system tray for instance) to manage certain aspects of browser behavior (Chrome, Chromium, Firefox). I installed and activated the Plasma extension from the Chrome Web Store into Chromium and now I have a control widget in my system tray whenever music or a video is playing in a browser tab. Also, Plasma search (Alt-F2) is able to find individual browser tabs now.

Again I promise to generate a Plasma Live ISO, containing the latest Qt5 and Plasma5… this time I hope to be able to keep that promise. The last ISO was more than 2 months ago and is due a refresh.

Comments

Comment from Eduardo
Posted: June 24, 2018 at 17:21

Thank you Eric! Will download these right now.

Comment from Eduardo
Posted: June 24, 2018 at 21:08

Eric, I can confirm that everything went out smoothly so far. Thank you again.

Comment from alienbob
Posted: June 24, 2018 at 22:37

Eduardo, good to get confirmation, thanks.
I have now also uploaded a rebuilt akonadi package to ‘testing’. Its sqlite3 backend was broken because it was linked against the older Qt5.

Comment from Eduardo
Posted: June 25, 2018 at 17:13

Thank you Eric. Will download these too.

Pingback from Links 25/6/2018: Perl 5.28.0, Linux 4.18 RC2, KBibTeX for KDE Frameworks 5 | Techrights
Posted: June 25, 2018 at 22:48

[…] Qt 5.11.1 and Plasma 5.13.1 in ktown ‘testing’ repository […]

Comment from chrisretusn
Posted: June 27, 2018 at 15:24

Plasma 5.13.1 fixes a few cosmetic issues I was seeing with the System Tray. Some icons were not showing up, for example when inserting an USB the Device Notifier would not appear, the Status and Notifications would instead. All is well now, so far. 😉

Comment from Drakeo
Posted: June 29, 2018 at 01:52

Do you plan on rebuilding this in the latest gcc for current ?
yours was out on the 24th of June.
If not will rebuild in the 8 TY for the builds

Comment from alienbob
Posted: June 29, 2018 at 07:23

Drakeo.
Why Should I rebuild Plasma5 with a newer gcc? Is there anything that got broken in Plasma5 as a result of the compiler upgrade?

Comment from Marcus_777
Posted: June 29, 2018 at 17:54

I have a problem that does not concern directly your plasma packages. After upgrading pulseaudio to latest Pat pulseaudio-12.0-x86_64-2.txz, process gsettings-helper consume 50% CPU and grow up to 6GiB. If I kill this process, then pulseaudio process take 5GiB of memory and cca 50% CPU. Does anyone have a similar experience?

Comment from Regnad Kcin
Posted: July 1, 2018 at 14:40

Thanks for adding the Wacom Tablet support. Unfortunately the stylus (drawing) tool does not seem to work. Tablet buttons are ok. The stylus functions well in fluxbox under X support but it seems that the kded daemon is not working correctly. In KDE5 the tablet detection tool functions normally and finds the tablet, stylus and eraser just the same as does “xsetwacom list”. I can set up buttons on the tablet for various functions but there is no stylus tool, only mouse-like tracking but no selection nor drawing. thanks.

Comment from Regnad Kcin
Posted: July 1, 2018 at 18:19

Sir, I tried the wacom pad with a different installation of slackware64 -current and kde5 on the same machine and it works just fine or at least better (havent fully checked it out) so it appears to be related to something conflicting in my old installation. will work on it.

Comment from Regnad Kcin
Posted: July 1, 2018 at 19:17

Turns out that there was an offending file kded_wacomtablet.so that was in my working system that was not to be found in the test system I had set up. disabled that file and voila the stylus works! dont know where it came from, perhaps from my poking around with the tablet many days ago.

Comment from alienbob
Posted: July 1, 2018 at 20:44

Regnad, good!

Comment from Eduardo
Posted: July 5, 2018 at 16:44

Hi Eric, just wanted to report that I upgraded to Plasma 5.13.2 in testing and everything works very well. Thank you!

Comment from ArTourter
Posted: July 6, 2018 at 02:01

Hi Eric,
I have upgrade my systems to 5.13.2 and every thing seems to work fine with the exception of one tab in the “system settings” where the first 3 sub-tab of the “Workspace Theme” tab are blank.
Is it something you can replicate or it is something specific to my system?

Comment from alienbob
Posted: July 6, 2018 at 09:30

ArTourter does this get fixed after a reboot? What are the errors you see when you start “systemsettings5” from a terminal commandline and then click on “Workspace Theme”?

Comment from ArTourter
Posted: July 6, 2018 at 12:59

I had not rebooted the machines before seeing the problem (only restarted X) but having done that now (to get the updated kernel on) and I am still getting the same behaviour. The error messages I get from the command line are:

$ systemsettings5
QCoreApplication::arguments: Please instantiate the QApplication object first
WARNING: viewBackgroundColor is deprecated, use backgroundColor with colorSet: Theme.View instead
WARNING: viewBackgroundColor is deprecated, use backgroundColor with colorSet: Theme.View instead
KActivities: Database connection: “kactivities_db_resources_139994360707008_readonly”
query_only: QVariant(qlonglong, 1)
journal_mode: QVariant(QString, “wal”)
wal_autocheckpoint: QVariant(qlonglong, 100)
synchronous: QVariant(qlonglong, 0)
Nothing to load – the client id is empty
Nothing to load – the client id is empty
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:90:27: Unable to assign [undefined] to QString
org.kde.kcoreaddons: Error loading plugin “kcm_lookandfeel” “The shared library was not found.”
Plugin search paths are (“/usr/lib64/qt5/plugins”, “/usr/bin”)
The environment variable QT_PLUGIN_PATH might be not correctly set
“file:///usr/share/kpackage/kcms/kcm_lookandfeel/contents/ui/main.qml”
“Error loading QML file.\n82: \”QtControls.Button.icon\” is not available due to component versioning.\n”
KActivitiesStats( 0x24f8ff0 ) ResultModelPrivate::onResultScoreUpdated result added: “kcm:kcm_lookandfeel.desktop” score: 7.39866 last: 1530873217 first: 1518222807
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:90:27: Unable to assign [undefined] to QString
org.kde.kcoreaddons: Error loading plugin “kcm_desktoptheme” “The shared library was not found.”
Plugin search paths are (“/usr/lib64/qt5/plugins”, “/usr/bin”)
The environment variable QT_PLUGIN_PATH might be not correctly set
“file:///usr/share/kpackage/kcms/kcm_desktoptheme/contents/ui/main.qml”
“Error loading QML file.\n133: \”QtControls.Button.icon\” is not available due to component versioning.\n”
KActivitiesStats( 0x24f8ff0 ) ResultModelPrivate::onResultScoreUpdated result added: “kcm:kcm_desktoptheme.desktop” score: 4.16857 last: 1530873273 first: 1508012659
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:90:27: Unable to assign [undefined] to QString
org.kde.kcoreaddons: Error loading plugin “kcm_cursortheme” “The shared library was not found.”
Plugin search paths are (“/usr/lib64/qt5/plugins”, “/usr/bin”)
The environment variable QT_PLUGIN_PATH might be not correctly set
“file:///usr/share/kpackage/kcms/kcm_cursortheme/contents/ui/main.qml”
“Error loading QML file.\n137: \”QtControls.Button.icon\” is not available due to component versioning.\n”
KActivitiesStats( 0x24f8ff0 ) ResultModelPrivate::onResultScoreUpdated result added: “kcm:kcm_cursortheme.desktop” score: 2.93847 last: 1530873462 first: 1530824662
org.kde.kcoreaddons: Error loading plugin “kcm_icons” “The shared library was not found.”
Plugin search paths are (“/usr/lib64/qt5/plugins”, “/usr/bin”)
The environment variable QT_PLUGIN_PATH might be not correctly set
“file:///usr/share/kpackage/kcms/kcm5_icons/contents/ui/main.qml”
“Error loading QML file.\n231: \”QtControls.Button.icon\” is not available due to component versioning.\n”
KActivitiesStats( 0x24f8ff0 ) ResultModelPrivate::onResultScoreUpdated result added: “kcm:kcm_icons.desktop” score: 4 last: 1530873495 first: 1530835828
file:///usr/share/kpackage/genericqml/org.kde.systemsettings.sidebar/contents/ui/introPage.qml:90:27: Unable to assign [undefined] to QString

Hope this helps

Comment from Regnad Kcin
Posted: July 7, 2018 at 17:57

Hi. Am using “testing” version on slackware64-current I was having difficulty with SCIM displaying lacunae (empty boxes) rather than Chinese characters for some characters. Fixed by deleting all of the noto-CJK fonts.

Comment from alienbob
Posted: July 7, 2018 at 21:07

Regnad Kcin, perhaps I should look whether there’s a newer version of the Noto CJK fonts. But thanks in any case, for supplying a problem description along with the solution.

Comment from ArTourter
Posted: July 8, 2018 at 18:13

Eric,
I looked a bit more into this. I think the “library not found” messages in my previous post are a red herring as the libraries are definitely present. I tried setting QT_DEBUG_PLUGINS to 1 and these messages do not appear any more. However the “…not available due to component versioning” ones still do.

Let me know if you want me to run more diagnostics.

Write a comment