LXQt 2.0 for Slackware Current, incl distributions based on Slackware current
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.
LXQt 2.0.0 updates to the same toolkit as KDE Plasma 6.
Meaning, no pain in the arse, I recommend to remove KDE.
Hopefully, Pat will upgrade to KDE6 shortly....makes everything easier.
I saw that you recommend the complete uninstallation of Plasma5.
I think this is understandable with the mega-builds that LuckyCyborg makes either for KDE4 or Plasma6, but is this really the case with LxQt2?
I don't know about others, but for me it seems ridiculous to have to choose between the stock Plasma5 and LxQt2.
To be honest, I always looked at LxQt as a light version of Qt Destkop, not as a competitor of Plasma5. Something like XFCE4 is for GNOME4, which both tag along.
Last edited by ZhaoLin1457; 04-22-2024 at 09:39 AM.
To be honest, I always looked at LxQt as a light version of Qt Destkop, not as a competitor of Plasma5. Something like XFCE4 is for GNOME4, which both tag along.
The LxQt 1.x is designed to tag along with Plasma5, BUT like @lancsuk already said, the LxQt2 is designed to tag along with Plasma6.
Honestly, I like the OP approach on building LxQt2 , as it does not really conflict with the Plasma6.
But if OP really want, he can make a build capable to tag along with the stock Plasma5, by renaming these several KDE Frameworks 6.x packages which are used.
Something like Mr. Hameleers did for his KTown of Plasma6 (and which I borrowed too) but in reverse - the KTown renames the KDE Frameworks 5.x packages which are all shipped by it.
Last edited by LuckyCyborg; 04-22-2024 at 10:09 AM.
i confirme, lxqt2 work perfectly with all Eric ktown based package, on the other hand here everything is updated ( dependencies, plasma-extra, qt6, etc.......).
The LxQt 1.x is designed to tag along with Plasma5, BUT like @lancsuk already said, the LxQt2 is designed to tag along with Plasma6.
Honestly, I like the OP approach on building LxQt2 , as it does not really conflict with the Plasma6.
But if OP really want, he can make a build capable to tag along with the stock Plasma5, by renaming these several KDE Frameworks 6.x packages which are used.
Something like Mr. Hameleers did for his KTown of Plasma6 (and which I borrowed too) but in reverse - the KTown renames the KDE Frameworks 5.x packages which are all shipped by it.
Good News, I was able to install LXQT2 and KDE5 side by side. But, as expected some issues.
Well, with the packages you have in your repo, honestly I do not think that you are able to install LxQt2 along with Plasma5, because it replaces a series of stock packages to Plasma6, from both KDE Frameworks and KDE Plasma. So, certainly you have broken the Plasma5 while installing your packages.
If you want to install your dependencies (part of Plasma6) without replacing the stock packages, you will need to rename the packages, something like for solid to generate a package named: solid-6-6.1.0-x86_64-1_snuk.txz
So, according with my suggestion, the package name will be solid-6, which is not equal with the name of the stock solid package from KDE Frameworks 5.x.
Something like this do also Mr. Hameleers for his KTown for Plasma6, with which I thinker in the last time. Only that he did vice-versa, naming the legacy KDE Frameworks 5.x packages like solid-5
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.