** Also affects: open-vm-tools (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Artful)
Importance: Undecided
Status: New
** No longer affects: systemd (Ubuntu Artful)
** Changed in: open-vm-tools (Ubuntu Xenial)
Status: Invalid => Tri
Public bug reported:
This is mostly an FYI and a tracker to link Upstream to Ubuntu.
Background:
I wondered why some of my services are missing just the most interesting "last"
messages before dying.
Unfortunately I found this is a known race and there seems to be no good fix
yet.
But I think
Public bug reported:
The test really seems to be triggered all of the time to resolve a flaky test.
That is just not worth the test.
But it provides goo coverage, so an override in britney would loose all that.
Lets skip the offending test on the arch it is known to be flaky
(s390x).
** Affects:
For open-vm-tools this issue will only exist with the planned backport of the
newer version.
Since we will not ship the broken backport as we found it in pre-checks the
correct state for open-vm-tools in xenial is invalid.
** Changed in: open-vm-tools (Ubuntu Xenial)
Status: Triaged => In
ubuntu@b-test:~$ sudo systemd-nspawn -D testmysql --bind /etc/resolv.conf
/bin/bash
Spawning container testmysql on /home/ubuntu/testmysql.
Press ^] three times within 1s to kill container.
Host and machine ids are equal (92544cb0ba5946158c7c4f9b57691fe3): refusing to
link journals
bash: cannot s
Installed another Xenial and Bionic in vmware to take a deper look.
- Xenial (with backported open-vm-tools): affected
- Bionic (with the interim fix reverted): no hit in several retries,
explanation below
Systemd fixed it (via our assumed implicit dependency).
In Bionic the PrivateTmp gives it a
** Also affects: systemd (Ubuntu Zesty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1736955
Title:
dep8 test systemd-fsckd fails on s
** Also affects: systemd (Ubuntu Artful)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1736955
Title:
dep8 test systemd-fsckd fails on
There are many potential affected packages I have no insight, but for
nbd this should be fixed since 1:3.14-1 by upstream now providing a
native systemd service.
That means >=Zesty should be fixed in that regard.
Not sure on backporting that - one would need to check the potential further
contex
Thanks Tom, I agree that loosing the hidden-shells seems to be a regression.
And to make the state more clear that this in the current state is considered a
an issue of accountservice or lightdm lets mark the other packages won't fix
for now. Otherwise everybody assumes "the other will do it".
T
The errors read like networking or concurrency breaking it.
I agree to have the bug to debug and improve the case.
For now I re-triggered the one hanging test on artful.
The release Team can mark dep8 tests as flaky to skip them blocking a
migration, but that would prereq an analysis of the case
s390x and arm skip the test so all green there isn't worth anything.
The others fail in ~30% of the cases I'd say:
http://autopkgtest.ubuntu.com/packages/gvfs/artful/ppc64el
http://autopkgtest.ubuntu.com/packages/gvfs/artful/i386
http://autopkgtest.ubuntu.com/packages/gvfs/artful/amd64
--
You re
*** This bug is a duplicate of bug 1707400 ***
https://bugs.launchpad.net/bugs/1707400
** This bug is no longer a duplicate of bug 1594902
Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04 64-bit
** This bug has been marked a duplicate of bug 1707400
libvirt-bin doesn't
** Tags added: triage
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1679435
Title:
GNOME Software fails to install .deb packages that trigger debconf
prompts
To manage n
Hi,
I wanted to notify that the merge of systemd version 234 fixed this bug - it is
only in proposed so far, but I checked against that.
So we can consider artful done (soon), but it would be great to consider SRUs.
** Changed in: systemd (Ubuntu Artful)
Status: New => Fix Released
** Cha
I was able to prove that this fixes my issue around libvirt-lxc loosing
containers on restart.
It could have an almost random number of other effects that are broken by it
and we don't know so I'd highly appreciate considering that fix - even for
SRU's actually.
But OTOH I need more of a system
systemd (Ubuntu)
Importance: Undecided
Assignee: ChristianEhrhardt (paelzer)
Status: New
** Affects: libvirt (Debian)
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #867379
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867379
Checking the issue that was referred shows it was handled and fixed in
1. Kernel
https://github.com/torvalds/linux/commit/37091fdd831f28a6509008542174ed324dd645bc
which is 4.6 and thereby fixed in >=Yakkety.
2. Systemd https://github.com/systemd/systemd/pull/2422 that went into systemd
230 which
> Anything else needed on src:systemd side of things?
Hi xnox,
Well, in a perfect world and with a time machine to help you could look what in
zesty's systemd fixed it to work reliably even with the suboptimal service file.
But then you have more important tasks all around you and it is fixed whe
Reported the request to pick up the PIDFile statement to Debian.
Linking up the debbug here.
** Bug watch added: Debian Bug tracker #857618
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857618
** Also affects: keepalived (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=8576
What I think is happening in our case:
Since no ExecStop= was specified, systemd will send SIGTERM [...]
Details: https://www.freedesktop.org/software/systemd/man/systemd.kill.html#
KillMode is "process" in the service file.
That means "If set to process, only the main process itself is killed."
Found more in fidonet and qmail, adding tasks.
But the more that are affected the more I think then general solution in
lightdm would be the right thing to do.
** Also affects: netqmail (Ubuntu)
Importance: Undecided
Status: New
** Also affects: fidogate (Ubuntu)
Importance: Undecid
The user Objects have an attribute for system accounts:
property Boolean SystemAccount
Whether or not the account is a system account, such as adm. System accounts
aren't returned by ListCachedUsers and should generally be ignored.
It also has a shell property, but that (by default) seems to have
** Project changed: systemd => systemd (Ubuntu)
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1594902
Title:
Failed to upgrade to libvirt-b
Adding Linux as it seems (at least) to be related to the kernel and might need
a bisect followed by a SRU for Xenial.
Also once 4.6 is ready this should be verified and closed on Yakkety.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notifi
The referenced Debian bug was about sanitizing the migration like postinst
steps.
These fixes of the systemdare in Wily and Xenial due to merges of the package.
Eventually we have to conclude that we have a new intended behavior and not
really a bug.
If you actually want the old behavior the bug
26 matches
Mail list logo
