[Touch-packages] [Bug 1938998] Re: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly
** Summary changed: - Update to mesa and xorg-server causes Cinnamon desktop to not render properly + [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly ** Tags added: vmware vmwgfx -- 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/1938998 Title: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+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 1938998] Re: Update to mesa and xorg-server causes Cinnamon desktop to not render properly
** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- 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/1938998 Title: Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+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 1944606] Re: [EDIFIER X3 R, recording] Microphone is not detected as an audio input
According to the PulseList.txt in the #1, the default input device should be "Digital Microphone - sof-hda-dsp": Default source name: alsa_input.pci-_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_6__source I have no idea why "Device doesn't appear in the input options inside gnome sound controls", could you upload a picture to show it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1944606 Title: [EDIFIER X3 R, recording] Microphone is not detected as an audio input Status in alsa-driver package in Ubuntu: New Bug description: Device doesn't appear in the input options inside gnome sound controls. It appears in pavucontrol, but there is no port associated to it, and no sound is captured. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amanda 2204 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Unity Date: Wed Sep 22 14:46:42 2021 InstallationDate: Installed on 2021-09-09 (13 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: EDIFIER X3 R Symptom_Type: None of the above Title: [EDIFIER X3 R, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/30/2021 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0TMFFT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd03/30/2021:br1.4:svnDellInc.:pnVostro5402:pvr:sku0A03:rvnDellInc.:rn0TMFFT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5402 dmi.product.sku: 0A03 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1944606/+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 1944409] Re: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling
** Tags added: fossa-squirtle ** Also affects: oem-priority 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/1944409 Title: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling Status in OEM Priority Project: New Status in systemd package in Ubuntu: New Bug description: My setup: - Dell Latitude 7520 - Dell WD15 USB C docking station - Ubuntu 20.04.3 - systemd 245.4-4ubuntu3.13 - uname -a: Linux CLIFMI085 5.13.0-1012-oem #16-Ubuntu SMP Tue Sep 7 09:23:08 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux I leave my laptop docked and, after waking it up from sleep, the fans start blowing. After a quick inspection with top/htop, I always see /usr/lib/systemd/systemd-udev consuming 50+% of my CPU. After a quick search, I discover that I can use `udevadm monitor` to check what device is making all this fuss, and this is the output: UDEV [92591.827159] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.873819] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.920022] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.967005] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.018200] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.068351] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.115100] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.166201] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.213318] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.261046] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.308824] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.356577] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.403766] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.451164] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) As you can see, the battery status is being polled every 0.05s. To fix this, I just need to restart the service with: sudo systemctl restart systemd-udevd systemd-udevd-kernel.socket systemd-udevd-control.socket Afterwards, this is the output of `udevadm monitor`: KERNEL[92739.612371] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92739.646888] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) KERNEL[92741.076823] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92741.099370] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) KERNEL[92742.539438] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92742.573812] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) As you can see, the battery is now being polled every ~1.5s, which is fine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1944409/+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 1944595] Re: text cursor
Thanks for the bug report. Please attach a photo or video of the problem so we can better understand what you are seeing. ** Tags added: amdgpu ** Summary changed: - text cursor + [amdgpu] text cursor ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/1944595 Title: [amdgpu] text cursor Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: When I click anywhere on the screen, I can see a text cursor in ṕoints where I shouldn't be able to write, such as youtube video titles. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 22 13:16:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.26, 5.11.0-34-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c9) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:876b] InstallationDate: Installed on 2021-07-15 (68 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=ce4e86ab-9ad3-41e8-aff3-3a08cdd0279d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1203 dmi.board.asset.tag: Default string dmi.board.name: PRIME A520M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1203:bd10/23/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnPRIMEA520M-K:rvrRevX.0x: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: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1944595/+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 1944621] Re: sshd in chroot has regression with glibc 2.34
** Patch added: "Configure without closefrom" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1944621/+attachment/5527126/+files/lp1944621.debdiff -- 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/1944621 Title: sshd in chroot has regression with glibc 2.34 Status in openssh package in Ubuntu: New Bug description: A regression to sshd running in a chroot exists under the following conditions: 1) sshd was built with glibc 2.34 2) sshd is running with a kernel that does not define the close_range syscall (kernel <= 5.8) 3) /proc/self/fd does not exist in the chroot The glibc 2.34 implementation of fallback_closefrom fails if /proc/self/fd is not present, which is a valid sshd use case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1944621/+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 1944060] Re: Black Screen after Session Unlock from Suspend
*** This bug is a duplicate of bug 1911055 *** https://bugs.launchpad.net/bugs/1911055 This bug was discovered as duplicate - the issue persisted while the P50 was suspended & resumed while in a docking station (probably prime- select using 'ondemand'). This is GPU driver related. ** This bug has been marked a duplicate of bug 1911055 [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1944060 Title: Black Screen after Session Unlock from Suspend Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu Release: Ubuntu 20.04.3 LTS Installation Style: Minimal (selected during GUI install) (Untested against full installation style) Patient System Hardware Information: Lenovo ThinkPad P50 (Xenon) - Intel HD Graphics + NVIDIA Quadro M2000M (NVIDIA Prime enabled w/proprietary drivers) (GPU is not suspected to be the issue) Expected Behavior: 1) Suspend the system into sleep mode. 2) Awake the system to be greeted by lock screen. 3) Type in password, press enter. 4)GNOME validates password successfully. 5) Resume user desktop session. Actual Behavior: 1) Suspend the system into sleep mode. 2) Awake the system to be greeted by lock screen. 3) Type in password, press enter. 4)GNOME validates password successfully. 5) GNOME lock screen freezes - spinner stops moving but mouse cursor and keyboard are responsive (can switch TTYs). After GNOME lock screen freeze, if you switch out of TTY2 (default for GUI), and back into it, a black screen is shown. If you attempt to login via TTY1, you are switched to the black screen session in TTY2. Solution / Workaround: This behavior can be avoided by installing the "gnome-scrensaver" package. Something in this package is required by GNOME in order to successfully resume this system from suspend, even though no screen saver settings were configured after installing it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1944060/+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 1616079] Re: [Latitude E7270, Realtek ALC3235, Speaker, Internal] Pulseaudio fails to detect card, no sound in speaker nor in line out
This is still a bug in 20.04.3 LTS. It's a fresh install with proprietary drivers enabled from the installer. Could it be routing analog audio to the wrong place? I can get it to work fine with bluetooth headphones, usb headphones on the dock and the laptop. I can't get any audio from the analog jacks on the laptop or the dock or the built in speakers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1616079 Title: [Latitude E7270, Realtek ALC3235, Speaker, Internal] Pulseaudio fails to detect card, no sound in speaker nor in line out Status in pulseaudio package in Ubuntu: Confirmed Bug description: No sound in speakers or in headphones after upgrade to ubuntu 16.04. No devices shown in Sound settings -> Play sound through Previously in ubuntu 14.04 sound works good. sglukhov@Galvatron:~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3235 Analog [ALC3235 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Aug 23 16:24:58 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-01-25 (210 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [Latitude E7270, Realtek ALC3235, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to xenial on 2016-07-05 (49 days ago) dmi.bios.date: 11/09/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: 00DTF3 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd11/09/2015:svnDellInc.:pnLatitudeE7270:pvr:rvnDellInc.:rn00DTF3:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7270 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1616079/+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 1934393] Re: systemd-logind network access is blocked, and breaks remote authentication configurations
I initially preferred your option two, a drop-in file in whichever nis and ldap binary packages, on principle of trying to keep the mitigations in place if we can. But your case for a difficult debugging session is persuasive. Reading the various bug reports around this, option three seems pretty bad -- none of those symptoms would make me think of changing a systemd hardening configuration on a service I might not know I am running. Nothing really looked obviously related to network-based id services. Trying to provide documentation around that won't be very discoverable. Ubuntu is supposed to be easy. So, option one: removing the restrictions for systemd-logind in our package. It would be nice if our implementation of option one would make it very easy to re-add the hardening setting; which we could then document in a hardening guide. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1934393 Title: systemd-logind network access is blocked, and breaks remote authentication configurations Status in systemd: Fix Released Status in nis package in Ubuntu: Confirmed Status in openldap package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in nis package in Debian: Fix Released Bug description: [impact] starting in focal, systemd-logind runs sandboxed without any network access, which breaks any configuration that uses remote servers for user data, e.g. ldap, nis, etc A more full discussion is available in the upstream bug report as well as the debian bug report, see other info section below [test case] many possible ways to reproduce this; there are reproducers in some of the bugs reported before that are caused by this, e.g. bug 1915502 or bug 1916235 [regression potential] failure to authenticate when using remote user data, incorrect authentication, security issues due to un-sandboxing of systemd-logind [scope] this is needed in f and later before focal, systemd-logind was not sandboxed so this did not apply [other info] this isn't actually a bug in systemd, this is a by-design security feature; see links below (and/or comment 13 in this bug) to upstream comments about how systemd's position is that no NSS module should ever perform network access, and any NSS module that does needs to also adjust the restrictions of systemd services such as systemd-logind, systemd-userdbd, and possibly others that might need to make NSS calls into glibc. https://github.com/systemd/systemd/issues/7074#issuecomment-338157851 https://github.com/systemd/systemd/issues/15705#issuecomment-624125354 this may also can cause systemd-udevd failures in some cases as well. https://github.com/systemd/systemd/pull/7343#issuecomment-344800313 For reference, upstream discussion around the systemd-logind sandboxing specifically: https://github.com/systemd/systemd/issues/7074 upstream updated doc PR explaining the upstream position: https://github.com/systemd/systemd/pull/7343 Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625 Note that while this Debian bug is marked as fix released, I don't think it actually fixes the problem, from the final comment it seems like the only change was to add Recommends: nscd, which doesn't really solve things if someone doesn't use nscd. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1934393/+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 1944621] Re: sshd in chroot has regression with glibc 2.34
I created upstream bugs to track this: https://bugzilla.mindrot.org/show_bug.cgi?id=3349 https://sourceware.org/bugzilla/show_bug.cgi?id=28377 ** Bug watch added: OpenSSH Portable Bugzilla #3349 https://bugzilla.mindrot.org/show_bug.cgi?id=3349 ** Bug watch added: Sourceware.org Bugzilla #28377 https://sourceware.org/bugzilla/show_bug.cgi?id=28377 -- 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/1944621 Title: sshd in chroot has regression with glibc 2.34 Status in openssh package in Ubuntu: New Bug description: A regression to sshd running in a chroot exists under the following conditions: 1) sshd was built with glibc 2.34 2) sshd is running with a kernel that does not define the close_range syscall (kernel <= 5.8) 3) /proc/self/fd does not exist in the chroot The glibc 2.34 implementation of fallback_closefrom fails if /proc/self/fd is not present, which is a valid sshd use case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1944621/+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 1308261]
*** Bug 89138 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1308261
Title:
ICE provoked by a lambda using the sizeof a captured stack-allocated
array
Status in gcc:
Fix Released
Status in gcc-4.8 package in Ubuntu:
Confirmed
Status in gcc-4.9 package in Ubuntu:
Confirmed
Bug description:
See upstream report,
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60855.
$ cat gcc-bug.cpp
int main() {
unsigned count = 5;
bool array[count];
[] () {
array[0] = sizeof(array) > 5;
}();
return 0;
}
$ g++ -Wall -Wextra --std=c++11 gcc-bug.cpp
gcc-bug.cpp: In lambda function:
gcc-bug.cpp:6:5: warning: ‘’ is used uninitialized in this
function [-Wuninitialized]
}();
^
gcc-bug.cpp:3:21: note: ‘’ was declared here
bool array[count];
^
gcc-bug.cpp:6:5: internal compiler error: in expand_expr_real_1, at
expr.c:9363
}();
^
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
Preprocessed source stored into /tmp/ccVaDFxq.out file, please attach this to
your bugreport.
$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro
4.8.1-10ubuntu9' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs
--enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.8 --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls
--with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin
--with-system-zlib --disable-browser-plugin --enable-java-awt=gtk
--enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre
--enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar
--enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9)
$ lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10
$ apt-cache policy gcc-4.8
gcc-4.8:
Installed: 4.8.1-10ubuntu9
Candidate: 4.8.1-10ubuntu9
Version table:
*** 4.8.1-10ubuntu9 0
500 http://us.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64
Packages
100 /var/lib/dpkg/status
4.8.1-10ubuntu8 0
500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1308261/+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 1934393] Re: systemd-logind network access is blocked, and breaks remote authentication configurations
One good point in favor of including systemd-userdbd in Debian/Ubuntu would be that we only need to adjust the restrictions for that service; all other systemd-provided services would use (or at least, *should* use...) systemd-userdbd to get user records. I'm not sure if that is actually worth including and using systemd-userdbd to the distro. Putting that aside for now, I think the only options to fix this all involve removing the systemd-logind restriction(s). The only question seems to be what/who removes the restrictions. 1) We could simply remove the restrictions for systemd-logind in the Debian/Ubuntu package, for everyone. This would (theoretically) reduce the security of systemd-logind by allowing it to access the network, but also it would allow network-based NSS lookups to work in all situations (meaning, for all possible NSS modules, not only NIS and/or select other packages/modules). 2) We could add drop-in files to remove the restrictions for systemd- logind, for the 'nis' package (which I think has been split out in later releases and in Debian, so we'd need to pick the correct client package). We would also need to include drop-in files for any other package that provides an NSS module that needs to perform network lookups, such as the 'libnss-ldap' package (I haven't verified this needs network access but I believe it does, e.g. comment 7 above). 3) We could simply add documentation to the README and/or man pages and/or other docs and leave it up to the system admin to add the systemd-logind drop-in file when they set up NIS or LDAP or whatever other network-based auth provider. Personally, I think #3 is barely better than the current situation; there's just far too many setup guides and other documentation out there for us to expect all Debian/Ubuntu users to notice the additional step we might add to our own docs, even if it's in the package README and man pages. However, if we think that NSS-based network auth services are a thing of the past (as seems to be the upstream position on this), then maybe just adding docs is the right way to handle this. I'm not too enthusiastic about option #2 either. While it would help with users of specific packages, without those users needing to know any specific details about the workaround, it won't cover all use cases - since we don't necessarily know all the different packages that might need to provide a drop-in - and also it could *add* confusion in some cases. For example, if someone is using a custom network-based libnss module, it would work on any system where they had the 'nis' package installed, but fail on any system where it wasn't installed - regardless of whether they are actually using nis for anything at all. That's the kind of thing that is incredibly painful to debug. This option also would require the 'nis' and 'libnss-ldap' packages to restart systemd- logind when they are installed, which (in the past at least) has sometimes been problematic. I know that option #1 is kind of the 'worst', since it essentially just gives up and removes the restriction from systemd-logind for everyone. However, I personally think it's the best option. If/when we do start providing systemd-userdbd (and it's enabled by default), I think we should move the lifted restriction over to it, instead of systemd- logind. But for now we should just modify systemd-logind to allow network access, IMHO. Since this is *theoretically* related to security, I'd like to get the Ubuntu security team's opinion on the change. I've cc'ed them on this bug. @mbiebl, what do you think? I really don't know what the best approach is, either for Debian or for Ubuntu. And obviously, if you (or anyone) has other suggestions I'm happy to hear them. And finally just FTR, I personally think upstream systemd should just remove the restriction (specifically, I mean remove IPAddressDeny=any) from systemd-userdbd.service. That service already funnels all systemd requests for user data into a single isolated process, I think it's overkill to also restrict that process from network access, when it's so common to have NSS-based network authentication mechanisms. However, Lennart's made his opinion known[1], and I'd prefer not to be the person who tries to argue with him to change his mind. [1]: https://github.com/systemd/systemd/issues/15705#issuecomment-624125354 ** Changed in: systemd (Ubuntu) Status: Won't Fix => Confirmed ** Description changed: [impact] starting in focal, systemd-logind runs sandboxed without any network access, which breaks any configuration that uses remote servers for user data, e.g. ldap, nis, etc A more full discussion is available in the upstream bug report as well as the debian bug report, see other info section below [test case] many possible ways to reproduce this; there are reproducers in some of the bugs reported before that are caused by this, e.g. bug 1915502 or bug 1916235 [regression
[Touch-packages] [Bug 1944621] [NEW] sshd in chroot has regression with glibc 2.34
Public bug reported: A regression to sshd running in a chroot exists under the following conditions: 1) sshd was built with glibc 2.34 2) sshd is running with a kernel that does not define the close_range syscall (kernel <= 5.8) 3) /proc/self/fd does not exist in the chroot The glibc 2.34 implementation of fallback_closefrom fails if /proc/self/fd is not present, which is a valid sshd use case. ** Affects: openssh (Ubuntu) Importance: Undecided Assignee: William Wilson (jawn-smith) Status: New ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => William Wilson (jawn-smith) -- 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/1944621 Title: sshd in chroot has regression with glibc 2.34 Status in openssh package in Ubuntu: New Bug description: A regression to sshd running in a chroot exists under the following conditions: 1) sshd was built with glibc 2.34 2) sshd is running with a kernel that does not define the close_range syscall (kernel <= 5.8) 3) /proc/self/fd does not exist in the chroot The glibc 2.34 implementation of fallback_closefrom fails if /proc/self/fd is not present, which is a valid sshd use case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1944621/+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 1692066] Re: [Request] Libreswan plugin for Network Manager
Hi, I've created the package if someone would like to review it. https://launchpad.net/~sagiben/+archive/ubuntu/network-manager-libreswan Thanks, Sagi. -- 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/1692066 Title: [Request] Libreswan plugin for Network Manager Status in libreswan package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Hello! I have the need to use Libreswan instead of strongswan to connect to an IPSec IKEv1 XAuth VPN in main mode without a group. Thing is strongswan doesn't support this configuration, so I explicitally need it. Nonetheless, libreswan is as developed as strongswan and it's widely used. using config files in /etc (ipsec.conf and .secrets) it's possible to correctly configure ipsec/libreswan, but needlessly to say, having the possibility to manage it via a GUI is 100 times better (and easier for "normal" users). In the current repositories (Zesty) I only found the libreswan's ipsec binaries (package libreswan), but not the network manager plugin (sources are available on github). I've tried to compile them, but I'm afraid they use a different path pattern than Ubuntu, so without making changes it's not possible to succesfully install it from sources. Thanks LibreSwan NetworkManager plugin sources: https://github.com/NetworkManager/network-manager-libreswan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreswan/+bug/1692066/+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 1944595] Re: text cursor
** Package changed: ubuntu => 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/1944595 Title: text cursor Status in xorg package in Ubuntu: New Bug description: When I click anywhere on the screen, I can see a text cursor in ṕoints where I shouldn't be able to write, such as youtube video titles. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 22 13:16:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.26, 5.11.0-34-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c9) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:876b] InstallationDate: Installed on 2021-07-15 (68 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=ce4e86ab-9ad3-41e8-aff3-3a08cdd0279d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1203 dmi.board.asset.tag: Default string dmi.board.name: PRIME A520M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1203:bd10/23/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnPRIMEA520M-K:rvrRevX.0x: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: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1944595/+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 1944595] [NEW] text cursor
You have been subscribed to a public bug: When I click anywhere on the screen, I can see a text cursor in ṕoints where I shouldn't be able to write, such as youtube video titles. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 22 13:16:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.26, 5.11.0-34-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c9) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Picasso [1043:876b] InstallationDate: Installed on 2021-07-15 (68 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=ce4e86ab-9ad3-41e8-aff3-3a08cdd0279d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1203 dmi.board.asset.tag: Default string dmi.board.name: PRIME A520M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1203:bd10/23/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnPRIMEA520M-K:rvrRevX.0x: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: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu -- text cursor https://bugs.launchpad.net/bugs/1944595 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 687689] Re: Audacity ruins bluetooth
** Changed in: audacity Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/687689 Title: Audacity ruins bluetooth Status in Audacity: Invalid Status in audacity package in Ubuntu: Incomplete Status in portaudio package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Invalid Bug description: Binary package hint: audacity Apparently Audacity is not smart enough to know that it's running under a Gnome environment. Everything in terms of audio devices is managed quite well with pulseaudio, bluetooth-applet, and other Gnome desktop infrastructure. It tries to hard and breaks it. It tries to hack into my bluetooth in a vain attempt to find a headset or something like that and it ruins my bluetooth support in the desktop. I am no longer able to send files or use bluetooth in anyway. First thing it does when you launch it is that it does nothing. It'll just hang. You click on the icon in the menu and you won't get any feedback. Even if you run it from the command line it will give no feedback and display no errors. It just hangs. Then you kill it and restart it a couple times and it launches successfully. Sorta. Besides the globalmenu bug reported in another report it displays this error on my terminal: $ audacity bt_audio_service_open: connect() failed: Connection refused (111) bt_audio_service_open: connect() failed: Connection refused (111) bt_audio_service_open: connect() failed: Connection refused (111) bt_audio_service_open: connect() failed: Connection refused (111) Cannot connect to server socket err = No such file or directory Cannot connect to server socket jack server is not running or cannot be started Expression 'stream->capture.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 3653 Here is the errors reported by dmesg: [ 807.086761] EXT4-fs (dm-0): re-mounted. Opts: commit=0 [ 812.790151] usb 6-1: USB disconnect, address 2 [ 812.790881] btusb_intr_complete: hci0 urb 88010e8e1600 failed to resubmit (19) [ 812.790905] btusb_bulk_complete: hci0 urb 88010e8e1c00 failed to resubmit (19) [ 812.791892] btusb_bulk_complete: hci0 urb 8801185a93c0 failed to resubmit (19) [ 812.792064] btusb_send_frame: hci0 urb 8800c0872e40 submission failed [ 813.322598] usb 6-1: new full speed USB device using uhci_hcd and address 3 [ 900.790130] usb 6-1: USB disconnect, address 3 [ 900.790753] btusb_intr_complete: hci0 urb 8800cba0d6c0 failed to resubmit (19) [ 900.790784] btusb_bulk_complete: hci0 urb 8800c0805d80 failed to resubmit (19) [ 900.791836] btusb_bulk_complete: hci0 urb 8800c0805180 failed to resubmit (19) [ 900.792039] btusb_send_frame: hci0 urb 8800c08ddf00 submission failed [ 900.807505] bluetooth-apple[2004]: segfault at a ip 7f65d520c9ee sp 7fffba728880 error 4 in libdbusmenu-glib.so.1.0.17[7f65d5208000+1] [ 901.320309] usb 6-1: new full speed USB device using uhci_hcd and address 4 [ 1308.540165] usb 6-1: USB disconnect, address 4 [ 1308.541015] btusb_intr_complete: hci0 urb 8800c0b18840 failed to resubmit (19) [ 1308.541045] btusb_bulk_complete: hci0 urb 8800c099eb40 failed to resubmit (19) [ 1308.542097] btusb_bulk_complete: hci0 urb 8800c0b180c0 failed to resubmit (19) [ 1308.542300] btusb_send_frame: hci0 urb 88010f313540 submission failed At that point my bluetooth support is broken and thus Audacity will successfully open. After hitting ctrl-f to work around the globalmenu bug (even though I am not using global menu) I can then edit files and such. Save them. Everything works. Of course I can no longer connect to the internet through my phone, send files, upload ringtones, use my bluetooth headset, etc. To work around you can remove the USB bluetooth adapter if you use a external one, plug it back in, and launch bluetooth-applet from the command line and it should be working again. It's not the end of the world, but Audacity should be configured to work properly in the default environment. I suggest eliminating Alsa and bluetooth support and have it not try to fight proper daemons handle it as they do a much better job. At least with PA and Bluetooth. I don't know how well Jack supports bluetooth audio devices, but Audacity really should not be allowed to do this sort of thing. I understand that it seems like a nice feature to be able to use a headset outside of Gnome, but it seems to be fundamentally incompatible with having a bluetooth adapter that is able to work with any other device. For people that may run into this problem in the future through Google or whatever here is two work arounds I suggest: 1. Remove or otherwise disable all your bluetooth radio prior to
[Touch-packages] [Bug 687689]
Closing this bug as it works for me (Xubuntu 20.04) and we've not seen any reports of this problem for many years. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/687689 Title: Audacity ruins bluetooth Status in Audacity: Invalid Status in audacity package in Ubuntu: Incomplete Status in portaudio package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Invalid Bug description: Binary package hint: audacity Apparently Audacity is not smart enough to know that it's running under a Gnome environment. Everything in terms of audio devices is managed quite well with pulseaudio, bluetooth-applet, and other Gnome desktop infrastructure. It tries to hard and breaks it. It tries to hack into my bluetooth in a vain attempt to find a headset or something like that and it ruins my bluetooth support in the desktop. I am no longer able to send files or use bluetooth in anyway. First thing it does when you launch it is that it does nothing. It'll just hang. You click on the icon in the menu and you won't get any feedback. Even if you run it from the command line it will give no feedback and display no errors. It just hangs. Then you kill it and restart it a couple times and it launches successfully. Sorta. Besides the globalmenu bug reported in another report it displays this error on my terminal: $ audacity bt_audio_service_open: connect() failed: Connection refused (111) bt_audio_service_open: connect() failed: Connection refused (111) bt_audio_service_open: connect() failed: Connection refused (111) bt_audio_service_open: connect() failed: Connection refused (111) Cannot connect to server socket err = No such file or directory Cannot connect to server socket jack server is not running or cannot be started Expression 'stream->capture.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 3653 Here is the errors reported by dmesg: [ 807.086761] EXT4-fs (dm-0): re-mounted. Opts: commit=0 [ 812.790151] usb 6-1: USB disconnect, address 2 [ 812.790881] btusb_intr_complete: hci0 urb 88010e8e1600 failed to resubmit (19) [ 812.790905] btusb_bulk_complete: hci0 urb 88010e8e1c00 failed to resubmit (19) [ 812.791892] btusb_bulk_complete: hci0 urb 8801185a93c0 failed to resubmit (19) [ 812.792064] btusb_send_frame: hci0 urb 8800c0872e40 submission failed [ 813.322598] usb 6-1: new full speed USB device using uhci_hcd and address 3 [ 900.790130] usb 6-1: USB disconnect, address 3 [ 900.790753] btusb_intr_complete: hci0 urb 8800cba0d6c0 failed to resubmit (19) [ 900.790784] btusb_bulk_complete: hci0 urb 8800c0805d80 failed to resubmit (19) [ 900.791836] btusb_bulk_complete: hci0 urb 8800c0805180 failed to resubmit (19) [ 900.792039] btusb_send_frame: hci0 urb 8800c08ddf00 submission failed [ 900.807505] bluetooth-apple[2004]: segfault at a ip 7f65d520c9ee sp 7fffba728880 error 4 in libdbusmenu-glib.so.1.0.17[7f65d5208000+1] [ 901.320309] usb 6-1: new full speed USB device using uhci_hcd and address 4 [ 1308.540165] usb 6-1: USB disconnect, address 4 [ 1308.541015] btusb_intr_complete: hci0 urb 8800c0b18840 failed to resubmit (19) [ 1308.541045] btusb_bulk_complete: hci0 urb 8800c099eb40 failed to resubmit (19) [ 1308.542097] btusb_bulk_complete: hci0 urb 8800c0b180c0 failed to resubmit (19) [ 1308.542300] btusb_send_frame: hci0 urb 88010f313540 submission failed At that point my bluetooth support is broken and thus Audacity will successfully open. After hitting ctrl-f to work around the globalmenu bug (even though I am not using global menu) I can then edit files and such. Save them. Everything works. Of course I can no longer connect to the internet through my phone, send files, upload ringtones, use my bluetooth headset, etc. To work around you can remove the USB bluetooth adapter if you use a external one, plug it back in, and launch bluetooth-applet from the command line and it should be working again. It's not the end of the world, but Audacity should be configured to work properly in the default environment. I suggest eliminating Alsa and bluetooth support and have it not try to fight proper daemons handle it as they do a much better job. At least with PA and Bluetooth. I don't know how well Jack supports bluetooth audio devices, but Audacity really should not be allowed to do this sort of thing. I understand that it seems like a nice feature to be able to use a headset outside of Gnome, but it seems to be fundamentally incompatible with having a bluetooth adapter that is able to work with any other device. For people that may run into this problem in the future through Google or whatever here is two work arounds I suggest: 1. Remove or
[Touch-packages] [Bug 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap
This bug was fixed in the package ubuntu-settings - 21.10.4 --- ubuntu-settings (21.10.4) impish; urgency=medium [ Olivier Tilloy ] * ubuntu-settings.gsettings-override: - Update the dock's gsetting override to pin the launcher for the firefox snap (LP: #1943840). -- Sebastien Bacher Wed, 22 Sep 2021 11:39:23 +0200 ** Changed in: ubuntu-settings (Ubuntu Impish) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1943840 Title: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap Status in ubuntu-meta package in Ubuntu: Fix Committed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-meta source package in Impish: Fix Committed Status in ubuntu-release-upgrader source package in Impish: Confirmed Status in ubuntu-settings source package in Impish: Fix Released Bug description: Per Canonical's distribution agreement with Mozilla, we're making the snap¹ the default installation of firefox on desktop ISOs starting with Ubuntu 21.10. The snap is built and published for amd64, armhf and arm64. It is jointly maintained by Mozilla and the Ubuntu desktop team, and published by Mozilla. This requires updating the desktop-minimal seed, as well as ubuntu- release-upgrader. ¹ https://snapcraft.io/firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+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 1944606] [NEW] [EDIFIER X3 R, recording] Microphone is not detected as an audio input
Public bug reported: Device doesn't appear in the input options inside gnome sound controls. It appears in pavucontrol, but there is no port associated to it, and no sound is captured. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amanda 2204 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Unity Date: Wed Sep 22 14:46:42 2021 InstallationDate: Installed on 2021-09-09 (13 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: EDIFIER X3 R Symptom_Type: None of the above Title: [EDIFIER X3 R, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/30/2021 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0TMFFT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd03/30/2021:br1.4:svnDellInc.:pnVostro5402:pvr:sku0A03:rvnDellInc.:rn0TMFFT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5402 dmi.product.sku: 0A03 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1944606 Title: [EDIFIER X3 R, recording] Microphone is not detected as an audio input Status in alsa-driver package in Ubuntu: New Bug description: Device doesn't appear in the input options inside gnome sound controls. It appears in pavucontrol, but there is no port associated to it, and no sound is captured. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amanda 2204 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Unity Date: Wed Sep 22 14:46:42 2021 InstallationDate: Installed on 2021-09-09 (13 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: EDIFIER X3 R Symptom_Type: None of the above Title: [EDIFIER X3 R, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/30/2021 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0TMFFT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd03/30/2021:br1.4:svnDellInc.:pnVostro5402:pvr:sku0A03:rvnDellInc.:rn0TMFFT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5402 dmi.product.sku: 0A03 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1944606/+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 1916485] Re: test -x fails inside shell scripts in containers
I took the liberty to clean up this bug and mark things as Invalid/Fix Released as needed. Hopefully I got everything right, but feel free to reopen/re-classify a task if there's something wrong. Thanks. ** Changed in: libseccomp (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: libseccomp (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: New => Invalid -- 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/1916485 Title: test -x fails inside shell scripts in containers Status in Ubuntu on IBM z Systems: Invalid Status in docker.io package in Ubuntu: Invalid Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Released Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: Invalid Status in libseccomp source package in Xenial: Fix Released Status in runc source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: Invalid Status in libseccomp source package in Bionic: Fix Released Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: Invalid Status in libseccomp source package in Focal: Fix Released Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: Won't Fix Status in libseccomp source package in Groovy: Won't Fix Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: Invalid Status in libseccomp source package in Hirsute: Fix Released Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ sudo tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt
[Touch-packages] [Bug 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap
ubuntu-meta (1.472) impish; urgency=medium * Refreshed dependencies * Added dmidecode to standard [riscv64] * Added gnome-initial-setup to desktop-minimal-recommends [riscv64], desktop-recommends [riscv64] * Added language-selector-common to desktop, desktop-minimal, desktop- raspi * Added open-vm-tools to server-raspi-recommends [arm64], server- recommends [arm64] * Added ubuntu-report to desktop-minimal-recommends [riscv64], desktop- recommends [riscv64] * Removed firefox from desktop-minimal-recommends [amd64 arm64 armhf ppc64el s390x], desktop-recommends [amd64 arm64 armhf ppc64el s390x] * Removed language-selector-common from standard * Removed xul-ext-ubufox from desktop-minimal-recommends, desktop- recommends -- Olivier Tilloy Wed, 22 Sep 2021 11:09:00 +0200 ** Changed in: ubuntu-meta (Ubuntu Impish) Status: Confirmed => Fix Committed ** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1943840 Title: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap Status in ubuntu-meta package in Ubuntu: Fix Committed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-meta source package in Impish: Fix Committed Status in ubuntu-release-upgrader source package in Impish: Confirmed Status in ubuntu-settings source package in Impish: New Bug description: Per Canonical's distribution agreement with Mozilla, we're making the snap¹ the default installation of firefox on desktop ISOs starting with Ubuntu 21.10. The snap is built and published for amd64, armhf and arm64. It is jointly maintained by Mozilla and the Ubuntu desktop team, and published by Mozilla. This requires updating the desktop-minimal seed, as well as ubuntu- release-upgrader. ¹ https://snapcraft.io/firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+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 1916485] Re: test -x fails inside shell scripts in containers
** Changed in: docker.io (Ubuntu Bionic) Status: New => Fix Released ** Changed in: docker.io (Ubuntu Focal) Status: New => Fix Released ** Changed in: docker.io (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: docker.io (Ubuntu Bionic) Status: Fix Released => Invalid ** Changed in: docker.io (Ubuntu Xenial) Status: Won't Fix => Invalid ** Changed in: docker.io (Ubuntu Focal) Status: Fix Released => Invalid ** Changed in: docker.io (Ubuntu Hirsute) Status: Fix Released => Invalid ** Changed in: libseccomp (Ubuntu Xenial) Status: New => Fix Released ** Changed in: libseccomp (Ubuntu Bionic) Status: New => Fix Released ** Changed in: libseccomp (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in Ubuntu on IBM z Systems: New Status in docker.io package in Ubuntu: Invalid Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: Invalid Status in libseccomp source package in Xenial: Fix Released Status in runc source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: Invalid Status in libseccomp source package in Bionic: Fix Released Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: Invalid Status in libseccomp source package in Focal: Fix Released Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: Won't Fix Status in libseccomp source package in Groovy: Won't Fix Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: Invalid Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ sudo tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
** Changed in: docker.io (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1916485 Title: test -x fails inside shell scripts in containers Status in Ubuntu on IBM z Systems: New Status in docker.io package in Ubuntu: Invalid Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: Invalid Status in libseccomp source package in Xenial: Fix Released Status in runc source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: Invalid Status in libseccomp source package in Bionic: Fix Released Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: Invalid Status in libseccomp source package in Focal: Fix Released Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: Won't Fix Status in libseccomp source package in Groovy: Won't Fix Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: Invalid Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ sudo tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
** Changed in: runc (Ubuntu Xenial) Status: New => Invalid -- 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/1916485 Title: test -x fails inside shell scripts in containers Status in Ubuntu on IBM z Systems: New Status in docker.io package in Ubuntu: Invalid Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: Invalid Status in libseccomp source package in Xenial: Fix Released Status in runc source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: Invalid Status in libseccomp source package in Bionic: Fix Released Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: Invalid Status in libseccomp source package in Focal: Fix Released Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: Won't Fix Status in libseccomp source package in Groovy: Won't Fix Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: Invalid Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ sudo tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not
[Touch-packages] [Bug 1934393] Re: systemd-logind network access is blocked, and breaks remote authentication configurations
** Description changed: [impact] starting in focal, systemd-logind runs sandboxed without any network access, which breaks any configuration that uses remote servers for user data, e.g. ldap, nis, etc A more full discussion is available in the upstream bug report as well as the debian bug report, see other info section below [test case] many possible ways to reproduce this; there are reproducers in some of the bugs reported before that are caused by this, e.g. bug 1915502 or bug 1916235 [regression potential] failure to authenticate when using remote user data, incorrect authentication, security issues due to un-sandboxing of systemd-logind [scope] this is needed in f and later before focal, systemd-logind was not sandboxed so this did not apply [other info] - this isn't actually a bug in systemd, this is a by-design security - feature, and the intended upstream design is for systemd-logind to talk - to systemd-userdb, so that systemd-logind can remain network-sandboxed - while systemd-userdb performs any needed network access for user/auth - data. However, Debian and Ubuntu don't enable/provide systemd-userdb, so - that design does not work for Debian/Ubuntu. + this isn't actually a bug in systemd, this is a by-design security feature; see links below (and/or comment 13 in this bug) to upstream comments about how systemd's position is that no NSS module should ever perform network access, and any NSS module that does needs to also adjust the restrictions of systemd services such as systemd-logind, systemd-userdbd, and possibly others that might need to make NSS calls into glibc. + https://github.com/systemd/systemd/issues/7074#issuecomment-338157851 + https://github.com/systemd/systemd/issues/15705#issuecomment-624125354 - this also can cause systemd-udevd failures in some cases as well, - apparently (based on upstream and debian discussion comments) + this may also can cause systemd-udevd failures in some cases as well. + https://github.com/systemd/systemd/pull/7343#issuecomment-344800313 For reference, upstream discussion around the systemd-logind sandboxing specifically: https://github.com/systemd/systemd/issues/7074 upstream updated doc PR explaining the upstream position: https://github.com/systemd/systemd/pull/7343 Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1934393 Title: systemd-logind network access is blocked, and breaks remote authentication configurations Status in systemd: Fix Released Status in nis package in Ubuntu: Confirmed Status in openldap package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Status in nis package in Debian: Fix Released Bug description: [impact] starting in focal, systemd-logind runs sandboxed without any network access, which breaks any configuration that uses remote servers for user data, e.g. ldap, nis, etc A more full discussion is available in the upstream bug report as well as the debian bug report, see other info section below [test case] many possible ways to reproduce this; there are reproducers in some of the bugs reported before that are caused by this, e.g. bug 1915502 or bug 1916235 [regression potential] failure to authenticate when using remote user data, incorrect authentication, security issues due to un-sandboxing of systemd-logind [scope] this is needed in f and later before focal, systemd-logind was not sandboxed so this did not apply [other info] this isn't actually a bug in systemd, this is a by-design security feature; see links below (and/or comment 13 in this bug) to upstream comments about how systemd's position is that no NSS module should ever perform network access, and any NSS module that does needs to also adjust the restrictions of systemd services such as systemd-logind, systemd-userdbd, and possibly others that might need to make NSS calls into glibc. https://github.com/systemd/systemd/issues/7074#issuecomment-338157851 https://github.com/systemd/systemd/issues/15705#issuecomment-624125354 this may also can cause systemd-udevd failures in some cases as well. https://github.com/systemd/systemd/pull/7343#issuecomment-344800313 For reference, upstream discussion around the systemd-logind sandboxing specifically: https://github.com/systemd/systemd/issues/7074 upstream updated doc PR explaining the upstream position: https://github.com/systemd/systemd/pull/7343 Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1934393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1934393] Re: systemd-logind network access is blocked, and breaks remote authentication configurations
> @Dan: have you actually confirmed, that building and running userdbd solves those issues with NIS and LDAP? sorry for the delay in getting back to this. So, you're correct, userdb doesn't actually help this, it only moves the problem. While systemd-userdbd.service does (currently, at least) allow AF_INET and AF_INET6, I missed that it also includes IPAddressDeny=any which results in the problem existing there as well. So if we include systemd-userdbd in Debian/Ubuntu, then the network- restricted systemd-logind problem is simply moved to systemd-userdbd. I will note that I did verify, if systemd-logind is running with its default restrictions and systemd-userdbd is also running without its IPAddressDeny=any restriction, the issue is fixed; systemd-logind does correctly get the user record from NIS through systemd-userdbd. I also seem to have misunderstood Lennart's position on this; after re- reading his statements[1] it seems that his position is that *all* systemd services should be locked down (or at least, both systemd-logind and systemd-userdbd) and the responsibility for poking holes in one (or both, or more) of those services' restrictions is on NIS and any other NSS library that requires network access. So enabling systemd-userdbd won't help with this bug, unless we want to diverge from upstream by removing its IPAddressDeny=any restriction. But we could just as easily remove that from systemd-logind (along with adding AF_INET and AF_INET6 to it). [1]: https://github.com/systemd/systemd/issues/7074#issuecomment-338157851 https://github.com/systemd/systemd/issues/15705#issuecomment-624125354 ** Bug watch added: github.com/systemd/systemd/issues #15705 https://github.com/systemd/systemd/issues/15705 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1934393 Title: systemd-logind network access is blocked, and breaks remote authentication configurations Status in systemd: Fix Released Status in nis package in Ubuntu: Confirmed Status in openldap package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Status in nis package in Debian: Fix Released Bug description: [impact] starting in focal, systemd-logind runs sandboxed without any network access, which breaks any configuration that uses remote servers for user data, e.g. ldap, nis, etc A more full discussion is available in the upstream bug report as well as the debian bug report, see other info section below [test case] many possible ways to reproduce this; there are reproducers in some of the bugs reported before that are caused by this, e.g. bug 1915502 or bug 1916235 [regression potential] failure to authenticate when using remote user data, incorrect authentication, security issues due to un-sandboxing of systemd-logind [scope] this is needed in f and later before focal, systemd-logind was not sandboxed so this did not apply [other info] this isn't actually a bug in systemd, this is a by-design security feature; see links below (and/or comment 13 in this bug) to upstream comments about how systemd's position is that no NSS module should ever perform network access, and any NSS module that does needs to also adjust the restrictions of systemd services such as systemd-logind, systemd-userdbd, and possibly others that might need to make NSS calls into glibc. https://github.com/systemd/systemd/issues/7074#issuecomment-338157851 https://github.com/systemd/systemd/issues/15705#issuecomment-624125354 this may also can cause systemd-udevd failures in some cases as well. https://github.com/systemd/systemd/pull/7343#issuecomment-344800313 For reference, upstream discussion around the systemd-logind sandboxing specifically: https://github.com/systemd/systemd/issues/7074 upstream updated doc PR explaining the upstream position: https://github.com/systemd/systemd/pull/7343 Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1934393/+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 1940505] Re: monero FTBFS on riscv64
** Changed in: binutils (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1940505 Title: monero FTBFS on riscv64 Status in binutils: Fix Released Status in binutils package in Ubuntu: Invalid Status in monero package in Ubuntu: Fix Released Bug description: monero FTBFS on riscv64 due to toolchain issues: [ 64%] Linking CXX executable signature_fuzz_tests cd "/<>/obj-riscv64-linux-gnu/tests/fuzz" && /usr/bin/cmake -E cmake_link_script CMakeFiles/signature_fuzz_tests.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -DNO_AES -fno-strict-aliasing -std=c++11 -D_GNU_SOURCE -Wall -Wextra -Wpointer-arith -Wundef -Wvla -Wwrite-strings -Wno-error=extra -Wno-error=deprecated-declarations -Wno-unused-parameter -Wno-unused-variable -Wno-error=unused-variable -Wno-error=undef -Wno-error=uninitialized -Wlogical-op -Wno-error=maybe-uninitialized -Wno-error=cpp -Wno-reorder -Wno-missing-field-initializers -fPIC -Wformat -Wformat-security -fstack-protector -fstack-protector-strong -fstack-clash-protection -fno-strict-aliasing -ftemplate-depth=900 -Wl,-Bsymbolic-functions -Wl,-z,relro -pie -Wl,-z,relro -Wl,-z,now -Wl,-z,noexecstack -rdynamic CMakeFiles/signature_fuzz_tests.dir/signature.cpp.o CMakeFiles/signature_fuzz_tests.dir/fuzzer.cpp.o -o signature_fuzz_tests ../../lib/libwallet.a ../../src/cryptonote_core/libcryptonote_core.a ../../src/p2p/libp2p.a ../../contrib/epee/src/libepee.a ../../src/device/libdevice.a -Wl,-Bstatic -lrt -Wl,-Bdynamic -ldl ../../src/rpc/librpc_base.a ../../src/mnemonics/libmnemonics.a ../../src/device_trezor/libdevice_trezor.a ../../src/cryptonote_core/libcryptonote_core.a ../../src/multisig/libmultisig.a ../../src/blockchain_db/libblockchain_db.a ../../external/db_drivers/liblmdb/liblmdb.a ../../src/ringct/libringct.a ../../src/cryptonote_basic/libcryptonote_basic.a ../../src/device/libdevice.a -lhidapi-libusb ../../src/ringct/libringct_basic.a ../../src/blocks/libblocks.a ../../src/checkpoints/libcheckpoints.a ../../src/hardforks/libhardforks.a ../../src/net/libnet.a ../../src/common/libcommon.a ../../src/crypto/libcncrypto.a ../../contrib/epee/src/libepee.a ../../external/easylogging++/libeasylogging.a -lrandomx -lunbound -lboost_regex -lboost_date_time -lssl -lcrypto -lzmq -lpgm -lnorm -lgssapi_krb5 -lsodium ../../src/libversion.a -lminiupnpc -lboost_chrono -lboost_serialization -lboost_filesystem -lboost_system -lboost_thread -lboost_program_options -Wl,-Bstatic -lrt -Wl,-Bdynamic -ldl -latomic ../../external/db_drivers/liblmdb/liblmdb.a(mdb.c.o): in function `mdb_node_add': ./obj-riscv64-linux-gnu/external/db_drivers/liblmdb/./external/db_drivers/liblmdb/mdb.c:8245:(.text+0x44e6): relocation truncated to fit: R_RISCV_JAL against `mdb_assert_fail.constprop.0' collect2: error: ld returned 1 exit status make[3]: *** [tests/fuzz/CMakeFiles/signature_fuzz_tests.dir/build.make:166: tests/fuzz/signature_fuzz_tests] Error 1 make[3]: Leaving directory '/<>/obj-riscv64-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:4165: tests/fuzz/CMakeFiles/signature_fuzz_tests.dir/all] Error 2 make[2]: Leaving directory '/<>/obj-riscv64-linux-gnu' make[1]: *** [Makefile:163: all] Error 2 make[1]: Leaving directory '/<>/obj-riscv64-linux-gnu' dh_auto_build: error: cd obj-riscv64-linux-gnu && make -j1 "INSTALL=install --strip-program=true" VERBOSE=1 returned exit code 2 make: *** [debian/rules:47: binary-arch] Error 25 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1940505/+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 1944436] Re: Please backport support for "close_range" syscall
I think the long test case in #5 now works. Note that later versions of crun have worked around the problem: https://github.com/containers/crun/pull/672 Still worth fixing, though, I think, as it is likely to cause further problems as more code starts to use close_range. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1944436 Title: Please backport support for "close_range" syscall Status in libseccomp package in Ubuntu: New Bug description: Please backport support for the "close_range" syscall .. may be as simple as cherrypicking https://github.com/seccomp/libseccomp/commit/01e5750e7c84bb14e5a5410c924bed519209db06 from upstream. I've hit problems running buildah in a systemd-nspawn container, but this will probably affect people trying to run modern code in other container systems as well, e.g. docker. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libseccomp2 2.5.1-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Xpra Date: Tue Sep 21 15:10:54 2021 InstallationDate: Installed on 2017-01-08 (1717 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libseccomp UpgradeStatus: Upgraded to focal on 2021-09-02 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1944436/+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 1944436] Re: Please backport support for "close_range" syscall
Still working out kinks in the above, but here's a simpler one. Needs
running in an nspawn container again (steps 1-2 above); should either
succeed (no output) or print "function not implemented", but without
seccomp support nspawn will block it and it will print "not permitted"
#include
#include
#include
int main()
{
if(syscall(436, 0, 0, 0)) {
perror("close_range");
exit(1);
}
exit(0);
}
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1944436
Title:
Please backport support for "close_range" syscall
Status in libseccomp package in Ubuntu:
New
Bug description:
Please backport support for the "close_range" syscall .. may be as
simple as cherrypicking
https://github.com/seccomp/libseccomp/commit/01e5750e7c84bb14e5a5410c924bed519209db06
from upstream. I've hit problems running buildah in a systemd-nspawn
container, but this will probably affect people trying to run modern
code in other container systems as well, e.g. docker.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libseccomp2 2.5.1-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133
Uname: Linux 5.4.0-84-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: Xpra
Date: Tue Sep 21 15:10:54 2021
InstallationDate: Installed on 2017-01-08 (1717 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: libseccomp
UpgradeStatus: Upgraded to focal on 2021-09-02 (19 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1944436/+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 1944436] Re: Please backport support for "close_range" syscall
It's not going to be simple I'm afraid, at least for the original
problem! "scmp_sys_resolver close_range" will quickly test whether
current seccomp has support for close_range (prints "-1" if not
supported, "436" otherwise - at least on x86_64.) Ubuntu seccomp
maintainers have been pretty happy SRUing this sort of thing before -
it's a running problem, and the changes are trivial.
Outline of a reproducer for my original problem would be something like:
1. download and unpack
https://partner-images.canonical.com/core/focal/current/ubuntu-focal-core-cloudimg-amd64-root.tar.gz
2. cd to the rootfs directory and start a container with "systemd-nspawn"
3. Add podman/buildah PPA:
. /etc/os-release
echo "deb
https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_${VERSION_ID}/
/" | sudo tee /etc/apt/sources.list.d/devel:kubic:libcontainers:stable.list
curl -L
"https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_${VERSION_ID}/Release.key;
| sudo apt-key add -
sudo apt-get update
sudo apt-get -y upgrade
4. apt-get -y install buildah
5. create scratch container and copy in busybox
ctr=$(buildah from scratch)
buildah copy $ctr /bin/busybox
6. check EOF handling
echo foo | buildah run $ctr /busybox cat
Without the patch, this should fail to return to the prompt, as the missing
syscall seems to interfere with buildah's ability to to process EOF; with the
patch it should return to the prompt.
In the event of failure there should also be messages logged about
"close_range" being unsupported.
Above is untested - I'll double-check it and flesh it out when
time/health permits, but hopefully it has some utility. There are
probably simpler test cases involving docker, but that's not my area...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1944436
Title:
Please backport support for "close_range" syscall
Status in libseccomp package in Ubuntu:
New
Bug description:
Please backport support for the "close_range" syscall .. may be as
simple as cherrypicking
https://github.com/seccomp/libseccomp/commit/01e5750e7c84bb14e5a5410c924bed519209db06
from upstream. I've hit problems running buildah in a systemd-nspawn
container, but this will probably affect people trying to run modern
code in other container systems as well, e.g. docker.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libseccomp2 2.5.1-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133
Uname: Linux 5.4.0-84-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: Xpra
Date: Tue Sep 21 15:10:54 2021
InstallationDate: Installed on 2017-01-08 (1717 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: libseccomp
UpgradeStatus: Upgraded to focal on 2021-09-02 (19 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1944436/+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 1944468] Re: Electron applications all crash upon launch
It's due to the new glibc, confirmed using vscode download and install using https://code.visualstudio.com/sha/download?build=stable=linux-deb-x64 $ code on an hirsute machine it works correctly, add an impish source and upgrade libc6 and it fails to start with the error reported ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Package changed: ubuntu => glibc (Ubuntu) ** Tags added: electron rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1944468 Title: Electron applications all crash upon launch Status in glibc package in Ubuntu: New Bug description: Just a few weeks ago, I noticed the .deb version of Visual Studio Code crashing upon launch. I also noticed Element (matrix client) also would crash. The only thing these applications have in common is electron. I was hoping this would get noticed by someone and that the issue would be figured out, but I guess that person had to be me. Erroneously-filed bug 1943568 exhibits the same issues. Experimenting with Visual Studio Code provided this: [347381:0921/133026.728654:ERROR:proxy_config_service_linux.cc(608)] inotify_init failed: Too many open files (24) [347419:0921/133026.764752:ERROR:file_path_watcher_linux.cc(326)] inotify_init() failed: Too many open files (24) [main 2021-09-21T20:30:26.930Z] update#setState idle [347381:0921/133027.009472:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159 [347381:0921/133027.323205:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159 [347381:0921/133027.690827:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159 [347490:0921/133027.728195:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader [347381:0921/133027.879310:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159 [347495:0921/133027.894439:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader [347381:0921/133028.049455:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159 [347499:0921/133028.063977:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader [347381:0921/133028.216114:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159 [347511:0921/133028.222585:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [347381:0921/133028.384052:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159 [347515:0921/133028.442903:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [347381:0921/133028.596590:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159 [347519:0921/133028.602088:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [347381:0921/133028.749373:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159 [347381:0921/133028.749401:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye. Server response: Server response: Illegal instruction (core dumped) Atom provided this: [347834:0921/133121.907198:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye. Unexpected crash report id length Failed to get crash dump id. Report Id: Unexpected crash report id length Failed to get crash dump id. Report Id: Illegal instruction (core dumped) When either application was provided "--no-sandbox" at the command line, they would run normally. However, Element does not pass that via command line, so I was unable to use the workaround for that. Upon investigating the runtime dependencies for Element, Atom, and VSCode, the one thing they had in common was libgtk-3-0, and the date of 2021-09-03 for publishing coincides with the time in which these errors started to appear. Another workaround, other than the "--no-sandbox" usage, is to use the snap version of the apps if available, or flatpak. These provide their own versions of these dependencies, which tells me these .deb-based applications are affected by libgtk-3-0. Granted, those applications are not in the Ubuntu repository, however, many people (including myself) rely on those to function correctly. It would be very bad if Electron apps failed to function when 21.10 is released. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libgtk-3-0 3.24.30-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-lowlatency 5.13.13 Uname: Linux 5.13.0-16-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Sep 21 13:25:17 2021 InstallationDate: Installed on 2021-03-20 (184 days
[Touch-packages] [Bug 1944453] Re: PDF documents signed with DocuSign show the error message "The document contains no pages"
Thanks, trying using the example from https://sec.report/lux/doc/102081415.pdf the issue is fixed in hirsute ** Package changed: evince (Ubuntu) => poppler (Ubuntu) ** Changed in: poppler (Ubuntu) Importance: Undecided => High ** Changed in: poppler (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1944453 Title: PDF documents signed with DocuSign show the error message "The document contains no pages" Status in poppler package in Ubuntu: Fix Released Bug description: Steps to reproduce: --- 1. Open a document signed with DocuSign Expected behaviour: --- Document opens fine Actual behaviour: --- Evince refuses to display the document, with the error message "The document contains no pages". If document is opened with `pdftotext`, the output is: ``` Syntax Error: Gen inside xref table too large (bigger than INT_MAX) Syntax Error: Invalid XRef entry 3 Syntax Error: Top-level pages object is wrong type (null) Command Line Error: Wrong page range given: the first page (1) can not be after the last page (0). ``` Other information --- This appears to be a bug in libpoppler, described at https://stackoverflow.com/questions/66636441/pdf2image-library- failing-to-read-pdf-signed-using-docusign and https://gitlab.freedesktop.org/poppler/poppler/-/issues/1014 . I believe that bumping the version of Poppler and/or Evince will solve the issue, though I have no way to test this as compiling from source is a significant undertaking. I do not have a public sample document that I could share, but examples of DocuSigned documents should be available online. Ubuntu version: 20.04 LTS (up to date) Evince version: 3.36.10 (official package) Poppler version: 0.86.1-0ubuntu1 (official package) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1944453/+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 1944107] Re: No archive files for static compilation are included in the -dev package
** Changed in: libdrm (Ubuntu) Status: New => Fix Committed ** Changed in: libdrm (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1944107 Title: No archive files for static compilation are included in the -dev package Status in libdrm package in Ubuntu: Fix Committed Bug description: There are no libdrm.a, libdrm_amdgpu.a, etc. files, so it is not possible to compile statically against this library. See attached debdiff to solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1944107/+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 1944453] [NEW] PDF documents signed with DocuSign show the error message "The document contains no pages"
You have been subscribed to a public bug: Steps to reproduce: --- 1. Open a document signed with DocuSign Expected behaviour: --- Document opens fine Actual behaviour: --- Evince refuses to display the document, with the error message "The document contains no pages". If document is opened with `pdftotext`, the output is: ``` Syntax Error: Gen inside xref table too large (bigger than INT_MAX) Syntax Error: Invalid XRef entry 3 Syntax Error: Top-level pages object is wrong type (null) Command Line Error: Wrong page range given: the first page (1) can not be after the last page (0). ``` Other information --- This appears to be a bug in libpoppler, described at https://stackoverflow.com/questions/66636441/pdf2image-library-failing- to-read-pdf-signed-using-docusign and https://gitlab.freedesktop.org/poppler/poppler/-/issues/1014 . I believe that bumping the version of Poppler and/or Evince will solve the issue, though I have no way to test this as compiling from source is a significant undertaking. I do not have a public sample document that I could share, but examples of DocuSigned documents should be available online. Ubuntu version: 20.04 LTS (up to date) Evince version: 3.36.10 (official package) Poppler version: 0.86.1-0ubuntu1 (official package) ** Affects: poppler (Ubuntu) Importance: High Status: Fix Released -- PDF documents signed with DocuSign show the error message "The document contains no pages" https://bugs.launchpad.net/bugs/1944453 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1944542] Re: [Lenovo IdeaPad 5 15IIL05] very slow
Thanks for the bug report. Can you explain what is slow? Is it just screen updates? Also please open a Terminal window and run: top Do you see any high CPU users? ** Summary changed: - very slow + [Lenovo IdeaPad 5 15IIL05] very slow ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1944542 Title: [Lenovo IdeaPad 5 15IIL05] very slow Status in Ubuntu: Incomplete Bug description: my system is very slow ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 22 12:07:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3fd9] InstallationDate: Installed on 2020-11-27 (298 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81YK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-36-generic root=UUID=a181ec35-bea8-4216-8066-0bb0b9f90034 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2020 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvrDPCN39WW:bd01/15/2020:br1.39:efr1.39:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:skuLENOVO_MT_81YK_BU_idea_FM_IdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1944542/+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 1944542] [NEW] very slow
Public bug reported: my system is very slow ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 22 12:07:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3fd9] InstallationDate: Installed on 2020-11-27 (298 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81YK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-36-generic root=UUID=a181ec35-bea8-4216-8066-0bb0b9f90034 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2020 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvrDPCN39WW:bd01/15/2020:br1.39:efr1.39:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:skuLENOVO_MT_81YK_BU_idea_FM_IdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages 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/1944542 Title: very slow Status in xorg package in Ubuntu: New Bug description: my system is very slow ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 22 12:07:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3fd9] InstallationDate: Installed on 2020-11-27 (298 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81YK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-36-generic root=UUID=a181ec35-bea8-4216-8066-0bb0b9f90034 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2020 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvrDPCN39WW:bd01/15/2020:br1.39:efr1.39:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:skuLENOVO_MT_81YK_BU_idea_FM_IdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati:
[Touch-packages] [Bug 1944468] Re: Electron applications all crash upon launch
I suspect these may be related: https://github.com/electron/electron/pull/30893 "fix: crash when launching app with systemd v249" https://github.com/microsoft/vscode/issues/132609 "Electron 14+ required? Potential systemd 249 / nVidia issue" Electron patch backported from Chromium: https://github.com/electron/electron/commit/1d531f29eeb8392195262bea038abed75fb51b8c Also, have you considered this could be caused by a recent Electron update that has made its way into these applications? https://www.electronjs.org/releases/stable Electron Sandboxing Overview https://www.electronjs.org/docs/tutorial/sandbox ** Bug watch added: github.com/microsoft/vscode/issues #132609 https://github.com/microsoft/vscode/issues/132609 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1944468 Title: Electron applications all crash upon launch Status in gtk+3.0 package in Ubuntu: New Bug description: Just a few weeks ago, I noticed the .deb version of Visual Studio Code crashing upon launch. I also noticed Element (matrix client) also would crash. The only thing these applications have in common is electron. I was hoping this would get noticed by someone and that the issue would be figured out, but I guess that person had to be me. Erroneously-filed bug 1943568 exhibits the same issues. Experimenting with Visual Studio Code provided this: [347381:0921/133026.728654:ERROR:proxy_config_service_linux.cc(608)] inotify_init failed: Too many open files (24) [347419:0921/133026.764752:ERROR:file_path_watcher_linux.cc(326)] inotify_init() failed: Too many open files (24) [main 2021-09-21T20:30:26.930Z] update#setState idle [347381:0921/133027.009472:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159 [347381:0921/133027.323205:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159 [347381:0921/133027.690827:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159 [347490:0921/133027.728195:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader [347381:0921/133027.879310:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159 [347495:0921/133027.894439:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader [347381:0921/133028.049455:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159 [347499:0921/133028.063977:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is swiftshader [347381:0921/133028.216114:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159 [347511:0921/133028.222585:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [347381:0921/133028.384052:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159 [347515:0921/133028.442903:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [347381:0921/133028.596590:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159 [347519:0921/133028.602088:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled [347381:0921/133028.749373:ERROR:gpu_process_host.cc(1007)] GPU process exited unexpectedly: exit_code=159 [347381:0921/133028.749401:FATAL:gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye. Server response: Server response: Illegal instruction (core dumped) Atom provided this: [347834:0921/133121.907198:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye. Unexpected crash report id length Failed to get crash dump id. Report Id: Unexpected crash report id length Failed to get crash dump id. Report Id: Illegal instruction (core dumped) When either application was provided "--no-sandbox" at the command line, they would run normally. However, Element does not pass that via command line, so I was unable to use the workaround for that. Upon investigating the runtime dependencies for Element, Atom, and VSCode, the one thing they had in common was libgtk-3-0, and the date of 2021-09-03 for publishing coincides with the time in which these errors started to appear. Another workaround, other than the "--no-sandbox" usage, is to use the snap version of the apps if available, or flatpak. These provide their own versions of these dependencies, which tells me these .deb-based applications are affected by libgtk-3-0. Granted, those applications are not in the Ubuntu repository, however, many people (including myself) rely on those to function correctly. It would be very bad if Electron apps failed to function when 21.10 is released. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libgtk-3-0 3.24.30-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-lowlatency 5.13.13
