Regression tests good as well, moving it to x-unapproved for the SRU Team to
consider.
=> qemu_2.5+dfsg-5ubuntu10.25_source.changes
** Changed in: qemu (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: qemu (Ubuntu)
Status: New => Fix Released
--
You received this bug
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: qemu-linaro (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenia
That means our assumption taken in comment #63 that it was fixed in
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=014628a705bdaf31c09915
either was wrong (unset fix released) - or this is a similar but not the
same issue (which would imply a new bug since this already has plenty of
potentially mis
Submitted upstream as https://www.redhat.com/archives/libvir-
list/2018-April/msg01408.html
** Changed in: libvirt (Ubuntu)
Status: New => In Progress
** Also affects: libvirt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Bionic)
Importanc
bug 1758428 unlocked, it's fix is on the way into Bionic.
Once that completes I can propose the changes as prepared to Artful and Xenial.
** Also affects: open-vm-tools (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: open-vm-tools (Ubuntu Artful)
Status: New => I
** 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
** Also affects: open-vm-tools (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: open-vm-tools (Ubuntu Artful)
Status: New => Triaged
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Ma
Ok, I can confirm the ppa fixing this case.
And OTOH it is fixed in qemu >=2.7.
Furthermore the change is very small and easily reviewable (essentially
only changing a malloc to a malloc0 to initialize properly).
I'm marking the tasks accordingly and prep this as an SRU.
** Also affects: qemu (U
Given the current Final Freeze for 18.04 this will (if done) have to be an SRU
for 18.04 as well.
I just did the initial triage, but will leave it for the screener team to
ensure it is as needed.
** Also affects: libguestfs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lib
Thanks Falstaff, yeah we knew the fixes are in latter releases - they just were
hard to backport keeping the general regression risk low (for all other users).
UCA as you used it is a valid way to get fixes ahead of time into last LTS,
Thanks for verifying this again falstaff.
@bestpa - sad to h
Hi,
sorry for chiming in so late, but I haven't seen this issue before - the last
update changed that.
Special chars as reported in comment #26 and comment #15 are an issue, but most
of them are fixed or at a better error message now.
First of all since Ubuntu 17.10 (~=UCA-Pike) all files in gen
** Changed in: postgresql-10 (Ubuntu Bionic)
Status: Triaged => Fix Released
** Changed in: postgresql-10 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matchin
Regression- and Case-Tested once more from a ppa and being good.
Also pushed to ubuntu libvirt-maintainers git as a new cosmic-4.0 branch
Uploaded to Cosmic and completed, now considering SRUs.
** Also affects: libvirt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: l
Per Debian fix in 5.1.2-1
"AFAIKS, autofs is providing a .service now with an After=sssd"
This is in Ubuntu as of Zesty.
I'll mark the tasks accordingly.
Adding the service in Xenial in general might have too much risk to cause other
regressions - not sure thou - I beg your pardon - this is just
Hi Laz,
thank you for your report.
Thanks for the log, I mostly looked at the condensed version like:
$ awk '/iscsiadm/ {gsub("[0-9]*: debug : virCommandRunAsync:2429 :","");
gsub("+",""); gsub("^2017-12-18 ",""); print $0}' 20171218-libvirt.txt |
pastebinit
=> http://paste.ubuntu.com/262141
You'd add [2] and always take packages from there non selectively.
So normal add-apt-repository and after that just update/upgrade as usual
according to your maintenance policies.
I'd say that while libvirt/qemu can break things I'd have very rarely seen
those to manifest as system instabilities
While I see the non-crit "other" issue with opening its own binary I can
not confirm the disconnected path issue in a current xenial guest.
Since we knew this appears when trigging the running service to emit an error
message I tried to force such an error message. I knew on later releases I
cou
I think I found it, the check to:
if `dpkg --compare-versions "$2" lt 3.1.0-1~`; then
has no else clause that we could hit.
But by checking more in Detail I realized that this version check is not in all
releases.
It was added in 3.1.3-1 and thereby is in all releases.
It is in Zesty and later
Hi Brian,
these versions are actually already in Artful and Bionic.
Given the time you opened this you found that on Xenial I'll add a task for an
SRU.
@Andreas - you look at bind fixes every now and then - how about to
include this on your next run?
** Also affects: bind9 (Ubuntu Xenial)
Imp
** Changed in: spamassassin (Ubuntu Trusty)
Status: Confirmed => Triaged
** Changed in: spamassassin (Ubuntu Xenial)
Status: Confirmed => Triaged
** Changed in: spamassassin (Ubuntu Zesty)
Status: Confirmed => Triaged
** Changed in: spamassassin (Ubuntu Artful)
Status
This actually doesn't affect T/X as the pearl there is older and does not
complain.
Thanks Ahasenack for spotting this before I started to build all the test ppa's!
** Changed in: spamassassin (Ubuntu Xenial)
Status: Triaged => Invalid
** Changed in: spamassassin (Ubuntu Trusty)
St
Thanks for identifying the changes, both changes are in since 2.6 so I'm
first marking the bug tasks accordingly.
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: qe
Hi Heinz-Werner,
thanks for the ping.
I think we agreed back then that the config itself is a Ubuntu wide
thing - but I haven't seen any discussions on procps or in general to
lift it. But then as I outlined in comment #7 any limit can be too low.
I'll set the KVM task to won't fix to clearly mark
Since all upgrades will go through LTS->LTS paths at least that should be good
now in general.
I don't see a need to fix other ubuntu releases (I might miss some).
So instead of "In Progress → New" I'll set Fix Released.
@Andreas - if I miss why this needs a change in other versions please
expla
there is /etc/defaults/chrony in later versions of it.
But even that is no more working since the native systemd service does not
consider it.
I might take a look into this for 18.04 to be correct, but atm I have no plan
to do so for 16.04.
You might take a look at later Ubuntu releases and take
** Bug watch added: Debian Bug tracker #889012
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889012
** Also affects: chrony (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889012
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Also affects: libvirt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Status: New => Fix Released
** Changed in: libvirt (Ubuntu Xenial)
Status: New => Triaged
--
You received this bug notification because you are a member of नेपाली
भ
Hi Tony,
yeah this is so far only fixed in Bionic (18.04) onwards.
It it not really an issue other than a log message itself (it is not needed for
the opt parsing).
It occurs "only" on NTP start/restart (since it is arg parsing) so it is not
that frequent that it would fill up the log or similar
Missed the right format in changelog :-/, but this is fixed in Bionic by
https://launchpad.net/ubuntu/+source/ntp/1:4.2.8p10+dfsg-5ubuntu7
** Changed in: ntp (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको
** Package changed: postgresql-9.5 (Ubuntu) => postgresql-common
(Ubuntu)
** Also affects: postgresql-common (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: postgresql-common (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: postgresql-common
Correctly added a bug task for ntp to also be affected.
Dropping Artful (EOL)
** Also affects: ntp (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: apparmor (Ubuntu Yakkety)
** Changed in: apparmor (Ubuntu Xenial)
Status: New => Triaged
** Changed in: ntp (Ubunt
Bionic - ok
SRU Template - ok
Debdiff for X/T checked - ok
Tested A upload from ppa - ok.
(This issue in particular doesn't apply to Xenial, so dropping this task)
** No longer affects: ntp (Ubuntu Xenial)
** Changed in: ntp (Ubuntu Artful)
Status: Triaged => In Progress
--
You received
** Changed in: apparmor (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: tor (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu
** Also affects: open-vm-tools (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: open-vm-tools (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: open-vm-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: open-vm-
Note: since 5.7.3+dfsg-1.4 a native systemd file is used which uses type=simple
and MAINPID tracking.
So >= Artful this is already fixed.
Setting the status to fixed, but adding a Xenial task as there the issue
still exists.
** Also affects: net-snmp (Ubuntu Xenial)
Importance: Undecided
Passing haproxy bugs after the latest stable 1-8 has landed in Ubuntu 18.04.
This bug is old and I agree with the former comment - setting states.
** Also affects: haproxy (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: haproxy (Ubuntu Precise)
Importance: Undecide
Thanks Tobias for all the tests.
With all that prep done I'll try to push it to SRU review now.
** Changed in: apache2 (Ubuntu Trusty)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to X
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
** Changed in: postgresql-10 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1730661
Tit
Thanks for the report Pooja,
this is fixed in v1.3.5
By that this in anything newer than Xenial via being upstream.
I need to take a look at backporting the suggested change to Xenial, but
that will probably not happen this week as I'm traveling.
** Also affects: libvirt (Ubuntu Xenial)
Impo
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
Thanks for the ping on this lnog standing bug @Tronde.
I updated the state accordingly.
If there is a change to be identified since Xenial->Bionic one could try to SRU
fix it in Xenial.
But I took a (quick) look and found nothing obvious.
There are major changes like going from sysV init in /etc/
Thanks Dariusz,
TL;DR we want this to be cancelled from SRU and need to rework upstream.
>From there into Bionic (which would be released that way) and from there
>reconsidering SRU.
Resetting Task status and verification tags.
** Tags added: 4.0.0-1ubuntu6 needs-upstreaming
** Tags removed: ve
** Also affects: open-vm-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: open-vm-tools (Ubuntu Xenial)
Status: New => In Progress
** Changed in: open-vm-tools (Ubuntu)
Status: Triaged => Fix Released
** Changed in: open-vm-tools (Ubuntu Xenial)
I
The way the newer versions solve this is to have a native systemd
service and in there there is:
Conflicts=systemd-timesyncd.service openntpd.service
That ensures only one of these can be started.
Xenial has no systemd service at all, it has sysV and uses the systemd
generator.
So there is no "
I think you are right here, not sure what happened to the triager of
march 14th.
23 is in Artful and Bionic already.
So the question here is to backport via an SRU to Xenial
** Also affects: psmisc (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: psmisc (Ubuntu)
Nice, thanks for the update.
I checked a few recent logs and agree that the message is gone since 2.9
Some might still encounter slow guests (for other reasons) and trigger
the message, but the most common TCG emulation case is solved by this
since Artful and later.
I think we don't want to backp
Since this fix is in 2.6 is is in >=Yakkety, so nonly considering Xenial
for the SRU
** Also affects: qemu (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Xenial)
Impor
Since the fix is in 2.9 only Xenial is considered for the SRU as
>=Artful is good
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu Xenial)
Status
)
** Changed in: dovecot-antispam (Ubuntu)
Status: New => Triaged
** Changed in: dovecot-antispam (Ubuntu)
Importance: Undecided => Medium
** Changed in: dovecot-antispam (Ubuntu)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
--
You received this bug notification because
Hi Michael,
this seems to confuse people regularly, so instead of just answering questions
as last time I went over the whole bug again to summarize. Thanks for being
persistent pitti and mwhudson!
TL;DR
please unsubscribe sponsors and SRU Verification
Summary:
Upstream DPDK & Openvswitch (and
Fixed in Yakkety already due to being fixed in >=1.4.0-8 (Yakkety is at
1.4.0-9).
** Changed in: pptpd (Ubuntu)
Status: Triaged => Fix Released
** Changed in: pptpd (Ubuntu Xenial)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
** Changed in: pptpd (Ubuntu)
Hi,
just to note I'd consider this not important enough for an SRU given the fact
that it is a very rare case and people can add the rule themselves if the need
to.
** Changed in: ntp (Ubuntu Xenial)
Status: New => Won't Fix
--
You received this bug notification because you are a member
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu Xenial)
Status: New => Triaged
** Changed in: qemu (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: qemu (Ubuntu)
Status: Triaged => Fix Released
--
You re
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu Xenial)
Status: New => Triaged
** Changed in: qemu (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of नेपाली
भाषा
I backported this and tried my tests again, but this alone isn't sufficient to
get the T->X->T working (which is effectively 2.0->2.5->2.0).
Wily (2.4) is already out of service, so setting this to won't fix.
Thanks for your guidance, but that now properly known I'll set the
Xenial task to won't
** Also affects: awstats (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1585121
T
** Also affects: ntp (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: ntp (Ubuntu Xenial)
Status: New => Triaged
** Changed in: ntp (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: ntp (Ubuntu)
Status: In Progress => Fix Committed
--
You
Unfortunately still no update on Debian including the fix.
But given that there is a workaround (place the file yourself) and this
bug (unfortunately) being very old but didn't get a huge crowd being
affected it is not reasonable to push a delta for that IMHO.
Also after a further check we'd have
ntu)
Assignee: ChristianEhrhardt (paelzer) => (unassigned)
** Changed in: dovecot-antispam (Ubuntu)
Assignee: ChristianEhrhardt (paelzer) => (unassigned)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
)
** Changed in: libvirt (Ubuntu)
Status: New => Fix Released
** Changed in: libvirt (Ubuntu Xenial)
Status: New => In Progress
** Changed in: libvirt (Ubuntu Xenial)
Importance: Undecided => Low
** Changed in: libvirt (Ubuntu Xenial)
Assignee: (unassigned) => Chris
** Changed in: ntp (Ubuntu)
Status: Triaged => Won't Fix
** Changed in: ntp (Ubuntu Xenial)
Status: Triaged => Won't Fix
** Changed in: ntp (Ubuntu Xenial)
Importance: Undecided => Low
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको सम
Since we merged 5.5 in zesty it was forgotten to mention it being fixed
for a while.
** Also affects: strongswan (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: strongswan (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: strongswan (Ubuntu
Fixed in >=2.7 and thereby >=Zesty.
Needs to be considered for SRUs now.
** Also affects: qemu (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: Triaged => Fix
Thanks a lot, I tagged this up as it was dormant for too long.
I hope I get to this rather soon as I wasn't aware at all so far.
In the other bug there was some mentioning of a newer windows release fixing it
(if on qemu 2.6.1).
If one could check that for this bug as well but on 2.5 that would b
Per former comment by Rickard we can consider Dev fixed, yet one might
want to look into Xenial.
** Also affects: debian-installer (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: syslinux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: g
Since Fedorahosted died this is the new link:
https://github.com/SSSD/sssd/commit/afec2ab750a453c592397f6775ec091e894d89b9
** Also affects: sssd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: sssd (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Chang
** Changed in: net-tools (Ubuntu Trusty)
Status: New => Won't Fix
** Changed in: net-tools (Ubuntu Xenial)
Status: New => Won't Fix
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions
Updated are so rare that we better fix this as-needed on any next
update, also it is ok in latter versions - therefore marking
appropriately and unsubscribing ubuntu-server.
** Also affects: nis (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: nis (Ubuntu Xenial)
I
I'm clearing out bugs that were dormant for too long.
This was fixed upstream in 1:4.0.0~rc1-1, that is already in Zesty and later.
So this is about fixing it in Xenial/Yakkety which is on 3.9.7
I beg your pardon this idled so long, but we'd need some help for the SRU.
Especially how to reprodu
In the upstream issue 673 [1].
Upstream removed some ciphers and ordered the others by preference.
That is fixed in >=Yakkety then.
@Seth - do you think we want/need to backport that change to Xenial?
[1]: https://community.openvpn.net/openvpn/ticket/673
** Bug watch added: community.openvpn.n
Discussed:
https://github.com/fish-shell/fish-shell/issues/2292
Fixed in:
https://github.com/fish-shell/fish-shell/issues/150
So TL;DR it was more seen as an issue in fish and should work in recent
versions of fish now.
Reassigning to fish due to that.
The discussions and fixes in fish are very
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
Also in general the whole thing around the socket got removed.
So the old issue:
Failed to stop clamav-daemon.socket: Unit clamav-daemon.socket not loaded.
Should be fixed indirectly by:
0.99.2+dfsg-3
* Drop support for clamav-daemon.socket. Should avoid restart loops if clamd
crashes o
Yeah Jamie, thanks for the status update - absolutely right for apparmor
(ubuntu).
Yet - at least I - have no idea what to backport in regard to provide debdiffs
in that case.
I would have hoped you(r team) would know what that was about in particular and
might have discussed/considered/rejected
** Also affects: dovecot (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: dovecot (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: dovecot (Ubuntu)
Status: New => Fix Released
** Changed in: dovecot (Ubuntu Xenial)
Status: New
Yeah we can, kernel had the fixes a while now.
It was a bit complex in this case as we had fix A, fix B and all 4 combinations
thereof.
Thanks Jeff!
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Release
Hi,
I beg your pardon that nobody found the time to look at this since I initially
triaged it.
Especially since here even a suggested fix was provided we want to encourage
and help.
I'm currently trying to clear out bugs that are dormant for too long, so lets
take a look.
Status on the checked
As a sync would be preferred for 1. of comment #5 I did:
- Poll Debian on the status of the release of the already queued changes [1].
- Link the Debian bug up here and waiting for a reply now.
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868007
** Bug watch added: Debian Bug tracker #8
I don't even know how much pardon to beg on this one ... a lot for sure.
I'm coming by trying to clear bugs that are dormant for too long - and this one
is really way too long :-/
Anyway forget the past and work on it ...
Now this is fixed in Zesty and later due to merging 2.7.4.
Updating tasks
The fix for 805167 is in Yakkety.
We need to consider that as an SRU for Xenial.
** Changed in: nis (Ubuntu)
Status: Triaged => Fix Released
** Changed in: rpcbind (Ubuntu Xenial)
Status: Confirmed => Triaged
** Tags added: server-next
--
You received this bug notification becaus
As nis needs no change set that to invalid.
** Changed in: nis (Ubuntu Xenial)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bug
Referred change is upstream in Libvirt 3.2, so assuming that is fixed.
But check on X-Z SRUs
** Also affects: libvirt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Y
** Also affects: qemu (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matc
Hi yuanzhicao,
thank you for your report and your analysis to a suggested fix.
The fix you refer to was released in 1.3.2, setting later releases to
fix-released.
In general Libvirt's lxc support is not of focus, I'd highly recommend
using lxd for system containers which is far more stable in my
crash is in 7.1.7 whichi is in >= Zesty so dev is good
** Changed in: crash (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: crash (Ubuntu)
Assignee: Nish Aravamudan (nacc) => (unassigned)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजक
Change is in >=v2.3.0 which makes this Fix released for a while.
Lets add and consider SRU from there.
** Also affects: libvirt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Status: New => Fix Released
--
You received this bug notification be
Hi Jorge,
thanks for your prep work on this.
Checking prereqs.
#1 fixed in Dev?
I read the "there is a patch" before as "there is a -new- patch", but checked
now.
This is in since version 3.2 which makes it fix released in Artful already.
While I work on 3.6 we don't need it to go on with this as
Hi,
the sync [1] of a mongodb set this to fix released quite a while ago, but in
fact it fails to build on arm64 [2].
To make things less debuggable, the build issue seems to be a hang, killed by
builders timeout and not a clear "error: foo is wrong".
I was "encouraged :-)" [3] for my s390x expe
** Changed in: nut (Ubuntu Yakkety)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1540008
Title:
USB p
That is what happens when bugs are dormant for too long :-/.
It still seems to be an issue for Trusty, but you are right without the ability
to reproduce we should cancel that bug here from the Xenial SRU.
I have to redo it anyway for Xenial as there is an FTBFS in the fix (that is
the reason you
Public bug reported:
Update to the new set of releases as per the standing micro-release
exception these should land in stable Ubuntu releases.
Curren versions in releases:
postgresql-9.3 | 9.3.18-0ubuntu0.14.04.1 | trusty-security | source, amd64,
arm64, armhf, i386, powerpc, ppc64el
postgres
** Also affects: nzbget (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: raphael (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: nzbget (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: raphael (Ubuntu Xenial)
This bug was fixed in the package postgresql-9.6 - 9.6.5-1
---
postgresql-9.6 (9.6.5-1) unstable; urgency=medium
* Team upload.
* New upstream version.
-- Christoph Berg Tue, 29 Aug 2017
12:15:37 +0200
** Changed in: postgresql-9.6 (Ubuntu)
Status: Triaged => Fix Relea
- Taking a Xenial and a Artful VM
- Installing ntp
- Check status of ntp
- running fine on both systems
- Reboot the VM
- Check status of ntp
- still ntp service ok on both systems
- install ntpdate
- Check status of ntp
- still ntp service ok on both systems
- reboot
- Check status of ntp
Removing the last uncertainties, the related Debian bug being fixed fixed it in
sysv init.
That now has:
LOCKFILE=/run/lock/ntpdate
It has so e.g. in Artful.
And thereby we considered being fixed as well after merging that.
But versions >= that also have the systemd wrapper which doesn't lock a
Given the (no) feedback and the fact that this actually is not part of
the virt cpu the old request is won't fix. Furthermore I spawned a task
to remove the patches that did add it in the past.
TL;DR:
- intentionally not enabled/added upstream
- long gone with a very low amount of people missing i
This bug was dead for quite some time, but the issue still exists for Trusty
(were we could take the supposed change) and we have to check the systemd cases
in >=Xenial.
Adapting tasks and will come back once I tested on >=Xenial.
** Also affects: libvirt (Ubuntu Zesty)
Importance: Undecided
To check on the systemd case I picked a rather slow system and spawned 30
guests.
I set all those to autostart and then shut them down.
Starting them sequentially as well as concurrently takes about ~20
seconds.
/var/run/libvirt/libvirt-sock is gone after the service is stopped.
With the follow
Changed the order of status and list to get it even better while testing on
Xenial.
Also the system was even slower which is good I think (for the test).
So things are good on Xenial onward (with systemd).
$ sudo ./test-restart.sh
+ date
Mi 6. Sep 09:03:35 UTC 2017
+ sudo systemctl start libvir
1 - 100 of 180 matches
Mail list logo
