Re: [DNG] Reboot through a ConsoleKit DBus message as user

[KatolaZ]

On Mon, Feb 12, 2018 at 06:55:56PM +0100, J. Fahrner wrote:
> Am 2018-02-12 16:35, schrieb Irrwahn:
> >You should have one of:
> > libpolkit-backend-1-0-elogind
> >or, probably more fittingly in your case:
> > libpolkit-backend-1-0-consolekit
> >installed.
> 
> Now I tried both, and both give me working shutdown/reboot/suspend.
> What's the prefered backend for Devuan? elogind? Does elogind replace
> consolekit? I tried to remove consolekit, but slim depends on it.

The basic idea is that there is no preferred one: you choose. Some
login managers work with either of the two, some with just one of
them. Slim seems to be working preferably with the consolekit
backend. Lightdm seems to be able to work with either of the
two. Also, almost all the desktop tasks allow to choose which login
manager to use.

HND

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Reboot through a ConsoleKit DBus message as user

[J. Fahrner]

Am 2018-02-12 16:35, schrieb Irrwahn:

You should have one of:
libpolkit-backend-1-0-elogind
or, probably more fittingly in your case:
libpolkit-backend-1-0-consolekit
installed.


Now I tried both, and both give me working shutdown/reboot/suspend.
What's the prefered backend for Devuan? elogind? Does elogind replace 
consolekit? I tried to remove consolekit, but slim depends on it.

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Reboot through a ConsoleKit DBus message as user

[Irrwahn]

J. Fahrner wrote on 12.02.2018 18:08:
> Am 2018-02-12 16:35, schrieb Irrwahn:
>>> $ dpkg -l | fgrep libpolkit-backend
>>> rc  libpolkit-backend-1-0:i3860.105-9+devuan1
>>> i386 PolicyKit backend API
>>> ii  libpolkit-backend-1-0-systemd:i3860.105-18+devuan2.4
>>   ^
>> Now, there's your problem! :)
>>
>> You should have one of:
>>  libpolkit-backend-1-0-elogind
>> or, probably more fittingly in your case:
>>  libpolkit-backend-1-0-consolekit
>> installed.
> 
> Cause is the recent polkit update:

As I suspected. The glitch that I was referring to up-thread manifests 
in libpolkit-backend-1-0-systemd and libpolkit-gobject-1-0-systemd
being installed by apt-get, instead of one of their respective *-elogind 
or *-consolekit counterparts. I will contact the packager about possible 
ways to prevent this, as the *-systemd backend is basically useless in
Devuan.

