[Bug 1971978] Re: Driver binaries fail to load on arm64 through LXD
The same problem can be reproduced with the sbsa 510 driver from the NVIDIA CUDA repository (see https://developer.nvidia.com/cuda- downloads?target_os=Linux_arch=arm64-sbsa=Native=Ubuntu_version=22.04_type=deb_network) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971978 Title: Driver binaries fail to load on arm64 through LXD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1971978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971978] Re: Driver binaries fail to load on arm64 through LXD
> Separately i'm failing to get even as far as the bug description gets > as i get failures on missing newuidmap binary and what not: The log looks exactly like what you should see. The error about missing newuidmap/newgidmap is expected as LXD writes the uidmap for the container directly and doesn't use the two tools to do that. The first two errors is what we look for: lxc evident-oyster 20220509154201.271 ERROR conf - conf.c:run_buffer:321 - Script exited with status 1 lxc evident-oyster 20220509154201.271 ERROR conf - conf.c:lxc_setup:4400 - Failed to run mount hooks Any error following after this is just a consequence of the start process failing here. If you have the NVIDIA drivers installed, as Stephane mentions, and also set $ lxc config set c0 raw.lxc lxc.log.level=0 you will get the error as given in the description. If you don't enable trace logging you will always remain with just lxc evident-oyster 20220509154201.271 ERROR conf - conf.c:lxc_setup:4400 - Failed to run mount hooks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971978 Title: Driver binaries fail to load on arm64 through LXD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1971978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971978] Re: Driver binaries fail to load on arm64 through LXD
The LXD snap itself isn't the problem. It only includes the nvidia- container-cli utility (see https://github.com/NVIDIA/libnvidia- container) which works as expected but fails to map to the driver binaries from the host into the container environment due to the incompatible symbols. This way you make e.g. bionic LXD containers work with the host NVIDIA driver binaries from jammy. This works well with the instructions given above on amd64 on Ubuntu 22.04 with the same 510 driver from the archive. For whatever reason the arm64 binaries are different though and depend on symbols not available in < 22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971978 Title: Driver binaries fail to load on arm64 through LXD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1971978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971978] [NEW] Driver binaries fail to load on arm64 through LXD
Public bug reported: On a fresh arm64 system I failed to start LXD containers with NVIDIA GPUs attached. The error message LXD / nvidia-container-cli fails with is: lxc t0 20220506112123.475 DEBUGconf - conf.c:run_buffer:310 - Script exec /snap/lxd/current/lxc/hooks/nvidia produced output: + exec nvidia-container-cli --user configure --no-cgroups --ldconfig=@/usr/sbin/ldconfig.real --compute --utility --require= --require= /var/snap/lxd/common/lxc/ lxc t0 20220506112123.492 DEBUGconf - conf.c:run_buffer:310 - Script exec /snap/lxd/current/lxc/hooks/nvidia produced output: nvidia-container-cli.real: initialization error: load library failed: /lib/aarch64-linux-gnu/libc.so.6: version `glibc_2.35' not found (required by /lib/aarch64-linux-gnu/libgcc_s.so.1) This seems to be related to how the aarch64 driver is linked and cannot be reproduced on amd64 on Ubuntu 22.04 with the same packages installed as on arm64. The error message indicates it's not nvidia-container-cli failing to start but rather a dependency it fails to load due to missing symbols in the core20 libc the LXD snap uses. Steps to reproduce: 1. Setup a fresh Ubuntu 22.04 arm64 system with an NVIDIA GPU attached 2. Install the 510 driver from the archive $ sudo apt install nvidia-utils-510 linux-modules-nvidia-510-generic libnvidia-compute-510 --purge 3. Create a container and configure it $ lxc init ubuntu:f c0 # Adjust the PCI address to match your GPU $ lxc config device add c0 gpu gpu pci=:01:00.0 $ lxc config set c0 nvidia.runtime=true # Make logs a bit more verbose $ lxc config set c0 raw.lxc lxc.log.level=0 4. Now start the container and see it failing $ lxc start c0 Error: Failed to run: /snap/lxd/current/bin/lxd forkstart c0 /var/snap/lxd/common/lxd/containers /var/snap/lxd/common/lxd/logs/c0/lxc.conf: Try `lxc info --show-log c0` for more info 5. Check logs and see the error mentioned above: $ lxc info --show-log c0 ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971978 Title: Driver binaries fail to load on arm64 through LXD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1971978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968027] Re: shiftfs breaks paths in /proc/*/maps
** Description changed: # Overview When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps within a container: root@anbox0:~# cat /proc/self/maps 55930e60-55930e608000 r-xp 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930e807000-55930e808000 r--p 7000 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930e808000-55930e809000 rw-p 8000 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930fd3c000-55930fd5d000 rw-p 00:00 0 [heap] 7fe736be2000-7fe736dc9000 r-xp 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736dc9000-7fe736fc9000 ---p 001e7000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fc9000-7fe736fcd000 r--p 001e7000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fcd000-7fe736fcf000 rw-p 001eb000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fcf000-7fe736fd3000 rw-p 00:00 0 7fe736fd3000-7fe736ffc000 r-xp 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371ba000-7fe7371de000 rw-p 00:00 0 7fe7371fc000-7fe7371fd000 r--p 00029000 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371fd000-7fe7371fe000 rw-p 0002a000 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371fe000-7fe7371ff000 rw-p 00:00 0 7ffcd50a-7ffcd50c1000 rw-p 00:00 0 [stack] 7ffcd51d2000-7ffcd51d6000 r--p 00:00 0 [vvar] 7ffcd51d6000-7ffcd51d8000 r-xp 00:00 0 [vdso] ff60-ff601000 --xp 00:00 0 [vsyscall] When shiftfs is disabled the paths look all correct and are relative to the root of the container root@anbox0:~# cat /proc/self/maps 557aaa20-557aaa208000 r-xp 00:48 14509 /bin/cat 557aaa407000-557aaa408000 r--p 7000 00:48 14509 /bin/cat 557aaa408000-557aaa409000 rw-p 8000 00:48 14509 /bin/cat 557aabaa5000-557aabac6000 rw-p 00:00 0 [heap] 7f4820526000-7f482070d000 r-xp 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f482070d000-7f482090d000 ---p 001e7000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f482090d000-7f4820911000 r--p 001e7000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f4820911000-7f4820913000 rw-p 001eb000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f4820913000-7f4820917000 rw-p 00:00 0 7f4820917000-7f482094 r-xp 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820afe000-7f4820b22000 rw-p 00:00 0 7f4820b4-7f4820b41000 r--p 00029000 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820b41000-7f4820b42000 rw-p 0002a000 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820b42000-7f4820b43000 rw-p 00:00 0 7ffd12ead000-7ffd12ece000 rw-p 00:00 0 [stack] 7ffd12fd8000-7ffd12fdc000 r--p 00:00 0 [vvar] 7ffd12fdc000-7ffd12fde000 r-xp 00:00 0 [vdso] ff60-ff601000 --xp 00:00 0 [vsyscall] To reproduce: 1. Use Ubuntu 20.04 or newer inluding shiftfs 2. Install LXD (4.0.x is good enough) and enable shiftfs support $ snap install lxd $ snap set lxd shiftfs.enable=true $ snap restart lxd $ lxd init --auto 3. Start a container and check /proc/self/maps $ lxc launch ubuntu:f test0 $ lxc exec test0 -- cat /proc/self/maps 4. Turn shiftfs back off $ snap set lxd shiftfs.enable=false $ snap restart lxd 5. Check /proc/self/maps again inside the container $ lxc exec test0 -- cat /proc/self/maps This can be reproduced with both the 5.4 and 5.13 kernels on Ubuntu - 20.04 and also with 5.15 on a fresh jammy installation + 20.04 and also with 5.15 on a fresh jammy installation with a ZFS + storage pool #
[Bug 1968077] [NEW] NVIDIA driver crashes with kernel NULL pointer dereference
Public bug reported: After leaving the system for a while and it turning the screen off the kernel crashes in the NVIDIA driver with the following: Apr 06 17:24:56 kore kernel: BUG: kernel NULL pointer dereference, address: 0070 Apr 06 17:24:56 kore kernel: #PF: supervisor read access in kernel mode Apr 06 17:24:56 kore kernel: #PF: error_code(0x) - not-present page Apr 06 17:24:56 kore kernel: PGD 0 P4D 0 Apr 06 17:24:56 kore kernel: Oops: [#1] SMP PTI Apr 06 17:24:56 kore kernel: CPU: 3 PID: 286160 Comm: Xorg Tainted: P C O 5.15.0-25-generic #25-Ubuntu Apr 06 17:24:56 kore kernel: Hardware name: Dell Inc. XPS 8930/0H0P0M, BIOS 1.1.15 07/01/2020 Apr 06 17:24:56 kore kernel: RIP: 0010:_nv002531kms+0x18/0x70 [nvidia_modeset] Apr 06 17:24:56 kore kernel: Code: ff c6 44 24 2f 01 eb af 66 2e 0f 1f 84 00 00 00 00 00 41 54 55 49 89 fc 53 89 d5 41 b8 04 00 00 00 ba 02 01 02 00 48 83 ec 10 <8b> 46 70 8b 3d 6f bb 0b 00 48 8d 4c 24 0c 89 ee 89 44 24 0c e8 6f Apr 06 17:24:56 kore kernel: RSP: 0018:bb9412827c90 EFLAGS: 00010286 Apr 06 17:24:56 kore kernel: RAX: RBX: 2002 RCX: 9ec1417f3980 Apr 06 17:24:56 kore kernel: RDX: 00020102 RSI: RDI: 9ec163d33008 Apr 06 17:24:56 kore kernel: RBP: 00010009 R08: 0004 R09: Apr 06 17:24:56 kore kernel: R10: 9ec5f1bd3000 R11: R12: 9ec163d33008 Apr 06 17:24:56 kore kernel: R13: 9ec163d330a0 R14: 0fff R15: 00010008 Apr 06 17:24:56 kore kernel: FS: 7f560151ea80() GS:9ec8a0ac() knlGS: Apr 06 17:24:56 kore kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 06 17:24:56 kore kernel: CR2: 0070 CR3: 0001ed208001 CR4: 003726e0 Apr 06 17:24:56 kore kernel: Call Trace: Apr 06 17:24:56 kore kernel: Apr 06 17:24:56 kore kernel: ? _nv002530kms+0xb3/0x150 [nvidia_modeset] Apr 06 17:24:56 kore kernel: ? _nv002308kms+0x499/0x680 [nvidia_modeset] Apr 06 17:24:56 kore kernel: ? _nv000453kms+0xa0/0xa0 [nvidia_modeset] Apr 06 17:24:56 kore kernel: ? _copy_from_user+0x2e/0x60 Apr 06 17:24:56 kore kernel: ? _nv000453kms+0xa0/0xa0 [nvidia_modeset] Apr 06 17:24:56 kore kernel: ? _nv000639kms+0x34/0x50 [nvidia_modeset] Apr 06 17:24:56 kore kernel: ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset] Apr 06 17:24:56 kore kernel: ? nvkms_ioctl+0x104/0x170 [nvidia_modeset] Apr 06 17:24:56 kore kernel: ? nvidia_frontend_unlocked_ioctl+0x58/0x90 [nvidia] Apr 06 17:24:56 kore kernel: ? __x64_sys_ioctl+0x91/0xc0 Apr 06 17:24:56 kore kernel: ? do_syscall_64+0x5c/0xc0 Apr 06 17:24:56 kore kernel: ? do_syscall_64+0x69/0xc0 Apr 06 17:24:56 kore kernel: ? syscall_exit_to_user_mode+0x27/0x50 Apr 06 17:24:56 kore kernel: ? do_syscall_64+0x69/0xc0 Apr 06 17:24:56 kore kernel: ? do_syscall_64+0x69/0xc0 Apr 06 17:24:56 kore kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xae I can reliable reproduce this on my current jammy system (proposed enabled, no pending updates) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-510 510.60.02-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 6 19:47:32 2022 InstallationDate: Installed on 2022-01-02 (94 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nvidia-graphics-drivers-510 UpgradeStatus: Upgraded to jammy on 2022-03-23 (13 days ago) ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968077 Title: NVIDIA driver crashes with kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1968077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968027] Re: shiftfs breaks paths in /proc/*/maps
** Description changed: When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps within a container: root@anbox0:~# cat /proc/self/maps 55930e60-55930e608000 r-xp 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930e807000-55930e808000 r--p 7000 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930e808000-55930e809000 rw-p 8000 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930fd3c000-55930fd5d000 rw-p 00:00 0 [heap] 7fe736be2000-7fe736dc9000 r-xp 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736dc9000-7fe736fc9000 ---p 001e7000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fc9000-7fe736fcd000 r--p 001e7000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fcd000-7fe736fcf000 rw-p 001eb000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fcf000-7fe736fd3000 rw-p 00:00 0 7fe736fd3000-7fe736ffc000 r-xp 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371ba000-7fe7371de000 rw-p 00:00 0 7fe7371fc000-7fe7371fd000 r--p 00029000 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371fd000-7fe7371fe000 rw-p 0002a000 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371fe000-7fe7371ff000 rw-p 00:00 0 7ffcd50a-7ffcd50c1000 rw-p 00:00 0 [stack] 7ffcd51d2000-7ffcd51d6000 r--p 00:00 0 [vvar] 7ffcd51d6000-7ffcd51d8000 r-xp 00:00 0 [vdso] ff60-ff601000 --xp 00:00 0 [vsyscall] When shiftfs is disabled the paths look all correct and are relative to the root of the container root@anbox0:~# cat /proc/self/maps 557aaa20-557aaa208000 r-xp 00:48 14509 /bin/cat 557aaa407000-557aaa408000 r--p 7000 00:48 14509 /bin/cat 557aaa408000-557aaa409000 rw-p 8000 00:48 14509 /bin/cat 557aabaa5000-557aabac6000 rw-p 00:00 0 [heap] 7f4820526000-7f482070d000 r-xp 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f482070d000-7f482090d000 ---p 001e7000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f482090d000-7f4820911000 r--p 001e7000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f4820911000-7f4820913000 rw-p 001eb000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f4820913000-7f4820917000 rw-p 00:00 0 7f4820917000-7f482094 r-xp 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820afe000-7f4820b22000 rw-p 00:00 0 7f4820b4-7f4820b41000 r--p 00029000 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820b41000-7f4820b42000 rw-p 0002a000 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820b42000-7f4820b43000 rw-p 00:00 0 7ffd12ead000-7ffd12ece000 rw-p 00:00 0 [stack] 7ffd12fd8000-7ffd12fdc000 r--p 00:00 0 [vvar] 7ffd12fdc000-7ffd12fde000 r-xp 00:00 0 [vdso] ff60-ff601000 --xp 00:00 0 [vsyscall] To reproduce: 1. Use Ubuntu 20.04 or newer inluding shiftfs 2. Install LXD (4.0.x is good enough) and enable shiftfs support $ snap install lxd $ snap set lxd shiftfs.enable=true $ snap restart lxd $ lxd init --auto 3. Start a container and check /proc/self/maps $ lxc launch ubuntu:f test0 $ lxc exec test0 -- cat /proc/self/maps 4. Turn shiftfs back off $ snap set lxd shiftfs.enable=false $ snap restart lxd 5. Check /proc/self/maps again inside the container $ lxc exec test0 -- cat /proc/self/maps This can be reproduced with both the 5.4 and 5.13 kernels on Ubuntu - 20.04 + 20.04 and also with 5.15 on a fresh jammy installation ** Description changed: + # Overview + When enabling shiftfs for LXD we get incorrect paths
[Bug 1968027] Re: shiftfs breaks paths in /proc/*/maps
Attaching logs fails when `apport-collect 1968027` wants to authorized with my LP with an "Not allowed error". ** Description changed: When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps within a container: root@anbox0:~# cat /proc/self/maps 55930e60-55930e608000 r-xp 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930e807000-55930e808000 r--p 7000 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930e808000-55930e809000 rw-p 8000 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930fd3c000-55930fd5d000 rw-p 00:00 0 [heap] 7fe736be2000-7fe736dc9000 r-xp 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736dc9000-7fe736fc9000 ---p 001e7000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fc9000-7fe736fcd000 r--p 001e7000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fcd000-7fe736fcf000 rw-p 001eb000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so - 7fe736fcf000-7fe736fd3000 rw-p 00:00 0 + 7fe736fcf000-7fe736fd3000 rw-p 00:00 0 7fe736fd3000-7fe736ffc000 r-xp 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so - 7fe7371ba000-7fe7371de000 rw-p 00:00 0 + 7fe7371ba000-7fe7371de000 rw-p 00:00 0 7fe7371fc000-7fe7371fd000 r--p 00029000 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371fd000-7fe7371fe000 rw-p 0002a000 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so - 7fe7371fe000-7fe7371ff000 rw-p 00:00 0 + 7fe7371fe000-7fe7371ff000 rw-p 00:00 0 7ffcd50a-7ffcd50c1000 rw-p 00:00 0 [stack] 7ffcd51d2000-7ffcd51d6000 r--p 00:00 0 [vvar] 7ffcd51d6000-7ffcd51d8000 r-xp 00:00 0 [vdso] ff60-ff601000 --xp 00:00 0 [vsyscall] When shiftfs is disabled the paths look all correct and are relative to the root of the container root@anbox0:~# cat /proc/self/maps 557aaa20-557aaa208000 r-xp 00:48 14509 /bin/cat 557aaa407000-557aaa408000 r--p 7000 00:48 14509 /bin/cat 557aaa408000-557aaa409000 rw-p 8000 00:48 14509 /bin/cat 557aabaa5000-557aabac6000 rw-p 00:00 0 [heap] 7f4820526000-7f482070d000 r-xp 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f482070d000-7f482090d000 ---p 001e7000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f482090d000-7f4820911000 r--p 001e7000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f4820911000-7f4820913000 rw-p 001eb000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so - 7f4820913000-7f4820917000 rw-p 00:00 0 + 7f4820913000-7f4820917000 rw-p 00:00 0 7f4820917000-7f482094 r-xp 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so - 7f4820afe000-7f4820b22000 rw-p 00:00 0 + 7f4820afe000-7f4820b22000 rw-p 00:00 0 7f4820b4-7f4820b41000 r--p 00029000 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820b41000-7f4820b42000 rw-p 0002a000 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so - 7f4820b42000-7f4820b43000 rw-p 00:00 0 + 7f4820b42000-7f4820b43000 rw-p 00:00 0 7ffd12ead000-7ffd12ece000 rw-p 00:00 0 [stack] 7ffd12fd8000-7ffd12fdc000 r--p 00:00 0 [vvar] 7ffd12fdc000-7ffd12fde000 r-xp 00:00 0 [vdso] ff60-ff601000 --xp 00:00 0 [vsyscall] - To reproduce: 1. Use Ubuntu 20.04 or newer inluding shiftfs 2. Install LXD (4.0.x is good enough) and enable shiftfs support $ snap install lxd $ snap set lxd shiftfs.enable=true $ snap restart lxd $ lxd init --auto 3. Start a container and check /proc/self/maps $ lxc launch ubuntu:f test0 $ lxc exec test0 -- cat /proc/self/maps 4.
[Bug 1968027] [NEW] shiftfs breaks paths in /proc/*/maps
Public bug reported: When enabling shiftfs for LXD we get incorrect paths in /proc/*/maps within a container: root@anbox0:~# cat /proc/self/maps 55930e60-55930e608000 r-xp 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930e807000-55930e808000 r--p 7000 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930e808000-55930e809000 rw-p 8000 00:51 14509 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/bin/cat 55930fd3c000-55930fd5d000 rw-p 00:00 0 [heap] 7fe736be2000-7fe736dc9000 r-xp 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736dc9000-7fe736fc9000 ---p 001e7000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fc9000-7fe736fcd000 r--p 001e7000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fcd000-7fe736fcf000 rw-p 001eb000 00:51 14226 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/libc-2.27.so 7fe736fcf000-7fe736fd3000 rw-p 00:00 0 7fe736fd3000-7fe736ffc000 r-xp 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371ba000-7fe7371de000 rw-p 00:00 0 7fe7371fc000-7fe7371fd000 r--p 00029000 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371fd000-7fe7371fe000 rw-p 0002a000 00:51 14139 /var/snap/lxd/common/lxd/storage-pools/default/containers/anbox0/rootfs/lib/x86_64-linux-gnu/ld-2.27.so 7fe7371fe000-7fe7371ff000 rw-p 00:00 0 7ffcd50a-7ffcd50c1000 rw-p 00:00 0 [stack] 7ffcd51d2000-7ffcd51d6000 r--p 00:00 0 [vvar] 7ffcd51d6000-7ffcd51d8000 r-xp 00:00 0 [vdso] ff60-ff601000 --xp 00:00 0 [vsyscall] When shiftfs is disabled the paths look all correct and are relative to the root of the container root@anbox0:~# cat /proc/self/maps 557aaa20-557aaa208000 r-xp 00:48 14509 /bin/cat 557aaa407000-557aaa408000 r--p 7000 00:48 14509 /bin/cat 557aaa408000-557aaa409000 rw-p 8000 00:48 14509 /bin/cat 557aabaa5000-557aabac6000 rw-p 00:00 0 [heap] 7f4820526000-7f482070d000 r-xp 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f482070d000-7f482090d000 ---p 001e7000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f482090d000-7f4820911000 r--p 001e7000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f4820911000-7f4820913000 rw-p 001eb000 00:48 14226 /lib/x86_64-linux-gnu/libc-2.27.so 7f4820913000-7f4820917000 rw-p 00:00 0 7f4820917000-7f482094 r-xp 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820afe000-7f4820b22000 rw-p 00:00 0 7f4820b4-7f4820b41000 r--p 00029000 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820b41000-7f4820b42000 rw-p 0002a000 00:48 14139 /lib/x86_64-linux-gnu/ld-2.27.so 7f4820b42000-7f4820b43000 rw-p 00:00 0 7ffd12ead000-7ffd12ece000 rw-p 00:00 0 [stack] 7ffd12fd8000-7ffd12fdc000 r--p 00:00 0 [vvar] 7ffd12fdc000-7ffd12fde000 r-xp 00:00 0 [vdso] ff60-ff601000 --xp 00:00 0 [vsyscall] To reproduce: 1. Use Ubuntu 20.04 or newer inluding shiftfs 2. Install LXD (4.0.x is good enough) and enable shiftfs support $ snap install lxd $ snap set lxd shiftfs.enable=true $ snap restart lxd $ lxd init --auto 3. Start a container and check /proc/self/maps $ lxc launch ubuntu:f test0 $ lxc exec test0 -- cat /proc/self/maps 4. Turn shiftfs back off $ snap set lxd shiftfs.enable=false $ snap restart lxd 5. Check /proc/self/maps again inside the container $ lxc exec test0 -- cat /proc/self/maps ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968027 Title: shiftfs breaks paths in /proc/*/maps To manage notifications about this bug go to:
[Bug 1964636] Re: Incorrect handling of apparmor `bpf` capability
I can easily reproduce with stgraber's instructions on an arm64 VM
running 20.04 with the 5.4 kernel.
Maciej asked me to provide the output of the following commands:
in the LXD container:
root@c1:~# echo 'profile snap-test { capability bpf, }' | apparmor_parser
--preprocess ; echo $?
Warning from stdin (line 1): apparmor_parser: Warning capping number of jobs to
0 * # of cpus == '16'AppArmor parser error, in stdin line 1: Invalid capability
bpf.
0
on the host:
ubuntu@anbox-streaming-stack-0:~$ echo 'profile snap-test { capability bpf, }'
| apparmor_parser --preprocess ; echo $?
AppArmor parser error, in stdin line 1: Invalid capability bpf.
profile snap-test { capability bpf1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964636
Title:
Incorrect handling of apparmor `bpf` capability
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1964636/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964636] Re: Incorrect handling of apparmor `bpf` capability
We start seeing the same behavior in the Anbox Cloud CI for a few days now. What tests (via spread) primarily do: 1. ssh to an existing arm64 VM 2. Install a fresh LXD from latest/edge and configure it with the following preseed (setting security.nesting to true or false doesn't make a difference): ``` config: cluster.https_address: $addr:8443 core.https_address: $addr:8443 cluster: enabled: false server_name: lxd0 networks: - name: lxdbr0 type: bridge config: ipv4.nat: true ipv4.dhcp.expiry: infinite ipv4.address: $LXD_SUBNET ipv6.address: none profiles: - name: default config: security.nesting: true devices: root: path: / pool: default type: disk eth0: type: nic nictype: bridged parent: lxdbr0 storage_pools: - name: default driver: zfs config: size: 20GB ``` 3. Now juju starts to bootstrap a controller on top of LXD and then we deploy our charms. 4. At some point the tests run the following: 11:08:00 timeout -s KILL 5m sudo -u root -H /snap/bin/juju ssh ams/0 -o 'ConnectionAttempts 30' -- /snap/bin/amc image add bionic:android10:arm64 /home/ubuntu/anbox-lxd-image.tar.xz 11:08:00 snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks This seems to be consis11:08:00 timeout -s KILL 5m sudo -u root -H /snap/bin/juju ssh ams/0 -o 'ConnectionAttempts 30' -- /snap/bin/amc image add bionic:android10:arm64 /home/ubuntu/anbox-lxd-image.tar.xz 11:08:00 snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks This doesn't always happen but I haven't yet checked if it's only happening on one particular machine. The VMs are all running 20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964636 Title: Incorrect handling of apparmor `bpf` capability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1964636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939301] Re: REGRESSION: shiftfs lets sendfile fail with EINVAL
I can confirm that running the HWE kernel 5.11.0-27-generic #29~20.04.1-Ubuntu from proposed on our Ubuntu 20.04 test system resolves the problem. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939301 Title: REGRESSION: shiftfs lets sendfile fail with EINVAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939301] Re: REGRESSION: shiftfs lets sendfile fail with EINVAL
I've verified on my end that with the patch from https://paste.ubuntu.com/p/TPsjfCpnD5/ the failing sendfile syscall on top of shiftfs is gone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939301 Title: REGRESSION: shiftfs lets sendfile fail with EINVAL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939301] [NEW] REGRESSION: shiftfs lets sendfile fail with EINVAL
Public bug reported:
With the 5.11 HWE kernel landing for Ubuntu 20.04 we noticed that LXC
tools we're using in bionic containers as part of Anbox Cloud start to
fail when executed on the 5.11 kernel.
A simple reproducer looks like this:
1. Run Ubuntu 20.04 with HWE kernel (linux-generic-hwe-20.04, 5.11.0-25-generic
#27~20.04.1-Ubuntu)
2. Install LXD and enable shiftfs
$ snap install lxd
$ snap set lxd shiftfs.enable true
$ snap restart --reload lxd
3. Launch bionic container and run `lxc-info`
$ lxc launch ubuntu:b c0
$ lxc shell c0
c0$ apt update
c0$ apt install -y lxc-utils
root@c1:~# apt show lxc-utils | grep Version
Version: 3.0.3-0ubuntu1~18.04.1
c0$ mkdir -p containers/test
c0$ touch containers/test/config
c0$ lxc-info -P containers -n test
Failed to load config for test
Failure to retrieve information on containers:test
Looking into the failing `lxc-info` call with strace reveals:
...
memfd_create(".lxc_config_file", MFD_CLOEXEC) = 4
openat(AT_FDCWD, "containers/test/config", O_RDONLY|O_CLOEXEC) = 5
sendfile(4, 5, NULL, 2147479552)= -1 EINVAL (Invalid argument
...
LXC >= 4.0.0 doesn't use sendfile anymore and with that isn't affected.
Any other tool using sendfile however is affected and will fail. Bionic
is affected as the 3.0.3 version of LXC it includes still uses sendfile.
Disabling shiftfs makes things work again and can be considered as a
workaround to a certain degree, but not be applicable in all cases.
Further analysis with Christian (cbrauner) from the LXD team this
morning showed that shiftfs is missing an implementation for the now
required slice_read handler in the file_operations structure. So
whenever shiftfs is being used, all calls to sendfile will fail because
of the missing implementation. The generic handler for this got removed
in the following upstream change:
https://lore.kernel.org/lkml/20200626075836.1998185-10-...@lst.de/
Christian implemented a quick fix:
https://paste.ubuntu.com/p/TPsjfCpnD5/
As of today I don't know of any customer of Anbox Cloud who is affected
by this as most of them run with one of our cloud kernels. However as
soon as 5.11 rolls out to the cloud kernels, we will hit production
systems and cause them to fail.
** Affects: linux-meta-hwe-5.11 (Ubuntu)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939301
Title:
REGRESSION: shiftfs lets sendfile fail with EINVAL
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.11/+bug/1939301/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925246] Re: binderfs support is not enabled
** Tags added: anbox-cloud -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925246 Title: binderfs support is not enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1925246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937987] Re: Latest GCP kernel has Android related config options disabled
** Tags added: anbox-cloud -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937987 Title: Latest GCP kernel has Android related config options disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1937987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937987] [NEW] Latest GCP kernel has Android related config options disabled
Public bug reported: In LP:1849493 we enabled support for CONFIG_ANDROID_* on the gcp kernels to support Anbox Cloud. However checking on the latest rolling kernel on GCP (5.8.0-1038-gcp #40~20.04.1-Ubuntu ) gives morphis@anbox0:~$ cat /boot/config-5.8.0-1038-gcp | grep CONFIG_AND # CONFIG_ANDROID is not set This is a regression and already affects customers of Anbox Cloud which intend to deploy on GCP and currently fail as the binder and ashmem kernel modules are missing. From the git history I wasn't able to figure out where the options got dropped. The following options are what we need CONFIG_ANDROID=y CONFIG_ANDROID_BINDER_IPC=m CONFIG_ANDROID_BINDERFS=m CONFIG_ANDROID_BINDER_DEVICES="" # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set CONFIG_ASHMEM=m These options should be set by default in all our cloud kernels, regardless which Ubuntu version. Can we get some regression testing in place for this too? Thanks! ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937987 Title: Latest GCP kernel has Android related config options disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1937987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928686] Re: Oracle kernel has Android related config options disabled
No, 4.15 isn't needed. We only need 5.4+ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928686 Title: Oracle kernel has Android related config options disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1928686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928686] [NEW] Oracle kernel has Android related config options disabled
Public bug reported: For Anbox Cloud we require certain CONFIG_ANDROID_* options to be enabled in the kernel. We do this already for most of our cloud kernels (GCE, AWS, Azure) and the generic kernel and should do so for the oracle (and possible others too). We have customers looking at running Anbox Cloud on OCI instances and having the ashmem and binder kernel modules available is a precondition for this to work. The following options are what we need CONFIG_ANDROID=y CONFIG_ANDROID_BINDER_IPC=m CONFIG_ANDROID_BINDERFS=m CONFIG_ANDROID_BINDER_DEVICES="" # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set CONFIG_ASHMEM=m These should be the same across all our kernels where we're going to support Anbox Cloud. ** Affects: linux-oracle (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928686 Title: Oracle kernel has Android related config options disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1928686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922599] Re: fails to create a new context
Yes, it's fixed with 460.73.01-0ubuntu0.20.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922599 Title: fails to create a new context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1922599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922599] Re: fails to create a new context
Executing a cudaDeviceSynchronize() instead of using cuCtxCreate gives "all CUDA-capable devices are busy or unavailable" which seems to hint to something incorrectly setup in the system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922599 Title: fails to create a new context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1922599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922599] Re: fails to create a new context
I can reproduce this here on the focal 5.4 kernel (5.4.0-72-generic) with 460.32.03 (deb 460.32.03-0ubuntu0.20.04.2) too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922599 Title: fails to create a new context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1922599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925246] [NEW] binderfs support is not enabled
Public bug reported: Hey, in https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1914568 we got binder support enabled but the configuration is completely different from what we have in our other cloud and generic kernels: ubuntu@machine-1:~$ cat /boot/config-5.4.0-1046-azure | grep BINDER CONFIG_ANDROID_BINDER_IPC=m # CONFIG_ANDROID_BINDERFS is not set CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder" # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set $ cat /boot/config-5.4.0-14-generic | grep BINDER CONFIG_ANDROID_BINDER_IPC=m CONFIG_ANDROID_BINDERFS=m CONFIG_ANDROID_BINDER_DEVICES="" # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set Not having binderfs support is breaking Anbox Cloud support. What is the reason for not having the config aligned between the kernels here? Thanks! ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925246 Title: binderfs support is not enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1925246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914568] [NEW] Azure kernel for focal misses binder and ashmem kernel modules
Public bug reported: For the purpose of Anbox Cloud we package both the binder and ashmem kernel modules in the Ubuntu kernel. The generic kernel ships it and all clouds specific kernels should too. However the azure kernel doesn't include the prebuilt binder_linux.ko and ashmem_linux.ko modules: ubuntu@ac0:~$ uname -r 5.4.0-1039-azure ubuntu@ac0:~$ dpkg -L linux-modules-extra-5.4.0-1039-azure | grep binder ubuntu@ac0:~$ dpkg -L linux-modules-extra-5.4.0-1039-azure | grep ashmem Can we please get both kernel modules added to azure kernel and at the same time double check that the modules are packaged in all other cloud kernels? Thanks! ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914568 Title: Azure kernel for focal misses binder and ashmem kernel modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1914568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884149] Re: haproxy crashes on in __pool_get_first if unique-id-header is used
I've just applied the package from https://launchpad.net/ubuntu/+source/haproxy/1.8.8-1ubuntu0.11 to our deployment and the crash is fixed. I will keep it running for a while to see if it remains that way. Thanks for all the work! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884149 Title: haproxy crashes on in __pool_get_first if unique-id-header is used To manage notifications about this bug go to: https://bugs.launchpad.net/haproxy/+bug/1884149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884149] Re: haproxy crashes on in __pool_get_first if unique-id-header is used
Thanks Christian! Will give the PPA a go tomorrow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884149 Title: haproxy crashes on in __pool_get_first if unique-id-header is used To manage notifications about this bug go to: https://bugs.launchpad.net/haproxy/+bug/1884149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884149] Re: haproxy crashes on in __pool_get_first if unique-id-header is used
Just ran through the bisect: git bisect start '--term-new=fixed' '--term-old=unfixed' # fixed: [ebf033b47d58aa04ae9913038c9369dab8740411] [RELEASE] Released version 1.8.19 git bisect fixed ebf033b47d58aa04ae9913038c9369dab8740411 # unfixed: [cd117685f0cff4f2f5577ef6a21eaae96ebd9f28] [RELEASE] Released version 1.8.8 git bisect unfixed cd117685f0cff4f2f5577ef6a21eaae96ebd9f28 # fixed: [88c166870a779985d50f6a2cf840c844bc9b64da] BUG/MINOR: tools: fix set_net_port() / set_host_port() on IPv4 git bisect fixed 88c166870a779985d50f6a2cf840c844bc9b64da # unfixed: [fdc6c62dbebf4b646b4f80c383e3b00f34b0440f] MINOR: systemd: consider exit status 143 as successful git bisect unfixed fdc6c62dbebf4b646b4f80c383e3b00f34b0440f # unfixed: [ad84851746243d85f9be59703e9bee0f5c5f8eba] BUG/MEDIUM: threads: fix the double CAS implementation for ARMv7 git bisect unfixed ad84851746243d85f9be59703e9bee0f5c5f8eba # fixed: [d9a130e1962c2a5352f33088c563f4248a102c48] BUG/MEDIUM: mux_pt: dereference the connection with care in mux_pt_wake() git bisect fixed d9a130e1962c2a5352f33088c563f4248a102c48 # unfixed: [a1110e24e5be53ba5fe9ab82372c02a60da06cf9] BUG/MINOR: map: fix map_regm with backref git bisect unfixed a1110e24e5be53ba5fe9ab82372c02a60da06cf9 # unfixed: [3c42f13badd149c9c3152d7b2e653bde5da7c17a] BUG/MEDIUM: cli/threads: protect all "proxy" commands against concurrent updates git bisect unfixed 3c42f13badd149c9c3152d7b2e653bde5da7c17a # unfixed: [d13cb1516cb5ae4cb8322ed630e1d4e1f584fd77] DOC: Fix spelling error in configuration doc git bisect unfixed d13cb1516cb5ae4cb8322ed630e1d4e1f584fd77 # unfixed: [5b58c92dc9357a87aa3fe94c8121f683feb9c80e] BUG/MINOR: lua: Bad HTTP client request duration. git bisect unfixed 5b58c92dc9357a87aa3fe94c8121f683feb9c80e # first fixed commit: [d9a130e1962c2a5352f33088c563f4248a102c48] BUG/MEDIUM: mux_pt: dereference the connection with care in mux_pt_wake() Cherry picking the identified commit (d9a130e1962c2a5352f33088c563f4248a102c48) on top of 1.8.8 makes things work. I will keep it running for a bit longer and see if it stays stable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884149 Title: haproxy crashes on in __pool_get_first if unique-id-header is used To manage notifications about this bug go to: https://bugs.launchpad.net/haproxy/+bug/1884149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884149] Re: haproxy crashes on in __pool_get_first if unique-id-header is used
Thanks Christian! I was planing to bisect today as I still have the environment up and can easily reproduce. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884149 Title: haproxy crashes on in __pool_get_first if unique-id-header is used To manage notifications about this bug go to: https://bugs.launchpad.net/haproxy/+bug/1884149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884149] [NEW] haproxy crashes on arm64 in __pool_get_first
Public bug reported: Version 1.8.8-1ubuntu0.10 of haproxy in Ubuntu 18.04 (bionic) crashes with Thread 2.1 "haproxy" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xf77b1010 (LWP 17174)] __pool_get_first (pool=0xaac6ddd0, pool=0xaac6ddd0) at include/common/memory.h:124 124 include/common/memory.h: No such file or directory. (gdb) bt #0 __pool_get_first (pool=0xaac6ddd0, pool=0xaac6ddd0) at include/common/memory.h:124 #1 pool_alloc_dirty (pool=0xaac6ddd0) at include/common/memory.h:154 #2 pool_alloc (pool=0xaac6ddd0) at include/common/memory.h:229 #3 conn_new () at include/proto/connection.h:655 #4 cs_new (conn=0x0) at include/proto/connection.h:683 #5 connect_conn_chk (t=0xaacb8820) at src/checks.c:1553 #6 process_chk_conn (t=0xaacb8820) at src/checks.c:2135 #7 process_chk (t=0xaacb8820) at src/checks.c:2281 #8 0xaabca0b4 in process_runnable_tasks () at src/task.c:231 #9 0xaab76f44 in run_poll_loop () at src/haproxy.c:2399 #10 run_thread_poll_loop (data=) at src/haproxy.c:2461 #11 0xaaad79ec in main (argc=, argv=0xaac61b30) at src/haproxy.c:3050 when running on an ARM64 system. The haproxy.cfg looks like this: global log /dev/log local0 log /dev/log local1 notice maxconn 4096 user haproxy group haproxy spread-checks 0 tune.ssl.default-dh-param 1024 ssl-default-bind-ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:!DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:!DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:!CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA defaults log global mode tcp option httplog option dontlognull retries 3 timeout queue 2 timeout client 5 timeout connect 5000 timeout server 5 frontend anbox-stream-gateway-lb-5-80 bind 0.0.0.0:80 default_backend api_http mode http http-request redirect scheme https backend api_http mode http frontend anbox-stream-gateway-lb-5-443 bind 0.0.0.0:443 ssl crt /var/lib/haproxy/default.pem no-sslv3 default_backend app-anbox-stream-gateway mode http backend app-anbox-stream-gateway mode http balance leastconn server anbox-stream-gateway-0-4000 10.212.218.61:4000 check ssl verify none inter 2000 rise 2 fall 5 maxconn 4096 server anbox-stream-gateway-1-4000 10.212.218.93:4000 check ssl verify none inter 2000 rise 2 fall 5 maxconn 4096 server anbox-stream-gateway-2-4000 10.212.218.144:4000 check ssl verify none inter 2000 rise 2 fall 5 maxconn 4096 The crash occurs after a first few HTTP requests going through and happens again when systemd restarts the service. The bug is already reported in Debian https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=921981 and upstream at https://github.com/haproxy/haproxy/issues/40 Using the 1.8.19-1+deb10u2 package from Debian fixes the crash. ** Affects: haproxy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884149 Title: haproxy crashes on arm64 in __pool_get_first To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1884149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876165] [NEW] Binder and ashmem drivers are missing from aws-edge kernel
Public bug reported: For quite a while the Ubuntu kernel now ships the Ashmem and Binder drivers as part of linux-modules-extra-*. They were available on previous linux-aws kernels but seem to have dropped with the 5.3.0 based edge kernel. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849493 for a similar bug report I filed in the past for the GCP kernels. Can we get both ashmem and binder enabled and added to linux-aws-edge as they are used for Anbox Cloud? ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876165 Title: Binder and ashmem drivers are missing from aws-edge kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1876165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849493] Re: CONFIG_ANDROID_BINDER_IPC=m is missing in the custom rolling kernels
Just checked on my bionic GCE instance today that the binder driver is now there: ubuntu@juju-1dfb8c-4:~$ find /lib | grep binder /lib/modules/5.0.0-1025-gcp/kernel/drivers/android/binder_linux.ko Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849493 Title: CONFIG_ANDROID_BINDER_IPC=m is missing in the custom rolling kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849493] [NEW] CONFIG_ANDROID_BINDER_IPC=m is missing in the GCP rolling kernel for bionic
Public bug reported: The rolling GCP kernel for bionic is missing CONFIG_ANDROID_BINDER_IPC=m which is enabled in the standard Ubuntu kernel since 19.04 and available through the HWE kernels in Bionic. As we require CONFIG_ANDROID_BINDER_IPC=m for a not released product in our kernels it would be great if we can import the relevant config changes to the GCP kernel (haven't yet checked our other cloud kernels). All relevant changes from Christian Brauner to enable binder in the Ubuntu kernel are present in the GCP kernel (see https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux- gcp/+git/bionic/log/?h=gcp-edge=grep=brauner). See https://kernel.ubuntu.com/git/ubuntu/ubuntu- bionic.git/commit/debian.master/config/config.common.ubuntu?h=hwe=a758aeb0bb0f52ccbee99f850709c57711753b33 and https://kernel.ubuntu.com/git/ubuntu/ubuntu- bionic.git/commit/debian.master/config/config.common.ubuntu?h=hwe=4b44b695fb5ee2f405d0ad4eda2fc2cad856414c for the relevant config changes in the Ubuntu kernel from Seth. ** Affects: linux (Ubuntu) Importance: High Assignee: Khaled El Mously (kmously) Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849493 Title: CONFIG_ANDROID_BINDER_IPC=m is missing in the GCP rolling kernel for bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1689539] Re: Pulseaudio "Access Denied" on Fedora 25 with Awesome WM as desktop environment
** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) ** Changed in: snapd (Ubuntu) Importance: Undecided => High ** Also affects: snapd (Fedora) Importance: Undecided Status: New ** Changed in: snapd (Fedora) Assignee: (unassigned) => Simon Fels (morphis) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1689539 Title: Pulseaudio "Access Denied" on Fedora 25 with Awesome WM as desktop environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1689539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674509] Re: Unable to find bluetooth device on RPi3 running Ubuntu Core 16
Btw. you guys should see if the more modern btattach utility does the job instead of hciattach too. See http://manpages.ubuntu.com/manpages/xenial/man1/btattach.1.html for a few details. Sooner or later btattach will replace hciattach as the way to attach serial lines to the kernel bluetooth stack. btattach is much smarter as it only sets the line discipline for a serial port and leaves everything else up to the kernel. Only supporting btattach would simply the whole implementation as we just have to provide a serial port plug on the bluez snap the user can plug any serial port to and then (via interface hooks) the bluez snap will figure out what to do with it, without having to know anything device specific. The relevant UART options (speed, noflow, vendor protocol) should be all specified via the connecting slot. Can we set arbitrary attributes on a slot definition and implement with that our own meta data needed for such a thing? Something like this would be possible then: gadget: bt-serial: interface: serial-port path: /dev/ttyUSB0 speed: 115200 flow-control: false hci-uart-protocol: h4 The plug side in the bluez could then just figure out everything on its own by inspecting the attributes of the connecting slot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674509 Title: Unable to find bluetooth device on RPi3 running Ubuntu Core 16 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1674509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680030] Re: Snap plugin for gnome-software misses self tests
** Summary changed: - Snap plug for gnome-software misses self tests + Snap plugin for gnome-software misses self tests -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680030 Title: Snap plugin for gnome-software misses self tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1680030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680030] [NEW] Snap plug for gnome-software misses self tests
Public bug reported: The snap plugin implemented in gnome-software upstream does not have any self tests yet which were requested by upstream to get the plugin into a better shape. Tested with latest gnome-software from https://git.gnome.org/browse /gnome-software/ on Ubuntu 17.04 against snapd 2.23.6 ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: cross-distro ** Tags added: cross-distro ** Description changed: The snap plugin implemented in gnome-software upstream does not have any self tests yet which were requested by upstream to get the plugin into a better shape. + + Tested with latest gnome-software from https://git.gnome.org/browse + /gnome-software/ on Ubuntu 17.04 against snapd 2.23.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680030 Title: Snap plug for gnome-software misses self tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1680030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680027] Re: gnome-software doesn't use snapd-glib exclusively
** Description changed: The code submitted to gnome-software upstream still doesn't use snapd- glib exclusively but has parts of the snapd REST API which are handled by its own. The HTTP REST API logic should be only implemented once and that in snapd-glib. See https://git.gnome.org/browse/gnome- software/tree/plugins/snap/gs-snapd.c + Tested with latest gnome-software from https://git.gnome.org/browse + /gnome-software/ on Ubuntu 17.04 against snapd 2.23.6 + This blocks enablement of snap support in gnome-software on Fedora. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680027 Title: gnome-software doesn't use snapd-glib exclusively To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1680027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680033] [NEW] Snap searches are often canceled
Public bug reported: Searching for specific snaps (e.g. rocket, wifi-ap or network-manager) through the UI is often canceled internally. Logs print: 11:16:42:0596 Gs failed to get search apps: Operation was cancelled 11:16:42:0596 Gs not handling error cancelled for action search: Operation was cancelled 11:16:42:0596 GsPluginSnap begin snapd request: GET /v2/find?q=network-m HTTP/1.1 Host: Authorization: Macaroon root="XXX" 11:16:43:0679 Gs failed to call gs_plugin_add_search on snap: Operation was cancelled Tested with latest gnome-software from https://git.gnome.org/browse /gnome-software/ on Ubuntu 17.04 against snapd 2.23.6 This blocks enablement of snap support in gnome-software on Fedora. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: cross-distro ** Description changed: Searching for specific snaps (e.g. rocket, wifi-ap or network-manager) through the UI is often canceled internally. Logs print: 11:16:42:0596 Gs failed to get search apps: Operation was cancelled 11:16:42:0596 Gs not handling error cancelled for action search: Operation was cancelled 11:16:42:0596 GsPluginSnap begin snapd request: GET /v2/find?q=network-m HTTP/1.1 Host: Authorization: Macaroon root="XXX" 11:16:43:0679 Gs failed to call gs_plugin_add_search on snap: Operation was cancelled + Tested with latest gnome-software from https://git.gnome.org/browse + /gnome-software/ on Ubuntu 17.04 against snapd 2.23.6 + This blocks enablement of snap support in gnome-software on Fedora. ** Tags added: cross-distro -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680033 Title: Snap searches are often canceled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1680033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679774] Re: snapd-glib doesn't read full json response from snapd
** Changed in: gnome-software (Ubuntu) Status: New => Confirmed ** Tags added: cross-distro -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679774 Title: snapd-glib doesn't read full json response from snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1679774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680027] [NEW] gnome-software doesn't use snapd-glib exclusively
Public bug reported: The code submitted to gnome-software upstream still doesn't use snapd- glib exclusively but has parts of the snapd REST API which are handled by its own. The HTTP REST API logic should be only implemented once and that in snapd-glib. See https://git.gnome.org/browse/gnome- software/tree/plugins/snap/gs-snapd.c This blocks enablement of snap support in gnome-software on Fedora. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: cross-distro ** Tags added: cross-distro ** Description changed: The code submitted to gnome-software upstream still doesn't use snapd- glib exclusively but has parts of the snapd REST API which are handled by its own. The HTTP REST API logic should be only implemented once and that in snapd-glib. See https://git.gnome.org/browse/gnome- software/tree/plugins/snap/gs-snapd.c + + This blocks enablement of snap support in gnome-software on Fedora. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680027 Title: gnome-software doesn't use snapd-glib exclusively To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1680027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679774] Re: snapd-glib doesn't read full json response from snapd
As an additional note, this happens with snapd 2.23.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679774 Title: snapd-glib doesn't read full json response from snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1679774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679774] Re: snapd-glib doesn't read full json response from snapd
See https://paste.ubuntu.com/24318397/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679774 Title: snapd-glib doesn't read full json response from snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1679774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674509] Re: Unable to find bluetooth device on RPi3 running Ubuntu Core 16
** Changed in: linux-raspi2 (Ubuntu) Status: New => Confirmed ** Changed in: snappy Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674509 Title: Unable to find bluetooth device on RPi3 running Ubuntu Core 16 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1674509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528173] Re: org.freedesktop.DBus.Properties.GetAll fails always for fi.w1.wpa_supplicant1.Interface interface
** Changed in: wpa (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528173 Title: org.freedesktop.DBus.Properties.GetAll fails always for fi.w1.wpa_supplicant1.Interface interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1528173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662866] Re: libhybris blocks migration to libglvnd
** Changed in: libhybris (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662866 Title: libhybris blocks migration to libglvnd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhybris/+bug/1662866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638537] Re: snapd eats 100% CPU for about 5 minutes on first boot causing a load of >2.0
I see this as well on various arm based devices. Any more ideas what could be the reason or a possible fix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638537 Title: snapd eats 100% CPU for about 5 minutes on first boot causing a load of >2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1638537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647168] Re: /dev/ashmem and /dev/binder not usable inside confinement
** Description changed: I have a snap which starts an entire Android system in a LXC container similar to how we do it on Ubuntu Touch. The LXC container itself works fine in devmode, confinement is not yet considered and left completely aside. The Android system needs access to the two nodes /dev/ashmem and /dev/binder from the host system. They are both available in the snap execution environment and are bind mounted into the LXC container environment. Inside the container both nodes are accessible and can be used. However certain mmap calls to memory allocated via /dev/ashmem fail with a permission denied error and also binder IPC calls fail. These problems are not occurring when the LXC container is started outside of the snap execution environment, so it can be already ruled out as a problem here. The container configuration is also the same. The problem can be fixed by executing the container management process via $ aa-exec -p unconfined -- $SNAP/bin/container-manager which then uses liblxc to start the container. I don't really understand why this is required as AppArmor shouldn't prevent any use of /dev/ashmem or /dev/binder when the snap is installed with --devmode and dmesg doesn't show any denials, just that it allows all calls. + This is with snap-confine 1.0.43 on Ubuntu 16.04 + I am opening this bug here to start tracking the problem and get some more visibility and thoughts from others. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647168 Title: /dev/ashmem and /dev/binder not usable inside confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snap-confine/+bug/1647168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647168] [NEW] /dev/ashmem and /dev/binder not usable inside confinement
Public bug reported: I have a snap which starts an entire Android system in a LXC container similar to how we do it on Ubuntu Touch. The LXC container itself works fine in devmode, confinement is not yet considered and left completely aside. The Android system needs access to the two nodes /dev/ashmem and /dev/binder from the host system. They are both available in the snap execution environment and are bind mounted into the LXC container environment. Inside the container both nodes are accessible and can be used. However certain mmap calls to memory allocated via /dev/ashmem fail with a permission denied error and also binder IPC calls fail. These problems are not occurring when the LXC container is started outside of the snap execution environment, so it can be already ruled out as a problem here. The container configuration is also the same. The problem can be fixed by executing the container management process via $ aa-exec -p unconfined -- $SNAP/bin/container-manager which then uses liblxc to start the container. I don't really understand why this is required as AppArmor shouldn't prevent any use of /dev/ashmem or /dev/binder when the snap is installed with --devmode and dmesg doesn't show any denials, just that it allows all calls. I am opening this bug here to start tracking the problem and get some more visibility and thoughts from others. ** Affects: snap-confine (Ubuntu) Importance: Undecided Status: New ** Description changed: I have a snap which starts an entire Android system in a LXC container similar to how we do it on Ubuntu Touch. The LXC container itself works fine in devmode, confinement is not yet considered and left completely aside. The Android system needs access to the two nodes /dev/ashmem and /dev/binder from the host system. They are both available in the snap execution environment and are bind mounted into the LXC container environment. Inside the container both nodes are accessible and can be used. However certain mmap calls to memory allocated via /dev/ashmem fail with a permission denied error and also binder IPC calls fail. These problems are not occurring when the LXC container is started outside of the snap execution environment, so it can be already ruled out as a problem here. The container configuration is also the same. The problem can be fixed by executing the container management process via $ aa-exec -p unconfined -- $SNAP/bin/container-manager which then uses liblxc to start the container. I don't really understand why this is required as AppArmor shouldn't prevent any use of /dev/ashmem or /dev/binder when the snap is installed - with --devmode. + with --devmode and dmesg doesn't show any denials, just that it allows + all calls. I am opening this bug here to start tracking the problem and get some more visibility and thoughts from others. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647168 Title: /dev/ashmem and /dev/binder not usable inside confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snap-confine/+bug/1647168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611638] Re: snap upgrade hook
@Kyle: How is that supposed to work? Will there be an additional flag passed to the snap when the configure hook is called to indicate its called because of 'install' or 'upgrade' operations? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611638 Title: snap upgrade hook To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1611638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626617] Re: console-conf does not allow to set up dns for static ip
** Tags added: plano-acan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626617 Title: console-conf does not allow to set up dns for static ip To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1626617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634540] Re: Configuring a static IP address generates a netplan file without a gateway
** Tags added: plano-acan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634540 Title: Configuring a static IP address generates a netplan file without a gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1634540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634540] Re: Configuring a static IP address generates a netplan file without a gateway
** Changed in: subiquity (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634540 Title: Configuring a static IP address generates a netplan file without a gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1634540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634430] Re: Probert crashes with "oundLocalError: local variable 'ifindex' referenced before assignment"
0.0.11~xenial just landed in the ubuntu image ppa (https://launchpad.net /~snappy- dev/+archive/ubuntu/image/+packages?field.name_filter=_filter=published_filter=xenial) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634430 Title: Probert crashes with "oundLocalError: local variable 'ifindex' referenced before assignment" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/probert/+bug/1634430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634430] Re: Probert crashes with "oundLocalError: local variable 'ifindex' referenced before assignment"
PR is https://github.com/CanonicalLtd/probert/pull/30 ** Changed in: probert (Ubuntu) Assignee: (unassigned) => Scott Sweeny (ssweeny) ** Changed in: probert (Ubuntu) Importance: Undecided => Critical ** Changed in: probert (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634430 Title: Probert crashes with "oundLocalError: local variable 'ifindex' referenced before assignment" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/probert/+bug/1634430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634430] Re: Probert crashes with "oundLocalError: local variable 'ifindex' referenced before assignment"
** Description changed:
Probert currently crashes with the following:
2016-10-18 08:14:56,241 subiquitycore.core:159 Exception in controller.run():
Traceback (most recent call last):
- File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 376, in _run
- self.event_loop.run()
- File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 1015, in run
- raise exc
- File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 1002, in
wrapper
- return func(*args, **kw)
- File "/usr/lib/python3/dist-packages/urwid/raw_display.py", line 393, in
- event_loop, callback, self.get_available_raw_input())
- File "/usr/lib/python3/dist-packages/urwid/raw_display.py", line 493, in
parse_input
- callback(processed, processed_codes)
- File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 403, in
_update
- self.process_input(keys)
- File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 503, in
process_input
- k = self._topmost_widget.keypress(self.screen_size, k)
- File "/usr/share/subiquity/subiquitycore/ui/frame.py", line 38, in keypress
- return super().keypress(size, key)
- File "/usr/lib/python3/dist-packages/urwid/container.py", line 1128, in
keypress
- return self.body.keypress( (maxcol, remaining), key )
- File "/usr/share/subiquity/subiquitycore/view.py", line 32, in keypress
- return super().keypress(size, key)
- File "/usr/lib/python3/dist-packages/urwid/listbox.py", line 985, in
keypress
- key = focus_widget.keypress((maxcol,),key)
- File "/usr/lib/python3/dist-packages/urwid/decoration.py", line 621, in
keypress
- return self._original_widget.keypress(maxvals, key)
- File "/usr/lib/python3/dist-packages/urwid/container.py", line 1587, in
keypress
- key = self.focus.keypress(tsize, key)
- File "/usr/lib/python3/dist-packages/urwid/wimp.py", line 535, in keypress
- self._emit('click')
- File "/usr/lib/python3/dist-packages/urwid/widget.py", line 463, in _emit
- signals.emit_signal(self, name, self, *args)
- File "/usr/lib/python3/dist-packages/urwid/signals.py", line 264, in emit
- result |= self._call_callback(callback, user_arg, user_args, args)
- File "/usr/lib/python3/dist-packages/urwid/signals.py", line 294, in
_call_callback
- return bool(callback(*args_to_pass))
- File "/usr/share/subiquity/console_conf/ui/views/welcome.py", line 39, in
confirm
- self.signal.emit_signal('welcome:done')
- File "/usr/share/subiquity/subiquitycore/signals.py", line 88, in
emit_signal
- urwid.emit_signal(self, name, *args, **kwargs)
- File "/usr/lib/python3/dist-packages/urwid/signals.py", line 264, in emit
- result |= self._call_callback(callback, user_arg, user_args, args)
- File "/usr/lib/python3/dist-packages/urwid/signals.py", line 294, in
_call_callback
- return bool(callback(*args_to_pass))
- File "/usr/share/subiquity/subiquitycore/controllers/welcome.py", line 43,
in done
- self.signal.emit_signal('next-screen')
- File "/usr/share/subiquity/subiquitycore/signals.py", line 88, in
emit_signal
- urwid.emit_signal(self, name, *args, **kwargs)
- File "/usr/lib/python3/dist-packages/urwid/signals.py", line 264, in emit
- result |= self._call_callback(callback, user_arg, user_args, args)
- File "/usr/lib/python3/dist-packages/urwid/signals.py", line 294, in
_call_callback
- return bool(callback(*args_to_pass))
- File "/usr/share/subiquity/subiquitycore/core.py", line 93, in next_screen
- next_controller.default()
- File "/usr/share/subiquity/subiquitycore/controllers/network.py", line 206,
in default
- self.model.probe_network()
- File "/usr/share/subiquity/subiquitycore/models/network.py", line 331, in
probe_network
- self.prober.probe()
- File "/usr/share/subiquity/subiquitycore/prober.py", line 58, in probe
- results = network.probe()
- File "/usr/lib/python3/dist-packages/probert/network.py", line 593, in probe
- sources[netifaces.AF_INET].append(self._get_ip_source(iface,
ip[netifaces.AF_INET][i]))
- File "/usr/lib/python3/dist-packages/probert/network.py", line 528, in
_get_ip_source
- dhcp = self._get_dhcp(ifname)
- File "/usr/lib/python3/dist-packages/probert/network.py", line 496, in
_get_dhcp
- lease = self._get_dhcp_lease(ifname)
- File "/usr/lib/python3/dist-packages/probert/network.py", line 482, in
_get_dhcp_lease
- for lease in self._get_dhcp_leases():
- File "/usr/lib/python3/dist-packages/probert/network.py", line 450, in
_get_dhcp_leases
- nm_lease["interface"] = socket.if_indextoname(int(ifindex))
+ File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 376, in _run
+ self.event_loop.run()
+ File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 1015, in run
+ raise exc
+ File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 1002, in
wrapper
+ return func(*args, **kw)
+ File
[Bug 1634430] [NEW] Probert crashes with "oundLocalError: local variable 'ifindex' referenced before assignment"
Public bug reported:
Probert currently crashes with the following:
2016-10-18 08:14:56,241 subiquitycore.core:159 Exception in controller.run():
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 376, in _run
self.event_loop.run()
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 1015, in run
raise exc
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 1002, in
wrapper
return func(*args, **kw)
File "/usr/lib/python3/dist-packages/urwid/raw_display.py", line 393, in
event_loop, callback, self.get_available_raw_input())
File "/usr/lib/python3/dist-packages/urwid/raw_display.py", line 493, in
parse_input
callback(processed, processed_codes)
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 403, in _update
self.process_input(keys)
File "/usr/lib/python3/dist-packages/urwid/main_loop.py", line 503, in
process_input
k = self._topmost_widget.keypress(self.screen_size, k)
File "/usr/share/subiquity/subiquitycore/ui/frame.py", line 38, in keypress
return super().keypress(size, key)
File "/usr/lib/python3/dist-packages/urwid/container.py", line 1128, in
keypress
return self.body.keypress( (maxcol, remaining), key )
File "/usr/share/subiquity/subiquitycore/view.py", line 32, in keypress
return super().keypress(size, key)
File "/usr/lib/python3/dist-packages/urwid/listbox.py", line 985, in keypress
key = focus_widget.keypress((maxcol,),key)
File "/usr/lib/python3/dist-packages/urwid/decoration.py", line 621, in
keypress
return self._original_widget.keypress(maxvals, key)
File "/usr/lib/python3/dist-packages/urwid/container.py", line 1587, in
keypress
key = self.focus.keypress(tsize, key)
File "/usr/lib/python3/dist-packages/urwid/wimp.py", line 535, in keypress
self._emit('click')
File "/usr/lib/python3/dist-packages/urwid/widget.py", line 463, in _emit
signals.emit_signal(self, name, self, *args)
File "/usr/lib/python3/dist-packages/urwid/signals.py", line 264, in emit
result |= self._call_callback(callback, user_arg, user_args, args)
File "/usr/lib/python3/dist-packages/urwid/signals.py", line 294, in
_call_callback
return bool(callback(*args_to_pass))
File "/usr/share/subiquity/console_conf/ui/views/welcome.py", line 39, in
confirm
self.signal.emit_signal('welcome:done')
File "/usr/share/subiquity/subiquitycore/signals.py", line 88, in emit_signal
urwid.emit_signal(self, name, *args, **kwargs)
File "/usr/lib/python3/dist-packages/urwid/signals.py", line 264, in emit
result |= self._call_callback(callback, user_arg, user_args, args)
File "/usr/lib/python3/dist-packages/urwid/signals.py", line 294, in
_call_callback
return bool(callback(*args_to_pass))
File "/usr/share/subiquity/subiquitycore/controllers/welcome.py", line 43, in
done
self.signal.emit_signal('next-screen')
File "/usr/share/subiquity/subiquitycore/signals.py", line 88, in emit_signal
urwid.emit_signal(self, name, *args, **kwargs)
File "/usr/lib/python3/dist-packages/urwid/signals.py", line 264, in emit
result |= self._call_callback(callback, user_arg, user_args, args)
File "/usr/lib/python3/dist-packages/urwid/signals.py", line 294, in
_call_callback
return bool(callback(*args_to_pass))
File "/usr/share/subiquity/subiquitycore/core.py", line 93, in next_screen
next_controller.default()
File "/usr/share/subiquity/subiquitycore/controllers/network.py", line 206,
in default
self.model.probe_network()
File "/usr/share/subiquity/subiquitycore/models/network.py", line 331, in
probe_network
self.prober.probe()
File "/usr/share/subiquity/subiquitycore/prober.py", line 58, in probe
results = network.probe()
File "/usr/lib/python3/dist-packages/probert/network.py", line 593, in probe
sources[netifaces.AF_INET].append(self._get_ip_source(iface,
ip[netifaces.AF_INET][i]))
File "/usr/lib/python3/dist-packages/probert/network.py", line 528, in
_get_ip_source
dhcp = self._get_dhcp(ifname)
File "/usr/lib/python3/dist-packages/probert/network.py", line 496, in
_get_dhcp
lease = self._get_dhcp_lease(ifname)
File "/usr/lib/python3/dist-packages/probert/network.py", line 482, in
_get_dhcp_lease
for lease in self._get_dhcp_leases():
File "/usr/lib/python3/dist-packages/probert/network.py", line 450, in
_get_dhcp_leases
nm_lease["interface"] = socket.if_indextoname(int(ifindex))
UnboundLocalError: local variable 'ifindex' referenced before assignment
This is with network-manager taking control over the whole network
management rather than networkd.
Steps to reproduce:
1. Enter console-conf
2. Configure DHCP for ethernet and hit the done button
3. Once network is configured and you're on the sign-on page hit the "cancel"
button which takes you back into the terminal where you have to hit enter to
start console-conf again.
4. Hit enter and see console-conf crashing
[Bug 1634430] Re: Probert crashes with "oundLocalError: local variable 'ifindex' referenced before assignment"
** Attachment added: "subiquity-debug.log" https://bugs.launchpad.net/ubuntu/+source/probert/+bug/1634430/+attachment/4763099/+files/subiquity-debug.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634430 Title: Probert crashes with "oundLocalError: local variable 'ifindex' referenced before assignment" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/probert/+bug/1634430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630586] Re: Pi3 kernel crash and is unreliable
@Paolo: Will give this image a try tomorrow morning. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630586 Title: Pi3 kernel crash and is unreliable To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1630586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630586] Re: Pi3 kernel crash and is unreliable
** Attachment added: "IMG_20161005_153003.jpg" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1630586/+attachment/4755051/+files/IMG_20161005_153003.jpg ** Description changed: Build an image today with - $ sudo ubuntu-image --channel edge -o pi3.img pi3.model - $ cat pi3.model + $ sudo ubuntu-image --channel edge -o pi3.img pi3.model + $ cat pi3.model type: model authority-id: 4BKZlf4WMNBKgQfij0rftmp5BzDdVhlf series: 16 brand-id: 4BKZlf4WMNBKgQfij0rftmp5BzDdVhlf model: pi3 architecture: armhf gadget: pi3 kernel: pi2-kernel timestamp: 2016-09-09T08:27:36+00:00 ... Once flashed to sdcard and booted on the Pi3 it crashes again and again - in the same place (__uart_start -> __dabt_svc). See attached picture. - Device is unusable. + in the same place (__uart_start -> __dabt_svc) without doing anything. + Reduced cable connections to just HDMI and power but no change. + + See attached picture. Kernel snap is pi2-kernel_15.snap ** Changed in: linux-raspi2 (Ubuntu) Importance: Undecided => Critical ** Also affects: snappy Importance: Undecided Status: New ** Description changed: Build an image today with $ sudo ubuntu-image --channel edge -o pi3.img pi3.model $ cat pi3.model type: model authority-id: 4BKZlf4WMNBKgQfij0rftmp5BzDdVhlf series: 16 brand-id: 4BKZlf4WMNBKgQfij0rftmp5BzDdVhlf model: pi3 architecture: armhf gadget: pi3 kernel: pi2-kernel timestamp: 2016-09-09T08:27:36+00:00 ... Once flashed to sdcard and booted on the Pi3 it crashes again and again in the same place (__uart_start -> __dabt_svc) without doing anything. + Device can't be used afterwards as this crashed the whole system. Reduced cable connections to just HDMI and power but no change. See attached picture. Kernel snap is pi2-kernel_15.snap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630586 Title: Pi3 kernel crash and is unreliable To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1630586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630586] [NEW] Pi3 kernel crash and is unreliable
Public bug reported: Build an image today with $ sudo ubuntu-image --channel edge -o pi3.img pi3.model $ cat pi3.model type: model authority-id: 4BKZlf4WMNBKgQfij0rftmp5BzDdVhlf series: 16 brand-id: 4BKZlf4WMNBKgQfij0rftmp5BzDdVhlf model: pi3 architecture: armhf gadget: pi3 kernel: pi2-kernel timestamp: 2016-09-09T08:27:36+00:00 ... Once flashed to sdcard and booted on the Pi3 it crashes again and again in the same place (__uart_start -> __dabt_svc) without doing anything. Device can't be used afterwards as this crashed the whole system. Reduced cable connections to just HDMI and power but no change. See attached picture. Kernel snap is pi2-kernel_15.snap ** Affects: snappy Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu) Importance: Critical Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630586 Title: Pi3 kernel crash and is unreliable To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1630586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630586] Re: Pi3 kernel crash and is unreliable
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1630586/+attachment/4755050/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630586 Title: Pi3 kernel crash and is unreliable To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1630586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1627031] Re: console-conf crashes with a WiFi which does not support SIOCGIWESSID
@Michael: That sounds like a first attempt to fix this but I guess we will then miss the ESSID in the UI for those dongles. The problem seems to be more that the driver does not support the necessary WEXT command SIOCGIWESSID anymore and just gives you access with nl80211. So we have two real options to fix this: 1. Force all kernels to have CONFIG_CFG80211_WEXT enabled. As this is the official pi2 kernel we should definitely open a bug there and get it included in the kernel config. 2. When the WEXT ioctl fails fallback to nl80211 or use nl80211 directly and fallback to the WEXT ioctl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1627031 Title: console-conf crashes with a WiFi which does not support SIOCGIWESSID To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1627031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1627031] [NEW] console-conf crashes with a WiFi which does not support SIOCGIWESSID
Public bug reported: console-cofn crashes with "PermissionError: [Errno 1] Operation not permitted" when I have my TP-LINK TL-WN725N V2 plugged via USB in the device. If the device is unplugged console-conf does not crash anymore. See attached log file for more details. ** Affects: subiquity (Ubuntu) Importance: Undecided Status: New ** Attachment added: "subiquity-debug.log" https://bugs.launchpad.net/bugs/1627031/+attachment/4747067/+files/subiquity-debug.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1627031 Title: console-conf crashes with a WiFi which does not support SIOCGIWESSID To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1627031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
Sorry, for seeing this one a bit late. First of all the relevant problem is ( 15.152| 0.000) E: [pulseaudio] volume.c: Assertion 'pa_channels_valid(channels)' failed at pulse/volume.c:74, function pa_cvolume_set(). Aborting. Which basically means there is a volume level being set for an invalid channel (simply a number which is out of range once passed to pa_cvolume_set). Looking into the code the function source_set_volume_cb in src/modules/bluetooth/module-bluez5-device.c (line 961) calls pa_cvolume_set and also sink_set_volume_cb (line 1187). Each gets called for either when a source or sink is added to the device and the profile being used is PA_BLUETOOTH_PROFILE_HEADSET_HEAD_UNIT. The sample_spec struct being used to provide the channel is configured in transport_config which is according to the log file attached in comment #1 never called before the abort happens. The function transport_acquire is called before and returns an error according to: ( 14.894| 0.000) D: [pulseaudio] module-bluez5-device.c: Acquiring transport /org/bluez/hci0/dev_44_5E_F3_B4_07_29/fd49 ( 14.894| 0.000) I: [pulseaudio] backend-native.c: doing connect ( 15.151| 0.257) E: [pulseaudio] backend-native.c: connect(): Function not implemented That the connect() syscall returns "Function no implemented" is suspicious. If we're going further in the log file we see ( 15.152| 0.000) D: [pulseaudio] backend-native.c: Transport /org/bluez/hci0/dev_44_5E_F3_B4_07_29/fd49 available for profile headset_head_unit which happens inside src/modules/bluetooth/backend-native.c in function profile_new_connection when we get called back from bluez if the HFP profile you get connected with the remote side. The next line is the interesting one: ( 15.152| 0.000) D: [pulseaudio] backend-native.c: RFCOMM << AT+VGS=8 This actually comes from set_speaker_gain in src/modules/bluetooth /backend-native.c line 276 and is called by sink_set_volume_cb in src/modules/bluetooth/module-bluez5-device.c (line 1187) which is called subsequently from add_sink -> init_profile. As set_speaker_gain prints out the string "RFCOMM << AT+VGS=8" AFTER it has the set volume in sink_set_volume_cb the first call to pa_cvolume_set already happened and went through without the assert in pa_cvolume_set failing for an incorrect channel. The only left candidate then is source_set_volume_cb but that one is using the same u->sample_spec.channels value as we used before and it shouldn't have changed in between. What somebody should now look into: Add pa_log_debug lines before and after the actual pa_cvolume_set calls in src/modules/bluetooth/module- bluez5-device.c so that we can verify which is actually causing the abort. These should also print the value of u->sample_spec.channels. With that we have at least the line which is causing the abort and can then look into possible reasons why this is happening. I suspect the order of a specific code flow has change slightly with the SCO-over-PCM changes we did for Ubuntu Touch. Also it would be great if someone who removed the patches can provide a log file for pulseaudio in debug mode where the headset gets connected and no abort occurs. @Luke: Can you provide packages with the necessary changes so that people expiring the abort can install these and provide new log files? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623068] Re: Networkd fails to configure a ethernet network device on a 3.4 kernel
That patch works but there are now more problems with the DHCP stack inside networkd. See https://paste.ubuntu.com/23178198/ Needs more investigation. To unblock our work we're now using a static ifupdown configuration but need to fix this bug here for real networkd support. ** Changed in: systemd (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1623068 Title: Networkd fails to configure a ethernet network device on a 3.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623068] Re: Networkd fails to configure a ethernet network device on a 3.4 kernel
Yes, the kernel has IPv6 support enabled so socket_ipv6_is_supported() returns true and with that it tries to setup the IPv6 part of the interface. The two problems which I've found so far are: - an empty IFLA_AF_SPEC seems to cause the kernel to return EINVAL - having IPv6 enabled and IFLA_AF_SPEC is filled with the ipv6ll mode we get EINVAL So to fix this we have to do two things: 1. disable IPv6 support in the 3.4 kernel; if that is not acceptable for the real product later than we have to find another solution. 2. move the open/close_container() inside the if() statement to avoid an empty container. For 2. we may can work around this on the kernel side too to allow empty IFLA_AF_SPEC containers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1623068 Title: Networkd fails to configure a ethernet network device on a 3.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623068] Re: Networkd fails to configure a ethernet network device on a 3.4 kernel
The actual error message comes from https://github.com/systemd/systemd/blob/95adafc428b5b4be0ddd4d43a7b96658390388bc/src/network /networkd-link.c#L1441 and due to the nature of this the problem only occurs when the network interface isn't already up. If lines 1391 to 1420 are commented on https://github.com/systemd/systemd/blob/95adafc428b5b4be0ddd4d43a7b96658390388bc/src/network /networkd-link.c#L1391 the kernel doesn't return EINVAL and the interface is properly setup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1623068 Title: Networkd fails to configure a ethernet network device on a 3.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623068] Re: Networkd fails to configure a ethernet network device on a 3.4 kernel
Output of sudo SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd ubuntu@nirvana:~$ sudo SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd sudo: unable to resolve host nirvana: Connection refused Failed to connect to bus, trying again in 5s: No such file or directory timestamp of '/etc/systemd/network' changed p2p0: Flags change: +MULTICAST +BROADCAST p2p0: Link 7 added p2p0: udev initialized link p2p0: Saved original MTU: 1500 sit0: MAC address not found for new device, continuing without sit0: Flags change: +NOARP sit0: Link 6 added sit0: udev initialized link sit0: Saved original MTU: 1480 wlan0: Flags change: +MULTICAST +BROADCAST wlan0: Link 5 added wlan0: udev initialized link wlan0: Saved original MTU: 1500 enx00606e43a573: Flags change: +MULTICAST +BROADCAST enx00606e43a573: Link 4 added enx00606e43a573: udev initialized link enx00606e43a573: Saved original MTU: 1500 enp1s0: Flags change: +MULTICAST +BROADCAST enp1s0: Link 3 added enp1s0: udev initialized link enp1s0: Saved original MTU: 1500 dummy0: Flags change: +BROADCAST +NOARP dummy0: Link 2 added dummy0: udev initialized link dummy0: Saved original MTU: 1500 lo: Flags change: +LOOPBACK +UP +LOWER_UP +RUNNING lo: Link 1 added lo: udev initialized link lo: Saved original MTU: 16436 lo: Adding address: ::1/128 (valid forever) lo: Adding address: 127.0.0.1/8 (valid forever) Enumeration completed p2p0: Link state is up-to-date p2p0: Unmanaged sit0: Link state is up-to-date sit0: Unmanaged wlan0: Link state is up-to-date wlan0: Unmanaged enx00606e43a573: Link state is up-to-date enx00606e43a573: Unmanaged enp1s0: Link state is up-to-date enp1s0: found matching network '/etc/systemd/network/enp1s0.network' enp1s0: Bringing link up enp1s0: Setting addresses dummy0: Link state is up-to-date dummy0: Unmanaged lo: Link state is up-to-date lo: Unmanaged enp1s0: Could not bring up interface: Invalid argument enp1s0: Updating address: 192.168.178.30/24 (valid forever) enp1s0: Addresses set enp1s0: Setting routes enp1s0: Could not set route: Invalid argument enp1s0: Routes set -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1623068 Title: Networkd fails to configure a ethernet network device on a 3.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623068] [NEW] Networkd fails to configure a ethernet network device on a 3.4 kernel
Public bug reported: Knowing that a 3.4 based kernel is unsupported we have to get it working for a specific customer. Systemd itself boots up nicely already but networkd fails to configure a network device with the following configuration file in /etc/systemd/network $ cat /etc/systemd/network/enp1s0.network [Match] Name=enp1s0 [Network] DNS=8.8.8.8 Address=192.168.178.30 Gateway=192.168.178.1 This gives the following error messages $ sudo /lib/systemd/systemd-networkd Enumeration completed enp1s0: Could not bring up interface: Invalid argument enp1s0: Could not set route: Invalid argument ifupdown or NetworkManager is reliable able to get the same interface up and configured. ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1623068 Title: Networkd fails to configure a ethernet network device on a 3.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623068] Re: Networkd fails to configure a ethernet network device on a 3.4 kernel
** Attachment added: "systemd-networkd-on-3.4.log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+attachment/4740099/+files/systemd-networkd-on-3.4.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1623068 Title: Networkd fails to configure a ethernet network device on a 3.4 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1619721] Re: /etc/machine-id changes with every reboot
@Oliver: What is console-conf using to retrieve a IP address over DHCP? If it is dhclient and in a subsequent boot networkd is used then we have different storage locations for the leases which would explain why the DHCP request is sent again and a new IP address assigned. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1619721 Title: /etc/machine-id changes with every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1619721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616063] Re: Create interface for urfkill
@Oliver: We can't add everything required for urfkilld into the network- control interface as we also need to allow it owning a dbus system service. So in summary I think we can easily archive this with an urfkill + network-control interface. ** Also affects: snappy-hwe-snaps Importance: Undecided Status: New ** Changed in: snappy-hwe-snaps Importance: Undecided => High ** Changed in: snappy-hwe-snaps Status: New => Triaged ** Changed in: snappy-hwe-snaps Assignee: (unassigned) => Simon Fels (morphis) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616063 Title: Create interface for urfkill To manage notifications about this bug go to: https://bugs.launchpad.net/snappy-hwe-snaps/+bug/1616063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318360] Re: Poor microphone quality (mako)
** Changed in: libhybris (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1318360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318360] Re: Poor microphone quality (mako)
** Changed in: libhybris (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1318360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318360] Re: Poor microphone quality (mako)
** Changed in: pulseaudio (Ubuntu) Status: Fix Committed => Invalid ** Also affects: libhybris (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1318360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318360] Re: Poor microphone quality (mako)
** Changed in: libhybris (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1318360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318360] Re: Poor microphone quality (mako)
@K1773R: It does not have to be in the milestone list to land. The package is already part of the overlay ppa and in rc-proposed so it will be automatically land with OTA 13. ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1318360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318360] Re: Poor microphone quality (mako)
This landed with 0.1.0+git20151016+6d424c9-0ubuntu18 in the overlay ppa. Can't say if that went out with OTA 12 or will come with OTA 13. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318360 Title: Poor microphone quality (mako) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1318360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618522] [NEW] netplan does not generates .network files just for ethernet
Public bug reported: On my pi3 I have an image with the ubuntu-core snap rev 354 and I get the following netplan configuration file after the first boot: ubuntu@localhost:~$ cat /etc/netplan/00-initial-config.yaml network: version: 2 ethernets: all: match: name: "*" dhcp4: true This generates the following .networkd file ubuntu@localhost:~$ cat /run/systemd/network/10-netplan-all.network [Match] Name=* [Network] DHCP=ipv4 If I look now at the output of networkctl I see it also tries to manage my mlan0 device which is a WiFi one and should be managed according to the netplan rule: ubuntu@localhost:~$ networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier configured 5 eth1 ether no-carrier configuring 6 eth0 ether routableconfigured 7 mlan0wlan no-carrier configuring In summary, the networkd generator inside netplan currently does not limit the generated .network file to tell networkd to only look at ethernet devices but rather tell it to control every device available on the system. Expectation: Specifying a wildcard rule in a netplan configuration file for ethernet devices should tell the configured networking system to only consider ethernet devices and nothing else. ** Affects: nplan (Ubuntu) Importance: Undecided Status: New ** Description changed: On my current pi3 I have with the ubuntu-core snap (rev 354) I get the following netplan configuration file: ubuntu@localhost:~$ cat /etc/netplan/00-initial-config.yaml network: - version: 2 - ethernets: -all: - match: - name: "*" - dhcp4: true + version: 2 + ethernets: + all: + match: + name: "*" + dhcp4: true This generates the following .networkd file ubuntu@localhost:~$ cat /run/systemd/network/10-netplan-all.network [Match] Name=* [Network] DHCP=ipv4 If I look now at the output of networkctl I see it also tries to manage my mlan0 device which is a WiFi one and should be managed according to the netplan rule: - ubuntu@localhost:~$ networkctl - IDX LINK TYPE OPERATIONAL SETUP - 1 lo loopback carrier configured - 5 eth1 ether no-carrier configuring - 6 eth0 ether routableconfigured - 7 mlan0wlan no-carrier configuring + ubuntu@localhost:~$ networkctl + IDX LINK TYPE OPERATIONAL SETUP + 1 lo loopback carrier configured + 5 eth1 ether no-carrier configuring + 6 eth0 ether routableconfigured + 7 mlan0wlan no-carrier configuring In summary, the networkd generator inside netplan currently does not limit the generated .network file to tell networkd to only look at ethernet devices but rather tell it to control every device available on the system. + + Expectation: Specifying a wildcard rule in a netplan configuration file + for ethernet devices should tell the configured networking system to + only consider ethernet devices and nothing else. ** Description changed: - On my current pi3 I have with the ubuntu-core snap (rev 354) I get the - following netplan configuration file: + On my pi3 I have an image with the ubuntu-core snap rev 354 and I get + the following netplan configuration file after the first boot: ubuntu@localhost:~$ cat /etc/netplan/00-initial-config.yaml network: version: 2 ethernets: all: match: name: "*" dhcp4: true This generates the following .networkd file ubuntu@localhost:~$ cat /run/systemd/network/10-netplan-all.network [Match] Name=* [Network] DHCP=ipv4 If I look now at the output of networkctl I see it also tries to manage my mlan0 device which is a WiFi one and should be managed according to the netplan rule: ubuntu@localhost:~$ networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier configured 5 eth1 ether no-carrier configuring 6 eth0 ether routableconfigured 7 mlan0wlan no-carrier configuring In summary, the networkd generator inside netplan currently does not limit the generated .network file to tell networkd to only look at ethernet devices but rather tell it to control every device available on the system. Expectation: Specifying a wildcard rule in a netplan configuration file for ethernet devices should tell the configured networking system to only consider ethernet devices and nothing else. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.
[Bug 1615819] Re: BQ M10 screen casting
Sadly, we don't have any direct plan right now to add support for WPS PIN in aethercast. This would also involve UI work to get things properly setup. Can you retry the connection and give me the content of /var/log/upstart/aethercast.log? Maybe there is a way we can workaround this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615819 Title: BQ M10 screen casting To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615819] Re: BQ M10 screen casting
This would be basically WPS PIN support in aethercast which we don't have yet. ** Also affects: aethercast (Ubuntu) Importance: Undecided Status: New ** Changed in: aethercast (Ubuntu) Importance: Undecided => Wishlist ** Changed in: aethercast (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615819 Title: BQ M10 screen casting To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602950] Re: Unity8 crashes when switching back to lockscreen while using WiDi
@Danial: You can easily do that with the attached crash file. So what also would a ubuntu-bug provide? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602950 Title: Unity8 crashes when switching back to lockscreen while using WiDi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1602950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602950] [NEW] Unity8 crashes when switching back to lockscreen while using WiDi
Public bug reported: Testing new aethercast changes (https://requests.ci- train.ubuntu.com/#/ticket/1620) and found unity8 is crashing when it switches after a timeout automatically to the lock screen. This is on current build number: 142 device name: frieza channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en last update: 2016-07-13 05:57:58 version version: 142 version ubuntu: 20160713 version device: 20160622.0 version custom: 20160712--42-19-vivid SEGV backtrace: #0 0xe656f40e in MirBufferSGTexture::bind() () from /usr/lib/arm-linux-gnueabihf/qt5/qml/Unity/Application/libunityapplicationplugin.so No symbol table info available. #1 0xf6f605e2 in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5 No symbol table info available. #2 0xf6f5194a in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5 No symbol table info available. #3 0xf6f527c8 in QSGBatchRenderer::Renderer::renderBatches() () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5 No symbol table info available. #4 0xf70d2f48 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5 ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "_usr_bin_unity8.32011.crash" https://bugs.launchpad.net/bugs/1602950/+attachment/4700604/+files/_usr_bin_unity8.32011.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602950 Title: Unity8 crashes when switching back to lockscreen while using WiDi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1602950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1596951] Re: [CTA] CameraService in trust prompt should be translated
** Changed in: trust-store (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1596951 Title: [CTA] CameraService in trust prompt should be translated To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1596951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586972] Re: Sometimes get "ok" box with no text
Saw this some times too. Not sure yet which error this triggers but likely we're not handling one error code in u-s-s yet. ** Changed in: ubuntu-system-settings (Ubuntu) Assignee: (unassigned) => Ken VanDine (ken-vandine) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586972 Title: Sometimes get "ok" box with no text To manage notifications about this bug go to: https://bugs.launchpad.net/aethercast/+bug/1586972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1596464] Re: unity greeter stays in desktop mode if a bluetooth HID is connected
This is nothing related to aethercast. Must be something wrong in unity8. ** Changed in: aethercast Status: New => Invalid ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1596464 Title: unity greeter stays in desktop mode if a bluetooth HID is connected To manage notifications about this bug go to: https://bugs.launchpad.net/aethercast/+bug/1596464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1583057] Re: Deny audio recording for all snap applications
Updated the patch. We now add snappy-policy always to default.pa. I couldn't figure out what I have to change to make the ifelse statement work properly to add the snappy policy module only conditionally to default.pa Also fixed the compiler warnings and other small things. ** Patch added: "pa-snappy-policy.patch" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583057/+attachment/4696316/+files/pa-snappy-policy.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583057 Title: Deny audio recording for all snap applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1583057] Re: Deny audio recording for all snap applications
@Jamie: Works fine here for me. Using a simple snap name: pulseaudio-clients version: 8.0-1 summary: Clients for PulseAudio description: | Contains PulseAudio client utilities apps: pactl: command: usr/bin/pactl plugs: [pulseaudio] paplay: command: usr/bin/paplay plugs: [pulseaudio] parec: command: usr/bin/parec plugs: [pulseaudio] parts: packages: plugin: nil stage-packages: - pulseaudio to test. Make sure that the module is loaded: simon@nirvana ~/Work/ubuntu/snappy/paplay-snap $ pactl list modules | grep snappy Name: module-snappy-policy If not you can load it with $ pactl load-module module-snappy-policy If you now install the snap from above and run $ pulseaudio-clients.parec you will see the client hangs. If you unload the module $ pactl unload-module module-snappy-policy you will see the client can record now and doesn't hang any longer. The only thing which might have went wrong with the package debdiff is that the module for the snappy policy wasn't added to /etc/pulse/daemon.pa. Will check that now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583057 Title: Deny audio recording for all snap applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598886] [NEW] Misleading error message when trying to install unconfined snaps from the edge channel
Public bug reported: When I try to install the TPM snap from the edge channel I get the following output: $ snap install tpm --channel=edge error: cannot perform the following tasks: - Download snap "tpm" from channel "edge" (snap not found) The mistake here is that I forgot --devmode as the snap is published with "confinement: devmode" but the error message is misleading here. For the filtering (channel==edge && confinement==struct) its ok to say "snap not found" but the user doesn't know he did wrong. We should extend this and say that he may want to add --devmode to install the snap if its only provided with "confinement: devmode". ** Affects: snapd (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598886 Title: Misleading error message when trying to install unconfined snaps from the edge channel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1598886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1583057] Re: Deny audio recording for all snap applications
@Jamie: Attached is a debdiff to update the pulse pacakge with snappy support. ** Patch added: "pulseaudio-snappy-deny-recording.diff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583057/+attachment/4695115/+files/pulseaudio-snappy-deny-recording.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583057 Title: Deny audio recording for all snap applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1593568] Re: Create an interface for tpm1.2
I've pushed the TPM snap now into a common repository on https://code.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/tpm If you're back from holiday lets quickly sync up on your work here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593568 Title: Create an interface for tpm1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1593568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590679] Re: Apps can't own session bus names (unity7 interface)
Just for interest I did such a simple interfaces some time ago for playing: dbus-name: https://github.com/morphis/snappy/commit/0489b6f23b190d817975247d460990f67e0c4d5c Allows you to bind a by attribute specified dbus name on the system bus. This was meant for snap internal communication but could be easily expanded to specify system/session bus and integrate some snapd management to avoid bus name collisions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590679 Title: Apps can't own session bus names (unity7 interface) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1590679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586972] Re: Sometimes get "ok" box with no text
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586972 Title: Sometimes get "ok" box with no text To manage notifications about this bug go to: https://bugs.launchpad.net/aethercast/+bug/1586972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1583057] Re: Deny audio recording for all snap applications
@Luke: How did you test the change before landing it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583057 Title: Deny audio recording for all snap applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1583057] [NEW] Deny audio recording for all snap applications
Public bug reported: Until we have a proper trust-store implementation with snappy and on the desktop/ubuntu core we want pulseaudio to simply deny any audio recording request coming from an app shipped as part of a snap. The implementation adds a module-snappy-policy module to pulseaudio which adds a hook for audio recording requests and checks on connection if the apparmor security label of the connecting peer starts with "snap." which will identify it as a snap application. Pulseaudio with the patch is available as part of the landing request at https://requests.ci-train.ubuntu.com/#/ticket/1428 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583057 Title: Deny audio recording for all snap applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1583057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576711] Re: [xenial] Enable arm64 build
** Package changed: aethercast (Ubuntu) => aethercast ** Changed in: aethercast Assignee: (unassigned) => Simon Fels (morphis) ** Changed in: aethercast Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576711 Title: [xenial] Enable arm64 build To manage notifications about this bug go to: https://bugs.launchpad.net/aethercast/+bug/1576711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567467] Re: Urfkill gets out of sync with actual rfkill on the kernel side
@John: Yes, fix was released with the last urfkilld landing: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable- phone-overlay/+sourcepub/6411875/+listing-archive-extra ** Changed in: urfkill (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: canonical-devices-system-image Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567467 Title: Urfkill gets out of sync with actual rfkill on the kernel side To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579915] Re: network-manager 1.2 uses more power
** Changed in: network-manager (Ubuntu) Status: Confirmed => In Progress ** Changed in: canonical-devices-system-image Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579915 Title: network-manager 1.2 uses more power To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579915] Re: network-manager 1.2 uses more power
Checked this on krillin with current build number: 329 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-05-10 03:25:03 version version: 329 version ubuntu: 20160510 version device: 20160329-a9bacdb version custom: 20160505-975-38-9 Device doesn't go to sleep and attempts are visible in dmesg which also shows [ 1231.568056] active wakeup source: WLAN AHB ISR as the reason for the failed attempt to sleep. Looks like something in NetworkManager causes the kernel to still held a wakelock even if the device should go into suspend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579915 Title: network-manager 1.2 uses more power To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579915] Re: big power increase in May 4th and later builds
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579915 Title: network-manager 1.2 uses more power To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
