My thoughts on Slackware, life and everything

Tag: plasma5 (Page 13 of 15)

(Hopefully) final recompilations for KDE 5_15.11

plasma5_startup There was still some work to do about my Plasma 5 package repository. The recent updates in slackware-current broke several packages that were still linking to older (and no longer present) libraries which were part of the icu4c and udev packages.

So finally I had the time to cure this situation. I rebuilt kdelibs, kde-workspace and all the telepathy dependencies, updated all the KDE Telepathy packages, and also compiled a git snapshot for the kio-mtp package after some people complained about the Unicode character in its ‘slack-desc’ file which caused breakage in pkgtools.

Hopefully, everything works again this time. Even Telepathy. Tell me your experiences with Amarok and the Plasmashell which were crashing for some people. And especially Plasmashell crashing leaves you with no desktop at all.

Have fun! Eric

Cleanups from the -current update fallout

blueSW-64pxI think I have managed to fix most of the important breakage in my packages, after Slackware-current updated its icu4c package a couple of days ago.

Recompiled packages are now available for -current:

  • Regular packages: LibreOffice 5.0.3
  • KDE 5_15.11 packages: qt5 (which was bumped to 5.5.1 at the same time), step, akonadi4, akonadi, akonadi-search, akonadi-calendar and kdepimlibs. Here at home, Plasma 5 works again on latest slackware-current.
  • Multilib: fixed convertpkg-compat32 script so that it will properly handle the new eudev; and also updated the “compat32” package directory with a new eudev-compat32 package.

If there are other packages in my -current repository that require recompilation, please let me know!

Eric

Slackware-current got updated… 448 lines of ChangeLog

Another big update to slackware-current today.

The ChangeLog.txt entry of “Thu Oct 29 20:12:14 UTC 2015” counts 448lines, and a little less than half of that number consists of updates to packages; the rest is rebuilds. A massive package recompilation occured because several core libraries got updated and Pat is quite conscientious in getting all the library dependency issues resolved properly.

Items of interest: this batch contains several security updates (gvfs, jasper, curl, ntp, php, mozilla-firefox).

The kernel got updated (from 4.1.6 to 4.1.12)! Perl was refreshed too (to 5.22.0 coming from 5.18.1). Scons got added. And ConsoleKit2 got added too folks! This replaces the unmaintained ConsoleKit.

The GTK/GLib subsystem got overhauled thanks to the hard work of  Robby. And then there’s Mesa which is now at 11.0.4 accompanied by X.Org 1.17.3 and libdrm 2.4.65.

In the KDE department, several components were updated to their most recent releases: KDEvelop is now at version 4.7.2, Calligra went up to 2.9.8. The various Long Term Support (LTS) packages are now at their final versions: kdelibs to 4.14.13, kdepim* to 4.14.10 and kde-workspace to 4.11.22. No further updates for KDE 4 are expected.

All in all a potentially disruptive update. I suggest that you upgrade with care, especially if you are running my Plasma 5 packages. I have not yet had the time to test whether recompilations are required, and I am pressed for time (delivering training courses to a new Helpdesk team this week and the next) so it may take several more days before I can come up with rebuilt Plasma packages.

If you want to dive right in and report the Plasma 5 packages that no longer work for you, I’d be grateful.

Have fun! Eric

KDE 5_15.10 for Slackware-current brings Telepathy

plasma5_startup It’s october, the leaves are falling, we had our first frost this week… and here is yet another KDE 5 release for Slackware to keep you warm and cozy. I am happy with my KDE 5_15.10 update. Again I waited until every KDE source was refreshed: this set contains Frameworks 5.15.0, Plasma 5.4.2 and Applications 15.08.2.

And you know what? The “progress bar issue” which has plagued me ever since the first Plasma 5.4 release could finally be resolved, thanks to  Gérard Monpontet who posted the solution in the comments section of previous Plasma 5 blog post. I love it when the Slackware community helps fixing issues well before they start bothering Pat. Apparently, desktop sessions not only need to be started using a ConsoleKit process but also using a DBus invocation.

plasma5_startup

But that’s not all; there is a bit more to tell about the October release.

