Launchpad has imported 18 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1201964.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
I'm on Ubuntu 15.10 and still have the same problem:
Feb 10 09:07:09 DELL-PC systemd-logind[710]: Failed to add match for
JobRemoved: Connection timed out
Feb 10 09:07:09 DELL-PC systemd-logind[710]: Failed to fully start up daemon:
Connection timed out
Feb 10 09:07:35 DELL-PC dbus[729]:
I am very, very painfully going through this process right now.
I REALLY need dpkg to stop trying to remove colord and network-manager
(dependent on policykit-1). It would also help if Ubuntu Web Browser
were a little more responsive.. Took 10 minutes to type this far
probably unrelated...
I cannot reproduce this with current upstream git master any more, so I
ran another bisect. Apparently
http://cgit.freedesktop.org/systemd/systemd/commit/?id=6410 fixes
this, so I guess the regression was introduced in
http://cgit.freedesktop.org/systemd/systemd/commit/?id=a354329f72 and
the
Also tracked in Arch Linux: https://bugs.archlinux.org/task/44016
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1423811
Title:
219-1ubuntu1 regression: boot hangs, logind fails
To manage
I just applied all v219-stable patches on top of our package, and
dropped the reverted patch. I now get the boot failures again, so I'm
afraid that wasn't it.
** Also affects: systemd (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1201964
Importance: Unknown
Status: Unknown
FWIW I was seeing something that sounds very similar on F22:
https://bugzilla.redhat.com/show_bug.cgi?id=1201964
but it *seems* to have gone away with systemd-219-11.fc22, which is
basically the same as systemd 'v219-stable' -
http://cgit.freedesktop.org/systemd/systemd-stable/log/?h=v219-stable
I don't get the hang with the reproducer in comment 11 on Fedora 21 with
systemd 219 and dbus 1.8.16 from rawhide.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1423811
Title:
219-1ubuntu1
I'm getting a similar (perhaps/hopefully the same) hang if I do this:
systemctl mask --runtime systemd-journald systemd-logind; systemctl stop
systemd-journald systemd-logind
SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-journald
# restart 5 times
SYSTEMD_LOG_LEVEL=debug
** Also affects: systemd
Importance: Undecided
Status: New
** Changed in: systemd
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1423811
This bug was fixed in the package systemd - 219-3ubuntu1
---
systemd (219-3ubuntu1) vivid; urgency=medium
* Merge with Debian experimental. Remaining Ubuntu changes:
- Hack to support system-image read-only /etc, and modify files in
/etc/writable/ instead.
- Keep our
I'm running git bisect start v219 v218 -- src/shared src/journal on
upstream trunk now (some 220 commits to test), using the above
autopkgtest. I don't use git bisect run, as the autopkgtest sometimes
fails with exit code 16 (testbed setup); in those cases it should be re-
run to either succeed,
This is an automated reproducer in the form of an autopkgtest. You can
call it like this:
adt-run --built-tree ./systemd-bootsmoke --- qemu /srv/vm/adt-
pid1.img
This reboots the VM up to 20 times, and check for stuck jobs or non-
running polkit on each iteration. You can also test with
autopkgtest committed: http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=experimentalid=75f84790871
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1423811
Title:
219-1ubuntu1
This is an improved git bisect script which is now robust against
transient testbed failures and make build failures. This is now
suitable for a fully automated git bisect run ./systemd-bisect-run.sh,
and was able to identify the regression in 2 h fully noninteractively.
This is now mostly of
Bisect run finished. The culprit is
http://cgit.freedesktop.org/systemd/systemd/commit/?id=13790add4bf64
This reverts cleanly against master, and running 219 with journald with
that commit reverted runs stable.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Bug watch added: Debian Bug tracker #778970
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778970
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778970
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: systemd (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1423811
Title:
219-1ubuntu1 regression: boot hangs, logind fails
To manage
** Changed in: systemd (Debian)
Status: Unknown = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1423811
Title:
219-1ubuntu1 regression: boot hangs, logind fails
To manage
Notekeeping:
- installing self-built .debs: boot ok
- reinstalling ubuntu debs: boot fail
- Removing persistant journal (sudo rm -r /var/log/journal) with the ubuntu
binaries: boot ok
- rebooting a few times with re-enabling persistant journal: boot ok
- QEMU with enabling persistant journal and
I can reproduce this quite reliably with:
sudo rm -r /var/log/journal
sudo mkdir /var/log/journal
sudo apt-get install --reinstall systemd
I now managed to reproduce the hang in a VM as well, with these
commands.
--
You received this bug notification because you are a member of Ubuntu
I continued to bisect binaries (/lib/systemd/{systemd,systemd-logind
,systemd-journald,systemd-fsck,systemd-fsckd}.
I never got a hang with 219 + journald from 218, and I did get a hang
with 218 + journald from 219, which indicates that this is related to
journald. Didier confirmed the latter
** Description changed:
Since yesterday, systemd does not boot properly any more. It takes very
long, ends up in an X failsafe session, and eventually you just get a
getty on VT1.
+ Downgrading libpam-systemd libsystemd0 systemd systemd-sysv to
+
23 matches
Mail list logo
