Bug#964926: systemd: systemctl show prints "Failed to parse bus message: Invalid argument" before output

2020-09-22 Thread Michael Biebl
Am 22.09.20 um 10:28 schrieb Marc Haber: > On Tue, Sep 15, 2020 at 09:33:52PM +0200, Michael Biebl wrote: >> Does it help, if you cherry-pick e41de5e491942b as well? >> >> commit e41de5e491942b5391b1efb71c82ffd329b3d23d >> Author: Michal Koutný >> Date: Wed Jun 24 12:43:22 2020 +0200 > > Yes.

Bug#964926: systemd: systemctl show prints "Failed to parse bus message: Invalid argument" before output

2020-09-22 Thread Marc Haber
On Tue, Sep 15, 2020 at 09:33:52PM +0200, Michael Biebl wrote: > Does it help, if you cherry-pick e41de5e491942b as well? > > commit e41de5e491942b5391b1efb71c82ffd329b3d23d > Author: Michal Koutný > Date: Wed Jun 24 12:43:22 2020 +0200 Yes. I can confirm that with this patch addiitonally

Bug#964926: systemd: systemctl show prints "Failed to parse bus message: Invalid argument" before output

2020-08-07 Thread Marc Haber
On Thu, Aug 06, 2020 at 11:40:23PM +0200, Michael Biebl wrote: > Am 06.08.20 um 14:25 schrieb Marc Haber: > > On Tue, Jul 14, 2020 at 09:13:15PM +0100, Hugh Cole-Baker wrote: > >> It turns out this is just caused by running a 5.8-rc kernel with systemd > >> compiled against linux-libc-dev 5.7,

Bug#964926: systemd: systemctl show prints "Failed to parse bus message: Invalid argument" before output

2020-08-06 Thread Michael Biebl
Control: user pkg-systemd-maintain...@lists.alioth.debian.org Control: usertag -1 + buster-backport Am 06.08.20 um 14:25 schrieb Marc Haber: > On Tue, Jul 14, 2020 at 09:13:15PM +0100, Hugh Cole-Baker wrote: >> It turns out this is just caused by running a 5.8-rc kernel with systemd >> compiled

Bug#964926: systemd: systemctl show prints "Failed to parse bus message: Invalid argument" before output

2020-08-06 Thread Marc Haber
On Tue, Jul 14, 2020 at 09:13:15PM +0100, Hugh Cole-Baker wrote: > It turns out this is just caused by running a 5.8-rc kernel with systemd > compiled against linux-libc-dev 5.7, there's a new capability cap_bpf > that systemctl fails to display since it's not in linux/capability.h. > > The same

Bug#964926: systemd: systemctl show prints "Failed to parse bus message: Invalid argument" before output

2020-07-14 Thread Michael Biebl
Control: tags -1 + fixed-upstream Control: forwarded -1 https://github.com/systemd/systemd/pull/16424 Am 14.07.20 um 22:13 schrieb Hugh Cole-Baker: > It turns out this is just caused by running a 5.8-rc kernel with systemd > compiled against linux-libc-dev 5.7, there's a new capability cap_bpf >

Bug#964926: systemd: systemctl show prints "Failed to parse bus message: Invalid argument" before output

2020-07-14 Thread Hugh Cole-Baker
It turns out this is just caused by running a 5.8-rc kernel with systemd compiled against linux-libc-dev 5.7, there's a new capability cap_bpf that systemctl fails to display since it's not in linux/capability.h. The same issue is described here, with a link to the upstream fix:

Bug#964926: systemd: systemctl show prints "Failed to parse bus message: Invalid argument" before output

2020-07-12 Thread Michael Biebl
Am 12.07.20 um 19:50 schrieb Hugh Cole-Baker: > I just realised after doing some further testing that this report may > not be very useful, since the bug doesn't occur on the standard bullseye > linux-image-arm64 kernel - only on a kernel I compiled with customised > options. I will do some more

Bug#964926: systemd: systemctl show prints "Failed to parse bus message: Invalid argument" before output

2020-07-12 Thread Hugh Cole-Baker
I just realised after doing some further testing that this report may not be very useful, since the bug doesn't occur on the standard bullseye linux-image-arm64 kernel - only on a kernel I compiled with customised options. I will do some more debugging to provide more information on the relation