[Touch-packages] [Bug 1354560] [NEW] Indicator doesn't show connected status when associated with hidden network

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 to

[Touch-packages] [Bug 1354560] Re: Indicator doesn't show connected status when associated with hidden network

** 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 in

[Touch-packages] [Bug 1354560] Re: Indicator doesn't show connected status when associated with hidden network

** 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

[Touch-packages] [Bug 1354560] Re: Indicator doesn't show connected status when associated with hidden network

** 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

[Touch-packages] [Bug 1354560] Re: Indicator doesn't show connected status when associated with hidden network

** 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 in

[Touch-packages] [Bug 1354560] Re: Indicator doesn't show connected status when associated with hidden network

** 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 in

[Touch-packages] [Bug 1202806] Re: [mako] Cannot connect to hidden wifi network (touch|android)

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

[Touch-packages] [Bug 1393206] Re: SD/mmc card with exFAT fs not automatically mounted since upgrade to utopic

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 .gvfsd-fuse

[Touch-packages] [Bug 1398458] Re: kernel fails to load iwlwifi firmware - disable CONFIG_FW_LOADER_USER_HELPER

** 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

[Touch-packages] [Bug 1398458] Re: kernel fails to load iwlwifi firmware - disable CONFIG_FW_LOADER_USER_HELPER

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

[Touch-packages] [Bug 1337239] Re: Digitiser still works when phone locked

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

[Touch-packages] [Bug 1359530] Re: Device trying to suspend when screen is turned off by proximity sensor (during a call)

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:

[Touch-packages] [Bug 1355441] Re: Wifi dropping

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

[Touch-packages] [Bug 1337753] Re: [mako] can not create an ad-hoc network

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

[Touch-packages] [Bug 1398458] Re: kernel fails to load iwlwifi firmware - disable CONFIG_FW_LOADER_USER_HELPER

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) = Seth Forshee

[Touch-packages] [Bug 1398458] Re: kernel fails to load iwlwifi firmware - disable CONFIG_FW_LOADER_USER_HELPER

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?

[Touch-packages] [Bug 1450017] Re: Sometimes resuming leaves only a black lit screen, no unity8

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

[Touch-packages] [Bug 1421455] Re: Slow wake up time on physical power button pressed

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

[Touch-packages] [Bug 1464442] Re: installing or upgrading libc6 in Trusty removes all content from /tmp directory

In addition to the requested logs could someone provide steps to reproduce, preferably in a VM without MAAS? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1464442 Title:

[Touch-packages] [Bug 1464442] Re: installing or upgrading libc6 in Trusty removes all content from /tmp directory

I've also reproduced it in a VM using Stefan's method. Both Stefan and I have verified that stubbing out or removing /etc/init/mounted-tmp.conf eliminates the problem, so it seems that this job is getting triggered somehow. -- You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 1464442] Re: installing or upgrading libc6 in Trusty removes all content from /tmp directory

Also I forgot to mention that Chris Arges pointed out that there's a eglibc postinst script which does a re-exec of upstart, which is an important piece of the puzzle. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in

[Touch-packages] [Bug 1464442] Re: installing or upgrading libc6 in Trusty removes all content from /tmp directory

http://paste.ubuntu.com/11768305/ That link shows upstart-monitor output during the libc6 upgrade. I see the mountall job starting, then later I see a mounted event for /tmp which triggers the mounted-tmp job, which is what ends up clearing out /tmp. In fact, generally it looks to me like many of

[Touch-packages] [Bug 1485659] [NEW] Date/time indicator doesn't update after changing time zone

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:

[Touch-packages] [Bug 1498162] Re: unable to make backup link of `./usr/sbin/uuidd' before installing new version: Operation not permitted

** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member

[Touch-packages] [Bug 1498162] Re: unable to make backup link of `./usr/sbin/uuidd' before installing new version: Operation not permitted

I have a fix, but I will want to run it by upstream before we apply it to be sure we aren't opening up any security issues. In the meantime I've put up a test build, please give it a try and verify that the uuid- runtime upgrade can be successfully installed.

[Touch-packages] [Bug 1506888] Re: wifi status not remembered after reboot

Losing the state when using the network indicator sounds like a network- manager bug, so I'm going to change this to affecting that package. The issue when using a key could be caused by network-manager, the kernel, or your system firmware depending on how it's implemented for your machine. **

[Touch-packages] [Bug 1530617] Re: FUSE in wily image with upstart installed causes chaos

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

[Touch-packages] [Bug 1366418] Re: Bluetooth BCM43142A0 doesn’t work

@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

[Touch-packages] [Bug 1600124] Re: Adjust KBL PCI-ID's

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

[Touch-packages] [Bug 1600124] Re: Adjust KBL PCI-ID's

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

[Touch-packages] [Bug 1625217] Re: udev sometimes doesn't apply systemd tag to devices

** 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

[Touch-packages] [Bug 1625217] [NEW] udev sometimes doesn't apply systemd tag to devices

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-

[Touch-packages] [Bug 1625217] Re: udev sometimes doesn't apply systemd tag to devices

** 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

[Touch-packages] [Bug 1625217] Re: udev sometimes doesn't apply systemd tag to devices

** 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

[Touch-packages] [Bug 1625217] Re: udev sometimes doesn't apply systemd tag to devices

** 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

[Touch-packages] [Bug 1625217] Re: udev sometimes doesn't apply systemd tag to devices

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

[Touch-packages] [Bug 1625217] Re: udev sometimes doesn't apply systemd tag to devices

** 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

[Touch-packages] [Bug 1611078] Re: Support snaps inside of lxd containers

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

[Touch-packages] [Bug 1611078] Re: Support snaps inside of lxd containers

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

[Touch-packages] [Bug 1672542] Re: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

It does seem to be something in zesty. Not in the kernel though, I tried xenial and yakkety kernels with zesty userspace and still got the hang. But when I use a zesty kernel with yakkety userspace I don't see it. -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1677377] [NEW] ADT failure in boot-smoke test with linux-hwe-edge

Public bug reported: ADT boot-smoke test fails with 4.10 hwe-edge kernel in xenial. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial/xenial/amd64/s/systemd/20170329_130746_29365@/log.gz checking that there are no running jobs FAIL:

[Touch-packages] [Bug 1674679] [NEW] lxc autopkgtest fails if http_proxy not set

Public bug reported: debian/tests/exercise fails if http_proxy is not set, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/amd64/l/lxc/20170320_194539_28897@/log.gz Since the script uses 'set -e' the expression 'if [ -n

[Touch-packages] [Bug 1672542] Re: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

