[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
Note, Bionic and Focal will likely require more than just that patch. There were multiple patches for Python 3 support landed in apparmor 3. I am not sure what the exact combination required will be. -- 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 # 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 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 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/262/+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 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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Hi, There are a few OEM platforms that also requires these memory patches in grub2 on jammy, could we also port 2.06-2ubuntu16 back to jammy? ** Tags added: originate-from-1998995 -- 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/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Fix Committed Status in grub2-unsigned package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: [Workaround] Some workarounds have been suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125 [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory region starvation in <1G addresses: Type StartEnd # Pages Attributes Available -00086FFF 0087 000F BS_Data00087000-00087FFF 0001 000F Available 00088000-0009EFFF 0017 000F Reserved 0009F000-0009 0001 000F Available 0010-00FF 0F00 000F LoaderCode 0100-01021FFF 0022 000F Available 01022000-238A7FFF 00022886 000F BS_Data238A8000-23927FFF 0080 000F Available 23928000-28860FFF 4F39 000F BS_Data28861000-2AB09FFF 22A9 000F LoaderCode 2AB0A000-2ACF8FFF 01EF 000F BS_Data2ACF9000-2B2FAFFF 0602 000F Available 2B2FB000-2B611FFF 0317 000F BS_Data2B612000-2B630FFF 001F 000F Available 2B631000-2B632FFF 0002 000F BS_Data2B633000-2B63CFFF 000A 000F Available 2B63D000-2B649FFF 000D 000F BS_Data2B64A000-2B64EFFF 0005 000F Available 2B64F000-2B666FFF 0018 000F BS_Data2B667000-2D8D5FFF 226F 000F LoaderCode 2D8D6000-2D8E9FFF 0014 000F BS_Data2D8EA000-2D925FFF 003C 000F LoaderCode 2D926000-2D932FFF 000D 000F BS_Data2D933000-2D969FFF 0037 000F BS_Code2D96A000-2D973FFF 000A 000F BS_Data2D974000-2E377FFF 0A04 000F Available 2E378000-2E37AFFF 0003 000F ... Reserved 3C08B000-4192 58A5 000F ACPI_NVS 4193-41B2 0200 000F ACPI_Recl 41B3-41BFEFFF 00CF 000F BS_Data41BFF000-41BF 0001 000F Available 0001-0002AB7F 001AB800 000F Reserved 000A-000F 0060 Reserved
[Touch-packages] [Bug 1946804] Re: ufw breaks boot on network root filesystem
Hello folks, sorry for digging the old thread. I'd like to ask whether you have tested the bug on Ubuntu VM? VMware specifically. Cheers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1946804 Title: ufw breaks boot on network root filesystem Status in ufw: Fix Committed Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Released Status in ufw source package in Focal: Fix Released Status in ufw source package in Hirsute: Fix Released Status in ufw source package in Impish: Fix Released Bug description: [Impact] A system with rootfs on iSCSI stops booting when ufw.service starts. The kernel logs iSCSI command/reset timeout until I/O fails and the root filesystem/journal break. The issue is that ufw_start() sets the default policy _first_, then adds rules _later_. So, a default INPUT policy of DROP (default setting in ufw) prevents further access to the root filesystem (blocks incoming iSCSI traffic) thus any rules that could help are not loaded (nor anything else.) [Fix] The fix is to set default policy after loading rules in ufw_start(). That seems to be OK as `ip[6]tables-restore -n/--noflush` is used, and per iptables source, that only sets the chain policy. This allows the system to boot due to the RELATED,ESTABLISHED rule, that is introduced by before.rules in INPUT/ufw-before-input chain. The comparison of `iptables -L` before/after shows no differences (verified on a local rootfs); `run_tests.sh` has 0 skipped/errors. [Test Steps] * Install Ubuntu on an iSCSI (or other network-based) root filesystem. (eg, Oracle Cloud's bare-metal 'BM.Standard1.36' shape.) * sudo ufw enable * Observed: system may stall immediately if no prior iptables rules. (eg, iptables -A INPUT -p tcp -s 169.254.0.2 --sport 3260 -j ACCEPT) * Expected: system continues working. * sudo reboot * Observed: system boot stalls once ufw.service starts (see below.) * Expected: system boot should move on. [Regression Potential] * Potential regressions would be observed on ufw start/reload, when iptables rules are configured. * The resulting iptables configuration has been compared before/after the change, with identical rules on both. [Other Info] * Fixed in Debian and Jammy. [ufw info] # ufw --version ufw 0.36 Copyright 2008-2015 Canonical Ltd. # lsb_release -cs focal [Boot Log] [ 232.168355] iBFT detected. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Setting up software interface enp45s0f0np0 ... [ 254.644505] Loading iSCSI transport class v2.0-870. [ 254.714938] iscsi: registered transport (tcp) [ 254.780129] scsi host12: iSCSI Initiator over TCP/IP ... [ 255.433491] sd 12:0:0:1: [sda] 251658240 512-byte logical blocks: (129 GB/120 GiB) ... [ 256.379550] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) ... [ 266.620860] systemd[1]: Starting Uncomplicated firewall... Starting Uncomplicated firewall... ... [ 298.491560] session1: iscsi_eh_cmd_timed_out scsi cmd 310a6696 timedout [ 298.580803] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 298.656262] session1: iscsi_eh_cmd_timed_out scsi cmd 94ad9246 timedout [ 298.745237] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 298.745270] session1: iscsi_eh_abort aborting sc 310a6696 [ 298.899644] session1: iscsi_eh_abort aborting [sc 310a6696 itt 0x13] [ 298.985788] session1: iscsi_exec_task_mgmt_fn tmf set timeout [ 302.075554] session1: iscsi_eh_cmd_timed_out scsi cmd 1a9458b5 timedout [ 302.164786] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 314.107541] session1: iscsi_tmf_timedout tmf timedout [ 314.169797] connection1:0: detected conn error (1021) [ 314.232266] session1: iscsi_eh_abort abort failed [sc 310a6696 itt 0x13] [ 314.323531] session1: iscsi_eh_abort aborting sc 94ad9246 [ 314.399640] session1: iscsi_eh_abort sc never reached iscsi layer or it completed. [ 314.495578] session1: iscsi_eh_abort aborting sc 1a9458b5 [ 314.571554] session1: iscsi_eh_abort sc never reached iscsi layer or it completed. [ 314.664050] session1: iscsi_eh_device_reset LU Reset [sc 310a6696 lun 1] [ 314.755773] session1: iscsi_eh_device_reset dev reset result = FAILED [ 314.834736] session1: iscsi_eh_target_reset tgt Reset [sc 310a6696 tgt <...>] [ 314.954144] session1: iscsi_eh_target_reset tgt <...> reset result = FAILED [ 315.063456] connection1:0: detected conn error (1021) [ 315.125743] session1: iscsi_eh_session_reset wait for relogin [ 398.843556] INFO: task systemd:1 blocked for more than 120 seconds.
[Touch-packages] [Bug 2000117] Re: package cups-common 2.3.1-9ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2000117 Title: package cups-common 2.3.1-9ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in cups package in Ubuntu: New Bug description: upgradation is not successful ProblemType: Package DistroRelease: Ubuntu 20.04 Package: cups-common 2.3.1-9ubuntu1.2 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 AptOrdering: ca-certificates:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: W [20/Dec/2022:09:22:47 +0530] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Brother_DCP_L2540DW_series-Gray..\' already exists W [20/Dec/2022:09:22:47 +0530] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Brother_DCP_L2540DW_series-DeviceN..\' already exists Date: Tue Dec 20 06:53:22 2022 Dependencies: DuplicateSignature: package:cups-common:2.3.1-9ubuntu1.2 Unpacking ca-certificates (20211016ubuntu0.20.04.1) over (20211016~20.04.1) ... dpkg: error processing package cups-common (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2022-09-21 (89 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for Brother_DCP_L2540DW_series: implicitclass://Brother_DCP_L2540DW_series/ device for DCP-L2520D-series: usb://Brother/DCP-L2520D%20series?serial=E73800M7N852807 MachineType: Tyrone Systems SS400TR PackageArchitecture: all Papersize: a4 PpdFiles: Brother_DCP_L2540DW_series: Brother DCP-L2540DW series, driverless, cups-filters 1.27.4 DCP-L2520D-series: Brother DCP-L2520D series, using brlaser v6 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=1affea12-c52b-4cfc-806d-e1c58530a677 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=1affea12-c52b-4cfc-806d-e1c58530a677 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: cups Title: package cups-common 2.3.1-9ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2020 dmi.bios.release: 5.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: SS400TR-54 dmi.board.vendor: Tyrone Systems dmi.board.version: 1.02 dmi.chassis.asset.tag: SOB300121130A dmi.chassis.type: 17 dmi.chassis.vendor: Tyrone Systems dmi.chassis.version: TY-SS4T dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd02/10/2020:br5.15:svnTyroneSystems:pnSS400TR:pvrIntelChipsetC422:rvnTyroneSystems:rnSS400TR-54:rvr1.02:cvnTyroneSystems:ct17:cvrTY-SS4T:skuDefaultstring: dmi.product.family: Default string dmi.product.name: SS400TR dmi.product.sku: Default string dmi.product.version: Intel Chipset C422 dmi.sys.vendor: Tyrone Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2000117/+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 1958019]
AMD based Gen 7 has the same problem. Here's the alsainfo: http://alsa-project.org/db/?f=fa86a2cb02044c07dee609a6decc51aaa1d02cea -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 2000117] [NEW] package cups-common 2.3.1-9ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati
Public bug reported: upgradation is not successful ProblemType: Package DistroRelease: Ubuntu 20.04 Package: cups-common 2.3.1-9ubuntu1.2 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 AptOrdering: ca-certificates:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: W [20/Dec/2022:09:22:47 +0530] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Brother_DCP_L2540DW_series-Gray..\' already exists W [20/Dec/2022:09:22:47 +0530] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Brother_DCP_L2540DW_series-DeviceN..\' already exists Date: Tue Dec 20 06:53:22 2022 Dependencies: DuplicateSignature: package:cups-common:2.3.1-9ubuntu1.2 Unpacking ca-certificates (20211016ubuntu0.20.04.1) over (20211016~20.04.1) ... dpkg: error processing package cups-common (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2022-09-21 (89 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for Brother_DCP_L2540DW_series: implicitclass://Brother_DCP_L2540DW_series/ device for DCP-L2520D-series: usb://Brother/DCP-L2520D%20series?serial=E73800M7N852807 MachineType: Tyrone Systems SS400TR PackageArchitecture: all Papersize: a4 PpdFiles: Brother_DCP_L2540DW_series: Brother DCP-L2540DW series, driverless, cups-filters 1.27.4 DCP-L2520D-series: Brother DCP-L2520D series, using brlaser v6 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=1affea12-c52b-4cfc-806d-e1c58530a677 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=1affea12-c52b-4cfc-806d-e1c58530a677 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: cups Title: package cups-common 2.3.1-9ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2020 dmi.bios.release: 5.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: SS400TR-54 dmi.board.vendor: Tyrone Systems dmi.board.version: 1.02 dmi.chassis.asset.tag: SOB300121130A dmi.chassis.type: 17 dmi.chassis.vendor: Tyrone Systems dmi.chassis.version: TY-SS4T dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd02/10/2020:br5.15:svnTyroneSystems:pnSS400TR:pvrIntelChipsetC422:rvnTyroneSystems:rnSS400TR-54:rvr1.02:cvnTyroneSystems:ct17:cvrTY-SS4T:skuDefaultstring: dmi.product.family: Default string dmi.product.name: SS400TR dmi.product.sku: Default string dmi.product.version: Intel Chipset C422 dmi.sys.vendor: Tyrone Systems ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2000117 Title: package cups-common 2.3.1-9ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in cups package in Ubuntu: New Bug description: upgradation is not successful ProblemType: Package DistroRelease: Ubuntu 20.04 Package: cups-common 2.3.1-9ubuntu1.2 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 AptOrdering: ca-certificates:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: W [20/Dec/2022:09:22:47 +0530] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Brother_DCP_L2540DW_series-Gray..\' already exists W [20/Dec/2022:09:22:47 +0530] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Brother_DCP_L2540DW_series-DeviceN..\' already exists Date: Tue Dec 20 06:53:22 2022 Dependencies: DuplicateSignature: package:cups-common:2.3.1-9ubuntu1.2 Unpacking ca-certificates (20211016ubuntu0.20.04.1) over (20211016~20.04.1) ... dpkg: error processing package cups-common (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2022-09-21 (89 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat:
[Touch-packages] [Bug 2000108] Re: Apple Airpods Max do not connect via bluetooth consistently.
** Package changed: ubuntu => bluez (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2000108 Title: Apple Airpods Max do not connect via bluetooth consistently. Status in bluez package in Ubuntu: New Bug description: After fresh install of 22.10 Apple Airpods Max connected and worked with sound out as well as microphone. Unfortunately this was the only time. All subsequent attempts to connect bluetooth did not work. Verified it with another pair of identical headphones - same problem. To make it clear it's bluetooth that is not connecting. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Dec 19 19:02:29 2022 InstallationDate: Installed on 2022-12-18 (1 days ago) InstallationMedia: Ubuntu-Server 22.10 "Kinetic Kudu" - Release amd64 (20221019) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=49aee598-51b7-4802-90eb-18f4a1d54733 ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2021 dmi.bios.release: 6.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0602 dmi.board.asset.tag: Default string dmi.board.name: Pro WS WRX80E-SAGE SE WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0602:bd07/13/2021:br6.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSWRX80E-SAGESEWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS hciconfig: hci0:Type: Primary Bus: USB BD Address: 70:9C:D1:3F:4B:06 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:525390 acl:24441 sco:0 events:2792 errors:0 TX bytes:22066 acl:98 sco:0 commands:1140 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2000108/+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 2000108] [NEW] Apple Airpods Max do not connect via bluetooth consistently.
You have been subscribed to a public bug: After fresh install of 22.10 Apple Airpods Max connected and worked with sound out as well as microphone. Unfortunately this was the only time. All subsequent attempts to connect bluetooth did not work. Verified it with another pair of identical headphones - same problem. To make it clear it's bluetooth that is not connecting. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Dec 19 19:02:29 2022 InstallationDate: Installed on 2022-12-18 (1 days ago) InstallationMedia: Ubuntu-Server 22.10 "Kinetic Kudu" - Release amd64 (20221019) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=49aee598-51b7-4802-90eb-18f4a1d54733 ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2021 dmi.bios.release: 6.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0602 dmi.board.asset.tag: Default string dmi.board.name: Pro WS WRX80E-SAGE SE WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0602:bd07/13/2021:br6.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSWRX80E-SAGESEWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS hciconfig: hci0: Type: Primary Bus: USB BD Address: 70:9C:D1:3F:4B:06 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:525390 acl:24441 sco:0 events:2792 errors:0 TX bytes:22066 acl:98 sco:0 commands:1140 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic uec-images -- Apple Airpods Max do not connect via bluetooth consistently. https://bugs.launchpad.net/bugs/2000108 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. -- 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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
request regression test on ~device-certification channel. https://chat.canonical.com/canonical/pl/mbrptg5713fbxqmwk8ooc97dmh -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Jammy: Fix Committed Status in libqmi source package in Jammy: Fix Committed Status in linux source package in Jammy: New Status in modemmanager source package in Jammy: Fix Committed Bug description: * Impact Fibocom FM350 modems aren't working with the current version of modemmanager in 22.04. * Test case - install modemmanager, libmbim, and libqmi from -proposed - reboot and try WWAN function to see if any regression there. - perform dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) The verification should be done on FM350 to ensure it's correctly handled but also on other hardware to verify that there are no regressions * Regression potential The SRU does an update to new modemmanager serie so we should do a complete round of testing on different hardware and confirm there are no regression. --- :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux- wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ Modemmanager requires >= 1.19.1, the detail info is in lp:1962525 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+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 2000098] [NEW] I am not sure if i am right
Public bug reported: I am not sure what i have done but the driver seems wrong. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.60.11 Wed Nov 23 23:04:03 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 20 00:56:43 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: nvidia/525.60.11, 5.19.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU116 [GeForce GTX 1660 SUPER] [1462:8d94] InstallationDate: Installed on 2022-12-17 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Gigabyte Technology Co., Ltd. B250M-Gaming 3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=847b2ef5-caec-47e0-a734-a25d0e008f1a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: Default string dmi.board.name: B250M-Gaming 3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/10/2018:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnB250M-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB250M-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B250M-Gaming 3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/298 Title: I am not sure if i am right Status in xorg package in Ubuntu: New Bug description: I am not sure what i have done but the driver seems wrong. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.60.11 Wed Nov 23 23:04:03 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 20 00:56:43 2022 DistUpgraded: Fresh install DistroCodename: kinetic
[Touch-packages] [Bug 1971066] Re: package sudo 1.9.9-1ubuntu2 failed to install/upgrade: installed sudo package pre-removal script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sudo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1971066 Title: package sudo 1.9.9-1ubuntu2 failed to install/upgrade: installed sudo package pre-removal script subprocess returned error exit status 1 Status in sudo package in Ubuntu: Confirmed Bug description: Autogenerated by install script. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: sudo 1.9.9-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Apr 30 22:25:46 2022 ErrorMessage: installed sudo package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2022-05-01 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: sudo Title: package sudo 1.9.9-1ubuntu2 failed to install/upgrade: installed sudo package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1971066/+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 1999993] Re: The following packages have been kept back (ubuntu-wallpapers)
Never an 'xorg' bug but probably https://wiki.ubuntu.com/StableReleaseUpdates#Phasing so that updates are 'rolled out' to users gradually. If you want to receive updates as they are released then please read https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345 for how to configure your system to do this. ** Package changed: xorg (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/193 Title: The following packages have been kept back (ubuntu-wallpapers) Status in Ubuntu: Fix Released Bug description: Ubuntu version: 22.10 Version of the packages: ubuntu-wallpapers: Installed: 22.10.2-0ubuntu1. Candidate: 22.10.2ubuntu1-0ubuntu1 ubuntu-wallpapers-kinetic: Installed: 22.10.2-0ubuntu1. Candidate: 22.10.2ubuntu1-0ubuntu1 What is expected to happen: upgrade packages via apt-get upgrade. What happened instead: packages not upgrading, with a message saying "the following packages have been kept back: ubuntu-wallpapers ubuntu- wallpapers-kinetic. apt-get install ubuntu-wallpapers ubuntu- wallpapers-kinetic or other workarounds don't work as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/193/+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 1078294] Re: please kick out that annoying locale warning
** Changed in: perl (Debian)
Status: Won't Fix => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1078294
Title:
please kick out that annoying locale warning
Status in perl package in Ubuntu:
Confirmed
Status in perl package in Debian:
Fix Released
Bug description:
Whenever perl gets invoked, e.g. when dpkg runs, perl prints this
annoying multi-line warning, if some of the selected locales aren't
available:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_PAPER = "de_DE.UTF-8",
LC_ADDRESS = "de_DE.UTF-8",
LC_MONETARY = "de_DE.UTF-8",
LC_NUMERIC = "de_DE.UTF-8",
LC_TELEPHONE = "de_DE.UTF-8",
LC_IDENTIFICATION = "de_DE.UTF-8",
LC_MEASUREMENT = "de_DE.UTF-8",
LC_TIME = "de_DE.UTF-8",
LC_NAME = "de_DE.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
I'm unable to see why only perl has to display such a warning, but all
programs written in another language just handle this fallback
silently.
It's not a big deal on a desktop system, where you usually just
install the missing locale - or where you already have it installed,
because otherwise your environment wouldn't be set like this.
But if you ssh to remote machines, then your language settings
automatically get forwarded. On those remote machines it might be
impossible to install the missing locales due to restricted user
permissions or due to limited space on embedded systems.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1078294/+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 1999207] Re: Error in dead key management of latin keyboards
Ok, I can confirm that it works... It seems weird to me that it works, but it just works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1999207 Title: Error in dead key management of latin keyboards Status in ibus package in Ubuntu: Incomplete Bug description: Composition events are incorrect in Ubuntu 22.04 for latin keyboard I opened an issue at Firefox [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1802989) that gives all the details, but they diagnosed a bug in ubuntu-ibus To reproduce the issue, you can go [here](https://developer.mozilla.org/en- US/docs/Web/API/Element/compositionstart_event#result) and type ^+u with a fr+latin9 keayboard configuration. Here is the conclusion on the bug report: Ubuntu-ibus commits dead key sequence with empty string first, then, sends only commit string without "composing" state. The latter behavior is a usual case for inputting non-ASCII characters like Emojis. In this case, browsers need to handle it without composition for compatibility between browsers. Therefore, we cannot represent the composed character insertion as a set of composition events. Anyway, dispatching 2 set of composition events for one dead key sequence may cause trouble in web apps. Therefore, as expected, the first composition should update the "preedit string" to the composed string and commit it simply. The bug was reproduced with installing Ubuntu 22.04 with English locale and adding "French (alt., Latin-9 only)" keyboard layout. And also reproduced with the other Western keyboard layouts which have dead keys. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1999207/+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 2000001] Re: Wifi 5/6 dropped randomly if ipv6 is enabled - Bug dhcp6!!!
** Attachment removed: "nmcli-con.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/201/+attachment/5636256/+files/nmcli-con.txt ** Attachment removed: "IpAddr.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/201/+attachment/5636246/+files/IpAddr.txt ** Attachment removed: "NetDevice.enp2s0.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/201/+attachment/5636248/+files/NetDevice.enp2s0.txt ** Attachment removed: "NetDevice.wlp3s0b1.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/201/+attachment/5636250/+files/NetDevice.wlp3s0b1.txt -- 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/201 Title: Wifi 5/6 dropped randomly if ipv6 is enabled - Bug dhcp6!!! Status in dhcp package in Ubuntu: New Status in dhcpcd package in Ubuntu: New Status in dhcpcd5 package in Ubuntu: New Status in isc-dhcp package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in network-manager-applet package in Ubuntu: New Status in wicd package in Ubuntu: New Bug description: Updated: 19.12.2022 # Hi Support at startup of analysis: Wifi5/6 dropped randomly if ipv6 is enabled/disabled on gnome-network-manager-gui no Error on Logs! No red Kernel Messages. My Lab: At my Lab i disabled all ipv6 on my Subnet LAN Openwrt-Routers, and my Laptop loses "randomly" 20times a day the Internet but the Signal is 100% to the WIFI-Routers, no ping, no nslookup to first DSL-WAN Router possible. First Handling: After i manual enable/disable WIFI by switch is works again fast. Analysis: After some search on Net i disabled ipv6 in sysctl.conf ! GTK-Apps Affected: seen on network-manager/network-manager-gnome/wicd Managers Hardware Change/Test: I tested / changed 3 different old wifi-5+ new wifi-6 intel AX 7260 HMW mini-pci-cards same problem! Now testing again.. Thanks Linuxonlinehelp_eu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.4 ProcVersionSignature: Ubuntu 5.4.0-135.152~18.04.2-generic 5.4.212 Uname: Linux 5.4.0-135-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 18 11:24:20 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2021-08-19 (486 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: default via 192.168.71.1 dev wlp3s0b1 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0b1 scope link metric 1000 192.168.71.0/24 dev wlp3s0b1 proto kernel scope link src 192.168.71.123 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: http_proxy: http://127.0.0.1:8118/ modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2022-06-30T19:17:37.737049 nmcli-dev: DEVICETYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0b1 wifi connected/org/freedesktop/NetworkManager/Devices/3 AXWIFI71bec4545b-24e6-40ef-a933-43121b9b819b /org/freedesktop/NetworkManager/ActiveConnection/3 enp2s0ethernet 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.10.6 connected started full enabled enabled enabled enabled enabled no_proxy: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dhcp/+bug/201/+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 2000001] Re: Wifi 5/6 dropped randomly if ipv6 is enabled - Bug dhcp6!!!
** Also affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- 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/201 Title: Wifi 5/6 dropped randomly if ipv6 is enabled - Bug dhcp6!!! Status in dhcp package in Ubuntu: New Status in dhcpcd package in Ubuntu: New Status in dhcpcd5 package in Ubuntu: New Status in isc-dhcp package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in network-manager-applet package in Ubuntu: New Status in wicd package in Ubuntu: New Bug description: Updated: 19.12.2022 # Hi Support at startup of analysis: Wifi5/6 dropped randomly if ipv6 is enabled/disabled on gnome-network-manager-gui no Error on Logs! No red Kernel Messages. My Lab: At my Lab i disabled all ipv6 on my Subnet LAN Openwrt-Routers, and my Laptop loses "randomly" 20times a day the Internet but the Signal is 100% to the WIFI-Routers, no ping, no nslookup to first DSL-WAN Router possible. First Handling: After i manual enable/disable WIFI by switch is works again fast. Analysis: After some search on Net i disabled ipv6 in sysctl.conf ! GTK-Apps Affected: seen on network-manager/network-manager-gnome/wicd Managers Hardware Change/Test: I tested / changed 3 different old wifi-5+ new wifi-6 intel AX 7260 HMW mini-pci-cards same problem! Now testing again.. Thanks Linuxonlinehelp_eu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.4 ProcVersionSignature: Ubuntu 5.4.0-135.152~18.04.2-generic 5.4.212 Uname: Linux 5.4.0-135-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 18 11:24:20 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2021-08-19 (486 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: default via 192.168.71.1 dev wlp3s0b1 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0b1 scope link metric 1000 192.168.71.0/24 dev wlp3s0b1 proto kernel scope link src 192.168.71.123 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: http_proxy: http://127.0.0.1:8118/ modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2022-06-30T19:17:37.737049 nmcli-dev: DEVICETYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0b1 wifi connected/org/freedesktop/NetworkManager/Devices/3 AXWIFI71bec4545b-24e6-40ef-a933-43121b9b819b /org/freedesktop/NetworkManager/ActiveConnection/3 enp2s0ethernet 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.10.6 connected started full enabled enabled enabled enabled enabled no_proxy: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dhcp/+bug/201/+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 2000001] Re: Wifi 5/6 dropped randomly if ipv6 is enabled - Bug dhcp6!!!
** Information type changed from Private to Public -- 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/201 Title: Wifi 5/6 dropped randomly if ipv6 is enabled - Bug dhcp6!!! Status in dhcp package in Ubuntu: New Status in dhcpcd package in Ubuntu: New Status in dhcpcd5 package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in network-manager-applet package in Ubuntu: New Status in wicd package in Ubuntu: New Bug description: Updated: 19.12.2022 # Hi Support at startup of analysis: Wifi5/6 dropped randomly if ipv6 is enabled/disabled on gnome-network-manager-gui no Error on Logs! No red Kernel Messages. My Lab: At my Lab i disabled all ipv6 on my Subnet LAN Openwrt-Routers, and my Laptop loses "randomly" 20times a day the Internet but the Signal is 100% to the WIFI-Routers, no ping, no nslookup to first DSL-WAN Router possible. First Handling: After i manual enable/disable WIFI by switch is works again fast. Analysis: After some search on Net i disabled ipv6 in sysctl.conf ! GTK-Apps Affected: seen on network-manager/network-manager-gnome/wicd Managers Hardware Change/Test: I tested / changed 3 different old wifi-5+ new wifi-6 intel AX 7260 HMW mini-pci-cards same problem! Now testing again.. Thanks Linuxonlinehelp_eu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.4 ProcVersionSignature: Ubuntu 5.4.0-135.152~18.04.2-generic 5.4.212 Uname: Linux 5.4.0-135-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 18 11:24:20 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2021-08-19 (486 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: default via 192.168.71.1 dev wlp3s0b1 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0b1 scope link metric 1000 192.168.71.0/24 dev wlp3s0b1 proto kernel scope link src 192.168.71.123 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: http_proxy: http://127.0.0.1:8118/ modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2022-06-30T19:17:37.737049 nmcli-dev: DEVICETYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0b1 wifi connected/org/freedesktop/NetworkManager/Devices/3 AXWIFI71bec4545b-24e6-40ef-a933-43121b9b819b /org/freedesktop/NetworkManager/ActiveConnection/3 enp2s0ethernet 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.10.6 connected started full enabled enabled enabled enabled enabled no_proxy: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dhcp/+bug/201/+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
