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-current with "True Multilib" and KDE4Town.
Posts: 9,131
Rep:
I've had the same problem with kde4 and Xfce. When I instruct either, via the gui interface, to shut down, it logs out to a command prompt. From there it is necessary to issue the "su -c halt" command and the root password to shutdown the system.
Also, after the last two "fresh" installations the user can no longer "control" access to the network/Internet via NetworkManager and it becomes necessary to edit /etc/dbus-1/systemd/org.freedesktop.NetworkManager.conf to re-gain control.
Last edited by cwizardone; 08-03-2020 at 10:15 AM.
I've had the same problem with kde4 and Xfce. When I instruct either, via the gui interface, to shut down, it logs out to a command prompt. From there it is necessary to issue the "su -c halt" command and the root password to shutdown the system.
Also, after the last two "fresh" installations the user can no longer "control" access to the network/Internet via NetworkManager and it becomes necessary to edit /etc/dbus-1/systemd/org.freedesktop.NetworkManager.conf to re-gain control.
Well, an elogind driven system permits the users members of group "power" to just use:
Code:
loginctl shutdown
Which I consider a great advantage.
Probably there are many who will want to empower his/her/its users to properly shutdown, reboot, suspend or even hibernate from console, without disclosing the root password to them. For example, think about the computers from a school.
Just reverted to mozjs60-60.9.0esr, reloaded Plasma 5 and now the power / session menu is populated again
In fact, was already published (but later) by Mr. Hameleers an updated package: polkit-0.117-x86_64-1alien.txz which works fine with the -current's mozjs68-68.11.0esr-x86_64-1.txz .
So, this issue was already fixed.
I for one, I always check for updates the next days after a new Plasma5 build deployment because some fine tuning always happens.
Last edited by LuckyCyborg; 08-03-2020 at 10:49 AM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,131
Rep:
Quote:
Originally Posted by cwizardone
I've had the same problem with kde4 and Xfce. When I instruct either, via the gui interface, to shut down, it logs out to a command prompt. From there it is necessary to issue the "su -c halt" command and the root password to shutdown the system.......
Installing Mr. Workman's recent dbus and polkit packages solved that problem with kde4. Didn't need to revert to mozjs60-60.9. http://rlworkman.net/pkgs/current/x86_64/
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,011
Original Poster
Rep:
Quote:
Originally Posted by cwizardone
Installing Mr. Workman's recent dbus and polkit packages solved that problem with kde4. Didn't need to revert to mozjs60-60.9. http://rlworkman.net/pkgs/current/x86_64/
Thank you everybody for helping.
After installing dbus and polkit from Mr. Workman's repository, as advised by cwizardone, my problem is fixed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.