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.
New Qt Releases Might Now Be Restricted To Paying Customers For 12 Months
Written by Michael Larabel in Qt on 8 April 2020 at 07:53 AM EDT
.........But the most surprising new information made public today by KDE's Olaf Schmidt-Wischhöfer is that The Qt Company is considering making new releases paid-customer-only for the first twelve months.
Olaf Schmidt-Wischhöfer wrote, "But last week, the company suddenly informed both the KDE e.V. board and the KDE Free QT Foundation that the economic outlook caused by the Corona virus puts more pressure on them to increase short-term revenue. As a result, they are thinking about restricting ALL Qt releases to paid license holders for the first 12 months. They are aware that this would mean the end of contributions via Open Governance in practice."............
.....KDE and the open-source Qt folks have been in discussions with The Qt Company especially with the restrictions announced back in January by The Qt Company that LTS point releases might only be available to commercial customers, Qt Accounts being needed for binary package downloads, etc......
The information quoted in post #46 is new as of this morning.
Last edited by cwizardone; 04-08-2020 at 02:01 PM.
No, and I do not think that Plasma5 packages shipped by Mr. Hameleers are supposed to work on Wayland.
I believe that those Plasma5 builds are X11 only.
Wayland is now part of Slackware, and mesa, qt5 and xorg-server are built against it. Also, my Plasma5 packages are built against those.
But a Plasma5 Wayland session will not work in Slackware, it looks like it may need (e)logind which is not part of Slackware. ConsoleKit2 is no longer working as a drop-in replacement for logind like it did last year. I do not know why.
AlienBob.. yes this is what I found when using Sway with Slackware and ConsoleKit2
It simply didnt work.
Building and installing elogind worked fine for that purpose though I understand that's not a part of Slackware either.
Folks, i have a strange problem with cyrillic symbols in some apps like emacs in plasma session (xorg). It recognizes cyrillic, however when it comes to add some path, that contains cyrillic, an app doesn't see this file. E.g. my ~/Downloads directory contains about a 100 files with cyrillic names. When i open this directory in emacs, i see these files, but when i try to open any of them with built in commandline, emacs sees no files with cyrillic. The problem comes with installation of ktown. I guess it's related to locale settings, but i can't open regional settings in system settings - i always get crush of settings.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.