> Reading package lists...
> Building dependency tree...
> Reading state information...
> The following additional packages will be installed:
>libpolkit-backend-1-0-systemd libpolkit-gobject-1-0-systemd
> The following packages will be REMOVED:
>libpolkit-backend-1-0 libpolkit-gobject-1-0
> The following NEW packages will be installed:
>libpolkit-backend-1-0-systemd libpolkit-gobject-1-0-systemd
> The following packages will be upgraded:
>libpolkit-agent-1-0 policykit-1
> 2 upgraded, 2 newly installed, 2 to remove and 0 not upgraded.
> Need to get 162 kB of archives.
> After this operation, 147 kB disk space will be freed.
> Get:1 http://pkgmaster.devuan.org/merged ascii/main amd64 policykit-1 
> amd64 0.105-18+devuan2.4 [59.8 kB]
> Get:2 http://pkgmaster.devuan.org/merged ascii/main amd64 
> libpolkit-agent-1-0 amd64 0.105-18+devuan2.4 [22.1 kB]
> Get:3 http://pkgmaster.devuan.org/merged ascii/main amd64 
> libpolkit-gobject-1-0-systemd amd64 0.105-18+devuan2.4 [38.5 kB]
> Get:4 http://pkgmaster.devuan.org/merged ascii/main amd64 
> libpolkit-backend-1-0-systemd amd64 0.105-18+devuan2.4 [41.4 kB]
> apt-listchanges: Reading changelogs...
> Fetched 162 kB in 0s (340 kB/s)
> dpkg: libpolkit-backend-1-0:amd64: dependency problems, but removing 
> anyway as you requested:
>   policykit-1 depends on libpolkit-backend-1-0 (>= 0.99).
> 
> Removing libpolkit-backend-1-0:amd64 (0.105-9+devuan1) ...
> Preparing to unpack .../policykit-1_0.105-18+devuan2.4_amd64.deb ...
> Unpacking policykit-1 (0.105-18+devuan2.4) over (0.105-9+devuan1) ...
> Preparing to unpack .../libpolkit-agent-1-0_0.105-18+devuan2.4_amd64.deb 
> ...
> Unpacking libpolkit-agent-1-0:amd64 (0.105-18+devuan2.4) over 
> (0.105-9+devuan1) ...
> 
> dpkg: libpolkit-gobject-1-0:amd64: dependency problems, but removing 
> anyway as you requested:
>   consolekit depends on libpolkit-gobject-1-0 (>= 0.94).
>   policykit-1-gnome depends on libpolkit-gobject-1-0 (>= 0.99); however:
>Package libpolkit-gobject-1-0:amd64 is to be removed.
>   colord depends on libpolkit-gobject-1-0 (>= 0.99).
>   network-manager depends on libpolkit-gobject-1-0 (>= 0.104); however:
>Package libpolkit-gobject-1-0:amd64 is to be removed.
>   upower depends on libpolkit-gobject-1-0 (>= 0.99).
>   udisks2 depends on libpolkit-gobject-1-0 (>= 0.101); however:
>Package libpolkit-gobject-1-0:amd64 is to be removed.
>   policykit-1 depends on libpolkit-gobject-1-0 (= 0.105-18+devuan2.4); 
> however:
>Package libpolkit-gobject-1-0:amd64 is to be removed.
>   libpolkit-agent-1-0:amd64 depends on libpolkit-gobject-1-0 (= 
> 0.105-18+devuan2.4).
> 
> Removing libpolkit-gobject-1-0:amd64 (0.105-9+devuan1) ...
> Selecting previously unselected package 
> libpolkit-gobject-1-0-systemd:amd64.
> Preparing to unpack 
> .../libpolkit-gobject-1-0-systemd_0.105-18+devuan2.4_amd64.deb ...
> Unpacking libpolkit-gobject-1-0-systemd:amd64 (0.105-18+devuan2.4) ...
> Selecting previously unselected package 
> libpolkit-backend-1-0-systemd:amd64.
> Preparing to unpack 
> .../libpolkit-backend-1-0-systemd_0.105-18+devuan2.4_amd64.deb ...
> Unpacking libpolkit-backend-1-0-systemd:amd64 (0.105-18+devuan2.4) ...
> Setting up libpolkit-gobject-1-0-systemd:amd64 (0.105-18+devuan2.4) ...
> Setting up libpolkit-agent-1-0:amd64 (0.105-18+devuan2.4) ...
> Setting up libpolkit-backend-1-0-systemd:amd64 (0.105-18+devuan2.4) ...
> Processing triggers for libc-bin (2.24-11+deb9u1) ...
> Processing triggers for man-db (2.7.6.1-2) ...
> Processing triggers for dbus (1.10.22-1+devuan1) ...
> Setting up policykit-1 (0.105-18+devuan2.4) ...
> Installing new version of config file /etc/pam.d/polkit-1 ...


Best regards
Urban
-- 
Sapere aude!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Reboot through a ConsoleKit DBus message as user

[J. Fahrner]

Am 2018-02-12 16:35, schrieb Irrwahn:

ii  libpolkit-backend-1-0-systemd:i3860.105-18+devuan2.4

  ^
Now, there's your problem! :)

You should have one of:
libpolkit-backend-1-0-elogind
or, probably more fittingly in your case:
libpolkit-backend-1-0-consolekit
installed.


Thanks for that hint. Replacing libpolkit-backend-1-0-systemd with 
libpolkit-backend-1-0-consolekit did the trick. No need to install any 
pkal file.


libpolkit-backend-1-0-systemd came in with the latest upgrade of 
policykit-1.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Reboot through a ConsoleKit DBus message as user

[J. Fahrner]

Am 2018-02-12 16:35, schrieb Irrwahn:

$ dpkg -l | fgrep libpolkit-backend
rc  libpolkit-backend-1-0:i3860.105-9+devuan1
i386 PolicyKit backend API
ii  libpolkit-backend-1-0-systemd:i3860.105-18+devuan2.4

  ^
Now, there's your problem! :)

You should have one of:
libpolkit-backend-1-0-elogind
or, probably more fittingly in your case:
libpolkit-backend-1-0-consolekit
installed.


Cause is the recent polkit update:

Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  libpolkit-backend-1-0-systemd libpolkit-gobject-1-0-systemd
The following packages will be REMOVED:
  libpolkit-backend-1-0 libpolkit-gobject-1-0
The following NEW packages will be installed:
  libpolkit-backend-1-0-systemd libpolkit-gobject-1-0-systemd
The following packages will be upgraded:
  libpolkit-agent-1-0 policykit-1
2 upgraded, 2 newly installed, 2 to remove and 0 not upgraded.
Need to get 162 kB of archives.
After this operation, 147 kB disk space will be freed.
Get:1 http://pkgmaster.devuan.org/merged ascii/main amd64 policykit-1 
amd64 0.105-18+devuan2.4 [59.8 kB]
Get:2 http://pkgmaster.devuan.org/merged ascii/main amd64 
libpolkit-agent-1-0 amd64 0.105-18+devuan2.4 [22.1 kB]
Get:3 http://pkgmaster.devuan.org/merged ascii/main amd64 
libpolkit-gobject-1-0-systemd amd64 0.105-18+devuan2.4 [38.5 kB]
Get:4 http://pkgmaster.devuan.org/merged ascii/main amd64 
libpolkit-backend-1-0-systemd amd64 0.105-18+devuan2.4 [41.4 kB]

apt-listchanges: Reading changelogs...
Fetched 162 kB in 0s (340 kB/s)
dpkg: libpolkit-backend-1-0:amd64: dependency problems, but removing 
anyway as you requested:

 policykit-1 depends on libpolkit-backend-1-0 (>= 0.99).

Removing libpolkit-backend-1-0:amd64 (0.105-9+devuan1) ...
Preparing to unpack .../policykit-1_0.105-18+devuan2.4_amd64.deb ...
Unpacking policykit-1 (0.105-18+devuan2.4) over (0.105-9+devuan1) ...
Preparing to unpack .../libpolkit-agent-1-0_0.105-18+devuan2.4_amd64.deb 
...
Unpacking libpolkit-agent-1-0:amd64 (0.105-18+devuan2.4) over 
(0.105-9+devuan1) ...


dpkg: libpolkit-gobject-1-0:amd64: dependency problems, but removing 
anyway as you requested:

 consolekit depends on libpolkit-gobject-1-0 (>= 0.94).
 policykit-1-gnome depends on libpolkit-gobject-1-0 (>= 0.99); however:
  Package libpolkit-gobject-1-0:amd64 is to be removed.
 colord depends on libpolkit-gobject-1-0 (>= 0.99).
 network-manager depends on libpolkit-gobject-1-0 (>= 0.104); however:
  Package libpolkit-gobject-1-0:amd64 is to be removed.
 upower depends on libpolkit-gobject-1-0 (>= 0.99).
 udisks2 depends on libpolkit-gobject-1-0 (>= 0.101); however:
  Package libpolkit-gobject-1-0:amd64 is to be removed.
 policykit-1 depends on libpolkit-gobject-1-0 (= 0.105-18+devuan2.4); 
however:

  Package libpolkit-gobject-1-0:amd64 is to be removed.
 libpolkit-agent-1-0:amd64 depends on libpolkit-gobject-1-0 (= 
0.105-18+devuan2.4).


Removing libpolkit-gobject-1-0:amd64 (0.105-9+devuan1) ...
Selecting previously unselected package 
libpolkit-gobject-1-0-systemd:amd64.
Preparing to unpack 
.../libpolkit-gobject-1-0-systemd_0.105-18+devuan2.4_amd64.deb ...

Unpacking libpolkit-gobject-1-0-systemd:amd64 (0.105-18+devuan2.4) ...
Selecting previously unselected package 
libpolkit-backend-1-0-systemd:amd64.
Preparing to unpack 
.../libpolkit-backend-1-0-systemd_0.105-18+devuan2.4_amd64.deb ...

Unpacking libpolkit-backend-1-0-systemd:amd64 (0.105-18+devuan2.4) ...
Setting up libpolkit-gobject-1-0-systemd:amd64 (0.105-18+devuan2.4) ...
Setting up libpolkit-agent-1-0:amd64 (0.105-18+devuan2.4) ...
Setting up libpolkit-backend-1-0-systemd:amd64 (0.105-18+devuan2.4) ...
Processing triggers for libc-bin (2.24-11+deb9u1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for dbus (1.10.22-1+devuan1) ...
Setting up policykit-1 (0.105-18+devuan2.4) ...
Installing new version of config file /etc/pam.d/polkit-1 ...


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Reboot through a ConsoleKit DBus message as user

[Irrwahn]

J. Fahrner wrote on 12.02.2018 16:22:
> Am 2018-02-12 16:04, schrieb Irrwahn:
>> Assuming you are on an ASCII system:
> 
> Yes.
> 
>> I strongly suspect this is linked to the recent addition of elogind
>> to the repositories and the consequential changes to policykit.
 

> I found a simpler way to make it work again on stackexchange (last 
> message):
> https://unix.stackexchange.com/questions/29637/how-do-i-shut-down-a-system-through-a-consolekit-dbus-message-as-user
> 
> But is this the right way to do this?

Yes. No. Maybe. As almost always when dealing with unixoid systems there 
is no one single right way to do a thing. Unless you use the broadest 
definition of the term, i.e.: "The right way is whatever works[TM] for me."

However, that having said (and IANAPKE[*]):
I suspect that the "ResultAny=yes" line in the linked SE thread could 
be considered a security hole at least by some. (I should probably not 
mention I used similar hacks in the past - alas, I just did. :P)

[*] I am not a policykit expert  ;o)

HTH
Best regards
Urban

-- 
Sapere aude!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Reboot through a ConsoleKit DBus message as user

[Irrwahn]

J. Fahrner wrote on 12.02.2018 16:19:
> Am 2018-02-12 16:05, schrieb Hleb Valoshka:
>> What Devuan version do you run? Ascii, don't you?
> 
> Yes, ascii.
> 
>> Show output of dpkg -l | grep libpolkit-backend
> 
> $ dpkg -l | fgrep libpolkit-backend
> rc  libpolkit-backend-1-0:i3860.105-9+devuan1
> i386 PolicyKit backend API
> ii  libpolkit-backend-1-0-systemd:i3860.105-18+devuan2.4   
  ^
Now, there's your problem! :)

You should have one of:
libpolkit-backend-1-0-elogind
or, probably more fittingly in your case:
libpolkit-backend-1-0-consolekit
installed.
Please refer to my earlier answer up-thread for more details.

Please allow me a side note, directed at all readers:
I assume we will see some more glitches like that happening upon 
updating Ascii systems in the near future.  Please remember: 
As solid as it may appear, Ascii is a yet unreleased testing suite, 
so some breakage should be expected anytime!

Best regards
Urban

-- 
Sapere aude!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Reboot through a ConsoleKit DBus message as user

[J. Fahrner]

Am 2018-02-12 16:04, schrieb Irrwahn:

Assuming you are on an ASCII system:


Yes.


I strongly suspect this is linked to the recent addition of elogind
to the repositories and the consequential changes to policykit.

In order to regain "classic" consolekit operation you may try the
following recipe:

1. Make sure the following packages are installed in their respective
   most recent versions:
consolekit
policykit-1
libpolkit-backend-1-0-consolekit

2. Run pam-auth-update in a root console and make sure that elogind
   is disabled and consolekit is enabled, leaving all other options
   as they are.

3. Reboot, or at least cycle through runlevel 1 and back to 2.

To switch back to elogind, if you so desire, you basically revert
steps 1. and 2.: Install libpolkit-backend-1-0-elogind and enable
it with pam-.auth-update, disabling consolekit at the same time.


I found a simpler way to make it work again on stackexchange (last 
message):

https://unix.stackexchange.com/questions/29637/how-do-i-shut-down-a-system-through-a-consolekit-dbus-message-as-user

But is this the right way to do this?
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Reboot through a ConsoleKit DBus message as user

[J. Fahrner]

Am 2018-02-12 16:05, schrieb Hleb Valoshka:

What Devuan version do you run? Ascii, don't you?


Yes, ascii.


Show output of dpkg -l | grep libpolkit-backend


$ dpkg -l | fgrep libpolkit-backend
rc  libpolkit-backend-1-0:i3860.105-9+devuan1
   i386 PolicyKit backend API
ii  libpolkit-backend-1-0-systemd:i3860.105-18+devuan2.4 
   i386 PolicyKit backend API




if you on Ascii you may have an incorrect polkit backend installed.


Is this ok?
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Reboot through a ConsoleKit DBus message as user

[Irrwahn]

J. Fahrner wrote on 12.02.2018 15:41:
> Hi,
> I have a small python gui script rebooting,shutdown,suspend. This sends 
> dbus messages to consolekit and is no longer working since a recent 
> update.
> 
> Rebooting is done as:
> 
> $ dbus-send --system --print-reply --dest='org.freedesktop.ConsoleKit' 
> /org/freedesktop/ConsoleKit/Manager 
> org.freedesktop.ConsoleKit.Manager.Restart
> Error org.freedesktop.ConsoleKit.Manager.NotPrivileged: Not Authorized
> 
> Any ideas what change recently caused this non-functioning? And how make 
> it work again?

Assuming you are on an ASCII system:

I strongly suspect this is linked to the recent addition of elogind
to the repositories and the consequential changes to policykit.

In order to regain "classic" consolekit operation you may try the 
following recipe:

1. Make sure the following packages are installed in their respective 
   most recent versions:
consolekit
policykit-1
libpolkit-backend-1-0-consolekit

2. Run pam-auth-update in a root console and make sure that elogind 
   is disabled and consolekit is enabled, leaving all other options 
   as they are.

3. Reboot, or at least cycle through runlevel 1 and back to 2.

To switch back to elogind, if you so desire, you basically revert 
steps 1. and 2.: Install libpolkit-backend-1-0-elogind and enable 
it with pam-.auth-update, disabling consolekit at the same time.

BTW, if you only used your script to fix a previous loss of GUI 
functionality WRT to shutdown, you may find that with elogind most
(if not all) desktop environments should now have (re-)gained that 
capability. Of course, this obviously only applies if you're using 
any prepackaged DE at all.

HTH
Best regards
Urban

-- 
Sapere aude!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Reboot through a ConsoleKit DBus message as user

[Hleb Valoshka]

Hi!

On 2/12/18, J. Fahrner  wrote:
> I have a small python gui script rebooting,shutdown,suspend. This sends
> dbus messages to consolekit and is no longer working since a recent
> update.

What Devuan version do you run? Ascii, don't you?

> Any ideas what change recently caused this non-functioning? And how make
> it work again?

Show output of dpkg -l | grep libpolkit-backend

if you on Ascii you may have an incorrect polkit backend installed.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng