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.
Mr. Volkerding will make the final call on what is included, implemented in 15.0. This isn't a democracy; our BDFL has a proven track record of getting it right. This development model works for me. I like where Beta 1 is heading.
Wonderful! BUT, I am afraid that our BDFL not even had been read what we written... yet.
At least a second user here. I am the inventor, so... how they says? Eat your dog food?
However, the PipeWire from today -current can fully replace the PulseAudio server, just like in Fedora.
Only the server, because the libraries and tools are still needed as usual.
I'm a third user since about a week, using pipewire both for video and also as a replacement of pulseaudio.
The move from pulseaudio to pipewire works nicely for audio here, and a few things works even better:
* kde is able to show app window previews in the taskbar under wayland
* "share screen" functionality works on chrome browser under wayland (not on firefox, but from their bugzilla they are still working on it)
* the mic on my bose qc35 headphones is now properly detected and available for use; pulseaudio was not able to use it, as far as i understand it was locked to a profile that didn't support bidirectional comms.
Wayland is necessary in the long run because Xorg is in fact spaghetti code, but it works.
What is so necessary in Wayland? It is like pulseaudio or any other brilliant idea from all we know source. I think Xorg will be fine for very long time just as init. And even if Wayland finally will work many will decide to use old good Xorg. This argument "spaghetti code" - what is not "spaghetti code"? Wayland at some point of its development also can be "spaghetti". People just say this but essentially don't understand what does it mean. It is about code quality? Lack of documentation? Too many developers with poor communication? Complex code?
I'm not sure we understood each other here, so I'll try to explain myself.
Quote:
Originally Posted by enorbet
So do you really think that the only two options are to 1) ignore the person and the topic immediately upon any suspicion, or 2) "throw the hate around" ? Firstly from my POV suspicion is a subjective value judgment based on little evidence. I don't want to be judged that way and I doubt you do, Andersen.
Well, that's your interpretation and the choices you offer have nothing to do with what I said. What I meant is exactly what I wrote, and I think the one who's throwing the hate around should be moderated.
Quote:
Originally Posted by enorbet
If you review even a couple of my responses here I think you will find I was not at all hateful and after the OP amassed sufficient evidence to at least doubt his knowledge and concern for Slackware and made a ghood case for some sort of negative agenda, possibly mere trigger trolling, I ignored OP... not the thread obviously, but the person.
Again, I wasn't talking about you throwing hate, it was about that other guy (the flamethrower).
Another thing: you are mentioning "a good case" that made you decide to ignore the guy (the reason being exactly the one I mentioned), and you dismiss my opinion as "subjective and based on little evidence"? What I said is just that: once it's obvious (not before, and preferably not after), mods should stop it. If you were able to recognize "a good case" and act accordingly, I thing the mods should be capable to do the same.
Quote:
Originally Posted by enorbet
I consider the thread to have value as well as fairly high profile. It demonstrates that most of us here in Slackware Land are not easily triggered, capable of handling dissent and even attacks in an intelligent and gentile manner, and very likely a knowledgeable, informed and helpful community. Isn't that the wisest and best conclusion against trolling?
I agree, but the price is a lot of time spent (cumulatively) by the community members arguing with a troll. That's why I think that moderators should react in such cases.
I can understand the tolerance, before it's obvious (as it's been for some time now with that account) that someone is trolling. When it becomes obvious, mods should protect the members, their time and energy. Simple as that. We can have many topics open and discuss anything in a polite and constructive manner, and that's what we do here most of the time, but certain kinds of behavior should not be tolerated. Of course, that's just my opinion, no one has to agree.
edit:
That being said, I think we should get back on topic
On my laptop using the trackpad is a frustrating experience on X: I get a lot of missed touches and ghost drag events (a single touch is being wrongly interpreted as the start of a drag and drop). Under wayland it works perfectly, i would say like a macbook touchpad.
Even if wayland has a few bugs here and there, that single problem is enough for me to prefer it to X.
With all respect, IF you do not noticed yet, I would like to inform you that we already have for Slackware a PipeWire server setup that can replace successfully the PulseAudio server. And we already use it.
Who cares about pipewire except hobbyists? I am waiting for stable release I don't need kind bleeding edge distribution - if you guys are fancy about this - just do what you want - but don't make Slackware hostage of this Plasma desktop stack. Fans of Plasma may essentially try to be satisfied with what is now. Just don't push it.
On my laptop using the trackpad is a frustrating experience on X: I get a lot of missed touches and ghost drag events (a single touch is being wrongly interpreted as the start of a drag and drop). Under wayland it works perfectly, i would say like a macbook touchpad.
Even if wayland has a few bugs here and there, that single problem is enough for me to prefer it to X.
Are you sure it is something wrong with Xorg? Do you expect auto-magic? Like Windows - turn power on and it works. Did you ever tried to find a fix? So you prefer Wayland because your trackpad works? Despite few bugs here and there? This is your concept of stability?
Who cares about pipewire except hobbyists? I am waiting for stable release I don't need kind bleeding edge distribution - if you guys are fancy about this - just do what you want - but don't make Slackware hostage of this Plasma desktop stack. Fans of Plasma may essentially try to be satisfied with what is now. Just don't push it.
Nobody makes Slackware hostage. Our BDFL can fulfill all our "demands" on ONE HOUR - probably would remain time even for "further tuning" ... IF he wants.
First to talk, please look about what we ask. They are truly minor things, with great positive effects for our purposes.
Last edited by LuckyCyborg; 04-15-2021 at 04:38 PM.
I'm a third user since about a week, using pipewire both for video and also as a replacement of pulseaudio.
The move from pulseaudio to pipewire works nicely for audio here, and a few things works even better:
* kde is able to show app window previews in the taskbar under wayland
* "share screen" functionality works on chrome browser under wayland (not on firefox, but from their bugzilla they are still working on it)
* the mic on my bose qc35 headphones is now properly detected and available for use; pulseaudio was not able to use it, as far as i understand it was locked to a profile that didn't support bidirectional comms.
Yeah, the PipeWire is way better at handling the Bluetooth audio devices. Seen myself that.
BTW, if we talk about screen sharing, there's needed also xdg-desktop-portal.
With it, also works on Wayland/Plasma5 even TeamViewer, non only Firefox. Tested myself.
Being so provocative won't make you look nicer to a community.
Quote:
Originally Posted by igadoter
Did you ever tried to find a fix?
Yes, lokked up online, tried different configurations of xf86-input-synaptics, tried forcing usage of xf86-input-libinput, and so on. It looks like libinput just works better for modern trackpads, but while using it under X it's just limited, eg. horizontal scrolling and multitouch can't be supported.
Quote:
Originally Posted by igadoter
So you prefer Wayland because your trackpad works?
Would you prefer using a broken mouse or a working one?
Quote:
Originally Posted by igadoter
Despite few bugs here and there? This is your concept of stability?
I'm tracking all the bugs I'm encountering and already submitted bug reports and patches. One of my patches already landed in plasma-workspace 5.21.4.
Quote:
Originally Posted by igadoter
This is your concept of stability?
My servers runs Slackware 14.2. That's my concept of stability.
Yeah, the PipeWire is way better at handling the Bluetooth audio devices. Seen myself that.
BTW, if we talk about screen sharing, there's needed also xdg-desktop-portal.
With it, also works on Wayland/Plasma5 even TeamViewer, non only Firefox. Tested myself.
Should we all feel excited? I am sure Windows even better handles bluetooth audio devices. So what? Should we all tomorrow through out Linux and install Windows?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.