Public bug reported:
Investigations done in 22.04/Jammy but may be affecting other series,
too.
The dnsmasq package recently was updated from 2.86-1.1ubuntu0.5 to
2.90-0ubuntu0.22.04.1. This seems to have brought back the same issue
reported in bug #1957086. Sounds like both have interaction issu
Sounds like some interaction issue between the system, systemd, and
dnsmasq somehow. As this fails on and off since a very long time. When I
test with the older dnsmasq and getting a success the time spent on the
test seems overly long. Like there is something not quite right even
then.
** Also af
** Attachment added: "Log of the DNS resolving dnsmasq while running the test"
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+attachment/5759256/+files/dnsmasq-vpn.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
** Attachment added: "Journal of systemd while running the test"
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+attachment/5759257/+files/systemd.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
** Attachment added: "Output of networkd-test.py"
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+attachment/5759255/+files/networkd-test.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubunt
** Changed in: linux (Ubuntu Hirsute)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1925211
Title:
Hot-unplug of disks leaves brok
Just as a heads up: The upstream stable update 5.11.20 for hirsute un-reverts
- "s390/cio: remove pm support from ccw bus driver"
and adds
- "s390/cio: remove invalid condition on IO_SCH_UNREG"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which i
Turns out that is a SUT which does not get freshly provisioned and had
proposed enabled. And there is a newer lxc in proposed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1969
Public bug reported:
This is a scripted bug report about ADT failures while running network-
manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by
the dep8 tests of the tested source or the kernel has yet to be
determined.
Testing failed on:
amd64:
https://autopkgtest.ubun
This seems to be related to: "rfkill: make new event layout opt-in" in
the -28 kernel. When I revert that a local reproduction run starts to
work again. However I never got the same error pattern as in the ADT
logs (those seem to get random data back from trying to read the MAC
address). So a littl
mmy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Stefan Bader (smb)
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notif
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1971418
Title:
network-manager/1.36.
With the revert, the network-manager ADT tests work again.
https://autopkgtest.ubuntu.com/results/autopkgtest-
jammy/jammy/amd64/n/network-manager/20220505_053118_fb2db@/log.gz
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification
>From ADT testing: https://autopkgtest.ubuntu.com/results/autopkgtest-
focal/focal/arm64/s/systemd/20220310_155736_6a08c@/log.gz
This was previously failing the storage subtest.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notificati
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.lau
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: apparmor (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Lunar)
Importance: Undecided
** Changed in: linux (Ubuntu Lunar)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2016908
Title:
udev fails to make prctl() sy
Public bug reported:
This is a scripted bug report about ADT failures while running systemd
tests for linux/5.4.0-128.144 on focal. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be determined.
Testing failed on:
armhf:
https://autopkgtest.ubuntu.com/r
To me it looks like the boot-and-services sub-tests got a lot less
reliable on armhf in Focal. The previous systemd version had a higher
chance of passing those. There always was root-unittests which required
multiple attempts. But now from about 10 attempts there was one which
had root-unittests o
Public bug reported:
We seem to get failed dep8 testing on lxc in Groovy for a while. What we
are interested in is knowing whether this is known problems in the
testing or something that waits on kernel fixes (who would be driving
those if this is the case).
Testing failed on:
amd64:
https:/
Thanks Christian, I think we would for now mark this up as known issue
in lxc. There is a bit of a mystery on our side as it seems right now as
if this failed for couple of our releases and never appears to have been
investigated/asked.
--
You received this bug notification because you are a memb
Could someone try to put the attached script into /etc/kernel/postinst.d
and let me know whether that make installkernel work? Thanks.
** Attachment added: "Copy to /etc/kernel/postinst.d/xx-update-initrd-links"
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1877088/+attachment/5441
** Changed in: linux-base (Ubuntu)
Status: New => In Progress
** Changed in: linux-base (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader
(smb)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
** Description changed:
- [MIR] libbpf (dependency of iproute2)
+ [Availability]
+ libbpf | 0.1.0-1 | groovy/universe | source
+ libbpf | 0.3-2 | hirsute/universe | source
+
+ [Rationale]
+ Libbpf is (or is about to become) a dependency for building iproute2 which
already is in main. Using BP
** Description changed:
[Availability]
libbpf | 0.1.0-1 | groovy/universe | source
libbpf | 0.3-2 | hirsute/universe | source
[Rationale]
Libbpf is (or is about to become) a dependency for building iproute2 which
already is in main. Using BPF is becoming more wide-spread. The libr
** Description changed:
[Availability]
libbpf | 0.1.0-1 | groovy/universe | source
libbpf | 0.3-2 | hirsute/universe | source
[Rationale]
Libbpf is (or is about to become) a dependency for building iproute2 which
already is in main. Using BPF is becoming more wide-spread. The libr
** Description changed:
[Availability]
libbpf | 0.1.0-1 | groovy/universe | source
libbpf | 0.3-2 | hirsute/universe | source
[Rationale]
Libbpf is (or is about to become) a dependency for building iproute2 which
already is in main. Using BPF is becoming more wide-spread. The libr
Updating the proposed change. This addresses the following:
- Only run from the trigger stage when called from dpkg
- Pass the same environmental flag as update-initramfs does
(in theory there never should be need to generate an initrd)
- Handle special case of installkernel called multiple times
** Changed in: systemd (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1837227
Title:
systemd mount units fail du
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2031352
Title:
Nouveau driver crash - Ubuntu 22.04.3
Public bug reported:
This might be apparmor, the test case, kernel or anything in between:
7720s running attach_disconnected
7720s Fatal Error (unix_fd_server): Unable to run test sub-executable
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux
Public bug reported:
9017s 12:26:37 DEBUG| [stdout] # PASS: neigh get
9018s 12:26:38 DEBUG| [stdout] # PASS: bridge_parent_id
9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "proto"
is a garbage.
9018s 12:26:38 DEBUG| [stdout] # Error: either "local" is duplicate, or "prot
I was going over the ADT results for the complete linux suite:
https://autopkgtest.ubuntu.com/results/autopkgtest-
mantic/mantic/amd64/l/linux/20231002_144159_55314@/log.gz (6.5.0-7.7)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
@Stéphane, isn't that the way Britney works? There will always be one
package from proposed which is triggering ADT and the rest is non-
proposed. Or was there more than one?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Stefan Bader (smb)
--
You received this bug notification because
** No longer affects: alsa-lib (Ubuntu Cosmic)
** Also affects: alsa-lib (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux-oem (Ubuntu Cosmic)
Importance: Undecided
Statu
The kernel fix for this arrived in Xenial/16.04 via upstream stable
v4.4.125.
** Also affects: laptop-mode-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Xenial)
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/n/network-manager/20180323_105026_adff0@/log.gz
** Affects: network-manager (Ubuntu)
Importance: Undecided
St
test_wpa2_ip4 (__main__.ColdplugWifi)
WPA2, 802.11g, IPv4 ... ok
test_wpa2_ip6 (__main__.ColdplugWifi)
WPA2, 802.11g, IPv6 with only RA ... ok
test_auto_detect_ap (__main__.Hotplug)
new AP is being detected automatically within 30s ... expected failure
test_auto_detect_eth (__main__.Hotplug)
new et
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/s/systemd/20180606_154452_00599@/log.gz
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** T
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu Zesty)
Importa
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/s/systemd/20171123_190248_4f60f@/log.gz
s390x:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a8492
The s390x failure is because tests now run in a VM and on s390x there is
no grub (zipl is used as the boot loader).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1734344
Ti
** Changed in: linux (Ubuntu Artful)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1746463
Title:
apparmor profile load in stac
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verifica
example the route_with_policy test of
netplan.io.
Testcase:
ip rule add from 10.1.0.0/24 to 10.2.0.0/24 lookup 99
ip rule show
Expected: *: from 10.1.0.0/24 to 10.2.0.0/24 lookup 99
Actual output: *: from 0.1.0.0/24 to 10.2.0.0 /24 lookup 99
** Affects: iproute2 (Ubuntu)
Importance: Hi
Fix proposal submitted upstream: https://marc.info/?l=linux-
netdev&m=153546645305223&w=2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1789431
Title:
ip rule show has u
** No longer affects: linux (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
** No longer affects: systemd (
I did prepare some slightly modified proposal for this and will try to
get things progressing tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1786574
Title:
remove i
I did prepare some slightly modified proposal for this and will try to
get things progressing tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1786574
Title:
remove i
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1729145
Title:
/dev/bcache/by-uuid links not cre
** Changed in: ubuntu-fan (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubuntu-fan (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-fan (Ubuntu)
Assignee: (unassigned) => Stefan Bader (smb)
--
You received this bug notification because you are a
** Changed in: ubuntu-fan (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netpl
Public bug reported:
Testing failed on:
* amd4:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/s/systemd/20180207_192259_e5f4f@/log.gz
* s390x:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a7
On s390x the test case still(!) does not handle the fact that there is
no grub used:
autopkgtest [18:29:24]: test systemd-fsckd: [---
Traceback (most recent call last):
File "/tmp/autopkgtest.L6HMaj/build.kLb/src/debian/tests/systemd-fsckd", line
267, in
boot_with_syste
On amd64 this looks to be a race between creating disk partitions and
having usable devnodes created by udev (wait, check?):
DeviceBoot StartEnd Sectors Size Id Type
/dev/loop12p12048 800767 798720 390M 83 Linux
/dev/loop12p2 800768 819199 184329M 83 Linux
The p
*** This bug is a duplicate of bug 1748398 ***
https://bugs.launchpad.net/bugs/1748398
** This bug has been marked a duplicate of bug 1748398
systemd 234-2ubuntu12.1 ADT test failure with linux 4.13.0-33.36
--
You received this bug notification because you are a member of Ubuntu
Touch see
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ub
Please, anybody having still the symptom of a not working keyboard, file
a new bug and do not add comments to this one. This bug is fixed and the
necessary USB OHCI drivers are built in. It might me something related
to USB3 but this will need further debugging and that is better done in
a new bug
Ok, Seth, I found that I can see this in a VM when using the original
Trusty release desktop 64bit ISO:
- boot into "Try Ubuntu"
- open a terminal (uxterm works best for me due to this stupid gfx bugs with
Cirrus)
- ls /tmp (contains some files already)
- sudo apt-get update
- sudo apt-get instal
Not sure this helps or adds just more confusion, but I find it odd that
with the broken environment there remain two /sbin/init processes
running at least for a while... Ok, could be because the 2nd one which
likely is the supposed restart is getting blocked because of the
vanished files in /tmp.
Oh right and the trace command that Steve used will show a call to init
early on which passes in a state fd which then, a bit later, seems to be
used as command stream to a shell. A construct like that was the parent
of mounted-tmp runs I observed. So I assume this is the method to
execute upstart
Oh f..., I hate user-space. Now it does not even reproduce with the
steps it was before...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1464442
Title:
installing or upgr
Maybe its actually the strace attached to pid1...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1464442
Title:
installing or upgrading libc6 in Trusty removes all content
So its confirmed: having a "strace -ff -p1 -e execve" running in a
different uxterm while doing the install will cause the reproduction to
fail. Damn Heisenbugs.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubunt
I took this log while installing libc with forkstat. /tmp was cleaned
when doing this. Not sure it shows more about what is going on.
** Attachment added: "forkstat.txt"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1464442/+attachment/4420389/+files/forkstat.txt
--
You received thi
Seems on bare-metal servers I have, I do not see this. The VM as well as
well as bare-metal server of the team mate I asked are booting rather
quickly. That as side note. I upgraded the VM today and now run on
systemd/udev 221-1ubuntu2.
Still the same. One observation that looks odd: There is a pi
** Changed in: ifupdown (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1466790
Title:
dhclient does not remain running on boot
Changed the disk from virtio to IDE without change. Added debug to the
kernel options and got a bit more info in journal but it looks odd.
There is a dhclient with PID 496 early on. Which does not seem to exit.
But then later on there is a 699 getting killed which matches the pid
file but never see
Comparing to output of a vivid VM, the sysctl status differs in one
important detail. The initial dhclient again is gone but under the
system-ifup.slice there is the new pid...
● ifup@eth0.service - ifup for eth0
Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset:
enabled
I think I may have a clue now what the problem is. Incidentally on my
bare-metal servers the network interface seems to be brought up by
something else than the ifup@.service. The status there reports it
already up when the service runs. The same seems to be happening to MAAS
instances after initia
Public bug reported:
Fresh VM installation from the Artful daily server ISO. Installation
finishes without issues but booting the installed system takes a long
time (until systemd-networkd-wait-online.service times out). The VM can
already be pinged at that stage, so network has been configured at
#> ifquery --list
lo
#> ip link show
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000
link/ether 00:16:3e:71:31:57 brd ff:ff:f
I created the directory and rebooted once ;) Here is the tarball.
** Attachment added: "journal.tgz"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+attachment/4895674/+files/journal.tgz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
@Steve, yes it does. And if the wait is related to the list of NICs from
ifquery, it does make sense (in some way) as that list only contains
"lo", not "eth0". Also "ifquery --state eth0" does not return anything
while it does return "lo=lo" for "lo".
--
You received this bug notification because
Here the netcat config. Note only eth0 appearing here (for KVM guests,
the same happens but with ensX NIC names).
** Attachment added: "01-netcfg.yaml"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1697730/+attachment/4895673/+files/01-netcfg.yaml
--
You received this bug notificati
Sorry, forgot above:
#> cat /run/systemd/network/10-netplan-eth0.network
[Match]
Name=eth0
[Network]
DHCP=ipv4
[DHCP]
RouteMetric=100
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpa
@Steve, eth0 is normal when you use Xen HVM guests. What I see when I
strace the wait command is that is is in some epoll most of the time.
That was the reason I was thinking that maybe it is waiting on some
status change. But then I also believe it did find two entries in
/run/systemd/netif/links
Hm, maybe that helps. This is the contents of /run/systemd/netif/links/2
(which is my eth0):
# This is private data. Do not parse.
ADMIN_STATE=configuring
OPER_STATE=routable
NETWORK_FILE=/run/systemd/network/10-netplan-eth0.network
DNS=192.168.2.1 fe80::c66e:1fff:fe3b:bdcd
NTP=
DOMAINS=
ROUTE_DOM
@Ryan:
2: eth0
Link File: /lib/systemd/network/99-default.link
Network File: /run/systemd/network/10-netplan-eth0.network
Type: ether
State: routable (configuring)
Path: xen-vif-0
Driver: vif
HW Address: 00:16:3e:71:31:57 (Xensource, In
So from what Steve wrote and what I see. the missing part is moving from
"Gained IPv6LL" to "Configured".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1697730
Title:
Lon
** Changed in: linux (Ubuntu Yakkety)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1661030
Title:
regession tests failing after s
** Changed in: linux (Ubuntu Yakkety)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1645037
Title:
apparmor_parser hangs indefinit
Not fixed because we had to revert the commits due to various
regressions.
** Changed in: linux (Ubuntu Xenial)
Status: Fix Released => Triaged
** Changed in: linux (Ubuntu Yakkety)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of U
Public bug reported:
The Zesty (17.04) version of nc (1.130-1ubuntu1) no longer returns the
received data when using the '-d' (do not listen on stdin) flag together
with the '-l' (listen on socket) flag. This used to work in previous
releases (1.105-7ubuntu1 Trusty-Yakkety). In fact, in the previo
Added to the Debian bug report. Basically the output problem is related to a
Debian add-on patch to introduce the -q# option (delayed exit) which has been
incorrectly adapted to the new code.
However while testing a possible solution I found that upstream changed the
default behaviour of nc to n
** Patch added: "Proposal to fix -q handling"
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1656785/+attachment/4808834/+files/ubuntu-fix-readwrite-loop.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Stefan Bader (smb)
** Also affects: multipath-tools (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: hw-detect (Ubuntu Y
Prepared a patch and sent to the kernel-team mailing list.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1673350
Title:
dm-queue-length module is not included in
Not fixed because we had to revert the commits due to various
regressions.
** Changed in: linux (Ubuntu Yakkety)
Status: Fix Released => Triaged
** Changed in: linux (Ubuntu Xenial)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of U
Not fixed because we had to revert the commits due to various
regressions.
** Changed in: linux (Ubuntu Xenial)
Status: Fix Released => Triaged
** Changed in: linux (Ubuntu Yakkety)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of U
Not fixed because we had to revert the commits due to various
regressions.
** Changed in: linux (Ubuntu Xenial)
Status: Fix Released => Triaged
** Changed in: linux (Ubuntu Yakkety)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of U
I was reviewing the latest patch and beside of this part being modified (@Ogra,
would you be fine with that? And btw Jan 1 2017 is a Saturday), I am not fully
understanding what exactly looking at file dates gains. The date will be less
wrong but still potentially off by days. The system date wo
@Alfonso, right, but the details about what exactly failed is quite
important/useful information. If some certificates are deemed invalid on boot
until there is network this does not sound too bad at first. If this causes
services to not start, then this becomes more important to fix.
Also wonde
Looking at the complete fixrtc-mount script (the part which was fixed in bug
#1623125 makes me think that this would fix your problem as well. And that with
much less required change. That script checks not only mount but also create
time of the fs. If create time is more recent than mount time,
*** This bug is a duplicate of bug 1623125 ***
https://bugs.launchpad.net/bugs/1623125
** This bug has been marked a duplicate of bug 1623125
fixrtc script does not catch "Last mount time: n/a" string
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
signee: (unassigned) => Stefan Bader (smb)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1623125
Title:
fixrtc script does not catch "Last mount time: n/a"
Started to bring up real HW with the same woes and timeout on boot.
After some more cursing and faffing around I realized an odd element of
the resulting setup:
There is some weird ipv6 link local address for DNS server:
fe80::c66e:1fff:fe3b:bdcd. It is the same for the VM doing dhcp and for
real
So that link local is from a Wireless AP that runs open-wrt. But why it
is picked up and how can I stop this madness?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1697730
1 - 100 of 172 matches
Mail list logo
