[Touch-packages] [Bug 2059872] Re: Unable to listen on port 22 if multiple Port= present in sshd configuration
Is there a workaround for this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2059872 Title: Unable to listen on port 22 if multiple Port= present in sshd configuration Status in openssh package in Ubuntu: In Progress Bug description: Recently introduced sshd-socket-generator for socket activation in openssh 1:9.6p1-3ubuntu3 has a bug when dealing with multiple Port or ListenAddress entries in the sshd configuration. If you have multiple Port or ListenAddress and one of them is for port 22, it just skips it. To show it clearly, here is an example: Port 22 Port 1024 It generates: ListenStream= ListenStream=1024 Now nothing is listening to port 22, hence breaking existing configurations. This was tested on 1:9.6p1-3ubuntu11. The intention seems to be to not generate the drop-in if only port 22 is in use, but it does not account for the case of multiple Port or ListenAddress where one of them is for port 22. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
I currently have the package patched in my PPA to resolve the bug. It is a difficult to debug problem that has been sending users upstream to kodi with bug reports and confusing stack traces. This will get more exposure when focal is released due to the LTS status. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in alsa-plugins package in Ubuntu: New Status in jackd2 package in Ubuntu: Confirmed Status in jackd2 package in Debian: Confirmed Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multi-threaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
Is this going to make it for focal? This bug causes kodi to crash when turning my TV screen off. ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in alsa-plugins package in Ubuntu: New Status in jackd2 package in Ubuntu: Confirmed Status in jackd2 package in Debian: Confirmed Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multi-threaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
No one is asking you to send them a fix. Since you are experiencing the issue on a stable release, you should let Mesa know that the issue exists in stable releases, and ask them to provide the fix for the stable 20.0.x branch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 Status in mesa package in Ubuntu: New Bug description: uname -a Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 1920x1080@60.00hz OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 9.0.0) version: 4.5 Mesa 19.2.8 For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen (top) compressed image. To solve the default, i have to revert via synaptic the package mesa- va-driver to 19.0.8. Other solution is to take nighty builds as complete mesa package via : https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers that works too and is at mesa 20.1 git Please correct the problem to the official Ubuntu repos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
Oibaf is using the development release of Mesa. It's not released yet. Mesa 20.1 isn't scheduled for release until May. You need them to backport the fix to the 20.0.x branch. Here is the upstream issue: https://gitlab.freedesktop.org/mesa/mesa/issues/2523 You can ask there for a backport to 20.0.x. ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #2523 https://gitlab.freedesktop.org/mesa/mesa/issues/2523 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 Status in mesa package in Ubuntu: New Bug description: uname -a Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 1920x1080@60.00hz OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 9.0.0) version: 4.5 Mesa 19.2.8 For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen (top) compressed image. To solve the default, i have to revert via synaptic the package mesa- va-driver to 19.0.8. Other solution is to take nighty builds as complete mesa package via : https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers that works too and is at mesa 20.1 git Please correct the problem to the official Ubuntu repos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1868352] Re: grub2 2.04-1ubuntu12.2 breaks boot on some machines
I filed this against grub2 originally. Somehow ubuntu-bug changed that to xorg. I added grub2 back. It's not letting me remove xorg. ** Also affects: grub2 (Ubuntu) Importance: Undecided Status: New ** No longer affects: xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1868352 Title: grub2 2.04-1ubuntu12.2 breaks boot on some machines Status in grub2 package in Ubuntu: New Bug description: 2.04-1ubuntu12.2 broke boot on my machine. It doesn't work with kernels that don't have CONFIG_EFI_STUB=y configured. This really needs to fall back to the old mode if EFI handover is not supported by the kernel. Also, after using a kernel with CONFIG_EFI_STUB=y it still failed to boot one of my machines with root specified by UUID. I was able to workaround it by manually specifying the boot device with /dev/nvme0n1p2 at the grub menu, and then specifying GRUB_DISABLE_LINUX_UUID=true in /etc/default/grub. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.5.10-customskl x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Mar 20 21:19:01 2020 DistUpgraded: 2019-10-26 18:15:16,011 DEBUG running apport_crash() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: zfs, 0.8.3, 5.5.10-customskl, x86_64: installed zfs, 0.8.3, 5.5.9-customskl, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:872f] InstallationDate: Installed on 2012-12-04 (2664 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.5.10-customskl root=/dev/nvme0n1p2 ro rootflags=subvol=@ drm_kms_helper.edid_firmware=DP-1:edid/monoprice_28_4k.edid SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-26 (146 days ago) dmi.bios.date: 10/07/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2203 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2203:bd10/07/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4~yasi1~19.10 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1~yasi1~19.10 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1~yasi1~19.10 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20191209.2226.f66d3954-0ubuntu0+yasi1~19.10 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1868352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1868352] [NEW] grub2 2.04-1ubuntu12.2 breaks boot on some machines
Public bug reported: 2.04-1ubuntu12.2 broke boot on my machine. It doesn't work with kernels that don't have CONFIG_EFI_STUB=y configured. This really needs to fall back to the old mode if EFI handover is not supported by the kernel. Also, after using a kernel with CONFIG_EFI_STUB=y it still failed to boot one of my machines with root specified by UUID. I was able to workaround it by manually specifying the boot device with /dev/nvme0n1p2 at the grub menu, and then specifying GRUB_DISABLE_LINUX_UUID=true in /etc/default/grub. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.5.10-customskl x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Mar 20 21:19:01 2020 DistUpgraded: 2019-10-26 18:15:16,011 DEBUG running apport_crash() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: zfs, 0.8.3, 5.5.10-customskl, x86_64: installed zfs, 0.8.3, 5.5.9-customskl, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:872f] InstallationDate: Installed on 2012-12-04 (2664 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.5.10-customskl root=/dev/nvme0n1p2 ro rootflags=subvol=@ drm_kms_helper.edid_firmware=DP-1:edid/monoprice_28_4k.edid SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-26 (146 days ago) dmi.bios.date: 10/07/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2203 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2203:bd10/07/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4~yasi1~19.10 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1~yasi1~19.10 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1~yasi1~19.10 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20191209.2226.f66d3954-0ubuntu0+yasi1~19.10 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan fonts kubuntu regression-update third-party-packages ubuntu ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1868352 Title: grub2 2.04-1ubuntu12.2 breaks boot on some machines Status in xorg package in Ubuntu: New Bug description: 2.04-1ubuntu12.2 broke boot on my machine. It doesn't work with kernels that don't have CONFIG_EFI_STUB=y configured. This really needs to fall back to the old mode if EFI handover is not supported by the kernel. Also, after using a kernel with CONFIG_EFI_STUB=y it still failed to boot one of my machines with root specified by UUID. I was able to workaround it by manually specifying the boot device with /dev/nvme0n1p2 at the grub menu, and then specifying GRUB_DISABLE_LINUX_UUID=true in /etc/default/grub. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.5.10-customskl x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Mar 20 21:19:01 2020 DistUpgraded: 2019-10-26 18:15:16,011 DEBUG running apport_crash() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: zfs, 0.8.3, 5.5.10-customskl, x86_64: installed zfs, 0.8.3, 5.5.9-customskl, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:872
[Touch-packages] [Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
This is supposed to be fixed in Mesa 20.1 git by c81aa15d, gallium/auxiliary/vl: fix bob compute shaders for deint yuv. See: https://gitlab.freedesktop.org/mesa/mesa/-/commit/c81aa15d646215eac38c8e0b6dc1a10b35bc13c3 This could be backported to Mesa 20 if someone wants to try it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 Status in mesa package in Ubuntu: New Bug description: uname -a Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 1920x1080@60.00hz OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 9.0.0) version: 4.5 Mesa 19.2.8 For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen (top) compressed image. To solve the default, i have to revert via synaptic the package mesa- va-driver to 19.0.8. Other solution is to take nighty builds as complete mesa package via : https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers that works too and is at mesa 20.1 git Please correct the problem to the official Ubuntu repos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
I'm marking this as also affects alsa-plugins since that is shipping a jack plugin by default, and this bug is triggered when jack isn't even running. Programs that scan for ALSA devices pick up that jack plugin and trigger the double close. ** Also affects: alsa-plugins (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in alsa-plugins package in Ubuntu: New Status in jackd2 package in Ubuntu: Confirmed Status in jackd2 package in Debian: Confirmed Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multi-threaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
Can this package get updated to 1.9.13, or at least patched in time for 20.04? The security exploitability of this bug may be low, but the impact on affected users is high. It causes hard to debug, random crashes of other programs (e g. Kodi) that are scanning ALSA devices when the jack daemon isn't even started. On Wed, Nov 20, 2019, 10:40 PM Teeedubb <1833...@bugs.launchpad.net> wrote: > Hi, > > I am experiencing the same issue with Kodi 18.5 and Xubuntu 19.10 with > similar stack traces to joe-yasi. Is there anyway to install the updated > package via Ubuntu updates? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1833479 > > Title: > libjack-jackd2-0 double close on a failure to connect to jackd which > causes crashes in multithreaded programs > > Status in jackd2 package in Ubuntu: > Confirmed > Status in jackd2 package in Debian: > Confirmed > > Bug description: > After upgrading to Ubuntu 19.04, I started experiencing sporadic > crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded > alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin > is enabled by default in /etc/alsa/conf.d/50-jack.conf. > > The crashes are caused by a race condition when kodi's audio engine > thread is enumerating the ALSA sound devices, and the udev thread is > enumerating the udev devices triggered by the sound device add from > turning the AVR on. > > When enumerating the ALSA jack plugin device, it tries to connect to > connect to jackd. Since I don't have jackd installed, it fails to > connect. libjack closes the socket on error, and then closes it again > in it's cleanup code. Since it's closing the same file descriptor > twice, it interacts with other threads that have potentially opened > file descriptors, and causes the crash. > > This same bug could potentially affect other multi-threaded programs > that enumerate ALSA devices. > > Fix committed upstream: > > https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in jackd2 package in Ubuntu: Confirmed Status in jackd2 package in Debian: Confirmed Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multi-threaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
jackd2 released version 1.9.13 which includes this fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in jackd2 package in Ubuntu: Confirmed Status in jackd2 package in Debian: Confirmed Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multi-threaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
I just requested one and received: CVE-2019-13351 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-13351 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in jackd2 package in Ubuntu: New Status in jackd2 package in Debian: New Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multi-threaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
** Description changed: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa- - plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is + plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. - When enumering the ALSA jack plugin device, it tries to connect to + When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. - This same bug could potentially affect other multithreaded programs that - enumerate ALSA devices. + This same bug could potentially affect other multi-threaded programs + that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in jackd2 package in Ubuntu: New Status in jackd2 package in Debian: New Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multi-threaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
** Patch added: "Set-fSocket-to--1-after-close-on-an-error-to-prevent-a-double-close.patch" https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+attachment/5271631/+files/Set-fSocket-to--1-after-close-on-an-error-to-prevent-a-double-close.patch ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in jackd2 package in Ubuntu: New Status in jackd2 package in Debian: New Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumering the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multithreaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
I'm marking this a security bug, since all double close bugs can potentially be security bugs in multithreaded programs depending on the close interleaving. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in jackd2 package in Ubuntu: New Status in jackd2 package in Debian: New Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumering the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multithreaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
See kodi issue with stack traces: https://github.com/xbmc/xbmc/issues/16258 ** Also affects: jackd2 (Debian) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in jackd2 package in Ubuntu: New Status in jackd2 package in Debian: New Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumering the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multithreaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833479] [NEW] libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
*** This bug is a security vulnerability *** Public security bug reported: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa- plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumering the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multithreaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 ** Affects: jackd2 (Ubuntu) Importance: Undecided Status: New ** Affects: jackd2 (Debian) Importance: Undecided Status: New ** Bug watch added: github.com/xbmc/xbmc/issues #16258 https://github.com/xbmc/xbmc/issues/16258 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in jackd2 package in Ubuntu: New Status in jackd2 package in Debian: New Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.8, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumering the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multithreaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788448] Re: CVE-2018-14598 CVE-2018-14599 CVE-2018-14600 in libx11
It looks like libx11-1.6.6 was pulled into cosmic. So this is fixed there. This still needs a backport to earlier releases. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1788448 Title: CVE-2018-14598 CVE-2018-14599 CVE-2018-14600 in libx11 Status in libx11 package in Ubuntu: New Bug description: There are 3 security issues reported in libx11 that are fixed upstream in libx11 1.6.6. Bugs announced: https://lists.x.org/archives/xorg-announce/2018-August/002915.html Release announcement of libx11 1.6.6 with commits fixing them listed: https://lists.x.org/archives/xorg-announce/2018-August/002916.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1788448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788448] [NEW] CVE-2018-14598 CVE-2018-14599 CVE-2018-14600 in libx11
*** This bug is a security vulnerability *** Public security bug reported: There are 3 security issues reported in libx11 that are fixed upstream in libx11 1.6.6. Bugs announced: https://lists.x.org/archives/xorg-announce/2018-August/002915.html Release announcement of libx11 1.6.6 with commits fixing them listed: https://lists.x.org/archives/xorg-announce/2018-August/002916.html ** Affects: libx11 (Ubuntu) Importance: Undecided Status: New ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-14598 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-14599 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-14600 ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1788448 Title: CVE-2018-14598 CVE-2018-14599 CVE-2018-14600 in libx11 Status in libx11 package in Ubuntu: New Bug description: There are 3 security issues reported in libx11 that are fixed upstream in libx11 1.6.6. Bugs announced: https://lists.x.org/archives/xorg-announce/2018-August/002915.html Release announcement of libx11 1.6.6 with commits fixing them listed: https://lists.x.org/archives/xorg-announce/2018-August/002916.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1788448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641468] Re: systemd-resolve: fallback from resolve causes lookup of local network hosts to fail
I've just upgraded to zesty, and this problem is still present. Since systemd-resolved is sticking a 127.0.0.53 nameserver in resolv.conf, the problem is worse. To work around it, I have to replace resolv.conf with the old dnsmasq 127.0.1.1 address instead to prevent DNS lookups from going through systemd-resolved. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1641468 Title: systemd-resolve: fallback from resolve causes lookup of local network hosts to fail Status in systemd package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 16.10 from 16.04, DNS resolution of hosts on my local network fails. The hosts line in /etc/nsswitch.conf is: hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns mdns4 If I change it to: hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 I can resolve hosts on my local network. Appending .local to the hostname also allows DNS resolution since systemd-resolve returns a different error for that case. Ex: systemd-resolve rt-ac66u rt-ac66u: resolve call failed: All attempts to contact name servers or networks failed systemd-resolve rt-ac66u.local rt-ac66u.local: resolve call failed: No appropriate name servers or networks for name found "dig rt-ac66u" returns the correct ip. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1641468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641468] [NEW] systemd-resolve: fallback from resolve causes lookup of local network hosts to fail
Public bug reported: After upgrading to Ubuntu 16.10 from 16.04, DNS resolution of hosts on my local network fails. The hosts line in /etc/nsswitch.conf is: hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns mdns4 If I change it to: hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 I can resolve hosts on my local network. Appending .local to the hostname also allows DNS resolution since systemd-resolve returns a different error for that case. Ex: systemd-resolve rt-ac66u rt-ac66u: resolve call failed: All attempts to contact name servers or networks failed systemd-resolve rt-ac66u.local rt-ac66u.local: resolve call failed: No appropriate name servers or networks for name found "dig rt-ac66u" returns the correct ip. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1641468 Title: systemd-resolve: fallback from resolve causes lookup of local network hosts to fail Status in systemd package in Ubuntu: New Bug description: After upgrading to Ubuntu 16.10 from 16.04, DNS resolution of hosts on my local network fails. The hosts line in /etc/nsswitch.conf is: hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns mdns4 If I change it to: hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 I can resolve hosts on my local network. Appending .local to the hostname also allows DNS resolution since systemd-resolve returns a different error for that case. Ex: systemd-resolve rt-ac66u rt-ac66u: resolve call failed: All attempts to contact name servers or networks failed systemd-resolve rt-ac66u.local rt-ac66u.local: resolve call failed: No appropriate name servers or networks for name found "dig rt-ac66u" returns the correct ip. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1641468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624560] [NEW] Use XCB 64-bit sequence API
Public bug reported: libx11 suffers from 32-bit sequence wraparound for programs that make a large number of calls to the server. (See: https://lists.x.org/archives /xorg-devel/2013-October/038370.html ) The Freedesktop bug is here: https://bugs.freedesktop.org/show_bug.cgi?id=71338 This was fixed with this commit: https://cgit.freedesktop.org/xorg/lib/libX11/commit/?id=a72d2d06c002b644b7040a0a9936c8525e092ba8 This fix requires libxcb >= 1.11.1 for the 64-bit sequence API. Xenial and higher ship libxcb 1.11.1. Can this patch be pulled into the Ubuntu package? ** Affects: libx11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1624560 Title: Use XCB 64-bit sequence API Status in libx11 package in Ubuntu: New Bug description: libx11 suffers from 32-bit sequence wraparound for programs that make a large number of calls to the server. (See: https://lists.x.org/archives/xorg-devel/2013-October/038370.html ) The Freedesktop bug is here: https://bugs.freedesktop.org/show_bug.cgi?id=71338 This was fixed with this commit: https://cgit.freedesktop.org/xorg/lib/libX11/commit/?id=a72d2d06c002b644b7040a0a9936c8525e092ba8 This fix requires libxcb >= 1.11.1 for the 64-bit sequence API. Xenial and higher ship libxcb 1.11.1. Can this patch be pulled into the Ubuntu package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1624560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1548766] Re: Plasma crashes when the monitor is disconnected (when it sleeps, in some cases)
I've been suffering the same issue. Plasma crashes every time my 4K monitor sleeps or is turned off in Kubuntu 15.10. I had to pull in Qt 5.5 and this patch to make my desktop usable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1548766 Title: Plasma crashes when the monitor is disconnected (when it sleeps, in some cases) Status in qtbase-opensource-src package in Ubuntu: In Progress Bug description: I'm reporting this on behalf of a coworker who has a 4K monitor, which disconnects whenever it sleeps. Older monitors didn't do that; but Qt 5.5 tries to be honest about it: the QScreen is destroyed whenever its corresponding monitor is disconnected, QGuiApplication::primaryScreen() returns null, and so on. KDE developers have been complaining. So in Qt 5.6 we made it keep the last-remaining QScreen as a fake instance, whenever the last monitor is disconnected. The main patch is here https://codereview.qt-project.org/#/c/138201/ You might need to cherry-pick that (a094af001795c9651b299d700a992150d1aba33a in qtbase) for as long as you are shipping Qt 5.5, to get Kubuntu behaving decently. It's relevant on Ubuntu 16.04. Too bad that Ubuntu LTS is not shipping the LTS Qt 5.6 release, but I know we are behind on our release schedule. Some users have also reported that their laptop's screen disconnects when it sleeps. And I have often experienced 5.5-based builds of Creator crashing or disappearing when I switch machines on my KVM. So, sorry that we didn't fix it sooner. It was my mistake for believing that modeling disappearing screens "correctly" was a good idea: it turned out to be a platform inconsistency which developers were not ready for. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1548766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492774] Re: update-initramfs doesn't copy symlinked firmware files
*** This bug is a duplicate of bug 1496163 *** https://bugs.launchpad.net/bugs/1496163 ** This bug has been marked a duplicate of bug 1496163 i915 firmware is not copied to initrd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1492774 Title: update-initramfs doesn't copy symlinked firmware files Status in initramfs-tools package in Ubuntu: New Bug description: In /usr/share/initramfs-tools/hook-functions, the firmware is copied to the initramfs using: cp -a "$firmware" "$target_dir" For symlinked firmware such as /lib/firmware/i915/skl_dmc_ver1.bin for Intel Skylake, this results in a copy of the symlink instead of the firmware file. update-initramfs then deletes the broken symlink before packaging. This needs to be replaced with a cp command that dereferences symlinks such as: cp -prL "$firmware" "$target_dir" I ran into this on vivid, but it is in wily as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1492774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492774] Re: update-initramfs doesn't copy symlinked firmware files
This bug is a duplicate of #1496163. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1492774 Title: update-initramfs doesn't copy symlinked firmware files Status in initramfs-tools package in Ubuntu: New Bug description: In /usr/share/initramfs-tools/hook-functions, the firmware is copied to the initramfs using: cp -a "$firmware" "$target_dir" For symlinked firmware such as /lib/firmware/i915/skl_dmc_ver1.bin for Intel Skylake, this results in a copy of the symlink instead of the firmware file. update-initramfs then deletes the broken symlink before packaging. This needs to be replaced with a cp command that dereferences symlinks such as: cp -prL "$firmware" "$target_dir" I ran into this on vivid, but it is in wily as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1492774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492774] Re: update-initramfs doesn't copy symlinked firmware files
I want to add that this isn't in the Debian version of the package. The change to remove the call to copy_exec is what broke this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1492774 Title: update-initramfs doesn't copy symlinked firmware files Status in initramfs-tools package in Ubuntu: New Bug description: In /usr/share/initramfs-tools/hook-functions, the firmware is copied to the initramfs using: cp -a "$firmware" "$target_dir" For symlinked firmware such as /lib/firmware/i915/skl_dmc_ver1.bin for Intel Skylake, this results in a copy of the symlink instead of the firmware file. update-initramfs then deletes the broken symlink before packaging. This needs to be replaced with a cp command that dereferences symlinks such as: cp -prL "$firmware" "$target_dir" I ran into this on vivid, but it is in wily as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1492774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492774] [NEW] update-initramfs doesn't copy symlinked firmware files
Public bug reported: In /usr/share/initramfs-tools/hook-functions, the firmware is copied to the initramfs using: cp -a "$firmware" "$target_dir" For symlinked firmware such as /lib/firmware/i915/skl_dmc_ver1.bin for Intel Skylake, this results in a copy of the symlink instead of the firmware file. update-initramfs then deletes the broken symlink before packaging. This needs to be replaced with a cp command that dereferences symlinks such as: cp -prL "$firmware" "$target_dir" I ran into this on vivid, but it is in wily as well. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1492774 Title: update-initramfs doesn't copy symlinked firmware files Status in initramfs-tools package in Ubuntu: New Bug description: In /usr/share/initramfs-tools/hook-functions, the firmware is copied to the initramfs using: cp -a "$firmware" "$target_dir" For symlinked firmware such as /lib/firmware/i915/skl_dmc_ver1.bin for Intel Skylake, this results in a copy of the symlink instead of the firmware file. update-initramfs then deletes the broken symlink before packaging. This needs to be replaced with a cp command that dereferences symlinks such as: cp -prL "$firmware" "$target_dir" I ran into this on vivid, but it is in wily as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1492774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1226766] Re: Mountall fails to mount NFS partitions on boot with GigE network managed by NM
I upgraded to Utopic and this problem got worse on that machine. I've attached the new mountall.log. The fstab line for the mount is now: rt-ac66u:/tmp/mnt/yasimedia /mnt/readyshare nfs _netdev,hard,intr,exec,nodev,nosuid,async,nobootwait 0 0 It looks like it's not detecting the mount as a remote share. The log says /mnt/readyshare is nowait. My workaround for this was sending a SIGUSR1 to mountall in rc.local, but that's not working anymore. It does not mount the NFS mount. A manual /mnt/readyshare works. ** Attachment added: "mountall.log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1226766/+attachment/4209192/+files/mountall.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1226766 Title: Mountall fails to mount NFS partitions on boot with GigE network managed by NM Status in “network-manager” package in Ubuntu: Confirmed Bug description: NFS partitions fail to mount on boot, and mountall freezes without mounting them. If I revert this change to the init script: . /etc/default/rcS || true [ -f /forcefsck ] && force_fsck="--force-fsck" [ "$FSCKFIX" = "yes" ] && fsck_fix="--fsck-fix" + # Doesn't work so well if mountall is responsible for mounting /proc, heh. + if [ -e /proc/cmdline ]; then + for arg in $(cat /proc/cmdline); do + case $arg in + -q|--quiet|-v|--verbose|--debug) + debug_arg=$arg + ;; + esac + done + fi # set $LANG so that messages appearing in plymouth are translated if [ -r /etc/default/locale ]; then . /etc/default/locale || true export LANG LANGUAGE LC_MESSAGES LC_ALL fi - exec mountall --daemon $force_fsck $fsck_fix + exec mountall --daemon $force_fsck $fsck_fix $debug_arg end script it works. It seems strange that this would stop NFS from mounting on boot. It appears that the NFS mounts are occurring before DNS is up. mountall.log contains: mount.nfs: Failed to resolve server rt-ac66u: Name or service not known mountall: mount /mnt/readyshare [815] terminated with status 32 Filesystem could not be mounted: /mnt/readyshare mountall: Disconnected from Plymouth ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: mountall 2.51 Uname: Linux 3.11.1-customatom x86_64 NonfreeKernelModules: nvidia .run.mount.utab: ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Tue Sep 17 14:49:53 2013 ExecutablePath: /sbin/mountall InstallationDate: Installed on 2012-04-15 (520 days ago) InstallationMedia: Mythbuntu 12.04 "Precise Pangolin" - Beta amd64 (20120328) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.1-customatom root=UUID=708b3ba8-c42a-4adf-a195-c0fb8d8f8dd3 ro --verbose SourcePackage: mountall UpgradeStatus: Upgraded to saucy on 2013-06-28 (81 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1226766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1200006] Re: appmenu-gtk support dropped, but unity-gtk-module doesn't work outside unity
It's still working for me here. I just tried Pidgin to make sure the menu is exported. You'll need appmenu-gtk from the PPA and the version of GTK2 in the PPA. appmenu-gtk requires a patched version of GTK2. This will not work for GTK3 apps as I have not forward ported the patch for GTK3 from raring. You'll also need libdbusmenu-qt2. Do QT4 apps properly export the menu in KDE for you? Firefox and Libreoffice are also different since they don't use standard GTK2 menus. You'll need to set ui.use_unity_menubar = true in about:config for Firefox. The Firefox package will also have to have the unity menubar patch applied (which the standard Ubuntu Firefox has). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/126 Title: appmenu-gtk support dropped, but unity-gtk-module doesn't work outside unity Status in Unity GTK+ module: New Status in “gtk+2.0” package in Ubuntu: Confirmed Bug description: GTK apps don't properly export menus on KDE since the appmenu-gtk support was removed. unity-gtk-module does not work outside of unity. Can the appmenu-gtk patch be added back in until unity-gtk-module works in other environments? To manage notifications about this bug go to: https://bugs.launchpad.net/unity-gtk-module/+bug/126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1343800] [NEW] upstart 1.12.1-0ubuntu4.1 breaks xsession start with lightdm
Public bug reported: After upgrading to upstart 1.12.1-0ubuntu4.1, logging in via lightdm freezes on xsession start. The choice of xsession doesn't matter. It will not load KDE or TWM. It freezes after pressing login without trying to start the xsession. startx from the commandline launches the xsession properly. lightdm works again after reverting to upstart 1.12.1-0ubuntu4. ** Affects: upstart (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1343800 Title: upstart 1.12.1-0ubuntu4.1 breaks xsession start with lightdm Status in “upstart” package in Ubuntu: New Bug description: After upgrading to upstart 1.12.1-0ubuntu4.1, logging in via lightdm freezes on xsession start. The choice of xsession doesn't matter. It will not load KDE or TWM. It freezes after pressing login without trying to start the xsession. startx from the commandline launches the xsession properly. lightdm works again after reverting to upstart 1.12.1-0ubuntu4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1343800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp