Re: systemctl reboot fails (doesn't reboot)

[tomas]

On Mon, Mar 04, 2019 at 08:40:50AM -0300, riveravaldez wrote:
> On 3/2/19, to...@tuxteam.de  wrote:
> > On Fri, Mar 01, 2019 at 06:38:33PM -0300, riveravaldez wrote:
> >> Hi, I'm on debian-testing (updated), and found this issue:
> >
> > I have very little experience with systemd, but...

[...]

> >   sudo apt-get install --reinstall policykit-1
> >
> > or whatever you favourite reinstallation method is.
> 
> Thanks a lot, tomás!

Let me reiterate that I don't know exactly what I am doing, but hey.

> Indeed, all hints point to PolicyKit (package: policykit-1)
> 
> Because of the errors on systemd I have it marked to hold, and I
> suppose some package updated and now I have an inconsistency, see:
> 
> $ sudo apt-get --reinstall install policykit-1
> Reading list of packages ... Done
> Creating dependency tree
> Reading the status information ... Done
> Can't instal some package. This may mean that you asked for an
> impossible situation or, if you are using the distribution unstable,
> that some necessary packages have not yet been created or have been
> removed from «Incoming».
> The following information can help resolve the situation:
> 
> The following packages have unfulfilled dependencies:
>   policykit-1: It depends: libpam-systemd but it will not be installed
>   systemd: It depends: libsystemd0 (= 240-4) but 240-6 is going to be 
> installed
> Recommend: libpam-systemd but it will not be installed
> E: Error, pkgProblemResolver :: Resolve generated cuts, this may be
> due to retained packets.
> 
> 
> So, I guess I could try downgrading policykit-1 until the situation
> gets fixed, but I don't know how.

Hm. You can (try to) install a specific version with

  sudo apt-get install --reinstall policykit-1=

but note two things: your apt source might not always carry that
(you have checked for that) and you're moving yourself into more
and more trouble, as your package set becomes more and more complex.

This isn't bad per se, but be prepared to learn some things about
packaging and dependencies :-)

Cheers
-- t


signature.asc
Description: Digital signature

