while (and almost nobody does LTS->nonLTS).
That said I'd vote to only fix T->X.
** Changed in: clamav (Ubuntu Wily)
Status: Triaged => Won't Fix
** Changed in: clamav (Ubuntu Wily)
Assignee: ChristianEhrhardt (paelzer) => (unassigned)
** Patch removed: "debdiff for wil
)
** 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 be
modinfo zfcp; for i in {1..1000}; do echo "Try $i"; modprobe zfcp; lsmod | grep
-q zfcp && echo ok-here; rmmod zfcp; lsmod | grep zfcp || echo ok-gone; done
filename: /lib/modules/4.4.0-15-generic/kernel/drivers/s390/scsi/zfcp.ko
license:GPL
description:FCP HBA driver
author:
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
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)
Thanks Merlijn for the link.
That means that 2.3.11 is fixed which in turn means >=Yakkety is fine.
Seth, what is the security Teams position on that for Xenial now?
** Also affects: openvpn (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: openvpn (Ubuntu Xenial)
Hi,
not sure what Neutron picked up - I'll ping one from the Cloud Archive Team.
Does it even have an own strongswan or just that from the Xenial Archive I'd
guess?
For Xenial in general an SRU makes sense.
The change itself is as simple as:
Thank you Simon,
since this is "only" about silencing a warning it wasn't worth an SRU in my
personal opinion.
I can consider to wrap it up in another SRU thou and let the SRU Team decide.
The "impact" of warnigns might be too low, but OTOH the regression potential is
as well and Xenial will be
Hi,
to confirm that is patch "virsh: host: Use bitmap size in bytes rather than bit
count" right?
Assuming that I'm setting all >=Yakkety to fix Released as that was in
anything >= v1.3.4
Am I correct that you hereby requested a Xenial SRU for this fix?
** Also affects: libvirt (Ubuntu Xenial)
** Also affects: qemu (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu Yakkety)
Status: New => Confirmed
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching
Thanks, setting verification done.
** Tags removed: verification-needed
** Tags added: verification-done
** Also affects: strongswan (Ubuntu Yakkety)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह,
Also zesty has synced latest Debian which has my fix, so setting pg-
repack fixed in devel as well.
** Changed in: pg-repack (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed
According to qemu git the patches are all in >=v2.7.1
Since zesty already holds 2.8 setting status accordingly.
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: New => Fix Released
--
You received this bug
** No longer affects: postgresql-9.3 (Ubuntu Zesty)
** No longer affects: postgresql-9.3 (Ubuntu Yakkety)
** No longer affects: postgresql-9.3 (Ubuntu Xenial)
** No longer affects: postgresql-9.5 (Ubuntu Trusty)
** Changed in: postgresql-9.5 (Ubuntu Zesty)
Status: New => Incomplete
**
I found the issue in pg-repack and suggested a fix upstream as well as
to Debian.
** Also affects: pg-repack (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pg-repack (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of
Jeremy Bicha spotted that in debici 2 days ago and I chimed in there,
linking the Debian bug for what we see in the Yakkety case.
** Bug watch added: Debian Bug tracker #854997
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854997
** Also affects: postgresql via
** Changed in: qemu (Ubuntu)
Status: Triaged => 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/1656112
Title:
Power
Ok, thanks.
While I like your fix being small and simple (always good), I'm afraid of
potential side effects for an SRU e.g. systems that crash in a more severe way
because they then pass that check.
That is why I'd like to know what the upstream fix was.
What we need is somebody
** Also affects: base-passwd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: base-passwd (Ubuntu Xenial)
Status: New => Won't Fix
** Changed in: libvirt (Ubuntu Xenial)
** Also affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Zesty)
Importance: Critical
Status: Confirmed
** Also affects: qemu-kvm (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Yakkety)
** 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 नेपाली
भाषा
** 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
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
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
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
** 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
--
** 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 नेपाली
भाषा समायोजकहरुको
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
** Also affects: clamav (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/1628275
** Also affects: dovecot (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: dovecot (Ubuntu Yakkety)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, wh
Thank you for your report and your help to make Ubuntu better.
1.2.24 is already in the coming Ubuntu relase, so that is fixed there.
To consider an SRU [1] there should be some clear steps to reproduce this issue.
Did you find on your debugging a reliable way to trigger this issue so it can
be
According to the comment "I have removed the backoff timer so this
should be resolved in master." in
https://github.com/tmux/tmux/issues/298 this should be fixed in 2.3, so
zesty is fine.
** Bug watch added: github.com/tmux/tmux/issues #298
https://github.com/tmux/tmux/issues/298
** Also
Fixed in Yakkety and Zesty, since they are >=2.2
Given the impact I don't think it qualifies for an SRU - if you think it does
please feel free to do the paperwork
(https://wiki.ubuntu.com/StableReleaseUpdates) for the SRU team to review, but
I'd not expect so.
** Also affects: tmux (Ubuntu
Hi Satheera,
the issue is now fixed in Zesty (Development release) and and the Dependency a
suggest.
But there is no intention to bring that as a feature back to Xenial.
Especially since the daemon itself is only in universe I'd not consider it all
too trustworthy.
I was ok with enabling since
That is qemu commit:
commit d62d9dc4b814950dcc8bd261a3e2e9300d9065e6
Author: Fam Zheng
Date: Thu Sep 17 13:04:10 2015 +0800
vmdk: Create streamOptimized as version 3
Which is in:
>= qemu v2.6.0
So setting fixed in Yakkety, Zesty and marking it for work on a backport
to
Hi,
as I outlined before the kernel is already fixed.
E.g. if testing install from 16.04.2 there kernel in there already "tolerates"
it enough to work fine.
If that was due to the patches you referred or others I don't know. But
it is not important, as the remaining question was to fix qemu in a
Extending your already good testcase description:
# create a simple guest
$ sudo apt-get install uvtool-libvirt zfsutils-linux
$ uvt-simplestreams-libvirt --verbose sync --source
http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=xenial
$ ssh-keygen
$ uvt-kvm create
Ok, thank you all for your help in clarifying that - given that Rafael
seems to be ok as initial reporter and that IBM stated there is nothing
to do for Qemu (we know newer qemu works, so there could be something,
yet unidentified yet) I'm setting that to Won't Fix for now.
** Changed in: qemu
This is a bit too much "nobody cares on yakkety" as after the fix it will
appear as regression X->Y upgrades. Yet the fix should be just the same, but
sponsors should mind that.
Jorge would you ack that the same should go to Yakkety or are there reasons not
to be seen too obviously that speaks
** Also affects: systemtap (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemtap (Ubuntu Yakkety)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to
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
Given that is only prevents an uncommon user-error I set the older
releases to Won't Fix.
Please if you really think this is SRU worthy please get in touch and
help me preparing a matching SRU teamplate that would convince the SRU
Team.
... Tests still running but so far looking good.
**
I agree, and in fact I've come to this error a few times in several crash
reports and it always ended up with "sorry, config issue likely too few memory".
Please do mind that there were a few cases where this triggered without really
being OOM.
For the option to be set - not only for
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."
On Zesty (still without the pidfile in the service) it seems to work
fine (Version 1:1.3.2-1).
Test:
2x zesty KVM guests
sudo apt-get install keepalived
Set up as above, but with ens3 (virtual ethenet device).
I think the name of backup/master conf names are interchanged in the
example above,
** Changed in: qemu (Ubuntu Xenial)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
** Changed in: qemu (Ubuntu)
Status: In Progress => Fix Released
** Description changed:
[Impact]
- * Some newer Power8 derivates fail to work correctly e.g. Power S822LC
- (83
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
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
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
** 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
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
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
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
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
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
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
That means it is fixed in Yakkety and later, and not Broken in Trusty
yet as the feature is not in.
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: New => Fix Released
** Changed in: qemu (Ubuntu Xenial)
Confirmed: Fixed in Zesty, still broken in Yakkety
** Also affects: nmap (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: nmap (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: nmap (Ubuntu)
Status: New => Fix Released
--
You
At least from the source containing the assert, this could go back to
Trusty.
** Also affects: squid3 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: squid3 (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: squid3 (Ubuntu Trusty)
Hi Thomas thank you for your report and your help to make Ubuntu better.
I found the associated change at:
https://pagure.io/SSSD/sssd/c/fcbcfa69f9291936f01f24b5fcb5a7672dca46f3
That fix is in version 1.14 which means that Ubuntu Zesty and later are already
fixed.
Adding a bug task fro X/Y -
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 नेपाली
भाषा
** 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.
I'm only now reading into details, but in general just taking 5.5.1 can be a
backport but not easily an SRU.
We have to check if there is a way to find a minimal amount of changes to SRU
them.
** Also affects: strongswan (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also
I checked and this is in 2.6.1 via a backport as [1] not as the original
[2].
But that means >=Yakkety is good and Xenial/Trusty are bad since the related
Security SRUs.
Updating bug tasks accordingly.
[1]:
http://git.qemu.org/?p=qemu.git;a=commit;h=7ff5dc445d6bb392f9fb3d0a254ef9071304780b
portance: Undecided => Low
** Changed in: qemu (Ubuntu Xenial)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
** Changed in: qemu (Ubuntu Yakkety)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
** Changed in: qemu (Ubuntu)
Status: New => Fix Released
** T
- Added and filled associated SRU Template
- checked once more the dep8 tests on the test bileto ppa
- checked regression tests
- added tasks for affected releases
With that in place uploaded to the unapproved queue of these releases
Please do note that Trusty is a bit old for the SRU as-is,
> 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
** 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
** Also affects: postgresql-9.3 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: postgresql-9.3 (Ubuntu Trusty)
Status: New => Fix Committed
** No longer affects: postgresql-9.3 (Ubuntu Xenial)
** No longer affects: postgresql-9.3 (Ubuntu Yakkety)
** No longer
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:
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
**
** 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
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)
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
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 =>
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
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
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
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:
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
I realized we carry this as Delta and there was no Debian report yet, I
opened one and linked it up here.
** Bug watch added: Debian Bug tracker #861727
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861727
** Also affects: ntp (Debian) via
I wasn't awake this morning it seems (or did to omuch at once), so I beg
your pardon and resummarize.
Also I had the chance to try the fs forwarding on a zestyl level
libvirt/qemu and it worked fine.
- The /srv/video rule obviously is just the case reported for a share that
exports this source.
Keeping Development open (waiting for statements on 17.10/18.04) but
denying the Xenial/Zesty tasks according to c#10
** Changed in: apache2 (Ubuntu Zesty)
Status: Confirmed => Won't Fix
** Changed in: apache2 (Ubuntu Xenial)
Status: Confirmed => Won't Fix
--
You received this
** Also affects: vlan (Ubuntu Artful)
Importance: Medium
Assignee: Dan Streetman (ddstreet)
Status: In Progress
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
** Changed in: libvirt (Ubuntu Yakkety)
Status: Confirmed => Won't Fix
** Changed in: libvirt (Ubuntu)
Status: Confirmed => In Progress
** Changed in: libvirt (Ubuntu Zesty)
Assignee: ChristianEhrhardt (paelzer) => (unassigned)
--
You received this bug notificatio
** Changed in: postgresql-9.5 (Ubuntu)
Status: Triaged => Fix Released
** Changed in: postgresql-9.6 (Ubuntu)
Status: Triaged => Fix Released
** Changed in: postgresql-9.3 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a
Thanks for coming back to this Kelvin.
I must admit I lack the TPM setup and in depth knowlegde to confirm or
deny if there is still something missing, but it sounds like it - either
that or a setup issue I don't know about.
Good to hear that at least this particular bug here is fixed as
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
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
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
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
I'm passing through old bugs, lacking further discussion and any
"forcing" argument why that would be needed in Xenial (which would be
feature enablement in SRU, so that would have to be a very good
argument) I'm closing the Xenial task to clean up.
Also if needed users have the option to get
Hi, sorry but since I can't reproduce (even without the ppa to test) I can't
continue on a fix for now.
Please come back once you found the time to check
1. the ppa I provided for your case (since there are newer versions you need to
force install that version from the ppa [1])
2. On the error
Lacking feedback on how real the case is to make a compelling SRU statement for
the SRU Team.
Please see my comment #4 and reply with the details needed to make a SRU
possible.
Until that was provided I set this back from incomplete to invalid (no
offense, consider it a timeout on the
** Changed in: qemu (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/1589923
Title:
Hi,
I'm currently cleaning out the tracking on dormant qemu/libvirt bugs.
On this one I'm still waiting for a check on newer vmware to make a
valid case for SRU (still reproducible) or consider it solved due to
other updates (in vmware in this case).
Lacking the feedback I'll consider the
Hi,
I'm checking bugs dormant too long to update their tracking.
On this one I highly appreciate the report and the fixing we did in zesty (and
later is done due to it being upstream) - it is ok to change that on a new
release which zesty was.
But as outlined in comment #4 SRU'ing it would be
1 - 100 of 172 matches
Mail list logo