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 haven't been keeping up. Is Wayland even robust yet? I know it's been around a long time but I've read some stuff is just easier with Xorg and frustrating to Wayland. What's the current consensus?
From what I've read, Gnome has better support for Wayland than KDE does, but that's expected because it's developed by the same people (I think?). Wayland itself is a relatively simple display server, and as far my own limited knowledge goes, it is fairly complete by now. Most of the work is on the implementation side, meaning the desktop environments themselves have to implement the protocol.
From what I've read, Gnome has better support for Wayland than KDE does, but that's expected because it's developed by the same people (I think?). Wayland itself is a relatively simple display server, and as far my own limited knowledge goes, it is fairly complete by now. Most of the work is on the implementation side, meaning the desktop environments themselves have to implement the protocol.
One of the reasons I asked is because I watched a video of a symposium in Australia by a Wayland dev who said it was going to take some time because "it's REALLY hard" which is how Xorg became messy in the first place. It is something of a crazy quilt that took decades to evolve, something like that Johnny Cash song about a parts Cadillac.
This is why I used quotes around "many odd flaws", because I know of none.
Ah, just so you know:
Quote:
These "many odd flaws" are largely the distributor's doing.
makes it sound like an authoritative statement (as in, you know about the flaws and you know that the distributors are to blame). If it was something like "Those 'many odd flaws' must be largely the distributor's doing", then the intended meaning would be conveyed
This is why I used quotes around "many odd flaws", because I know of none.
Over the last several months I have extensively tested Debian, Arch, and openSUSE and I have not experienced many flaws in KDE-plasma.
I am looking forward to running KDE-plasma on Slackware when it arrives.
makes it sound like an authoritative statement (as in, you know about the flaws and you know that the distributors are to blame). If it was something like "Those 'many odd flaws' must be largely the distributor's doing", then the intended meaning would be conveyed
(Slightly OT.) These things happen when you don't use your native language. Reminds me of the time back at the university when I wanted to politely ask a professor if he intended to be busy for a long time with the copy machine, so I translated an expression from my native german into french, and the result was something in the line of "When will you bugger off?"
So, what I initially meant was:
1. I never encountered any flaws in Plasma 5.
2. If someone did, there's a fat chance it's the distributor's doing.
(Slightly OT.) These things happen when you don't use your native language.
I guessed that this was the case, I also have difficulty sometimes in Spanish, differences of meaning in language can be very subtle!
Quote:
Reminds me of the time back at the university when I wanted to politely ask a professor if he intended to be busy for a long time with the copy machine, so I translated an expression from my native german into french, and the result was something in the line of "When will you bugger off?"
Haha yes, I've had such mishaps. Back in the class days I tried to describe a film about a guy free climbing a mountain (without a rope), and ended up saying that I watched a movie about a guy who scales mountains in the nude
Haha yes, I've had such mishaps. Back in the class days I tried to describe a film about a guy free climbing a mountain (without a rope), and ended up saying that I watched a movie about a guy who scales mountains in the nude
Going off topic here, but one of my favourites is YouTube's automated captioning of "Unix" as "eunuchs".
Regarding about KDE4 and Plasma5 bugs induced by packaging made by distributions, with all respect to the venerable people here, I have an example for Slackware: the Darth's Bug.
This bug is specific for Slackware's KDE4 and propagate up to latest build of Plasma5 made by Mr. Hameleers, and it is about strange error messages when setting the clock from the applet of KDE4/Plasma5.
If I remember right, Darth Vader explained long time ago that it is produced apparently because of lack of PAM from Slackware and that only God knows how many other flaws are introduced in KDE4 or Plasma5 by this lack of PAM.
Please note that I am truly certain that this clock setting issue does not appear on Kubuntu or OpenSUSE, from my own experiences. Honestly, I do not tested KDE4 or Plasma5 also in Fedora, but I expect the same fine working.
Last edited by ZhaoLin1457; 11-28-2019 at 04:03 PM.
There's also the possibility that other things are being worked in the background in addition to Plasma5 and Pat wants to make sure they all work when they are pushed out.
He could be working on things like Pam/Kerberos or Wayland and wants to make sure that when things are pushed out, that everything works as expected. Since those can cause fundamental changes in many different aspects of the system, it isn't something as simple as "let's see if plasma5 works"
The binary NVidia drivers don't work with Wayland.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.