The cause seems to be that TEST-12-ISSUE-3171 is hanging. I've reproduced the problem with the 4.10.0-11 and 4.10.0-13 kernels and with systemd 232-18ubuntu1 and 232-19. I'm attaching the journal from one of the test runs, taken from within the nspawn container while the test was hung (using linux

[Touch-packages] [Bug 1679598] Re: TEST-03-JOBS faliing in ADT

Here's an example with the test passing for the same kernel/systemd versions as fail later (4.10.0-15/232-19): https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/amd64/s/systemd/20170328_002748_44e26@/log.gz -- You received this

[Touch-packages] [Bug 1679764] Re: systemd 232-21ubuntu2 ADT test failure with linux-raspi2 4.10.0-1001.3

Note that the "error: org.freedesktop.systemd1.NoSuchUnit: Unit c.service not found." is reported in bug #1672499. -- 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/1679764

[Touch-packages] [Bug 1679764] Re: systemd 232-21ubuntu2 ADT test failure with linux-raspi2 4.10.0-1001.3

autopkgtest [17:28:29]: test boot-smoke: [--- reboot #0 bash: line 1: 32362 Killed /tmp/autopkgtest.eXsKq9/build.l7Q/systemd-232/debian/tests/boot-smoke 2> >(tee -a /tmp/autopkgtest.eXsKq9/boot-smoke-stderr >&2) > >(tee -a

[Touch-packages] [Bug 1679764] [NEW] systemd 232-21ubuntu2 ADT test failure with linux-raspi2 4.10.0-1001.3

Public bug reported: Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/armhf/s/systemd/20170329_172954_1ba5b@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New **

[Touch-packages] [Bug 1672542] Re: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

Confirmed that the test in the 232-21ubuntu3 source package no longer hangs. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1671216] [NEW] ColdplugWifi test failures in ADT

Public bug reported: We're seeing intermittent kernel ADT test failues against network- manager due to the ColdplugWifi test timing out. This is happening across multiple releases. Here's an example from xenial:

[Touch-packages] [Bug 1672499] [NEW] systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on armhf

Public bug reported: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/armhf/s/systemd/20170310_221057_b5cf9@/log.gz root-unittests fails: -> Unit a.service: Description: a.service Instance:

[Touch-packages] [Bug 1672542] [NEW] systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170313_204550_ecb32@/log.gz i386:

[Touch-packages] [Bug 1710654] Re: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12

There are quite a few messages like these that lead me to believe where running out of inotify watches. Failed to acquire watch file descriptor: Too many open files path-exists.path: Failed to enter waiting state: Too many open files -- You received this bug notification because you are a

[Touch-packages] [Bug 1710654] Re: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12

networkd-test.py FAIL non-zero exit status 1 root-unittests FAIL non-zero exit status 1 networkd-test: == FAIL: test_catchall_config (__main__.UnmanagedClientTest) Verify link states with a catch-all config, hot-plug.

[Touch-packages] [Bug 1710654] [NEW] systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12

Public bug reported: Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170814_062054_7f9b9@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New **

[Touch-packages] [Bug 1700806] Re: systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5

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

[Touch-packages] [Bug 1692543] Re: Regression tests cannot write to apparmor path_max module parameter in artful/4.11

This patch fixes the tests for me. Turns out that we can't simply skip writing to path_max as that seems to break the test case completely, so I changed it to print an XFAIL message and abort the test. ** Patch added: "fix-longpath-test.patch"

[Touch-packages] [Bug 1700211] Re: package linux-firmware 1.157.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

E: /usr/share/initramfs-tools/hooks/casper-memdisk failed with return 1. This seems to be related to an initramfs hook for casper, so marking this bug as also affecting casper. ** Also affects: casper (Ubuntu) Importance: Undecided Status: New -- You received this bug notification

[Touch-packages] [Bug 1700806] Re: systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5

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

[Touch-packages] [Bug 1700806] [NEW] systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5

Public bug reported: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/systemd/20170627_083238_11cda@/log.gz ** Affects: systemd (Ubuntu) Importance:

[Touch-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes

Zesty already has the latest 7260 firmware (revision 459231), and according to the attached CurrentDmesg.txt that's what being using: [8.000329] iwlwifi :01:00.0: loaded firmware version 17.459231.0 op_mode iwlmvm -- You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 1707267] [NEW] systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-9.10

Public bug reported: Testing failed on: s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/s390x/s/systemd/20170728_111056_ccb5f@/log.gz ** Affects: systemd (Ubuntu) Importance:

[Touch-packages] [Bug 1707267] Re: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-9.10

autopkgtest [11:09:53]: test boot-smoke: [--- ... checking that there are no running jobs running jobs after remaining timeout -1: 61 apt-daily-upgrade.timerstart waiting 209 systemd-hostnamed.service start running 64 NetworkManager-wait-online.service

[Touch-packages] [Bug 1692543] Re: Regression tests cannot write to apparmor path_max module parameter in artful/4.11

What if the test was changed to check writability of path_max? Just changing the the check for the sysfs path to -w won't work for root, but maybe something like this (perhaps there's a simpler way to do the check though): if [[ -f /sys/module/apparmor/parameters/path_max && $(stat -c "%a"

[Touch-packages] [Bug 1692543] Re: Regression tests cannot write to apparmor path_max module parameter in artful/4.11

Something more like this then. if [ ! -f /sys/module/apparmor/parameters/path_max ] ; then echo "WARNING: This version of AppArmor does not support changing buffer size." else mode=$(stat -c "%a" /sys/module/apparmor/parameters/path_max) if (( 8#$mode & 0222 )); then

[Touch-packages] [Bug 1691836] Re: lxc 2.0.8-0ubuntu1 ADT test failure with linux 4.11.0-3.8

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

[Touch-packages] [Bug 1691836] Re: lxc 2.0.8-0ubuntu1 ADT test failure with linux 4.11.0-3.8

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

[Touch-packages] [Bug 1692543] [NEW] Regression tests cannot write to apparmor path_max module parameter in artful/4.11

Public bug reported: The longpath regression tests tries to write to /sys/module/apparmor/parameters/path_max, but this is read-only in artful/4.11: commit cdc8e09e16bb7eb7d23fcbdbe416aa91770fb4d6 Author: John Johansen Date: Thu Apr 6 05:14:20 2017 -0700

[Touch-packages] [Bug 1691836] [NEW] lxc 2.0.8-0ubuntu1 ADT test failure with linux 4.11.0-3.8

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

[Touch-packages] [Bug 1691836] Re: lxc 2.0.8-0ubuntu1 ADT test failure with linux 4.11.0-3.8

--- 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)

[Touch-packages] [Bug 1703339] Re: Unable to install Ubuntu on the NVMe disk under VMD PCI domain

** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- 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/1703339 Title: Unable to

[Touch-packages] [Bug 1715397] [NEW] systemd 234-2ubuntu9 ADT test failure with linux 4.13.0-9.10

Public bug reported: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/systemd/20170906_131209_2a96a@/log.gz ** Affects: systemd (Ubuntu) Importance:

[Touch-packages] [Bug 1713726] Re: lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-7.8

With the latest upload tests still fail, but it seems to get slightly farther. Is this a different issue? https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful-canonical-kernel-team- unstable/artful/amd64/l/lxc/20170906_003748_d668f@/log.gz

[Touch-packages] [Bug 1715397] Re: systemd 234-2ubuntu9 ADT test failure with linux 4.13.0-9.10

I see adt failures with 4.12 as well, looks like a regression in ppc64-diag. Changing affected package. ** Package changed: systemd (Ubuntu) => ppc64-diag (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in

[Touch-packages] [Bug 1715397] Re: systemd 234-2ubuntu9 ADT test failure with linux 4.13.0-9.10

ep 06 12:23:41 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: Starting ppc64-diag rtas_errd (platform error handling) Service... Sep 06 12:23:41 6963eeea-263f-4ad0-8fdf-549bd646f5dc-adt-prepare systemd[1]: Started ppc64-diag rtas_errd (platform error handling) Service. Sep 06

[Touch-packages] [Bug 1712865] Re: systemd 234-2ubuntu6 ADT test failure with linux 4.12.0-12.13

armhf failure: == FAIL: test_search_domains_too_long (__main__.NetworkdClientTest) -- Traceback (most recent call last): File

[Touch-packages] [Bug 1712865] [NEW] systemd 234-2ubuntu6 ADT test failure with linux 4.12.0-12.13

Public bug reported: Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170823_191459_e2f1d@/log.gz s390x:

[Touch-packages] [Bug 1712865] Re: systemd 234-2ubuntu6 ADT test failure with linux 4.12.0-12.13

s390x failure: autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from proposed Reading package lists... Building dependency tree... Reading state information... Correcting dependencies...Starting pkgProblemResolver with broken

[Touch-packages] [Bug 1712865] Re: systemd 234-2ubuntu6 ADT test failure with linux 4.12.0-12.13

armhf passed after re-running, so I guess we can ignore it. Since the s390x failure is fixed in -proposed I'll close the bug as invalid, I can hint away the kernel test failure since it's clearly not a kernel issue. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received

[Touch-packages] [Bug 1713075] [NEW] lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-6.7

Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/l/lxc/20170825_140357_85137@/log.gz i386:

[Touch-packages] [Bug 1713726] [NEW] lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-7.8

Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/l/lxc/20170829_024349_c4b5f@/log.gz i386:

[Touch-packages] [Bug 1731283] Re: network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

Seems that s390x ADT does now run in VMs, which explains the change. Since we don't have wireless support in our s390x kernels, these failures are expected. Seems the tests will need to be changed to skip these tests or make them expected failures. -- You received this bug notification because

[Touch-packages] [Bug 1731283] Re: network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

Tests were previously getting skipped for s390, due to "Restrictions: ... isolation-machine" in the test control file. Possibly some sort of infrastructure problem detecting that the tests are running in a container. -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1716009] Re: problem with the sound since the latest update

I'm not sure why this was reported against alsa-drivers, you didn't report any alsa packages in those that were upgraded when the problem started. To get the bug noticed it's helpful to report the bug against the appropriate package. If you believe the issue is related to a linux- firmware update

[Touch-packages] [Bug 1733328] Re: systemd 235-2ubuntu3 ADT test failure with linux 4.14.0-7.9

** Description changed: Testing failed on: - i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/s/systemd/20171118_221900_c23d7@/log.gz - s390x:

[Touch-packages] [Bug 1733328] Re: systemd 235-2ubuntu3 ADT test failure with linux 4.14.0-7.9

amd64 also passed on retry. s390x failure is present with 4.13 kernel too, so not a regression in 4.14. -- 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/1733328 Title:

[Touch-packages] [Bug 1733328] [NEW] systemd 235-2ubuntu3 ADT test failure with linux 4.14.0-7.9

Public bug reported: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/s/systemd/20171118_221900_c23d7@/log.gz s390x:

[Touch-packages] [Bug 1733328] Re: systemd 235-2ubuntu3 ADT test failure with linux 4.14.0-7.9

Oops, didn't mean to file this yet as tests haven't completed. However there are failures already. On s390x, the test history leads me to believe that the tests started failing when we switch to running tests in VMs. Traceback (most recent call last): File

[Touch-packages] [Bug 1731283] Re: network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

autopkgtest [13:37:31]: test wpa-dhclient: [--- modprobe: FATAL: Module cfg80211 not found in directory /lib/modules/4.14.0-6-generic ERROR == ERROR: setUpClass (__main__.T)

[Touch-packages] [Bug 1731283] Re: network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

This and other errors are related to lacking the cfg80211 module, which we do not build for s390. However we did not build it in artful either, and we currently have the same version of network-manager in artful and bionic, so it's odd that the tests are failing in bionic and not in artful. --

[Touch-packages] [Bug 1731283] [NEW] network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

Public bug reported: Testing failed on: s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/n/network-manager/20171107_135937_02323@/log.gz ** Affects: network-manager (Ubuntu)

[Touch-packages] [Bug 1733328] Re: systemd 235-2ubuntu3 ADT test failure with linux 4.14.0-7.9

** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1733328 Title: systemd 235-2ubuntu3 ADT test failure with

[Touch-packages] [Bug 1776670] [NEW] systemd 237-3ubuntu10 ADT test failure with linux 4.17.0-2.3

Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz i386:

[Touch-packages] [Bug 1776669] [NEW] network-manager 1.10.6-2ubuntu1 ADT test failure with linux 4.17.0-2.3

Public bug reported: Testing failed on: s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/s390x/n/network-manager/20180613_112923_bf26d@/log.gz ** Affects: network-manager (Ubuntu)

[Touch-packages] [Bug 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present

This is not a problem with linux-firmware itself, it does is trigger a rebuild of the initrd for all installed kernels but it's initramfs-tools which does this. It will try to generate an initrd for all kernels with a file in /var/lib/initramfs-tools, so it sounds like you have a file there for

[Touch-packages] [Bug 1778551] [NEW] Add linux-modules* packages to VersionedKernelPackages

Public bug reported: == SRU Justification == Impact: The 4.15 hwe kernel includes some package shuffling, so the VersionedKernelPackages list in /etc/apt/apt.conf.d/01autoremove needs to be updated to include linux-modules* packages. Fix: Backport the conf file changes from bionic. Test Case:

[Touch-packages] [Bug 1778551] Re: Add linux-modules* packages to VersionedKernelPackages

Other than simply checking the patterns in the file, I can't think of an easier way to test. If you know of one please let me know. I do currently have a vm set up to let me test it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1778551] Re: Add linux-modules* packages to VersionedKernelPackages

Hmm, now that I actually look at how the file is used, I guess we could verify the list generated by /etc/kernel/postinst.d/apt-auto-removal, couldn't we? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu.

[Touch-packages] [Bug 1768001] Re: En Thinkpad T430 con controlador BCM20702A0

I'm afraid that the firmware files just look to be pulled out of Windows drivers downloaded from arbitrary download sites. I'd be hesitant to stick those into our linux-firmware package in any case, and without a license which allows us to redistribute the files we simply cannot distribute them in

[Touch-packages] [Bug 1727850] Re: systemd 229-4ubuntu20 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

>From journal.txt in the adt artifacts: Oct 25 13:55:35 autopkgtest systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE Oct 25 13:55:35 autopkgtest systemd[1]: lightdm.service: Unit entered failed state. Oct 25 13:55:35 autopkgtest systemd[1]: lightdm.service:

[Touch-packages] [Bug 1727850] [NEW] systemd 229-4ubuntu20 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/s/systemd/20171025_152041_0db62@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New **

  1   2   >