Building the Plasma6 for Slackware-current in the KTown style - a build based on the AlienBOB's KTown
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.
kdevelop, compile with qt5, only if you uninstall the latest package 'libksysguard' before, because, it is compiled with qt6, another solution, make one package 'libksysguard-5' for qt5 the latest version for qt5, is in slack-current.
After the latest update (Wed May 22 18:57:13 UTC 2024) I no longer can open a Plasma session on Wayland. Opening using "Plasma X11" is still OK.
EDIT: even on a Plasma X11 session, the desktop is unstable. KWin crashes frequently to the point that the desktop is not usable. I have to resort to XFce.
Last edited by sombragris; 05-22-2024 at 08:11 PM.
After the latest update (Wed May 22 18:57:13 UTC 2024) I no longer can open a Plasma session on Wayland. Opening using "Plasma X11" is still OK.
EDIT: even on a Plasma X11 session, the desktop is unstable. KWin crashes frequently to the point that the desktop is not usable. I have to resort to XFce.
This is due qt6-6.7.1_20240516_6977d02f upgrade. Three choices here:
Downgrade to qt6-6.6.3_20240319_c2516323
Recompile your entire plasma6 stack against new qt6-6.7.1
Wait for the plasma6 packages provider to recompile the entire stack against new qt6-6.7.1
You can find cumulative Slackware packages here (thanks to AlienBOB):
slackpkg_build is a script i use when I want to build in current a single package or full DE (kde, xfce) or a project that build multiple files from one main SlackBuild (X11 etc..)
If you want try it.
First clean your /tmp from any *.t?z
Then to build all kde command
Code:
slackpkg_build kde
it will download it in /tmp/slackpkg_buil/kde
then you can cd there and run kde.SlackBuild
when it finish
Code:
upgradepkg --reinstall /tmp/*.t?z
PS. Note that it will some time to build all kde i never tried this...
I mostly use it to rebuild a package from source...for special reasons...
It is about Plasma6 which is built by LuckyCyborg. These packages and their sources are only available as large tarballs.
I don't think this slackpkg_build can be useful when it comes to a KTown-style source tree, which is available in a big tarball uploaded to Mega.
I warmly recommend the use of these three -compat packages by those who use this build of Plasma6, because they were very useful even when Plasma5 was in KTown.
Another suggestion I have for those who use packages built by LuckyCyborg, is that (just like when Plasma5 was in KTown) to carefully inspect the ChangeLog and if you find packages that you believe can affect Plasma6, to wait for updates to be available from his side. For example, a Qt-6.6.3 update to Qt-6.7.1 is a recipe for disaster.
And here an important note must be made: he does not have at his disposal computers as powerful as many in this forum. And above all, he uses a 3G mobile Internet connection, which is particularly slow in the case of uploads.
This means that you will have to be patient to have updates available, especially when it comes to a full rebuild.
Unfortunately, this is the truth. LuckyCyborg does not have the same high-performance logistics as many of you.
Last edited by ZhaoLin1457; 05-23-2024 at 06:13 AM.
You may want to also downgrade poppler, otherway okular won't be able to open PDFs, even with the poppler-compat package installed.
Indeed. Okular outputs this when trying to load a PDF:
Code:
kf.coreaddons: "Could not load plugin from /usr/lib64/qt6/plugins/okular_generators/okularGenerator_poppler.so: Could not load library from /usr/lib64/qt6/plugins/okular_generators/okularGenerator_poppler.so: (/usr/lib64/libQt6Core.so.6: version `Qt_6.7' not found (required by /usr/lib64/libpoppler-qt6.so.3))"
org.kde.okular.core: Failed to load plugin "/usr/lib64/qt6/plugins/okular_generators/okularGenerator_poppler.so": "Could not load plugin from /usr/lib64/qt6/plugins/okular_generators/okularGenerator_poppler.so: Não foi possível carregar a biblioteca /usr/lib64/qt6/plugins/okular_generators/okularGenerator_poppler.so: (/usr/lib64/libQt6Core.so.6: version `Qt_6.7' not found (required by /usr/lib64/libpoppler-qt6.so.3))"
The upgraded poppler-24.05.0 is also compiled against qt6-6.7.1, so it complains about the version mismatch. That's why poppler-compat doesn't help on this case as it's also built with new qt6 in place.
Downgrading to poppler-24.04.0 workaround the issue for now.
As a side note, blacklist (slackpkg) or greylist (slackpkg+) these sensible packages also helps here.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.