You are not logged in.
Pages: 1
Before install Devuan I was running Debian 10 in which KDE was working perfectly. After install Devuan, I can't shutdown or reboot the machine from the interface. When I click to turn off the computer, xorg are killed and then restart, with KDE session manager opening.
I had try what was suggested on web.
1) Purge and reinstall upower.
2) Purge and reinstall all xorg and KDE.
3) Purge and upgrade (ascii-updates) all xorg and KDE.
4) Upgrade the kernel.
5) Delete some log files of KDE.
6) Put user on adm group and give him permissions on /sbin/shutdown and /sbin/reboot.
I only can shutdown the system through root or the shutdown icon of session manager.
Last edited by ReallyNigga (2019-11-19 14:52:52)
Offline
Post the output of the following command. That will show which policykit related packages are installed. Something you need might be missing.
dpkg -l | egrep "consolekit|elogind|policykit|polkit|libpam"
Offline
Post the output of the following command. That will show which policykit related packages are installed. Something you need might be missing.
dpkg -l | egrep "consolekit|elogind|policykit|polkit|libpam"
root@devuan:/home/notebook# dpkg -l | egrep "consolekit|elogind|policykit|polkit|libpam"
ii consolekit 0.4.6-6 amd64 framework for defining and tracking users, sessions and seats
ii elogind 234.4-2 amd64 user, seat and session management daemon
ii libelogind0:amd64 234.4-2 amd64 user, seat and session management library
ii libpam-elogind:amd64 234.4-2 amd64 elogind PAM module
ii libpam-modules:amd64 1.1.8-3.6 amd64 Pluggable Authentication Modules for PAM
ii libpam-modules-bin 1.1.8-3.6 amd64 Pluggable Authentication Modules for PAM - helper binaries
ii libpam-runtime 1.1.8-3.6 all Runtime support for the PAM library
ii libpam0g:amd64 1.1.8-3.6 amd64 Pluggable Authentication Modules library
ii libpolkit-agent-1-0:amd64 0.105-25+devuan0~bpo2+1 amd64 PolicyKit Authentication Agent API
ii libpolkit-backend-1-0 0.105-25+devuan0~bpo2+1 all PolicyKit Authorization API
ii libpolkit-backend-consolekit-1-0:amd64 0.105-25+devuan0~bpo2+1 amd64 PolicyKit backend API
ii libpolkit-gobject-1-0 0.105-25+devuan0~bpo2+1 all PolicyKit Authorization API
ii libpolkit-gobject-consolekit-1-0:amd64 0.105-25+devuan0~bpo2+1 amd64 PolicyKit Authorization API
ii libpolkit-qt-1-1:amd64 0.112.0-5 amd64 PolicyKit-qt-1 library
ii libpolkit-qt5-1-1:amd64 0.112.0-5 amd64 PolicyKit-qt5-1 library
ii policykit-1 0.105-25+devuan0~bpo2+1 amd64 framework for managing administrative policies and privileges
ii polkit-kde-1 4:5.8.4-1 all transitional dummy package
ii polkit-kde-agent-1 4:5.8.4-1 amd64 KDE dialogs for PolicyKit
Offline
I think you need to remove consolekit. I'm not sure if you'll have problems doing that. You'll need to replace
libpolkit-backend-consolekit-1-0 libpolkit-gobject-consolekit-1-0
with
libpolkit-backend-elogind-1-0 libpolkit-gobject-elogind-1-0
which may or may not happen automatically.
Yell if you need help with it. (And post some terminal output if there are conflicts that you or aptitude can't resolve.)
Offline
I think you need to remove consolekit. I'm not sure if you'll have problems doing that. You'll need to replace
libpolkit-backend-consolekit-1-0 libpolkit-gobject-consolekit-1-0
with
libpolkit-backend-elogind-1-0 libpolkit-gobject-elogind-1-0
which may or may not happen automatically.
Yell if you need help with it. (And post some terminal output if there are conflicts that you or aptitude can't resolve.)
Oh, works! Thanks a lot. Can you say me if I had done some shit to this happens? Maybe I installed the wrong dependency or some shit like this? I don't want to repeat the error.
Edit: On a new install I had realized that elogind-dbgsym is also needed. Might it wasn't installed.
Last edited by ReallyNigga (2019-11-22 16:24:29)
Offline
I can't say why it happened, but there's a good chance it wasn't anything that you did. Take a look at the section on Session management and policykit backends in the release notes. It's a rat's nest of dependencies.
http://files.devuan.org/devuan_ascii/Release_notes.txt
Offline
I can't say why it happened, but there's a good chance it wasn't anything that you did. Take a look at the section on Session management and policykit backends in the release notes. It's a rat's nest of dependencies.
http://files.devuan.org/devuan_ascii/Release_notes.txt
I'm afraid to bother you again, but I want to share my minimal KDE install with the community, so here is another question: would be wise to include consolekit*- on the list, forcing APT to not install consolekit?
Last edited by ReallyNigga (2019-11-20 06:02:01)
Offline
What format for this system will you be offering? Live-iso, installer iso, disk image?
If you use live-sdk to make the iso, you can add consolekit to the purge_packages list. If you use refractasnapshot, you can remove consolekit before making the snapshot if it's installed. You should not add it to the excludes list - that wouldn't work right. If you're making a live iso that has the debian-installer, I probably can't help.
Offline
What format for this system will you be offering? Live-iso, installer iso, disk image?
If you use live-sdk to make the iso, you can add consolekit to the purge_packages list. If you use refractasnapshot, you can remove consolekit before making the snapshot if it's installed. You should not add it to the excludes list - that wouldn't work right. If you're making a live iso that has the debian-installer, I probably can't help.
No man, it's just a tutorial, a list of packages to install. I didn't find none when decide to install KDE, so I want to share.
Offline
Then include instructions for replacing consolekit just how you did it, in case it's needed.
Offline
sorry to revive this old thread.
But why is this whole policy stuff? or at least, why is it used to regulate shutdown/reboot, which can be handled by sudoers just as fine?
(at least IF some of the lightwight loginmanager like slim will survive.Which sadly might be unlikely for slim)
Offline
The issues with consolekit are not only limited to reboot/shutdown, initially you also can't open memory sticks/external drives as a user.
Simply installing
apt install libpolkit-backend-elogind-1-0 libpolkit-gobject-elogind-1-0
did the trick for me. It removes consolekit or whatever and issues are gone.
I guess this is inherited from Debian. The ASCII2.0 installer brings consolekit, and if I am not mistaken this is fixed with ASCII2.1, and for sure with Beowulf, no matter if installed from netinstall (currently no more available) or upgraded from ASCII.
rolfie
Last edited by rolfie (2020-03-01 09:48:23)
Online
Pages: 1