Building the KDE4 for Slackware 15.0 in the KTown style - a build based on the PBSLACKS patches
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've been using xfce as my daily driver as of late, but I did like kde4 back in the day. Will kde5 (and 6?) widgets like kdenlive and dolphin run on the updated kde4?
Sure, I am at least partly motivated by spite in looking at kde4 rather than kde6,
at least partly because I dont like the "puniest schtick" team, but everybody doesnt like something.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,099
Rep:
Received this error when running sweeper, see image below.
The other day a similiar error message appeared when trying to start Ksysguard. Rebooting solved the problem.
Edit in: This was with the 6.8.0 kernel, but it worked yesterday and the day before. Rebooting did not solve the problem, nor did reverting to the 6.6.20 kernel.
Last edited by cwizardone; 03-12-2024 at 10:47 AM.
Received this error when running sweeper, see image below.
The other day a similiar error message appeared when trying to start Ksysguard. Rebooting solved the problem.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,099
Rep:
Quote:
Originally Posted by BrunoLafleur
Maybe a lib has changed. I don't see which one. Is ldd /usr/bin/krunner say something unusual ?
Sorry, I don't understand what you mean by "unusual."
From the KDE docs,
Quote:
KRunner lets you start applications, open web pages, search through your desktop data, and more with a simple keyboard shortcut. You can customize KRunner's settings, actions, and plugins to suit your needs and preferences.
libqalculate 5.0.0 which is now in current is not binary compatible with the former but has the same version number. It has been corrected recently upstream in github by adding a new version library which could permit coexistence of old and new version of that lib.
krunner, sweeper and some others don't depend directly on it but some kde libs or applications depends on it. So there can be a problem here.
Else I don't know. I should test to try to reproduce.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,099
Rep:
There has been no breakage from the most recent round of -current Python updates (yet).
BTW, the 6.9-rc1 kernel has been running perfectly on this box for the last several days.
Last edited by cwizardone; 03-31-2024 at 09:40 AM.
From what I understand, a particular update of Slackware-current is used as a reference for kde4town. It is about the update from Sat Dec 5 20:36:27 UTC 2020.
We have the binary packages of this particular update of Slackware-current in the form of the ISO kindly shared by @cwizardone. However, I managed to find a full Slackware-current tree from a friend, containing both sources and packages for this update, obtained as a rsync mirror.
Using the file hosting used by LuckyCyborg too, I uploaded this Slackware-current tree in the form of 2 large tarballs, which those interested can find in the link below:
Due to file hosting size limitations, I used a separate tarball for the huge /testing directory containing the vtown that will be merged in the next update.
For completeness, the sha256 checksums of the 2 tarballs are the following:
From what I understand, a particular update of Slackware-current is used as a reference for kde4town. It is about the update from Sat Dec 5 20:36:27 UTC 2020.
We have the binary packages of this particular update of Slackware-current in the form of the ISO kindly shared by @cwizardone. However, I managed to find a full Slackware-current tree from a friend, containing both sources and packages for this update, obtained as a rsync mirror.
Using the file hosting used by LuckyCyborg too, I uploaded this Slackware-current tree in the form of 2 large tarballs, which those interested can find in the link below:
Due to file hosting size limitations, I used a separate tarball for the huge /testing directory containing the vtown that will be merged in the next update.
For completeness, the sha256 checksums of the 2 tarballs are the following:
Please note that the 2 tarballs are extracted in a directory named slackware64-current , so make sure no files will be overwritten.
Nice find! Many thanks for.
Yep, this particular update is the last one before the KDE4 was replaced by Plasma5 on -current, and it's quite useful (at least) for me, for knowing how was built and on how was behaving the original KDE4 on Slackware.
Last edited by LuckyCyborg; 04-07-2024 at 09:49 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
