[Touch-packages] [Bug 1840624] [NEW] Ubuntu 18.04: Can't remove software key via software-properties package GUI
Public bug reported: I have these packages installed: ii python3-software-properties0.96.24.32.11 all manage the repositories that you install software from ii software-properties-common 0.96.24.32.11 all manage the repositories that you install software from (common) ii software-properties-gtk0.96.24.32.11 all manage the repositories that you install software from (gtk) However, after calling out `Software & Updates` GUI and clicking the `Authenication` tab, I found the `Remove` button there does not work. It does not delete any trusted software keys. I had to resort to using cli cmds as given in https://askubuntu.com/questions/107177/how-can-i -remove-gpg-key-that-i-added-using-apt-key-add/846877#846877 to remove any trusted software keys. The 'Remove' button needs to work; it needs to be fixed. **System information:** $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 $ uname -a Linux Machine 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Can't remove software key via its GUI + Can't remove software key via software-properties package GUI ** Summary changed: - Can't remove software key via software-properties package GUI + Ubuntu 18.04: Can't remove software key via software-properties package GUI -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1840624 Title: Ubuntu 18.04: Can't remove software key via software-properties package GUI Status in software-properties package in Ubuntu: New Bug description: I have these packages installed: ii python3-software-properties0.96.24.32.11 all manage the repositories that you install software from ii software-properties-common 0.96.24.32.11 all manage the repositories that you install software from (common) ii software-properties-gtk0.96.24.32.11 all manage the repositories that you install software from (gtk) However, after calling out `Software & Updates` GUI and clicking the `Authenication` tab, I found the `Remove` button there does not work. It does not delete any trusted software keys. I had to resort to using cli cmds as given in https://askubuntu.com/questions/107177/how-can-i -remove-gpg-key-that-i-added-using-apt-key-add/846877#846877 to remove any trusted software keys. The 'Remove' button needs to work; it needs to be fixed. **System information:** $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 $ uname -a Linux Machine 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1840624/+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 1840626] [NEW] Description
Public bug reported: Since maybe two months, my computer deosn't work correctly. There is slowness and sometime the computer freeze. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Aug 19 00:42:31 2019 DistUpgraded: 2019-02-23 11:53:16,014 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0974] Subsystem: Acer Incorporated [ALI] GK208BM [GeForce 920M] [1025:0974] InstallationDate: Installed on 2019-02-21 (178 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Acer Aspire E5-772G ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=377aa352-9018-46e8-bfee-2799a1be51e6 ro persistent quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-02-23 (176 days ago) dmi.bios.date: 07/28/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire E5-772G dmi.board.vendor: Acer dmi.board.version: V1.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd07/28/2015:svnAcer:pnAspireE5-772G:pvrV1.09:rvnAcer:rnAspireE5-772G:rvrV1.09:cvnAcer:ct10:cvrV1.09: dmi.product.family: BDW dmi.product.name: Aspire E5-772G dmi.product.version: V1.09 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Aug 19 00:38:49 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1840626 Title: Description Status in xorg package in Ubuntu: New Bug description: Since maybe two months, my computer deosn't work correctly. There is slowness and sometime the computer freeze. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Aug 19 00:42:31 2019 DistUpgraded: 2019-02-23 11:53:16,014 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0974] Subsystem: Ace
[Touch-packages] [Bug 1840626] Re: Description
I wonder if the slowness is related to this from your Xorg log: [ 137.718] randr: falling back to unsynchronized pixmap sharing ** Tags added: nvidia ** Summary changed: - Description + Slowness and sometimes the computer freezes ** Summary changed: - Slowness and sometimes the computer freezes + [nvidia] Slowness and sometimes the computer freezes ** Tags added: hybrid ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- 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/1840626 Title: [nvidia] Slowness and sometimes the computer freezes Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Since maybe two months, my computer deosn't work correctly. There is slowness and sometime the computer freeze. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Aug 19 00:42:31 2019 DistUpgraded: 2019-02-23 11:53:16,014 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0974] Subsystem: Acer Incorporated [ALI] GK208BM [GeForce 920M] [1025:0974] InstallationDate: Installed on 2019-02-21 (178 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Acer Aspire E5-772G ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=377aa352-9018-46e8-bfee-2799a1be51e6 ro persistent quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-02-23 (176 days ago) dmi.bios.date: 07/28/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire E5-772G dmi.board.vendor: Acer dmi.board.version: V1.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd07/28/2015:svnAcer:pnAspireE5-772G:pvrV1.09:rvnAcer:rnAspireE5-772G:rvrV1.09:cvnAcer:ct10:cvrV1.09: dmi.product.family: BDW dmi.product.name: Aspire E5-772G dmi.product.version: V1.09 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Aug 19 00:38:49 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1840626/+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 1840633] [NEW] autopkgtests get stuck in Eoan with iptables 1.8.3
Public bug reported: Hi, it is time to report a bug to keep all info in one place. First of all ufw tests were broken with iptables 1.8.3 due to an ordering issue in the output. This I fixed and tested in [1]. It only adds one more "allowed result" to one of the tests, so it should be no big change. I double checked the upload to not (by any accident) change something else. $ debdiff ufw_0.36-1ubuntu1.dsc ufw_0.36-1ubuntu2.dsc | diffstat changelog |8 patches/0003-fix-test-iptables1.8.patch | 4151 patches/series |1 3 files changed, 4160 insertions(+) $ grep -e '---' -e '+++' ufw-0.36/debian/patches/0003-fix-test-iptables1.8.patch --- /dev/null +++ b/tests/root/valid/result.1.8 --- /dev/null +++ b/tests/root/valid6/result.1.8 => That seems safe to me. But since this hit Eoan the tests get stuck and hang what seems until aborted (we have seen up to 75h). A normal execution in the past was ~30 minutes. The modified test worked fine: http://paste.ubuntu.com/p/RKFvhTP8Ft/ But the test for ufw has multiple runs and I only fixed/modified/tested the "root-unitest". I'm running the full test now hoping it might reproduce locally for debugging. First I thought something else in Eoan changed now trigging this issue. But that is rather unlikely, as without the new iptables it works fine. So for now the working theory for now is that iptables 1.8.3 changed something else changed Formerly this was not seen as it failed on the bug I fixed before hitting the hang. But with the fix above applied it now triggers the hang. It always hangs at this tests: Test get_netfilter_capabilities() ERROR (CommandError): No server with a name or ID of '0eb6260d-c544-41eb-8cfa-baa9a745c528' nova show 0eb6260d-c544-41eb-8cfa-baa9a745c528 (adt-eoan-s390x-ufw-20190815-202934) The test uses no Nova, the last two lines is from the automation being aborted. What is interesting is that this test would be ran up to three times, and it sometimes succeeds one or two times now. So it might (in addition to be broken) also be flaky. [1]: https://code.launchpad.net/~paelzer/ubuntu/+source/ufw/+git/ufw/+merge/371391 ** Affects: ufw (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, it is time to report a bug to keep all info in one place. First of all ufw tests were broken with iptables 1.8.3 due to an ordering issue in the output. This I fixed and tested in [1]. It only adds one more "allowed result" to one of the tests, so it should be no big change. I double checked the upload to not (by any accident) change something else. $ debdiff ufw_0.36-1ubuntu1.dsc ufw_0.36-1ubuntu2.dsc | diffstat - changelog |8 - patches/0003-fix-test-iptables1.8.patch | 4151 - patches/series |1 - 3 files changed, 4160 insertions(+) + changelog |8 + patches/0003-fix-test-iptables1.8.patch | 4151 + patches/series |1 + 3 files changed, 4160 insertions(+) $ grep -e '---' -e '+++' ufw-0.36/debian/patches/0003-fix-test-iptables1.8.patch --- /dev/null +++ b/tests/root/valid/result.1.8 --- /dev/null +++ b/tests/root/valid6/result.1.8 - That seems safe to me. + => That seems safe to me. - But since this hit Eoan the tests get stuck and hang what seems until - aborted (we have seen up to 75h). A normal execution in the past was ~30 - minutes. - First I thought something else in Eoan changed now trigging this issue. - But that is rather unlikely, as without the new iptables it works fine. + But since this hit Eoan the tests get stuck and hang what seems until aborted (we have seen up to 75h). A normal execution in the past was ~30 minutes. + + The modified test worked fine: http://paste.ubuntu.com/p/RKFvhTP8Ft/ + But the test for ufw has multiple runs and I only fixed/modified/tested the "root-unitest". I'm running the full test now hoping it might reproduce locally for debugging. + + + First I thought something else in Eoan changed now trigging this issue. But that is rather unlikely, as without the new iptables it works fine. So for now the working theory for now is that iptables 1.8.3 changed something else changed Formerly this was not seen as it failed on the bug I fixed before hitting the hang. But with the fix above applied it now triggers the hang. It always hangs at this tests: - Test get_netfilter_capabilities() - ERROR (CommandError): No server with a name or ID of '0eb6260d-c544-41eb-8cfa-baa9a745c528' - nova show 0eb6260d-c544-41eb-8cfa-baa9a745c528 (adt-eoan-s390x-ufw-20190815-202934) + Test get_netfilter_capabilities() + ERROR (CommandError): No server with a name or ID of '0eb6260d-c544-41eb-8cfa-baa9a745c528' + nova show 0eb6260d-c
[Touch-packages] [Bug 1840633] Re: autopkgtests get stuck in Eoan with iptables 1.8.3
This ordering is interesting (from a good case): $ grep -e 'autopkgtest .*\[.*\]: test .*:' -e get_netfilter_capabilities old-iptables-good.txt test_get_netfilter_capabilities (tests.unit.test_util.UtilTestCase) Test get_netfilter_capabilities() ... ok test_get_netfilter_capabilities (tests.unit.test_util.UtilTestCase) Test get_netfilter_capabilities() ... ok autopkgtest [20:42:36]: test test-ufw.py: preparing testbed autopkgtest [20:44:18]: test test-ufw.py: [--- autopkgtest [20:44:22]: test test-ufw.py: ---] autopkgtest [20:44:22]: test test-ufw.py: - - - - - - - - - - results - - - - - - - - - - autopkgtest [20:44:22]: test root-unittest: preparing testbed autopkgtest [20:46:24]: test root-unittest: [--- autopkgtest [20:52:16]: test root-unittest: ---] autopkgtest [20:52:16]: test root-unittest: - - - - - - - - - - results - - - - - - - - - - autopkgtest [20:52:16]: test unittest: preparing testbed autopkgtest [20:52:24]: test unittest: [--- test_get_netfilter_capabilities (tests.unit.test_util.UtilTestCase) Test get_netfilter_capabilities() ... ok autopkgtest [20:59:10]: test unittest: ---] autopkgtest [20:59:11]: test unittest: - - - - - - - - - - results - - - - - - - - - - That means at least the first two of the times the test runs seems to be from the build as two of the autopkgtest entries come with "build-needed". That is interesting as: 1. the new ufw's actual build was obviously against proposed and there things worked fine You can see both occasions of the test in the build log at [1] 2. that build ran on all my tests before upload and it worked fine there Two occasions in http://paste.ubuntu.com/p/RKFvhTP8Ft/ 3. it is not the test, but the prep stage for "build-needed" that is failing which might also be the reason why there is no auto-timeout-abort The bad part, in a local build this just works fine: - autopkgtest in a VM is ok - sbuild building the package itself is ok Next steps: - what does this particular test actually do that could hang - what might be different in that build time comapred to "local-autopkgtest-vm" and the "normal LP builds" [1]: https://launchpadlibrarian.net/437577267/buildlog_ubuntu-eoan- amd64.ufw_0.36-1ubuntu2_BUILDING.txt.gz -- 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/1840633 Title: autopkgtests get stuck in Eoan with iptables 1.8.3 Status in ufw package in Ubuntu: New Bug description: Hi, it is time to report a bug to keep all info in one place. First of all ufw tests were broken with iptables 1.8.3 due to an ordering issue in the output. This I fixed and tested in [1]. It only adds one more "allowed result" to one of the tests, so it should be no big change. I double checked the upload to not (by any accident) change something else. $ debdiff ufw_0.36-1ubuntu1.dsc ufw_0.36-1ubuntu2.dsc | diffstat changelog |8 patches/0003-fix-test-iptables1.8.patch | 4151 patches/series |1 3 files changed, 4160 insertions(+) $ grep -e '---' -e '+++' ufw-0.36/debian/patches/0003-fix-test-iptables1.8.patch --- /dev/null +++ b/tests/root/valid/result.1.8 --- /dev/null +++ b/tests/root/valid6/result.1.8 => That seems safe to me. But since this hit Eoan the tests get stuck and hang what seems until aborted (we have seen up to 75h). A normal execution in the past was ~30 minutes. The modified test worked fine: http://paste.ubuntu.com/p/RKFvhTP8Ft/ But the test for ufw has multiple runs and I only fixed/modified/tested the "root-unitest". I'm running the full test now hoping it might reproduce locally for debugging. First I thought something else in Eoan changed now trigging this issue. But that is rather unlikely, as without the new iptables it works fine. So for now the working theory for now is that iptables 1.8.3 changed something else changed Formerly this was not seen as it failed on the bug I fixed before hitting the hang. But with the fix above applied it now triggers the hang. It always hangs at this tests: Test get_netfilter_capabilities() ERROR (CommandError): No server with a name or ID of '0eb6260d-c544-41eb-8cfa-baa9a745c528' nova show 0eb6260d-c544-41eb-8cfa-baa9a745c528 (adt-eoan-s390x-ufw-20190815-202934) The test uses no Nova, the last two lines is from the automation being aborted. What is interesting is that this test would be ran up to three times, and it sometimes succeeds one or two times now. So it might (in addition to be broken) also be flaky. [1]: https://code.launchpad.net/~paelzer/ubuntu/+source/ufw/+git/ufw/+merge/371391 To manage notifications about this bug go to: https://bugs.lau
[Touch-packages] [Bug 1840633] Re: autopkgtests get stuck in Eoan with iptables 1.8.3
There were a bunch of mentions of that function in bug 1044361 bug 1039729 and bug 1062521. And while the issues back then are in the code since version 34 we might again face something that is special about the network environment that is present only in the autopkgtest-env for "build-needed" but not in any other build env where everything is passing. -- 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/1840633 Title: autopkgtests get stuck in Eoan with iptables 1.8.3 Status in ufw package in Ubuntu: New Bug description: Hi, it is time to report a bug to keep all info in one place. First of all ufw tests were broken with iptables 1.8.3 due to an ordering issue in the output. This I fixed and tested in [1]. It only adds one more "allowed result" to one of the tests, so it should be no big change. I double checked the upload to not (by any accident) change something else. $ debdiff ufw_0.36-1ubuntu1.dsc ufw_0.36-1ubuntu2.dsc | diffstat changelog |8 patches/0003-fix-test-iptables1.8.patch | 4151 patches/series |1 3 files changed, 4160 insertions(+) $ grep -e '---' -e '+++' ufw-0.36/debian/patches/0003-fix-test-iptables1.8.patch --- /dev/null +++ b/tests/root/valid/result.1.8 --- /dev/null +++ b/tests/root/valid6/result.1.8 => That seems safe to me. But since this hit Eoan the tests get stuck and hang what seems until aborted (we have seen up to 75h). A normal execution in the past was ~30 minutes. The modified test worked fine: http://paste.ubuntu.com/p/RKFvhTP8Ft/ But the test for ufw has multiple runs and I only fixed/modified/tested the "root-unitest". I'm running the full test now hoping it might reproduce locally for debugging. First I thought something else in Eoan changed now trigging this issue. But that is rather unlikely, as without the new iptables it works fine. So for now the working theory for now is that iptables 1.8.3 changed something else changed Formerly this was not seen as it failed on the bug I fixed before hitting the hang. But with the fix above applied it now triggers the hang. It always hangs at this tests: Test get_netfilter_capabilities() ERROR (CommandError): No server with a name or ID of '0eb6260d-c544-41eb-8cfa-baa9a745c528' nova show 0eb6260d-c544-41eb-8cfa-baa9a745c528 (adt-eoan-s390x-ufw-20190815-202934) The test uses no Nova, the last two lines is from the automation being aborted. What is interesting is that this test would be ran up to three times, and it sometimes succeeds one or two times now. So it might (in addition to be broken) also be flaky. [1]: https://code.launchpad.net/~paelzer/ubuntu/+source/ufw/+git/ufw/+merge/371391 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1840633/+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 1840639] [NEW] Version 3.0.3 breaks lxc-usernsexec
Public bug reported: Affected version: 3.0.3 Last working version: 3.0.1 Upgrade from 3.0.1 to 3.0.3 for lxc packages breaks lxc-usernsexec with message 'Failed to find subuid or subgid allocation' even those allocation is fine. Downgrading back to 3.0.1 fixes the problem. Steps to reproduce: Set up 3.0.1 lxc to work. (lxc-usernsexec whoami should show 'root') Upgrade to 3.0.3 Run lxc-usernsexec whoami Expected result: root Actual result: Failed to find subuid or subgid allocation ** 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/1840639 Title: Version 3.0.3 breaks lxc-usernsexec Status in lxc package in Ubuntu: New Bug description: Affected version: 3.0.3 Last working version: 3.0.1 Upgrade from 3.0.1 to 3.0.3 for lxc packages breaks lxc-usernsexec with message 'Failed to find subuid or subgid allocation' even those allocation is fine. Downgrading back to 3.0.1 fixes the problem. Steps to reproduce: Set up 3.0.1 lxc to work. (lxc-usernsexec whoami should show 'root') Upgrade to 3.0.3 Run lxc-usernsexec whoami Expected result: root Actual result: Failed to find subuid or subgid allocation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1840639/+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 1840640] [NEW] sync_file_range fails in nspawn containers on arm, ppc
Public bug reported:
ARM has two sync_file_range syscalls, sync_file_range and
sync_file_range2. The former is apparently not used, and glibc calls the
latter whenever a userspace program calls sync_file_range. I'm guessing
systemd-nspawn doesn't know this, because the follow code consistently
fails in an nspawn container on ARM:
#define _GNU_SOURCE
#include
#include
#include
#include
void main()
{
int f = open("/tmp/syncrange.test",O_CREAT|O_RDWR,0666);
int r=sync_file_range(f, 0, 0, 0);
if (r)
perror("sync_file_range");
close(f);
}
This seems to be causing problems specifically for borg(backup) and
postgres:
https://github.com/borgbackup/borg/issues/4710
https://www.postgresql.org/message-id/flat/CA%2BhUKG%2BydOUT4zjxb6QmJWy8U9WbC-q%2BJWV7wLsEY9Df%3Dmw0Mw%40mail.gmail.com#ac8f14897647dc7eae3c7e7cbed36d93
The solution should be to cherrypick
https://github.com/systemd/systemd/pull/13352, I am currently waiting
for systemd to rebuild on a slow ARM box. Any chance of an SRU?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd-container 237-3ubuntu10.24
Uname: Linux 4.14.66+ armv7l
NonfreeKernelModules: extcon_usb_gpio
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: armhf
Date: Mon Aug 19 11:10:48 2019
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Tags: apport-bug armhf bionic
--
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/1840640
Title:
sync_file_range fails in nspawn containers on arm, ppc
Status in systemd package in Ubuntu:
New
Status in systemd source package in Bionic:
New
Bug description:
ARM has two sync_file_range syscalls, sync_file_range and
sync_file_range2. The former is apparently not used, and glibc calls
the latter whenever a userspace program calls sync_file_range. I'm
guessing systemd-nspawn doesn't know this, because the follow code
consistently fails in an nspawn container on ARM:
#define _GNU_SOURCE
#include
#include
#include
#include
void main()
{
int f = open("/tmp/syncrange.test",O_CREAT|O_RDWR,0666);
int r=sync_file_range(f, 0, 0, 0);
if (r)
perror("sync_file_range");
close(f);
}
This seems to be causing problems specifically for borg(backup) and
postgres:
https://github.com/borgbackup/borg/issues/4710
https://www.postgresql.org/message-id/flat/CA%2BhUKG%2BydOUT4zjxb6QmJWy8U9WbC-q%2BJWV7wLsEY9Df%3Dmw0Mw%40mail.gmail.com#ac8f14897647dc7eae3c7e7cbed36d93
The solution should be to cherrypick
https://github.com/systemd/systemd/pull/13352, I am currently waiting
for systemd to rebuild on a slow ARM box. Any chance of an SRU?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd-container 237-3ubuntu10.24
Uname: Linux 4.14.66+ armv7l
NonfreeKernelModules: extcon_usb_gpio
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: armhf
Date: Mon Aug 19 11:10:48 2019
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840640/+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 1840640] Re: sync_file_range fails in nspawn containers on arm, ppc
https://github.com/systemd/systemd/pull/13352/commits/90ddac6087b5f8f3736364cfdf698e713f7e8869.patch
--
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/1840640
Title:
sync_file_range fails in nspawn containers on arm, ppc
Status in systemd package in Ubuntu:
New
Status in systemd source package in Bionic:
New
Bug description:
ARM has two sync_file_range syscalls, sync_file_range and
sync_file_range2. The former is apparently not used, and glibc calls
the latter whenever a userspace program calls sync_file_range. I'm
guessing systemd-nspawn doesn't know this, because the follow code
consistently fails in an nspawn container on ARM:
#define _GNU_SOURCE
#include
#include
#include
#include
void main()
{
int f = open("/tmp/syncrange.test",O_CREAT|O_RDWR,0666);
int r=sync_file_range(f, 0, 0, 0);
if (r)
perror("sync_file_range");
close(f);
}
This seems to be causing problems specifically for borg(backup) and
postgres:
https://github.com/borgbackup/borg/issues/4710
https://www.postgresql.org/message-id/flat/CA%2BhUKG%2BydOUT4zjxb6QmJWy8U9WbC-q%2BJWV7wLsEY9Df%3Dmw0Mw%40mail.gmail.com#ac8f14897647dc7eae3c7e7cbed36d93
The solution should be to cherrypick
https://github.com/systemd/systemd/pull/13352, I am currently waiting
for systemd to rebuild on a slow ARM box. Any chance of an SRU?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd-container 237-3ubuntu10.24
Uname: Linux 4.14.66+ armv7l
NonfreeKernelModules: extcon_usb_gpio
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: armhf
Date: Mon Aug 19 11:10:48 2019
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840640/+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 1840640] Re: sync_file_range fails in nspawn containers on arm, ppc
this is cherrypickable, yes.
** Also affects: systemd (Ubuntu Bionic)
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/1840640
Title:
sync_file_range fails in nspawn containers on arm, ppc
Status in systemd package in Ubuntu:
New
Status in systemd source package in Bionic:
New
Bug description:
ARM has two sync_file_range syscalls, sync_file_range and
sync_file_range2. The former is apparently not used, and glibc calls
the latter whenever a userspace program calls sync_file_range. I'm
guessing systemd-nspawn doesn't know this, because the follow code
consistently fails in an nspawn container on ARM:
#define _GNU_SOURCE
#include
#include
#include
#include
void main()
{
int f = open("/tmp/syncrange.test",O_CREAT|O_RDWR,0666);
int r=sync_file_range(f, 0, 0, 0);
if (r)
perror("sync_file_range");
close(f);
}
This seems to be causing problems specifically for borg(backup) and
postgres:
https://github.com/borgbackup/borg/issues/4710
https://www.postgresql.org/message-id/flat/CA%2BhUKG%2BydOUT4zjxb6QmJWy8U9WbC-q%2BJWV7wLsEY9Df%3Dmw0Mw%40mail.gmail.com#ac8f14897647dc7eae3c7e7cbed36d93
The solution should be to cherrypick
https://github.com/systemd/systemd/pull/13352, I am currently waiting
for systemd to rebuild on a slow ARM box. Any chance of an SRU?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd-container 237-3ubuntu10.24
Uname: Linux 4.14.66+ armv7l
NonfreeKernelModules: extcon_usb_gpio
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: armhf
Date: Mon Aug 19 11:10:48 2019
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840640/+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 1754671] Re: Full-tunnel VPN DNS leakage regression
Any word on when this CVE will be fixed? In the meantime I have put the 1.10.14-0ubuntu2 package into an apt repository at http://david.woodhou.se/cve-2018-1000135/ for users who need it. I couldn't work out how to copy it into a PPA without rebuilding it. In the short term can someone please at least confirm that no new update will be shipped for Bionic which *doesn't* fix this, so that I don't have to play games with keeping a package in that repository "newer" than the latest in bionic-updates? -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Confirmed Status in systemd source package in Xenial: Invalid Status in network-manager source package in Bionic: In Progress Status in systemd source package in Bionic: Fix Released Status in network-manager source package in Cosmic: Won't Fix Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1840640] Re: sync_file_range fails in nspawn containers on arm, ppc
Test packages in case anyone wants them:
https://www.dropbox.com/sh/gxuy14k1t2chwbu/AABKX2idDrGu2R3Fwio0DAOTa?dl=0
--
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/1840640
Title:
sync_file_range fails in nspawn containers on arm, ppc
Status in systemd package in Ubuntu:
New
Status in systemd source package in Bionic:
New
Bug description:
ARM has two sync_file_range syscalls, sync_file_range and
sync_file_range2. The former is apparently not used, and glibc calls
the latter whenever a userspace program calls sync_file_range. I'm
guessing systemd-nspawn doesn't know this, because the follow code
consistently fails in an nspawn container on ARM:
#define _GNU_SOURCE
#include
#include
#include
#include
void main()
{
int f = open("/tmp/syncrange.test",O_CREAT|O_RDWR,0666);
int r=sync_file_range(f, 0, 0, 0);
if (r)
perror("sync_file_range");
close(f);
}
This seems to be causing problems specifically for borg(backup) and
postgres:
https://github.com/borgbackup/borg/issues/4710
https://www.postgresql.org/message-id/flat/CA%2BhUKG%2BydOUT4zjxb6QmJWy8U9WbC-q%2BJWV7wLsEY9Df%3Dmw0Mw%40mail.gmail.com#ac8f14897647dc7eae3c7e7cbed36d93
The solution should be to cherrypick
https://github.com/systemd/systemd/pull/13352, I am currently waiting
for systemd to rebuild on a slow ARM box. Any chance of an SRU?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd-container 237-3ubuntu10.24
Uname: Linux 4.14.66+ armv7l
NonfreeKernelModules: extcon_usb_gpio
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: armhf
Date: Mon Aug 19 11:10:48 2019
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840640/+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 1840633] Re: autopkgtests get stuck in Eoan with iptables 1.8.3
Thanks to Laney I now know that iptables is actually hanging in what seems to be a busy loop: ubuntu 717 0.0 0.7 22976 11968 ?S08:36 0:00 | \_ sshd: ubuntu@notty root 3715 0.0 0.6 16064 9536 ?Ss 08:36 0:00 | \_ sudo -n /tmp/autopkgtest-run-wrapper env ADT_TEST_TRIGGERS=iptables/1.8.3-2ubuntu1 sh -ec su --shell=/bin/sh ubuntu -c 'set -e; exec 3>&1 >&2; set -x; cd /tmp/autopkgtest.eeLwnO/build.zyB/src; DEB_BUILD_OPTIONS="parallel=1 $DEB_BUILD_OPTIONS" dpkg-buildpackage -us -uc -b; dpkg-source --before-build .' root 3716 0.0 0.1 11200 1920 ?S08:36 0:00 | \_ /bin/bash /tmp/autopkgtest-run-wrapper env ADT_TEST_TRIGGERS=iptables/1.8.3-2ubuntu1 sh -ec su --shell=/bin/sh ubuntu -c 'set -e; exec 3>&1 >&2; set -x; cd /tmp/autopkgtest.eeLwnO/build.zyB/src; DEB_BUILD_OPTIONS="parallel=1 $DEB_BUILD_OPTIONS" dpkg-buildpackage -us -uc -b; dpkg-source --before-build .' root 3718 0.0 0.0 3520 1408 ?S08:36 0:00 | \_ sh -ec su --shell=/bin/sh ubuntu -c 'set -e; exec 3>&1 >&2; set -x; cd /tmp/autopkgtest.eeLwnO/build.zyB/src; DEB_BUILD_OPTIONS="parallel=1 $DEB_BUILD_OPTIONS" dpkg-buildpackage -us -uc -b; dpkg-source --before-build .' root 3719 0.0 0.5 15680 8960 ?S08:36 0:00 | \_ su --shell=/bin/sh ubuntu -c set -e; exec 3>&1 >&2; set -x; cd /tmp/autopkgtest.eeLwnO/build.zyB/src; DEB_BUILD_OPTIONS="parallel=1 $DEB_BUILD_OPTIONS" dpkg-buildpackage -us -uc -b; dpkg-source --before-build . ubuntu3720 0.0 0.0 3520 1344 ?Ss 08:36 0:00 | \_ sh -c set -e; exec 3>&1 >&2; set -x; cd /tmp/autopkgtest.eeLwnO/build.zyB/src; DEB_BUILD_OPTIONS="parallel=1 $DEB_BUILD_OPTIONS" dpkg-buildpackage -us -uc -b; dpkg-source --before-build . ubuntu3721 0.0 1.3 28416 21120 ?S08:36 0:00 | \_ /usr/bin/perl /usr/bin/dpkg-buildpackage -us -uc -b ubuntu3810 0.0 0.0 3520 1344 ?S08:36 0:00 | \_ /bin/sh /usr/bin/fakeroot debian/rules binary ubuntu3825 0.0 0.1 9728 1728 ?S08:36 0:00 | \_ /usr/bin/make -f debian/rules binary ubuntu3835 0.0 0.1 3904 1792 ?S08:36 0:00 | \_ /bin/sh ./run_tests.sh -i /usr/bin/python2 ubuntu3854 1.0 3.4 58048 53952 ?S08:36 1:54 | \_ /usr/bin/python2 ./tests/unit/runner.py ubuntu 25819 99.9 0.1 5312 2368 ?R08:39 173:53 | \_ /sbin/iptables -N ufw-caps-testZNBjxu -- 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/1840633 Title: autopkgtests get stuck in Eoan with iptables 1.8.3 Status in ufw package in Ubuntu: New Bug description: Hi, it is time to report a bug to keep all info in one place. First of all ufw tests were broken with iptables 1.8.3 due to an ordering issue in the output. This I fixed and tested in [1]. It only adds one more "allowed result" to one of the tests, so it should be no big change. I double checked the upload to not (by any accident) change something else. $ debdiff ufw_0.36-1ubuntu1.dsc ufw_0.36-1ubuntu2.dsc | diffstat changelog |8 patches/0003-fix-test-iptables1.8.patch | 4151 patches/series |1 3 files changed, 4160 insertions(+) $ grep -e '---' -e '+++' ufw-0.36/debian/patches/0003-fix-test-iptables1.8.patch --- /dev/null +++ b/tests/root/valid/result.1.8 --- /dev/null +++ b/tests/root/valid6/result.1.8 => That seems safe to me. But since this hit Eoan the tests get stuck and hang what seems until aborted (we have seen up to 75h). A normal execution in the past was ~30 minutes. The modified test worked fine: http://paste.ubuntu.com/p/RKFvhTP8Ft/ But the test for ufw has multiple runs and I only fixed/modified/tested the "root-unitest". I'm running the full test now hoping it might reproduce locally for debugging. First I thought something else in Eoan changed now trigging this issue. But that is rather unlikely, as without the new iptables it works fine. So for now the working theory for now is that iptables 1.8.3 changed something else changed Formerly this was not seen as it failed on the bug I fixed before hitting the hang. But with the fix above applied it now triggers the hang. It always hangs at this tests: Test get_netfilter_capabilities() ERROR (CommandError): No server with a name or ID of '0eb6260d-c544-41eb-8cfa-baa9a745c528' nova show 0eb6260d-c544-41eb-8cfa-baa9a745c528 (adt-eoan-s390x-ufw-20190815-202934) The
[Touch-packages] [Bug 1840633] Re: autopkgtests get stuck in Eoan with iptables 1.8.3
Checking the hanging process shows:
https://paste.ubuntu.com/p/5Z745G963k/ <- that repeating endlessly
And wchan is "0" which means it is really busy
That is:
sendto(4, {{len=20,
type=NFNL_SUBSYS_NFTABLES<<8|NFT_MSG_GETGEN, flags=NLM_F_REQUEST, seq=0,
pid=0}, {nfgen_family=AF_UNSPEC, version=NFNETLINK_V0, res_id=htons(0)}, 20, 0,
{sa_family=AF_NETLINK, nl_pid=0, nl_groups=}, 12) = 20
recvmsg(4, {msg_name={sa_family=AF_NETLINK, nl_pid=0,
nl_groups=}, msg_namelen=12, msg_iov=[{iov_base={{len=40,
type=NLMSG_ERROR, flags=0, seq=0, pid=25819}, {error=-EPERM, msg={{len=20,
type=NFNL_SUBSYS_NFTABLES<<8|NFT_MSG_GETGEN, flags=NLM_F_REQUEST, seq=0,
pid=0}, {nfgen_family=AF_UNSPEC, version=NFNETLINK_V0, res_id=htons(0)}}},
iov_len=16536}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 40
sendto(4, {{len=20,
type=NFNL_SUBSYS_NFTABLES<<8|NFT_MSG_GETGEN, flags=NLM_F_REQUEST, seq=0,
pid=0}, {nfgen_family=AF_UNSPEC, version=NFNETLINK_V0, res_id=htons(0)}, 20, 0,
{sa_family=AF_NETLINK, nl_pid=0, nl_groups=}, 12) = 20
recvmsg(4, {msg_name={sa_family=AF_NETLINK, nl_pid=0,
nl_groups=}, msg_namelen=12, msg_iov=[{iov_base={{len=40,
type=NLMSG_ERROR, flags=0, seq=0, pid=25819}, {error=-EPERM, msg={{len=20,
type=NFNL_SUBSYS_NFTABLES<<8|NFT_MSG_GETGEN, flags=NLM_F_REQUEST, seq=0,
pid=0}, {nfgen_family=AF_UNSPEC, version=NFNETLINK_V0, res_id=htons(0)}}},
iov_len=16536}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 40
sendto(4, {{len=20,
type=NFNL_SUBSYS_NFTABLES<<8|NFT_MSG_GETTABLE, flags=NLM_F_REQUEST|NLM_F_DUMP,
seq=0, pid=0}, {nfgen_family=AF_INET, version=NFNETLINK_V0, res_id=htons(0)},
20, 0, {sa_family=AF_NETLINK, nl_pid=0, nl_groups=}, 12) = 20
recvmsg(4, {msg_name={sa_family=AF_NETLINK, nl_pid=0,
nl_groups=}, msg_namelen=12, msg_iov=[{iov_base={{len=40,
type=NLMSG_ERROR, flags=0, seq=0, pid=25819}, {error=-EPERM, msg={{len=20,
type=NFNL_SUBSYS_NFTABLES<<8|NFT_MSG_GETTABLE, flags=NLM_F_REQUEST|NLM_F_DUMP,
seq=0, pid=0}, {nfgen_family=AF_INET, version=NFNETLINK_V0, res_id=htons(0)}}},
iov_len=16536}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 40
sendto(4, {{len=20,
type=NFNL_SUBSYS_NFTABLES<<8|NFT_MSG_GETCHAIN, flags=NLM_F_REQUEST|NLM_F_DUMP,
seq=0, pid=0}, {nfgen_family=AF_INET, version=NFNETLINK_V0, res_id=htons(0)},
20, 0, {sa_family=AF_NETLINK, nl_pid=0, nl_groups=}, 12) = 20
recvmsg(4, {msg_name={sa_family=AF_NETLINK, nl_pid=0,
nl_groups=}, msg_namelen=12, msg_iov=[{iov_base={{len=40,
type=NLMSG_ERROR, flags=0, seq=0, pid=25819}, {error=-EPERM, msg={{len=20,
type=NFNL_SUBSYS_NFTABLES<<8|NFT_MSG_GETCHAIN, flags=NLM_F_REQUEST|NLM_F_DUMP,
seq=0, pid=0}, {nfgen_family=AF_INET, version=NFNETLINK_V0, res_id=htons(0)}}},
iov_len=16536}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 40
sendto(4, {{len=20,
type=NFNL_SUBSYS_NFTABLES<<8|NFT_MSG_GETGEN, flags=NLM_F_REQUEST, seq=0,
pid=0}, {nfgen_family=AF_UNSPEC, version=NFNETLINK_V0, res_id=htons(0)}, 20, 0,
{sa_family=AF_NETLINK, nl_pid=0, nl_groups=}, 12) = 20
recvmsg(4, {msg_name={sa_family=AF_NETLINK, nl_pid=0,
nl_groups=}, msg_namelen=12, msg_iov=[{iov_base={{len=40,
type=NLMSG_ERROR, flags=0, seq=0, pid=25819}, {error=-EPERM, msg={{len=20,
type=NFNL_SUBSYS_NFTABLES<<8|NFT_MSG_GETGEN, flags=NLM_F_REQUEST, seq=0,
pid=0}, {nfgen_family=AF_UNSPEC, version=NFNETLINK_V0, res_id=htons(0)}}},
iov_len=16536}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 40
sendto(4, {{len=20,
type=NFNL_SUBSYS_NFTABLES<<8|NFT_MSG_GETGEN, flags=NLM_F_REQUEST, seq=0,
pid=0}, {nfgen_family=AF_UNSPEC, version=NFNETLINK_V0, res_id=htons(0)}, 20, 0,
{sa_family=AF_NETLINK, nl_pid=0, nl_groups=}, 12) = 20
recvmsg(4, {msg_name={sa_family=AF_NETLINK, nl_pid=0,
nl_groups=}, msg_namelen=12, msg_iov=[{iov_base={{len=40,
type=NLMSG_ERROR, flags=0, seq=0, pid=25819}, {error=-EPERM, msg={{len=20,
type=NFNL_SUBSYS_NFTABLES<<8|NFT_MSG_GETGEN, flags=NLM_F_REQUEST, seq=0,
pid=0}, {nfgen_family=AF_UNSPEC, version=NFNETLINK_V0, res_id=htons(0)}}},
iov_len=16536}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 40
sendto(4, {{len=20,
type=NFNL_SUBSYS_NFTABLES<<8|NFT_MSG_GETTABLE, flags=NLM_F_REQUEST|NLM_F_DUMP,
seq=0, pid=0}, {nfgen_family=AF_INET, version=NFNETLINK_V0, res_id=htons(0)},
20, 0, {sa_family=AF_NETLINK, nl_pid=0, nl_groups=}, 12) = 20
--
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/1840633
Title:
autopkgtests get stuck in Eoan with iptables 1.8.3
Status in ufw package in Ubuntu:
New
Bug description:
Hi,
it is time to report a bug to keep all info in one place.
First of all ufw tests were broken with iptables 1.8.3 due to an ordering
issue in the output.
This I fixed and tested in [1].
It only adds one more "allowed result" to one of the tests, so it should be
no big change.
I dou
[Touch-packages] [Bug 1840633] Re: autopkgtests get stuck in Eoan with iptables 1.8.3
I ran a test on bileto ticket [1] with some extended debug output. A good run would look like: test_get_netfilter_capabilities (tests.unit.test_util.UtilTestCase) Test get_netfilter_capabilities() ...· TDEBUG: check OSError GNC: Enter get_netfilter_capabilities GNC: we are root GNC: chain ufw-caps-testSz014H GNC: exe /sbin/iptables TDEBUG: past OSError TDEBUG: exe /<>/tests/unit/fake-binaries/iptables GNC: Enter get_netfilter_capabilities GNC: we are root GNC: chain ufw-caps-test4To0RO GNC: exe /<>/tests/unit/fake-binaries/iptables GNC: recent-set GNC: recent-update GNC: cleanup GNC: rc 0 GNC: caps ['recent-set', 'recent-update'] TDEBUG: post check I TDEBUG: exe /<>/tests/unit/fake-binaries/ip6tables GNC: Enter get_netfilter_capabilities GNC: we are root GNC: chain ufw6-caps-testwvcC9O GNC: exe /<>/tests/unit/fake-binaries/ip6tables GNC: recent-set GNC: recent-update GNC: cleanup GNC: rc 0 GNC: caps ['recent-set', 'recent-update'] TDEBUG: post check II ok This is just to check which call from python actually breaks it. [1]: https://bileto.ubuntu.com/#/ticket/3790 -- 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/1840633 Title: autopkgtests get stuck in Eoan with iptables 1.8.3 Status in ufw package in Ubuntu: New Bug description: Hi, it is time to report a bug to keep all info in one place. First of all ufw tests were broken with iptables 1.8.3 due to an ordering issue in the output. This I fixed and tested in [1]. It only adds one more "allowed result" to one of the tests, so it should be no big change. I double checked the upload to not (by any accident) change something else. $ debdiff ufw_0.36-1ubuntu1.dsc ufw_0.36-1ubuntu2.dsc | diffstat changelog |8 patches/0003-fix-test-iptables1.8.patch | 4151 patches/series |1 3 files changed, 4160 insertions(+) $ grep -e '---' -e '+++' ufw-0.36/debian/patches/0003-fix-test-iptables1.8.patch --- /dev/null +++ b/tests/root/valid/result.1.8 --- /dev/null +++ b/tests/root/valid6/result.1.8 => That seems safe to me. But since this hit Eoan the tests get stuck and hang what seems until aborted (we have seen up to 75h). A normal execution in the past was ~30 minutes. The modified test worked fine: http://paste.ubuntu.com/p/RKFvhTP8Ft/ But the test for ufw has multiple runs and I only fixed/modified/tested the "root-unitest". I'm running the full test now hoping it might reproduce locally for debugging. First I thought something else in Eoan changed now trigging this issue. But that is rather unlikely, as without the new iptables it works fine. So for now the working theory for now is that iptables 1.8.3 changed something else changed Formerly this was not seen as it failed on the bug I fixed before hitting the hang. But with the fix above applied it now triggers the hang. It always hangs at this tests: Test get_netfilter_capabilities() ERROR (CommandError):
[Touch-packages] [Bug 1840633] Re: autopkgtests get stuck in Eoan with iptables 1.8.3
But the ps output already has identified a hang inside of iptables itself hanging. The commandline identified it coming from 767 # First install a test chain 768 (rc, out) = cmd([exe, '-N', chain]) 769 if rc != 0: In the example: /sbin/iptables -N ufw-caps-testZNBjxu That doesn't have a lot of content yet, it is "just" installing a new chain. -- 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/1840633 Title: autopkgtests get stuck in Eoan with iptables 1.8.3 Status in ufw package in Ubuntu: New Bug description: Hi, it is time to report a bug to keep all info in one place. First of all ufw tests were broken with iptables 1.8.3 due to an ordering issue in the output. This I fixed and tested in [1]. It only adds one more "allowed result" to one of the tests, so it should be no big change. I double checked the upload to not (by any accident) change something else. $ debdiff ufw_0.36-1ubuntu1.dsc ufw_0.36-1ubuntu2.dsc | diffstat changelog |8 patches/0003-fix-test-iptables1.8.patch | 4151 patches/series |1 3 files changed, 4160 insertions(+) $ grep -e '---' -e '+++' ufw-0.36/debian/patches/0003-fix-test-iptables1.8.patch --- /dev/null +++ b/tests/root/valid/result.1.8 --- /dev/null +++ b/tests/root/valid6/result.1.8 => That seems safe to me. But since this hit Eoan the tests get stuck and hang what seems until aborted (we have seen up to 75h). A normal execution in the past was ~30 minutes. The modified test worked fine: http://paste.ubuntu.com/p/RKFvhTP8Ft/ But the test for ufw has multiple runs and I only fixed/modified/tested the "root-unitest". I'm running the full test now hoping it might reproduce locally for debugging. First I thought something else in Eoan changed now trigging this issue. But that is rather unlikely, as without the new iptables it works fine. So for now the working theory for now is that iptables 1.8.3 changed something else changed Formerly this was not seen as it failed on the bug I fixed before hitting the hang. But with the fix above applied it now triggers the hang. It always hangs at this tests: Test get_netfilter_capabilities() ERROR (CommandError): No server with a name or ID of '0eb6260d-c544-41eb-8cfa-baa9a745c528' nova show 0eb6260d-c544-41eb-8cfa-baa9a745c528 (adt-eoan-s390x-ufw-20190815-202934) The test uses no Nova, the last two lines is from the automation being aborted. What is interesting is that this test would be ran up to three times, and it sometimes succeeds one or two times now. So it might (in addition to be broken) also be flaky. [1]: https://code.launchpad.net/~paelzer/ubuntu/+source/ufw/+git/ufw/+merge/371391 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1840633/+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 1807709] Re: dbus always crashes at session start (on wayland)
Would someone be able to indicate how to get a full backtrace & coredump? That could be useful in getting the reason of the crashes? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1807709 Title: dbus always crashes at session start (on wayland) Status in dbus package in Ubuntu: Confirmed Bug description: When you login in ubuntu 18.10 using gnome shell and wayland, dbus always crashes and you are welcomed with a dialog to report the crash. Looking into the file `/var/crash/_usr_bin_dbus-daemon.1000.crash` one can see that there is antoher bug, previoulsy reported as #1591548 (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1591548) So may be the bug report is never sent, either ? /var/crash/_usr_bin_dbus-daemon.1000.crash content is: ProblemType: Crash Architecture: amd64 Date: Sun Dec 9 11:16:22 2018 DistroRelease: Ubuntu 18.10 ExecutablePath: /usr/bin/dbus-daemon ExecutableTimestamp: 1536206167 ProcCmdline: /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only ProcCwd: /home/solstice ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcMaps: 55c9bfc7a000-55c9bfc83000 r--p 08:07 787824 /usr/bin/dbus-daemon 55c9bfc83000-55c9bfca5000 r-xp 9000 08:07 787824 /usr/bin/dbus-daemon 55c9bfca5000-55c9bfcb3000 r--p 0002b000 08:07 787824 /usr/bin/dbus-daemon 55c9bfcb3000-55c9bfcb5000 r--p 00038000 08:07 787824 /usr/bin/dbus-daemon 55c9bfcb5000-55c9bfcb6000 rw-p 0003a000 08:07 787824 /usr/bin/dbus-daemon 55c9c1bd8000-55c9c1f1e000 rw-p 00:00 0 [heap] 7eff0278c000-7eff02792000 r--p 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff02792000-7eff027bd000 r-xp 6000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027bd000-7eff027cc000 r--p 00031000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027cc000-7eff027cf000 r--p 0003f000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027cf000-7eff027d rw-p 00042000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027d-7eff027d1000 rw-p 00:00 0 7eff027d1000-7eff027d4000 r--p 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027d4000-7eff027db000 r-xp 3000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027db000-7eff027de000 r--p a000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027de000-7eff027df000 r--p c000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027df000-7eff027e rw-p d000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027e-7eff027e6000 rw-p 00:00 0 7eff027e6000-7eff027ea000 r--p 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027ea000-7eff027f8000 r-xp 4000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027f8000-7eff027fd000 r--p 00012000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027fd000-7eff027fe000 r--p 00016000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027fe000-7eff027ff000 rw-p 00017000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027ff000-7eff02801000 rw-p 00:00 0 7eff02801000-7eff02803000 r--p 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff02803000-7eff0280b000 r-xp 2000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280b000-7eff0280d000 r--p a000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280d000-7eff0280e000 r--p b000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280e000-7eff0280f000 rw-p c000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280f000-7eff02811000 r--p 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02811000-7eff02817000 r-xp 2000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02817000-7eff02818000 r--p 8000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02818000-7eff02819000 r--p 8000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02819000-7eff0281a000 rw-p 9000 08:07 654767 /lib/x86_64-linux
[Touch-packages] [Bug 1840633] Re: autopkgtests get stuck in Eoan with iptables 1.8.3
Original run command would be: $ #/home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.zn3q26vh/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --setup-commands /home/ubuntu/autopkgtest/setup-commands/setup-testbed --apt-pocket=proposed --apt-upgrade ufw --env=ADT_TEST_TRIGGERS=iptables/1.8.3-2ubuntu1 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest --security-groups autopkgtest@lgw01-14.secgroup --name adt-eoan-amd64-ufw-20190817-072321 --image adt/ubuntu-eoan-amd64-server --keyname testbed-juju-prod-ues-proposed-migration-machine-11 --net-id=net_ues_proposed_migration -e ''"'"'http_proxy=http://squid.internal:3128'"'"'' -e ''"'"'https_proxy=http://squid.internal:3128'"'"'' -e ''"'"'no_proxy=127.0.0.1,127.0.1.1,localhost,localdomain,novalocal,internal,archive.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,ppa.launchpad.net'"'"'' --mirror=http://ftpmaster.internal/ubuntu But I could not convince canonistack to take a new instance as that. Probably special image type and some internal credentials. The closest I could try was running it (build) on a canonistack instance myself. But since I knew tat even build on LP is fine (only the build-need autopkgtest isn't) the hope that this triggers was low. Setup I used: 1. canonistack m1.medium per [2] 2. copy into this instacne my local UFW directory (to not install ubuntu-dev-tools and all its dependences) 3. use autopkgtest with autopkgtest-virt-null driver to run on this instance $ sudo touch /run/autopkgtest_no_reboot.stamp $ sudo autopkgtest --apt-upgrade --apt-pocket=proposed=src:iptables --shell-fail --output-dir=/tmp/test-v1 ufw_0.36-1ubuntu3~ppa1.dsc -- null But this goes straight to the testing, I need to isolate what the build-needed flag runs. [1]: https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure#Worker_service_in_the_cloud [2]: https://wiki.canonical.com/InformationInfrastructure/IS/CanoniStack-BOS01#Non-Juju -- 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/1840633 Title: autopkgtests get stuck in Eoan with iptables 1.8.3 Status in ufw package in Ubuntu: New Bug description: Hi, it is time to report a bug to keep all info in one place. First of all ufw tests were broken with iptables 1.8.3 due to an ordering issue in the output. This I fixed and tested in [1]. It only adds one more "allowed result" to one of the tests, so it should be no big change. I double checked the upload to not (by any accident) change something else. $ debdiff ufw_0.36-1ubuntu1.dsc ufw_0.36-1ubuntu2.dsc | diffstat changelog |8 patches/0003-fix-test-iptables1.8.patch | 4151 patches/series |1 3 files changed, 4160 insertions(+) $ grep -e '---' -e '+++' ufw-0.36/debian/patches/0003-fix-test-iptables1.8.patch --- /dev/null +++ b/tests/root/valid/result.1.8 --- /dev/null +++ b/tests/root/valid6/result.1.8 => That seems safe to me. But since this hit Eoan the tests get stuck and hang what seems until aborted (we have seen up to 75h). A normal execution in the past was ~30 minutes. The modified test worked fine: http://paste.ubuntu.com/p/RKFvhTP8Ft/ But the test for ufw has multiple runs and I only fixed/modified/tested the "root-unitest". I'm running the full test now hoping it might reproduce locally for debugging. First I thought something else in Eoan changed now trigging this issue. But that is rather unlikely, as without the new iptables it works fine. So for now the working theory for now is that iptables 1.8.3 changed something else changed Formerly this was not seen as it failed on the bug I fixed before hitting the hang. But with the fix above applied it now triggers the hang. It always hangs at this tests: Test get_netfilter_capabilities() ERROR (CommandError): No server with a name or ID of '0eb6260d-c544-41eb-8cfa-baa9a745c528' nova show 0eb6260d-c544-41eb-8cfa-baa9a745c528 (adt-eoan-s390x-ufw-20190815-202934) The test uses no Nova, the last two lines is from the automation being aborted. What is interesting is that this test would be ran up to three times, and it sometimes succeeds one or two times now. So it might (in addition to be broken) also be flaky. [1]: https://code.launchpad.net/~paelzer/ubuntu/+source/ufw/+git/ufw/+merge/371391 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1840633/+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 1840633] Re: autopkgtests get stuck in Eoan with iptables 1.8.3
I discussed if maybe it is part of the special net rules "autopkgtest@lgw01-14.secgroup" that I saw in the command - but according to Laney/Juliank those are just copies of the default group for scaling reasons. -- 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/1840633 Title: autopkgtests get stuck in Eoan with iptables 1.8.3 Status in ufw package in Ubuntu: New Bug description: Hi, it is time to report a bug to keep all info in one place. First of all ufw tests were broken with iptables 1.8.3 due to an ordering issue in the output. This I fixed and tested in [1]. It only adds one more "allowed result" to one of the tests, so it should be no big change. I double checked the upload to not (by any accident) change something else. $ debdiff ufw_0.36-1ubuntu1.dsc ufw_0.36-1ubuntu2.dsc | diffstat changelog |8 patches/0003-fix-test-iptables1.8.patch | 4151 patches/series |1 3 files changed, 4160 insertions(+) $ grep -e '---' -e '+++' ufw-0.36/debian/patches/0003-fix-test-iptables1.8.patch --- /dev/null +++ b/tests/root/valid/result.1.8 --- /dev/null +++ b/tests/root/valid6/result.1.8 => That seems safe to me. But since this hit Eoan the tests get stuck and hang what seems until aborted (we have seen up to 75h). A normal execution in the past was ~30 minutes. The modified test worked fine: http://paste.ubuntu.com/p/RKFvhTP8Ft/ But the test for ufw has multiple runs and I only fixed/modified/tested the "root-unitest". I'm running the full test now hoping it might reproduce locally for debugging. First I thought something else in Eoan changed now trigging this issue. But that is rather unlikely, as without the new iptables it works fine. So for now the working theory for now is that iptables 1.8.3 changed something else changed Formerly this was not seen as it failed on the bug I fixed before hitting the hang. But with the fix above applied it now triggers the hang. It always hangs at this tests: Test get_netfilter_capabilities() ERROR (CommandError): No server with a name or ID of '0eb6260d-c544-41eb-8cfa-baa9a745c528' nova show 0eb6260d-c544-41eb-8cfa-baa9a745c528 (adt-eoan-s390x-ufw-20190815-202934) The test uses no Nova, the last two lines is from the automation being aborted. What is interesting is that this test would be ran up to three times, and it sometimes succeeds one or two times now. So it might (in addition to be broken) also be flaky. [1]: https://code.launchpad.net/~paelzer/ubuntu/+source/ufw/+git/ufw/+merge/371391 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1840633/+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 1840633] Re: autopkgtests get stuck in Eoan with iptables 1.8.3
Note from my debug builds:
TDEBUG: check OSError
GNC: Enter get_netfilter_capabilities
GNC: we are root
GNC: chain ufw-caps-testSqLa5Y
GNC: exe /sbin/iptables
That means it is the first action of the test, just running
/sbin/iptables -N ufw-caps-testSqLa5Y
Nothing else of the python stack was running before as part of the test.
debian/rules just has:
30 install: build
31 »···dh_testdir
32 »···dh_testroot
33 »···dh_prep
34 »···dh_installdirs
35
36 ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS)))
37 »···./run_tests.sh -i $(PYTHON2)
38 »···./run_tests.sh -i $(PYTHON)
39 »···# the testsuite creates the build/ directory with test values that we
40 »···# don't want to use
41 »···make clean
42 endif
We should actually be able to just run
$ sudo apt build-dep ufw
$ ./debian/rules install
In general this is mostly python, so build almost only consists of
selftests.
But no matter what I do the test either
a) works
b) breaks on the root check like
File "/home/ubuntu/ufw/tests/unit/test_util.py", line 918, in
test_get_netfilter_capabilities
ufw.util.get_netfilter_capabilities)
File "/home/ubuntu/ufw/tests/unit/support.py", line 164, in
check_for_exception
t.fail('%s not thrown' % str(expectedException))
AssertionError: not thrown
--
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/1840633
Title:
autopkgtests get stuck in Eoan with iptables 1.8.3
Status in ufw package in Ubuntu:
New
Bug description:
Hi,
it is time to report a bug to keep all info in one place.
First of all ufw tests were broken with iptables 1.8.3 due to an ordering
issue in the output.
This I fixed and tested in [1].
It only adds one more "allowed result" to one of the tests, so it should be
no big change.
I double checked the upload to not (by any accident) change something else.
$ debdiff ufw_0.36-1ubuntu1.dsc ufw_0.36-1ubuntu2.dsc | diffstat
changelog |8
patches/0003-fix-test-iptables1.8.patch | 4151
patches/series |1
3 files changed, 4160 insertions(+)
$ grep -e '---' -e '+++'
ufw-0.36/debian/patches/0003-fix-test-iptables1.8.patch
--- /dev/null
+++ b/tests/root/valid/result.1.8
--- /dev/null
+++ b/tests/root/valid6/result.1.8
=> That seems safe to me.
But since this hit Eoan the tests get stuck and hang what seems until aborted
(we have seen up to 75h). A normal execution in the past was ~30 minutes.
The modified test worked fine: http://paste.ubuntu.com/p/RKFvhTP8Ft/
But the test for ufw has multiple runs and I only fixed/modified/tested the
"root-unitest". I'm running the full test now hoping it might reproduce locally
for debugging.
First I thought something else in Eoan changed now trigging this issue. But
that is rather unlikely, as without the new iptables it works fine.
So for now the working theory for now is that iptables 1.8.3 changed
something else changed
Formerly this was not seen as it failed on the bug I fixed before hitting the
hang.
But with the fix above applied it now triggers the hang.
It always hangs at this tests:
Test get_netfilter_capabilities()
ERROR (CommandError): No server with a name or ID of
'0eb6260d-c544-41eb-8cfa-baa9a745c528'
nova show 0eb6260d-c544-41eb-8cfa-baa9a745c528
(adt-eoan-s390x-ufw-20190815-202934)
The test uses no Nova, the last two lines is from the automation being
aborted.
What is interesting is that this test would be ran up to three times,
and it sometimes succeeds one or two times now. So it might (in
addition to be broken) also be flaky.
[1]:
https://code.launchpad.net/~paelzer/ubuntu/+source/ufw/+git/ufw/+merge/371391
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1840633/+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 1840633] Re: autopkgtests get stuck in Eoan with iptables 1.8.3
Since iptables seems to hang it might be more a bug in there, but I fail to recreate the case for further analysis no matter what I tried so far :-/ Adding iptables bug task and subscribing jdstrand in case he has another idea due to his experience in that area. ** Also affects: iptables (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1840633 Title: autopkgtests get stuck in Eoan with iptables 1.8.3 Status in iptables package in Ubuntu: New Status in ufw package in Ubuntu: New Bug description: Hi, it is time to report a bug to keep all info in one place. First of all ufw tests were broken with iptables 1.8.3 due to an ordering issue in the output. This I fixed and tested in [1]. It only adds one more "allowed result" to one of the tests, so it should be no big change. I double checked the upload to not (by any accident) change something else. $ debdiff ufw_0.36-1ubuntu1.dsc ufw_0.36-1ubuntu2.dsc | diffstat changelog |8 patches/0003-fix-test-iptables1.8.patch | 4151 patches/series |1 3 files changed, 4160 insertions(+) $ grep -e '---' -e '+++' ufw-0.36/debian/patches/0003-fix-test-iptables1.8.patch --- /dev/null +++ b/tests/root/valid/result.1.8 --- /dev/null +++ b/tests/root/valid6/result.1.8 => That seems safe to me. But since this hit Eoan the tests get stuck and hang what seems until aborted (we have seen up to 75h). A normal execution in the past was ~30 minutes. The modified test worked fine: http://paste.ubuntu.com/p/RKFvhTP8Ft/ But the test for ufw has multiple runs and I only fixed/modified/tested the "root-unitest". I'm running the full test now hoping it might reproduce locally for debugging. First I thought something else in Eoan changed now trigging this issue. But that is rather unlikely, as without the new iptables it works fine. So for now the working theory for now is that iptables 1.8.3 changed something else changed Formerly this was not seen as it failed on the bug I fixed before hitting the hang. But with the fix above applied it now triggers the hang. It always hangs at this tests: Test get_netfilter_capabilities() ERROR (CommandError): No server with a name or ID of '0eb6260d-c544-41eb-8cfa-baa9a745c528' nova show 0eb6260d-c544-41eb-8cfa-baa9a745c528 (adt-eoan-s390x-ufw-20190815-202934) The test uses no Nova, the last two lines is from the automation being aborted. What is interesting is that this test would be ran up to three times, and it sometimes succeeds one or two times now. So it might (in addition to be broken) also be flaky. [1]: https://code.launchpad.net/~paelzer/ubuntu/+source/ufw/+git/ufw/+merge/371391 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1840633/+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 1833532] Re: systemd-backlight does not restore screen brightness after reboot
Still affected. https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1840592 ** Changed in: systemd (Ubuntu) Status: Incomplete => Confirmed -- 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/1833532 Title: systemd-backlight does not restore screen brightness after reboot Status in systemd package in Ubuntu: Confirmed Bug description: As the title says, on this laptop the brightness controls are NOT saved after reboot. What is saved instead, is only the keyboard brightness. I have tested two distros, Ubuntu 18.04.2 LTS and 19.04, happens on both systems. But there is a difference On 19.04, "systemctl status systemd-backlight@:*intel_screen_backlight_*" shows: "Saved brightness 20 too low, increasing to 75" On 18.04.2 does not show anything rather than the service starting normally The laptop is a Dell XPS 15 9550, the screen backlight driver is the intel one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1833532/+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 1840592] Re: display brightness not restored on next boot resets to 100
/lib/systemd/system/systemd-backlight@.service NOT working properly with nvidia cards. ** 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/1840592 Title: display brightness not restored on next boot resets to 100 Status in nvidia-graphics-drivers package in Ubuntu: New Status in nvidia-graphics-drivers-418 package in Ubuntu: New Status in nvidia-settings package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5% steps. However, after a reboot or after a shutdown, brightness level reverts to 100%. Please fix to is "remembers" the current brightness value at shutdown time, like in does Windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1840592/+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 1440818] Re: apport-bug does not anonymize udevdb log
** Changed in: apport (Ubuntu) Status: New => Incomplete -- 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/1440818 Title: apport-bug does not anonymize udevdb log Status in apport package in Ubuntu: Incomplete Bug description: when apport-bug joins the output of 'udevadm info --export-db' as UdevDb.txt' in a bug report, various uuid related to partitions, file systems, and disks are not anonymized. More over serial number of disk, mac adress, or WWN are not anonymized either. I join a patch (to hookutils.py) that attempts to fix that ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apport 2.17-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: wl ApportLog: ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CrashReports: 640:1000:118:1466952:2015-04-02 01:07:55.905460014 +0200:2015-04-02 02:29:42.472130210 +0200:/var/crash/_usr_bin_cryptkeeper.1000.crash 600:109:118:0:2015-04-02 01:07:53.619086261 +0200:2015-04-02 19:56:51.622507923 +0200:/var/crash/_usr_bin_cryptkeeper.1000.uploaded 664:1000:118:0:2015-04-02 01:07:52.598016638 +0200:2015-04-02 19:56:51.622507923 +0200:/var/crash/_usr_bin_cryptkeeper.1000.upload 640:1000:118:8871994:2015-04-02 20:28:37.247845958 +0200:2015-04-02 20:28:37.599849491 +0200:/var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash CurrentDesktop: Unity Date: Mon Apr 6 19:28:41 2015 InstallationDate: Installed on 2015-04-01 (4 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) 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/1440818/+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 1361447] Re: Cannot examine crash report locally: "Error while creating the child process": (No such file or directory)
** Changed in: apport (Ubuntu) Status: Confirmed => Incomplete -- 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/1361447 Title: Cannot examine crash report locally: "Error while creating the child process": (No such file or directory) Status in apport package in Ubuntu: Incomplete Bug description: When using "Examine locally" after "ubuntu-bug /var/crash/..." and selecting to run a gdb session, the following error dialog pops up: Error while creating the child process: Failed to execute child process "apport-retrace --gdb '/var/crash/crash'" (No such file or directory) It looks like apport is calling the process wrong: instead of as a command plus arguments, the whole string might get used as command. It works fine from the shell. (btw: it would be nice, if copy'n'paste would work for the text of such popups) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu3.3 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CrashReports: 640:0:114:198430:2014-08-17 16:42:49.715965167 +0200:2014-08-17 16:42:49.711965167 +0200:/var/crash/susres.2014-08-17_16:42:49.718598.crash 640:1000:114:185625:2014-08-20 18:38:13.700118400 +0200:2014-08-20 18:38:13.520118396 +0200:/var/crash/_usr_bin_redshift.1000.crash 640:1000:114:5702851:2014-08-26 02:18:55.313115119 +0200:2014-08-26 02:19:13.153115552 +0200:/var/crash/_usr_bin_vim.gnome.1000.crash CurrentDesktop: GNOME Date: Tue Aug 26 02:20:45 2014 InstallationDate: Installed on 2012-05-28 (819 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-05-01 (116 days ago) mtime.conffile..etc.apport.crashdb.conf: 2014-05-07T17:51:23.631588 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1361447/+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 1840592] Re: systemd-backlight does not save&restore brightness for nvidia display
** Summary changed: - display brightness not restored on next boot resets to 100 + systemd-backlight does not save&restore brightness for nvidia display -- 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/1840592 Title: systemd-backlight does not save and restore brightness for nvidia display Status in nvidia-graphics-drivers package in Ubuntu: New Status in nvidia-graphics-drivers-418 package in Ubuntu: New Status in nvidia-settings package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5% steps. However, after a reboot or after a shutdown, brightness level reverts to 100%. Please fix to is "remembers" the current brightness value at shutdown time, like in does Windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1840592/+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 1840592] Re: systemd-backlight does not save and restore brightness for nvidia display
** Summary changed: - systemd-backlight does not save&restore brightness for nvidia display + systemd-backlight does not save and restore brightness for nvidia display -- 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/1840592 Title: systemd-backlight does not save and restore brightness for nvidia display Status in nvidia-graphics-drivers package in Ubuntu: New Status in nvidia-graphics-drivers-418 package in Ubuntu: New Status in nvidia-settings package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5% steps. However, after a reboot or after a shutdown, brightness level reverts to 100%. Please fix to is "remembers" the current brightness value at shutdown time, like in does Windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1840592/+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 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox
This bug was fixed in the package ibus - 1.5.17-3ubuntu5 --- ibus (1.5.17-3ubuntu5) bionic; urgency=medium * debian/patches/ubuntu-password-discard-environment-variables.patch: - Added upstream patch which implements selective ignoring of processing inputs to password fields based on two new environment variables, IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS (LP: #1838358) -- Matthew Ruffell Thu, 01 Aug 2019 16:07:31 +1200 ** Changed in: ibus (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1838358 Title: Ibus causes gnome-shell to freeze when password fields are selected in Firefox Status in ibus package in Ubuntu: Fix Released Status in ibus source package in Bionic: Fix Released Bug description: [Impact] The following has been seen in a VMware Horizon VDI. I cannot reproduce this issue myself. When a user interacts with any password field in Firefox, gnome-shell and Firefox both freeze and the system becomes unusable. If you ssh into the system and terminate Firefox, gnome-shell unfreezes. This only happens when the environment variable GTK_IM_MODULE is set to "ibus". If you unset the variable, or change it to GTK_IM_MODULE=gtk-im-context-simple and then start Firefox, everything works as intended. This has been seen before with gnome-shell 3.28.4-0ubuntu18.04.1, ibus 1.5.17-3ubuntu4 and Firefox versions starting with 68.0+build3-0ubuntu0.18.04.1 Note: Chrome[ium] and other applications do not trigger it, and it cannot be reproduced in other desktop environments. This seems to be an interaction issue between ibus and gnome-shell. [Test Case] Launch firefox from within a gnome-session, making sure the GTK_IM_MODULE is set to "ibus". Note, this is the default value. $ env GTK_IM_MODULE="ibus" firefox Navigate to any website which has a password field. Wikipedia or Reddit will do. Click a password field and attempt to enter text. Firefox and gnome- shell both lock up and stay frozen for an extended period of time. Now, try it with the fix by enabling: $ env IBUS_DISCARD_PASSWORD=1 firefox When you enter text into a password field, ibus should directly pass through the text and the problem will be solved. We can also ask it to always apply for a specific application with: $ export IBUS_DISCARD_PASSWORD_APPS="firefox" $ firefox Again, when you enter text into a password input field, the problem will be solved. Test package is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf235370-test Please test with the revised version, 1.5.17-3ubuntu4+sf235370v20190731b1. [Regression Potential] This change has a low risk of regression, because the default behaviour is unchanged. To be able to use the password input field discard functionality, a user has to explicitly set an environment variable for the specific process, or set a regex that matches a process name. This means the fix is not enabled by default on any machines, and will only be utilised by those suffering problems and go and manually set environment variables or have their system administrator enable the environment variables permanently. This commit is present in upstream ibus from version ibus-1.5.19 onward, and is currently present in cosmic, disco and eoan. If a regression occurs, users can ensure that the environment variables are unset and continue working. [Other info] * This patch is functionally the same as ibus-xx-f19-password.patch, but just hides the features behind environment variables. * When ibus is built with the patch ibus-xx-f19-password.patch which was dropped in ibus-1.5.17-2, the problem is solved. Instead of using ibus-xx-f19-password.patch, we will instead fix it with upstream commit f328fd67f479faa46ca87bf3c85eed7080ec5ec0: https://github.com/ibus/ibus/commit/f328fd67f479faa46ca87bf3c85eed7080ec5ec0 Subject: client/gtk2: Add IBUS_DISCARD_PASSWORD for firefox and chrome Author: fujiwarat This implements the password discard functionality found in ibus-xx-f19-password.patch and places it behind two environment variables, IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS. IBUS_DISCARD_PASSWORD is for a single process, and IBUS_DISCARD_PASSWORD_APPS lets you set a regex of process names to filter and enable the fix for. If IBUS_DISCARD_PASSWORD is set or IBUS_DISCARD_PASSWORD_APPS is set with the process name which input is being placed into password fields, ibus will pass through the input to the application without any processing. * This only affect Bionic - Upstream first introduction: $ git describe --contains f328fd67f479faa46ca87bf3c85eed7080ec5ec0 1.5.19~7 - Ubuntu ibus current version found in t
[Touch-packages] [Bug 1838358] Update Released
The verification of the Stable Release Update for ibus has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1838358 Title: Ibus causes gnome-shell to freeze when password fields are selected in Firefox Status in ibus package in Ubuntu: Fix Released Status in ibus source package in Bionic: Fix Released Bug description: [Impact] The following has been seen in a VMware Horizon VDI. I cannot reproduce this issue myself. When a user interacts with any password field in Firefox, gnome-shell and Firefox both freeze and the system becomes unusable. If you ssh into the system and terminate Firefox, gnome-shell unfreezes. This only happens when the environment variable GTK_IM_MODULE is set to "ibus". If you unset the variable, or change it to GTK_IM_MODULE=gtk-im-context-simple and then start Firefox, everything works as intended. This has been seen before with gnome-shell 3.28.4-0ubuntu18.04.1, ibus 1.5.17-3ubuntu4 and Firefox versions starting with 68.0+build3-0ubuntu0.18.04.1 Note: Chrome[ium] and other applications do not trigger it, and it cannot be reproduced in other desktop environments. This seems to be an interaction issue between ibus and gnome-shell. [Test Case] Launch firefox from within a gnome-session, making sure the GTK_IM_MODULE is set to "ibus". Note, this is the default value. $ env GTK_IM_MODULE="ibus" firefox Navigate to any website which has a password field. Wikipedia or Reddit will do. Click a password field and attempt to enter text. Firefox and gnome- shell both lock up and stay frozen for an extended period of time. Now, try it with the fix by enabling: $ env IBUS_DISCARD_PASSWORD=1 firefox When you enter text into a password field, ibus should directly pass through the text and the problem will be solved. We can also ask it to always apply for a specific application with: $ export IBUS_DISCARD_PASSWORD_APPS="firefox" $ firefox Again, when you enter text into a password input field, the problem will be solved. Test package is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf235370-test Please test with the revised version, 1.5.17-3ubuntu4+sf235370v20190731b1. [Regression Potential] This change has a low risk of regression, because the default behaviour is unchanged. To be able to use the password input field discard functionality, a user has to explicitly set an environment variable for the specific process, or set a regex that matches a process name. This means the fix is not enabled by default on any machines, and will only be utilised by those suffering problems and go and manually set environment variables or have their system administrator enable the environment variables permanently. This commit is present in upstream ibus from version ibus-1.5.19 onward, and is currently present in cosmic, disco and eoan. If a regression occurs, users can ensure that the environment variables are unset and continue working. [Other info] * This patch is functionally the same as ibus-xx-f19-password.patch, but just hides the features behind environment variables. * When ibus is built with the patch ibus-xx-f19-password.patch which was dropped in ibus-1.5.17-2, the problem is solved. Instead of using ibus-xx-f19-password.patch, we will instead fix it with upstream commit f328fd67f479faa46ca87bf3c85eed7080ec5ec0: https://github.com/ibus/ibus/commit/f328fd67f479faa46ca87bf3c85eed7080ec5ec0 Subject: client/gtk2: Add IBUS_DISCARD_PASSWORD for firefox and chrome Author: fujiwarat This implements the password discard functionality found in ibus-xx-f19-password.patch and places it behind two environment variables, IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS. IBUS_DISCARD_PASSWORD is for a single process, and IBUS_DISCARD_PASSWORD_APPS lets you set a regex of process names to filter and enable the fix for. If IBUS_DISCARD_PASSWORD is set or IBUS_DISCARD_PASSWORD_APPS is set with the process name which input is being placed into password fields, ibus will pass through the input to the application without any processing. * This only affect Bionic - Upstream first introduction: $ git describe --contains f328fd67f479faa46ca87bf3c85eed7080ec5ec0 1.5.19~7 - Ubuntu ibus current version found in the archive: $ rmadison ibus ==> ibus | 1.5.17-3ubuntu4 | bionic ibus | 1.5
[Touch-packages] [Bug 1840699] [NEW] Caps-lock doesn't work correctly in Old Hungarian layout
Public bug reported: Xkeyboard-config's version 2.27 resolves this problem ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New ** Tags: xkb-data -- 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/1840699 Title: Caps-lock doesn't work correctly in Old Hungarian layout Status in xkeyboard-config package in Ubuntu: New Bug description: Xkeyboard-config's version 2.27 resolves this problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1840699/+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 1823157] Re: [19.10 FEAT] zlib compression improvements
** Information type changed from Private Security to Public ** Changed in: zlib (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1823157 Title: [19.10 FEAT] zlib compression improvements Status in Ubuntu on IBM z Systems: Triaged Status in zlib package in Ubuntu: Fix Committed Bug description: Compression improvements for Linux on z using zlib in support of better performance. Upstream post 2019-03-15: https://github.com/madler/zlib/pull/410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1823157/+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 892918] Re: Cannot start jack using qjackctrl via dbus when playback only option is needed
** Changed in: jackd2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/892918 Title: Cannot start jack using qjackctrl via dbus when playback only option is needed Status in jackd2 package in Ubuntu: Invalid Bug description: My audio hardware requires the playback only option to be specified to successfully start jackd. However I cannot start jackd with this option via qjackctrl unless dbus startup option is disabled. I am guessing that qjacktrl causes a dbus jackd with default parameters to be started (and stopped) before it tries to start the one with the playback only parameter. Starting a jackd without the playback only parameter always results in a server that hang and doe not respond to any client requests. Catch 22. Ubuntu 11.10 jackd2 1.9.7~dsfg-1ubuntu2 qjackctl 0.3.8-1 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: jackd2 1.9.7~dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Mon Nov 21 01:32:38 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: Upgraded to oneiric on 2011-10-15 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/892918/+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 1532431] Re: NetworkManager interferes with unmanaged 802.11 monitor mode interfaces
** Changed in: network-manager (Ubuntu) Status: New => Invalid -- 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/1532431 Title: NetworkManager interferes with unmanaged 802.11 monitor mode interfaces Status in network-manager package in Ubuntu: Invalid Bug description: If a virtual 802.11 interface of type monitor is created on a 802.11 physical interface that already has a virtual interface of type managed created on it, then the managed interface is deleted. NetworkManager sets the type of the monitor interface to managed. This can be illustrated by the following commands. All the interface names have been listed in /etc/network/interfaces as follows so NetworkManager should not be managing them in any way. # Disable network manager on interface names I want to use for monitoring # related purposes iface eth1 inet manual iface BigTenda inet manual iface LittleBelkin inet manual iface LittleTenda inet manual iface Sinmax inet manual iface mon0 inet manual iface phy0.mon manual iface phy1.mon manual iface phy2.mon manual iface phy3.mon manual iface phy4.mon manual iface phy5.mon manual iface phy6.mon manual iface phy7.mon manual iface phy8.mon manual iface phy9.mon manual root@dragon:/home/roger# systemctl start NetworkManager root@dragon:/home/roger# iw dev phy#3 Interface Sinmax ifindex 11 wdev 0x30001 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# iw phy phy3 interface add phy2.mon type monitor flags otherbss root@dragon:/home/roger# iw dev phy#3 Interface phy2.mon ifindex 12 wdev 0x30002 addr 00:0f:11:92:06:b2 type monitor Interface Sinmax ifindex 11 wdev 0x30001 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# iw dev Sinmax del root@dragon:/home/roger# iw dev phy#3 Interface phy2.mon ifindex 12 wdev 0x30002 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# systemctl stop NetworkManager root@dragon:/home/roger# iw dev phy#3 Interface phy2.mon ifindex 12 wdev 0x30002 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# # Unplug the netwaork adapter for a few seconds root@dragon:/home/roger# iw dev phy#4 Interface Sinmax ifindex 13 wdev 0x40001 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# iw phy phy4 interface add phy2.mon type monitor flags otherbss root@dragon:/home/roger# iw dev phy#4 Interface phy2.mon ifindex 14 wdev 0x40002 addr 00:0f:11:92:06:b2 type monitor Interface Sinmax ifindex 13 wdev 0x40001 addr 00:0f:11:92:06:b2 type managed root@dragon:/home/roger# iw dev Sinmax del root@dragon:/home/roger# iw dev phy#4 Interface phy2.mon ifindex 14 wdev 0x40002 addr 00:0f:11:92:06:b2 type monitor This stops any running or future network traces on this interface working. This is another example of network manager interfering with interfaces it is not supposed to be managing. See bug #1314848 which is still unresolved. The above test was carried out on Ubuntu 15.10 network-manager: Installed: 1.0.4-0ubuntu5.2 Candidate: 1.0.4-0ubuntu5.2 Version table: *** 1.0.4-0ubuntu5.2 0 500 http://gb.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.4-0ubuntu5 0 500 http://gb.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1532431/+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 1840532] Re: ubuntu-bug behaviour differs from that described on the page https://help.ubuntu.com/community/ReportingBugs
This is likely a duplicate of bug 1814611. What is the output of 'systemctl is-enabled whoopsie' and 'systemctl is-active whoopsie'? Thanks in advance. ** Changed in: apport (Ubuntu) Status: New => Incomplete -- 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/1840532 Title: ubuntu-bug behaviour differs from that described on the page https://help.ubuntu.com/community/ReportingBugs Status in apport package in Ubuntu: Incomplete Bug description: I run this application with the command line ubuntu-bug gnome-power-manager and then, I proceed as described in the section 'Complete the bug report filing process' on the page https://help.ubuntu.com/community/ReportingBugs till the message 'Uploading problem information' must appear, followed by 'Report a bug' page. Neither of the last two windows appear and the application terminates silently. Return code is 0. 1)$ lsb_release -rd Description: Ubuntu 19.04 Release: 19.04 2)$ apt-cache policy apport apport: Installed: 2.20.10-0ubuntu27.1 Candidate: 2.20.10-0ubuntu27.1 Version table: *** 2.20.10-0ubuntu27.1 500 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages 100 /var/lib/dpkg/status 2.20.10-0ubuntu27 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu disco/main i386 Packages 500 http://ua.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://ua.archive.ubuntu.com/ubuntu disco/main i386 Packages 3) Expected the page 'Report a bug' would appear. 4) Instead the application terminates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1840532/+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 218637] Re: Non-breaking space is easy to write accidentally and impossible to distinguish from regular space.
** Description changed: OS: from Hardy to at least Trusty. When you use Finnish keyboard, you have to hold Alt Gr down to type | or \ or certain other characters. When typing a shell command, you may often want to enter a space character after such characters. But it easily happens that Alt Gr is still down when you press space, and consequently you type non-breaking space character U+00A0 (at least, if you use UTF-8 keyboard layout, which is default in Ubuntu). $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar" ls: cannot access foo bar: No such file or directory $cat foo bar | grep 0 No command ' grep' found, but there are 16 similar ones grep: command not found Besides it may be hard to see the typing error, as non-breaking space character looks exactly same as regular space character. A way to avoid such typos would be to use another keyboard shortcut for non-breaking space. Besides non-breaking space should look different than regular space in terminal emulators and in editors. A workaround in to run setxkbmap -option "nbsp:none" - to make type regular space character, - and use `printf '\u00a0'` or `printf "\xc2\xa0"` to have a non-breaking space in scripts and in command line. + to make type regular space character. To make this default setting, you could add + + XKBOPTIONS="nbsp:none" + + in '/etc/default/keyboard'. + + Then use `printf '\u00a0'` or `printf "\xc2\xa0"` to have a non-breaking + space in scripts and in command line. Non-breaking space can be typed (in GTK apps) by u 00a0, if needed, but it looks exactly like a regular space. For me, would be a good shortcut for non-breaking space. -- 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/218637 Title: Non-breaking space is easy to write accidentally and impossible to distinguish from regular space. Status in Geany: New Status in gedit: New Status in GNOME Terminal: New Status in nano: New Status in xfce4-terminal: New Status in xorg package in Ubuntu: Invalid Bug description: OS: from Hardy to at least Trusty. When you use Finnish keyboard, you have to hold Alt Gr down to type | or \ or certain other characters. When typing a shell command, you may often want to enter a space character after such characters. But it easily happens that Alt Gr is still down when you press space, and consequently you type non-breaking space character U+00A0 (at least, if you use UTF-8 keyboard layout, which is default in Ubuntu). $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar" ls: cannot access foo bar: No such file or directory $cat foo bar | grep 0 No command ' grep' found, but there are 16 similar ones grep: command not found Besides it may be hard to see the typing error, as non-breaking space character looks exactly same as regular space character. A way to avoid such typos would be to use another keyboard shortcut for non-breaking space. Besides non-breaking space should look different than regular space in terminal emulators and in editors. A workaround in to run setxkbmap -option "nbsp:none" to make type regular space character. To make this default setting, you could add XKBOPTIONS="nbsp:none" in '/etc/default/keyboard'. Then use `printf '\u00a0'` or `printf "\xc2\xa0"` to have a non- breaking space in scripts and in command line. Non-breaking space can be typed (in GTK apps) by u 00a0, if needed, but it looks exactly like a regular space. For me, would be a good shortcut for non-breaking space. To manage notifications about this bug go to: https://bugs.launchpad.net/geany/+bug/218637/+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 1840699] Re: Caps-lock doesn't work correctly in Old Hungarian layout
Let's fix this one way or the other. Either an upgrade to 2.27, if that happens in Debian, or we could cherry pick the upstream commit which fixes it. ** Bug watch added: gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues #154 https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues/154 ** Also affects: xkeyboard-config via https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues/154 Importance: Unknown Status: Unknown ** Changed in: xkeyboard-config (Ubuntu) Importance: Undecided => Medium ** Changed in: xkeyboard-config (Ubuntu) Status: New => Triaged ** Changed in: xkeyboard-config (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- 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/1840699 Title: Caps-lock doesn't work correctly in Old Hungarian layout Status in xkeyboard-config: Unknown Status in xkeyboard-config package in Ubuntu: Triaged Bug description: Xkeyboard-config's version 2.27 resolves this problem To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1840699/+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 1691225] Re: hud-service trying to output error messages using ncurses colours to syslog
This issue still exists in version 14.10+17.10.20170619-0ubuntu. ** Changed in: hud (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1691225 Title: hud-service trying to output error messages using ncurses colours to syslog Status in hud package in Ubuntu: Confirmed Bug description: Wherever hud-service is failing, it's trying to print using ncurses colour tags (m#NNN[NN) where syslog is text-only. example error message: May 16 14:11:02 eva hud-service[1967]: #033[31mvoid DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m: "No such interface 'com.canonical.dbusmenu' on object at path /org/ayatana/bamf/window/75498803" what this error message should probably be: May 16 14:11:02 eva hud-service[1967]: void DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*): "No such interface 'com.canonical.dbusmenu' on object at path /org/ayatana/bamf/window/75498803" Ubuntu 17.04 zesty hud: 14.10+17.04.20170106.1-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: hud 14.10+17.04.20170106.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Tue May 16 14:10:55 2017 InstallationDate: Installed on 2017-04-18 (27 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: hud UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1691225/+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 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
I discovered that the Software & Updates application "Authentication" tab's "Remove" button does not work properly too. After pressing the "Remove" button, pkexec was called. After submitting the password for administration level, nothing happens, i.e. Trusted software keys that was selected for deletion do not get removed. Not error was shown in terminal. $ dpkg -l | grep software-properties ii python3-software-properties0.96.24.32.11 all manage the repositories that you install software from ii software-properties-common 0.96.24.32.11 all manage the repositories that you install software from (common) ii software-properties-gtk0.96.24.32.11 all manage the repositories that you install software from (gtk) I had filed a bug report (see https://bugs.launchpad.net/ubuntu/+source /software-properties/+bug/1840624). Should it fall under this bug report too and this bug report's title be amended to include the "Authentication" Tab? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+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 1799974] Re: [MIR] gupnp
I reviewed gupnp 1.2.1-1 as checked in to eoan. This isn't a full security audit, but rather a quick gauge of maintainability. - gupnp is a gobject based library for implementing and consuming UPnP services, and is required by Rygel. - It's part of the GNOME project. - It's written in C. - One CVE in our database from 2009 (a DoS). Doesn't affect current releases, although it doesn't look like it was fixed in Ubuntu before the affected releases went EoL. - Build-dependencies in main except for libgssdp-doc and libgssdp-1.2-dev (bug 1799977). Also gnome-pkg-tools, meson, valac, gtk-doc-tools, docbook-xml, docbook-xsl - none of these create binary dependencies. - No maintainer scripts - No init scripts / systemd units. - No dbus services. - No setuid binaries. - Only binary is gupnp-binding-tool-1.2 in libgupnp-1.2-dev - No sudo fragments. - No udev rules. - There's a few tests that seem to run in the build. - No cron jobs. - Build logs clean other than some documentation warnings. - Lintian clean - Doesn't spawn any subprocesses. - Memory management looks ok - there is a g_malloc in strip_camel_case that allocates memory based on a multiplication that isn't overflow safe, but the source of this isn't attacker controlled and I don't think it can overflow anyway. - The only file IO it seems to do is using glib's GMappedFile API, which is used for providing file contents to libsoup for hosting local files. See below for how paths are looked up. - Not much logging - a few g_debugs (not enabled by default) and some g_message calls. It doesn't look like anything sensitive is logged. - Reads a couple of variables from the environment - GUPNP_DEBUG and GUPNP_DEBUG_NETLINK. The first one enables logging to stdout of headers + request/response bodies in libsoup, and enables reporting of warnings and errors in libxml when loading local XML files. The second one enables the dumping of netlink packets to stdout. - Doesn't call any privileged commands. - No crypto. - Doesn't use temporary files. - GUPnPContext creates a HTTP server using libsoup. There is one GUPnPContext per network interface, created and managed by GUPnPContextManager. The availability of services is advertised via SSDP (using gssdp - GUPnPContext sub-classes GSSDPClient for this) - The default handler just returns 404. - It provides a simple API for hosting local paths for read access. The default libsoup handler (host_path_handler) for this supports directory listing and automatic redirection to index.html for paths to directories. This API is used by root device instances to host device and service XML descriptions. - host_path_handler() uses construct_local_path() to build a local file path, which just appends the request path to the handler's base path. It's relying on a feature of libsoup to not be vulnerable to path traversal attacks, which I've tested and seems to work. - GUPnPContext provides a mechanism to register handler functions for specific server paths, which is used by service instances to implement action handlers. I believe rygel also uses this for hosting media files. - It provides a mechanism for applications to implement ACLs by registering an ACL handler, which is called before server handler functions are executed. The ACL handler can make access control decisions based on source IP / source user agent and request path. - The 2 handlers registered by each service instance can be protected with ACLs. - The control handler function for each service instance (control_server_handler) parses the HTTP body with xmlRecoverMemory. This doesn't perform replacement of entity references with content by default, which is good. It converts requests to gobject signals which are delivered to application code, or returns a 401 if the request doesn't have a corresponding gobject signal handler. - A service instance provides a way for clients to subscribe to events (via subscription_server_handler). A subscription is referenced by a SID, which is a uuid created by uuid_generate(). The SID is used in order to unsubscibe and provided in the event notification headers. Subscriptions timeout and are automatically removed after 5 minutes, unless the client resubscribes with the same SID. - The subscribe() handler calls gupnp_context_rewrite_url() on each callback URL, which are provided by the requesting client device. This function extracts the host from the URL, constructs a GInetAddress instance by calling g_inet_address_new_from_string() with this host string and then calls g_inet_address_get_is_link_local() without any null check. Won't g_inet_address_new_from_string() fail if the host isn't a valid IPV4 or IPV6 address though? - The default GUPnPContextManager implementation uses NETLINK_ROUTE for observing network interface changes to manage GUPnPContext instances. There is a network manager implementation, but it doesn't look like it's built. - No webkit. - No policykit. - N
[Touch-packages] [Bug 1840725] [NEW] Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Public bug reported: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: alsa internal-mic ubuntu18.04.4lts ** Tags added: internal mic ** Tags added: alsa ubuntu18.04.4lts ** Tags removed: internal mic ** Tags added: internal-mic -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: New Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Probably on this machine, the internal mic is connected to pin 0x13. -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: New Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Pin 0x13 does not work as well. Overriding pin 0x13 to use the Internal Mic causes an undesirable side-effect of static noise in any plugged in headphone. -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: New Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1823157] Re: [19.10 FEAT] zlib compression improvements
** Changed in: ubuntu-z-systems Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1823157 Title: [19.10 FEAT] zlib compression improvements Status in Ubuntu on IBM z Systems: Fix Committed Status in zlib package in Ubuntu: Fix Committed Bug description: Compression improvements for Linux on z using zlib in support of better performance. Upstream post 2019-03-15: https://github.com/madler/zlib/pull/410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1823157/+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
