/etc/ssh/sshd_config: No such file or directory
This file is essential to ssh, if you have deleted it the service won't work.
That means you either have to remove the service or re-fix it's configuration.
To restore that you can find a default in /usr/share/openssh/sshd_config
--
You received t
As Daniel asked in [1] making this abug report against Qemu (upstream).
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1568939
** Bug watch added: Red Hat Bugzilla #1568939
https://bugzilla.redhat.com/show_bug.cgi?id=1568939
** Also affects: qemu
Importance: Undecided
Status: New
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time w
Ubuntu task is not actionable until we settled on how to change the
parsing code for long strings upstream, so I set it to confirmed but
wishlist (until we know what size a patch - or actions a recommendation
on handling differently has).
** Changed in: qemu (Ubuntu)
Status: New => Confirme
Thanks Matt, yeah we actually had no similar report in all the time.
It is unclear to me if there still is something needed in the kernel, but it is
unclear which (if any) qemu change needs to be done as there is no external
reproducer.
It is good to hear that in your case after working heavily i
I re-deployed one of my systems to Xenial.
For the complexity of going back I took what kernel is currently active which
was 4.4.0-224
With that I spun up the Xubuntu 32 bit iso you referred.
For the sake of completeness I also did the same on 4.15.0-20-generic
(also with newer qemu of bionic).
SRU test builds and tests from PPA worked, pushed for SRU review to
X/A/B-unapproved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758037
Title:
LTC Test- Ubuntu18.04: Starting the guest with netw
*** This bug is a duplicate of bug 1741390 ***
https://bugs.launchpad.net/bugs/1741390
Interesting - thanks for the check, in that case I'll mark this bug as a
dup as your issue will then be solved by the backport we are working on.
** This bug has been marked a duplicate of bug 1741390
Pl
The Upload was also tested by the reporter against another bug that will be
fixed by the backport.
So I dup'ed 1668244 onto this bug here.
+1 on the backport adressing more issues :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
*** This bug is a duplicate of bug 1764314 ***
https://bugs.launchpad.net/bugs/1764314
Hi Daniel,
thanks for your report.
The issue that libvirt can't "see" all devices existed quite a while actually.
Whatever you have through networkd or NetworkManager was invisible.
This is due to netcf bei
This bug was fixed in the package libqb - 1.0.3-1
---
libqb (1.0.3-1) unstable; urgency=medium
[ Christoph Berg ]
* [3e6a1ea] Remove Richard and myself from Uploaders
[ Ferenc Wágner ]
* [2dbb472] Update old style gbp.conf section names
* [c566381] New upstream release (1.0
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
There already was an upload ongoing, but I need to group bug 1758037 on the
same run and need to set new branches. ... Integrated that now.
Regression- and Case-Tested once more from a ppa and being good.
Uploaded to Cosmic - and it already completed.
Also pushed to ubuntu libvirt-maintainers git.
Test builds in the referred PPAs are all good.
Need some more tests as usual on the MRE for confidence, but other than that
all looks good atm.
** Summary changed:
- MRE Prep
+ New upstream microreleases 9.3.23, 9.5.13, 9.6.9 and 10.4
** Information type changed from Private Security to Public
Xenial is at 1.2.6p12-1ubuntu0.16.04.1 and later release are even newer.
This is still true for Trusty so I flagged it that way.
** Also affects: check-mk (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: check-mk (Ubuntu)
Status: New => Fix Released
--
You recei
Hi Adrian (after a long time),
I came by clearing or reconsidering old bugs.
Checks are at /usr/share/check_mk/checks
Docs for them are
/usr/share/check_mk/checks-man
Both are part of check-mk-server package.
The default in the tool is in /usr/share/check_mk/modules/check_mk.py
check_manpages_di
1. Upgrade from proposed
Binaries usually installed are open-vm-tools and open-vm-tools-desktop
I see 10.2.0-3~... in Xenial and Artful, checking if the upgrade works without
issues.
On the upgrade one sees a list of new dependencies libdrm2, libudev,
libxml2 libxmlsec1 libxmlsec1-openssl pciutil
1. Upgrade from proposed - this is the same for all associated bugs, so
I only documented details in bug 1741390
2. This bug in particular
Running a few restarts and checking
$ systemctl status -l open-vm-tools.service
This checks if the service rules avoid the issue on these systems with older
s
1. Upgrade from proposed - this is the same for all associated bugs, so
I only documented details in bug 1741390
2. This bug in particular
While triggering the raw error throu VMOMI API is complex one can check the
services mountpoints.
E.g. with that we see the issue present in Artful before thi
Started tests for a Cosmic upload and added SRU Template.
** Description changed:
+ [Impact]
+
+ * nwfilters were not usable if configured to use dhcp based learning
+
+ * Fix by backporting upstream bug
+
+ [Test Case]
+
+ * Add the following to the interface section of a guest descriptio
Thank you so much Richard!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404396
Title:
[regression] vgabios -> seabios breaks (my) 16-bit applications
To manage notifications about this bug go to:
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
FYI - loop was enabled even longer and ipc was enabled in Feb 2017
1.0.1-1ubuntu1
Currently a sync is in progress which will enable the last test being log that
now works as well, but for the scope of this bug description things are already
fixed.
** Changed in: libqb (Ubuntu)
Status: Tr
I think we are fine doing that change >=Cosmic if we can confirm it is
working now. We have no regression that would make us need a SRU, this
is more a request to simplify maintenance and get in sync with upstreams
defaults again if they are ok now.
I really appreciate your help and your self-reli
Hmm,
so it is not even burning CPU for anything neither in the Host (usr ~=qemu, sys
~=kernel) nor in the guest itself (~=guest).
The KVM exits confirm that, it doesn't do a a lot entry/exit is the pass in/out
of guest context and the only meaningful exit means it emulates an instruction.
So if
Filed a bug in Debian for the netcf Dependency going forward, linked at
the bug tasks.
** Bug watch added: Debian Bug tracker #898194
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898194
** Also affects: libvirt (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898194
Im
We had a discussion on this:
I have to beg your pardon for all of the Ubuntu community, but we never
intended to support write-managing through libvirt in Bionic. Libvirt iface-*
never supported networkd or NetworkManager. To manage networks with different
backends there is netplan.io.
Adding a
*** This bug is a security vulnerability ***
Private security bug reported:
Postgresql stable update
Current versions in supported releases:
postgresql-9.3 | 9.3.22-0ubuntu0.14.04 trusty
postgresql-9.5 | 9.5.12-0ubuntu0.16.04 xenial
postgresql-9.6 | 9.6.8-0ubuntu0.17.10 artful
postgresql-10
This is all of such a long time ago, I've read through the old Mail threads and
seabios git.
As far as I can tell this would still be an issue.
I'm a bit concerned we carry this Delta along like forever.
To have some hope resolving that I wanted to ask you @Richard if you could
still retest it w
This was regression tested already, it was tested by the STS engineer workign
on it and we have postive feedback on a affected user - furthermore the former
SRU now cleared on last Friday.
>Xenial releases are not affected (So no need to think on other releases) and
>the change to Xenial LGTM.
On Tue, May 8, 2018 at 10:37 AM, Dr. David Alan Gilbert wrote:
> * ChristianEhrhardt (1769...@bugs.launchpad.net) wrote:
> > > Interesting; I thought this was supposed to work.
> >
> > Exactly that was my thought when triaging it initially
> > Furthermore I ass
Public bug reported:
Without this some autopkgtests break (even the default version is 10 and
correct which makes the test work) as it emits messages on STDERR.
This is filed as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898166
And already accepted as
https://salsa.debian.org/postgresql/p
1.190-2 is in cosmic-proposed, but right now some tests still fail for
18.10/Cosmic not being fully open (e.g. no autotest/cloud images or missing
18.10 in postgres common.
So I have to beg your pardon to wait a bit more :-/
--
You received this bug notification because you are a member of Ubun
Thanks Andreas for the ping, yes the update will include the upstream fix [2]
to this bug as well.
If it fixes the issue of the reporter I'm not 100% sure. The reason for that
uncertainty is [1] which mentions the rule changed but not working for some on
the Fedora bug.
I'd want to keep this se
Thanks Andreas for the ping, yes this update will include the upstream fix to
bug 1668244 as well.
If it fixes the issue of the reporter I'm not 100% sure, but I'll update and
subscribe to the other bug if not. We really don't need another unrelated bug
stopping this backport :-)
Actually we on
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/libqb/+git/libqb/+merge/345212
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1239109
Title:
aarch64 clock_gettime wit
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/nss/+git/nss/+merge/345213
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747411
Title:
Change of default database fil
Yeah, forgot to update this one - thanks Stefan for catching this!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717790
Title:
libibverbs should come from the rdma-core source package
To manage no
This very very likely was fixed a long time ago, but I wanted to be sure.
So I used this simple test program:
#include
#include
#include
#include
void timespec_diff(const struct timespec *start, const struct timespec *stop,
struct timespec *result)
{
if ((stop->tv_nsec
Actually lets close libqb with the sync then (when the Delta is
dropped).
** Changed in: libqb (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1239109
Ti
Corosync is actually a sync for Cosmic, with all Delta dropped:
* Merge with Debian unstable (LP: #1747411). Remaining changes:
* Dropped Changes:
- Properly restart corosync and pacemaker together (LP: #1740892)
d/rules: pass --restart-after-upgrade to dh_installinit.
(th
For corosync the affected components are corosync-qnetd.
I checked and without adaption on install they would be fine as they
initialize a new DB and nowhere does anyone specify the type. But as
with some other tools on an upgrade we have to assume that the old DBM
format will be tried to be read
Yeah this is a sync now, thanks for spotting - setting fix released.
** Changed in: ipset (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710077
Title:
> Interesting; I thought this was supposed to work.
Exactly that was my thought when triaging it initially
Furthermore I assume people working la57 (https://lwn.net/Articles/730925/) and
such ran tests on much bigger sizes.
> Ah right Dan, if you're seeing the 40 bits physical in the guest you
d
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since there isn't enough information in your report to differentiate
between a local configuration problem and a bug in Ubuntu, I'm marking
this bug as Incomplete.
If indeed this is a local configuration problem,
Hi Nur,
that is odd the handling is as following.
In the past there was a group libvirtd - new packaging in Debian and
Ubuntu renamed that to libvirt but the install handles that.
In case of a new install you would have those groups for libvirt:
libvirt:x:132:paelzer
Hi Ayslinn,
thanks for your report.
The users are actually only tried to be removed as there might be e.g. running
processes or files of them. But it is not an issue if they stay behind, so
normally this would be on install -> purge.
Removing libvirt-daemon-system (4.0.0-1ubuntu8) ...
Warning:
Hi rbasak,
almost right - just missing a slight twist.
Yes to all you said until "leaving the situation as-is for stable releases is
appropriate since use case 1 above is far less serious than a potential
regression in use case 3."
I think we all ack on >=18.10 to select the udev backend and be
So could that just have changed over the years upstream?
And if so can you now run your config against e.g. a Cloud image which has this
use created on first boot and still succeed with a config that dropped
allowdupe?
--
You received this bug notification because you are a member of Ubuntu
Bug
For the per thread view use:
$ sudo pidstat -t -p
For perf to track kvm exits you can install it like:
$ sudo apt install linux-tools-common
And then run while your guest hangs (or not in the good case) as:
$ sudo perf stat -e 'kvm:*' -a sleep 1h
More on [1] if you want.
[1]: https://www.linu
Thanks for your clarification Daniel, I'll mark both tasks incomplete
then until you come back with that data.
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubu
Thanks Cyphermox for co-testign this with me.
Here an example of his better interface overview now:
virsh # iface-list
Name State MAC Address
---
enp3s0 active c8:60:00:6d:8c:07
lxdbr0 active
Hi Daniel,
might I ask what you expect now?
The changes to seabios are not even upstream yet in
git://git.seabios.org/seabios.git
The changes to qemu are neither upstream in git://git.qemu.org/qemu.git
The changes linked also are for a qemu way++ back in time (like pre trusty), so
they just don
# id puppet
uid=112(puppet) gid=119(puppet) groups=119(puppet)
$ puppet resource -e user danisch
user { 'danisch':
ensure => present,
uid=> '1015',
gid=> '119',
comment=> 'Hadmut Danisch',
shell => '/bin/bash',
home => '/home/danisch'
}
When saving
Any updates on testing from upstream (or from newer versions in newer
Ubuntu releases) fixing the issue?
** Changed in: open-iscsi (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time w
Hi Rogerio,
neither the mysql error log nor the journal that you auto-attached contain
useful hints to help you.
If anything then I'd wonder about:
2018-05-03T01:48:33.898935Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.22-0ubuntu0.16.04.1' socket: '/var/run/mysqld/mysqld.sock
Hi Skipper,
thanks for sharing the qemu cmdline, there is nothing odd in this and I can run
a system like that (not a win 10 guest) just fine.
What about the per thread stats I asked, which threads are busy and where do
they consume time?
Depending on your experience you could even check "perf k
Thanks for your reply Nicolas, so even for you if udev backend would
work it would be preferred (full view of the network).
We are evaluating if udev works well for the read-only part and I
discussed with upstream how to enable/disable as well as on the approach
in general.
--
You received this
Networks are configured through net-* commands (and respective APIs) and they
all work.
This is what is commonly used by libvirt users and solutions depending on
libvirt.
The scope of iface-* commands is to manage the Host network interfaces.
This is not really what we'd want libvirt to do.
You
Note: easiest test without compiling is likely
$ apt install netcf
$ netcftool list
...
Related to all of that is bug 1688345.
I contacted cyphermox who filed and worked on that to get his opinion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hi,
after sleeping once about this to sort my thoughts I have this morning
revisited most of the code.
## Usage and state of ncf ##
In its only user currently being libvirt I checked that usage via:
$ git log src/interface/
There were only structural changes (how to allocate, make interface ac
Also a per qemu thread view is often useful, you might also add
$ pidstat -t -p
Further since this is reported as kernel update regression I'll flag it
as that for now.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags added: regression-update
--
You received
This didn't fully work even pre netplan, in fact it is separate.
On my partially E/N/I partially NetworkManager system only the former are
accessible to netcf.
So this functionality from libvirts POV was reduced for quite a while.
While netcf itself can be considered really broken atm.
That is w
I wanted to take a look at this again, but TBH at the moment all I've
got was crashing my P9 system three times. I'll start a mail thread on
it and keep this bug clean of it for now.
While resolving that I hope that Bala/Greg will find something about the
issue here on their side.
--
You receive
Following the update to set won't fix here as well
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752797
Title:
[Ubuntu 18.04]
It is sometimes surprising what extra features libvirt all has - I
haven't touched this for all the time working with it - Feature of 2009
it seems :-)
First of all yes, I also can't see anything on 18.04 boxes (not that on
16.04 I'd have got a lot, only "lo" actually).
There is nothing of the co
Opened for a discussion upstream at:
https://www.redhat.com/archives/libvir-list/2018-May/msg00043.html
I didn't have your email to CC you, but you can track via the WEB UI of the ML.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
In fact the MP above is approved by Pitti who sort of owns cockpit.
Since neither of us can push this change I'd appreciate if on SRU handling this
could be done (as it is ~ubuntu-sru scope).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Interesting, I didn't know about the need of that stdio_handler.
But still the issue is solved then - great.
I'll set the status to invalid then to reflect that (we have no closed).
Thanks Stefan!
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Invalid
** Changed in: cloud-archive
** Summary changed:
- virt-manager destroys all volumes in libvirt zfs pool
+ refreshign a pool destroys all volume info in libvirt zfs backend
** Summary changed:
- refreshign a pool destroys all volume info in libvirt zfs backend
+ refreshing a pool destroys all volume info in libvirt zfs back
FYI - we opened [1], and while this needs some processing to be acked an
merged I'd ask the SRU team to consider these autopkgtest fails not a
blocker to move on with thie SRU here atm.
[1]: https://code.launchpad.net/~paelzer/britney/hints-ubuntu-artful-
cockpitfails/+merge/344874
--
You receiv
I was collecting a summary to report upstream, but then I wondered are there
other scenarios where this should not be stripped to the base?
Or is there another common use case were the pool is created differently so it
works?
I followed some other guides and ended up with a non-external created
Ok, without apparmor fixes (unlikely soon for reasons outlined in other
bug) or you weakening the isolation a bit on your system it won't work
then.
So lets focus on the clearing of this volume list in this bug - which
should not happen.
--
You received this bug notification because you are a me
@Tim - Could you check the ntp apparmor profile if it has the change that was
made in 1:4.2.8p10+dfsg-5ubuntu4 ?
It is a conffile so if depending on your former changes it might have been not
updated by default.
Essentially if /etc/apparmor.d/usr.sbin.ntpd has
flags=(attach_disconnected) ?
--
Flagging as libvirt issue as we ruled out virt-manager
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767997
Title:
virt-manager destroys all volumes in libvirt zfs pool
To manage notifications abo
Haven't read all your updates in between while I was writing :-)
Need to re-read all you posted - thanks for your work on this.
You might answer the questions around if that worked for you before or
not while I'm doing so ...
--
You received this bug notification because you are a member of Ubun
Read - I see we both got to the bad zpool call for now.
I'm in a hurry and need to drop for now (sorry), but will look at the source
and maybe if there are later fixes post 4.0 - if not I'll go deeper and try to
create a test version.
Thanks for finding "virsh pool-refresh zfs" for this case.
*
Repro without disks or other HW dependency:
$ apt install zfsutils-linux
$ fallocate -l 100M /tmp/zfs
$ sudo zpool create zfs /tmp/zfs
$ sudo zfs create -V 10M zfs/vol1
You can use that as a disk just fine:
But using disks "through" libvirt pools had a known issu
Hi (again) Brian,
this is rather unexpected let me try to follow what happened.
So far you only triggered this via virt-manager start/refresh so I'll follow
that until we know a non virt-manager trigger - usually it only calls libvirt
tasks so I'd assume we can identify a virsh or so to trigger
I even had an entry in release notes already:
"The packaging now builds libvirt storage drivers as pluggable libraries. This
slims down the installation requirements but some drivers of less general
interest will now be found in universe. (ex: gluster, sheepdog, zfs)"
Extenting that with: "On th
Ok, if that was what you had in mind when selecting patches fine.
Thanks for taking a look.
I'll for tracking eventually fork a bug number for the remaining issue
on this then, but this can wait until it is discussed and pre-tested
here.
--
You received this bug notification because you are a me
Note - in fact this allows to compile more (instead of fewer as assumed)
storage backends as we can deliver some in main (as needed) and the rest
in universe [1] instead of having to support all of them - which e.g.
failed some security checks for sheepdog.
So I'd really hope what I described is y
Hi Brian,
some optional storage backends where separated by Debian a while ago to avoid
pulling in too much non-needed code in most of the cases.
Now on a upgrade since this dependency is only a suggest (for above)
reason isn't installed automatically.
Can you try installing (or check if you hav
Per bug 1763427 this is Fix released since 4.15.0-18.19
** Changed in: apparmor (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679704
Title:
li
@SRU-Team: Dep8 tests show unrelated issues in cockpit for Artful.
I'm in discussion with pitti if we should even mask those tests, considering
what fails and what we changed they are really unrelated (and this type of
error showed before the changes of this SRU).
See the artful column in [1] for
The old title defies my understanding of this case thou, never the less all
changes so far were to 18.04.
And on confirmation it was 18.04 broken -> 18.04 working after the fix.
I'll set up a few systems to try if they are free atm.
But a new bug would still be appreciated.
--
You received this
As described in testcases I set up a few guests and made sure some of them
won't shutdown properly. We want to see
1. all tried to shut down
2. waiting up until timeout for the one that does not shut down
## Pre-Fix ##
Xenial:
sudo /usr/lib/libvirt/libvirt-guests.sh stop
Running guests on defau
Hi Bala,
interesting, but not 100% the same case IMHO.
The former fix and discussion was about 18.04 on P8 to 18.04 on P9 and
it worked fine after the fixes that were pointed out were integrated.
I'd ask you to file a new bug (internally for you and your PPC dev's as
well as with launchpad for us
Using the repro steps above:
1. as-is in Xenial:
ii qemu-system-x86 1:2.5+dfsg-5ubuntu10.25 amd64QEMU full
system emulation binaries (x86)
$ qemu-system-x86_64 -enable-kvm -vnc
unix:/tmp/service/../service/../service/../service/vnc-sock
# due to socat in other shell:
*** Error in `qemu
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
Public bug reported:
Certain cases are mis-debugged for quite a while and users are confused
on a bad apparmor profile (for a guest) being reporte as:
error: internal error: Process exited prior to exec: libvirt: error :
unable to set AppArmor profile 'libvirt-5a0e5825-717b-4edb-857a-
b7bab2f708
Ok, together we found a fix for this which now is integrated upstream.
commit ce5aebeacd10a1c15cb3ee46a59c8b5ff235589e
Author: Laine Stump
Date: Wed Apr 25 17:12:03 2018 -0400
nwfilter: increase pcap buffer size to be compatible with TPACKET_V3
Bionic+1 is not yet open, so atm it is a bit
Fix is now available in [1].
But needs to be picked up for 18.10 (once archive is open in a few days) and
then prepped as 18.04 SRU.
[1]: https://salsa.debian.org/debian/netcat-
openbsd/commit/338b1fa7c3db9bd791095f51325b3287330dac7d
--
You received this bug notification because you are a membe
Debian bug at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897020
** Bug watch added: Debian Bug tracker #897020
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897020
** Also affects: netcat-openbsd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897020
Importance:
I'm not an expert on netcat but I hope this initial triage helps the
next that will look at it.
I reported to Debian as well as they are also affected.
Especially since the change came from Guilhem - it might be best to think about
a solution together.
--
You received this bug notification beca
In gdb I see it gets to read -s
case 's':
sflag = optarg;
break;
It realizes no more options are there and then ends at
} else if (argv[0] && argv[1]) {
host = argv[0];
uport = &argv[1];
Even the example from the manpage fails:
$ nc -s 10.1.2.3 host.example.com 42
** Changed in: netcat-openbsd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17672
-t in description (typo) mislead me - fixed the description
** Description changed:
Hey,
- netcat shows a usage error if i try to use the "-t" option:
+ netcat shows a usage error if i try to use the "-s" option:
Example in Bionic:
- $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
+
Hi Fi,
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of th
1 - 100 of 5815 matches
Mail list logo
