Am 03.09.19 um 01:07 schrieb David Anderson:
> If possible, could this fix be released as a Buster update as well?
> This bug prevents the use of networkd to set up Wireguard VPN servers
> on Buster, and it's hard to workaround without resorting to racey
> shell scripts.
According to the upstream
Package: systemd
Version: 241-5
Submitter: s.pri...@profihost.ag
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: buster-backport
Am 04.09.19 um 14:09 schrieb Stefan Priebe - Profihost AG:
> Hello,
>
> currently systemd is broken in buster regarding RootDirectory and User.
>
>
On Thu, 27 Nov 2014 14:43:33 -0800 Nikolaus Rath wrote:
> On Sat, 15 Nov 2014 00:17:59 +0100 Szymon Weihs wrote:
> >
> > When I'm doing reboot or shutdown from graphical environment (systemctl
> > reboot/poweroff), my screen turns off immediately so I can't see any
> > messages
> > provided
Am 04.09.19 um 14:09 schrieb Stefan Priebe - Profihost AG:
> Hello,
>
> currently systemd is broken in buster regarding RootDirectory and User.
>
> The issue was fixed in systemd 243 and the relevant commits are
> referenced in the specific bug report:
>
Am 04.09.19 um 14:57 schrieb Michael Biebl:
> Am 04.09.19 um 14:09 schrieb Stefan Priebe - Profihost AG:
>> Hello,
>>
>> currently systemd is broken in buster regarding RootDirectory and User.
>>
>> The issue was fixed in systemd 243 and the relevant commits are
Am 06.09.19 um 10:25 schrieb Harald Dunkel:
> Package: systemd
> Version: 241-5
>
> systemd in Buster and older fails to handle MountFlags correctly,
> see
>
> https://github.com/systemd/systemd/commit/37ed15d7edaf59a1fc7c9e3552cd93a83f3814ef
>
>
> This seriously affects the "containerd"
Am 06.09.19 um 10:07 schrieb Martins Pukitis:
> Package: systemd
> Version: 241-5
> Severity: important
> File: systemd-networkd
>
> Dear Maintainer, bridge interface setup status stays "configuring" (not
> "configured").
> My systemd-networkd configuration:
> lieta@lieta:~$ sudo brctl show
>
Am 06.09.19 um 10:35 schrieb Michael Biebl:
> Am 06.09.19 um 10:25 schrieb Harald Dunkel:
>> Package: systemd
>> Version: 241-5
>>
>> systemd in Buster and older fails to handle MountFlags correctly,
>> see
>>
>> https://github.com/systemd/systemd/co
Am 06.09.19 um 10:07 schrieb Martins Pukitis:
> Package: systemd
> Version: 241-5
> Severity: important
> File: systemd-networkd
>
> Dear Maintainer, bridge interface setup status stays "configuring" (not
> "configured").
> My systemd-networkd configuration:
> lieta@lieta:~$ sudo brctl show
>
Hi,
https://github.com/systemd/systemd/pull/13357 has just been merged into
systemd.
With this available in udev, I wonder if lib2f-udev and its static rules
becomes obsolete or if there is still value to keep that package?
Regards,
Michael
--
Why is it that all of the instruments seeking
Control: reassign -1 initramfs-tools 0.135
Am 13.09.19 um 11:54 schrieb Mikulas Patocka:
> Package: udev
> Version: 242-7
> Severity: normal
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
>
> I use
Am 11.09.19 um 15:54 schrieb Julian Hübenthal:
> Just discovered something that may help to debug:
>
>
>
> It does not happen with a simple “Hello World” bash script instead of
> the Check MK Agent.
>
> It does not happen when the Encryption of the Check MK Agent is disabled.
>
> It happens
Am 10.09.19 um 11:03 schrieb Svante Signell:
> severity 935304 important
> thanks
>
> Michael: Next time you lower the importance of this bug, please give a
> motivation. It is not especially instructive doing such a thing without
> explaining why.
Svante, next you respect the decision of the
Am 09.09.19 um 13:53 schrieb Elimar Riesebieter:
> * Michael Biebl [2019-09-09 13:09 +0200]:
>
>> Control: tags -1 moreinfo
>>
>> Am 09.09.19 um 12:30 schrieb Elimar Riesebieter:
>>> Package: systemd
>>> Version: 242-7
>>> Severity: normal
>&
Control: tags -1 moreinfo
Am 09.09.19 um 12:30 schrieb Elimar Riesebieter:
> Package: systemd
> Version: 242-7
> Severity: normal
>
> Dear maintainer,
>
> found in jornalctl -alb:
> systemd-udevd: Specified group 'render' unknown
>
> Don't know why this group is needed. There is no group
Am 11.09.19 um 00:12 schrieb Guillem Jover:
> We hit an assert in logind from the latest systemd package in buster:
>
> systemd-logind coredumped: in log_assert_failed_realm ... at
> ../src/basic/log.c:795
>
> Investiaging from the following stack trace:
[...]
Hi Guillem, thanks for the
wouldn't it be better if wireguard calls resolvctl directly?
Then it knows exactly what kind of behaviour it'll get.
You're right about the resolvconf.1 man page. We should not ship that in
the systemd man page since we don't ship the resolvconf symlink either
(for obvious reasons).
Regards,
Am 07.09.19 um 12:44 schrieb Michael Biebl:
> Control: tags -1 moreinfo
>
> Am 07.09.19 um 11:36 schrieb Nikolaus Rath:
>> Package: systemd-container
>> Version: 241-5
>> Severity: normal
>> File: /usr/bin/systemd-nspawn
>>
>> Not sure what to make of
Control: tags -1 moreinfo
Am 07.09.19 um 11:36 schrieb Nikolaus Rath:
> Package: systemd-container
> Version: 241-5
> Severity: normal
> File: /usr/bin/systemd-nspawn
>
> Not sure what to make of this:
>
> # systemd-nspawn -M resuce --boot --private-users -D /mnt/usbdrive
> Spawning container
Am 07.09.19 um 12:46 schrieb Nikolaus Rath:
>
> On Sat, 7 Sep 2019, at 11:44, Michael Biebl wrote:
>> Control: tags -1 moreinfo
>>
>> Am 07.09.19 um 11:36 schrieb Nikolaus Rath:
>>> Package: systemd-container
>>> Version: 241-5
>>>
Am 06.09.19 um 10:42 schrieb Michael Biebl:
> Am 06.09.19 um 10:35 schrieb Michael Biebl:
>> Am 06.09.19 um 10:25 schrieb Harald Dunkel:
>>> Would it be possible to cherrypick this fix for Buster and
>>> Stretch?
>>
>> Why stretch? According to the ups
Hi Joel
On Tue, 26 Jun 2018 11:54:36 +0100 Joel Cross
wrote:
> Package: systemd
> Version: 239-1
> Severity: normal
>
> Dear Maintainer,
>
> Over the last few days (since my last system upgrade) I am unable to
> successfully hibernate/resume using the `systemctl hibernate` command. This is
>
Am 17.09.19 um 04:47 schrieb Bob Tracy:
> I note the bug was closed back on April 15th. I wanted to report that
> the underlying issue was evidently a buggy "glibc" implementation. A
> recent upgrade to "libc6.1" (to version 2.29-1) took care of the
> problem.
>
> See a discussion thread in the
Am 08.09.19 um 16:12 schrieb Michael Biebl:
> Control: tags -1 moreinfo
>
> Can you attach the output of blkid please.
And please also the "gdisk i" output for all partitions
--
Why is it that all of the instruments seeking intelligent life in the
universe are poin
Control: tags -1 moreinfo
Can you attach the output of blkid please.
I suspect it is systemd-gpt-auto-generator which generates this swap
unit based on the GPT information it finds (man 8
systemd-gpt-auto-generator)
You can of course disable that generator if you so desire.
First I'd like to
Thanks for testing
Am 05.09.19 um 07:52 schrieb Stefan Priebe - Profihost AG:
> Yes, that works fine! Thanks a lot. Is there any ETA for a release?
As I tried to explain (see below), since I don't knwo when 10.2 will be,
the answer is no.
> Am 04.09.19 um 22:32 schrieb Michael Biebl:
Am 13.09.19 um 00:53 schrieb Michael Biebl:
> Am 12.09.19 um 14:29 schrieb Michael Biebl:
>> Am 11.09.19 um 15:54 schrieb Julian Hübenthal:
>>> Just discovered something that may help to debug:
>>>
>>>
>>>
>>> It does not happen with a simple
Am 12.09.19 um 14:29 schrieb Michael Biebl:
> Am 11.09.19 um 15:54 schrieb Julian Hübenthal:
>> Just discovered something that may help to debug:
>>
>>
>>
>> It does not happen with a simple “Hello World” bash script instead of
>> the Check MK Agent.
>&
Source: haveged
Version: 1.9.1-8
Severity: normal
Hi,
I noticed that debian/haveged.service uses
[Install]
WantedBy=default.target
default.target is an alias and should not be used directly.
Instead you should either hook into multi-user.target or
graphical.target.
In this particular case,
Package: lintian
Version: 2.17.0
Severity: wishlist
Hi,
I noticed a couple of systemd system services
(files that match /lib/systemd/system/*.{service,socket,...})
that use
[Install]
Alias=default.target
default.target is only an alias and should not be used for that.
Instead services should
Control: tags -1 + moreinfo
Am 07.08.19 um 20:14 schrieb Daniel Baumann:
> Package: systemd
> Severity: important
> Version: 241-7 242-2
>
> Hi,
>
> when using systemd-nspawn containers, systemd 241 and 242 do not bring
> up the interfaces when using kernel 5.2. with kernel 4.9 it works.
>
>
Am 07.08.19 um 18:22 schrieb Michael Biebl:
> Package: lintian
> Version: 2.17.0
> Severity: wishlist
>
> Hi,
>
> I noticed a couple of systemd system services
> (files that match /lib/systemd/system/*.{service,socket,...})
> that use
>
> [Install]
> Alias=d
Am 06.08.19 um 15:35 schrieb Felipe Sateler:>
>
> On Tue, Aug 6, 2019 at 3:15 AM Michael Biebl # systemctl restart rpcbind.service rpcbind.socket
>
> Job for rpcbind.socket failed.
> See "systemctl status rpcbind.socket" and "journalctl -xe&quo
Control: tags -1 + moreinfo unreproducible
Am 09.08.19 um 08:15 schrieb Marc Haber:
>
> I have not fully understood what happens here. I am monitoring my
> filesystems with aide, and sometimes get the following report:
>
> ---
> Changed entries:
>
Am 06.08.19 um 04:48 schrieb Debian Bug Tracking System:
> rpcbind (1.2.5-5) unstable; urgency=medium
> .
>* debian/rules: Add --no-restart-after-upgrade option to
> dh_installsystemd to avoid race condition at rpcbind.socket
> initialization (Closes: #933268)
Am 06.08.19 um 09:15 schrieb Michael Biebl:
> Am 06.08.19 um 04:48 schrieb Debian Bug Tracking System:
>> rpcbind (1.2.5-5) unstable; urgency=medium
>> .
>>* debian/rules: Add --no-restart-after-upgrade option to
>> dh_installsystemd to avoid race
On Mon, 27 May 2019 21:03:03 + Simon Beirnaert
wrote:
> Package: systemd
> Version: 232-25+deb9u11
> Severity: normal
>
> Dear Maintainer,
>
>
> Systemd does not seem to consistently put sshd processes under the
> relevant user's slice. I have a user with 10925 sshd processes related
> to
Hi Kevin,
could you give the packages at
https://people.debian.org/~biebl/systemd/stretch/
a try and report back if they fix your issue?
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital
Am 11.07.19 um 17:41 schrieb Mert Dirik:
> On 7/11/19, Thomas Bätzler wrote:
>>
>> To wit:
>>
>> root@kvm1:~# /etc/init.d/rsync
>> Usage: /etc/init.d/rsync {start|stop|reload|force-reload|restart|status}
>>
>> vs.
>>
>> root@kvm1:~# /etc/init.d/mysql
>>
Am 18.07.19 um 13:55 schrieb Michael Biebl:
> Am 11.07.19 um 17:41 schrieb Mert Dirik:
>> On 7/11/19, Thomas Bätzler wrote:
>>>
>>> To wit:
>>>
>>> root@kvm1:~# /etc/init.d/rsync
>>> Usage: /etc/init.d/rsync {start|stop|reload|force-
Hi everyone,
the first buster point release is not that far away.
I've pushed the changes I think are appropriate for buster to master and
just released 241-7 to unstable so we have some more wide spread test
coverage.
I basically want to release 241-7 as-is to buster (as either
241-7~deb10u1 or
reassign 932421 release.debian.org
severity 932421 normal
retitle 932421 nmu: systemd_242-2
user release.debian@packages.debian.org
usertag 932421 + binnmu
thanks
Am 19.07.19 um 04:43 schrieb 積丹尼 Dan Jacobson:
> Package: systemd
> Version: 242-2
> Severity: minor
>
> # aptitude search ~o
> i
On Thu, 11 Jul 2019 18:41:01 +0300 Mert Dirik wrote:
> On 7/11/19, Thomas Bätzler wrote:
> >
> > To wit:
> >
> > root@kvm1:~# /etc/init.d/rsync
> > Usage: /etc/init.d/rsync {start|stop|reload|force-reload|restart|status}
> >
> > vs.
> >
> > root@kvm1:~# /etc/init.d/mysql
> >
Control: tags -1 moreinfo unreproducible
Am 26.07.19 um 07:04 schrieb WHR:
> Package: systemd
> Version: 241-5
> Severity: normal
>
> Hello.
> I found the systemctl(1) command outputs are garbled in my terminal, if auto
> terminal paging is disabled.
> A screenshot is attached, or it is also
Am 26.07.19 um 11:21 schrieb 王昊然:
> OK, now I understands that was a feature, but how should I tell
> systemd to disable this feature so I can get a normal terminal output
> in terminals that doesn't support this feature?
man systemd
$SYSTEMD_URLIFY
The value must be a boolean.
+
+ [ Mert Dirik ]
+ * 40-systemd: Don't fail if SysV init script uses set -u and $1 is unset
+(Closes: #931719)
+
+ -- Michael Biebl Fri, 26 Jul 2019 21:32:04 +0200
+
systemd (241-5) unstable; urgency=medium
* Revert "Add check to switch VTs only between K_XLATE or K_UNICODE"
Am 20.09.19 um 23:23 schrieb Marc Haber:
> On Fri, Sep 20, 2019 at 11:13:51PM +0200, Michael Biebl wrote:
>> Am 20.09.19 um 23:07 schrieb Marc Haber:
>>> 118 ippl.service start waiting
>>
>> Where is this service coming from?
>
>>F
Am 20.09.19 um 18:41 schrieb Marc Haber:
> Package: systemd
> Version: 242-7
> Severity: important
>
> Hi,
>
> thie system in question is a Banana Pi which I cannot update properly.
> apt's postinst isues systemctl restart apt-daily-upgrade.timer which
> hangs indefinetely. I can reproduce this
Am 20.09.19 um 23:07 schrieb Marc Haber:
>> systemd-analyze dump
> Attached, too long.
Afaics this is missing
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Am 31.08.19 um 20:08 schrieb Michael Biebl:
> On Tue, 6 Aug 2019 09:42:15 -0400 Kathryn Tolsen
> wrote:
>>> Which version is this?
>>
>>> Is the problem still reproducible?
>>
>> root@t440:/home/user# dpkg -l systemd udev linux-image-amd64;cat
>> /e
Hi Marc
Am 20.09.19 um 23:07 schrieb Marc Haber:
> 118 ippl.service start waiting
Where is this service coming from?
Can you attach the status / content of this service.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away
Am 21.09.19 um 08:53 schrieb Marc Haber:
> On Sat, Sep 21, 2019 at 12:06:51AM +0200, Michael Biebl wrote:
>> Ok, thanks. I have a feeling we are getting closer.
>> If you (temporarily) disable ippl (via update-rc.d ippl disable), what
>> do you get on next reboot fo
Am 26.09.19 um 08:35 schrieb Jörg Sommer:
> Michael Biebl hat am Do 26. Sep, 00:00 (+0200) geschrieben:
>> Am 25.09.19 um 14:22 schrieb Jörg Sommer:
>>> Michael Biebl hat am Mi 25. Sep, 12:33 (+0200) geschrieben:
>>>> output of
>>>> systemd-analyz
Am 02.10.19 um 18:50 schrieb Alexandra N. Kossovsky:
> On 02/10/2019 19:36, Michael Biebl wrote:
>> Could you file this upstream at
>> https://github.com/systemd/systemd/issues and report back with the bug
>> number?
>
> Sorry, but I can't, because I did not tes
Am 02.10.19 um 18:01 schrieb Alexandra N. Kossovsky:
> Package: udev
> Version: 242-7
> Severity: normal
>
> When I create a bonding interface on an older Debian system, it
> naturally inherits one of the slave's mac address. With new Debian
> testing (systemd=242-7) the bonding interface gets a
Am 22.09.19 um 16:29 schrieb Marc Haber:
> On Sun, Sep 22, 2019 at 04:12:43PM +0200, Michael Biebl wrote:
>> Since systemd-time-wait-sync.service doesn't seem to really work with
>> alternative implementations, I wonder if it wouldn't be better to err on
>> the safe safe
Am 22.09.19 um 15:39 schrieb Michael Biebl:
> does
> "systemd-time-wait-sync blocks indefinitely with alternative NTP
> implementations, stalling boot and units depending on time-sync.target"
> sound ok?
So, I just ran a test on a system which has chrony installed and it
s
Am 22.09.19 um 16:29 schrieb Marc Haber:
> On Sun, Sep 22, 2019 at 04:12:43PM +0200, Michael Biebl wrote:
>> Since systemd-time-wait-sync.service doesn't seem to really work with
>> alternative implementations, I wonder if it wouldn't be better to err on
>> the safe safe
Am 22.09.19 um 16:46 schrieb Michael Biebl:
> Am 22.09.19 um 16:29 schrieb Marc Haber:
>> On Sun, Sep 22, 2019 at 04:12:43PM +0200, Michael Biebl wrote:
>>> Since systemd-time-wait-sync.service doesn't seem to really work with
>>> alternative implementations, I wond
Am 22.09.19 um 15:39 schrieb Michael Biebl:
> Since you are adamant that you haven't enabled the service manually (at
> least not explicitly), I wonder if you used something like "systemctl
> preset" in the past and it was enabled because of that (afaics
> systemd-
Am 22.09.19 um 14:08 schrieb Marc Haber:
> On Sat, Sep 21, 2019 at 05:05:10PM +0200, Michael Biebl wrote:
>>> 58 systemd-time-wait-sync.service start running
>>
>> Hm, this service is not enabled by default and I'm guessing it prevents
>> time-sync.targ
Control: tags -1 + pending
Am 01.10.19 um 16:08 schrieb Laurent Bonnaud:
> Package: udev
> Version: 243-2
> Severity: normal
>
>
> Dear Maintainer,
>
> here is an error message I see in the journal:
>
> Oct 01 09:32:00 host systemd-udevd[403]:
>
Am 30.06.2019 um 07:12 schrieb Michael Biebl:
> As you can see, after 30s the eye-of-cylon animation kicks in and after
> 300s the boot proceeds and successfully completes.
sorry for the typo, meant 200s here
> This is even a more elaborate setup with LVM and stuff.
To be sure, I al
Am 09.07.19 um 21:41 schrieb Marc Haber:
> On Tue, Jul 09, 2019 at 07:16:07PM +0200, Michael Biebl wrote:
>> Can you test those patches to verify that they fix your issue?
>
> Even an unpatched systemd 241-6 fails building in my sid build chroot:
>
> 433/51
Am 09.07.19 um 18:44 schrieb Marc Haber:
> https://bugzilla.kernel.org/show_bug.cgi?id=204099
> https://bugzilla.kernel.org/show_bug.cgi?id=203769
>
> identify the kernel commit that broke things,
See also
https://lore.kernel.org/netdev/58ac6ec1-9255-0e51-981a-195c2b1ac...@mellanox.com/T/
but
Am 09.07.19 um 17:48 schrieb Marc Haber:
> On Mon, Jul 08, 2019 at 04:41:00PM +0200, Marc Haber wrote:
>> I will attach straces of a working and a non-working case once the bug
>> number is known. If you need additional information, I will help.
>
> Here are the straces. .prelink is an invocation
Hi Noah
Am 02.11.19 um 00:05 schrieb Noah Meyerhans:
> I'd like to propose that we switch to cgroupv2 as the default
> configuration for the bullseye release. This has the potential to
> impact quite a few packages (notably, it breaks Docker today), so I
Afaics, lxc is also affected, which is
Control: tags -1 + moreinfo
On Mon, 23 Jul 2018 10:11:15 +0800 Zhu Yijun wrote:
> Package: systemd
> Version: 232-25+deb9u4
>
>
> Description of problem:
> After a 'systemctl daemon-reload' followed by any service 'systemctl
> restart xxx' the blkio, cpu,cpuacct、memory cgroup path changed.
>
Hi Ansgar
On Thu, 12 Sep 2019 09:00:12 +0200 Ansgar wrote:
> Ben Hutchings writes:
> > On Wed, 2019-09-11 at 19:20 +0200, Ansgar wrote:
> >> would it be possible to add a fallback to try /lib/systemd/systemd if
> >> the user provided init=/bin/systemd and the file no longer exists?
> >>
> >> I
Hi Noah,
I plan to upload v243 to unstable soonish and will revert back to hybrid
for the time being.
That said, I started filing / user tagging bugs:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-systemd-maintain...@lists.alioth.debian.org;tag=cgroupv2
Please *do* test cgroupv2 /
On Sun, 30 Sep 2018 10:24:10 +0300
=?UTF-8?B?0J/QsNCy0LXQuyDQodCw0LzRgdC+0L3QvtCy?=
wrote:
> Please get image
> wget http://tinyware.ru/iso/Test.iso
Is this issue still valid? If so, can you please re-upload that image.
I'm getting a 404 for that URL.
Thanks,
Michael
--
Why is it that all of
Hi Peter,
can you file this issue to upstream at
https://github.com/systemd/systemd/issues and report back with the issue
number.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description:
Btw, this reminds me of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883877#103
Is this the same host where this is happening (again)?
Is this a Virtualbox guest?
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
control: notfound -1 242-8
control: found -1 243-5
Am 13.11.19 um 17:01 schrieb Peter Habcak:
> Package: udev
> Version: 242-8
> Severity: normal
>
> Dear Maintainer,
>
> After upgrading systemd (including udev) from 242-8 to 243-5 on my SID laptop,
> keyboard and mouse suddenly stopped working
Thanks a lot for the information so far.
Am 13.11.19 um 16:53 schrieb Martin-Éric Racine:
> Setting up udev (243-5) ...
Could you add a "set -x" to
/var/lib/dpkg/info/udev.postinst to see which command triggers the segfault.
I suspect it's the daemon-reload, if so, it would be interesting if a
Control: tags -1 moreinfo unreproducible
Hi
Am 13.11.19 um 10:34 schrieb Martin-Éric Racine:
> Package: systemd
> Version: 243-5
> Severity: important
>
> systemd upgrade broke dbus, which in turn prevents normal operation of APT
> and upgrade of packages that depend upon dbus messages.
>
>
Am 13.11.19 um 16:09 schrieb Martin-Éric Racine:
> ke 13. marrask. 2019 klo 17.06 Martin-Éric Racine
> (martin-eric.rac...@iki.fi) kirjoitti:
>> It indeed crashed as soon as it was upgraded.
>>
...
>>> I suppose your problem should be fixed when you do a forced reboot.
>>
>> It wasn't fixed by
Control: forwarded -1 https://github.com/systemd/systemd/issues/14027
Am 14.11.19 um 14:23 schrieb Gunther Furtado:
> Keyboard and mouse not working in X.org with udev 243-5 #14027
Thanks, marking accordingly.
--
Why is it that all of the instruments seeking intelligent life in the
universe
Control: severity -1 normal
Am 14.11.19 um 13:22 schrieb Jan Sindelar:
> Package: systemd
> Version: 243-5
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
>* What led up to the situation?
> Installing latest systemd package using apt full-upgrade in
Am 14.11.19 um 17:16 schrieb Michael Biebl:
> For the failing binary, please run
> ldd /path/to/binary
>
> and attach the output to this bug report.
I see from your systemd-delta.txt output:
systemd-delta: symbol lookup error:
/lib/systemd/libsystemd-shared-243.so: unde
Am 13.11.19 um 20:48 schrieb Martin-Éric Racine:
> ke 13. marrask. 2019 klo 21.03 Michael Biebl (bi...@debian.org) kirjoitti:
>>
>> Btw, this reminds me of
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883877#103
>>
>> Is this the same ho
Ok, at this point I guess it's best to involve upstream.
Would you mind filing an upstream bug report at
https://github.com/systemd/system/issues
mentionting that a daemon-reload triggers an assert in
manager_unref_uid_internal() and attaching your backtrace.
Thanks,
Michael
--
Why is it that
Am 14.11.19 um 20:26 schrieb Sorin Manolache:
I copy the new binaries from
> /usr/lib/x86_64-linux-gnu to /lib/x86_64-linux-gnu.
Please don't do that. The only reasonable solution is to remove any
stale libraries you have copied/installed manually.
You might have to run ldconfig afterwards.
--
Am 14.11.19 um 23:27 schrieb Jan Sindelar:
> Actually I have found a bunch of libraries not owned by any package
> (according to dpkg) in this directory and I am pretty sure I never manually
> copied them. Clearly this bug is not related to systemd, but I am not sure
> where should I report it.
Am 14.11.19 um 20:26 schrieb Sorin Manolache:
> I had the same problem. The cause were some old libs in
> /lib/x86_64-linux-gnu, especially a libseccomp. They are not
> package-managed (i.e. they don't belong to any package). I have copied
> them manually from /usr/lib/x86_64-linux-gnu to
On Sun, 17 Nov 2019 18:23:08 +0100 Nicolas Patrois
wrote:
> Package: udev
> Version: 243-7
> Severity: minor
> File: systemd-udevd
>
> Dear Maintainer,
>
> I just had an upgrade and I see this in the logs:
>
> nov. 17 18:11:23 nicolas.home systemd-udevd[24479]:
>
Am 17.11.19 um 01:57 schrieb Jonah Brüchert:
> Thanks for looking into the issue.
>
>> Can you be more specific how you setup your chroot so we have a chance
>> to reproduce the problem?
[..]
I guess you'll need to break that down to a more minimal test case for
me being able to reproduce the
Am 17.11.19 um 01:57 schrieb Jonah Brüchert:
> After slightly looking into the debos source code it seems also possible
> that it uses a systemd-spawn container in some cases
> (https://github.com/go-debos/debos/blob/2764eed783b1b0ffb5d09f796338f09a4e2594b6/commands.go#L15)
Can you please verify,
Control: retitle -1 udevadm trigger fails in containers with ro /sys
Am 17.11.19 um 02:43 schrieb Michael Biebl:
> Am 17.11.19 um 01:57 schrieb Jonah Brüchert:
>> After slightly looking into the debos source code it seems also possible
>> that it uses a systemd-spawn containe
Can you all check if you have the i386 version of libinput-bin installed
(by accident) on your amd64 system?
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Control: tags -1 + moreinfo
Am 18.11.19 um 10:20 schrieb Fred Boiteux:
> Package: systemd
> Version: 241-7~deb10u2
> Severity: normal
>
> Dear Maintainer,
>
> On a Debian Buster system, I've installed the Squid package. It doesn't
> start on every boot. On my system, the /var directory is on a
Am 18.11.19 um 11:24 schrieb Michael Biebl:
> Can you all check if you have the i386 version of libinput-bin installed
> (by accident) on your amd64 system?
>
.. and if installing the amd64 version via
apt install libinput-bin:amd64
helps
--
Why is it that all of the instrument
Control: severity -1 wishlist
Control: forwarded -1 https://github.com/systemd/systemd/issues/14002
Am 12.11.19 um 12:35 schrieb Vincent Lefevre:
> Package: systemd
> Version: 243-5
> Severity: normal
>
> I can notice new setting
>
> [Network]
> #SpeedMeter=no
> #SpeedMeterIntervalSec=10sec
>
Am 12.11.19 um 18:07 schrieb gregor herrmann:
> Anyway, back to the lvremove issue; I have a few packages to upload
> anyway, so I can test autopkgtest with schroot and LVM snapshots in
> production :)
>
> I have now run autopkgtest(-pkg-perl) on 5 packages, that means 15
> creations and
Am 12.11.19 um 10:09 schrieb gregor herrmann:
> On Tue, 12 Nov 2019 08:17:07 +0100, Antonio wrote:
>
>> after updating systemd to version 243-5, my backup procedures, which
>> include the use of snapshots on lvm2 logical volumes, were blocked
>> during the snapshot removal phase.
>
> FWIW, I've
Am 12.11.19 um 14:36 schrieb Michael Biebl:
> There is this upstream bug report
> https://github.com/systemd/systemd/issues/14002
Oops, wrong C This is the right one
https://github.com/systemd/systemd/issues/13976
> and a associated PR
> https://github.com/systemd/systemd/pull/1398
Am 12.11.19 um 19:04 schrieb gregor herrmann:
> On Tue, 12 Nov 2019 18:55:46 +0100, Michael Biebl wrote:
>
>>> I have now run autopkgtest(-pkg-perl) on 5 packages, that means 15
>>> creations and removals of LVM snapshots, and I haven't encountered
>>> any issu
Control: tags -1 + moreinfo
Am 23.08.19 um 01:06 schrieb Marc Lehmann:
> Package: systemd
> Version: 241-5
> Severity: minor
>
> Dear Maintainer,
>
> on one of my systems, debian runs from a filesystem image loop-mounted
> from an ntfs volume using ntfs-3g, and thus, the ntfs-3g process must be
Am 15.11.19 um 11:30 schrieb Sorin Manolache:
> As a side, I think having systemd depend on libraries deployed in /usr
> is a bad idea. More generally, using tools (e.g. /usr/bin/find) in the
> pre-mount phase of the boot process that either are deployed in /usr or
> depend on libs in /usr is, in
Control: tags -1 moreinfo unreproducible
Am 16.11.19 um 16:05 schrieb Jonah Brüchert:
> Package: udev
> Version: 243-5
> Severity: normal
>
> Dear Maintainer,
>
> When running udevadm trigger in a chroot, in this case using debos, it fails
> to write changes to /sys and exits with an error
601 - 700 of 1851 matches
Mail list logo