Re: systemctl reboot fails (doesn't reboot)

[riveravaldez]

On 3/2/19, to...@tuxteam.de  wrote:
> On Fri, Mar 01, 2019 at 06:38:33PM -0300, riveravaldez wrote:
>> Hi, I'm on debian-testing (updated), and found this issue:
>
> I have very little experience with systemd, but...
>
>> $ systemctl reboot
>> Failed to set wall message, ignoring: The name
>> org.freedesktop.PolicyKit1 was not provided by any .service files
>
> ...as other posts in this thread already seem to hint at, something
> in your PolicyKit seems broken: and as PolicyKit is the machinery
> which has to decide whether you, as a "normal user" are allowed to
> reboot...
>
>> Failed to reboot system via logind: The name
>
> ...no decision can be taken, so you aren't allowed.
>
> I'd try reinstalling whatever PolicyKit packages seem relevant.
> Perhaps start trying to locate whatever file hides behind the
> ".service file" which is supposed to "provide" the "name"
> "org.freedesktop.PolicyKit1" (goodness! the jargon alone is for
> me reason enough to stay clear of that stuff -- but I disgress).
>
> As a starting point, apt-file search [1] is usually a good help:
>
>   tomas@trotzki:~$ apt-file search PolicyKit1
>   policykit-1: /etc/dbus-1/system.d/org.freedesktop.PolicyKit1.conf
>   policykit-1:
> /usr/share/dbus-1/system-services/org.freedesktop.PolicyKit1.service
>   policykit-1-doc:
> /usr/share/doc/policykit-1-doc/html/eggdbus-interface-org.freedesktop.PolicyKit1.AuthenticationAgent.html
>   policykit-1-doc:
> /usr/share/doc/policykit-1-doc/html/eggdbus-interface-org.freedesktop.PolicyKit1.Authority.html
>
> The second line looks like right. So if I were you, I'd try
> to reinstall the package "policykit-1", e.g. by issuing:
>
>   sudo apt-get install --reinstall policykit-1
>
> or whatever you favourite reinstallation method is.

Thanks a lot, tomás!

Indeed, all hints point to PolicyKit (package: policykit-1)

Because of the errors on systemd I have it marked to hold, and I
suppose some package updated and now I have an inconsistency, see:

$ sudo apt-get --reinstall install policykit-1
Reading list of packages ... Done
Creating dependency tree
Reading the status information ... Done
Can't instal some package. This may mean that you asked for an
impossible situation or, if you are using the distribution unstable,
that some necessary packages have not yet been created or have been
removed from «Incoming».
The following information can help resolve the situation:

The following packages have unfulfilled dependencies:
  policykit-1: It depends: libpam-systemd but it will not be installed
  systemd: It depends: libsystemd0 (= 240-4) but 240-6 is going to be installed
Recommend: libpam-systemd but it will not be installed
E: Error, pkgProblemResolver :: Resolve generated cuts, this may be
due to retained packets.


So, I guess I could try downgrading policykit-1 until the situation
gets fixed, but I don't know how.

Which would be the proper/best way to downgrade policykit-1 (or any
other package necessary) to the last working version?

It seems like I don't have the previous version available from repositories...

$ apt-cache policy policykit-1
policykit-1:
  Instalados: (ninguno)
  Candidato:  0.105-25
  Tabla de versión:
 0.105-25 500
500 http://deb.debian.org/debian testing/main amd64 Packages
100 /var/lib/dpkg/status

$ apt-cache showpkg policykit-1
Package: policykit-1
Versions:
0.105-25 
(/var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_binary-amd64_Packages)
(/var/lib/dpkg/status)
 Description Language:
 File:
/var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_binary-amd64_Packages
  MD5: 233f6ea057dc90084c0e92b57d21a7a8
 Description Language:
 File:
/var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_binary-i386_Packages
  MD5: 233f6ea057dc90084c0e92b57d21a7a8
 Description Language: es
 File:
/var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_i18n_Translation-es
  MD5: 233f6ea057dc90084c0e92b57d21a7a8
 Description Language: en
 File:
/var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_i18n_Translation-en
  MD5: 233f6ea057dc90084c0e92b57d21a7a8


Reverse Depends:
  tuned,policykit-1 0.105-17~
  udisks2,policykit-1
  systemd,policykit-1
  policykit-1:i386,policykit-1
  dbus-user-session:i386,policykit-1 0.105-12~
  zulupolkit,policykit-1
  zoneminder,policykit-1
  wicd-gtk,policykit-1
  veyon-master,policykit-1
  upower,policykit-1
  ukui-power-manager,policykit-1
  ukui-polkit,policykit-1
  udisks2,policykit-1
  gdm3,policykit-1 0.105-5~
  tails-installer,policykit-1
  systemd,policykit-1
  synaptic,policykit-1
  python-jarabe,policykit-1
  policycoreutils-gui,policykit-1
  policycoreutils-dbus,policykit-1
  gameconqueror,policykit-1
  rtkit,policykit-1
  realmd,policykit-1
  polkit-kde-agent-1,policykit-1
  policykit-1-gnome,policykit-1
  peony-admin,policykit-1
  packagekit,policykit-1
  zen

Re: systemctl reboot fails (doesn't reboot)

[tomas]

On Sat, Mar 02, 2019 at 02:03:38AM +0100, deloptes wrote:
> riveravaldez wrote:
> 
> > Hi, I'm on debian-testing (updated), and found this issue:
> > 
> > $ systemctl reboot
> 
> At this point it is advisable to read some linux basics ... I think there
> are also videos in youtube - just like taking driving course or any kind of
> course for operating a device. I mean you can not cook without knowing what
> a pan is.

This seems unnecessarily condescending.

Cheers
-- tomás


signature.asc
Description: Digital signature

Re: systemctl reboot fails (doesn't reboot)

[tomas]

On Fri, Mar 01, 2019 at 06:38:33PM -0300, riveravaldez wrote:
> Hi, I'm on debian-testing (updated), and found this issue:

I have very little experience with systemd, but...

> $ systemctl reboot
> Failed to set wall message, ignoring: The name
> org.freedesktop.PolicyKit1 was not provided by any .service files

...as other posts in this thread already seem to hint at, something
in your PolicyKit seems broken: and as PolicyKit is the machinery
which has to decide whether you, as a "normal user" are allowed to
reboot...

> Failed to reboot system via logind: The name

...no decision can be taken, so you aren't allowed.

I'd try reinstalling whatever PolicyKit packages seem relevant.
Perhaps start trying to locate whatever file hides behind the
".service file" which is supposed to "provide" the "name"
"org.freedesktop.PolicyKit1" (goodness! the jargon alone is for
me reason enough to stay clear of that stuff -- but I disgress).

As a starting point, apt-file search [1] is usually a good help:

  tomas@trotzki:~$ apt-file search PolicyKit1
  policykit-1: /etc/dbus-1/system.d/org.freedesktop.PolicyKit1.conf
  policykit-1: 
/usr/share/dbus-1/system-services/org.freedesktop.PolicyKit1.service
  policykit-1-doc: 
/usr/share/doc/policykit-1-doc/html/eggdbus-interface-org.freedesktop.PolicyKit1.AuthenticationAgent.html
  policykit-1-doc: 
/usr/share/doc/policykit-1-doc/html/eggdbus-interface-org.freedesktop.PolicyKit1.Authority.html

The second line looks like right. So if I were you, I'd try
to reinstall the package "policykit-1", e.g. by issuing:

  sudo apt-get install --reinstall policykit-1

or whatever you favourite reinstallation method is.

Take all this with a grain of salt: those packages aren't installed
on /my/ machine ;-)

Cheers

[1] You don't have apt-file? Go, no, RUN! to your next pharmacy
  uh, apt repo and install it. Right now!
-- tomás


signature.asc
Description: Digital signature

Re: systemctl reboot fails (doesn't reboot)

[Cindy-Sue Causey]

On 3/2/19, Teemu Likonen  wrote:
> riveravaldez [2019-03-01 23:09:12-03] wrote:
>
>> I've been rebooting with 'systemctl reboot' as a normal user in
>> debian-testing (and even other distros) for a couple of years now, and
>> never had no problem.
>
> "systemctl reboot" as a normal user should work if Policy kit and
> Systemd components are working. I don't know what is the problem but I
> have seen it a couple of times: a normal user can't shut down or reboot
> the machine nor put it in suspend mode. After reboot the problem is
> gone. It seems that the bug has something to do Policy kit.


This topic came up a while back. Can't remember if I participated then
but had intended to do so.

It always seems odd that you can shut down or reboot from either the
Applications menu at the top left or the "Session Menu" (hiding under
the user name) at the top right of the screen (in Xfce4)...

But it doesn't work from a terminal command line. :)

I'm in Buster for good now... and I got blocked in the last couple
weeks. Had to "sudo" to get out. Was just too lazy to reach up to dig
out "Log Out" from either of those menus. :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed *

Re: systemctl reboot fails (doesn't reboot)

[Teemu Likonen]

riveravaldez [2019-03-01 23:09:12-03] wrote:

> I've been rebooting with 'systemctl reboot' as a normal user in
> debian-testing (and even other distros) for a couple of years now, and
> never had no problem.

"systemctl reboot" as a normal user should work if Policy kit and
Systemd components are working. I don't know what is the problem but I
have seen it a couple of times: a normal user can't shut down or reboot
the machine nor put it in suspend mode. After reboot the problem is
gone. It seems that the bug has something to do Policy kit.


-- 
/// Teemu Likonen   - .-..    //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///


signature.asc
Description: PGP signature

Re: systemctl reboot fails (doesn't reboot)

[Jape Person]

On 3/1/19 5:53 PM, Gian Carlo wrote:
> Il 01/03/19 22:40, riveravaldez ha scritto:
>> Hi, I'm on debian-testing (updated), and found this issue:
>>
>> $ systemctl reboot
>> Failed to set wall message, ignoring: The name
>> org.freedesktop.PolicyKit1 was not provided by any .service files
>> Failed to reboot system via logind: The name
>> org.freedesktop.PolicyKit1 was not provided by any .service files
>> Failed to start reboot.target: The name org.freedesktop.PolicyKit1 was
>> not provided by any .service files
>> See system logs and 'systemctl status reboot.target' for details.
>>
>> $ systemctl status reboot.target
>> reboot.target - Reboot
>> Loaded: loaded (/lib/systemd/system/reboot.target; disabled; vendor
>> preset: enabled)
>> Active: inactive (dead)
>> Docs: man:systemd.special(7)
>>
>> $ systemctl restart reboot.target
>> Failed to restart reboot.target: The name org.freedesktop.PolicyKit1
>> was not provided by any .service files
>> See system logs and 'systemctl status reboot.target' for details.
>>
>> But 'sudo reboot' worked.
>>
>> Any idea?
> 
> 
>> $ systemctl reboot
>> $ systemctl status reboot.target
>> $ systemctl restart reboot.target
> You are NOT root
> 
>> But 'sudo reboot' worked.
> After "sudo..." you are root
> 
> Bye,
> 
> gc
> 
> 

I'm curious as to why

$ systemctl restart reboot.target

is being used. On my systems

$ systemctl start reboot.target

results in a request for the root password. (And results for failure to type it 
correctly for a remote system via SSH often gets you punished with a 
non-responsive SSH session on the terminal.)

Am I misunderstanding the problem?

Re: systemctl reboot fails (doesn't reboot)

[riveravaldez]

On 3/1/19, deloptes  wrote:
> riveravaldez wrote:
>
>> Hi, I'm on debian-testing (updated), and found this issue:
>>
>> $ systemctl reboot
>
> At this point it is advisable to read some linux basics ... I think there
> are also videos in youtube - just like taking driving course or any kind of
> course for operating a device. I mean you can not cook without knowing what
> a pan is.

Thanks for the help (?), but I've been rebooting with 'systemctl
reboot' as a normal user in debian-testing (and even other distros)
for a couple of years now, and never had no problem.

I'll try with sudo as soon as I come back to that machine, but I
inform this because, as said, it's a new behavior, and I don't know
what provoked the change.

Maybe someone can give some hint about it.

Thanks again.

Re: systemctl reboot fails (doesn't reboot)

[deloptes]

riveravaldez wrote:

> Hi, I'm on debian-testing (updated), and found this issue:
> 
> $ systemctl reboot

At this point it is advisable to read some linux basics ... I think there
are also videos in youtube - just like taking driving course or any kind of
course for operating a device. I mean you can not cook without knowing what
a pan is.

regards

Re: systemctl reboot fails (doesn't reboot)

[Gian Carlo]

Il 01/03/19 22:40, riveravaldez ha scritto:
> Hi, I'm on debian-testing (updated), and found this issue:
> 
> $ systemctl reboot
> Failed to set wall message, ignoring: The name
> org.freedesktop.PolicyKit1 was not provided by any .service files
> Failed to reboot system via logind: The name
> org.freedesktop.PolicyKit1 was not provided by any .service files
> Failed to start reboot.target: The name org.freedesktop.PolicyKit1 was
> not provided by any .service files
> See system logs and 'systemctl status reboot.target' for details.
> 
> $ systemctl status reboot.target
> reboot.target - Reboot
> Loaded: loaded (/lib/systemd/system/reboot.target; disabled; vendor
> preset: enabled)
> Active: inactive (dead)
> Docs: man:systemd.special(7)
> 
> $ systemctl restart reboot.target
> Failed to restart reboot.target: The name org.freedesktop.PolicyKit1
> was not provided by any .service files
> See system logs and 'systemctl status reboot.target' for details.
> 
> But 'sudo reboot' worked.
> 
> Any idea?


> $ systemctl reboot
> $ systemctl status reboot.target
> $ systemctl restart reboot.target
You are NOT root

> But 'sudo reboot' worked.
After "sudo..." you are root

Bye,

gc

systemctl reboot fails (doesn't reboot)

[riveravaldez]

Hi, I'm on debian-testing (updated), and found this issue:

$ systemctl reboot
Failed to set wall message, ignoring: The name
org.freedesktop.PolicyKit1 was not provided by any .service files
Failed to reboot system via logind: The name
org.freedesktop.PolicyKit1 was not provided by any .service files
Failed to start reboot.target: The name org.freedesktop.PolicyKit1 was
not provided by any .service files
See system logs and 'systemctl status reboot.target' for details.

$ systemctl status reboot.target
reboot.target - Reboot
Loaded: loaded (/lib/systemd/system/reboot.target; disabled; vendor
preset: enabled)
Active: inactive (dead)
Docs: man:systemd.special(7)

$ systemctl restart reboot.target
Failed to restart reboot.target: The name org.freedesktop.PolicyKit1
was not provided by any .service files
See system logs and 'systemctl status reboot.target' for details.

But 'sudo reboot' worked.

Any idea?

Thanks a lot!