** Changed in: dbus
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus timeout-ed during an upgrade, taking services down
> The comment at
https://github.com/fwupd/fwupd/issues/3037#issuecomment-1100816992
suggests that disabling the DynamicUser= setting makes the service work
again. Maybe that's worth a try, in order to get both problems solved?
(i.e. shipping an override config for fwupd)
> $cat
Quoting upstream systemd developers
(https://github.com/systemd/systemd/issues/22737#issuecomment-1077682307):
"We essentially traded one problem (lockup when starting services) for another
(the failure described in this commit).
I actually think that the lockup is worse. Here there is a simple
> https://git.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/systemd/commit/?id=e3aacfa26e3fc6df369e6f28e740389ae0020907
This appears to have caused a regression in fwupd in Ubuntu 20.04 with
details at https://github.com/fwupd/fwupd/issues/3037
fwupd-refresh.service uses DynamicUser and now
This bug was fixed in the package systemd - 248.3-1ubuntu8.5
---
systemd (248.3-1ubuntu8.5) impish; urgency=medium
* debian/tests/boot-and-services: Ignore failed snap mount units in
test_no_failed (LP: #1967576)
systemd (248.3-1ubuntu8.4) impish; urgency=medium
[ Lukas Märdian
This bug was fixed in the package systemd - 245.4-4ubuntu3.16
---
systemd (245.4-4ubuntu3.16) focal; urgency=medium
[ Dan Streetman ]
* d/p/lp1946388-sd-journal-don-t-check-namespaces-if-we-have-no-name.patch:
Avoid journalctl segfault (LP: #1946388)
[ Jeremy Szu ]
* Add
** Tags removed: verification-needed verification-needed-focal
verification-needed-impish
** Tags added: verification-done verification-done-focal
verification-done-impish
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I started 156 instances for both:
* an impish image with systemd 248.3-1ubuntu8.5
* a focal image with systemd 245.4-4ubuntu3.16
In both images, I also removed the workaround in
/etc/systemd/system/dbus.service.d
(Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=1) to make sure I was really
testing the
The autopkgtest regressions blocking systemd 248.3-1ubuntu8.5 in impish-
proposed have been resolved. The regressions were caused either by (1)
network/infrastructure issues and succeeded on retry, or by (2)
unrelated snapd regressions. The systemd 248.3-1ubuntu8.5 upload added
an autopkgtest
The autopkgtest regressions blocking systemd 245.4-4ubuntu3.16 in focal-
proposed have been resolved. The regressions appear to have been related
to recent autopkgtest infrastructure issues, and retrying the tests
resolved the issues.
--
You received this bug notification because you are a
I can't test this reliably (as stated in the SRU description), but at
least I can say I haven't seen it in the last 24h :-) I think this is on
@gjolly to try to reproduce it in the mentioned azure test environment.
--
You received this bug notification because you are a member of Ubuntu
Touch
Hello Christian, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.16 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Christian, or anyone else affected,
Accepted systemd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Merge proposal linked:
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/417577
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Fixed also in systemd v250.4 and v249.11
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus timeout-ed during an upgrade, taking services down including
This bug was fixed in the package systemd - 249.10-0ubuntu2
---
systemd (249.10-0ubuntu2) jammy; urgency=medium
* Fix deadlock between pid1 and dbus-daemon (LP: #1871538)
File:
debian/patches/pid1-set-SYSTEMD_NSS_DYNAMIC_BYPASS-1-env-var-for-dbus-da.patch
** Changed in: systemd (Ubuntu Jammy)
Status: New => In Progress
** Changed in: systemd (Ubuntu Jammy)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
** Description changed:
+ [Impact]
+
+ * There's currently a deadlock between PID 1 and dbus-daemon: in some
+ cases dbus-daemon will do NSS lookups (which are blocking) at the same
+ time PID 1 synchronously blocks on some call to dbus-daemon (e.g.
`GetConnectionUnixUser` DBus call). Let's
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: systemd (Ubuntu Groovy)
** No longer affects: systemd (Ubuntu Hirsute)
** Also affects: dbus (Ubuntu Jammy)
Importance: High
Status: Incomplete
** Also affects: gnome-shell (Ubuntu
The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.
** Changed in: dbus (Ubuntu Hirsute)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This is now part of Azure's cloud images (focal to devel) and I can
confirm that it fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
There is some news about this issue at systemd:
https://github.com/systemd/systemd/issues/15316#issuecomment-1000842001
Could people try to place this systemd override config for dbus and
observe if it avoids the issue?
```
$ cat /etc/systemd/system/dbus.service.d/override.conf
[Service]
I'm still suspecting dbus to be at fault here. We might need to bisect
dbus in order to find out more about this, but that is hard without a
reliable reproducer.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice
FYI triggered again for me due to unattended upgrades.
The time in the journal when things go down matches the
unpack/configuee/install phase of
- accountsservice:amd64 0.6.55-0ubuntu12~20.04.5
- libaccountsservice0:amd64 0.6.55-0ubuntu12~20.04.5
- dbus:amd64 1.12.16-2ubuntu2.1
I - again - had
Addressed in FR-1460
** Tags removed: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus timeout-ed during an upgrade, taking
** Merge proposal linked:
https://code.launchpad.net/~vorlon/ubuntu-seeds/+git/platform/+merge/408418
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
** Tags added: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus timeout-ed during an upgrade, taking services down including gdm
An interesting observation I made is that all journal logs (in this LP
bug and the upstream systemd bug) show the "polkit.service: Unexpected
error response from GetNameOwner(): Connection terminated" message, in
addition to a bunch of other "Connection terminated" errors from
changing services
** Changed in: accountsservice (Ubuntu Groovy)
Status: New => Invalid
** Changed in: accountsservice (Ubuntu Hirsute)
Status: New => Invalid
** Changed in: gnome-shell (Ubuntu Groovy)
Status: New => Invalid
** Changed in: gnome-shell (Ubuntu Hirsute)
Status: New =>
** Tags removed: rls-ff-incoming rls-hh-incoming rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus timeout-ed during an upgrade,
** Tags added: fr-1460
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus timeout-ed during an upgrade, taking services down including gdm
Status
I filed an upstream bug with D-Bus:
https://gitlab.freedesktop.org/dbus/dbus/-/issues/337
Hopefully a maintainer there will be able to give a better opinion as to
what's going on here
** Bug watch added: gitlab.freedesktop.org/dbus/dbus/-/issues #337
Ok I will cook an other custom image and try to reproduce.
Concerning this log line:
Jun 16 08:55:45 alan-hirsute-base-aiamcicscciaelhaktpo dbus-daemon[711]:
[system] Connection has not authenticated soon enough, closing it
(auth_timeout=3ms, elapsed: 45129ms)
Please note that during our
Thanks! Here's where I think the problem starts:
Ok, let's authenticate to dbus:
Jun 16 08:54:54 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Bus
bus-api-system: changing state AUTHENTICATING → HELLO
...
Jun 16 08:54:54 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Bus
Also, systemd is actually reloaded by cloud-init. In cloud-init logs, I
can read:
2021-06-16 08:54:51,608 - subp.py[DEBUG]: Running command ['systemctl',
'daemon-reload'] with allowed return codes [0] (shell=False, capture=True)
2021-06-16 08:54:51,953 - cc_mounts.py[DEBUG]: Activate mounts:
@laney I built a custom image with system logs level set to debug and I
was able to reproduce the issue. You can find the logs attached.
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1871538/+attachment/5505001/+files/syslog
--
You received this bug
** Also affects: dbus (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: accountsservice (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Tags added:
That's interesting actually. I thought this was an interaction between
reloading dbus-daemon and daemon-reloading systems at the same time. But
in this cloud case, I don't think dbus is being reloaded, is it?
It's going to be next to impossible for me to look into this in detail
without being
I seems that we are seeing this issue on Azure with Ubuntu >=20.04. The
CPC team is running a series of tests before publishing images, those
tests spin up ~50 instances in Azure and usually one of them is having
this issue.
You can find the system logs of a failing instance here:
** Tags removed: champagne
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus timeout-ed during an upgrade, taking services down including gdm
** Tags removed: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus timeout-ed during an upgrade, taking services down including
Oh.. I wasn't really aware of that (-1 = all) and it looked so similar.
Right, so we still somehow need to find a proper reproducer...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
Yeah, sorry, I don't think that's a reproducer for the bug. You killed
dbus, gdm and everything else, and they obligingly died on you. :)
My feeling is that this bug is about a deadlock that somehow happens
when dbus and/or systemd are reloaded, possibly at the same time. It
looks like dbus stops
Well, more correctly -1 means to all processes you can send to, and if
you're root, well it's everyone.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
kill(-1, SIGINT) kills all processes on the system with SIGINT, so this
is hardly surprising.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus
By chance (while developing some netplan code), I seem to have found a
reproducer for this bug... I don't know what is going on, but calling
the 'Trigger' method from the attached 'dbus.c' file will kill the GDM
session in a reproducible way.
The invalid `kill(-1, SIGINT);` of line 21, seems to
@Dimitri desktop isn't working on it at this point, unsure how to figure
out where the issue is exactly but it sounds like it could be either
dbus or systemd which are owned by foundations
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Hm, so is desktop working on this? Have we figured out at all what is
happening? Or just the general symptoms that dbus seems to be non-
responsive and then everything goes bad?
** Changed in: dbus (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: dbus (Ubuntu Focal)
Status:
I've a similar issue on Groovy. I got it 2 days in a row after my daily package
update.
Reverting the machine to a state before the upgrade and re-upgrading the same
packages doesn't reproduce the issue. However, when it worked with the same
package update the message "Unexpected error response
The last two updates went smooth for me, not triggering it.
I'm still too afraid to "just update while working" as I did in the past since
it could drag things down thou :-/
I was feeling like this could be solved, but reading that Steve is also
affected I'm worried that I might just not hit the
** Changed in: systemd
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus timeout-ed during an upgrade, taking
** Bug watch added: github.com/systemd/systemd/issues #15316
https://github.com/systemd/systemd/issues/15316
** Also affects: systemd via
https://github.com/systemd/systemd/issues/15316
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
I also hit this again in focal on 2020-06-25, with an update to systemd
245.4-4ubuntu3.1; I had previously updated dbus to 1.12.16-2ubuntu2.1 on
2020-06-17 without event. It's still an issue at least with updates to
systemd in focal.
Similar messages end up in the journal:
Jun 25 13:04:55 kryten
[Expired for dbus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: dbus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
[Expired for dbus (Ubuntu Focal) because there has been no activity for
60 days.]
** Changed in: dbus (Ubuntu Focal)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in
I hit that again today on an upgrade.
Network manager didn't come up again.
Mai 20 11:04:46 Keschdeichel systemd[1]: NetworkManager.service: Unexpected
error response from GetNameOwner(): Connection terminated
Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9491]
caught
** Tags added: id-5e988df7fb344884f67bc04f
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus timeout-ed during an upgrade, taking services down
** Also affects: dbus (Ubuntu Focal)
Importance: High
Status: Incomplete
** Also affects: gnome-shell (Ubuntu Focal)
Importance: Undecided
Status: Invalid
** Also affects: accountsservice (Ubuntu Focal)
Importance: Undecided
Status: Invalid
--
You received this
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus timeout-ed during an upgrade, taking services down including gdm
Oh, and I have no crash files in /var/crash/.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus timeout-ed during an upgrade, taking services
Hi, I had a similar crash this morning upgrading focal, after trying to
get unattended-upgrades to stop spinning on missing focal-security apt
list files. In this case, I don't use gnome-shell as my desktop
environment, but it still tore down my entire desktop environment and
caused gdm3 to
Sure @seb128 - I'll let you know if it happens again (as I did a
cleaning-reboot now).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus
62 matches
Mail list logo
