*** This bug is a duplicate of bug 1453330 ***
https://bugs.launchpad.net/bugs/1453330
This is added in bug 1453330 (but using http by default for mirrors).
** This bug has been marked a duplicate of bug 1453330
rewrite pull-[lp|debian|uca]-source
--
You received this bug notification
I think you have this backwards, the current pull-debian-source does
verify its dsc signature while pull-lp-source does *not* verify its dsc
signature (this is done in ubuntutools/archive.py). However, it does
verify the checksum (listed in the dsc file) for all other source files
downloaded
The only failure shown now seems to be network-manager, which is failing its
'test_no_ap' test; that appears to have been failing for a while:
http://autopkgtest.ubuntu.com/packages/n/network-manager/artful/amd64
also there's a bug opened today for it:
artful:
ubuntu@lp1718568-artful:~$ dpkg -l | grep isc-dhcp
ii isc-dhcp-client4.3.5-3ubuntu2.2
amd64DHCP client for automatically obtaining an IP address
ii isc-dhcp-common4.3.5-3ubuntu2.2
xenial:
ubuntu@lp1718568-xenial:~$ dpkg -l | grep isc-dhcp
ii isc-dhcp-client 4.3.3-5ubuntu12.9
amd64DHCP client for automatically obtaining an IP address
ii isc-dhcp-common 4.3.3-5ubuntu12.9
amd64
trusty:
host~$ virsh domif-setlink lp1718568-trusty vnet4 down
Device updated successfully
ubuntu@lp1718568-trusty:~$ dpkg -l | grep isc-dhcp
ii isc-dhcp-client 4.2.4-7ubuntu12.12
amd64ISC DHCP client
ii isc-dhcp-common
verification that it fixes the problem for me, re: autopkgtest. As that
was the same cause/problem as initial reporter's, I expect it should be
fixed for them as well.
ddstreet@thorin:~/bugs/lp1730627/verification$ pull-lp-source lsb-base trusty
pull-lp-source: Using source package 'lsb' for
Well I can't say I'm too surprised that something broke, the
ifupdown<->vlan<->udev love triangle of creating and configuring vlans,
is a bit of a mess. I'll take a look at this as soon as I have a
chance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Due to the nature of this bug, being very difficult to reproduce, real
verification could take weeks instead of only days. However, one reporter has
been running with a test kernel I built here
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1723127
which is the base 4.4.0-112 kernel plus
Opened github sosreport issue 1266 for this
https://github.com/sosreport/sos/issues/1266
Also opened pull request 1267 to fix
https://github.com/sosreport/sos/pull/1267
** Bug watch added: github.com/sosreport/sos/issues #1266
https://github.com/sosreport/sos/issues/1266
** Also affects:
sthou...@in.ibm.com I built a test sosreport package for Xenial in this ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1761442
can you install that sosreport and retest to verify it fixes the error?
If you need a test pkg for trusty or artful (or bionic) let me know and
I can build in the
I reproduced this hang on trusty and I'm investigating.
** Changed in: vlan (Ubuntu Trusty)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: vlan (Ubuntu Trusty)
Status: Confirmed => In Progress
--
You received this bug notification because you are a
** Tags added: regression-update sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701023
Title:
(on trusty) version 1.9-3ubuntu10.4 regression blocking boot
completion
To manage notifications
in this area. This may also affect newer releases too, so
I need to test those as well.
** Changed in: vlan (Ubuntu)
Status: Confirmed => In Progress
** Changed in: vlan (Ubuntu)
Assignee: (unassigned) => Dan Streetman (ddstreet)
--
You received this bug notification becau
It appears this ifupdown locking issue doesn't happen in Xenial, but
I'll do more testing to confirm that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701023
Title:
(on trusty) version
Notes on the apache-deps pending sru autopkgtest failures:
For trusty, the 'puppet' autopkgtest is failing:
http://autopkgtest.ubuntu.com/packages/p/puppet/trusty/amd64
the failure for this sru is here:
I reproduced the 'cacti' autopkgtest on my local system, without this
sru apache2 package; so the test failure is not related to this sru.
This and the last comment provide justification for ignoring all the
pending-sru autopkgtest failures.
--
You received this bug notification because you are
Yep, I think this is similar or the same as bug 1701023, the original
vlan-ordering-ifup-call that i had to add for bug 1573272 is sometimes
causing ifupdown locking issues, although ifupdown is supposed to do
separate locking for each device.
Anyway, I have a test fix that's similar to yours -
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Zesty)
Assignee: Dan Streetman (ddstreet) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Jiri,
no the "Won't Fix" is only for the Zesty release, as that's EOL now.
I actually have a test kernel building in the ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1711407/+packages
it's version 4.13.0-38.43+hf1711407v20180412b2; it hasn't finished
building yet, probably will
> caused by bug 1723272
sorry, i meant bug 1723223
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750013
Title:
systemd-logind: memory leaks on session's connections (trusty-only)
To manage
Note, the 'linux-*' autopkgtest failures in pending-sru for this pkg are
caused by bug 1723272, a known bug that can be ignored as it's unrelated
to this sru.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> I have just reproduced it using the previous #43+hf1711407v20180412b2"
kernel:
Excellent. And just to clarify again, I do *not* expect the kernel to
fix/avoid the problem - I fully expect it to happen - the change in
these kernels is strictly to make sure that the system is still usable
after
*** This bug is a duplicate of bug 1701023 ***
https://bugs.launchpad.net/bugs/1701023
> @ddstreet here's how I reproduced:
ok thnx, I will set that up and try it to reproduce
> You are correct: the proper way to bring up the bond is to bring up
> it's slaves. Running ifup on the bond just
> identified this commit will fix the issue.
>
>
> https://github.com/sosreport/sos/commit/1fd12690870e85e8ac83b0e99bb272ce4489dc60
that commit is already included in the sosreport version being used, so
it does not seem it will fix this.
--
You received this bug notification because you are
sthou...@in.ibm.com I can't reproduce this on x86, does this happen on
all ppc64le systems or only on specific system(s) you have? Can you
provide the sosreport generated with that error?
** Changed in: sosreport (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
I did find an existing sosreport I have that includes this error; I'll
look at the code to see what's going on.
** Changed in: sosreport (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** This bug is no longer a duplicate of bug 1701023
(on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759573
Title:
vlan on
@tom-verdaat I'm temporarily removing this as dup, because I can't
reproduce your error on xenial, or maybe I don't understand the specific
error you're talking about.
> # ifup bond1
> Waiting for a slave to join bond1 (will timeout after 60s)
This isn't new; trying to do this even with an
Just to re-summarize this:
The problem here is when a net namespace is being cleaned up, the thread
cleaning it up gets hung inside net/core/dev.c netdev_wait_allrefs()
function. This is called every time anything calls rtnl_unlock(), which
happens a lot, including during net namespace cleanup.
Jiri,
I just added a new artful version to the ppa, version
4.13.0-38.43+hf1711407v20180413b1; it's building right now. It should
avoid the hang just like the last version from yesterday; but the last
one blocked freeing any future net namespaces after one hangs; this one
fixes that so even
marking this as affecting T/X/A/B, although I need to specifically check
each.
** Also affects: vlan (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: vlan (Ubuntu Bionic)
Importance: High
Assignee: Dan Streetman (ddstreet)
Status: In Progress
** Also
from bug 1759573, looks like this does affect X as well as T.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701023
Title:
(on trusty) version 1.9-3ubuntu10.4 regression blocking boot
completion
*** This bug is a duplicate of bug 1701023 ***
https://bugs.launchpad.net/bugs/1701023
@paelzer yep will do
@tom-verdaat if you don't mind, i'll just dup this bug as @paelzer
suggested and work the fix in bug 1701023. Sorry about this regression.
** This bug has been marked a duplicate of
** Description changed:
[Impact]
When using dhcpv6 configured via ifupdown, the interface's dhcp client
fails to start at boot with the error:
Can't bind to dhcp address: Cannot assign requested address
This is because ifupdown doesn't wait, after bringing the interface up,
Test case #1 (bug 1573272), part (a) and (b) only:
I'm unable to reproduce test case #1 failure on trusty, because upstart
is used instead of systemd. I'm not sure if that means the race
condition doesn't affect trusty, or if i'm just not able to properly
introduce a upstart delay to bond0 to
For testcase 3, from this bug, I'm able to reproduce it on trusty using
vlan 1.9-3ubuntu10.5, and using the pkg from my ppa it is fixed.
I'm not able to reproduce testcase 3 in xenial or later, so there is
nothing to verify re: testcase 3 (this bug's reported error) in X/A/B.
However, my redesign
@smu-u, please do let me know if you are seeing this issue in X/A/B.
Otherwise, I'll assume you only see this issue in trusty, which matches
what I found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also re: testcase 3, I could only reproduce it on reboot and ifup -a; it
did not fail when i tried hotplugging the interface (modprobing its
driver).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For testcase 2, from bug 1759573, I can't reproduce the reported hang
from that bug.
@tom-verdaat, can you provide simpler/clearer reproduction steps, or can you
test with the vlan pkg from this ppa to verify it fixes the problem you're
seeing:
Test pkgs for both ifupdown and vlan available in this ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1701023
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701023
Title:
(on trusty)
** Bug watch added: Debian Bug tracker #896433
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896433
** Also affects: ifupdown (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896433
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker
signed) => Dan Streetman (ddstreet)
** Changed in: ifupdown (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: ifupdown (Ubuntu Xenial)
Status: New => In Progress
** Changed in: ifupdown (Ubuntu Xenial)
Assignee: (unassigned) => Dan Streetman (dds
Public bug reported:
[impact]
when configuring an interface in ifupdown to use 'inet6 auto' (SLAAC),
the option 'dhcp 1' can also be used, which will use isc-dhcp-client to
perform 'stateless' dhcpv6, which does not get a dhcpv6 address, only
config info, like DNS domain and server, etc.
bug
> The machine continue to run and the docker is still able to create new
> instances,
> i.e. there is no complete lock out.
Great!
> The machine continued to run further, and after an ~hour , 3 namespaces
> leaked.
> The machine now has load "3", which seems to be an artifact of this. Other
>
d in: isc-dhcp (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: isc-dhcp (Ubuntu Bionic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: isc-dhcp (Ubuntu Artful)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: isc-d
This bug is caused in two different ways, both not directly from
ifupdown or vlan, but instead because of 'helpful' actions in the
ifenslave and bridge-utils if-pre-up scripts.
First, as reported in this bug, the bridge-utils package adds a
if-pre-up.d/bridge ifupdown script, and in that
The reason the if-pre-up.d/vlan script was changed to call ifup for its
raw-device, was for bug 1573272, where the problem was a race condition
between the VLAN and its raw-device; if the VLAN interface was processed
through if-pre-up.d/vlan before the raw-device was fully configured,
then in some
Xenial verification:
ubuntu@lp1447715:/etc/network/interfaces.d$ dpkg -l | grep ifupdown
ii ifupdown 0.8.10ubuntu1.2
amd64high level tools to configure network interfaces
ubuntu@lp1447715:/etc/network/interfaces.d$ grep -A 2 ens7
Also, for each of those test cases, this fix needs to be tested for:
a) normal bootup
b) ifup -a
c) physical device hotplug (e.g. insmod driver, or hotplug removable nic)
all cases should bring up the configure the associated vlans correctly.
--
You received this bug notification because you
There are 3 test cases here to verify this:
1) the original bug 1573272. Test case is in that case's description. Note
this test case needs to be (using trusty version numbers):
a) FAIL with vlan 1.9-3ubuntu10.1
b) PASS with vlan 1.9-3ubuntu10.5 (current version)
c) PASS with the
Debian's included a variation of my patch to ifupdown, so I'll update my
ppa to use that patch instead and do some testing, then start sru'ing
both ifupdown and vlan.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> @ddstreet tested with the latest version of ifupdown and vlan from your PPA
> with
> my 4 testscenario's and can confirm it works as expected. Interfaces come up
> correctly both when doing an "ifup -a" and during boot.
Excellent, thanks.
> One small thing I've noticed is a variation in the
> the CPU usage is zero, there is nothing popping up. The tasks causing the
> high load
> value are in D state
ok that seems expected then. This doesn't 'fix' the problem of the
leaked dst (and namespace), just prevents blocking further net namespace
creation/deletion.
> if I can't run out of
** Patch removed: "lp1447715-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1447715/+attachment/4745626/+files/lp1447715-xenial.debdiff
** Patch added: "lp1447715-xenial.debdiff"
Test build in ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1447715
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447715
Title:
dhclient -6: Can't bind to dhcp address: Cannot assign
this issue was raised before in bug 1633562, and closed as invalid
because a side effect of isc-dhcp doing 'preinit6' is clearing any
existing global ipv6 addresses from the interface, which definitely is
not desirable when using RA to get the address.
--
You received this bug notification
Additional note for this bug: this has been "fixed" upstream by adding a
--dad-wait-time parameter to dhclient. However, that param defaults to
0, and also requires an update to the dhclient-script.linux that isc-
dhcp provides. Debian has its own modified dhclient-script.linux,
slightly
*** This bug is a duplicate of bug 1633562 ***
https://bugs.launchpad.net/bugs/1633562
this is also related to bug 1447715 in which i added the DAD wait to
ifupdown. however, since bug 1633479 fixed the issue in dhclient
instead of ifupdown, at around the same time, i marked bug 1447715 as
I'm re-opening this for Xenial, moving from Wontfix back to in progress.
This is because while 'normal' dhcpv6 works without this fix because of
the patch to dhclient (see my explanation in comment 23), there is a
special case of using dhclient in 'stateless' mode, i.e. dhclient -6 -S.
In that
i opened bug 1764478 to change dhclient 'stateless' mode, but as
explained in that bug, it's better to fix ifupdown, here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447715
Title:
dhclient -6:
The reason that udev calls /lib/udev/vlan-network-interface is because
of hotplugging.
During boot up, as network interfaces are detected by the kernel, they
are reported to udev, and udev passes each to vlan-network-interface.
If the vlan-network-interface script detects that a new interface is
Anyone experiencing this bug, can you please test with the vlan package from
this test ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1701023
I still need to do more testing with it as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Once the LP: #1466926 apache2 SRU in xenial -proposed is either promoted
or removed, I'll upload this to affected releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752683
Title:
race
Jiri,
I've looked at several possible ways to just work around the main issue,
of hanging netns creation/destruction, and just allow the netns to leak
when a dst leaks. However, none of the approaches I tried were usable.
I'm going to keep looking at it this week and I'll let you know when I
the commit 5c4654daf2e2f25dfbd7fa572c59937ea6d4198b
("i40e/i40evf: Allow up to 12K bytes of data per Tx descriptor instead
of 8K") is also required.
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Artful)
Assignee: (unassign
> Hi, might be useful to find root-cause
"root-cause" for this is a dst object leak, and there have been many
kernel dst leak patches, there almost certainly are still dst leak(s) in
the kernel, and more dst leaks will be accidentally added later.
Unfortunately, the dst leaks all lead to an
** Description changed:
+ [impact]
+
+ The i40e driver sometimes causes a "malicious device" event that the
+ firmware detects, which causes the firmware to reset the nic, causing an
+ interruption in the network connection - which can cause further
+ problems, e.g. if the interface is in a
ok i'll recreate the debdiffs and reupload.
** Tags removed: verification-needed verification-needed-artful
verification-needed-trusty verification-needed-xenial
** Changed in: isc-dhcp (Ubuntu Artful)
Status: Fix Committed => In Progress
** Changed in: isc-dhcp (Ubuntu Xenial)
** Description changed:
I've essentially re-written the pull-[lp|debian|uca]-source scripts,
consolidating them all to use a common codebase and extending the
functionality to allow pulling not only source but also debs, udebs, and
ddebs.
The updates also allow specifying binary
> when SSH ends, for example, a Release event is sent
> through dbus and systemd-logind captures it, in the function
> manager_message_handler().
>
> From there, the function session_remove_fifo() is called. That point is our
> "bootstrap"
> to add the closing session on gc
ok i see that path,
> Is there no other more reliable way to reproduce the case that's being
fixed here
sure yes, here's what i did; first, setup:
-create VMs for the releases (T/X/A), managed by virsh (e.g. with uvt-kvm or
whatever)
-add a second interface to each of them, e.g.:
$ virsh attach-interface
That looks good.
My only comment now is, I see you've switched cgmanager from Suggests:
to Depends:...is that *really* needed to fix a memleak here? i.e., if
you uninstall cgmanager and re-run your memleak tests, does mem still
leak? While changing it to a Depends: isn't impossible, I'd prefer
** Tags added: sts-sponsor-ddstreet
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688508
Title:
libvirt-guests.sh fails to shutdown guests in parallel
To manage notifications about this bug go
This does not look right to me:
@@ -951,6 +952,7 @@
free(s->fifo_path);
s->fifo_path = NULL;
}
+session_add_to_gc_queue(s);
}
int session_check_gc(Session *s, bool drop_not_started) {
that puts the session on the manager's gc queue, however
This problem was not that the encoding was non-utf8, python-debian
correctly detects that and uses chardet to autodetect the right
encoding. That 'decoding from utf-8 failed' message is harmless.
The problem here is that the old package signature required a public key
that's no longer in the
** Description changed:
I've essentially re-written the pull-[lp|debian|uca]-source scripts,
consolidating them all to use a common codebase and extending the
functionality to allow pulling not only source but also debs, udebs, and
ddebs.
The updates also allow specifying binary
Thanks @rbalint, I just got back from vac.
** Changed in: ebtables (Ubuntu Trusty)
Assignee: Dan Streetman (ddstreet) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774120
Ti
as I can't reproduce this, and I have heard no more reports of it, i'm
marking this as incomplete. If anyone does actually still see this
problem with the latest (x/b/c) kernel, please add a comment to this
bug.
** Changed in: linux (Ubuntu Xenial)
Assignee: Dan Streetman (ddstreet
** Changed in: simplestreams (Ubuntu Artful)
Status: Confirmed => 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/1686086
Title:
glance mirror and nova-lxd need support for squashfs
uploaded to xenial queue, now waiting on SRU approver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749289
Title:
Installer stops after pressing Cancel on Select a language screen
during OEM
** Summary changed:
- nodejs-dev conflicts with libcurl4-openssl-dev libssh-dev libssl-dev, causing
build failures
+ libssl1.0-dev conflicts libssl-dev
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As an example of some of the packages that conflict with libssl1.0-dev,
due to conflict:
$ sudo apt install libssl1.0-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
n: openssl1.0 (Ubuntu Bionic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: openssl1.0 (Ubuntu Cosmic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: openssl1.0 (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: openssl1.0 (Ubuntu
This has bugged me too, unless someone else gets to this first I'll take
a look at adding it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797290
Title:
no bash-completion for pull-lp-source (and
** Changed in: ubiquity (Ubuntu Xenial)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
** Changed in: ubiquity (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: ubiquity (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification
ubuntu@lp1748147:~$ dpkg -l systemd | grep systemd
ii systemd229-4ubuntu21.4 amd64system and service manager
ubuntu@lp1748147:~$ ls -lad /var/log
drwxrwxr-x 7 root syslog 4096 Oct 15 16:32 /var/log
ubuntu@lp1748147:~$ sudo apt install --reinstall systemd
...
ubuntu@lp1748147:~$
** Tags removed: verification-needed
** Tags added: verification-done
** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781039
Title:
GCE cloudinit and ubuntu keys from
Xenial nvme-cli doesn't provide any bash completion script; this is
needed only in bionic/cosmic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800544
Title:
nvme-cli drops bash completion file in
inside the 'bash-completion'
pkg, and only rarely are managed directly by owning packages. Those
that do should drop their scripts into /etc/bash_completion.d/, not
/usr/share/bash_completion.d/.
** Affects: nvme-cli (Ubuntu)
Importance: Low
Assignee: Dan Streetman (ddstreet
apt cache for the first 3 (or so) letters of a package name, but
after that switch to real LP querying (hopefully with caching). Or,
maybe we could use a LP package local cache, but if that's not populated
yet fall back to apt caching.
** Changed in: ubuntu-dev-tools (Ubuntu)
Assignee: (unass
** Changed in: openssl1.0 (Ubuntu Bionic)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: openssl1.0 (Ubuntu Cosmic)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: openssl1.0 (Ubuntu Bionic)
Status: In Progress => Confirmed
*
** Changed in: openssl1.0 (Ubuntu Bionic)
Importance: High => Medium
** Changed in: openssl1.0 (Ubuntu Cosmic)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
@fayomidimeji, my comment 4 applies to you as well.
Additionally, you both might want to verify you are actually seeing this
problem, and not something else.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@terryh-orcas,
if you are able to reproduce the problem relatively quickly and easily, then I
suggest testing different kernel versions, up to the latest upstream, to see if
and where it may be fixed with a newer i40e kernel driver. You can get
upstream kernel debs here:
Trusty)
Importance: Low
Assignee: Dan Streetman (ddstreet)
Status: In Progress
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Trusty)
Status: New => In Progress
** Changed in: systemd (Ubuntu Tru
** Description changed:
[impact]
udev (in trusty) does not create symlinks in /dev/disk/by-path/ for any
disks that are connected via sata.
[test case]
Install trusty onto a system with sata drives, and check /dev/disk/by-
path/ for symlink(s) to those sata drive(s).
uploaded to trusty and xenial queues, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802958
Title:
libgs9-common not upgraded when libgs9 upgraded
To manage notifications about this bug go
** Also affects: netplan.io (Ubuntu Cosmic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767849
Title:
from key in routes generates incorrect networkd
** Also affects: ghostscript (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: ghostscript (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: ghostscript (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: ghostscript (Ubuntu
801 - 900 of 4672 matches
Mail list logo