What’s new in KDE 5_15.10?

  • Frameworks 5.15.0 is an enhancement release with no new Frameworks added. You can read the details on https://www.kde.org/announcements/kde-frameworks-5.15.0.php
  • Plasma 5.4.2 is a bugfix release and perhaps the last before 5.5.0, because 5.4.3 will only be released if there’s a need for it. See https://www.kde.org/announcements/plasma-5.4.2.php . New this month is that I enabled the compilation of the “plasma-mediacenter” application, which you may or may not like, but at least you can check it out now.
  • Applications 15.08.2 was just released today. It is a bugfix release – but for Slackware it means the sudden appearance of a lot more packages. Because:
  • I have finally enabled KDE Telepathy in my KDE.SlackBuild framework. That’s 14 new packages for you! Only the voice & video GUI is still missing, the KDE Telepathy developers are looking for someone knowledgeable to port the old KDE 4 version to Frameworks 5.
    And to support building them, I had to add yet another 18 packages in the “deps” section. You will find those dependencies all self-contained in a single “telepathy” subdirectory right below “deps”. That way, if you don’t care much for Telepathy you can easily skip these packages. Similarly, the new KDE Telepathy packages are all located in a subdirectory “telepathy” below “kde”. The full list of new Telepathy dependencies is : libotr, libnice, farstream, libaccounts-glib, libaccounts-qt5, signon, signon-plugin-oauth2, signon-ui, libsignon-glib, telepathy-glib, telepathy-farstream, telepathy-haze, telepathy-gabble, telepathy-qt5, telepathy-logger, telepathy-logger-qt5, telepathy-mission-control and telepathy-accounts-signon.
  • I added a new package to “plasma-extra” because I did not want to wait for Plasma 5.5 where this program will likely be included by default. It is called “xembed-sni-proxy” and on startup (automatically when you launch a Plasma 5 desktop session) it will dock into the Plasma system tray area and start listening for XEmbed requests. Tray icons for applications adhering to the “legacy” XEmbed protocol will be displayed seamlessly inside the Plasma tray area, courtesy of xembed-sni-proxy). There is no longer a need for external tray applications like trayer-srg or stalonetray.

Here is a screenshot which shows the (XEmbed) HP system tray icon – snugly placed inside the xembed-sni-proxy tray area. You’ll also notice the reddish avatar at the left – that is KDE Telepathy, its color informing me that it is does not have any account configured yet.

plasma5_xembed

Installing or upgrading Frameworks 5, Plasma 5 and Applications

The remainder of the article is mostly a re-hash, but I include it every time so that you do not have to search through this blog, and have everything together on a single page.

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

Upgrading to this KDE 5 is not difficult, especially if you already are running KDE 5_15.09_02. You will have to remove old KDE 4 packages manually. If you do not have KDE 4 installed at all, you will have to install some of Slackware’s own KDE 4 packages manually.

Note:

If you are using slackpkg+, have already moved to KDE 5_15.09_02 and are adventurous, you can try upgrading using the following set of commands. This should work but feel free to send me improved instructions if needed (assuming in this example that you tagged my KDE 5 repository with the name “ktown_testing” in the configuration file “/etc/slackpkg/slackpkgplus.conf“):
# slackpkg update
# slackpkg install ktown_testing (to get the newly added packages from my repo)
# slackpkg install-new (to get the new official Slackware packages that were part of my deps previously)
# slackpkg upgrade ktown_testing (upgrade all existing packages to their latest versions)
# slackpkg upgrade-all (upgrade the remaining dependencies that were part of my repo previously)

And doublecheck that you have not inadvertently blacklisted my packages in “/etc/slackpkg/blacklist“! Check for the existence of a line in that blacklist file that looks like “[0-9]+alien” and remove it if you find it!

Recommended reading material

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

A note on Frameworks

The KDE Frameworks are extensions on top of Qt 5.x and their usability is not limited to the KDE Software Collection. There are other projects which rely (in part) on the KDE Frameworks, and if you are looking for a proper Frameworks repository which is compatible with Slackware package managers such as slackpkg+, then you can use these URL’s to assure yourself of the latest Frameworks packages for Slackware-current (indeed, this is a sub-tree of my KDE 5 “testing” repository):

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). If you are interested in the development of KDE 5 for Slackware, you can peek at my git repository too.

Using a mirror is preferred because you get more bandwidth from a mirror and it’s friendlier to the owners of the master server!

Have fun! Eric

Second Plasma 5 update for September

The previous update was targeted for August but due to the difficulties I had in compiling all packages, that release slipped to early September. That is why I can announce a second September release for my KDE 5 packages for Slackware. The KDE 5_15.09_02 update contains all new software: Frameworks 5.14.0, Plasma 5.4.1 and Applications 15.08.1.

I had a couple of complaints bout how my previous package set performed. The most annoying issue was the minute-long delay in displaying the “Leave” menu, and the minute-log delay in showing the Logout dialog when the Logoff widget was clicked. I found the cause. It was the LoginKit package which I had added because I hoped that it could help in keeping systemd out of Slackware. I have now removed LoginKit again, and the problem has disappeared. Anyway, ConsoleKit2 does what I hoped LoginKit would do: provide a useable systemd-logind compatible API. It looks like LoginKit will not be needed.

