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.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 935
Rep:
Quote:
Originally Posted by enorbet
Hello Paulo2
I, too, have seen some changes in encoding for graphics formats. Some .jpg and .gif formats seem to have new encoding such as WebP that are incompatible with some apps, even GIMP, at least as they are now. I suppose they are due since those formats have been around a long time and could likely benefit by being updated. I haven't seen .jfif yet though.
It seems that it is a problem with my user and older KDE4 configurations. I created a new user and Gwenview can save as jpg.
I deleted all Gewnview files and folders but it didn't fix.
Maybe the best to do with the new KDE5 (and maybe Xfce 4.16) is a new install.
I believe that the latest Plasma5 will not work well with ConsoleKit2.
What is the basis for such a religious belief? Is there any?
This is how rumors are started and eventually translate as fact as people reproduce the myths. If the same upstream pkgs that constitute plasma worked with ck2 last year, and still do with all the upgrades today, and I am not talking about slackware but arch based Obarun (cutting edge) and elogind has never been available through Obarun repositories, then it is neither a Plasma problem or a ck2 problem. It works with sddm too.
If there are reasons to switch from ck2 to a chunk of systemd (elogind) there should be rational explanations, not myths and rumors.
I personally don't ever use elogind or ck2, and trying my hardest not to even have to use dbus. I may have it installed as a dependency but keep it dead asleep and inaccessible. The point is not to defend ck2 but to fight off the dependency to systemd functionality "everywhere".
How does plasma/sddm work without elogind in Obarun, it is all opensource and it takes a few minutes to install an obarun plasma (if you have a fast connection, or however long it takes to download 3-4GB through net-install plus a few minutes. The configuration is all open to be audited, the source is all open and public. So it can be done.
What is the basis for such a religious belief? Is there any?
This is how rumors are started and eventually translate as fact as people reproduce the myths. If the same upstream pkgs that constitute plasma worked with ck2 last year, and still do with all the upgrades today, and I am not talking about slackware but arch based Obarun (cutting edge) and elogind has never been available through Obarun repositories, then it is neither a Plasma problem or a ck2 problem. It works with sddm too.
If there are reasons to switch from ck2 to a chunk of systemd (elogind) there should be rational explanations, not myths and rumors.
I personally don't ever use elogind or ck2, and trying my hardest not to even have to use dbus. I may have it installed as a dependency but keep it dead asleep and inaccessible. The point is not to defend ck2 but to fight off the dependency to systemd functionality "everywhere".
How does plasma/sddm work without elogind in Obarun, it is all opensource and it takes a few minutes to install an obarun plasma (if you have a fast connection, or however long it takes to download 3-4GB through net-install plus a few minutes. The configuration is all open to be audited, the source is all open and public. So it can be done.
It is NOT a religious belief, but a practical observation.
As disappointing looks for you, the Wayland/Plasma5 needs the elogind to work - or rather an function login1 service, such as systemd-logind.
And not only it - there are many other software who need a proper login1 service.
And BTW, the ConsoleKit2 is now dead and buried.
You may cry as you like over its beloved bones, but that does not changes the fact that it was an ideological driven project needed by no one, which invented nothing new, excluding its naming of DBUS commands - which was probably a very shoot on its own legs.
And you are kind to spread your anti-systemd venom somewhere else? We, we do not use systemd.
Not because we hate it and we are against it, but just because we literally do not use it and we do not care about it.
So, please do not confuse us with your bunch of rebels without a cause.
Last edited by LuckyCyborg; 12-19-2020 at 01:47 PM.
It is NOT a religious belief, but a practical observation.
As disappointing looks for you, the Wayland/Plasma5 needs the elogind to work. And not only it - there are many other software who need a proper login1 service.
It has to be religious, you are saying it doesn't work when I just provided adequate reference that it does. So the difference MUST be that packaging is just lazy and relying on the easy solution of adopting systemd.
All you have to do is try, then explain why it IS working on Obarun but can't work on any other linux. But without reference contradicting mine you can't dismiss it like saying the earth is flat and going west from Portugal you will fall of the earth disk.
Go cleanly and say I MADE A CHOICE, don't propagate myths about something is not working when in fact it does.
It has to be religious, you are saying it doesn't work when I just provided adequate reference that it does. So the difference MUST be that packaging is just lazy and relying on the easy solution of adopting systemd.
All you have to do is try, then explain why it IS working on Obarun but can't work on any other linux. But without reference contradicting mine you can't dismiss it like saying the earth is flat and going west from Portugal you will fall of the earth disk.
Go cleanly and say I MADE A CHOICE, don't propagate myths about something is not working when in fact it does.
So, the Plasma5 with Wayland sessions works without elogind under Obarun? Hard to believe...
Still, that does changes the fact the ConsoleKit2 is dead software, abandoned since more than 3 years by its authors.
Anyways, The Choice wasn't made by myself, as I am not a Slackware developer.
Me, I am just an happy user that ConsoleKit2 is gone from Slackware...
You may cry as you like over its beloved bones, but that does not changes the fact that it was an ideological driven project needed by no one
Nothing wrong with being ideologically driven, in fact ideology is largely responsible for giving us the free software world (which you, and I, and many others enjoy). Actually it wasn't so long ago that free/libre software was called "cancerous" etc. If people are motivated to produce free software, for whatever reason, then I think they ought to be encouraged, and definitely not put down as "needed by no one" or not tending to some sacred market/need. If people are producing free software then they're part of the community, and that's good.
Quote:
Originally Posted by LuckyCyborg
And you are kind to spread your anti-systemd venom somewhere else? We, we do not use systemd.
Not because we hate it and we are against it, but just because we literally do not use it and we do not care about it.
So, please do not confuse us with your bunch of rebels without a cause.
And by the way, can we please not turn this thread into a discussion about Plasma on Obarun, elogind vs ConsoleKit2? It's great that people are working on projects, but this thread is about Plasma on Slackware.
And by the way, can we please not turn this thread into a discussion about Plasma on Obarun, elogind vs ConsoleKit2? It's great that people are working on projects, but this thread is about Plasma on Slackware.
Indeed. I'm very happy with Plasma and running it on several units. I think we're a lot closer to a beta release.
I wonder what Obarun do with this particular service...
This was a community member who made a service file for it, but elogind itself doesn't exist in Obarun repositories, or Arch (since systemd exists there). But you can build elogind from source from Arch's community repository AUR.
The point is not to contrast any distro with any distro, but wild statements such as KDE/plasma will not work without elogind is just an absolute lie and misinformation. This is my contribution here, to prevent lies, myths, and rumors from being spread so someone's choice is defended on the wrong basis.
Void switched to elogind this past year, and Adelie did too, and I believe Alpine has for some time, and many many others. But let's not fool ourselves and say "they had to" because xxx wouldn't work, when it is not true!
You talk about religious but then refuse to use pieces of software because of what they're tied to?
Quote:
Originally Posted by FungalNet
The point is not to defend ck2 but to fight off the dependency to systemd functionality "everywhere".
Slackware supports both X11 and wayland plasma sessions. I don't know if plasma5 needs a login1 implementation for a wayland session, but if it does, then that's a valid reason.
There is also other software that requires a login1 implementation and if that was implemented in a plasma5 session running CK2, then it broke logging out. Granted, that software isn't a part of Slackware, but more and more are going to start requiring the login1 implementation. The simple answer is to add elogind.
As I said in the other thread, Pat and team have done a great job getting elogind, eudev, PAM, pulseaudio, and possibly other software integrated into Slackware mostly unnoticed by people who don't read the changelog. If you didn't read the changelog and didn't have special cases, then it's unlikely many would notice that these changes were made.
Slackware supports both X11 and wayland plasma sessions. I don't know if plasma5 needs a login1 implementation for a wayland session, but if it does, then that's a valid reason.
Yes, the Plasma5 really needs a functional login1 service for its Wayland sessions. And from what I read, any Wayland desktop needs it.
Without a function login1 service, the Wayland/Plasma5 will not even start, as I tested this myself long time ago, while trying to make the Wayland work under Slackware.
And as you know, there are just two implementations of login1 service in the wild: systemd-logind and elogind.
Last edited by LuckyCyborg; 12-19-2020 at 02:58 PM.
You talk about religious but then refuse to use pieces of software because of what they're tied to?
Absolutely. If I am looking for a calculator gui and try to install it and I see it is tied to a ton of Qt crap, I refuse to use it. There are many others that don't have this one ton of crap reliance and still run on my minimalist WM.
Where I used the term religious is where someone says Plasma Will NOT run without elogind. But it does! And that is the end of the story.
Saying "I choose to use elogind to make plasma work easier" is much more accurate and understandable. LXQT will not work without Qt. That is true and acceptable. To say lxqt will not run without systemd is an absolute lie! It is only religious people that will believe a known lie and a myth as "truth".
Last edited by michaelk; 12-31-2020 at 07:27 AM.
Reason: inappropriate language
I don't understand, FungalNet. Why are you even here in this thread arguing over trivia? You apparently don't use Slackware or Plasma. Why should anyone care about your "police badge"? If it is as you say, and I have no reason to doubt it yet, that Plasma 5 will run with ConsoleKit, so what? Since your sig shows your location as "nonsytemd-land" I imagine this is something of a Crusade for you, but here, in this thread, it is irrelevant. I see no evidence that Slackware is slipping into systemd by degrees. We are not frogs duped by slow change.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.