[Touch-packages] [Bug 2062138] Re: test-logprof.py from test_utils_testsuite / test_utils_testsuite3 in ubuntu_qrt_apparmor failing on Azure Standard_A2_v2
This issue can be found on openstack ARM64 instance with M/M-lowlatency as well. ** Changed in: apparmor (Ubuntu) Status: New => Fix Released ** Tags added: sru-20240401 sru-s20240304 ** Tags added: ubuntu-qrt-apparmor -- 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/2062138 Title: test-logprof.py from test_utils_testsuite / test_utils_testsuite3 in ubuntu_qrt_apparmor failing on Azure Standard_A2_v2 Status in ubuntu-kernel-tests: New Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Mantic: New Bug description: This issue can be found on M-generic 6.5.0-34.34 and M-lowlatency 6.5.0-27.28.1 on Azure instance Standard_A2_v2 The test-logprof.py test from ApparmorTestsuites.test_utils_testsuite and test_utils_testsuite3 failed with: $ sudo python3 ./test-logprof.py E == ERROR: test_0 (__main__.TestLogprof.test_0) test 'ping' -- Traceback (most recent call last): File "/tmp/mine/source/mantic/apparmor-4.0.0~alpha2/utils/test/common_test.py", line 90, in stub_test self._run_test(test_data, expected) File "/tmp/mine/source/mantic/apparmor-4.0.0~alpha2/utils/test/./test-logprof.py", line 99, in _run_test self.process.wait(timeout=0.2) File "/usr/lib/python3.11/subprocess.py", line 1264, in wait return self._wait(timeout=timeout) ^^^ File "/usr/lib/python3.11/subprocess.py", line 2038, in _wait raise TimeoutExpired(self.args, timeout) subprocess.TimeoutExpired: Command '['/usr/bin/python3', '../aa-logprof', '--json', '--configdir', './', '-f', './logprof/ping.auditlog', '-d', '/tmp/aa-test-7feu1ddr/profiles', '--no-check-mountpoint']' timed out after 0.2 seconds -- Ran 1 test in 1.831s FAILED (errors=1) The fail rate is almost 100%, 3 successful out of 100 attempts If you bump the timeout to 0.3 and it will pass. We need this patch to be backported to apparmor on Mantic, or keep it as a patch file in q-r-t: https://gitlab.com/apparmor/apparmor/-/commit/dd9b7b358f0dd0887767a5840ed7f7499aa50ee6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2062138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2062138] Re: test-logprof.py from test_utils_testsuite / test_utils_testsuite3 in ubuntu_qrt_apparmor failing on Azure Standard_A2_v2
** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Also affects: apparmor (Ubuntu Mantic) Importance: Undecided Status: New -- 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/2062138 Title: test-logprof.py from test_utils_testsuite / test_utils_testsuite3 in ubuntu_qrt_apparmor failing on Azure Standard_A2_v2 Status in ubuntu-kernel-tests: New Status in apparmor package in Ubuntu: New Status in apparmor source package in Mantic: New Bug description: This issue can be found on M-generic 6.5.0-34.34 and M-lowlatency 6.5.0-27.28.1 on Azure instance Standard_A2_v2 The test-logprof.py test from ApparmorTestsuites.test_utils_testsuite and test_utils_testsuite3 failed with: $ sudo python3 ./test-logprof.py E == ERROR: test_0 (__main__.TestLogprof.test_0) test 'ping' -- Traceback (most recent call last): File "/tmp/mine/source/mantic/apparmor-4.0.0~alpha2/utils/test/common_test.py", line 90, in stub_test self._run_test(test_data, expected) File "/tmp/mine/source/mantic/apparmor-4.0.0~alpha2/utils/test/./test-logprof.py", line 99, in _run_test self.process.wait(timeout=0.2) File "/usr/lib/python3.11/subprocess.py", line 1264, in wait return self._wait(timeout=timeout) ^^^ File "/usr/lib/python3.11/subprocess.py", line 2038, in _wait raise TimeoutExpired(self.args, timeout) subprocess.TimeoutExpired: Command '['/usr/bin/python3', '../aa-logprof', '--json', '--configdir', './', '-f', './logprof/ping.auditlog', '-d', '/tmp/aa-test-7feu1ddr/profiles', '--no-check-mountpoint']' timed out after 0.2 seconds -- Ran 1 test in 1.831s FAILED (errors=1) The fail rate is almost 100%, 3 successful out of 100 attempts If you bump the timeout to 0.3 and it will pass. We need this patch to be backported to apparmor on Mantic, or keep it as a patch file in q-r-t: https://gitlab.com/apparmor/apparmor/-/commit/dd9b7b358f0dd0887767a5840ed7f7499aa50ee6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2062138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)
Hints removed, closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- 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/1886790 Title: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test) Status in ubuntu-kernel-tests: Fix Released Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Bionic: Fix Released Bug description: [ Impact ] * The device_add_remove_test test fails on the affected series (e.g. Bionic). * Having the test fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for this test. [ Test Plan ] * Run the affected test on an affected series (e.g. Bionic). * The test should pass. [ Where problems could occur ] * The regression risk is very low, and the changes only affect the tests, so the regression scope is minimal. [ Other Info ] Upstream drop of network_latency: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3082a674f46fe49383b157882c41dfabaa37113 Related to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587 Original bug report: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note that this testcase is successful on Focal with the same kernel version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1979258] Re: lxc: lxc-test-parse-config-file failed (failed to set config item)
Thanks! I have checked with our test result, this is not affecting newer kernels any more. But it's still visible <= Jammy (lxc-5.0.0~git2209-g5a7b9ce67). Looks like we will need to backport this. ** Changed in: lxc (Ubuntu) Status: New => Fix Released ** Changed in: lxc (Ubuntu Jammy) Status: New => Confirmed -- 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/1979258 Title: lxc: lxc-test-parse-config-file failed (failed to set config item) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Jammy: Confirmed Bug description: With bug 1943441 (expected value and retrieved value do not match) fixed with lxc 1:4.0.12-0ubuntu1 on Jammy (still exist on F / I) Now this test on Jammy with lxc 1:5.0.0~git2209-g5a7b9ce67-0ubuntu1 will fail with: Running '/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file' parse_config_file.c: 49: set_get_compare_clear_save_load: failed to set config item "lxc.selinux.context" to "system_u:system_r:lxc_t:s0:c22" parse_config_file.c: 49: set_get_compare_clear_save_load: failed to set config item "lxc.seccomp.profile" to "/some/seccomp/file" parse_config_file.c: 580: main: lxc.seccomp.profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1979258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961566] Re: 5.15 kernel selftest srv6_end_dt6_l3vpn_test.sh failure
** Also affects: iproute2 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: iproute2 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: iproute2 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: iproute2 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/1961566 Title: 5.15 kernel selftest srv6_end_dt6_l3vpn_test.sh failure Status in ubuntu-kernel-tests: New Status in iproute2 package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in iproute2 source package in Focal: New Status in linux source package in Focal: New Status in iproute2 source package in Jammy: Fix Released Status in linux source package in Jammy: Confirmed Bug description: Kernel selftest srv6_end_dt6_l3vpn_test.sh fails on s2lp4.s390x: # selftests: net: srv6_end_dt6_l3vpn_test.sh # Error: either "to" is duplicate, or "vrftable" is a garbage. # Error: either "to" is duplicate, or "vrftable" is a garbage. # Error: either "to" is duplicate, or "vrftable" is a garbage. # Error: either "to" is duplicate, or "vrftable" is a garbage. ... # # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant # # # TEST: Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [FAIL] # # TEST: Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [FAIL] # # TEST: Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1961566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040484] Re: ubuntu_seccomp pseudo-syscall fails on s390 / PowerPC
** Tags added: 4.4 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/2040484 Title: ubuntu_seccomp pseudo-syscall fails on s390 / PowerPC Status in ubuntu-kernel-tests: New Status in libseccomp package in Ubuntu: New Bug description: libseccomp upstream has changed the test code for 29-sim- pseudo_syscall.c, which has broken it for s390. Perhaps s390 has been broken since forever and the test change is just uncovering it. We need to investigate if the fix would be needed in the test, libseccomp or the kernel. This seems to affect at least 4.4 and 5.4 kernels, but may affect everything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2040484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040484] Re: ubuntu_seccomp pseudo-syscall fails on s390 / PowerPC
** Summary changed: - ubuntu_seccomp pseudo-syscall fails on s390 + ubuntu_seccomp pseudo-syscall fails on s390 / PowerPC -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/2040484 Title: ubuntu_seccomp pseudo-syscall fails on s390 / PowerPC Status in ubuntu-kernel-tests: New Status in libseccomp package in Ubuntu: New Bug description: libseccomp upstream has changed the test code for 29-sim- pseudo_syscall.c, which has broken it for s390. Perhaps s390 has been broken since forever and the test change is just uncovering it. We need to investigate if the fix would be needed in the test, libseccomp or the kernel. This seems to affect at least 4.4 and 5.4 kernels, but may affect everything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2040484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040484] Re: ubuntu_seccomp pseudo-syscall fails on s390
This issue can be found on ppc64el (openstack VM) as well, all the way from 5.4 to 6.5 ** Tags added: 5.15 5.4 6.2 6.5 focal jammy lunar mantic ppc64el s390x sru-20231030 ubuntu-seccomp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/2040484 Title: ubuntu_seccomp pseudo-syscall fails on s390 Status in ubuntu-kernel-tests: New Status in libseccomp package in Ubuntu: New Bug description: libseccomp upstream has changed the test code for 29-sim- pseudo_syscall.c, which has broken it for s390. Perhaps s390 has been broken since forever and the test change is just uncovering it. We need to investigate if the fix would be needed in the test, libseccomp or the kernel. This seems to affect at least 4.4 and 5.4 kernels, but may affect everything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2040484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943441] Re: lxc: lxc-test-parse-config-file failure (expected value and retrieved value do not match)
** Merge proposal unlinked: https://code.launchpad.net/~canonical-kernel-team/+git/rt-hints/+merge/440756 -- 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/1943441 Title: lxc: lxc-test-parse-config-file failure (expected value and retrieved value do not match) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Focal: New Status in lxc source package in Impish: Confirmed Bug description: I'm getting the following error with the lxc kernel autotest on impish: 08:46:04 DEBUG| parse_config_file.c: 60: set_get_compare_clear_save_load: expected value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key "lxc.selinux.context" do not match 08:46:04 DEBUG| 08:46:04 DEBUG| parse_config_file.c: 382: main: lxc.selinux.context 08:46:06 INFO | ERRORubuntu_lxc.lxc-test-parse-config-file ubuntu_lxc.lxc-test-parse-config-filetimestamp=1631090766localtime=Sep 08 08:46:06Command failed, rc=1, Command returned non-zero exit status * Command: /tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file Exit status: 1 Duration: 0.0550210475922 stderr: parse_config_file.c: 60: set_get_compare_clear_save_load: expected value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key "lxc.selinux.context" do not match parse_config_file.c: 382: main: lxc.selinux.context I haven't investigated very much, but it looks like a (mis)configuration change / issue. Does it ring any bell? Otherwise I'll investigate more. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1943441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)
** Tags removed: sru-2023-01-30 ** Tags added: sru-20230130 -- 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/1886790 Title: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Bionic: Triaged Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note that this testcase is successful on Focal with the same kernel version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2000359] Re: posix_ipc in test_regression_testsuite from ubuntu_qrt_apparmor failed on K-5.19 arm64 (Unable to run test sub-executable)
Test re-triggered and passed, hints removed. Closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: apparmor (Ubuntu) Status: New => Fix Released ** Changed in: apparmor (Ubuntu Kinetic) Status: New => Invalid -- 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/2000359 Title: posix_ipc in test_regression_testsuite from ubuntu_qrt_apparmor failed on K-5.19 arm64 (Unable to run test sub-executable) Status in QA Regression Testing: Fix Released Status in ubuntu-kernel-tests: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Kinetic: Invalid Bug description: Issue found on Kinetic 5.19 ARM64 systems, The ApparmorTestsuites.test_regression_testsuite in ubuntu_qrt_apparmor will fail with posix_ipc test: running posix_ipc Fatal Error (posix_mq_rcv): Unable to run test sub-executable It's a bit hard to find which one is failing, here is the test output of ApparmorTestsuites.test_regression_testsuite: == BEGIN OF TEST OUPTUT == running aa_exec running access xfail: ACCESS file rx (r) xfail: ACCESS file rwx (r) xfail: ACCESS file r (wx) xfail: ACCESS file rx (wx) xfail: ACCESS file rwx (wx) xfail: ACCESS dir rwx (r) xfail: ACCESS dir r (wx) xfail: ACCESS dir rx (wx) xfail: ACCESS dir rwx (wx) running at_secure running introspect running capabilities (ptrace) (sethostname) (setdomainname) (setpriority) (setscheduler) (reboot) (chroot) (mlockall) (net_raw) running changeprofile running onexec running changehat running changehat_fork running changehat_misc *** A 'Killed' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309514 Killed $testexec "$@" > $outfile 2>&1 *** A 'Killed' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309547 Killed $testexec "$@" > $outfile 2>&1 running chdir running clone running coredump *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309797 Segmentation fault (core dumped) $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309826 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309861 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309896 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309931 Segmentation fault $testexec "$@" > $outfile 2>&1 XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement) running deleted running environ running exec running exec_qual running fchdir running fd_inheritance running fork running i18n running link running link_subset running mkdir running mmap running mount using mount rules ... running mult_mount running named_pipe running namespaces running net_raw running open running openat running pipe running pivot_root kernel does not support pivot_root domain transitions - skipping tests ... running posix_ipc Fatal Error (posix_mq_rcv): Unable to run test sub-executable running ptrace using ptrace v6 tests ... running pwrite running query_label running regex running rename running readdir running rw running socketpair running swap running sd_flags running setattr running symlink running syscall WARNING: syscall sysctl not supported by kernel headers, skipping tests ... running sysv_ipc Required feature 'ipc/sysv_mqueue' not available.. Skipping tests ... running tcp running unix_fd_server running unix_socket_pathname xpass: AF_UNIX pathname socket (dgram); confined server w/ access (rw) xpass: AF_UNIX pathname socket (dgram); confined client w/
[Touch-packages] [Bug 2000359] Re: posix_ipc in test_regression_testsuite from ubuntu_qrt_apparmor failed on K-5.19 arm64 (Unable to run test sub-executable)
I can confirm this has passed with K-aws 5.19.0-1016.17 ARM64 Thanks! ** Also affects: qa-regression-testing Importance: Undecided Status: New ** Changed in: qa-regression-testing Status: New => Fix Released -- 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/2000359 Title: posix_ipc in test_regression_testsuite from ubuntu_qrt_apparmor failed on K-5.19 arm64 (Unable to run test sub-executable) Status in QA Regression Testing: Fix Released Status in ubuntu-kernel-tests: New Status in apparmor package in Ubuntu: New Status in apparmor source package in Kinetic: New Bug description: Issue found on Kinetic 5.19 ARM64 systems, The ApparmorTestsuites.test_regression_testsuite in ubuntu_qrt_apparmor will fail with posix_ipc test: running posix_ipc Fatal Error (posix_mq_rcv): Unable to run test sub-executable It's a bit hard to find which one is failing, here is the test output of ApparmorTestsuites.test_regression_testsuite: == BEGIN OF TEST OUPTUT == running aa_exec running access xfail: ACCESS file rx (r) xfail: ACCESS file rwx (r) xfail: ACCESS file r (wx) xfail: ACCESS file rx (wx) xfail: ACCESS file rwx (wx) xfail: ACCESS dir rwx (r) xfail: ACCESS dir r (wx) xfail: ACCESS dir rx (wx) xfail: ACCESS dir rwx (wx) running at_secure running introspect running capabilities (ptrace) (sethostname) (setdomainname) (setpriority) (setscheduler) (reboot) (chroot) (mlockall) (net_raw) running changeprofile running onexec running changehat running changehat_fork running changehat_misc *** A 'Killed' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309514 Killed $testexec "$@" > $outfile 2>&1 *** A 'Killed' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309547 Killed $testexec "$@" > $outfile 2>&1 running chdir running clone running coredump *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309797 Segmentation fault (core dumped) $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309826 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309861 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309896 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309931 Segmentation fault $testexec "$@" > $outfile 2>&1 XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement) running deleted running environ running exec running exec_qual running fchdir running fd_inheritance running fork running i18n running link running link_subset running mkdir running mmap running mount using mount rules ... running mult_mount running named_pipe running namespaces running net_raw running open running openat running pipe running pivot_root kernel does not support pivot_root domain transitions - skipping tests ... running posix_ipc Fatal Error (posix_mq_rcv): Unable to run test sub-executable running ptrace using ptrace v6 tests ... running pwrite running query_label running regex running rename running readdir running rw running socketpair running swap running sd_flags running setattr running symlink running syscall WARNING: syscall sysctl not supported by kernel headers, skipping tests ... running sysv_ipc Required feature 'ipc/sysv_mqueue' not available.. Skipping tests ... running tcp running unix_fd_server running unix_socket_pathname xpass: AF_UNIX pathname socket (dgram); confined server w/ access (rw) xpass: AF_UNIX pathname socket (dgram); confined client w/ access (rw) running unix_socket_abstract running
[Touch-packages] [Bug 2000359] Re: posix_ipc in test_regression_testsuite from ubuntu_qrt_apparmor failed on K-5.19 arm64 (Unable to run test sub-executable)
This issue can be found on other non-x64 instances, like Power9 and s390x. ** Tags added: arm64 ppc64el s390x -- 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/2000359 Title: posix_ipc in test_regression_testsuite from ubuntu_qrt_apparmor failed on K-5.19 arm64 (Unable to run test sub-executable) Status in ubuntu-kernel-tests: New Status in apparmor package in Ubuntu: New Status in apparmor source package in Kinetic: New Bug description: Issue found on Kinetic 5.19 ARM64 systems, The ApparmorTestsuites.test_regression_testsuite in ubuntu_qrt_apparmor will fail with posix_ipc test: running posix_ipc Fatal Error (posix_mq_rcv): Unable to run test sub-executable It's a bit hard to find which one is failing, here is the test output of ApparmorTestsuites.test_regression_testsuite: == BEGIN OF TEST OUPTUT == running aa_exec running access xfail: ACCESS file rx (r) xfail: ACCESS file rwx (r) xfail: ACCESS file r (wx) xfail: ACCESS file rx (wx) xfail: ACCESS file rwx (wx) xfail: ACCESS dir rwx (r) xfail: ACCESS dir r (wx) xfail: ACCESS dir rx (wx) xfail: ACCESS dir rwx (wx) running at_secure running introspect running capabilities (ptrace) (sethostname) (setdomainname) (setpriority) (setscheduler) (reboot) (chroot) (mlockall) (net_raw) running changeprofile running onexec running changehat running changehat_fork running changehat_misc *** A 'Killed' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309514 Killed $testexec "$@" > $outfile 2>&1 *** A 'Killed' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309547 Killed $testexec "$@" > $outfile 2>&1 running chdir running clone running coredump *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309797 Segmentation fault (core dumped) $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309826 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309861 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309896 Segmentation fault $testexec "$@" > $outfile 2>&1 *** A 'Segmentation Fault' message from bash is expected for the following test /tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc: line 264: 309931 Segmentation fault $testexec "$@" > $outfile 2>&1 XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement) running deleted running environ running exec running exec_qual running fchdir running fd_inheritance running fork running i18n running link running link_subset running mkdir running mmap running mount using mount rules ... running mult_mount running named_pipe running namespaces running net_raw running open running openat running pipe running pivot_root kernel does not support pivot_root domain transitions - skipping tests ... running posix_ipc Fatal Error (posix_mq_rcv): Unable to run test sub-executable running ptrace using ptrace v6 tests ... running pwrite running query_label running regex running rename running readdir running rw running socketpair running swap running sd_flags running setattr running symlink running syscall WARNING: syscall sysctl not supported by kernel headers, skipping tests ... running sysv_ipc Required feature 'ipc/sysv_mqueue' not available.. Skipping tests ... running tcp running unix_fd_server running unix_socket_pathname xpass: AF_UNIX pathname socket (dgram); confined server w/ access (rw) xpass: AF_UNIX pathname socket (dgram); confined client w/ access (rw) running unix_socket_abstract running unix_socket_unnamed xpass: AF_UNIX unnamed socket (dgram); confined server (peer label w/ implicit perms) xpass: AF_UNIX unnamed socket (dgram); confined server (peer label w/
[Touch-packages] [Bug 2000359] Re: posix_ipc in test_regression_testsuite from ubuntu_qrt_apparmor failed on K-5.19 arm64 (Unable to run test sub-executable)
Add "set -x" to posix_mq.sh script will give us some clue about this
failure:
+ do_tests 'unconfined root' pass pass pass pass
+ prefix='unconfined root'
+ expect_send=pass
+ expect_recv=pass
+ expect_open=pass
+ all_args=("$@")
+ rest_args=("${all_args[@]:5}")
+ do_test 'unconfined root' pass
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/posix_mq_snd
pass -c
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/posix_mq_snd
-k /queuename
+ local 'desc=POSIX MQUEUE (unconfined root)'
+ shift
+ runchecktest 'POSIX MQUEUE (unconfined root)' pass
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/posix_mq_snd
pass -c
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/posix_mq_snd
-k /queuename
+ '[' -z '' ']'
+ trap error_handler ERR
+ runtestfg 'POSIX MQUEUE (unconfined root)' pass
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/posix_mq_snd
pass -c
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/posix_mq_snd
-k /queuename
+ _testdesc='POSIX MQUEUE (unconfined root)'
+ '[' p == x ']'
+ _pfmode=pass
+ _known=
+ shift 2
+ genrunscript
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/posix_mq_snd
pass -c
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/posix_mq_snd
-k /queuename
+ local runfile
+ '[' false = true ']'
+ _pid=383471
+ wait 383471
+
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/posix_mq_rcv
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/posix_mq_snd
pass -c
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/posix_mq_snd
-k /queuename
+ test_rc=1
+ '[' 1 -gt 128 ']'
+ checktestfg
+ local ret expectedsig killedsig
++ cat /tmp/sdtest.383410-8658-VS6Rmq/output.posix_mq_rcv
+ ret='Unrecognized option
Usage:
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/posix_mq_rcv
[options]
Options are:
-nget notified if there'\''s an item in the queue
available options are: mq_notify, select, poll and epoll
-kmessage queue name (default is /testmq)
-cpath of the client binary
-urun test as specified UID
-ttimeout in seconds'
It's the posix_mq_rcv binary in command:
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/posix_mq_rcv
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/posix_mq_snd
pass -c
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/posix_mq_snd
-k /queuename
Complaining "Unrecognized option" here.
It's unclear why this issue is only affecting Kinetic arm64 for the moment.
** Tags added: sru-20221114 ubuntu-qrt-apparmor
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Description changed:
Issue found on Kinetic 5.19 ARM64 systems,
The ApparmorTestsuites.test_regression_testsuite in ubuntu_qrt_apparmor
will fail with posix_ipc test:
running posix_ipc
Fatal Error (posix_mq_rcv): Unable to run test sub-executable
It's a bit hard to find which one is failing, here is the test output of
ApparmorTestsuites.test_regression_testsuite:
== BEGIN OF TEST OUPTUT ==
running aa_exec
running access
xfail: ACCESS file rx (r)
xfail: ACCESS file rwx (r)
xfail: ACCESS file r (wx)
xfail: ACCESS file rx (wx)
xfail: ACCESS file rwx (wx)
xfail: ACCESS dir rwx (r)
xfail: ACCESS dir r (wx)
xfail: ACCESS dir rx (wx)
xfail: ACCESS dir rwx (wx)
running at_secure
running introspect
running capabilities
- (ptrace)
- (sethostname)
- (setdomainname)
- (setpriority)
- (setscheduler)
- (reboot)
- (chroot)
- (mlockall)
- (net_raw)
+ (ptrace)
+ (sethostname)
+ (setdomainname)
+ (setpriority)
+ (setscheduler)
+ (reboot)
+ (chroot)
+ (mlockall)
+ (net_raw)
running changeprofile
running onexec
running changehat
running changehat_fork
running changehat_misc
*** A 'Killed' message from bash is expected for the following test
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
line 264: 309514 Killed $testexec "$@" > $outfile 2>&1
*** A 'Killed' message from bash is expected for the following test
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
line 264: 309547 Killed $testexec "$@" > $outfile 2>&1
running chdir
running clone
running coredump
*** A 'Segmentation Fault' message from bash is expected for the following
test
[Touch-packages] [Bug 2000062] Re: test-pivot_root_parse.py in apparmor failed with ImportError: No module named apparmor.aa
Note that this issue was not uncovered when running the whole test suite in test-apparmor.py from qa-regression-testing is because of bug 2000233 -- 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/262 Title: test-pivot_root_parse.py in apparmor failed with ImportError: No module named apparmor.aa Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in apparmor package in Ubuntu: New Status in apparmor source package in Bionic: New Status in apparmor source package in Focal: New Bug description: Steps to reproduce: # Via qa-regression-testing git clone --depth=1 git://git.launchpad.net/qa-regression-testing cd qa-regression-testing/scripts sudo python3 ./test-apparmor.py -v ApparmorTestsuites.test_utils_testsuite == Update base on John's comment in #1 Note that we cannot use apparmor cloned from launchpad directly, it requires some other local patches in qa-regression-testing: https://git.launchpad.net/qa-regression-testing/tree/scripts/apparmor/patches To experiment with the patched version via qa-regression-testing, comment out the following lines (1583, 1584) in tearDown(): if os.path.exists(self.tmpdir): testlib.recursive_rm(self.tmpdir) And run: sudo python3 ./test-apparmor.py -v ApparmorTestsuites.test_utils_testsuite The patched apparmor can be found in /tmp, now it can be tested with things like: cd /tmp/testlibwl29iqzr/source/focal/apparmor-2.13.3/utils export USE_SYSTEM=1 make check == End of update Output: LANG=C podchecker -warning -warning *.pod aa-audit.pod pod syntax OK. aa-autodep.pod pod syntax OK. aa-cleanprof.pod pod syntax OK. aa-complain.pod pod syntax OK. aa-decode.pod pod syntax OK. aa-disable.pod pod syntax OK. aa-easyprof.pod pod syntax OK. aa-enforce.pod pod syntax OK. aa-genprof.pod pod syntax OK. aa-logprof.pod pod syntax OK. aa-mergeprof.pod pod syntax OK. aa-notify.pod pod syntax OK. aa-remove-unknown.pod pod syntax OK. aa-sandbox.pod pod syntax OK. aa-status.pod pod syntax OK. aa-unconfined.pod pod syntax OK. logprof.conf.pod pod syntax OK. aa-notify syntax OK Checking aa-easyprof Checking aa-genprof Checking aa-logprof Checking aa-cleanprof Checking aa-mergeprof Checking aa-autodep Checking aa-audit Checking aa-complain Checking aa-enforce Checking aa-disable Checking aa-status Checking aa-unconfined Checking apparmor Checking test/common_test.py Checking test/minitools_test.py Checking test/test-aa-decode.py Checking test/test-aa-easyprof.py Checking test/test-aa.py Checking test/test-aamode.py Checking test/test-aare.py Checking test/test-baserule.py Checking test/test-capability.py Checking test/test-change_profile.py Checking test/test-common.py Checking test/test-config.py Checking test/test-dbus.py Checking test/test-example.py Checking test/test-file.py Checking test/test-libapparmor-test_multi.py Checking test/test-logparser.py Checking test/test-mount_parse.py Checking test/test-network.py Checking test/test-parser-simple-tests.py Checking test/test-pivot_root_parse.py Checking test/test-profile-list.py Checking test/test-profile-storage.py Checking test/test-ptrace.py Checking test/test-regex_matches.py Checking test/test-rlimit.py Checking test/test-severity.py Checking test/test-signal.py Checking test/test-translations.py Checking test/test-unix_parse.py make[1]: Entering directory '/home/ubuntu/testlibwl29iqzr/source/focal/apparmor-2.13.3/utils/test' === test-example.py === ... -- Ran 7 tests in 0.000s OK ... -- Ran 7 tests in 0.000s OK === test-pivot_root_parse.py === Traceback (most recent call last): File "test-pivot_root_parse.py", line 12, in import apparmor.aa as aa ImportError: No module named apparmor.aa make[1]: *** [Makefile:81: check] Error 1 make[1]: Leaving directory '/home/ubuntu/testlibwl29iqzr/source/focal/apparmor-2.13.3/utils/test' make: *** [Makefile:97: check] Error 2 Issue found on B-ibm-gt-5.4, F-oem-5.14, F-aws-fips after we changed how we run the ubuntu_qrt_apparmor test in bug 1982439. Sub-test in ApparmorTestsuites.test_utils_testsuite will fail with this. After some inspection it is because the script is trying to use python2. This can be verified with: python2 -c "import apparmor.aa" python3 -c "import apparmor.aa" This appears to be a known issue. https://gitlab.com/apparmor/apparmor/-/commit/af69088546d7d2f7188b9dec814f81721254964f And this patch has already landed in apparmor on Jammy, we will need this for Bionic / Focal as well. A temporary workaround is to
[Touch-packages] [Bug 2000062] Re: test-pivot_root_parse.py in apparmor failed with ImportError: No module named apparmor.aa
Considering the fact that fixing this in apparmor might need many other changes (as presented in the qa-regression- testing/tree/scripts/apparmor/patches directory) I think it's probably easier to add another fix there. And if we're removing python2, we can remove test_utils_testsuite() and just keep test_utils_testsuite3() which is a test with python3. This will require some tests with older releases. -- 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/262 Title: test-pivot_root_parse.py in apparmor failed with ImportError: No module named apparmor.aa Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in apparmor package in Ubuntu: New Status in apparmor source package in Bionic: New Status in apparmor source package in Focal: New Bug description: Steps to reproduce: # Via qa-regression-testing git clone --depth=1 git://git.launchpad.net/qa-regression-testing cd qa-regression-testing/scripts sudo python3 ./test-apparmor.py -v ApparmorTestsuites.test_utils_testsuite == Update base on John's comment in #1 Note that we cannot use apparmor cloned from launchpad directly, it requires some other local patches in qa-regression-testing: https://git.launchpad.net/qa-regression-testing/tree/scripts/apparmor/patches To experiment with the patched version via qa-regression-testing, comment out the following lines (1583, 1584) in tearDown(): if os.path.exists(self.tmpdir): testlib.recursive_rm(self.tmpdir) And run: sudo python3 ./test-apparmor.py -v ApparmorTestsuites.test_utils_testsuite The patched apparmor can be found in /tmp, now it can be tested with things like: cd /tmp/testlibwl29iqzr/source/focal/apparmor-2.13.3/utils export USE_SYSTEM=1 make check == End of update Output: LANG=C podchecker -warning -warning *.pod aa-audit.pod pod syntax OK. aa-autodep.pod pod syntax OK. aa-cleanprof.pod pod syntax OK. aa-complain.pod pod syntax OK. aa-decode.pod pod syntax OK. aa-disable.pod pod syntax OK. aa-easyprof.pod pod syntax OK. aa-enforce.pod pod syntax OK. aa-genprof.pod pod syntax OK. aa-logprof.pod pod syntax OK. aa-mergeprof.pod pod syntax OK. aa-notify.pod pod syntax OK. aa-remove-unknown.pod pod syntax OK. aa-sandbox.pod pod syntax OK. aa-status.pod pod syntax OK. aa-unconfined.pod pod syntax OK. logprof.conf.pod pod syntax OK. aa-notify syntax OK Checking aa-easyprof Checking aa-genprof Checking aa-logprof Checking aa-cleanprof Checking aa-mergeprof Checking aa-autodep Checking aa-audit Checking aa-complain Checking aa-enforce Checking aa-disable Checking aa-status Checking aa-unconfined Checking apparmor Checking test/common_test.py Checking test/minitools_test.py Checking test/test-aa-decode.py Checking test/test-aa-easyprof.py Checking test/test-aa.py Checking test/test-aamode.py Checking test/test-aare.py Checking test/test-baserule.py Checking test/test-capability.py Checking test/test-change_profile.py Checking test/test-common.py Checking test/test-config.py Checking test/test-dbus.py Checking test/test-example.py Checking test/test-file.py Checking test/test-libapparmor-test_multi.py Checking test/test-logparser.py Checking test/test-mount_parse.py Checking test/test-network.py Checking test/test-parser-simple-tests.py Checking test/test-pivot_root_parse.py Checking test/test-profile-list.py Checking test/test-profile-storage.py Checking test/test-ptrace.py Checking test/test-regex_matches.py Checking test/test-rlimit.py Checking test/test-severity.py Checking test/test-signal.py Checking test/test-translations.py Checking test/test-unix_parse.py make[1]: Entering directory '/home/ubuntu/testlibwl29iqzr/source/focal/apparmor-2.13.3/utils/test' === test-example.py === ... -- Ran 7 tests in 0.000s OK ... -- Ran 7 tests in 0.000s OK === test-pivot_root_parse.py === Traceback (most recent call last): File "test-pivot_root_parse.py", line 12, in import apparmor.aa as aa ImportError: No module named apparmor.aa make[1]: *** [Makefile:81: check] Error 1 make[1]: Leaving directory '/home/ubuntu/testlibwl29iqzr/source/focal/apparmor-2.13.3/utils/test' make: *** [Makefile:97: check] Error 2 Issue found on B-ibm-gt-5.4, F-oem-5.14, F-aws-fips after we changed how we run the ubuntu_qrt_apparmor test in bug 1982439. Sub-test in ApparmorTestsuites.test_utils_testsuite will fail with this. After some inspection it is because the script is trying to use python2. This can be verified with: python2 -c "import apparmor.aa" python3 -c "import apparmor.aa"
[Touch-packages] [Bug 2000062] Re: test-pivot_root_parse.py in apparmor failed with ImportError: No module named apparmor.aa
** Also affects: qa-regression-testing Importance: Undecided Status: New -- 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/262 Title: test-pivot_root_parse.py in apparmor failed with ImportError: No module named apparmor.aa Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in apparmor package in Ubuntu: New Status in apparmor source package in Bionic: New Status in apparmor source package in Focal: New Bug description: Steps to reproduce: # Via qa-regression-testing git clone --depth=1 git://git.launchpad.net/qa-regression-testing cd qa-regression-testing/scripts sudo python3 ./test-apparmor.py -v ApparmorTestsuites.test_utils_testsuite == Update base on John's comment in #1 Note that we cannot use apparmor cloned from launchpad directly, it requires some other local patches in qa-regression-testing: https://git.launchpad.net/qa-regression-testing/tree/scripts/apparmor/patches To experiment with the patched version via qa-regression-testing, comment out the following lines (1583, 1584) in tearDown(): if os.path.exists(self.tmpdir): testlib.recursive_rm(self.tmpdir) And run: sudo python3 ./test-apparmor.py -v ApparmorTestsuites.test_utils_testsuite The patched apparmor can be found in /tmp, now it can be tested with things like: cd /tmp/testlibwl29iqzr/source/focal/apparmor-2.13.3/utils export USE_SYSTEM=1 make check == End of update Output: LANG=C podchecker -warning -warning *.pod aa-audit.pod pod syntax OK. aa-autodep.pod pod syntax OK. aa-cleanprof.pod pod syntax OK. aa-complain.pod pod syntax OK. aa-decode.pod pod syntax OK. aa-disable.pod pod syntax OK. aa-easyprof.pod pod syntax OK. aa-enforce.pod pod syntax OK. aa-genprof.pod pod syntax OK. aa-logprof.pod pod syntax OK. aa-mergeprof.pod pod syntax OK. aa-notify.pod pod syntax OK. aa-remove-unknown.pod pod syntax OK. aa-sandbox.pod pod syntax OK. aa-status.pod pod syntax OK. aa-unconfined.pod pod syntax OK. logprof.conf.pod pod syntax OK. aa-notify syntax OK Checking aa-easyprof Checking aa-genprof Checking aa-logprof Checking aa-cleanprof Checking aa-mergeprof Checking aa-autodep Checking aa-audit Checking aa-complain Checking aa-enforce Checking aa-disable Checking aa-status Checking aa-unconfined Checking apparmor Checking test/common_test.py Checking test/minitools_test.py Checking test/test-aa-decode.py Checking test/test-aa-easyprof.py Checking test/test-aa.py Checking test/test-aamode.py Checking test/test-aare.py Checking test/test-baserule.py Checking test/test-capability.py Checking test/test-change_profile.py Checking test/test-common.py Checking test/test-config.py Checking test/test-dbus.py Checking test/test-example.py Checking test/test-file.py Checking test/test-libapparmor-test_multi.py Checking test/test-logparser.py Checking test/test-mount_parse.py Checking test/test-network.py Checking test/test-parser-simple-tests.py Checking test/test-pivot_root_parse.py Checking test/test-profile-list.py Checking test/test-profile-storage.py Checking test/test-ptrace.py Checking test/test-regex_matches.py Checking test/test-rlimit.py Checking test/test-severity.py Checking test/test-signal.py Checking test/test-translations.py Checking test/test-unix_parse.py make[1]: Entering directory '/home/ubuntu/testlibwl29iqzr/source/focal/apparmor-2.13.3/utils/test' === test-example.py === ... -- Ran 7 tests in 0.000s OK ... -- Ran 7 tests in 0.000s OK === test-pivot_root_parse.py === Traceback (most recent call last): File "test-pivot_root_parse.py", line 12, in import apparmor.aa as aa ImportError: No module named apparmor.aa make[1]: *** [Makefile:81: check] Error 1 make[1]: Leaving directory '/home/ubuntu/testlibwl29iqzr/source/focal/apparmor-2.13.3/utils/test' make: *** [Makefile:97: check] Error 2 Issue found on B-ibm-gt-5.4, F-oem-5.14, F-aws-fips after we changed how we run the ubuntu_qrt_apparmor test in bug 1982439. Sub-test in ApparmorTestsuites.test_utils_testsuite will fail with this. After some inspection it is because the script is trying to use python2. This can be verified with: python2 -c "import apparmor.aa" python3 -c "import apparmor.aa" This appears to be a known issue. https://gitlab.com/apparmor/apparmor/-/commit/af69088546d7d2f7188b9dec814f81721254964f And this patch has already landed in apparmor on Jammy, we will need this for Bionic / Focal as well. A temporary workaround is to run: export PYTHON_VERSIONS=python3 Before starting the
[Touch-packages] [Bug 2000062] Re: test-pivot_root_parse.py in apparmor failed with ImportError: No module named apparmor.aa
** Description changed: Steps to reproduce: # Via qa-regression-testing git clone --depth=1 git://git.launchpad.net/qa-regression-testing cd qa-regression-testing/scripts sudo python3 ./test-apparmor.py -v ApparmorTestsuites.test_utils_testsuite - # Or with apparmor directly - git clone -b ubuntu/focal-devel https://git.launchpad.net/ubuntu/+source/apparmor - cd apparmor/utils + == Update base on John's comment in #1 + Note that we cannot use apparmor cloned from launchpad directly, it requires some other local patches in qa-regression-testing: + https://git.launchpad.net/qa-regression-testing/tree/scripts/apparmor/patches + To experiment with the patched version via qa-regression-testing, comment out the following lines (1583, 1584) in tearDown(): + if os.path.exists(self.tmpdir): + testlib.recursive_rm(self.tmpdir) + And run: + sudo python3 ./test-apparmor.py -v ApparmorTestsuites.test_utils_testsuite + + The patched apparmor can be found in /tmp, now it can be tested with things like: + cd /tmp/testlibwl29iqzr/source/focal/apparmor-2.13.3/utils export USE_SYSTEM=1 make check + == End of update + Output: LANG=C podchecker -warning -warning *.pod aa-audit.pod pod syntax OK. aa-autodep.pod pod syntax OK. aa-cleanprof.pod pod syntax OK. aa-complain.pod pod syntax OK. aa-decode.pod pod syntax OK. aa-disable.pod pod syntax OK. aa-easyprof.pod pod syntax OK. aa-enforce.pod pod syntax OK. aa-genprof.pod pod syntax OK. aa-logprof.pod pod syntax OK. aa-mergeprof.pod pod syntax OK. aa-notify.pod pod syntax OK. aa-remove-unknown.pod pod syntax OK. aa-sandbox.pod pod syntax OK. aa-status.pod pod syntax OK. aa-unconfined.pod pod syntax OK. logprof.conf.pod pod syntax OK. aa-notify syntax OK Checking aa-easyprof Checking aa-genprof Checking aa-logprof Checking aa-cleanprof Checking aa-mergeprof Checking aa-autodep Checking aa-audit Checking aa-complain Checking aa-enforce Checking aa-disable Checking aa-status Checking aa-unconfined Checking apparmor Checking test/common_test.py Checking test/minitools_test.py Checking test/test-aa-decode.py Checking test/test-aa-easyprof.py Checking test/test-aa.py Checking test/test-aamode.py Checking test/test-aare.py Checking test/test-baserule.py Checking test/test-capability.py Checking test/test-change_profile.py Checking test/test-common.py Checking test/test-config.py Checking test/test-dbus.py Checking test/test-example.py Checking test/test-file.py Checking test/test-libapparmor-test_multi.py Checking test/test-logparser.py Checking test/test-mount_parse.py Checking test/test-network.py Checking test/test-parser-simple-tests.py Checking test/test-pivot_root_parse.py Checking test/test-profile-list.py Checking test/test-profile-storage.py Checking test/test-ptrace.py Checking test/test-regex_matches.py Checking test/test-rlimit.py Checking test/test-severity.py Checking test/test-signal.py Checking test/test-translations.py Checking test/test-unix_parse.py make[1]: Entering directory '/home/ubuntu/testlibwl29iqzr/source/focal/apparmor-2.13.3/utils/test' === test-example.py === ... -- Ran 7 tests in 0.000s OK ... -- Ran 7 tests in 0.000s OK === test-pivot_root_parse.py === Traceback (most recent call last): - File "test-pivot_root_parse.py", line 12, in - import apparmor.aa as aa + File "test-pivot_root_parse.py", line 12, in + import apparmor.aa as aa ImportError: No module named apparmor.aa make[1]: *** [Makefile:81: check] Error 1 make[1]: Leaving directory '/home/ubuntu/testlibwl29iqzr/source/focal/apparmor-2.13.3/utils/test' make: *** [Makefile:97: check] Error 2 - - Issue found on B-ibm-gt-5.4, F-oem-5.14, F-aws-fips after we changed how we run the ubuntu_qrt_apparmor test in bug 1982439. + Issue found on B-ibm-gt-5.4, F-oem-5.14, F-aws-fips after we changed how + we run the ubuntu_qrt_apparmor test in bug 1982439. Sub-test in ApparmorTestsuites.test_utils_testsuite will fail with this. After some inspection it is because the script is trying to use python2. This can be verified with: python2 -c "import apparmor.aa" python3 -c "import apparmor.aa" This appears to be a known issue. https://gitlab.com/apparmor/apparmor/-/commit/af69088546d7d2f7188b9dec814f81721254964f And this patch has already landed in apparmor on Jammy, we will need this for Bionic / Focal as well. A temporary workaround is to run: export PYTHON_VERSIONS=python3 Before starting the tests. I am not sure why this was not uncovered with "./test-apparmor.py -v" in q-r-t until we run test cases one-by-one now. -- You received this bug notification because you are a member of Ubuntu
[Touch-packages] [Bug 2000062] Re: test-pivot_root_parse.py in apparmor failed with ImportError: No module named apparmor.aa
Yes John's comment is correct, we can't just run `make check` for source cloned from launchpad directly. It will complain about: aa-genprof:60: undefined name 'PermissionError' aa-genprof:130: undefined name 'PermissionError' I will update the bug description. qa-regression-testing will have some local patches[1] applied before starting the test. We must use it to get a working version. To experiment with the patched version via qa-regression-testing, comment out the following lines (1583, 1584) in tearDown() if os.path.exists(self.tmpdir): testlib.recursive_rm(self.tmpdir) With the patched apparmor-2.13.3, I can just remove the "python2" string from apparmor-2.13.3/common/Make.rules file and run the following commands without any error: export USE_SYSTEM=1 make check Please find attachment for the test output. In this case we might be able to add another local patch in qa-regression-testing for this change. [1] https://git.launchpad.net/qa-regression-testing/tree/scripts/apparmor/patches ** Attachment added: "apparmor-2.13.3.log" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/262/+attachment/5636724/+files/apparmor-2.13.3.log -- 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/262 Title: test-pivot_root_parse.py in apparmor failed with ImportError: No module named apparmor.aa Status in ubuntu-kernel-tests: New Status in apparmor package in Ubuntu: New Status in apparmor source package in Bionic: New Status in apparmor source package in Focal: New Bug description: Steps to reproduce: # Via qa-regression-testing git clone --depth=1 git://git.launchpad.net/qa-regression-testing cd qa-regression-testing/scripts sudo python3 ./test-apparmor.py -v ApparmorTestsuites.test_utils_testsuite == Update base on John's comment in #1 Note that we cannot use apparmor cloned from launchpad directly, it requires some other local patches in qa-regression-testing: https://git.launchpad.net/qa-regression-testing/tree/scripts/apparmor/patches To experiment with the patched version via qa-regression-testing, comment out the following lines (1583, 1584) in tearDown(): if os.path.exists(self.tmpdir): testlib.recursive_rm(self.tmpdir) And run: sudo python3 ./test-apparmor.py -v ApparmorTestsuites.test_utils_testsuite The patched apparmor can be found in /tmp, now it can be tested with things like: cd /tmp/testlibwl29iqzr/source/focal/apparmor-2.13.3/utils export USE_SYSTEM=1 make check == End of update Output: LANG=C podchecker -warning -warning *.pod aa-audit.pod pod syntax OK. aa-autodep.pod pod syntax OK. aa-cleanprof.pod pod syntax OK. aa-complain.pod pod syntax OK. aa-decode.pod pod syntax OK. aa-disable.pod pod syntax OK. aa-easyprof.pod pod syntax OK. aa-enforce.pod pod syntax OK. aa-genprof.pod pod syntax OK. aa-logprof.pod pod syntax OK. aa-mergeprof.pod pod syntax OK. aa-notify.pod pod syntax OK. aa-remove-unknown.pod pod syntax OK. aa-sandbox.pod pod syntax OK. aa-status.pod pod syntax OK. aa-unconfined.pod pod syntax OK. logprof.conf.pod pod syntax OK. aa-notify syntax OK Checking aa-easyprof Checking aa-genprof Checking aa-logprof Checking aa-cleanprof Checking aa-mergeprof Checking aa-autodep Checking aa-audit Checking aa-complain Checking aa-enforce Checking aa-disable Checking aa-status Checking aa-unconfined Checking apparmor Checking test/common_test.py Checking test/minitools_test.py Checking test/test-aa-decode.py Checking test/test-aa-easyprof.py Checking test/test-aa.py Checking test/test-aamode.py Checking test/test-aare.py Checking test/test-baserule.py Checking test/test-capability.py Checking test/test-change_profile.py Checking test/test-common.py Checking test/test-config.py Checking test/test-dbus.py Checking test/test-example.py Checking test/test-file.py Checking test/test-libapparmor-test_multi.py Checking test/test-logparser.py Checking test/test-mount_parse.py Checking test/test-network.py Checking test/test-parser-simple-tests.py Checking test/test-pivot_root_parse.py Checking test/test-profile-list.py Checking test/test-profile-storage.py Checking test/test-ptrace.py Checking test/test-regex_matches.py Checking test/test-rlimit.py Checking test/test-severity.py Checking test/test-signal.py Checking test/test-translations.py Checking test/test-unix_parse.py make[1]: Entering directory '/home/ubuntu/testlibwl29iqzr/source/focal/apparmor-2.13.3/utils/test' === test-example.py === ... -- Ran 7 tests in 0.000s OK ... -- Ran 7 tests in 0.000s OK ===
[Touch-packages] [Bug 2000062] Re: test-pivot_root_parse.py in apparmor failed with ImportError: No module named apparmor.aa
** Description changed: - Issue found on B-ibm-gt-5.4, F-oem-5.14, F-aws-fips after the change in - bug 1982439 has landed. + Steps to reproduce: + # Via qa-regression-testing + git clone --depth=1 git://git.launchpad.net/qa-regression-testing + cd qa-regression-testing/scripts + sudo python3 ./test-apparmor.py -v ApparmorTestsuites.test_utils_testsuite - Sub-test in ApparmorTestsuites.test_utils_testsuite failed with: + # Or with apparmor directly + git clone -b ubuntu/focal-devel https://git.launchpad.net/ubuntu/+source/apparmor + cd apparmor/utils + export USE_SYSTEM=1 + make check - === test-pivot_root_parse.py === - Traceback (most recent call last): -File "test-pivot_root_parse.py", line 12, in - import apparmor.aa as aa - ImportError: No module named apparmor.aa - Makefile:81: recipe for target 'check' failed - make[1]: *** [check] Error 1 - make[1]: Leaving directory '/tmp/testlibyXL5ua/source/bionic/apparmor-2.12/utils/test' - Makefile:95: recipe for target 'check' failed - make: *** [check] Error 2 + Output: + LANG=C podchecker -warning -warning *.pod + aa-audit.pod pod syntax OK. + aa-autodep.pod pod syntax OK. + aa-cleanprof.pod pod syntax OK. + aa-complain.pod pod syntax OK. + aa-decode.pod pod syntax OK. + aa-disable.pod pod syntax OK. + aa-easyprof.pod pod syntax OK. + aa-enforce.pod pod syntax OK. + aa-genprof.pod pod syntax OK. + aa-logprof.pod pod syntax OK. + aa-mergeprof.pod pod syntax OK. + aa-notify.pod pod syntax OK. + aa-remove-unknown.pod pod syntax OK. + aa-sandbox.pod pod syntax OK. + aa-status.pod pod syntax OK. + aa-unconfined.pod pod syntax OK. + logprof.conf.pod pod syntax OK. + aa-notify syntax OK + Checking aa-easyprof + Checking aa-genprof + Checking aa-logprof + Checking aa-cleanprof + Checking aa-mergeprof + Checking aa-autodep + Checking aa-audit + Checking aa-complain + Checking aa-enforce + Checking aa-disable + Checking aa-status + Checking aa-unconfined + Checking apparmor + Checking test/common_test.py + Checking test/minitools_test.py + Checking test/test-aa-decode.py + Checking test/test-aa-easyprof.py + Checking test/test-aa.py + Checking test/test-aamode.py + Checking test/test-aare.py + Checking test/test-baserule.py + Checking test/test-capability.py + Checking test/test-change_profile.py + Checking test/test-common.py + Checking test/test-config.py + Checking test/test-dbus.py + Checking test/test-example.py + Checking test/test-file.py + Checking test/test-libapparmor-test_multi.py + Checking test/test-logparser.py + Checking test/test-mount_parse.py + Checking test/test-network.py + Checking test/test-parser-simple-tests.py + Checking test/test-pivot_root_parse.py + Checking test/test-profile-list.py + Checking test/test-profile-storage.py + Checking test/test-ptrace.py + Checking test/test-regex_matches.py + Checking test/test-rlimit.py + Checking test/test-severity.py + Checking test/test-signal.py + Checking test/test-translations.py + Checking test/test-unix_parse.py + make[1]: Entering directory '/home/ubuntu/testlibwl29iqzr/source/focal/apparmor-2.13.3/utils/test' - After some inspection it looks like this is because the script is trying to use python2. This can be verified with: + === test-example.py === + ... + -- + Ran 7 tests in 0.000s + + OK + ... + -- + Ran 7 tests in 0.000s + + OK + + === test-pivot_root_parse.py === + Traceback (most recent call last): + File "test-pivot_root_parse.py", line 12, in + import apparmor.aa as aa + ImportError: No module named apparmor.aa + make[1]: *** [Makefile:81: check] Error 1 + make[1]: Leaving directory '/home/ubuntu/testlibwl29iqzr/source/focal/apparmor-2.13.3/utils/test' + make: *** [Makefile:97: check] Error 2 + + + Issue found on B-ibm-gt-5.4, F-oem-5.14, F-aws-fips after we changed how we run the ubuntu_qrt_apparmor test in bug 1982439. + + Sub-test in ApparmorTestsuites.test_utils_testsuite will fail with this. + + After some inspection it is because the script is trying to use python2. This can be verified with: python2 -c "import apparmor.aa" python3 -c "import apparmor.aa" - It's still yet to be clear why this is only happening with "python3 - ./test-apparmor.py -v ApparmorTestsuites.test_utils_testsuite" but - didn't happen before when we're running everything with "python3 ./test- - apparmor.py -v" + This appears to be a known issue. + https://gitlab.com/apparmor/apparmor/-/commit/af69088546d7d2f7188b9dec814f81721254964f + + And this patch has already landed in apparmor on Jammy, we will need this for Bionic / Focal as well. A temporary workaround is to run: + export PYTHON_VERSIONS=python3 + + Before starting the tests. + + I am not sure why this was not uncovered with "./test-apparmor.py -v" in + q-r-t until we run test cases one-by-one now. ** Also affects: apparmor (Ubuntu)
[Touch-packages] [Bug 1979258] Re: lxc: lxc-test-parse-config-file failed (failed to set config item)
** Tags added: sru-20220620 -- 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/1979258 Title: lxc: lxc-test-parse-config-file failed (failed to set config item) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: New Status in lxc source package in Jammy: New Bug description: With bug 1943441 (expected value and retrieved value do not match) fixed with lxc 1:4.0.12-0ubuntu1 on Jammy (still exist on F / I) Now this test on Jammy with lxc 1:5.0.0~git2209-g5a7b9ce67-0ubuntu1 will fail with: Running '/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file' parse_config_file.c: 49: set_get_compare_clear_save_load: failed to set config item "lxc.selinux.context" to "system_u:system_r:lxc_t:s0:c22" parse_config_file.c: 49: set_get_compare_clear_save_load: failed to set config item "lxc.seccomp.profile" to "/some/seccomp/file" parse_config_file.c: 580: main: lxc.seccomp.profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1979258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969905] Re: lxc-test-no-new-privs in ubuntu_lxc failed on F-s390x zVM (lxc 1:4.0.12-0ubuntu1~20.04.1 )
OK I misread Stefan's comment, checking the report again, it's using the consistent version (1:4.0.12-0ubuntu1~20.04.1)) for both lxc and test cases (source) on that s390x zVM. Please find attachment for the full test log. I will switch the bug status back to New. ** Attachment added: "test-110.log" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1969905/+attachment/5582419/+files/test-110.log ** Changed in: lxc (Ubuntu) Status: Invalid => New -- 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/1969905 Title: lxc-test-no-new-privs in ubuntu_lxc failed on F-s390x zVM (lxc 1:4.0.12-0ubuntu1~20.04.1 ) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: New Bug description: Issue found on F 5.4.0-108.122 s390x node kernel04 Test failed with: Running '/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-no-new-privs' + DONE=0 + trap cleanup EXIT SIGHUP SIGINT SIGTERM + '[' '!' -d /etc/lxc ']' + lxc-create -t busybox -n c1 + echo 'lxc.no_new_privs = 1' + lxc-start -n c1 ++ lxc-info -n c1 -p -H + p1=65479 + '[' 65479 '!=' -1 ']' + lxc-attach -n c1 --clear-env -- mkdir -p /home/ubuntu + lxc-attach -n c1 --clear-env -- /bin/sh -c 'cat <> /etc/passwd ubuntu:x:1000:1000:ubuntu:/home/ubuntu:/bin/sh EOF' + lxc-attach -n c1 --clear-env --uid 1000 --gid 1000 -- ping -c 1 127.0.0.1 PING 127.0.0.1 (127.0.0.1): 56 data bytes ping: permission denied (are you root?) + lxc-stop -n c1 -k + sed -i 's/lxc.no_new_privs = 1/lxc.no_new_privs = 0/' /var/lib/lxc/c1/config + lxc-start -n c1 + lxc-attach -n c1 --clear-env --uid 1000 --gid 1000 -- ping -c 1 127.0.0.1 PING 127.0.0.1 (127.0.0.1): 56 data bytes ping: sendto: Network is unreachable Managed to ping localhost + echo 'Managed to ping localhost' + false + cleanup + cd / + lxc-destroy -n c1 -f FAIL + '[' 0 -eq 0 ']' + echo FAIL + exit 1 It's worthy to note that this test has passed with 5.4.0-106.120 + lxc 1:4.0.6-0ubuntu1~20.04.1 The test output is a bit different, I think it's because of this commit: https://github.com/lxc/lxc/commit/f6a53ad2c593ade2320cc357abd15e01e22b6f8d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1969905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969905] Re: lxc-test-no-new-privs in ubuntu_lxc failed on F-s390x zVM (lxc 1:4.0.12-0ubuntu1~20.04.1 )
Tried this on a Focal AMD64 instance, and it passed with 1:4.0.12-0ubuntu1~20.04.1 Stefan is right, the tool was not updated on that s390x SUT. Sorry for the noise, this is a manually provisioned system and this -proposed stuff must be something leftover from the past. ** Changed in: lxc (Ubuntu) Status: New => Invalid -- 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/1969905 Title: lxc-test-no-new-privs in ubuntu_lxc failed on F-s390x zVM (lxc 1:4.0.12-0ubuntu1~20.04.1 ) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Invalid Bug description: Issue found on F 5.4.0-108.122 s390x node kernel04 Test failed with: Running '/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-no-new-privs' + DONE=0 + trap cleanup EXIT SIGHUP SIGINT SIGTERM + '[' '!' -d /etc/lxc ']' + lxc-create -t busybox -n c1 + echo 'lxc.no_new_privs = 1' + lxc-start -n c1 ++ lxc-info -n c1 -p -H + p1=65479 + '[' 65479 '!=' -1 ']' + lxc-attach -n c1 --clear-env -- mkdir -p /home/ubuntu + lxc-attach -n c1 --clear-env -- /bin/sh -c 'cat <> /etc/passwd ubuntu:x:1000:1000:ubuntu:/home/ubuntu:/bin/sh EOF' + lxc-attach -n c1 --clear-env --uid 1000 --gid 1000 -- ping -c 1 127.0.0.1 PING 127.0.0.1 (127.0.0.1): 56 data bytes ping: permission denied (are you root?) + lxc-stop -n c1 -k + sed -i 's/lxc.no_new_privs = 1/lxc.no_new_privs = 0/' /var/lib/lxc/c1/config + lxc-start -n c1 + lxc-attach -n c1 --clear-env --uid 1000 --gid 1000 -- ping -c 1 127.0.0.1 PING 127.0.0.1 (127.0.0.1): 56 data bytes ping: sendto: Network is unreachable Managed to ping localhost + echo 'Managed to ping localhost' + false + cleanup + cd / + lxc-destroy -n c1 -f FAIL + '[' 0 -eq 0 ']' + echo FAIL + exit 1 It's worthy to note that this test has passed with 5.4.0-106.120 + lxc 1:4.0.6-0ubuntu1~20.04.1 The test output is a bit different, I think it's because of this commit: https://github.com/lxc/lxc/commit/f6a53ad2c593ade2320cc357abd15e01e22b6f8d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1969905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969905] Re: lxc-test-no-new-privs in ubuntu_lxc failed on F-s390x zVM (lxc 1:4.0.12-0ubuntu1~20.04.1 )
Hi Christian, we just found that it's because we have universe -proposed enabled on that node only. (Which should be disabled for our SRU test) On other instances they're still using the old test case from 1:4.0.6-0ubuntu1~20.04.1. I can give it a try on AMD64 instance. -- 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/1969905 Title: lxc-test-no-new-privs in ubuntu_lxc failed on F-s390x zVM (lxc 1:4.0.12-0ubuntu1~20.04.1 ) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: New Bug description: Issue found on F 5.4.0-108.122 s390x node kernel04 Test failed with: Running '/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-no-new-privs' + DONE=0 + trap cleanup EXIT SIGHUP SIGINT SIGTERM + '[' '!' -d /etc/lxc ']' + lxc-create -t busybox -n c1 + echo 'lxc.no_new_privs = 1' + lxc-start -n c1 ++ lxc-info -n c1 -p -H + p1=65479 + '[' 65479 '!=' -1 ']' + lxc-attach -n c1 --clear-env -- mkdir -p /home/ubuntu + lxc-attach -n c1 --clear-env -- /bin/sh -c 'cat <> /etc/passwd ubuntu:x:1000:1000:ubuntu:/home/ubuntu:/bin/sh EOF' + lxc-attach -n c1 --clear-env --uid 1000 --gid 1000 -- ping -c 1 127.0.0.1 PING 127.0.0.1 (127.0.0.1): 56 data bytes ping: permission denied (are you root?) + lxc-stop -n c1 -k + sed -i 's/lxc.no_new_privs = 1/lxc.no_new_privs = 0/' /var/lib/lxc/c1/config + lxc-start -n c1 + lxc-attach -n c1 --clear-env --uid 1000 --gid 1000 -- ping -c 1 127.0.0.1 PING 127.0.0.1 (127.0.0.1): 56 data bytes ping: sendto: Network is unreachable Managed to ping localhost + echo 'Managed to ping localhost' + false + cleanup + cd / + lxc-destroy -n c1 -f FAIL + '[' 0 -eq 0 ']' + echo FAIL + exit 1 It's worthy to note that this test has passed with 5.4.0-106.120 + lxc 1:4.0.6-0ubuntu1~20.04.1 The test output is a bit different, I think it's because of this commit: https://github.com/lxc/lxc/commit/f6a53ad2c593ade2320cc357abd15e01e22b6f8d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1969905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969905] Re: lxc-test-no-new-privs in ubuntu_lxc failed on F-s390x zVM (lxc 1:4.0.12-0ubuntu1~20.04.1 )
** Tags added: 5.4 focal s390x sru-20220321 ubuntu-lxc ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/1969905 Title: lxc-test-no-new-privs in ubuntu_lxc failed on F-s390x zVM (lxc 1:4.0.12-0ubuntu1~20.04.1 ) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: New Bug description: Issue found on F 5.4.0-108.122 s390x node kernel04 Test failed with: Running '/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-no-new-privs' + DONE=0 + trap cleanup EXIT SIGHUP SIGINT SIGTERM + '[' '!' -d /etc/lxc ']' + lxc-create -t busybox -n c1 + echo 'lxc.no_new_privs = 1' + lxc-start -n c1 ++ lxc-info -n c1 -p -H + p1=65479 + '[' 65479 '!=' -1 ']' + lxc-attach -n c1 --clear-env -- mkdir -p /home/ubuntu + lxc-attach -n c1 --clear-env -- /bin/sh -c 'cat <> /etc/passwd ubuntu:x:1000:1000:ubuntu:/home/ubuntu:/bin/sh EOF' + lxc-attach -n c1 --clear-env --uid 1000 --gid 1000 -- ping -c 1 127.0.0.1 PING 127.0.0.1 (127.0.0.1): 56 data bytes ping: permission denied (are you root?) + lxc-stop -n c1 -k + sed -i 's/lxc.no_new_privs = 1/lxc.no_new_privs = 0/' /var/lib/lxc/c1/config + lxc-start -n c1 + lxc-attach -n c1 --clear-env --uid 1000 --gid 1000 -- ping -c 1 127.0.0.1 PING 127.0.0.1 (127.0.0.1): 56 data bytes ping: sendto: Network is unreachable Managed to ping localhost + echo 'Managed to ping localhost' + false + cleanup + cd / + lxc-destroy -n c1 -f FAIL + '[' 0 -eq 0 ']' + echo FAIL + exit 1 It's worthy to note that this test has passed with 5.4.0-106.120 + lxc 1:4.0.6-0ubuntu1~20.04.1 The test output is a bit different, I think it's because of this commit: https://github.com/lxc/lxc/commit/f6a53ad2c593ade2320cc357abd15e01e22b6f8d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1969905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966188] Re: lxc: lxc-test-parse-config-file failure on Jammy (retrieved value "" for config key "lxc.selinux.context")
** Summary changed:
- lxc: lxc-test-parse-config-file failure on Jammy
+ lxc: lxc-test-parse-config-file failure on Jammy (retrieved value "" for
config key "lxc.selinux.context")
--
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/1966188
Title:
lxc: lxc-test-parse-config-file failure on Jammy (retrieved value ""
for config key "lxc.selinux.context")
Status in lxc package in Ubuntu:
New
Bug description:
After bug 1943441 fixed for Impish, we're seeing this again on Jammy,
with lxc 1:4.0.12-0ubuntu2 from Jammy archive.
STARTubuntu_lxc.lxc-test-parse-config-file
ubuntu_lxc.lxc-test-parse-config-filetimestamp=1648013959timeout=1200
localtime=Mar 23 05:39:19
Persistent state client._record_indent now set to 2
Persistent state client.unexpected_reboot now set to
('ubuntu_lxc.lxc-test-parse-config-file',
'ubuntu_lxc.lxc-test-parse-config-file')
Waiting for pid 79677 for 1200 seconds
System python is too old, crash handling disabled
Running '/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file'
parse_config_file.c: 63: set_get_compare_clear_save_load: expected value
"system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key
"lxc.selinux.context" do not match
parse_config_file.c: 49: set_get_compare_clear_save_load: failed to
set config item "lxc.seccomp.profile" to "/some/seccomp/file"
parse_config_file.c: 580: main: lxc.seccomp.profile
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1966188/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966188] Re: lxc: lxc-test-parse-config-file failure on Jammy
** Description changed:
After bug 1943441 fixed for Impish, we're seeing this again on Jammy,
with lxc 1:4.0.12-0ubuntu2 from Jammy archive.
- STARTubuntu_lxc.lxc-test-parse-config-file
ubuntu_lxc.lxc-test-parse-config-filetimestamp=1648013959timeout=1200
localtime=Mar 23 05:39:19
- Persistent state client._record_indent now set to 2
- Persistent state client.unexpected_reboot now set to
('ubuntu_lxc.lxc-test-parse-config-file',
'ubuntu_lxc.lxc-test-parse-config-file')
- Waiting for pid 79677 for 1200 seconds
- System python is too old, crash handling disabled
- Running '/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file'
- [stderr] parse_config_file.c: 63: set_get_compare_clear_save_load: expected
value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key
"lxc.selinux.context" do not match
- [stderr]
- [stderr] parse_config_file.c: 49: set_get_compare_clear_save_load: failed to
set config item "lxc.seccomp.profile" to "/some/seccomp/file"
- [stderr]
- [stderr] parse_config_file.c: 580: main: lxc.seccomp.profile
- [stderr]
- Exception escaping from test:
- ~
+ STARTubuntu_lxc.lxc-test-parse-config-file
ubuntu_lxc.lxc-test-parse-config-filetimestamp=1648013959timeout=1200
localtime=Mar 23 05:39:19
+ Persistent state client._record_indent now set to 2
+ Persistent state client.unexpected_reboot now set to
('ubuntu_lxc.lxc-test-parse-config-file',
'ubuntu_lxc.lxc-test-parse-config-file')
+ Waiting for pid 79677 for 1200 seconds
+ System python is too old, crash handling disabled
+ Running '/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file'
+ parse_config_file.c: 63: set_get_compare_clear_save_load: expected value
"system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key
"lxc.selinux.context" do not match
+
+ parse_config_file.c: 49: set_get_compare_clear_save_load: failed to set
+ config item "lxc.seccomp.profile" to "/some/seccomp/file"
+
+ parse_config_file.c: 580: main: lxc.seccomp.profile
** Tags added: 5.15 jammy ubuntu-lxc
--
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/1966188
Title:
lxc: lxc-test-parse-config-file failure on Jammy (retrieved value ""
for config key "lxc.selinux.context")
Status in lxc package in Ubuntu:
New
Bug description:
After bug 1943441 fixed for Impish, we're seeing this again on Jammy,
with lxc 1:4.0.12-0ubuntu2 from Jammy archive.
STARTubuntu_lxc.lxc-test-parse-config-file
ubuntu_lxc.lxc-test-parse-config-filetimestamp=1648013959timeout=1200
localtime=Mar 23 05:39:19
Persistent state client._record_indent now set to 2
Persistent state client.unexpected_reboot now set to
('ubuntu_lxc.lxc-test-parse-config-file',
'ubuntu_lxc.lxc-test-parse-config-file')
Waiting for pid 79677 for 1200 seconds
System python is too old, crash handling disabled
Running '/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file'
parse_config_file.c: 63: set_get_compare_clear_save_load: expected value
"system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key
"lxc.selinux.context" do not match
parse_config_file.c: 49: set_get_compare_clear_save_load: failed to
set config item "lxc.seccomp.profile" to "/some/seccomp/file"
parse_config_file.c: 580: main: lxc.seccomp.profile
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1966188/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966188] [NEW] lxc: lxc-test-parse-config-file failure on Jammy
Public bug reported:
After bug 1943441 fixed for Impish, we're seeing this again on Jammy,
with lxc 1:4.0.12-0ubuntu2 from Jammy archive.
STARTubuntu_lxc.lxc-test-parse-config-file
ubuntu_lxc.lxc-test-parse-config-filetimestamp=1648013959timeout=1200
localtime=Mar 23 05:39:19
Persistent state client._record_indent now set to 2
Persistent state client.unexpected_reboot now set to
('ubuntu_lxc.lxc-test-parse-config-file',
'ubuntu_lxc.lxc-test-parse-config-file')
Waiting for pid 79677 for 1200 seconds
System python is too old, crash handling disabled
Running '/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file'
[stderr] parse_config_file.c: 63: set_get_compare_clear_save_load: expected
value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key
"lxc.selinux.context" do not match
[stderr]
[stderr] parse_config_file.c: 49: set_get_compare_clear_save_load: failed to
set config item "lxc.seccomp.profile" to "/some/seccomp/file"
[stderr]
[stderr] parse_config_file.c: 580: main: lxc.seccomp.profile
[stderr]
Exception escaping from test:
~
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
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/1966188
Title:
lxc: lxc-test-parse-config-file failure on Jammy
Status in lxc package in Ubuntu:
New
Bug description:
After bug 1943441 fixed for Impish, we're seeing this again on Jammy,
with lxc 1:4.0.12-0ubuntu2 from Jammy archive.
STARTubuntu_lxc.lxc-test-parse-config-file
ubuntu_lxc.lxc-test-parse-config-filetimestamp=1648013959timeout=1200
localtime=Mar 23 05:39:19
Persistent state client._record_indent now set to 2
Persistent state client.unexpected_reboot now set to
('ubuntu_lxc.lxc-test-parse-config-file',
'ubuntu_lxc.lxc-test-parse-config-file')
Waiting for pid 79677 for 1200 seconds
System python is too old, crash handling disabled
Running '/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file'
[stderr] parse_config_file.c: 63: set_get_compare_clear_save_load: expected
value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key
"lxc.selinux.context" do not match
[stderr]
[stderr] parse_config_file.c: 49: set_get_compare_clear_save_load: failed to
set config item "lxc.seccomp.profile" to "/some/seccomp/file"
[stderr]
[stderr] parse_config_file.c: 580: main: lxc.seccomp.profile
[stderr]
Exception escaping from test:
~
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1966188/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960847] Re: lxc autopkgtests failures with cgroupv2 on jammy
** Changed in: ubuntu-kernel-tests Status: Fix Committed => Fix Released -- 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/1960847 Title: lxc autopkgtests failures with cgroupv2 on jammy Status in ubuntu-kernel-tests: Fix Released Status in lxc package in Ubuntu: Invalid Bug description: Some lxc autotests (like lxc-test-apparmor-mount for example) are still expecting to find cgroupv1 or a hybrid hierarchy and they just fail on jammy, because systemd is now using a full cgroupv2 hierarchy. Running these tests in a cgroupv2 system is pointless, because it's just going to trigger lots of errors and it's not really stress- testing anything. We should consider to create a new test based on this: https://github.com/lxc/lxc-ci and enable it only on those systems that are using cgroupv2 (for example checking if /sys/fs/cgroup/cgroup.procs exists as a regular file). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1960847/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961800] Re: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal)
Note that version 2.2.9-1ubuntu0.2 has gone on bionic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1961800 Title: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) Status in expat package in Ubuntu: Invalid Status in python-xmltodict package in Ubuntu: Confirmed Bug description: I started seeing errors parsing XML files today (Feb 22, 2022) after my system was updated to 2.2.5-3ubuntu0.4. This is on a bionic server. The parsing is being done by python3's xmltodict module, which uses python3 expat as the actual parser. This is the error it raises: xml.parsers.expat.ExpatError: out of memory: line 1, column 0 So far this is happening on multiple xml files, although they all come from the same source (these are jenkins config.xml files). I'm working on coming up with a minimal test case which I'll provide once I have it cleaned up of any private data. [System info] $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy libexpat1 libexpat1: Installed: 2.2.5-3ubuntu0.4 Candidate: 2.2.5-3ubuntu0.4 Version table: *** 2.2.5-3ubuntu0.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.5-3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960847] Re: lxc autopkgtests failures with cgroupv2 on jammy
** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Committed -- 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/1960847 Title: lxc autopkgtests failures with cgroupv2 on jammy Status in ubuntu-kernel-tests: Fix Committed Status in lxc package in Ubuntu: Invalid Bug description: Some lxc autotests (like lxc-test-apparmor-mount for example) are still expecting to find cgroupv1 or a hybrid hierarchy and they just fail on jammy, because systemd is now using a full cgroupv2 hierarchy. Running these tests in a cgroupv2 system is pointless, because it's just going to trigger lots of errors and it's not really stress- testing anything. We should consider to create a new test based on this: https://github.com/lxc/lxc-ci and enable it only on those systems that are using cgroupv2 (for example checking if /sys/fs/cgroup/cgroup.procs exists as a regular file). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1960847/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960847] Re: lxc autopkgtests failures with cgroupv2 on jammy
https://lists.ubuntu.com/archives/kernel-team/2022-February/128112.html -- 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/1960847 Title: lxc autopkgtests failures with cgroupv2 on jammy Status in ubuntu-kernel-tests: In Progress Status in lxc package in Ubuntu: Invalid Bug description: Some lxc autotests (like lxc-test-apparmor-mount for example) are still expecting to find cgroupv1 or a hybrid hierarchy and they just fail on jammy, because systemd is now using a full cgroupv2 hierarchy. Running these tests in a cgroupv2 system is pointless, because it's just going to trigger lots of errors and it's not really stress- testing anything. We should consider to create a new test based on this: https://github.com/lxc/lxc-ci and enable it only on those systems that are using cgroupv2 (for example checking if /sys/fs/cgroup/cgroup.procs exists as a regular file). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1960847/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960847] Re: lxc autopkgtests failures with cgroupv2 on jammy
We used to run the lxc tests via autopkgtest command directly from the archive. This has been changed for our test granularity improvement to make it easier to review the result about 6 months ago and the outcome is pretty good until now: https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/commit/?id=f914a916508e9c866e013837408a28e777ce1a82 By running sub-tests one-by-one we will be able to know which one is failing easily without checking the overall test report from "exercise" script. The lxc-pkg-ubuntu git repo was used as the test script source at that time since it's the upstream source. We didn't expect there will be such an issue like package version mismatch (bug 1960094) due to the upload delay back then, it's been corrected now. Please don't hesitate to let us know if there is any other option to improve this. Thank you! -- 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/1960847 Title: lxc autopkgtests failures with cgroupv2 on jammy Status in ubuntu-kernel-tests: In Progress Status in lxc package in Ubuntu: Invalid Bug description: Some lxc autotests (like lxc-test-apparmor-mount for example) are still expecting to find cgroupv1 or a hybrid hierarchy and they just fail on jammy, because systemd is now using a full cgroupv2 hierarchy. Running these tests in a cgroupv2 system is pointless, because it's just going to trigger lots of errors and it's not really stress- testing anything. We should consider to create a new test based on this: https://github.com/lxc/lxc-ci and enable it only on those systems that are using cgroupv2 (for example checking if /sys/fs/cgroup/cgroup.procs exists as a regular file). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1960847/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960847] Re: lxc autopkgtests failures with cgroupv2 on jammy
Thanks for the hint Stéphane, I found the fix here: https://github.com/lxc/lxc-pkg-ubuntu/commit/a9b80060f910e133fe899bd89ff9182b4a4d02e9 ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => In Progress -- 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/1960847 Title: lxc autopkgtests failures with cgroupv2 on jammy Status in ubuntu-kernel-tests: In Progress Status in lxc package in Ubuntu: Invalid Bug description: Some lxc autotests (like lxc-test-apparmor-mount for example) are still expecting to find cgroupv1 or a hybrid hierarchy and they just fail on jammy, because systemd is now using a full cgroupv2 hierarchy. Running these tests in a cgroupv2 system is pointless, because it's just going to trigger lots of errors and it's not really stress- testing anything. We should consider to create a new test based on this: https://github.com/lxc/lxc-ci and enable it only on those systems that are using cgroupv2 (for example checking if /sys/fs/cgroup/cgroup.procs exists as a regular file). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1960847/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960847] Re: lxc autopkgtests failures with cgroupv2
** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Summary changed: - lxc autopkgtests failures with cgroupv2 + lxc autopkgtests failures with cgroupv2 on jammy ** Tags added: jammy ubuntu-lxc -- 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/1960847 Title: lxc autopkgtests failures with cgroupv2 on jammy Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: New Bug description: Some lxc autotests (like lxc-test-apparmor-mount for example) are still expecting to find cgroupv1 or a hybrid hierarchy and they just fail on jammy, because systemd is now using a full cgroupv2 hierarchy. Running these tests in a cgroupv2 system is pointless, because it's just going to trigger lots of errors and it's not really stress- testing anything. We should consider to create a new test based on this: https://github.com/lxc/lxc-ci and enable it only on those systems that are using cgroupv2 (for example checking if /sys/fs/cgroup/cgroup.procs exists as a regular file). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1960847/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)
Spotted on linux-gkeop-5.4/5.4.0-1024.25~18.04.1 ** Tags added: sru-20210906 -- 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/1886790 Title: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: In Progress Status in lxc source package in Bionic: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note that this testcase is successful on Focal with the same kernel version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)
** Tags added: sru-20210816 -- 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/1886790 Title: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: In Progress Status in lxc source package in Bionic: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note that this testcase is successful on Focal with the same kernel version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1937945] Re: old gpg keyserver no longer works
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
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/1937945
Title:
old gpg keyserver no longer works
Status in lxc package in Ubuntu:
Confirmed
Bug description:
This is with lxc 1:4.0.6-0ubuntu1~20.04.1 on Ubuntu 20.04 LTS.
All lxc-create commands that need to download GPG keys fail with
something similar to:
$ lxc-create -n foobar -t download -- -d ubuntu -r focal -a amd64
The cached copy has expired, re-downloading...
Setting up the GPG keyring
ERROR: Unable to fetch GPG key from keyserver
lxc-create: foobar: lxccontainer.c: create_run_template: 1616 Failed to
create container from template
It turns out that the GPG keyserver used (pool.sks-keyservers.net) no
longer produces the expected responses. Upstream lxc has a ticket for
this:
https://github.com/lxc/lxc/issues/3894 ('lxc-create fails because
"ERROR: Unable to fetch GPG key from keyserver')
and it was fixed by changing:
DOWNLOAD_KEYSERVER="hkp://pool.sks-keyservers.net"
to:
DOWNLOAD_KEYSERVER="hkp://keyserver.ubuntu.com"
in this commit:
https://github.com/lxc/lxc/commit/f2a5d95d00a55bed27ef9920d67617cc75fecad8
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1937945/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776381] Re: lxc-test-api-reboot will hang with autopkgtest
ubuntu@s2lp3:~$ dpkg -l | grep lxc ii liblxc-common 3.0.3-0ubuntu1~18.04.1 s390xLinux Containers userspace tools (common tools) ii liblxc-dev 3.0.3-0ubuntu1~18.04.1 s390xLinux Containers userspace tools (development) ii liblxc13.0.3-0ubuntu1~18.04.1 s390xLinux Containers userspace tools (library) ii lxc3.0.3-0ubuntu1~18.04.1 all Transitional package - lxc -> lxc-utils rc lxc-common 2.1.1-0ubuntu1 s390xLinux Containers userspace tools (common tools) ii lxc-dev3.0.3-0ubuntu1~18.04.1 all Transitional package - lxc-dev -> liblxc-dev ii lxc-utils 3.0.3-0ubuntu1~18.04.1 s390xLinux Containers userspace tools ii lxc1 3.0.3-0ubuntu1~18.04.1 all Transitional package - lxc1 -> lxc-utils ii lxcfs 3.0.3-0ubuntu1~18.04.2 s390xFUSE based filesystem for LXC -- 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/1776381 Title: lxc-test-api-reboot will hang with autopkgtest Status in ubuntu-kernel-tests: Confirmed Status in lxc package in Ubuntu: New Bug description: Steps: 1. Deploy Bionic on a bare-metal system. 2. Enable deb-src, install the autopkgtest package 3. sudo autopkgtest lxc -- null Result: * The test will hang, a "reboot" lxc container will be created. The last message on the screen will be: make[1]: Entering directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' make[1]: Nothing to be done for 'all-am'. make[1]: Leaving directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' * Tried to connect to the "reboot" container with "sudo lxc-console reboot", but nothing there: Connected to tty 1 Type to exit the console, to enter Ctrl+a itself * If you kill the job and run it again, this time the test will go on (fail with the lxc-test-api-reboot test, as the container has already been created) This issue can be reproduced on an amd64 box and a s390x zKVM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1776381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776381] Re: lxc-test-api-reboot will hang with autopkgtest
Note: s2lp3 here is our Bionic s390x LPAR instance -- 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/1776381 Title: lxc-test-api-reboot will hang with autopkgtest Status in ubuntu-kernel-tests: Confirmed Status in lxc package in Ubuntu: New Bug description: Steps: 1. Deploy Bionic on a bare-metal system. 2. Enable deb-src, install the autopkgtest package 3. sudo autopkgtest lxc -- null Result: * The test will hang, a "reboot" lxc container will be created. The last message on the screen will be: make[1]: Entering directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' make[1]: Nothing to be done for 'all-am'. make[1]: Leaving directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' * Tried to connect to the "reboot" container with "sudo lxc-console reboot", but nothing there: Connected to tty 1 Type to exit the console, to enter Ctrl+a itself * If you kill the job and run it again, this time the test will go on (fail with the lxc-test-api-reboot test, as the container has already been created) This issue can be reproduced on an amd64 box and a s390x zKVM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1776381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776381] Re: lxc-test-api-reboot will hang with autopkgtest
I tried the following on a s390x LPAR instance with Bionic 4.15 kernel: $ sudo lxc-create -t /usr/share/lxc/templates/lxc-busybox -n test $ sudo lxc-ls test $ sudo lxc-start test $ sudo lxc-attach test # Make sure the container is running here # Use another terminal on this instance to do lxc-stop $ sudo lxc-stop test lxc-stop: test: commands_utils.c: lxc_cmd_sock_rcv_state: 70 Resource temporarily unavailable - Failed to receive message $ echo $? 0 The container terminated. -- 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/1776381 Title: lxc-test-api-reboot will hang with autopkgtest Status in ubuntu-kernel-tests: Confirmed Status in lxc package in Ubuntu: New Bug description: Steps: 1. Deploy Bionic on a bare-metal system. 2. Enable deb-src, install the autopkgtest package 3. sudo autopkgtest lxc -- null Result: * The test will hang, a "reboot" lxc container will be created. The last message on the screen will be: make[1]: Entering directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' make[1]: Nothing to be done for 'all-am'. make[1]: Leaving directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' * Tried to connect to the "reboot" container with "sudo lxc-console reboot", but nothing there: Connected to tty 1 Type to exit the console, to enter Ctrl+a itself * If you kill the job and run it again, this time the test will go on (fail with the lxc-test-api-reboot test, as the container has already been created) This issue can be reproduced on an amd64 box and a s390x zKVM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1776381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776381] Re: lxc-test-api-reboot will hang with autopkgtest
Re-open this bug, the reason why this was not reported for a while is because of bug 1788574. On the first attempt we tried to run the test, and it hangs with this issue. The second attempt this test will fail due to the container already exists. The the container properly removed, this is hitting us again on Bionic 4.15 s390x ** Changed in: lxc (Ubuntu) Status: Invalid => New -- 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/1776381 Title: lxc-test-api-reboot will hang with autopkgtest Status in ubuntu-kernel-tests: Confirmed Status in lxc package in Ubuntu: New Bug description: Steps: 1. Deploy Bionic on a bare-metal system. 2. Enable deb-src, install the autopkgtest package 3. sudo autopkgtest lxc -- null Result: * The test will hang, a "reboot" lxc container will be created. The last message on the screen will be: make[1]: Entering directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' make[1]: Nothing to be done for 'all-am'. make[1]: Leaving directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' * Tried to connect to the "reboot" container with "sudo lxc-console reboot", but nothing there: Connected to tty 1 Type to exit the console, to enter Ctrl+a itself * If you kill the job and run it again, this time the test will go on (fail with the lxc-test-api-reboot test, as the container has already been created) This issue can be reproduced on an amd64 box and a s390x zKVM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1776381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903612] Re: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel
** Changed in: kmod (Ubuntu) Status: New => Fix Released ** Changed in: kmod (Ubuntu Bionic) Status: New => Confirmed -- 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/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in kmod package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: Confirmed Status in kmod source package in Bionic: Confirmed Status in linux-hwe source package in Bionic: Confirmed Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 07/22/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help
[Touch-packages] [Bug 1903612] Re: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel
Hello Youhei, we have found the `modinfo` command (from the kmod package[1]) will need to be at least with version 27 (which is available in Focal) to support reading information from built-in modules. To be more precise, with these commits: https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/commit/?h=v27=60084cf1cb24dc3a257976c0d539a4c3ffda5db5 https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/commit/?h=v27=73eed2aba3cbe18bbda40f18f7bc32e8de1ec81f https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/commit/?h=v27=b866b2165ae6cf18fb26b635f4a7ee57c0334731 https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/commit/?h=v27=e7e2cb61fa9f1db3429d91ef6accff549500d268 I have these changes backported here: https://code.launchpad.net/~cypressyew/ubuntu/+source/kmod/+git/kmod/+ref/builtin-test If you want to give this a try, you can clone this repo and do the following: git clone -b builtin-test https://git.launchpad.net/~cypressyew/ubuntu/+source/kmod sudo apt install gtk-doc-tools autoconf automake libtool cd kmod ./autogen.sh ./configure CFLAGS='-g -O2' --prefix=/usr --sysconfdir=/etc --libdir=/usr/lib --with-rootprefix= --with-rootlibdir=/lib make cd tools ./modinfo vfio-pci This will fix this modinfo issue, it can print the built-in module info correctly. Hopefully we can push this to Ubuntu archive later. Regarding DPDK, I have no experience with it, not sure if it will use the modinfo command here (a quick check with their repository[2] I didn't see it calling modinfo directly.) I found this article with keyword "unused vfio-pci dpdk" on the Internet, it looks like you will have to bind the driver to the device with something like: # dpdk-devbind -b vfio-pci :01:00.0 :01:00.1 Hope this helps: https://www.miraclelinux.com/tech-blog/gofc5x [1] https://launchpad.net/ubuntu/+source/kmod [2] https://github.com/DPDK/dpdk -- 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/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in kmod package in Ubuntu: New Status in linux-hwe package in Ubuntu: Confirmed Status in kmod source package in Bionic: New Status in linux-hwe source package in Bionic: Confirmed Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
[Touch-packages] [Bug 1931064] Re: lxc autotest failure with kernel >= 5.13
** Tags added: impish
--
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/1931064
Title:
lxc autotest failure with kernel >= 5.13
Status in ubuntu-kernel-tests:
New
Status in lxc package in Ubuntu:
New
Bug description:
The lxc autotest is failing with the following error(s) on the latest
kernel linux-unstable 5.13:
FAIL: lxc-tests: lxc-test-apparmor (1s)
---
failed - opened /sys/kernel/uevent_helper
---
PASS: lxc-tests: lxc-test-apparmor-generated (0s)
PASS: lxc-tests: lxc-test-apparmor-mount (29s)
FAIL: lxc-tests: lxc-test-attach (1s)
---
attach.c: 410: main: Using "/tmp/attach_x8lgO2" as temporary log file for
container lxc-attach-test
I was able to bisect the problem and found that the offending commit
is:
bfb819ea20ce8bbeeba17e1a6418bf8bda91fc28 ("proc: Check
/proc/$pid/attr/ writes against file opener")
This commit looks like a sane fix, so simply reverting it in the
kernel doesn't seem a viable solution.
I think we should address and understand the issue in the lxc package.
Detailed log of the failure: https://autopkgtest.ubuntu.com/results
/autopkgtest-impish-canonical-kernel-team-
bootstrap/impish/amd64/l/lxc/20210601_082733_a3ae4@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1931064/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1931064] Re: lxc autotest failure with kernel >= 5.13
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Tags added: 5.13 ubuntu-lxc
** Tags added: sru-20210531
--
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/1931064
Title:
lxc autotest failure with kernel >= 5.13
Status in ubuntu-kernel-tests:
New
Status in lxc package in Ubuntu:
New
Bug description:
The lxc autotest is failing with the following error(s) on the latest
kernel linux-unstable 5.13:
FAIL: lxc-tests: lxc-test-apparmor (1s)
---
failed - opened /sys/kernel/uevent_helper
---
PASS: lxc-tests: lxc-test-apparmor-generated (0s)
PASS: lxc-tests: lxc-test-apparmor-mount (29s)
FAIL: lxc-tests: lxc-test-attach (1s)
---
attach.c: 410: main: Using "/tmp/attach_x8lgO2" as temporary log file for
container lxc-attach-test
I was able to bisect the problem and found that the offending commit
is:
bfb819ea20ce8bbeeba17e1a6418bf8bda91fc28 ("proc: Check
/proc/$pid/attr/ writes against file opener")
This commit looks like a sane fix, so simply reverting it in the
kernel doesn't seem a viable solution.
I think we should address and understand the issue in the lxc package.
Detailed log of the failure: https://autopkgtest.ubuntu.com/results
/autopkgtest-impish-canonical-kernel-team-
bootstrap/impish/amd64/l/lxc/20210601_082733_a3ae4@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1931064/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651500] Re: [ASUS X441SA] [8086:2284] No sound at all
Hi W.R. Irsyad Hamda, Looks like this is the fix: https://github.com/torvalds/linux/commit/216d7aebbfbe1d3361e21c3a97d1607e1c1c48cd It's been added to Bionic: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/tree/sound/pci/hda/patch_realtek.c#n7071 And Focal kernel. https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/tree/sound/pci/hda/patch_realtek.c#n7887 As this bug is quite old, do you still need the fix in 4.4 Xenial? Thanks ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1651500 Title: [ASUS X441SA] [8086:2284] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: 1. Release of ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 2. version of the package AlsaMixer v1.1.0 3. I expect to hear sound from speaker 4. I can not any sound from speaker ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hamda 1627 F pulseaudio CurrentDesktop: Unity Date: Tue Dec 20 22:51:08 2016 InstallationDate: Installed on 2016-12-15 (5 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hamda 1627 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X441SA, Realtek ALC3236, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X441SA.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X441SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX441SA.301:bd08/08/2016:svnASUSTeKCOMPUTERINC.:pnX441SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X441SA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1651500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884024] Re: lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4
https://github.com/lxc/lxc/issues/3616 -- 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/1884024 Title: lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4 Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: New Bug description: Issue found on with 5.4.0-1016.16~18.04.1-oracle on both VM.Standard2.1 and VM.Standard2.16 Test failed with: FAIL: lxc-tests: lxc-test-device-add-remove (1s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... This issue can be found on oracle : 5.4.0-1011.11~18.04.1 on VM.Standard2.16 but passed on VM.Standard2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1884024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884024] Re: lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4
Test output on node gummo (5.4.0-60-generic #67~18.04.1) ** Attachment added: "test.log" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1884024/+attachment/5451631/+files/test.log ** Bug watch added: LXC bug tracker #3616 https://github.com/lxc/lxc/issues/3616 -- 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/1884024 Title: lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4 Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: New Bug description: Issue found on with 5.4.0-1016.16~18.04.1-oracle on both VM.Standard2.1 and VM.Standard2.16 Test failed with: FAIL: lxc-tests: lxc-test-device-add-remove (1s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... This issue can be found on oracle : 5.4.0-1011.11~18.04.1 on VM.Standard2.16 but passed on VM.Standard2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1884024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884024] Re: lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4
Syslog output on node gummo (5.4.0-60-generic #67~18.04.1) ** Attachment added: "syslog.log" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1884024/+attachment/5451630/+files/syslog.log -- 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/1884024 Title: lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4 Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: New Bug description: Issue found on with 5.4.0-1016.16~18.04.1-oracle on both VM.Standard2.1 and VM.Standard2.16 Test failed with: FAIL: lxc-tests: lxc-test-device-add-remove (1s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... This issue can be found on oracle : 5.4.0-1011.11~18.04.1 on VM.Standard2.16 but passed on VM.Standard2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1884024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848862] Re: HP Elitebook 840 G1 - 19.10 - Microphone mute key does not work
https://github.com/systemd/systemd/commit/b0eb3d6ed2ab3a7920e7139d62b04a88b2fa6382 This fix has been merged. I will close this bug, thanks! ** Changed in: systemd (Ubuntu) Status: In Progress => Fix Released -- 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/1848862 Title: HP Elitebook 840 G1 - 19.10 - Microphone mute key does not work Status in systemd package in Ubuntu: Fix Released Bug description: I just installed Ubuntu 19.10 on my HP Elitebook 840 G1. Switching from Windows to Ubuntu for personal use. The mic does not enable/disable with FN+F8 combo and the light is constantly on. I found the following solution to my problem. However, I do not know how to implement it in Ubuntu 19.10 (new to Ubuntu and generally not as techinical). https://wiki.archlinux.org/index.php/HP_EliteBook_840_G1#Enable_the_microphone_muting_key 1. Would greatly appreciate if someone could point me to step by step instructions to install the code from the link above. I can report back if this resolve the issue. 2. Also, is there a way to incorporate a fix for this issue with HP laptops in Ubuntu going forward? When I was searching for a fix, I found this to be a widespread issue with various HP laptops and Ubuntu dating back a couple years. Many thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1848862/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1884024] Re: lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4 Oracle / Azure
** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags added: sru-20201130 ** Summary changed: - lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4 Oracle / Azure + lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4 -- 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/1884024 Title: lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4 Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: New Bug description: Issue found on with 5.4.0-1016.16~18.04.1-oracle on both VM.Standard2.1 and VM.Standard2.16 Test failed with: FAIL: lxc-tests: lxc-test-device-add-remove (1s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... This issue can be found on oracle : 5.4.0-1011.11~18.04.1 on VM.Standard2.16 but passed on VM.Standard2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1884024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854001] Re: pmtu net kernel selftests are skipped on bionic linux-hwe-edge 5.3
We don have this net/pmtu test in bionic 4.15 and this has already landed on 5.4, therefore I will close this bug. ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: iproute2 (Ubuntu Bionic) Status: New => Invalid ** Package changed: linux-hwe-edge (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Bionic) 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 iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1854001 Title: pmtu net kernel selftests are skipped on bionic linux-hwe-edge 5.3 Status in ubuntu-kernel-tests: Fix Released Status in iproute2 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Invalid Status in linux source package in Bionic: Won't Fix Bug description: [Impact] selftests will incorrectly indicate a failure, taking the time of developers to verify a false positive, and preventing us from finding real bugs in the corresponding code. [Test case] Run the script directly and verify there are no failures. sudo ./tools/testing/selftests/net/pmtu.sh [Regression potential] No kernel code was changed, only the test. The fix could cause false positives to happen with newer versions of iproute2, but those were tested as well. 11:52:44 DEBUG| [stdout] # selftests: net: pmtu.sh 11:52:44 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 11:52:44 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 11:52:44 DEBUG| [stdout] # vxlan4 not supported 11:52:44 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] 11:52:44 DEBUG| [stdout] # vxlan4 not supported 11:52:44 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] 11:52:46 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] 11:52:47 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] 11:52:47 DEBUG| [stdout] # geneve4 not supported 11:52:47 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions [SKIP] 11:52:47 DEBUG| [stdout] # geneve4 not supported 11:52:47 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions [SKIP] 11:52:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions [ OK ] 11:52:49 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions [ OK ] 11:52:51 DEBUG| [stdout] # TEST: IPv4 over fou4: PMTU exceptions [ OK ] 11:52:52 DEBUG| [stdout] # TEST: IPv6 over fou4: PMTU exceptions [ OK ] 11:52:53 DEBUG| [stdout] # TEST: IPv4 over fou6: PMTU exceptions [ OK ] 11:52:54 DEBUG| [stdout] # TEST: IPv6 over fou6: PMTU exceptions [ OK ] 11:52:55 DEBUG| [stdout] # TEST: IPv4 over gue4: PMTU exceptions [ OK ] 11:52:57 DEBUG| [stdout] # TEST: IPv6 over gue4: PMTU exceptions [ OK ] 11:52:58 DEBUG| [stdout] # TEST: IPv4 over gue6: PMTU exceptions [ OK ] 11:52:59 DEBUG| [stdout] # TEST: IPv6 over gue6: PMTU exceptions [ OK ] 11:53:00 DEBUG| [stdout] # TEST: vti6: PMTU exceptions [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: PMTU exceptions [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: default MTU assignment [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti6: default MTU assignment [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: MTU setting on link creation [ OK ] 11:53:04 DEBUG| [stdout] # TEST: vti6: MTU setting on link creation [ OK ] 11:53:04 DEBUG| [stdout] # TEST: vti6: MTU changes on link changes [ OK ] 11:53:04 DEBUG| [stdout] # vxlan4 not supported 11:53:04 DEBUG| [stdout] # TEST: ipv4: cleanup of cached exceptions [SKIP] Upgrading iproute2 to 5.2 fixes this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1854001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903612] Re: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel
** Also affects: kmod (Ubuntu) Importance: Undecided Status: New -- 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/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in kmod package in Ubuntu: New Status in linux-hwe package in Ubuntu: Confirmed Status in kmod source package in Bionic: New Status in linux-hwe source package in Bionic: Confirmed Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.173.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 07/22/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/22/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1903612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes
Still visible 4.15.0-1059.65 - oracle on instance VM.DenseIO2.8 only. ** Tags added: sru-20201109 -- 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/1783881 Title: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in systemd source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in systemd source package in Bionic: New Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834782] Re: ASUS Zenbook UX433FN: sound stops working after a couple of seconds
Hello, do you still seeing this issue with the latest kernel on you system? Thanks ** Changed in: linux-hwe (Ubuntu) Status: New => Incomplete ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete ** Changed in: linux-hwe-edge (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1834782 Title: ASUS Zenbook UX433FN: sound stops working after a couple of seconds Status in linux-firmware package in Ubuntu: Incomplete Status in linux-hwe package in Ubuntu: Incomplete Status in linux-hwe-edge package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Invalid Bug description: Issue: whichever sound-related action (sound +/- media keys, spotify song, youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and then stops and becomes silent. The interesting thing is that when I stop playing the audio (ie close the browser tab with a song), after a while when I try aain the sound works again. Yet still for just the few secs. Environment: up-to-date Ubuntu 18.04, tried -hwe, hwe-edge kernels. This is a regression, the sound used to work OK on this machine, and nothing significant related to sound has changed since. Thank you for looking into this bug! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmm 28065 F pulseaudio CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Dependencies: DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2380 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: pulseaudio PackageArchitecture: all ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Tags: bionic wayland-session third-party-packages wayland-session Uname: Linux 4.18.0-25-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/24/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.306:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1834782/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882505] Re: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service
Modify the test, only try to stop systemd-timesyncd when it's running. https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=d64ab9921ce1b43bee676251ff1b57562b99e85b ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- 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/1882505 Title: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service Status in ubuntu-kernel-tests: Fix Released Status in systemd package in Ubuntu: Invalid Bug description: Issue found on 5.4.0-34.38 s390x LPAR / zVM We need to stop timesyncd for the following tests: ['leapsec01','stime01','settimeofday01','clock_settime01'] But it looks like when we're trying to restart it: systemctl start systemd-timesyncd It will fail with: Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service is masked. This issue did not happen on 5.4.0-33.37, the ubuntu_ltp_syscalls test can finish with that kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882505] Re: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service
BTW nothing special for ntp recursive grep -- 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/1882505 Title: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service Status in ubuntu-kernel-tests: New Status in systemd package in Ubuntu: Incomplete Bug description: Issue found on 5.4.0-34.38 s390x LPAR / zVM We need to stop timesyncd for the following tests: ['leapsec01','stime01','settimeofday01','clock_settime01'] But it looks like when we're trying to restart it: systemctl start systemd-timesyncd It will fail with: Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service is masked. This issue did not happen on 5.4.0-33.37, the ubuntu_ltp_syscalls test can finish with that kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882505] Re: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service
This issue can be found on Focal Azure 5.4 The attachment is from the a deployed F-azure-5.4 instance $ dpkg -l | grep ntp $ dpkg -l | grep timesyncd rc systemd-timesyncd 245.4-4ubuntu3.1 amd64minimalistic service to synchronize local time with NTP servers A quick recursive grep for timesyncd shows it's been removed here: Start-Date: 2020-06-03 22:37:42 Commandline: apt-get -y install walinuxagent cifs-utils linux-azure keyutils chrony Install: libwbclient0:amd64 (2:4.11.6+dfsg-0ubuntu1.2, automatic), cifs-utils:amd64 (2:6.9-1), libtalloc2:amd64 (2.3.0-3ubuntu1, automatic), chrony:amd64 (3.5-6ubuntu6.1), keyutils:amd64 (1.6-6ubuntu1), libtevent0:amd64 (0.10.1-4, automatic), walinuxagent:amd64 (2.2.46-0ubuntu1) Remove: systemd-timesyncd:amd64 (245.4-4ubuntu3.1) End-Date: 2020-06-03 22:37:50 ** Attachment added: "log.tar.gz" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882505/+attachment/5381995/+files/log.tar.gz -- 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/1882505 Title: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service Status in ubuntu-kernel-tests: New Status in systemd package in Ubuntu: Incomplete Bug description: Issue found on 5.4.0-34.38 s390x LPAR / zVM We need to stop timesyncd for the following tests: ['leapsec01','stime01','settimeofday01','clock_settime01'] But it looks like when we're trying to restart it: systemctl start systemd-timesyncd It will fail with: Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service is masked. This issue did not happen on 5.4.0-33.37, the ubuntu_ltp_syscalls test can finish with that kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882505] Re: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service
Re-install systemd-timesyncd seem to fix this issue. However while trying to install systemd-timesyncd the ntp package will be removed. Maybe we're using ntp instead of systemd-timesyncd on Focal s390x by default? -- 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/1882505 Title: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service Status in ubuntu-kernel-tests: New Status in systemd package in Ubuntu: Incomplete Bug description: Issue found on 5.4.0-34.38 s390x LPAR / zVM We need to stop timesyncd for the following tests: ['leapsec01','stime01','settimeofday01','clock_settime01'] But it looks like when we're trying to restart it: systemctl start systemd-timesyncd It will fail with: Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service is masked. This issue did not happen on 5.4.0-33.37, the ubuntu_ltp_syscalls test can finish with that kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882505] Re: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service
I tried to remove the /etc/systemd/system/systemd-timesyncd.service symbolic link to /dev/null by following this post [1] After that it's complaining the service was not found: $ sudo systemctl start systemd-timesyncd Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service not found. Hmm... [1] https://blog.ruanbekker.com/blog/2017/12/09/unmask-a-masked-service- in-systemd/ -- 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/1882505 Title: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service Status in ubuntu-kernel-tests: New Status in systemd package in Ubuntu: Incomplete Bug description: Issue found on 5.4.0-34.38 s390x LPAR / zVM We need to stop timesyncd for the following tests: ['leapsec01','stime01','settimeofday01','clock_settime01'] But it looks like when we're trying to restart it: systemctl start systemd-timesyncd It will fail with: Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service is masked. This issue did not happen on 5.4.0-33.37, the ubuntu_ltp_syscalls test can finish with that kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882505] Re: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service
The correct file location for systemd-timesyncd.service should be: $ sudo systemctl enable systemd-timesyncd Failed to enable unit: Unit file /etc/systemd/system/systemd-timesyncd.service is masked. $ file /etc/systemd/system/systemd-timesyncd.service /etc/systemd/system/systemd-timesyncd.service: symbolic link to /dev/null -- 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/1882505 Title: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service Status in ubuntu-kernel-tests: New Status in systemd package in Ubuntu: Incomplete Bug description: Issue found on 5.4.0-34.38 s390x LPAR / zVM We need to stop timesyncd for the following tests: ['leapsec01','stime01','settimeofday01','clock_settime01'] But it looks like when we're trying to restart it: systemctl start systemd-timesyncd It will fail with: Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service is masked. This issue did not happen on 5.4.0-33.37, the ubuntu_ltp_syscalls test can finish with that kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882505] Re: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service
Hello Dimitri, After a quick check it looks like this service is still in inactive (dead) state even after a reboot. ubuntu@kernel04:/lib/systemd$ sudo systemctl status systemd-timesyncd ● systemd-timesyncd.service Loaded: masked (Reason: Unit systemd-timesyncd.service is masked.) Active: inactive (dead) ubuntu@kernel04:/lib/systemd$ file /lib/systemd/system/systemd-timesyncd.service /lib/systemd/system/systemd-timesyncd.service: cannot open `/lib/systemd/system/systemd-timesyncd.service' (No such file or directory) And there is no "systemd-timesyncd.service" file at where is should be. So yeah it's not running, our testing tool did not check the state first before trying to stop / start it. $ sudo systemctl edit systemd-timesyncd Cannot edit systemd-timesyncd.service: unit is masked. Let me see if I can un-mask it. -- 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/1882505 Title: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service Status in ubuntu-kernel-tests: New Status in systemd package in Ubuntu: Incomplete Bug description: Issue found on 5.4.0-34.38 s390x LPAR / zVM We need to stop timesyncd for the following tests: ['leapsec01','stime01','settimeofday01','clock_settime01'] But it looks like when we're trying to restart it: systemctl start systemd-timesyncd It will fail with: Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service is masked. This issue did not happen on 5.4.0-33.37, the ubuntu_ltp_syscalls test can finish with that kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1882505] Re: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service
Looks like this has something to do with systemd, with zVM boot with 5.4.0-33, I can still reproduce this issue: ubuntu@kernel04:~$ sudo systemctl stop systemd-timesyncd ubuntu@kernel04:~$ sudo systemctl start systemd-timesyncd Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service is masked. ubuntu@kernel04:~$ ** Summary changed: - ubuntu_ltp_syscalls failed to run on Focal s390x + ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service ** Also affects: systemd (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. https://bugs.launchpad.net/bugs/1882505 Title: ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart systemd-timesyncd.service Status in ubuntu-kernel-tests: New Status in systemd package in Ubuntu: New Bug description: Issue found on 5.4.0-34.38 s390x LPAR / zVM We need to stop timesyncd for the following tests: ['leapsec01','stime01','settimeofday01','clock_settime01'] But it looks like when we're trying to restart it: systemctl start systemd-timesyncd It will fail with: Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service is masked. This issue did not happen on 5.4.0-33.37, the ubuntu_ltp_syscalls test can finish with that kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869368] Re: ubuntu_qrt_apparmor fails on ADT bionic/linux i386
** Tags added: 4.15 i386 ubuntu-qrt-apparmor -- 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/1869368 Title: ubuntu_qrt_apparmor fails on ADT bionic/linux i386 Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in apparmor source package in Bionic: New Status in linux source package in Bionic: Confirmed Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/l/linux/20200326_224620_0dd01@/log.gz Kernel version: bionic/linux 4.15.0-94.95 The ubuntu_qrt_apparmor.test-apparmor.py fails intermittently on bionic/linux i386 ADT tests. It has failed some releases in the past and I'm seeing the failure in the current release as well. I have not seen this failure on other architectures. These are the last messages on the test log: 20:12:39 ERROR| [stderr] Test mediation of file based SOCK_STREAM connect ... ok 20:12:39 ERROR| [stderr] test_libapparmor_testsuite (__main__.ApparmorTestsuites) 20:14:18 DEBUG| [stdout] unconfined_user can access confined_user's file 20:14:18 DEBUG| [stdout] unconfined_user can access default_user's file 20:14:18 DEBUG| [stdout] unconfined_user can access unconfined_group's file 20:14:18 DEBUG| [stdout] 20:15:42 ERROR| [stderr] Run libapparmor testsuite ... (Applying patch 0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying patch 0001-usr-merge-fixups.patch) ok 20:15:42 ERROR| [stderr] test_libapparmor_testsuite3 (__main__.ApparmorTestsuites) 20:15:52 DEBUG| [stdout] preparing apparmor_2.12-4ubuntu5.1.dsc... done 20:15:52 DEBUG| [stdout] 20:17:10 ERROR| [stderr] Run libapparmor testsuite (with python3) ... (Applying patch 0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying patch 0001-usr-merge-fixups.patch) ok 20:17:10 ERROR| [stderr] test_old_trusty_parser_testsuite (__main__.ApparmorTestsuites) 20:17:10 DEBUG| [stdout] preparing apparmor_2.12-4ubuntu5.1.dsc... done 20:17:10 ERROR| [stderr] Run parser regression tests from 14.04's apparmor_2.8.95~2430-0ubuntu5.3 ... (skipped: This test is only for 14.04 systems with the apparmor 2.10.95 SRU or newer installed) ok 20:17:10 ERROR| [stderr] test_old_trusty_regression_testsuite (__main__.ApparmorTestsuites) 20:17:10 ERROR| [stderr] Run kernel regression tests from 14.04's apparmor_2.8.95~2430-0ubuntu5.3 ... (skipped: This test is only for 14.04 systems with the apparmor 2.10.95 SRU or newer installed) ok 20:17:10 ERROR| [stderr] test_parser_testsuite (__main__.ApparmorTestsuites) 20:17:19 DEBUG| [stdout] 20:52:35 ERROR| [stderr] Run parser regression tests ... (Applying patch 0001-mount-regression-test-convert-mount-test-to-use-MS_N.patch) (Applying patch 0001-usr-merge-fixups.patch) ok 20:52:35 ERROR| [stderr] test_regression_testsuite (__main__.ApparmorTestsuites) 20:52:42 DEBUG| [stdout] preparing apparmor_2.12-4ubuntu5.1.dsc... done 20:52:42 DEBUG| [stdout] 21:01:56 INFO | ERROR ubuntu_qrt_apparmor.test-apparmor.py ubuntu_qrt_apparmor.test-apparmor.pytimestamp=1585256516localtime=Mar 26 21:01:56 Test subprocess failed rc=9 To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1869368/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834192] Re: apparmor mult_mount regression test fails in eoan
** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: qa-regression-testing Status: New => Fix Released -- 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/1834192 Title: apparmor mult_mount regression test fails in eoan Status in QA Regression Testing: Fix Released Status in ubuntu-kernel-tests: Fix Released Status in apparmor package in Ubuntu: Fix Released Bug description: In running adt testing on 5.2-based kernels for eoan, I'm seeing failures from the apparmor mult_mount regression test. Running the test case manually with -x yields: + dd if=/dev/zero of=/tmp/sdtest.2210-22387-i6UxxQ/image.ext3 bs=4096 count=20 + mkfs.ext2 -F -m 0 -N 10 /tmp/sdtest.2210-22387-i6UxxQ/image.ext3 ++ error_handler ++ fatalerror 'Unexpected shell error. Run with -x to debug' Running the following manually in a shell also fails in eoan with the 5.0 kernel copied forward from disco, while it passes in disco: $ uname -a Linux ee-apparmor 5.0.0-17-generic #18-Ubuntu SMP Tue Jun 4 15:34:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ dd if=/dev/zero of=test.img bs=4096 count=20 20+0 records in 20+0 records out 81920 bytes (82 kB, 80 KiB) copied, 0.000406443 s, 202 MB/s $ mkfs.ext2 -F -m 0 -N 10 test.img mke2fs 1.45.2 (27-May-2019) test.img: Not enough space to build proposed filesystem while setting up superblock So this seems likely to be due to some change with mke2fs; not sure if this is a regression there or if the test was getting away with doing something invalid. To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1834192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1134069] Re: [HP Envy 4 Sleekbook] external audio jacks are reversed
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1134069
Title:
[HP Envy 4 Sleekbook] external audio jacks are reversed
Status in alsa-driver package in Ubuntu:
Won't Fix
Bug description:
Looking at the outside of the system, the external audio jacks are in
this order:
Mic ___Headphone ___
However, on testing, it appears that they are either mislabled, or the
outputs are reversed internally. I had to plug the headphones into
the Mic jack to hear sound, and plug the mic into the headphone jack
to record sound.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-25-generic 3.5.0-25.39~precise1
ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4
Uname: Linux 3.5.0-25-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1545 F pulseaudio
/dev/snd/pcmC0D0c: ubuntu 1545 F...m pulseaudio
CRDA:
country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x5071 irq 48'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:111d76e0,103c1894,00100102
HDA:80862806,80860101,0010'
Controls : 24
Simple ctrls : 11
Date: Wed Feb 27 03:05:29 2013
HibernationDevice: RESUME=UUID=286b25cc-7928-4406-854e-6c1cae69a6e6
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64
(20130213)
MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic
root=UUID=0c6af5a9-e287-43f5-8ce6-647a4ae228f2 ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-25-generic N/A
linux-backports-modules-3.5.0-25-generic N/A
linux-firmware1.79.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/31/2012
dmi.bios.vendor: Insyde
dmi.bios.version: B.38
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 1894
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 72.66
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrB.38:bd10/31/2012:svnHewlett-Packard:pnHPPaviliondm4NotebookPC:pvr088810250E102:rvnHewlett-Packard:rn1894:rvr72.66:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion dm4 Notebook PC
dmi.product.version: 088810250E102
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1134069/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434447] Re: apport reports are not complete for filing bugs against linux-lts-utopic kernel
** Changed in: apport (Ubuntu) Status: Incomplete => Invalid ** Changed in: apport (Ubuntu) Status: Invalid => Won't Fix ** Changed in: apport (Ubuntu Utopic) Status: Confirmed => Won't Fix ** Changed in: apport (Ubuntu Trusty) Status: Confirmed => Won't Fix -- 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/1434447 Title: apport reports are not complete for filing bugs against linux-lts- utopic kernel Status in apport package in Ubuntu: Won't Fix Status in apport source package in Trusty: Won't Fix Status in apport source package in Utopic: Won't Fix Bug description: When filing a bug with ubuntu-bug linux command on 14.04.2, it won't collect extra reports for attachment. Only Dependencies.txt and ProcEnviron.txt will be attached to the report. (See bug 1434442) Similar bugs: bug 1352829, bug 1229611 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu3.7 ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 20 04:36:34 2015 InstallationDate: Installed on 2015-03-20 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1434447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854001] Re: pmtu net kernel selftests are skipped on bionic linux-hwe-edge 5.3
Patch applied upstream: https://github.com/torvalds/linux/commit/2745aea6750ff0d2c48285d25bdb00e5b636ec8b It can be backported now. -- 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/1854001 Title: pmtu net kernel selftests are skipped on bionic linux-hwe-edge 5.3 Status in ubuntu-kernel-tests: New Status in iproute2 package in Ubuntu: Fix Released Status in linux-hwe-edge package in Ubuntu: In Progress Status in iproute2 source package in Bionic: New Status in linux-hwe-edge source package in Bionic: In Progress Bug description: [Impact] selftests will incorrectly indicate a failure, taking the time of developers to verify a false positive, and preventing us from finding real bugs in the corresponding code. [Test case] Run the script directly and verify there are no failures. sudo ./tools/testing/selftests/net/pmtu.sh [Regression potential] No kernel code was changed, only the test. The fix could cause false positives to happen with newer versions of iproute2, but those were tested as well. 11:52:44 DEBUG| [stdout] # selftests: net: pmtu.sh 11:52:44 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 11:52:44 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 11:52:44 DEBUG| [stdout] # vxlan4 not supported 11:52:44 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] 11:52:44 DEBUG| [stdout] # vxlan4 not supported 11:52:44 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] 11:52:46 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] 11:52:47 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] 11:52:47 DEBUG| [stdout] # geneve4 not supported 11:52:47 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions [SKIP] 11:52:47 DEBUG| [stdout] # geneve4 not supported 11:52:47 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions [SKIP] 11:52:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions [ OK ] 11:52:49 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions [ OK ] 11:52:51 DEBUG| [stdout] # TEST: IPv4 over fou4: PMTU exceptions [ OK ] 11:52:52 DEBUG| [stdout] # TEST: IPv6 over fou4: PMTU exceptions [ OK ] 11:52:53 DEBUG| [stdout] # TEST: IPv4 over fou6: PMTU exceptions [ OK ] 11:52:54 DEBUG| [stdout] # TEST: IPv6 over fou6: PMTU exceptions [ OK ] 11:52:55 DEBUG| [stdout] # TEST: IPv4 over gue4: PMTU exceptions [ OK ] 11:52:57 DEBUG| [stdout] # TEST: IPv6 over gue4: PMTU exceptions [ OK ] 11:52:58 DEBUG| [stdout] # TEST: IPv4 over gue6: PMTU exceptions [ OK ] 11:52:59 DEBUG| [stdout] # TEST: IPv6 over gue6: PMTU exceptions [ OK ] 11:53:00 DEBUG| [stdout] # TEST: vti6: PMTU exceptions [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: PMTU exceptions [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: default MTU assignment [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti6: default MTU assignment [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: MTU setting on link creation [ OK ] 11:53:04 DEBUG| [stdout] # TEST: vti6: MTU setting on link creation [ OK ] 11:53:04 DEBUG| [stdout] # TEST: vti6: MTU changes on link changes [ OK ] 11:53:04 DEBUG| [stdout] # vxlan4 not supported 11:53:04 DEBUG| [stdout] # TEST: ipv4: cleanup of cached exceptions [SKIP] Upgrading iproute2 to 5.2 fixes this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1854001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 882147] Re: overlayfs does not implement inotify interfaces correctly
Closing this bug with Won't fix as this kernel / release is no longer supported. Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04) Thanks! ** Changed in: linux (Ubuntu) Status: Triaged => Won't Fix ** Changed in: linux (Ubuntu Precise) Status: Triaged => Won't Fix ** Changed in: coreutils (Ubuntu) Status: In Progress => Won't Fix ** Changed in: coreutils (Ubuntu Precise) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/882147 Title: overlayfs does not implement inotify interfaces correctly Status in coreutils package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in coreutils source package in Precise: Won't Fix Status in linux source package in Precise: Won't Fix Bug description: When using tail on the liveCD some updates are not reported. This seems to be triggered by tail using inotify to identify modified files. Overlayfs does not appear to be implementing inotify quite the way you might hope reporting only against the underlying filesystems. Related bugs: * bug 1213925: upstart should notice "/etc" inode change ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-12-generic 3.0.0-12.20 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu3 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: apw2296 F pulseaudio /dev/snd/pcmC0D0c: apw2296 F...m pulseaudio /dev/snd/pcmC0D0p: apw2296 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc70 irq 47' Mixer name : 'Intel Cantiga HDMI' Components : 'HDA:111d7675,1028029f,00100103 HDA:80862802,80860101,0010' Controls : 20 Simple ctrls : 11 Date: Wed Oct 26 17:46:16 2011 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d8328455-deac-4bae-877d-c408d371cefe MachineType: Dell Inc. Studio 1537 ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=cf503727-25f2-4ecd-b0f3-2b894523bcba ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-12-generic N/A linux-backports-modules-3.0.0-12-generic N/A linux-firmware1.60 SourcePackage: linux UpgradeStatus: Upgraded to oneiric on 2011-10-17 (9 days ago) WpaSupplicantLog: dmi.bios.date: 09/22/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A03 dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/22/2008:svnDellInc.:pnStudio1537:pvrA03:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrA03: dmi.product.name: Studio 1537 dmi.product.version: A03 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/882147/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676912] Re: Kernel 4.9+ regression: Suspend - Freezing of tasks failed
Closing this bug with Won't fix as this kernel / release is no longer supported. Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04) Thanks! ** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1676912 Title: Kernel 4.9+ regression: Suspend - Freezing of tasks failed Status in linux package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: Won't Fix Bug description: Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu Gnome 17.04 and since then sometimes my Laptop won't suspend when I close the lid. The power led does not blink like it is supposed to do and when I open the Laptop the lockscreen appears but freezes after a short time, followed by a blackscreen until eventually it reappears and allows me to unlock it. After that certain application can not be started anymore and would freeze if they were running before. These include Chrome, Gedit and Gnome System Monitor for example. Also my Laptop will not connect to my WLAN until I restart it. In syslog I found the line: "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to freeze, wq_busy=0):" According to syslog network-nanaeger whoopsie cups-browsed wpa-supplicant geoclue packagekitd several evolution-related processes goa-daemon gnome-software geary dropbox deja-dup-monitor are responsible. I tried disabling some of them, but it did not solve the problem. Update: I tested different Kernel versions in the last days. So far there were no issues with suspend/resume using Kernel 4.8 and 4.9. The problem is present in 4.10 and 4.11. Update 2: I just encountered this issue with Kernel 4.9. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 28 16:27:34 2017 InstallationDate: Installed on 2017-03-24 (3 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: LENOVO 80J8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B8CN31WW(V2.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paganini dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 3 11 dmi.modalias: dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311: dmi.product.name: 80J8 dmi.product.version: Lenovo Yoga 3 11 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 620931] Re: earphone has no sound on iMac 8, 1
Closing this bug with Won't fix as this kernel / release is no longer supported. Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04) Thanks! ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/620931 Title: earphone has no sound on iMac 8,1 Status in alsa-driver package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: I'm using an iMac 8,1 with Ubuntu 10.10. I plugged the earphone, but the sound is still from the speaker. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xhacker1490 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0x9060 irq 47' Mixer name : 'Realtek ALC889A' Components : 'HDA:10ec0885,106b3e00,00100103' Controls : 21 Simple ctrls : 11 DistroRelease: Ubuntu 10.10 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) NonfreeKernelModules: wl Package: alsa-base 1.0.23+dfsg-1ubuntu2 PackageArchitecture: all ProcEnviron: LANGUAGE=zh_CN:zh PATH=(custom, no user) LANG=zh_CN.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.35-19.26-generic 2.6.35.3 Tags: ubuntu-une maverick Uname: Linux 2.6.35-19-generic i686 UserGroups: dmi.bios.date: 02/09/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM81.88Z.00C1.B00.0802091538 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F227BEC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F227BEC8 dmi.modalias: dmi:bvnAppleInc.:bvrIM81.88Z.00C1.B00.0802091538:bd02/09/08:svnAppleInc.:pniMac8,1:pvr1.0:rvnAppleInc.:rnMac-F227BEC8:rvrPVT:cvnAppleInc.:ct13:cvrMac-F227BEC8: dmi.product.name: iMac8,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/620931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 429109] Re: 0x103c08b0 needs HP_ONLY ac97 quirk
Closing this bug with Won't fix as this kernel / release is no longer supported. Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04) Thanks! ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/429109 Title: 0x103c08b0 needs HP_ONLY ac97 quirk Status in Linux: Incomplete Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Invalid Bug description: Binary package hint: pulseaudio I'm running latest Karmic on a HP TC1100. GNOME volume slider works as follows (you can examine it by running alsamixer -c 0 and looking at ALSA mixer levels): 1. When the volume slider is at 0, both PCM and Master are at 0 2. Now when we start increasing the volume, PCM gets increased and Master starts at 0 (but unmuted), until PCM is equal to 71%; this is at about 10% slider volume 3. Then Master is increased from 0 to 100% while PCM is kept at 74%, this happens until about 63% volume 4. Finally, PCM is increased from 74% to 100% This behavior, apparently implemented in PulseAudio, is perfect (it ensures minimum distortion from cheap audio cards), but I have one problem: phase 3 only increases Master, and ignores Headphones. This means that the volume slider does nothing to headphone volume between approximately 10 and 63%. The GConf setting at /desktop/gnome/sound/default_mixer_tracks that was used to set this doesn't work anymore. An acceptable workaround would be to tie together Master and Headphone channels at the ALSA level, so that setting one would update the other, but I have no idea how to do this. A proper solution would be to update both Master and Headphones channels in phase 3. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/429109/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 456564] Re: Another sound problem (volume and balance)
Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on
a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/456564
Title:
Another sound problem (volume and balance)
Status in linux package in Ubuntu:
Won't Fix
Status in pulseaudio package in Ubuntu:
Invalid
Bug description:
Binary package hint: pulseaudio
Hi,
just upgraded to current Karmic beta. All went fine and well, but I
have one issueabout the volume control - as it's working now it's
almost dangerous.
When I adjust the volume slider I can max out my laptop speakers at
about 15%, any higher and they are about to blow. When using a headset
I can't go over 9% before the sound gets dangerously loud. When using
the volume buttons on my laptop I can start at 0%, then click two
times until the volume becomes so loud (12%) I don't dare go any
further when wearing a headset...In Jaunty I had a much more fine-
grained control.
After inspecting how the new volume control works, I see that it
adjusts both the master volume and the PCM according to some
algorithm. While in concept I understand this is smart in order to
keep noise down, it works really terrible in my case. Imagine having a
computer that if someone (or something!) sets the volume to anything
above 20% and your speakers (and hearing) stand a good chance to blow.
Laptop:
Fujitsu Siemens Si1520.
lspci -v attached.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sveint 3353 F pulseaudio
/dev/snd/pcmC0D0p: sveint 3353 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xdc24 irq 22'
Mixer name : 'Conexant CX20549 (Venice)'
Components : 'HDA:14f15045,173410ad,00100100'
Controls : 18
Simple ctrls : 8
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386
(20100419.1)
Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
PackageArchitecture: all
ProcEnviron:
LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
LANG=nb_NO.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Tags: lucid
Uname: Linux 2.6.32-22-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/21/2006
dmi.bios.vendor: Phoenix
dmi.bios.version: 1.10
dmi.board.name: 10AD
dmi.board.vendor: FUJITSU
dmi.board.version: 3D22
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenix:bvr1.10:bd07/21/2006:svnFUJITSUSIEMENS:pnAmiloSi1520:pvrRev1:rvnFUJITSU:rn10AD:rvr3D22:cvnFUJITSUSIEMENS:ct10:cvrN/A:
dmi.product.name: Amilo Si 1520
dmi.product.version: Rev 1
dmi.sys.vendor: FUJITSU SIEMENS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/456564/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 510004] Re: [lucid regression] random graphics effects after resume from suspend to RAM
Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on
a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/510004
Title:
[lucid regression] random graphics effects after resume from suspend
to RAM
Status in linux package in Ubuntu:
Won't Fix
Status in nvidia-graphics-drivers package in Ubuntu:
Invalid
Status in pm-utils package in Ubuntu:
Fix Released
Bug description:
On this laptop, resume from suspend to RAM barely works under Lucid,
while it works flawlessly under Jaunty.
These are the most salient aberrations:
1) The display comes back in a strange pattern of random colors and
characters. It looks like the display is in console mode, but the screen saver
seems to be active, since if I type in my password I will later find the
display unlocked.
2) To actually get to a sane display, I have found that switching between a
few virtual consoles will eventually do the trick. If I did not blindly type in
my password earlier on, I will now see the screen saver's password prompt.
3) When I finally get back to Gnome, I find that the desktop background has
changed to an irregular black-and-white pattern.
4) After resume, the machine thinks it is running on battery, so the display
is dimmed to the lowest setting, and the battery icon is displayed.
I don't find this behavior acceptable, especially since the same
function used to work perfectly on the same hardware in an earlier OS
version.
ProblemType: Bug
Architecture: amd64
Date: Wed Jan 20 09:17:12 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: pm-utils 1.3.0~rc1-0ubuntu1
PackageArchitecture: all
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
SourcePackage: pm-utils
Tags: lucid
Uname: Linux 2.6.32-10-generic x86_64
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC262 Analog [ALC262 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pang 2192 F pulseaudio
/dev/snd/pcmC0D0p: pang 2192 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfef0 irq 22'
Mixer name : 'Realtek ALC262'
Components : 'HDA:10ec0262,18540120,0012'
Controls : 20
Simple ctrls : 12
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=2a4d2eac-9fba-4760-849b-e366ea52a359
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
MachineType: LG Electronics P300-T.APE4V
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-12-generic
root=UUID=01ebab7a-379c-48c8-87d6-a2800f6dccfd ro quiet splash
ProcVersionSignature: Ubuntu 2.6.32-12.16-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.29
Reproducible: Yes
Tags: lucid needs-upstream-testing regression-potential
TestedUpstream: No
Uname: Linux 2.6.32-12-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 06/30/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: ELGNSF18
dmi.board.name: ELGON
dmi.board.vendor: LG Electronics
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LG Electronics
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvrELGNSF18:bd06/30/2008:svnLGElectronics:pnP300-T.APE4V:pvrNotApplicable:rvnLGElectronics:rnELGON:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A:
dmi.product.name: P300-T.APE4V
dmi.product.version: Not Applicable
dmi.sys.vendor: LG Electronics
---
Architecture: amd64
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: nvidia-current 190.53-0ubuntu12
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 2.6.32-12.16-generic
Tags: lucid
Uname: Linux 2.6.32-12-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/510004/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe :
[Touch-packages] [Bug 195982] Re: Shift key (and caps lock) stop working when using VMWare
Closing this bug with Won't fix as this kernel is no longer supported. Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04) Thanks! ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/195982 Title: Shift key (and caps lock) stop working when using VMWare Status in Linux: Invalid Status in linux package in Ubuntu: Won't Fix Status in xkeyboard-config package in Ubuntu: Invalid Status in Gentoo Linux: New Bug description: [Problem] VMWare's keyboard mapping is imperfect, sometimes resulting in certain keys stopping functionality when running under VMWare, requiring the user to setup their configuration settings manually in VMWare. For a detailed explanation see the following article: http://www.vmware.com/support/ws55/doc/ws_devices_keymap_linux_longer.html [Original Report] After a day or so of running the shift key mysteriously stops working as does the cap lock. In other words I cannot enter shifted characters of any kind. The keyboard is connected to a KVM and all other systems respond to it properly. In additional any VMWare sessions I have open respond correctly. So I have the condition where all non-vmware applications in Ubuntu Hardy (all updates applied as of 2008-02-26 at 12:43 UTC) fail to recognize the shift key BUT applications within an active (a paused/restarted session also works) VMWare sessions running DO recognize the key. When this condition occurs ALL applications (except those within a VMWare session) are also unstable and will usually crash within a few keystrokes.If I continue to operate in this mode. I cannot pinpoint what, if any, application triggers this. It has always happened while working within terminal/browser/vmware sessions and NOT when opening a new application. It could be related to the KVM switch, but none of my other systems (2 Mandriva, 1 Windows) are affected by this. This bug has been present on my system for a number of days across daily updates and reboots (if the update requested it) and I think since I installed Hardy Alpha 1. A work around: log off and back on. A reboot/restart does not appear to be needed. Error logs show some unusual activity. --- MARK ... ... kernel ... rtc lost 7 interrupts ... --- MARK --- Plus some segfaults indicating which application crashed as I tried to type into it (mouse works fine). System: HP dv9743cl (which otherwise works lovely) Ubuntu: Hardy 8.04 (from lsb-release) TEST CASE: 1. Click inside the VM and 2. Hold any of the Ctrl, Alt and/or shift keys while releasing the keyboard/mouse to the host OS (which you obviously do when you press Crtl-Alt to revert back to windowed mode, as the cursor is then released from the VM). WORKAROUND: After this happens to recover your keyboard execute 'setxkbmap' in a terminal To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/195982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 183303] Re: Can't create new wireless network using mac80211 based drivers
Closing this bug with Won't fix as this kernel is no longer supported. Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04) Thanks! ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix -- 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/183303 Title: Can't create new wireless network using mac80211 based drivers Status in NetworkManager: Unknown Status in linux package in Ubuntu: Won't Fix Status in ltsp package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in wpasupplicant package in Ubuntu: Fix Released Status in network-manager package in Debian: Fix Released Bug description: I am trying to create a new wireless network (particularly, with no encryption) with the gnome applet. However, I just get the message "Trying to connect to wireless network «(null)»". Then, after a couple of minutes or so, it gets back to the cabled connection and no wireless connection is created. I am using Gutsy, network-manager 0.6.5-0ubuntu16.7.10.0 and network- manager-gnome 0.6.5-0ubuntu11~7.10.0. Updated description: The original reporter used ipw2200, but for that driver a bug has already been reported for this isse: Bug #75358. This bug now addresses users with mac20811-based drivers, since the majority of the commenters have such cards/drivers. The bug has persisted in Gutsy, Hardy, Intrepid and even Jaunty RC... To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/183303/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 616064] Re: Broken networking in kvm guests with pcnet driver
Closing this bug with Won't fix as Lucid is no longer supported. Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04) Thanks! ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: qemu-kvm (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/616064 Title: Broken networking in kvm guests with pcnet driver Status in bridge-utils package in Ubuntu: Invalid Status in linux package in Ubuntu: Won't Fix Status in qemu-kvm package in Ubuntu: Won't Fix Bug description: Binary package hint: qemu-kvm Some TCP operations receive unexpected reset (RST) packets when executed on the guest. I can see these RST packets via Wireshark but can't explain their source. This breaks certain (most) networking on the guest. I uncovered this when some 'git clone' operations failed with "Broken Pipe" in the guests. I've been able to reproduce the same failures using scp and 'svn checkout'. The failure occurs 80-90% of the time and 'svn checkout' seems to be the quickest to fail. The same operations on the host are always successful. My setup is a Lucid amd64 host with two guests (Lucid and Hardy, both i386, using kvm). Networking seems to mostly work. I can maintain persistent ssh connections to the guest and some networking operations from the guest (ie. ping) never fail. However, the git-clone/scp/svn- checkout operations fail almost all the time. I've tried this with both virtio and e1000 drivers with no difference. This may be similar to some of the behavior reported in bug 584048 but not the final patch referenced in comment 27. I built a custon deb including the upstream patch for testing and it had no effect. BIOS: http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5080935 $ apt-cache policy qemu-kvm qemu-kvm: Installed: 0.12.3+noroms-0ubuntu9.2 Candidate: 0.12.3+noroms-0ubuntu9.2 Version table: *** 0.12.3+noroms-0ubuntu9.2 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status 0.12.3+noroms-0ubuntu9 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: kvm 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9.2 ProcVersionSignature: Ubuntu 2.6.32-24.39-server 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-server x86_64 Architecture: amd64 Date: Tue Aug 10 16:39:24 2010 InstallationMedia: Ubuntu-Server 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) KvmCmdLine: UIDPID PPID CSZ RSS PSR STIME TTY TIME CMD root 17641 1 1 2174883 1087144 1 15:42 ? 00:00:59 /usr/bin/kvm -S -M pc-0.12 -cpu qemu32 -enable-kvm -m 8192 -smp 8 -name hound-lucid -uuid 0e32438c-cb4d-1eb9-a560-f25c89c1dbf6 -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/hound-lucid.monitor,server,nowait -monitor chardev:monitor -boot c -drive file=/opt/hound-lucid,if=virtio,index=0,boot=on -drive if=ide,media=cdrom,index=2 -net nic,macaddr=52:54:00:61:7e:c0,vlan=0,model=virtio,name=virtio.0 -net tap,fd=59,vlan=0,name=tap.0 -chardev pty,id=serial0 -serial chardev:serial0 -parallel none -usb -vnc 127.0.0.1:0 -k en-us -vga cirrus MachineType: IBM IBM System x3400 M2 Server -[7836AC1]- ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-server root=UUID=7d9adc6b-cfec-42fa-b469-bc09ccd24478 ro quiet ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qemu-kvm dmi.bios.date: 11/20/2009 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[Y4E131BUS-1.02]- dmi.board.name: 49Y6715 dmi.board.vendor: IBM dmi.board.version: GA dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: GA dmi.modalias: dmi:bvnIBMCorp.:bvr-[Y4E131BUS-1.02]-:bd11/20/2009:svnIBM:pnIBMSystemx3400M2Server-[7836AC1]-:pvr06:rvnIBM:rn49Y6715:rvrGA:cvnIBM:ct23:cvrGA: dmi.product.name: IBM System x3400 M2 Server -[7836AC1]- dmi.product.version: 06 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/616064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1723644] Re: NetworkManager/wicd hang, might be driver issue
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- 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/1723644 Title: NetworkManager/wicd hang, might be driver issue Status in linux package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Bug description: Recently I had issues with NetworkManager. When I try to restart or close NetworkManager, the process hangs. First it sends a SIGTERM to the NetworkManager process, and after a while it sends SIGKILL, yet nothing happens. After the attempt to restart/close NetworkManager, the OS behaves badly: - journalctl doesn't work, doesn't output anything, SIGTERMing/SIGABRTing/ SIGKILLing it causes the kill command to hang (no matter how many times I try it), it also hangs the terminal - 'sudo dmesg' hangs (killing it with SIGKILL/SIGTERM/SIGABRT hangs the kill command, can't close the terminal) - the OS won't reboot/suspend/shutdown (it does only after holding the restart button) Suspending/rebooting normally/shutdowning normally the laptop hangs the OS (because of NetworkManager). What I've tried: - reinstalling NetworkManager (uninstalling it using --purge, installing it clean) - deleting ~/.config - deleting ~/.cache - installing a version from NetworkManager from Debian (version: 1.8.4.2), reinstalling NetworkManager from Ubuntu back affects ubuntu affects ubuntu/network-manager affects ubuntu/systemd --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1259 F pulseaudio DistroRelease: Ubuntu 17.10 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-10-15 (1 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) IpRoute: default via 192.168.100.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.100.0/24 dev wlp3s0 proto kernel scope link src 192.168.100.6 metric 600 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:57f3 Realtek Semiconductor Corp. Bus 001 Device 002: ID 0489:e0a3 Foxconn / Hon Hai Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G Package: systemd PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=1df26300-dc4d-42b3-bf5f-0c77c8df7667 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/21/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.29 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.29 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.29:bd07/21/2017:svnAcer:pnAspireE5-575G:pvrV1.29:rvnAcer:rnIronman_SK:rvrV1.29:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.version: V1.29 dmi.sys.vendor: Acer nmcli-dev: DEVICETYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0wifi connected/org/freedesktop/NetworkManager/Devices/3 Bojescu 2278c0fb-6947-469e-a8fc-7bbbafb10cf2 /org/freedesktop/NetworkManager/ActiveConnection/1 enp4s0f1 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- loloopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Touch-packages] [Bug 460925] Re: Kernel log message corruption due to incomplete /proc separation
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- 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/460925 Title: Kernel log message corruption due to incomplete /proc separation Status in linux package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Bug description: Binary package hint: lxc When using LXC (linux containers), /proc/kmsg can be read in guest systems in their filtered view of /proc. This special file should never be present in guest systems, and if created within a guest system, it should be effectively using /dev/null as it's source. The effect of this bug ranges from simply annoying to potentially a security issue in that kernel messages are allowed to be destroyed and never fully logged on the host system, which could be used to cover evidence of some sort of attack on the system. I'm adding the kernel team as well, as this could be an issue inside the kernel. I'm not sure if /proc filtration happens there or in the context of the lxc userland utilities. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/460925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- 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/1762385 Title: dell_wmi: Unknown key codes Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Bogus keycode messages produced by the kernel / user annoyance * rfkill keyboard shortcuts not working as intended on some Dell machines [Test Case] * check that there are no spurious kernel messages about unknown keys in journalctl upon RFKill key presses * check that RFKill key presses work correctly and kill/restore RF capabilities [Regression Potential] * The change is scoped to particular SKUs and thus should only affect them * It is related to matching gsd support, which is in-place on xenial and up [Solution] Cherrypick upstream commit https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f [Original Bug report] RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86 /dell-wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1762385/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834192] Re: apparmor mult_mount regression test fails in eoan
** Also affects: qa-regression-testing Importance: Undecided Status: New -- 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/1834192 Title: apparmor mult_mount regression test fails in eoan Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in apparmor package in Ubuntu: Confirmed Bug description: In running adt testing on 5.2-based kernels for eoan, I'm seeing failures from the apparmor mult_mount regression test. Running the test case manually with -x yields: + dd if=/dev/zero of=/tmp/sdtest.2210-22387-i6UxxQ/image.ext3 bs=4096 count=20 + mkfs.ext2 -F -m 0 -N 10 /tmp/sdtest.2210-22387-i6UxxQ/image.ext3 ++ error_handler ++ fatalerror 'Unexpected shell error. Run with -x to debug' Running the following manually in a shell also fails in eoan with the 5.0 kernel copied forward from disco, while it passes in disco: $ uname -a Linux ee-apparmor 5.0.0-17-generic #18-Ubuntu SMP Tue Jun 4 15:34:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ dd if=/dev/zero of=test.img bs=4096 count=20 20+0 records in 20+0 records out 81920 bytes (82 kB, 80 KiB) copied, 0.000406443 s, 202 MB/s $ mkfs.ext2 -F -m 0 -N 10 test.img mke2fs 1.45.2 (27-May-2019) test.img: Not enough space to build proposed filesystem while setting up superblock So this seems likely to be due to some change with mke2fs; not sure if this is a regression there or if the test was getting away with doing something invalid. To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1834192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776381] Re: lxc-test-api-reboot will hang with autopkgtest
** Tags added: ubuntu-lxc ** Tags added: bionic -- 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/1776381 Title: lxc-test-api-reboot will hang with autopkgtest Status in ubuntu-kernel-tests: Confirmed Status in lxc package in Ubuntu: New Bug description: Steps: 1. Deploy Bionic on a bare-metal system. 2. Enable deb-src, install the autopkgtest package 3. sudo autopkgtest lxc -- null Result: * The test will hang, a "reboot" lxc container will be created. The last message on the screen will be: make[1]: Entering directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' make[1]: Nothing to be done for 'all-am'. make[1]: Leaving directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' * Tried to connect to the "reboot" container with "sudo lxc-console reboot", but nothing there: Connected to tty 1 Type to exit the console, to enter Ctrl+a itself * If you kill the job and run it again, this time the test will go on (fail with the lxc-test-api-reboot test, as the container has already been created) This issue can be reproduced on an amd64 box and a s390x zKVM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1776381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401474] Re: [Dell Inspiron 7737] The power indicator won't be available until the adapter connected / disconnected
Didn't see this issue with Bionic. Closing it. ** Changed in: indicator-power (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1401474 Title: [Dell Inspiron 7737] The power indicator won't be available until the adapter connected / disconnected Status in indicator-power package in Ubuntu: Fix Released Bug description: CID: 201306-13869 Dell Inspiron 7737 The power indicator on this system only appears after you connect or disconnect it from the adapter. After it appears, reboot it will make the indicator disappear again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Dec 11 05:06:39 2014 InstallationDate: Installed on 2014-12-11 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1401474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837937] Re: CRASH
Marked as Incomplete for request in comment #44, please feel free to switch it back to confirmed when you have it tested. Thanks. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1837937 Title: CRASH Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: The screen froze but the mouse was still moving then it all froze and said systemd-journal not able to write entry. I had to press the power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-9-generic 5.2.0-9.10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2068 F pulseaudio /dev/snd/controlC0: administrator 2068 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:11:47 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-9-generic N/A linux-backports-modules-5.2.0-9-generic N/A linux-firmware 1.181 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2852 F pulseaudio /dev/snd/controlC0: administrator 2852 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-05 (51 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 RelatedPackageVersions: linux-restricted-modules-5.2.0-9-generic N/A linux-backports-modules-5.2.0-9-generic N/A linux-firmware 1.181 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: eoan Uname: Linux 5.2.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2852 F pulseaudio /dev/snd/controlC0: administrator 2852 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-05 (51 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron:
[Touch-packages] [Bug 1834192] Re: apparmor mult_mount regression test fails in eoan
** Tags added: sru-20190722 ubuntu-qrt-apparmor ** Tags added: eoan -- 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/1834192 Title: apparmor mult_mount regression test fails in eoan Status in ubuntu-kernel-tests: New Status in apparmor package in Ubuntu: Confirmed Bug description: In running adt testing on 5.2-based kernels for eoan, I'm seeing failures from the apparmor mult_mount regression test. Running the test case manually with -x yields: + dd if=/dev/zero of=/tmp/sdtest.2210-22387-i6UxxQ/image.ext3 bs=4096 count=20 + mkfs.ext2 -F -m 0 -N 10 /tmp/sdtest.2210-22387-i6UxxQ/image.ext3 ++ error_handler ++ fatalerror 'Unexpected shell error. Run with -x to debug' Running the following manually in a shell also fails in eoan with the 5.0 kernel copied forward from disco, while it passes in disco: $ uname -a Linux ee-apparmor 5.0.0-17-generic #18-Ubuntu SMP Tue Jun 4 15:34:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ dd if=/dev/zero of=test.img bs=4096 count=20 20+0 records in 20+0 records out 81920 bytes (82 kB, 80 KiB) copied, 0.000406443 s, 202 MB/s $ mkfs.ext2 -F -m 0 -N 10 test.img mke2fs 1.45.2 (27-May-2019) test.img: Not enough space to build proposed filesystem while setting up superblock So this seems likely to be due to some change with mke2fs; not sure if this is a regression there or if the test was getting away with doing something invalid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1834192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834192] Re: apparmor mult_mount regression test fails in eoan
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- 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/1834192 Title: apparmor mult_mount regression test fails in eoan Status in ubuntu-kernel-tests: New Status in apparmor package in Ubuntu: Confirmed Bug description: In running adt testing on 5.2-based kernels for eoan, I'm seeing failures from the apparmor mult_mount regression test. Running the test case manually with -x yields: + dd if=/dev/zero of=/tmp/sdtest.2210-22387-i6UxxQ/image.ext3 bs=4096 count=20 + mkfs.ext2 -F -m 0 -N 10 /tmp/sdtest.2210-22387-i6UxxQ/image.ext3 ++ error_handler ++ fatalerror 'Unexpected shell error. Run with -x to debug' Running the following manually in a shell also fails in eoan with the 5.0 kernel copied forward from disco, while it passes in disco: $ uname -a Linux ee-apparmor 5.0.0-17-generic #18-Ubuntu SMP Tue Jun 4 15:34:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ dd if=/dev/zero of=test.img bs=4096 count=20 20+0 records in 20+0 records out 81920 bytes (82 kB, 80 KiB) copied, 0.000406443 s, 202 MB/s $ mkfs.ext2 -F -m 0 -N 10 test.img mke2fs 1.45.2 (27-May-2019) test.img: Not enough space to build proposed filesystem while setting up superblock So this seems likely to be due to some change with mke2fs; not sure if this is a regression there or if the test was getting away with doing something invalid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1834192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1783881 Title: ltp-syscalls: msgstress03 fails because systemd limits number of processes Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in systemd source package in Xenial: New Status in linux source package in Cosmic: Incomplete Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes
** Tags added: amd64 linux-kvm sru-20190603 ubuntu-ltp-syscalls -- 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/1783881 Title: ltp-syscalls: msgstress03 fails because systemd limits number of processes Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693540] Re: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
I will close this as 4.8 is not supported anymore. Please feel free to open a new bug report if you have encounter this again. ** Changed in: linux-hwe (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux-hwe (Ubuntu) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1693540 Title: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in debconf package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: Invalid Bug description: it show there's bug in my system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-53-generic (not installed) ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu May 25 08:42:40 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-04-03 (51 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: linux-hwe Title: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1693540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work
Mark this as verification done for Cosmic as per Sami's comment in #48 Thanks ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- 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/1818204 Title: Qualcomm Atheros QCA9377 wireless does not work Status in linux package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in network-manager source package in Bionic: Invalid Status in linux source package in Cosmic: Fix Committed Status in network-manager source package in Cosmic: Invalid Bug description: === SRU Justification === [Impact] Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked [Fix] The platform in question doesn't have hardware RF switch, so quirk it off. [Test] User confirm it fixes the issue. [Regression Potential] Minimal. This fix is limited to one specific platform. === Original Bug Report === I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31). The menu shows that wireless is off. Turning on the wireless from the menu does not do anything. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 1 11:42:34 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-02-20 (8 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100 130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 130.232.69.176 metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 ada277fe-966d-33ff-aba2-8ba32d6ce5a9 ethernet 155143 pe 1. maaliskuuta 2019 11.42.13 yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes enx00e04c704f68 activated /org/freedesktop/NetworkManager/ActiveConnection/11 -- virbr0 dc46fe89-5b22-438a-85d5-37be48a077ea bridge 155143 pe 1. maaliskuuta 2019 11.42.13 no 0 no/org/freedesktop/NetworkManager/Settings/2 yes virbr0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled disabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sami 1315 F pulseaudio /dev/snd/controlC0: sami 1315 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-02-20 (11 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100 130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 130.232.69.176 metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown MachineType: LENOVO 81H1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A
[Touch-packages] [Bug 33101] Re: update-initramfs -u fails during install when /boot contains vmlinux symlink to an old kernel.
** Changed in: linux-signed-hwe (Ubuntu) Status: New => Invalid ** Changed in: initramfs-tools Status: New => Invalid -- 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/33101 Title: update-initramfs -u fails during install when /boot contains vmlinux symlink to an old kernel. Status in initramfs-tools: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux-signed-hwe package in Ubuntu: Invalid Bug description: I tried a Flight-4 i386 install on my amd64 and selected an old /boot partition that had a 2.6.9-amd64 kernel on it from a previous install. The install failed because update-initramfs -u was being run as part of a post install script (for either initramfs-tools, initrd-tools, or udev I can't recall exactly). update-initramfs was erroring out with: "Kernel too old, requires at least 2.6.12". I fixed the problem by dropping into a console and removing the old kernel and the symlinks (vmlinux, initrd) that had been created to the old kernels, and then rerunning update-initramfs. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/33101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812095] Re: console login loop after entering username followed by RETURN
Possible dup with https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813683 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1812095 Title: console login loop after entering username followed by RETURN Status in shadow package in Ubuntu: Confirmed Bug description: login: password: Just do nothing. About two seconds later ... login: password: login: password: login: password: After this being displayed three times: "Too many failure" or so and login is restarting. You cant login at all. Only solution: clear the password for the account you want to login with. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 16 19:34:30 2019 InstallationDate: Installed on 2011-10-19 (2645 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: shadow UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813122] [NEW] "ubuntu-bug linux" command on PowerPC will ask for authentication
Public bug reported: On Bionic, when reporting bug with "ubuntu-bug linux" command in a terminal, you will be asked to enter password on a PowerPC: $ ubuntu-bug linux *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. tar: Removing leading `/' from member names AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: But with other arch like AMD64, you won't be asked for the authentication. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.5 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic ppc64le ApportVersion: 2.20.9-0ubuntu7.5 Architecture: ppc64el Date: Thu Jan 24 07:07:36 2019 PackageArchitecture: all ProcLoadAvg: 882.90 268.29 93.65 1281/2696 24907 ProcLocks: 1: POSIX ADVISORY WRITE 3876 00:17:569 0 EOF 2: FLOCK ADVISORY WRITE 3556 00:17:497 0 EOF 3: FLOCK ADVISORY WRITE 4090 00:17:596 0 EOF 4: POSIX ADVISORY WRITE 3955 00:17:571 0 EOF 5: POSIX ADVISORY WRITE 1823 00:17:348 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-43-generic (buildd@bos02-ppc64el-020) (gcc version 7.3.0 (User Name 7.3.0-16ubuntu3)) #46-User Name SMP Thu Dec 6 14:43:28 UTC 2018 SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 40 cpu_smt: SMT=4 ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic ppc64el uec-images -- 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/1813122 Title: "ubuntu-bug linux" command on PowerPC will ask for authentication Status in apport package in Ubuntu: New Bug description: On Bionic, when reporting bug with "ubuntu-bug linux" command in a terminal, you will be asked to enter password on a PowerPC: $ ubuntu-bug linux *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. tar: Removing leading `/' from member names AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: But with other arch like AMD64, you won't be asked for the authentication. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.5 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic ppc64le ApportVersion: 2.20.9-0ubuntu7.5 Architecture: ppc64el Date: Thu Jan 24 07:07:36 2019 PackageArchitecture: all ProcLoadAvg: 882.90 268.29 93.65 1281/2696 24907 ProcLocks: 1: POSIX ADVISORY WRITE 3876 00:17:569 0 EOF 2: FLOCK ADVISORY WRITE 3556 00:17:497 0 EOF 3: FLOCK ADVISORY WRITE 4090 00:17:596 0 EOF 4: POSIX ADVISORY WRITE 3955 00:17:571 0 EOF 5: POSIX ADVISORY WRITE 1823 00:17:348 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-43-generic (buildd@bos02-ppc64el-020) (gcc version 7.3.0 (User Name 7.3.0-16ubuntu3)) #46-User Name SMP Thu Dec 6 14:43:28 UTC 2018 SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 40 cpu_smt: SMT=4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1813122/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765331] Re: ar in ubuntu_ltp test failed with 4.15 KVM
Passed with Bionic kernel 4.15.0-44.47: ar01 14 TPASS: ar updated modified file0 (-u) ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** No longer affects: binutils ** No longer affects: binutils (Ubuntu) ** No longer affects: linux-kvm (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1765331 Title: ar in ubuntu_ltp test failed with 4.15 KVM Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: ar tests in ubuntu_ltp has failed with 4.15.0-1004.4 kvm kernel <<>> tag=ar stime=1523972462 cmdline="export TCdat=$LTPROOT/testcases/bin; ar01" contacts="" analysis=exit <<>> ar01 1 TPASS: ar added new file after another (-a) ar01 2 TPASS: ar moved file correctly (-ma) ar01 3 TPASS: ar added new file before another (-b) ar01 4 TPASS: ar moved file correctly (-mb) ar01 5 TPASS: ar haven't produced output (-c) ar01 6 TPASS: ar haven't produced output (-qc) ar01 7 TPASS: ar deleted files correctly (-d) ar01 8 TPASS: ar deleted nothing (-d with empty list) ar01 9 TPASS: ar added new file before another (-i) ar01 10 TPASS: ar moved file correctly (-mi) ar01 11 TPASS: ar moved file correctly (-m) ar01 12 TPASS: ar printed file content correctly (-p) ar01 13 TPASS: ar appended file correctly (-q) ar: `u' modifier ignored since `D' is the default (see `U') ar01 14 TFAIL: ar haven't updated modified file0 (-u) ar01 14 TPASS: ar haven't updated unmodified file1 (-u) ar01 15 TPASS: ar verbose listing works (-tv) ar01 16 TPASS: ar printed extracted filenames (-xv) ar01 16 TPASS: ar extracted files correctly ar01 17 TPASS: ar printed extracted filename (-xv) ar01 17 TPASS: ar extracted file correctly Summary: passed 19 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=9 cstime=4 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1004-kvm 4.15.0-1004.4 ProcVersionSignature: User Name 4.15.0-1004.4-kvm 4.15.15 Uname: Linux 4.15.0-1004-kvm x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 08:24:19 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1765331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805978] Re: ubuntu_lxc test is failed with lxc-utils package not installed
Didn't see this issue this cycle for the Bionic OEM kernel testing. Probably it's because all these packages have been released. Closing this bug. ** Changed in: ubuntu-kernel-tests Status: Confirmed => Fix Released -- 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/1805978 Title: ubuntu_lxc test is failed with lxc-utils package not installed Status in ubuntu-kernel-tests: Fix Released Status in lxc package in Ubuntu: Invalid Bug description: On Bionic since Nov.29, the ubuntu_lxc test is failing with: Running 'apt-get install --yes automake autopkgtest build-essential cloud-image-utils dh-autoreconf lxc texinfo gcc-multilib liblxc1' [stdout] Reading package lists... [stdout] Building dependency tree... [stdout] Reading state information... [stdout] liblxc1 is already the newest version (3.0.3-0ubuntu1~18.04.1). [stdout] Some packages could not be installed. This may mean that you have [stdout] requested an impossible situation or if you are using the unstable [stdout] distribution that some required packages have not yet been created [stdout] or been moved out of Incoming. [stdout] The following information may help to resolve the situation: [stdout] [stdout] The following packages have unmet dependencies: [stdout] lxc : Depends: lxc-utils (>= 3.0.2-0ubuntu1~18.04.1) but it is not going to be installed [stderr] E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1805978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805978] Re: ubuntu_lxc test is failed with lxc-utils package not installed
So I think the solution is to get both of lxc-utils (universe) and liblxc1 (main) from -proposed, right? -- 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/1805978 Title: ubuntu_lxc test is failed with lxc-utils package not installed Status in ubuntu-kernel-tests: Confirmed Status in lxc package in Ubuntu: Invalid Bug description: On Bionic since Nov.29, the ubuntu_lxc test is failing with: Running 'apt-get install --yes automake autopkgtest build-essential cloud-image-utils dh-autoreconf lxc texinfo gcc-multilib liblxc1' [stdout] Reading package lists... [stdout] Building dependency tree... [stdout] Reading state information... [stdout] liblxc1 is already the newest version (3.0.3-0ubuntu1~18.04.1). [stdout] Some packages could not be installed. This may mean that you have [stdout] requested an impossible situation or if you are using the unstable [stdout] distribution that some required packages have not yet been created [stdout] or been moved out of Incoming. [stdout] The following information may help to resolve the situation: [stdout] [stdout] The following packages have unmet dependencies: [stdout] lxc : Depends: lxc-utils (>= 3.0.2-0ubuntu1~18.04.1) but it is not going to be installed [stderr] E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1805978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805978] Re: ubuntu_lxc test is failed with lxc-utils package not installed
** Tags added: bionic ** Tags added: package-from-proposed ** Changed in: ubuntu-kernel-tests Status: In Progress => Confirmed ** Changed in: ubuntu-kernel-tests Assignee: Po-Hsu Lin (cypressyew) => (unassigned) -- 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/1805978 Title: ubuntu_lxc test is failed with lxc-utils package not installed Status in ubuntu-kernel-tests: Confirmed Status in lxc package in Ubuntu: New Bug description: On Bionic since Nov.29, the ubuntu_lxc test is failing with: Running 'apt-get install --yes automake autopkgtest build-essential cloud-image-utils dh-autoreconf lxc texinfo gcc-multilib liblxc1' [stdout] Reading package lists... [stdout] Building dependency tree... [stdout] Reading state information... [stdout] liblxc1 is already the newest version (3.0.3-0ubuntu1~18.04.1). [stdout] Some packages could not be installed. This may mean that you have [stdout] requested an impossible situation or if you are using the unstable [stdout] distribution that some required packages have not yet been created [stdout] or been moved out of Incoming. [stdout] The following information may help to resolve the situation: [stdout] [stdout] The following packages have unmet dependencies: [stdout] lxc : Depends: lxc-utils (>= 3.0.2-0ubuntu1~18.04.1) but it is not going to be installed [stderr] E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1805978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805978] Re: ubuntu_lxc test is failed with lxc-utils package not installed
I can see this issue again, seems that there is another new update for it... Running 'apt-get install --yes automake autopkgtest build-essential cloud-image-utils dh-autoreconf lxc lxc-utils texinfo gcc-multilib liblxc1' Reading package lists... Building dependency tree... Reading state information... liblxc1 is already the newest version (3.0.3-0ubuntu1~18.04.1). Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: lxc-utils : Depends: liblxc1 (= 3.0.2-0ubuntu1~18.04.1) but 3.0.3-0ubuntu1~18.04.1 is to be installed Recommends: libpam-cgfs but it is not going to be installed E: Unable to correct problems, you have held broken packages. ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/1805978 Title: ubuntu_lxc test is failed with lxc-utils package not installed Status in ubuntu-kernel-tests: In Progress Status in lxc package in Ubuntu: New Bug description: On Bionic since Nov.29, the ubuntu_lxc test is failing with: Running 'apt-get install --yes automake autopkgtest build-essential cloud-image-utils dh-autoreconf lxc texinfo gcc-multilib liblxc1' [stdout] Reading package lists... [stdout] Building dependency tree... [stdout] Reading state information... [stdout] liblxc1 is already the newest version (3.0.3-0ubuntu1~18.04.1). [stdout] Some packages could not be installed. This may mean that you have [stdout] requested an impossible situation or if you are using the unstable [stdout] distribution that some required packages have not yet been created [stdout] or been moved out of Incoming. [stdout] The following information may help to resolve the situation: [stdout] [stdout] The following packages have unmet dependencies: [stdout] lxc : Depends: lxc-utils (>= 3.0.2-0ubuntu1~18.04.1) but it is not going to be installed [stderr] E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1805978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776381] Re: lxc-test-api-reboot will hang with autopkgtest
** Changed in: ubuntu-kernel-tests Status: New => Confirmed -- 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/1776381 Title: lxc-test-api-reboot will hang with autopkgtest Status in ubuntu-kernel-tests: Confirmed Status in lxc package in Ubuntu: New Bug description: Steps: 1. Deploy Bionic on a bare-metal system. 2. Enable deb-src, install the autopkgtest package 3. sudo autopkgtest lxc -- null Result: * The test will hang, a "reboot" lxc container will be created. The last message on the screen will be: make[1]: Entering directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' make[1]: Nothing to be done for 'all-am'. make[1]: Leaving directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' * Tried to connect to the "reboot" container with "sudo lxc-console reboot", but nothing there: Connected to tty 1 Type to exit the console, to enter Ctrl+a itself * If you kill the job and run it again, this time the test will go on (fail with the lxc-test-api-reboot test, as the container has already been created) This issue can be reproduced on an amd64 box and a s390x zKVM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1776381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
