By the time BLKRRPART returns the partition device nodes should have
been created in devtmpfs, so there shouldn't be any need to wait for
things to settle. I'm not sure where a race could exist.
Yet it's odd that this failed only for ppc since all the code which
deals with this is generic, not pla
I failed to follow up.
There were no failures when re-running the test, and no errors with
4.12.0-5.6, so marking this invalid.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
Testing failed on:
ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-ppa/artful/ppc64el/l/lxc/20170517_145323_cd88a@/log.gz
** Affects: lxc (Ubuntu)
Importance: Undecided
---
Setting up the GPG keyring
ERROR: Unable to fetch GPG key from keyserver.
Getting instance for '86e24950-3b10-11e7-8eab-fa163ee158b9'
Creating rootfs using 'download', arch=ppc64el
Traceback (most recent call last):
File "/tmp/tmp.MzGrfkfdXM", line 72, in
assert(container.defined)
Assert
I can't retry myself (ppa kernel, apw is able to make tests run
somehow). I'll be uploading a new kernel in the near future for the
iptables thing anyway, so I'll mark this invalid.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
I can't retry myself (ppa kernel, apw is able to make tests run
somehow). I'll be uploading a new kernel in the near future for the
iptables thing anyway, so I'll mark this invalid.
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a
linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
*** This bug is a duplicate of bug 1823862 ***
https://bugs.launchpad.net/bugs/1823862
** This bug has been marked a duplicate of bug 1823862
disco: unable to use iptables/enable ufw under -virtual kernel
--
You received this bug notification because you are a member of Ubuntu
Touch seede
** Description changed:
+ SRU Justification
+
+ Impact: iptables does not work in disco with linux-virtual.
+
+ Fix: Add bpfilter to the generic inclusion list.
+
+ Regression Potential: There are no code changes and thus minimal
+ potential for regressions.
+
+ Test Case: Verify that bpffilte
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1823862
Title:
disco: unable to use iptables/enable ufw u
** Changed in: linux (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 ufw in Ubuntu.
https://bugs.launchpad.net/bugs/1823862
Title:
disco: unable to use iptables/enable uf
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/l/lxc/20200619_210334_814e1@/log.gz
arm64:
https://objectstorage.prodstack4-5.canonical
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/s/systemd/20200619_224023_f687b@/log.gz
arm64:
https://objectstorage.prodstack4-5.canon
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/s/systemd/20200630_154532_b7979@/log.gz
arm64:
https://objectstorage.prodstack4-5.canon
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/i/initramfs-tools/20200702_083751_cff4d@/log.gz
** Affects: initramfs-tools (Ubuntu)
I
This appears to be a race in debian/tests/run-image:
dev=$(losetup -Pf --show "$IMAGE")
mount "${dev}p1" mnt
It appears that loop0p1 is not ready before the mount command. I
reproduced the issue locally, and adding a 'sleep 1' between these lines
caused the test to pass.
--
You received this
Seeing these failures with 5.4, 5.7, and 5.8 kernels.
--
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/1887542
Title:
apparmor 2.13.3-7ubuntu6 ADT test failure with linux-5
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/a/apparmor/20200714_133743_4383d@/log.gz
arm64:
https://objectstorage.prodstack4-5.cano
** Description changed:
+ == test-cap-list ===
+ Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at
src/test/test-cap-list.c:60, function test_capability_set_one(). Aborting.
+ FAIL: test-cap-list (code: 134)
+
+ This seems to be a result of new capabilities added in 5.8.
This is a new failure, an autopkgtest run on July 7 did not have these
failures whereas a run on July 14 did, so something happened between
those dates. As noted I also seen tests with 5.4 and 5.7 kernels showing
the same errors:
http://autopkgtest.ubuntu.com/packages/a/apparmor
There the first f
The test still fails with systemd 245.6-3ubuntu3.
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-groovy-canonical-kernel-team-
bootstrap/groovy/amd64/s/systemd/20200721_162550_a22c1@/log.gz
** Changed in: systemd (Ubuntu)
Status: Fix
I think the problem might be an unnecessary backslash in
common/Make.rules:
CAPABILITIES=$(shell echo "\#include " | cpp -dM |
LC_ALL=C sed -n -e '/CAP_EMPTY_SET/d' -e 's/^\#define[
\t]\+CAP_\([A-Z0-9_]\+\)[ \t]\+\([0-9xa-f]\+\)\(.*\)$$/CAP_\1/p' |
LC_ALL=C sort)
I wrote a dummy makefile to test
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => 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.lau
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-groovy/groovy/amd64/s/systemd/20200812_210502_aa555@/log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubun
Public bug reported:
Linux 5.8 allows unprivileged creation of whiteout devices, causing a
couple of test failures in systemd:
== test-fs-util ===
/* test_chase_symlinks */
/* test_unlink_noerrno */
/* test_readlink_and_make_absolute */
/* test_var_tmp */
/* test_dot_or_dot_dot */
/* test
I'm getting an oops from launchpad trying to attach a debdiff to update
the package to fix the problem, so supplying a link instead:
https://people.canonical.com/~sforshee/initramfs-
tools_0.137ubuntu11.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Upstream fix:
https://github.com/systemd/systemd/pull/16734
--
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/1891527
Title:
systemd unit tests need updates for Linux 5.8 an
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
htt
I hadn't seen this bug before today when I noticed that it's blocking my
kernel in groovy-proposed. I upgraded systemd, and I am seeing this
issue. But when I boot back to 5.4.0-37 the problem persists, so it
doesn't seem to have anything to do with the 5.8 kernel.
It seems like a problem with app
I should note, I did not update systemd in isolation. I can provide a
complete list of packages installed/upgrade at the same time if that is
helpful.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://
These messages show up repeatedly in the journal:
Aug 19 21:33:11 ubuntu-x1 systemd[1]: Failed to start Process error reports
when automatic reporting is enabled.
Aug 19 21:33:11 ubuntu-x1 systemd[1]: apport-autoreport.service: Start request
repeated too quickly.
Aug 19 21:33:11 ubuntu-x1 system
Looks like a problem generating a new initramfs:
update-initramfs: Generating /boot/initrd.img-5.4.0-47-generic
mv: cannot stat '/boot/initrd.img-5.4.0-47-generic.new': No such file or
directory
I don't see any information about what went wrong though. The disk isn't
full, so that's not the prob
signed) => Seth Forshee (sforshee)
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received thi
** Description changed:
+ SRU Justification
+
+ Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the
+ lowlatency kernel since we expected most RT users to use that kernel.
+ However we are getting RT regressions with the generic kernel. Digging
+ deeper into this option, it seems t
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oracle (Ubuntu)
Importance:
This should be point at linux-5.4 and not linux-signed-5.4.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1861446
Title:
on focal 'ubuntu-bug linux' doesn't automatically
Adding kmod, since the error comes from depmod.
The file it's complaining about is relatively new (added in 5.2
timeframe iirc), and we haven't been shipping it. However as of 5.4.0-17
we are shipping it in linux-modules. I've confirmed that
/lib/modules/5.4.0-17-generic/modules.builtin.bin is the
Sorry, I was getting that confused with another file,
modules.builtin.modinfo. That was the one we just added to linux-
modules.
modules.builtin.bin is generated by depmod, and if I remove the file for
a given kernel and run depmod I get these messages. So this looks like
something fully from depm
The powerd main thread only ever checks fb_state with the mutex locked,
and the monitor thread only ever changes it with the mutex locked. The
main thread also only calls pthread_cond_wait() *after* finding fb_state
!= FB_AWAKE *without any intervening unlock of the mutex.* So the
scenario you desc
Yeah it seems likely that some driver is probably being slow in its
late_resume handler. There may be something in dmesg which shows how
long individual late_resume calls are making, I can't remember (there
may also be some debug option which has to be enabled).
Iirc the reason we have to wait for
ngs should still just work, but potentially there are some corner
cases which still rely on the fallback.
In the end I guess we probably ought to change it though.
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) =&
It looks like I don't have any of the affected hardware. I put up a test
build at the link below; Sebastien, could you give it a try (with the
workaround removed obviously) and confirm that it fixes the problem?
http://people.canonical.com/~sforshee/lp1398458/linux-3.18.0-5.6+lp1398458v20141203102
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
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/1398458
Title:
kernel fails to load iwlwifi firmware
I used https://github.com/mcgrof/fake-firmware-test to confirm that
disabling CONFIG_FW_LOADER_USER_HELPER eliminates use of the user helper
and the associated delay when the firmware is missing. Patch has been
sent to the kernel team mailing list.
--
You received this bug notification because yo
This is still happening, and it feels like a race. I've enabled debug
logging and captured the journal from good and bad boots. Comparing them
hasn't told me a whole lot; on the whole the udev debug logging isn't
very applicable. I do see that in both cases udev starts up and reads
the exact same s
** Attachment added: "Output of 'journalctl -xb' from a good boot"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+attachment/4751946/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to syste
** Attachment added: "Output of 'journalctl -xb' from a failed boot"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+attachment/4751944/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sys
** Attachment added: "Output of 'udevadm info --export-db' from a failed boot"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+attachment/4751945/+files/udev-db.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
** Attachment added: "Output of 'udevadm info --export-db' from a good boot"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+attachment/4751947/+files/udev-db.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
Based on feedback from @jjohansen there will be follow-up patches to fix
the problems, but the patches already applied should be kept and do not
need to be reverted.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
Public bug reported:
Since upgrading this machine to yakkety I've seen periodic hangs during
booting. If I wait long enough systemd give up and drops to maintenance
mode. Looking in the journal I see events like this:
Sep 19 08:24:22 ubuntu-xps13 systemd[1]: dev-disk-by\x2duuid-
63cd6483\x2ddf95\
** Attachment added: "Output of 'udevadm info --export-db'"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+attachment/4743665/+files/udev-db.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in U
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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
Verified that i915_bpo.ko in 4.4.0-34.53 reflects the PCI id changes
from the patches.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm
I'm seeing a direct correlation here between the symptom and the kernel
emitting uevents. For example, in the host run:
$ udevadm --monitor
And in another terminal in the host run:
# losetup /dev/loop0 foo
This causes the symptoms even though it has no direct impact on the
container, but does
@Amr: We cannot add this firmware to Ubuntu without a license from
Broadcom which allows redistribution. As far as I can see the sources
posted so far do not include such a license. Do you know of any sources
which do?
** Changed in: linux-firmware (Ubuntu)
Status: Confirmed => Incomplete
Public bug reported:
After changing the timezone the time displayed in the date/time
indicator is still in my old time zone. I sent a signal to the
indicator-datetime-service process, and after it restarted the correct
time was displayed.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: indi
It looks like apparmor isn't allowing the mount.
[ 7963.575900] audit: type=1400 audit(1416145652.685:70):
apparmor="DENIED" operation="mount" info="failed mntpnt match" error=-13
profile="/usr/lib/lightdm/lightdm-guest-session"
name="/run/user/127/gvfs/" pid=7101 comm="gvfsd-fuse" fstype="fuse
.g
=> Confirmed
** Changed in: indicator-network (Ubuntu)
Assignee: Seth Forshee (sforshee) => Antti Kaijanmäki (kaijanmaki)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.la
All right, it turns out I didn't run ubuntu-device-flash the right way
and ended up with an old image. I tested with devel-proposed, and I'd
say that it's mostly fixed.
The UI is there, and I can use it to connect to a hidden network, but I
did have a few of problems. First, when the keyboard was
Public bug reported:
After connecting to a hidden wifi network the indicator does not
correctly show the connection status. Instead of the "connected" icon in
the top bar there's just a blank space, the hidden network shows up in
the indicator's network list twice, and there's no check mark next t
** Attachment added: "indicator-3.png"
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+attachment/4173011/+files/indicator-3.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network i
** Attachment added: "menumodel.txt"
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+attachment/4173014/+files/menumodel.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ub
** Attachment added: "nmcli_d_wifi_list.txt"
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+attachment/4173015/+files/nmcli_d_wifi_list.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicat
** Attachment added: "indicator-2.png"
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+attachment/4173010/+files/indicator-2.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network i
** Attachment added: "actiongroup.txt"
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+attachment/4173013/+files/actiongroup.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network i
Okay - bug #1354560.
Just one note though - bug #1333135 talks specifically about landscape
orientation, but I was using the phone in portrait orientation.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
This isn't really a problem with powerd. As far as I know there's no
standard interface (and likely as not no interface at all) for telling
an input driver to stop sending events other than closing the input
device, and powerd can't close the device on behalf of another process.
The input stack nee
Why isn't it valid for the system CPU to suspend during a phone call?
Does android enforce such a restriction?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powerd in Ubuntu.
https://bugs.launchpad.net/bugs/1359530
Title:
It looks like the disconnections are initiated by NetworkManager, which
gives the reason 'ip-config-unavailable'. Maybe some kind of dhcp
problem, I'm not sure. Right now it isn't looking like a driver problem
but something higher in the stack, so I'm updating the bug to affect
network manager so t
As far as the errors from the driver goes, the first one I see is "could
not activate Heartbeat timer" (not sure yet what the heartbeat timer
does, perhaps expiring peer STAs in the IBSS network when beacons aren't
seen for some period). This is printed using some internal logging
functions and has
101 - 172 of 172 matches
Mail list logo
