Sorry if this may be kind of a duplicate, but once again I can't launch apps with sudo privileges. I use Plasma and I have policy-kde-authentication installed. However, if I try to save edited configuration file or run Partition Manager the usual prompt asking for my user's password won't show up. Consolekit, polkit and the authentication agent services are up and running. Could it be, again, something related to sddm?

  • [deleted]

  • Post #2
Hi

It's really weird and I don't know from where to start. Polkit-KDE Agent at least works as expected when I'm mounting an external USB pendrive, but obviously something is wrong with Kate, PartitionManager and maybe others software.
WHEN I was using Plasma I found this same issue with PartitionManager and a few other services.

EVEN NOW, using JWM barebones I still find the issue with Eddie-UI and a couple of others.

BUT I have also adapted my usage so that almost all apps are launched from keyboard with shortcuts, or running in terminal

THANK YOU Fungal Net for helping me see that automation is totally unnecessary :)
At some historic speech Poetering was asked/criticized that he does what he does because he considers users disabled. His response was "what do you have against disabled people?". This is the mentality that has taken over as dominant in Linux, maybe even flowing out to non-linux unix as well. If you look at some BSD forums the dominant discussion is to get plasma, gnome, wayland working there. The power of market and popularity can set new goals and directions.

LXQT doesn't work on spark-linux, many things don't, but the dev never said they will either, and it is what I've liked about Spark.
https://fleshless.org/pages/spark.html
I suspect that it's kind of a miscommunication among sddm, dbus and consolekit. When I run the partition manager from terminal it throws me a lot of Qdbus errors, and if I remember well, I had a similar problem two years ago, that Jean-Michel was able to fix with a new sddm release. However it's an uphill battle, now that the devs of sddm totally dropped the support for consolekit upstream in favor of elogind.
What I have failed to understand for a long while is why to run plasma you must use the dreaded sddm and not any other dm, like lxdm or lightdm for example. For years here there is constant headache with sddm's idiosyncrasies.
You know, in the old days, the very first Obarun version that I installed was Plasma with lightdm (and beautiful art by Jean Michel too :)). Then the default display manager that plasma pulled in became sddm, I remember that once I tried to replace sddm with ightdm and enable its service but it failed, maybe I should try again following specific instructions, if they are needed.
there are both lightdm and lxdm -66serv files ready to use. I don't use DMs at all, tested a few, lxdm worked fine, why bother with more complex things. A pseudo DM was choosewm from http://packages.debian.org/unstable/x11/choosewm but archers decided to remove it from AUR, it was messing their "image" up. Or maybe they used the excuse it is "abandoned".
UPDATE! Three years later I have installed again lightdm and this time it works! Also, the authentication box is back, so my guess was right, SDDM is the culprit. Now I would like to replace that ugly black background of the greeter with some Obarun splash image, I checked out https://web.obarun.org/obgraphics/ but I only found the logo, not the background.
It is inside the live image and I bet it is inside the installer-themes somewhere, let me see, can I find it before you do :)
No problem, you will be faster for sure, im too slow at this hour:)
Bingo!
pacman -Ql obarun-install-themes | grep png
pacman -Ql obarun-install-themes | grep jpg
How about:
obarun-install-themes /var/lib/obarun/obarun-install/config/jwm/rootfs/usr/share/wallpapers/obarun-wallpapers.jpg
obarun-install-themes /var/lib/obarun/obarun-install/config/openbox/rootfs/usr/share/wallpapers/obarun-wallpapers.jpg

Both 161K
all the .png are too small to be backgrounds :)

feh --bg-fill /var/lib/obarun/obarun-install/config/openbox/rootfs/usr/share/wallpapers/obarun-wallpapers.jpg
will set the background for any WM ...

but you have to temporatily install obarun-install-themes (pacman -Sdd obarun-install-themes)

Also, if you want a nice mouse theme

pacman -Ql obarun-install-themes | grep Jeex
/var/lib/obarun/obarun-install/config/openbox/rootfs/usr/share/icons/Jeex_Mix/

Copy
cp /var/lib/obarun/obarun-install/config/openbox/rootfs/usr/share/icons/Jeex_Mix/ /usr/share/icons/
And pop, you open your theme changer (like lxappearance) and go to choose mouse themes ... and Jeex is there

copy what you like, pacman -Rnsu obarun-install-themes and it is all out again.
Thanks so much! I had already followed the short dirty way, that is directly downloading the wallpaper from Eric's framagit to /usr/share/wallpapers :D .

and now the greeter is watchable :)
Key issue here is whether plasma functions well with its use.
I can't remember how lightdm gets beautified, I know lxdm is very customizable, Last time I used lightdm was in Debian wheezy ,,, to later antiX transition. But I stopped using DM all together and that made me happier :)
Maybe it's no coincidence that Eric has, indeed, an "obarun-lxdm-theme" package in his framagit :) . Both lxdm and lightdm use GTK libraries but I read somewhere that lightdm should have a better compatibility with a Qt based desktop like plasma. So far it seems to work, despite looking quite "out-of-place" after that plasma desktop shows up. However that's the best that I can do in order to keep plasma working with a DM until I decide that it's better to start a desktop the good old way :D .
3 months later

  • [deleted]

  • Post #16
It is now fixed if you use SDDM as Display Manager

Powered by Obarun