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.
Maybe you can ask me to explain then. Are you asking?
I was, but after this nasty response I won't again..
Quote:
Originally Posted by FungalNet
What I use is totally irrelevant. I've used and have an installation of Slackel, does that count? But I could be using winXP, does this change the fact that the latest upstream stable version of KDE/plasma works without systemd and elogind?
It's sometimes irrelevant, and in this case it simply doesn't matter. Slackware no longer supports Plasma on CK2 for whatever reason. That's just reality. Next.
Quote:
Originally Posted by FungalNet
One of Slackware's fanboys is making a false statement and I am correcting the record. This is LinuxQuestions it is not Slackware's private club! And poor slackware is nowhere blamed here for anything, it is one fool believing in things that are not right. That's all. He, or anyone else can just admit on the error of the statement and it will all be over.
So your reaction to LuckyCyborg is to take it out on me who is trying to mediate? Look.. I believe you that Plasma CAN run with ConsoleKit2 but it currently CAN'T on Slackware Current so it is eminently relevant that we're talking "apples" and you are talking "oranges".
Quote:
Originally Posted by FungalNet
INSTEAD, to defend the LIAR you are trying to say I am attacking Slackware for its choices and its justifications. I am not, you are simply using Slackware as a shield to cover up on a lie!
Check the record here. I never said you are attacking Slackware. I did say you are in effect beating on a dead horse since that boat has already sailed. Your comments in this thread have been insufficient, unnecessary, and irrelevant simply because you have a tunnel vision Crusade in your head. This thread is not about Obaron or systemd, and is certainly not about you and your sensibilities and triggers.
Quote:
Originally Posted by FungalNet
Now, do you understand? Or is this too complicated for you and I need to break it down in simpler statements?
There, feel better now now that you've assumed you know everyone and everything and struck a blow against the systemd dragon? Frankly and despite it's initial massive coup d'etat, I don't think systemd is all that important, just one more obstacle to walk around, just like restrictive Unix licensing was that motivated a few to come up with Linux and the whole FOSS movement. It's a balloon... push in on one side, it bulges out in opposition.
"The Wayland implementation in KDE Plasma5 depends on a session API called “login1” which was originally defined and implemented by systemd and is for the most part (read: the relevant part) implemented in ConsoleKit2 as well. In the current state of software development, unfortunately ConsoleKit2 is blocking a successful Wayland implementation in Slackware; fixing this demands another core change in Slackware (next to PAM)." https://alien.slackbook.org/blog/rep...d-first-steps/
Code:
bash-5.1# slackpkg search wayland
Looking for wayland in package list. Please wait... DONE
The list below shows all packages with name matching "wayland".
[ Status ] [ Repository ] [ Package ]
installed multilib wayland-compat32-1.18.0-x86_64-1compat32
installed slackware64 kwayland-5.77.0-x86_64-1
installed slackware64 kwayland-integration-5.20.4-x86_64-1
installed slackware64 kwayland-server-5.20.4-x86_64-1
installed slackware64 plasma-wayland-protocols-1.1.1-x86_64-1
installed slackware64 wayland-1.18.0-x86_64-1
installed slackware64 wayland-protocols-1.20-noarch-1
installed slackware64 xisxwayland-1-x86_64-1
installed slackware64 xorg-server-xwayland-1.20.10-x86_64-2
This thread is not about Obaron or systemd, and is certainly not about you and your sensibilities and triggers.
Exactly. Thank you, enorbet. This thread is about the KDE-plasma introduction into Slackware Linux.
KDE5 is now my default desktop on Slackware64-current. I think we have a winning combination of KDE5, XFCE 4.14, and now the 5.10.1 kernel.
I expect that Mr. Volkerding and the Slackware Team will continue to make adjustments to KDE5 and other things in the next while. We're closer to a beta release.
Ran into a couple of issues with Plasma on Wayland today:
* using Ctrl-C to copy would occasionally and seemingly randomly copy just an empty string instead of what I selected.
* submenus under the main menu of Google Chrome (e.g. "Bookmarks" or "More Tools") were completely unusable. Instead of highlighting the menu item I hover over, it would highlight the one in the main menu of the same order.
The first I worked around by disabling "Prevent empty clipboard" in the Clipboard widget. However I was not able to find a workaround for the second one, which totally breaks my workflow, so I had to go back to plain old X.
Hi , when i go out to restart or poweroff , i ear a system notification sound , i go inspectioning settings --> notifications , but im not see a option called sound on logout or similar to disable this.
Any idea ?
I want only put OFF this sound when go to out , im not waant put "all system sounds off" , or down volume in the system.
I ask if exist a configure option to exactly turns off that sound.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 935
Rep:
Quote:
Originally Posted by USUARIONUEVO
Hi , when i go out to restart or poweroff , i ear a system notification sound , i go inspectioning settings --> notifications , but im not see a option called sound on logout or similar to disable this.
Any idea ?
I want only put OFF this sound when go to out , im not waant put "all system sounds off" , or down volume in the system.
I ask if exist a configure option to exactly turns off that sound.
Thanks!
Is it a sound from the speakers or from the pc-speaker (buzzer)?
After the kernel upgrade yesterday I'm getting a crackling sound from the pc-speaker when I first log-in to KDE-plasma or XFCE 4.16 on first boot-up. The sound goes away after a few seconds. This is a new occurrence.
After the kernel upgrade yesterday I'm getting a crackling sound from the pc-speaker when I first log-in to KDE-plasma or XFCE 4.16 on first boot-up. The sound goes away after a few seconds. This is a new occurrence.
I'm assuming it is kernel related. The same thing happened to me, but I am not using KDE or Xfce.
Last edited by individual; 12-27-2020 at 08:48 PM.
Reason: Assumption not fact
Whew! I just noticed this myself after doing the upgrades to -current. Thought it might be the terrifying sound of an impending hd failure (yes, I still have a few spinners as storage drives). It happens only on logon for me, for both Plasma and Xfce DE's. Haven't tried others.
Hi , when i go out to restart or poweroff , i ear a system notification sound , i go inspectioning settings --> notifications , but im not see a option called sound on logout or similar to disable this.
Any idea ?
System Settings > Notifications > Applications: Configure > System Services - Plasma Workspace > Configure: Events > look for Login and Logout.
System Settings > Notifications > Applications: Configure > System Services - Plasma Workspace > Configure: Events > look for Login and Logout.
Hi , not exactly this , but under notifications i found event "beep" , with sound asigned , then when go off, he make the noise , im not sure if this option are the default or i change , but now is fixed here. THANKS!
Hi , not exactly this , but under notifications i found event "beep" , with sound asigned , then when go off, he make the noise , im not sure if this option are the default or i change , but now is fixed here. THANKS!
Ah, okay. That "beep" is enabled here.
I don't recall hearing that on reboot or shutdown. That same sound is also tied to KAlarm.
Check the record here. I never said you are attacking Slackware. I did say you are in effect beating on a dead horse since that boat has already sailed. Your comments in this thread have been insufficient, unnecessary, and irrelevant simply because you have a tunnel vision Crusade in your head.
You explain to me why, till Dec 7th 2020, I could use xinit and a wm (in my case openbox) and I could live and survive without a logindaemon, but now to even start x I need it. X will not start without it. pcmanfm will not run (I've never seen this anywhere) without it.
It is one thing making elogind or even systemd available, and it is another thing shoehorning it everywhere you possibly can, and you can if you wanted to. You can make a wrapper around vi or nano and before they start on console ask whether you want to use them as user or root, and have elogind and polkit and dbus employed to start nano or vi, otherwise they will not start at all.
Slackware went from best to shit all in one day. It is worse than fedora in this respect.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
That "beep" is enabled here.
That same sound is also tied to KAlarm.