My other major annoyance has not been solved yet, and I am still in dubio whether this is being caused by the recent updates to slackware-current or by the recent Wayland-related code changes in KWin. The issue? Whenever the power saver kicks in and I am not paying attention, the screen of my Lenovo T400 laptop (Intel graphics) turns black. It looks like the backlight does not get turned back on when I move the mouse or press a key. I have to Ctrl-Alt-F1 to get to my Linux console, press the backlight-brightness button until I can see my screen’s content again, and then I can switch back to X using Alt-F7. Another thing: if the screenlocker started during this powersave period, the lock screen that stares me in the eye I switch back to the graphical console, is frozen. I can type my password but no visual feedback is provided, even when I press ENTER. But if I then press Alt-TAB, the screen suddenly refreshes and I see my Plasma 5 desktop in full glory. This looks like a desktop- or window refresh issue, which is why I think it may be related to KWin. I have not filed a bug report yet because I do not yet know against which component to file the bug.

Lastly, the progress bar which shows as part of the Plasma 5 startup splash screen, is not moving. Yet the desktop loads properly in the background and eventually the non-moving progress bar is replaced by the Plasma 5 desktop. Does anyone know if this progress bar is broken somehow? Does anyone know which software component draws that progress bar so that I can file a bug for this as well?

Let’s hope this will be addressed and get fixed eventually. Other than that, Plasma 5 is a fine desktop at the moment.

What’s new in KDE 5_15.09_02?

  • ConsoleKit2 (a drop-in replacement for Slackware’s unmaintained ConsoleKit) has been rebuilt with several patches provided by Robby Workman. And plasma-workspace was patched to allow the screenlocker to use the systemd-logind API provided by ConsoleKit2. No systemd needed! SDDM will again start a ConsoleKit session by adding “ck-launch-session” to the session startup (was accidentally removed previously)
  • As said earlier, I have removed the LoginKit package, it is not needed and did not play nice.
  • One addition to the “deps” is a rebuilt version of Slackware’s libproxy package. I have removed KDE 4 support from that package. The original Slackware libproxy package (with KDE 4 support) is causing crashes in Frameworks 5 (KF5) software which calls functionality in libproxy. One example is the OwnCloud client, and KDE Telepathy will also use libproxy (I am working on adding that soon)
  • I have removed the KDE 4 entry from “xwmconfig” because there is no more KDE 4 desktop session to start. Likewise, I have removed the “startkde4” script.
  • Frameworks 5.14.0 is an enhancement release, you can read the details on https://www.kde.org/announcements/kde-frameworks-5.14.0.php
  • Plasma 5.4.1 is a bugfix release, see https://www.kde.org/announcements/plasma-5.4.1.php . Nothing really stands out in the ChangeLog for this release.
  • Applications 15.08.1 was just released today. It is a bugfix release for the 107 programs which have already been ported to KF5 . Let me know what you think of the KF5 port of the Kontact Suite (KDEPIM) which was also updated… I do not use it myself.

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 several subdirectories below “kde”, instead of directly in “kde”. This makes it easier for me to do partial updates of packages. The subdirectories are “kde4”, “kde4-extragear”, “frameworks” “plasma”, “plasma-extra” and “applications”.

Upgrading to this KDE 5 is not difficult, especially if you already are running KDE 5_15.09. You will have to remove old KDE 4 packages manually. If you do not have KDE 4 installed at all, you will have to install some of Slackware’s own KDE 4 packages manually.

Note:

If you are using slackpkg+, have already moved to KDE 5_15.09 and are adventurous, you can try upgrading using the following set of commands. This should work but feel free to send me improved instructions if needed (assuming in this example that you tagged my KDE 5 repository with the name “ktown_testing” in the configuration file “/etc/slackpkg/slackpkgplus.conf“):
# slackpkg update
# slackpkg install ktown_testing (to get the newly added packages from my repo)
# slackpkg install-new (to get the new official Slackware packages that were part of my deps previously)
# slackpkg upgrade ktown_testing (upgrade all existing packages to their latest versions)
# slackpkg upgrade-all (upgrade the remaining dependencies that were part of my repo previously)
# slackpkg remove LoginKit (because I removed this package again, which was added to 5_15.09)

And doublecheck that you have not inadvertently blacklisted my packages in “/etc/slackpkg/blacklist“! Check for the existence of a line in that blacklist file that looks like “[0-9]+alien” and remove it if you find it!

Recommended reading material

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

A note on Frameworks

The KDE Frameworks are extensions on top of Qt 5.x and their usability is not limited to the KDE Software Collection. There are other projects which rely (in part) on the KDE Frameworks, and if you are looking for a proper Frameworks repository which is compatible with Slackware package managers such as slackpkg+, then you can use these URL’s to assure yourself of the latest Frameworks packages for Slackware-current (indeed, this is a sub-tree of my KDE 5 “testing” repository):

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). If you are interested in the development of KDE 5 for Slackware, you can peek at my git repository too.

Using a mirror is preferred because you get more bandwidth from a mirror and it’s friendlier to the owners of the master server!

Have fun! Eric

« Older posts Newer posts »

© 2025 Alien Pastures

Theme by Anders NorenUp ↑