[Touch-packages] [Bug 1985887] Re: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s)
okay, I can reproduce this issue in Xorg as well. `stress-ng --stack 0 --timeout 300` and I can see Tue Aug 16 03:13:49 PM CST 2022 ./memory.pressure some avg10=64.25 avg60=28.75 avg300=7.33 total=23575913 full avg10=62.74 avg60=28.13 avg300=7.17 total=23107632 ./vte-spawn-9dbf6c12-a335-464f-b337-c3b5b6d1ac30.scope/memory.pressure some avg10=63.79 avg60=29.06 avg300=7.44 total=23418603 full avg10=62.34 avg60=28.46 avg300=7.29 total=22962690 ./gnome-terminal-server.service/memory.pressure some avg10=3.99 avg60=1.22 avg300=0.28 total=1098016 full avg10=3.99 avg60=1.22 avg300=0.28 total=1098016 already over 50% as Aug 16 15:13:49 ubuntu systemd-oomd[795]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-9dbf6c12-a335-464f-b337-c3b5b6d1ac30.scope due to memory pressure for /user.slice/user-1001.slice/user@1001.service being 70.58% > 50.00% for > 20s with reclaim activity ** Summary changed: - systemd kills gnome-shell or gnome-terminal if gnome is in Wayland mode + systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s) ** Description changed: [Steps to reproduce] 0. Install Jammy image 1. open gnome terminal 2. issue stress_ng or Canonical certification tool checkbox as "checkbox-cli run com.canonical.certification::memory/memory_stress_ng" + or + "stress-ng --stack 0 --timeout 300" 3. Terminal or Gnome-shell will be killed by systemd-oomd - It's because all stressors are under same cgroup. + It's because all stressors are under same cgroup belongs to terminal. - So far, it only happen in Wayland. + Both Wayland and Xorg can reproduce. over ssh and in multi-user.target work good. -- 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/1985887 Title: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s) Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: New Bug description: [Steps to reproduce] 0. Install Jammy image 1. open gnome terminal 2. issue stress_ng or Canonical certification tool checkbox as "checkbox-cli run com.canonical.certification::memory/memory_stress_ng" or "stress-ng --stack 0 --timeout 300" 3. Terminal or Gnome-shell will be killed by systemd-oomd It's because all stressors are under same cgroup belongs to terminal. Both Wayland and Xorg can reproduce. over ssh and in multi-user.target work good. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1985887/+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 1985887] Re: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s)
systemd-oomd doesn't care about the slices other than user slice, it's why the sshd won't be killed but it also use a lot of memory: /sys/fs/cgroup/user.slice/user-1001.slice/session-4.scope/memory.pressure some avg10=69.94 avg60=69.56 avg300=43.64 total=202010660 full avg10=69.07 avg60=68.73 avg300=43.07 total=199371697 Tue Aug 16 03:32:11 PM CST 2022 Dry Run: no Swap Used Limit: 90.00% Default Memory Pressure Limit: 60.00% Default Memory Pressure Duration: 20s System Context: Memory: Used: 3.5G Total: 3.5G Swap: Used: 1.9G Total: 1.9G Swap Monitored CGroups: Memory Pressure Monitored CGroups: Path: /user.slice/user-1001.slice/user@1001.service Memory Pressure Limit: 50.00% Pressure: Avg10: 25.40 Avg60: 24.64 Avg300: 12.24 Total: 1min 15s Current Memory Usage: 74.5M Memory Min: 0B Memory Low: 0B Pgscan: 24554223 Last Pgscan: 24533954 --- only user@1001.service in monitoring score. -- 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/1985887 Title: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s) Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: New Bug description: [Steps to reproduce] 0. Install Jammy image 1. open gnome terminal 2. issue stress_ng or Canonical certification tool checkbox as "checkbox-cli run com.canonical.certification::memory/memory_stress_ng" or "stress-ng --stack 0 --timeout 300" 3. Terminal or Gnome-shell will be killed by systemd-oomd It's because all stressors are under same cgroup belongs to terminal. Both Wayland and Xorg can reproduce. over ssh and in multi-user.target work good. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1985887/+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 1986631] [NEW] package linux-image-5.14.0-1048-oem 5.14.0-1048.55 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: happened on startup ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1048-oem 5.14.0-1048.55 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 13 11:35:12 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-10-07 (312 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.14.0-1048-oem 5.14.0-1048.55 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to focal on 2022-08-13 (2 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1986631 Title: package linux-image-5.14.0-1048-oem 5.14.0-1048.55 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: happened on startup ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1048-oem 5.14.0-1048.55 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 13 11:35:12 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-10-07 (312 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.14.0-1048-oem 5.14.0-1048.55 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to focal on 2022-08-13 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1986631/+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 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)
Hello Heinrich, yes, very gladly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1907878 Title: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found) Status in ifupdown package in Ubuntu: Fix Released Bug description: Syslog error: nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir: not found I think it's because of this line: if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface <- this is interpreted as a 'mystatedir' command and fails interface=$IFACE if [ ! "$interface" ]; then Perhaps the intention was to 'export mystatedir statedir ...' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+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 1980386] Re: `radeonsi_dri.so` driver missing on riscv64
@tjaalton it's 21.2.6-0ubuntu0.1~20.04.2 in focal: https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/23235579 https://launchpad.net/ubuntu/+source/mesa -- 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/1980386 Title: `radeonsi_dri.so` driver missing on riscv64 Status in llvm-toolchain-14 package in Ubuntu: New Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-14 source package in Jammy: New Status in mesa source package in Jammy: Confirmed Status in llvm-toolchain-14 source package in Kinetic: New Status in mesa source package in Kinetic: Confirmed Bug description: The package is missing the `radeonsi` driver, with the reasoning that LLVM is not implemented on the architecture: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995618 That said, it works just fine on focal, where it is still enabled. Without this driver there's no way to use AMD graphics cards on RISC-V. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.0.1-1ubuntu2 ProcVersionSignature: User Name 5.15.0-1007.7-generic 5.15.30 Uname: Linux 5.15.0-1007-generic riscv64 ApportVersion: 2.20.11-0ubuntu82 Architecture: riscv64 CasperMD5CheckResult: unknown Date: Thu Jun 30 15:48:11 2022 ProcCpuinfoMinimal: processor: 3 hart : 4 isa : rv64imafdc mmu : sv39 uarch: sifive,u74-mc ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-14/+bug/1980386/+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 1895426] Re: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1895426 Title: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Invalid Bug description: linux-firmware bug ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.3 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tirtha 1397 F pulseaudio CasperMD5CheckResult: skip Date: Sun Sep 13 11:45:12 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-09-13 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox PackageArchitecture: all ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=a24d343d-9753-4460-ac8f-43882d4197c7 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.3 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1895426/+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 1986660] [NEW] Phased update configuration flags not documented in apt.conf(5)
Public bug reported: Hi, https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345 describes Dir::Etc::machine-id, APT::Get::Always-Include-Phased-Updates and APT::Get::Never-Include-Phased-Updates. I expected these to be documented in apt.conf(5) which I treat as a definitive reference to configuration options, but they aren't there. ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Phased update configuration flags not documented in apt.conf + Phased update configuration flags not documented in apt.conf(5) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1986660 Title: Phased update configuration flags not documented in apt.conf(5) Status in apt package in Ubuntu: New Bug description: Hi, https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345 describes Dir::Etc::machine-id, APT::Get::Always-Include-Phased- Updates and APT::Get::Never-Include-Phased-Updates. I expected these to be documented in apt.conf(5) which I treat as a definitive reference to configuration options, but they aren't there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1986660/+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 1986663] [NEW] Missing run-time dependency on package python3-sip
Public bug reported: ubuntu-bug on Kinetic Kudu crashes with: $ ubuntu-bug Traceback (most recent call last): File "/usr/share/apport/apport-kde", line 19, in import sip ModuleNotFoundError: No module named 'sip' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/share/apport/apport-kde", line 58, in apport.fatal( NameError: name 'apport' is not defined Please, add python3-sip to the list of run-time dependencies. Best regards Heinrich ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Missing dependency for package sip + Missing dependency for package python3-sip ** Summary changed: - Missing dependency for package python3-sip + Missing run-time dependency on package python3-sip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1986663 Title: Missing run-time dependency on package python3-sip Status in apport package in Ubuntu: New Bug description: ubuntu-bug on Kinetic Kudu crashes with: $ ubuntu-bug Traceback (most recent call last): File "/usr/share/apport/apport-kde", line 19, in import sip ModuleNotFoundError: No module named 'sip' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/share/apport/apport-kde", line 58, in apport.fatal( NameError: name 'apport' is not defined Please, add python3-sip to the list of run-time dependencies. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1986663/+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 1986660] Re: Phased update configuration flags not documented in apt.conf(5)
Just to be clear: apt.conf(5) is not the definitive source, that is (fsvo reference) in /use/share/doc/examples/configure-index. The manual page only documents popular options whereas the index lists them all (apt test suite type checks against it). Phased updates are documented in apt_preferences, but the documentation has not been updated for the new implementation either. They are also, and primarily, documented in the discourse post as that was requested as the preferred documentation medium. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1986660 Title: Phased update configuration flags not documented in apt.conf(5) Status in apt package in Ubuntu: New Bug description: Hi, https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345 describes Dir::Etc::machine-id, APT::Get::Always-Include-Phased- Updates and APT::Get::Never-Include-Phased-Updates. I expected these to be documented in apt.conf(5) which I treat as a definitive reference to configuration options, but they aren't there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1986660/+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 1986521] Re: ssh client spins if output fd closed
And I can confirm that the patch at https://bugzilla.mindrot.org/attachment.cgi?id=3581 applies cleanly and fixes this issue. -- 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/1986521 Title: ssh client spins if output fd closed Status in openssh package in Ubuntu: New Bug description: The OpenSSH package 8.9p1 as shipped with U22.04 (8.9p1-3) suffers from the bug described at https://bugzilla.mindrot.org/show_bug.cgi?id=3411 and https://bugzilla.mindrot.org/show_bug.cgi?id=3405 A command such as "xterm -e 'ssh -f remote.host sleep 60'" will pop up an xterm, ask for whatever authentication is needed, close the xterm, and leave the ssh client spinning consuming CPU time for 60 seconds before it exits. It should leave the ssh client idle for 60 seconds. Many uses of ssh to launch graphical applications will be caught by this bug. This is fixed in OpenSSH 9.0p1 as the first bugfix listed in its release notes at https://www.openssh.com/txt/release-9.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1986521/+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 1986660] Re: Phased update configuration flags not documented in apt.conf(5)
That's not really discoverable as a reference though. I wouldn't expect "examples" to contain a definitive reference, and nor a Discourse post about a feature that as far as I know isn't pointed to from any definitive documentation. Same with apt_preferences - I do expect to find information about scoring and the syntax of preferences.d/ files in there, but if I want a reference to a configuration option, it's not obvious to look there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1986660 Title: Phased update configuration flags not documented in apt.conf(5) Status in apt package in Ubuntu: New Bug description: Hi, https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345 describes Dir::Etc::machine-id, APT::Get::Always-Include-Phased- Updates and APT::Get::Never-Include-Phased-Updates. I expected these to be documented in apt.conf(5) which I treat as a definitive reference to configuration options, but they aren't there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1986660/+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 1986660] Re: Phased update configuration flags not documented in apt.conf(5)
Looking at apt.conf(5), it does read as if it's the definitive reference, too, and the examples file is just an example. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1986660 Title: Phased update configuration flags not documented in apt.conf(5) Status in apt package in Ubuntu: New Bug description: Hi, https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345 describes Dir::Etc::machine-id, APT::Get::Always-Include-Phased- Updates and APT::Get::Never-Include-Phased-Updates. I expected these to be documented in apt.conf(5) which I treat as a definitive reference to configuration options, but they aren't there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1986660/+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 1945225] Re: udev produces unpredictable net names when PCI device is a bridge
I was not able to make the .link approach work, even in an installed environment. I fought with it for a while during spurts of machine access. Without that, I was not able to move on to the next step of trying to insert it into a commissioning script. -- 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/1945225 Title: udev produces unpredictable net names when PCI device is a bridge Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Status in systemd source package in Hirsute: Fix Released Status in systemd source package in Impish: Fix Released Bug description: [Impact] udev can produce unpredictable network interface names by default when multiple devices map to the same slot due to an intermediate bridge. On an Nvidia DGX2 system, I see the following when booting a system with udev 245.4-4ubuntu3.13: ubuntu@akis:~$ ls /sys/class/net enp134s0f0 enp6s0 ens103 ens107 eth3 eth9 enp134s0f1 ens102 ens106 eth1eth7 lo For each ens* device, there is a sibling eth* device that maps to the same slot because both devices are behind the same bridge. Unpredictable names present well known problems, but I'll describe a specific issue I'm having. We currently do automated network testing that MAAS deploys a system and then configures 2 specific NICs on the system. While MAAS does take care to always restore the names used during commissioning (eth3 will always be the same NIC on every deploy), these names can change each time the system is commissioned. So today we need to go in and edit the NIC names manually in MAAS any time the system is re-commissioned. [Test Case] Boot with kernel option net.naming-scheme=v247; verify that all network interfaces receive predictable names. [Fix] This issue was addressed upstream by adding a new v247 naming scheme that detects this scenario and disables usage of slot-based names for these devices. Obviously changing the default naming scheme in a released LTS series could break users. However, we could introduce the v247 scheme in a focal SRU, and keep the default scheme of v245 (via -Ddefault-net-naming-scheme=v245). Users impacted by this could then opt-in to the v247 scheme by passing net.naming-scheme=v247 or net.naming-scheme=latest on the kernel command line. I could add this to DGX2 systems via a kernel_opts MAAS tag to always get predictable names during commissioning. [Regression Risk] This would change the behavior of any users who select net.naming-scheme=latest, since the latest will now be v247 and not v245. I'm not sure why an existing Ubuntu user would be doing that though - AFAICT, Ubuntu currently always defaults to the latest scheme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1945225/+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 1980386] Re: `radeonsi_dri.so` driver missing on riscv64
oh right, 22.0.5 hasn't been backported yet anyway, if llvm is enabled, it'll essentially break swrast for riscv64.. if that's a tradeoff you can live with, then okay -- 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/1980386 Title: `radeonsi_dri.so` driver missing on riscv64 Status in llvm-toolchain-14 package in Ubuntu: New Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-14 source package in Jammy: New Status in mesa source package in Jammy: Confirmed Status in llvm-toolchain-14 source package in Kinetic: New Status in mesa source package in Kinetic: Confirmed Bug description: The package is missing the `radeonsi` driver, with the reasoning that LLVM is not implemented on the architecture: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995618 That said, it works just fine on focal, where it is still enabled. Without this driver there's no way to use AMD graphics cards on RISC-V. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.0.1-1ubuntu2 ProcVersionSignature: User Name 5.15.0-1007.7-generic 5.15.30 Uname: Linux 5.15.0-1007-generic riscv64 ApportVersion: 2.20.11-0ubuntu82 Architecture: riscv64 CasperMD5CheckResult: unknown Date: Thu Jun 30 15:48:11 2022 ProcCpuinfoMinimal: processor: 3 hart : 4 isa : rv64imafdc mmu : sv39 uarch: sifive,u74-mc ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-14/+bug/1980386/+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 1986663] Re: Missing run-time dependency on package python3-sip
*** This bug is a duplicate of bug 1980553 *** https://bugs.launchpad.net/bugs/1980553 ** This bug has been marked a duplicate of bug 1980553 /usr/share/apport/apport-kde:NameError:/usr/share/apport/apport-kde@19:/usr/share/apport/apport-kde@58 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1986663 Title: Missing run-time dependency on package python3-sip Status in apport package in Ubuntu: New Bug description: ubuntu-bug on Kinetic Kudu crashes with: $ ubuntu-bug Traceback (most recent call last): File "/usr/share/apport/apport-kde", line 19, in import sip ModuleNotFoundError: No module named 'sip' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/share/apport/apport-kde", line 58, in apport.fatal( NameError: name 'apport' is not defined Please, add python3-sip to the list of run-time dependencies. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1986663/+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 1983794] Re: Evolution not deleting autosave files
** Changed in: evolution (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: gtk+3.0 (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) -- 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/1983794 Title: Evolution not deleting autosave files Status in evolution package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: New Bug description: Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1 was installed with the distribution on a new system and received settings imported from an earlier version on another computer. When composing an email, if the process takes long enough an autosave file is created as ~/.local/share/evolution/.evolution- composer.autosave-xx ("xx" is a random 6 character string). When the email is successfully sent, the autosave file SHOULD be deleted. It's not. When evolution is shut down and restarted I'm asked if I want to recover an unfinished email. Answering No to this will delete the autosave file, but otherwise it persists and the recovery query recurs the next time I open evolution. Other people are having the same issue, see https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome people aren't dealing with it, perhaps considering it a distro- specific bug. On a system used by many people this is a potential security issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1983794/+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 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1980937 Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise Status in alsa-driver package in Ubuntu: Confirmed Bug description: New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake- LP audio controller. When playing any audio, the internal speaker plays no sound except periodic loud crackling noise. The 3.5mm jack does not work either, producing the same craclking noise alongside some eletrical noise. HDMI audio skimmishly tested, but also gave no sound. Curiously, USB headphone (along with microphone) works perfectly, also the internal microphone. As attempts to fix the problem, I have tried the following separately, with no avail: - Installing some Ubuntu OEM version of the 5.17 kernel - Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject on github), reverted afterwards I found exactly the same problem reported in the Fedora community: https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound&p=1860086 As the pre-installed Windows has been destroyed, no further test on Windows has been done. Since USB headphone and internal microphone work, I think that there is no problem on the Intel Tiger Lake-LP controller and its driver. The bug probably lies elsewhere, like in the handling of ALC245 on this new laptop model. Thank you very much for your time and effort in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jul 7 10:59:22 2022 InstallationDate: Installed on 2022-06-29 (7 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 9.1 dmi.bios.vendor: HP dmi.bios.version: T37 Ver. 01.09.01 dmi.board.name: 8AB8 dmi.board.vendor: HP dmi.board.version: KBC Version 58.03.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.3 dmi.modalias: dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G8 Notebook PC dmi.product.sku: 6A3P3AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+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 1965439] Re: [SRU] kdesu fails to authenticate with sudo from Jammy
** Description changed: kdesu fails to authenticate with sudo from Jammy. See upstream bug: KDE bug: https://bugs.kde.org/show_bug.cgi?id=452532 Examples: Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. On entering the correct password authentication is refused, stating that possibly an incorrect password has been entered. It appears that kdesu fails to cope with the sudo config change in this commit: https://salsa.debian.org/sudo- team/sudo/-/commit/59db341d46aa4c26b54c1270e69f2562e7f3d751 kdesu was fixed in Debian with: https://tracker.debian.org/news/1330116/accepted-kdesu-5940-2-source- into-unstable/ and fixed in kinetic with: https://launchpad.net/ubuntu/+source/kdesu/5.94.0-0ubuntu2 The issue can be worked around by adding /etc/sudoers.d/kdesu-sudoers with the contents Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty [Impact] - * Users are unable to authenticate to and launch applications via kdesu. - * This should be backported to restore functionality that users expect. + * Users are unable to authenticate to and launch applications via kdesu. + * This should be backported to restore functionality that users expect. [Test Plan] - * Launch Kubuntu driver manager from system setting, launching + * Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. * Confirm that the application authentcate and launch as successfully as in previous releases. [Where problems could occur] - * Examples. + * While this update only returns sudo to its default behaviour (used in + previous releases and virtually all other distributions) for kdesu, care + should be taken to test some other applications that seek root + permissions to confirm that no unexpected consequences occur. ** Changed in: sudo (Ubuntu Kinetic) Status: Confirmed => Won't Fix ** Changed in: sudo (Ubuntu Jammy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: [SRU] kdesu fails to authenticate with sudo from Jammy Status in kdesu package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Fix Released Status in kdesu source package in Jammy: In Progress Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Won't Fix Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Fix Released Status in kubuntu-settings source package in Kinetic: Fix Released Status in sudo source package in Kinetic: Won't Fix Status in ubuntustudio-default-settings source package in Kinetic: Fix Released Status in kdesu package in Debian: Fix Released Bug description: kdesu fails to authenticate with sudo from Jammy. See upstream bug: KDE bug: https://bugs.kde.org/show_bug.cgi?id=452532 Examples: Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. On entering the correct password authentication is refused, stating that possibly an incorrect password has been entered. It appears that kdesu fails to cope with the sudo config change in this commit: https://salsa.debian.org/sudo- team/sudo/-/commit/59db341d46aa4c26b54c1270e69f2562e7f3d751 kdesu was fixed in Debian with: https://tracker.debian.org/news/1330116/accepted-kdesu-5940-2-source- into-unstable/ and fixed in kinetic with: https://launchpad.net/ubuntu/+source/kdesu/5.94.0-0ubuntu2 The issue can be worked around by adding /etc/sudoers.d/kdesu-sudoers with the contents Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty [Impact] * Users are unable to authenticate to and launch applications via kdesu. * This should be backported to restore functionality that users expect. [Test Plan] * Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. * Confirm that the application authentcate and launch
[Touch-packages] [Bug 1986660] Re: Phased update configuration flags not documented in apt.conf(5)
Yeah many options are not really for end users though so it's not all encompassing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1986660 Title: Phased update configuration flags not documented in apt.conf(5) Status in apt package in Ubuntu: New Bug description: Hi, https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345 describes Dir::Etc::machine-id, APT::Get::Always-Include-Phased- Updates and APT::Get::Never-Include-Phased-Updates. I expected these to be documented in apt.conf(5) which I treat as a definitive reference to configuration options, but they aren't there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1986660/+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 1980146] Re: dnsmasq often using 100% of CPU
Thanks for the information you provided. I set up a Ubuntu Jammy VM with ssh and dnsmasq running and unfortunately I cannot reproduce it just with that. There might be something else happening in your system. If you could provide information about all processes running in your system when this happens it would be great. It could at least serve as a lead for us to keep investigating this issue, right now I am not sure what's going on. ** Changed in: dnsmasq (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1980146 Title: dnsmasq often using 100% of CPU Status in dnsmasq package in Ubuntu: Incomplete Bug description: Release: 22.04 Codename: jammy Kernel: Linux 5.15.0-40-generic x86_64 ⏵ apt-cache policy dnsmasq Installed: 2.86-1.1ubuntu0.1 dnsmasq is caught in a loop after every dns request, resulting in 100% CPU usage for several minutes each time. This leads to a hot and lethargic computer. During this time thousands of the following messages (see below) are printed from strace. The loop tends to obsess on denied connections, but there are so many I'm not 100% sure. systemd-resolved is _not_ running, some bugs refer to that. ⏵ head /etc/dnsmasq.d/foo.conf address=/#/127.0.0.2 port=53 resolv-file=/var/run/NetworkManager/resolv.conf ⏵ sudo strace -p 3519 (dnsmasq) poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=6, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, events=POLLIN}, {fd=13, events=POLLIN}, {fd=14, events=POLLIN}], 9, -1) = 1 ([{fd=4, revents=POLLIN}]) recvmsg(4, {msg_name={sa_family=AF_INET, sin_port=htons(60224), sin_addr=inet_addr("127.0.0.1")}, msg_namelen=28 => 16, msg_iov=[{iov_base="\302\221\1\0\0\1\0\0\0\0\0\0\17classify- client\10ser"..., iov_len=4096}], msg_iovlen=1, msg_control=[{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO, cmsg_data={ipi_ifindex=if_nametoindex("lo"), ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], msg_controllen=32, msg_flags=0}, 0) = 54 ioctl(4, SIOCGIFNAME, {ifr_ifindex=1, ifr_name="lo"}) = 0 sendto(14, "\302\221\1\0\0\1\0\0\0\0\0\0\17classify-client\10ser"..., 54, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("127.0.0.53")}, 16) = 54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1980146/+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 1983794] Re: Evolution not deleting autosave files
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- 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/1983794 Title: Evolution not deleting autosave files Status in evolution package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1 was installed with the distribution on a new system and received settings imported from an earlier version on another computer. When composing an email, if the process takes long enough an autosave file is created as ~/.local/share/evolution/.evolution- composer.autosave-xx ("xx" is a random 6 character string). When the email is successfully sent, the autosave file SHOULD be deleted. It's not. When evolution is shut down and restarted I'm asked if I want to recover an unfinished email. Answering No to this will delete the autosave file, but otherwise it persists and the recovery query recurs the next time I open evolution. Other people are having the same issue, see https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome people aren't dealing with it, perhaps considering it a distro- specific bug. On a system used by many people this is a potential security issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1983794/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
The issue exists in the Firefox snap as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1784977 ** Bug watch added: Mozilla Bugzilla #1784977 https://bugzilla.mozilla.org/show_bug.cgi?id=1784977 -- 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/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in chromium-browser package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1949340/+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 1889443] Re: "ValueError: ['separator'] has no binary content" when running `apport-unpack /var/crash/...`
Fixed upstream: https://github.com/canonical/apport/commit/64820a0e2de0065d2ce08592bd1765169656c716 ** Changed in: apport Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1889443 Title: "ValueError: ['separator'] has no binary content" when running `apport-unpack /var/crash/...` Status in Apport: Fix Committed Status in apport package in Ubuntu: Confirmed Bug description: The crash file I'm using is as-produced by the system (on groovy), and appears to have an empty value for separator: $ grep separator /var/crash/_usr_bin_neomutt.1000.crash separator: Traceback (most recent call last): File "/usr/bin/apport-unpack", line 77, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 269, in extract_keys raise ValueError('%s has no binary content' % ValueError: ['separator'] has no binary content ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apport 2.20.11-0ubuntu42 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:117:1620030:2020-07-29 12:16:57.045274496 -0400:2020-07-29 12:19:15.559243636 -0400:/var/crash/_usr_bin_neomutt.1000.crash 640:1000:117:4399480:2020-07-23 10:30:21.433552906 -0400:2020-07-23 10:30:18.921508067 -0400:/var/crash/_usr_bin_pavucontrol.1000.crash 640:1000:117:29909:2020-07-29 12:19:15.603244279 -0400:2020-07-29 12:19:15.603244279 -0400:/var/crash/_usr_bin_apport-unpack.1000.crash CurrentDesktop: i3 Date: Wed Jul 29 12:22:54 2020 InstallationDate: Installed on 2019-05-07 (448 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to groovy on 2020-06-22 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1889443/+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 1661209] Re: apport-unpack crashes with ValueError: ['ProcEnviron', UserGroups'] has no binary content
*** This bug is a duplicate of bug 1889443 *** https://bugs.launchpad.net/bugs/1889443 This bug is fixed by https://github.com/canonical/apport/commit/64820a0e2de0065d2ce08592bd1765169656c716 So I will mark this bug as duplicate of bug #1889443. ** This bug has been marked a duplicate of bug 1889443 "ValueError: ['separator'] has no binary content" when running `apport-unpack /var/crash/...` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1661209 Title: apport-unpack crashes with ValueError: ['ProcEnviron', UserGroups'] has no binary content Status in Apport: Triaged Status in apport package in Ubuntu: Triaged Bug description: In bug #1661205 avahi-dameon repeatedly crashes, and causes apport to go into an infinite loop. However I suspect this is a problem with apport, because when I manually unpack the .crash I get: # apport-unpack /var/crash/_usr_sbin_avahi-daemon.0.crash /home/redacted/foo Traceback (most recent call last): File "/usr/bin/apport-unpack", line 73, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 270, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['ProcEnviron', 'UserGroups'] has no binary content Please find attached /var/crash/_usr_sbin_avahi-daemon.0.crash ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apport 2.20.3-0ubuntu8.2 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CrashReports: 640:0:122:14612:2017-02-02 10:48:08.638081761 +:2017-02-02 10:48:08.638081761 +:/var/crash/_usr_bin_apport-unpack.0.crash 640:0:122:1355374:2017-02-02 10:42:53.922800121 +:2017-02-02 10:48:08.582079751 +:/var/crash/_usr_sbin_avahi-daemon.0.crash CurrentDesktop: Unity Date: Thu Feb 2 10:51:34 2017 InstallationDate: Installed on 2016-10-31 (93 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1661209/+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 1986536] Re: Running ifup@ for all interfaces breaks no-auto-down
Can reproduce on Jammy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1986536 Title: Running ifup@ for all interfaces breaks no-auto-down Status in ifupdown package in Ubuntu: New Bug description: We (mythic-beasts.com) run a "Raspberry Pi cloud", consisting of Raspberry Pis with no SD card and an NFS root file system. This requires special considerations for shutting down, as bringing down eth0 will break the file system and cause the shutdown process to hang forever. ifupdown has a config option for exactly this situation: no-auto-down. We set this flag in /etc/network/interfaces.d/eth0. However, this flag only prevents `ifdown -a` from bringing down the interface; `ifdown eth0` still does. Unfortunately, ifup@eth0.service does exactly this when bringing down the system. This isn't an issue on Debian, because Debian only starts ifup@.service for services marked "allow-hotplug"; non-hotplug services are started and stopped by networking.service, which just uses `if{up,down} -a`. Ubuntu, on the other hand, brings up ifup@.service for all services marked auto. (This was an intentional change - see the Ubuntu ifupdown changelog.) As such, unless I'm missing something, there's no way on Ubuntu to have an interface that's automatically brought up on boot, but not automatically brought down on shutdown. Tested on bionic and focal: root@rpi-bionic-arm64:~# lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 root@rpi-bionic-arm64:~# apt-cache policy ifupdown ifupdown: Installed: 0.8.17ubuntu1.1 Candidate: 0.8.17ubuntu1.1 Version table: *** 0.8.17ubuntu1.1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages 100 /var/lib/dpkg/status 0.8.17ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages root@rpi-focal-arm64:~# lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 root@rpi-focal-arm64:~# apt-cache policy ifupdown ifupdown: Installed: 0.8.35ubuntu1 Candidate: 0.8.35ubuntu1 Version table: *** 0.8.35ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/universe arm64 Packages 100 /var/lib/dpkg/status I can't easily test on jammy, as we're not producing jammy images yet; but I'm happy to create one (or try upgrading a pi from focal) if people think it's likely to do something interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1986536/+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 1980386] Re: `radeonsi_dri.so` driver missing on riscv64
I suppose we may need to work with a PPA then. @xypron what do you think? -- 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/1980386 Title: `radeonsi_dri.so` driver missing on riscv64 Status in llvm-toolchain-14 package in Ubuntu: New Status in mesa package in Ubuntu: Confirmed Status in llvm-toolchain-14 source package in Jammy: New Status in mesa source package in Jammy: Confirmed Status in llvm-toolchain-14 source package in Kinetic: New Status in mesa source package in Kinetic: Confirmed Bug description: The package is missing the `radeonsi` driver, with the reasoning that LLVM is not implemented on the architecture: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995618 That said, it works just fine on focal, where it is still enabled. Without this driver there's no way to use AMD graphics cards on RISC-V. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.0.1-1ubuntu2 ProcVersionSignature: User Name 5.15.0-1007.7-generic 5.15.30 Uname: Linux 5.15.0-1007-generic riscv64 ApportVersion: 2.20.11-0ubuntu82 Architecture: riscv64 CasperMD5CheckResult: unknown Date: Thu Jun 30 15:48:11 2022 ProcCpuinfoMinimal: processor: 3 hart : 4 isa : rv64imafdc mmu : sv39 uarch: sifive,u74-mc ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-14/+bug/1980386/+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 1001035] Re: lightdm uses a hardcoded path to .xsession-errors, please make it configurable
Upstream feature request: https://github.com/canonical/lightdm/issues/95 ** Bug watch added: github.com/canonical/lightdm/issues #95 https://github.com/canonical/lightdm/issues/95 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1001035 Title: lightdm uses a hardcoded path to .xsession-errors, please make it configurable Status in Light Display Manager: Triaged Status in lightdm package in Ubuntu: Triaged Bug description: LightDM uses always $HOME/.xsession-errors as the log file because is harcoded in xsession.c. But sometimes you want to use a logfile outside your $HOME, suposse your $HOME is in an SSD and you want to minimize writes, so you want to put it in /tmp/${USER}_xsession-errors for example. If you try to make a $HOME/.xsession_errors -> /tmp/{$USER}_xsession-errors symlink to cheat LightDM, then LightDM will recreate the $HOME/.xsession_errors file and the hack will not work. LightDM _always_ recreates $HOME/.xsession_errors and you can't change it without recompiling. So, I think this log file needs to be configurable, or at least preserve the symlink if one is present. Ubuntu 12.04 LTS LightDM 1.2.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1001035/+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 1983794] Re: Evolution not deleting autosave files
** Changed in: evolution (Ubuntu) Importance: Undecided => Medium ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Medium -- 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/1983794 Title: Evolution not deleting autosave files Status in evolution package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1 was installed with the distribution on a new system and received settings imported from an earlier version on another computer. When composing an email, if the process takes long enough an autosave file is created as ~/.local/share/evolution/.evolution- composer.autosave-xx ("xx" is a random 6 character string). When the email is successfully sent, the autosave file SHOULD be deleted. It's not. When evolution is shut down and restarted I'm asked if I want to recover an unfinished email. Answering No to this will delete the autosave file, but otherwise it persists and the recovery query recurs the next time I open evolution. Other people are having the same issue, see https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome people aren't dealing with it, perhaps considering it a distro- specific bug. On a system used by many people this is a potential security issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1983794/+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 1971409] Re: value_copy: Assertion `arg->contents != nullptr' failed.
Looks like the specific upstream issue is https://github.deere.com/FOCUS/WineATL/blob/fab575865d1bbceedde12226d2517d17b20189bc/gdb/wine- add-symbol-file.py And there's a build for kinetic that contains the fix, which does actually install and work on jammy (since no other dependencies changed too much, at least not yet): https://github.com/microsoft/vscode- cpptools/issues/103#issuecomment-1151217772 ** Bug watch added: github.com/microsoft/vscode-cpptools/issues #103 https://github.com/microsoft/vscode-cpptools/issues/103 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1971409 Title: value_copy: Assertion `arg->contents != nullptr' failed. Status in gdb package in Ubuntu: Confirmed Bug description: When debugging RP2040 with vscode this assert makes gdb crash. This is a new assert, that wasn't present in gdb 11. The fix is easy, replace `if (!value_lazy (val))` to `if (!value_lazy (val) && arg->contents != nullptr) `. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971409/+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 1985887] Re: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s)
It seems that systemd-oomd is doing what it is supposed to do -- you're running a memory stress test that is exceeding the memory pressure limits set by systemd-oomd, so it is killing the offending cgroup(s). If you want to run the stress tests in a separate cgroup, try making a script called e.g. `stress.sh`, and execute the script with systemd-run: $ systemd-run --user ./stress.sh Further, you can always make changes to Ubuntu's default systemd-oomd configuration[1] if it better suits your stress testing environment. There are some complaints about the current state of "swap kill" in systemd-oomd, but that has been discussed in [2] and [3]. [1] https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html#ManagedOOMSwap=auto%7Ckill [2] https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159 [3] https://lists.ubuntu.com/archives/ubuntu-devel/2022-June/042116.html -- 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/1985887 Title: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s) Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: New Bug description: [Steps to reproduce] 0. Install Jammy image 1. open gnome terminal 2. issue stress_ng or Canonical certification tool checkbox as "checkbox-cli run com.canonical.certification::memory/memory_stress_ng" or "stress-ng --stack 0 --timeout 300" 3. Terminal or Gnome-shell will be killed by systemd-oomd It's because all stressors are under same cgroup belongs to terminal. Both Wayland and Xorg can reproduce. over ssh and in multi-user.target work good. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1985887/+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 1986705] [NEW] package base-files 12ubuntu4.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
Public bug reported: error with dpkg and base-files..12ubuntu.amd64.deb ProblemType: Package DistroRelease: Ubuntu 22.04 Package: base-files 12ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: base-files:amd64: Install base-files:amd64: Configure NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 16 13:20:40 2022 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2022-05-09 (99 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.4, unpackaged PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: base-files Title: package base-files 12ubuntu4.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: base-files (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1986705 Title: package base-files 12ubuntu4.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in base-files package in Ubuntu: New Bug description: error with dpkg and base-files..12ubuntu.amd64.deb ProblemType: Package DistroRelease: Ubuntu 22.04 Package: base-files 12ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: base-files:amd64: Install base-files:amd64: Configure NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 16 13:20:40 2022 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2022-05-09 (99 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.4, unpackaged PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: base-files Title: package base-files 12ubuntu4.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1986705/+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 1986705] Re: package base-files 12ubuntu4.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
This does not look like an Ubuntu bug. You have the most recent jammy version of dpkg installed on your system according to your bug report, however the upgrade failure shows an internal error when trying to invoke 'dpkg --valiate-version' from dpkg-maintscript-helper. What does `which dpkg` return on your system? ** Package changed: base-files (Ubuntu) => dpkg (Ubuntu) ** Changed in: dpkg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1986705 Title: package base-files 12ubuntu4.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in dpkg package in Ubuntu: Incomplete Bug description: error with dpkg and base-files..12ubuntu.amd64.deb ProblemType: Package DistroRelease: Ubuntu 22.04 Package: base-files 12ubuntu4.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: base-files:amd64: Install base-files:amd64: Configure NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 16 13:20:40 2022 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2022-05-09 (99 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.4, unpackaged PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: base-files Title: package base-files 12ubuntu4.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1986705/+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 1912256] Re: Missing channel binding prevents authentication to ActiveDirectory
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/cyrus-sasl2/+git/cyrus-sasl2/+merge/428422 -- 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/1912256 Title: Missing channel binding prevents authentication to ActiveDirectory Status in cyrus-sasl2 package in Ubuntu: In Progress Status in openldap package in Ubuntu: Confirmed Bug description: > Are you uncertain if your issue is really a bug? Effect is an authentication error. Root case is a "missing feature" (see below) and requires updating dependencies, downporting. > If you are certain this is a bug please include the source package the bug is in. It's in the interaction between three libraries: openldap, cyrus-sasl, krb5 > 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Broken in 18.04 and also in 20.10 (I guess it's also broken in anything inbetween) > 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center libsasl2-modules-gssapi-mit: 2.1.27+dfsg-2ubuntu1 ldap-utils: 2.4.53+dfsg-1ubuntu1.2 libgssapi-krb5-2: 1.17-10ubuntu0.1 > 3) What you expected to happen # kinit $ export LDAPSASL_CBINDING=tls-endpoint $ ldapwhoami -O minssf=0,maxssf=0 -N -Y GSSAPI -H ldaps:// SASL/GSSAPI authentication started SASL username: SASL SSF: 0 u: > 4) What happened instead SASL/GSSAPI authentication started ldap_sasl_interactive_bind_s: Invalid credentials (49) additional info: 80090346: LdapErr: DSID-0C090597, comment: AcceptSecurityContext error, data 80090346, v4563 --- Microsoft ActiveDirectory has "LDAP Channel Binding" and recommends activating this as a required feature. See https://access.redhat.com/articles/4661861 Authentication to any AD DC which has mandatory channel binding fails. Channel binding requires at least an update to cyrus-sasl, which is not in any release as far as I can see: https://github.com/cyrusimap/cyrus- sasl/commit/975edbb69070eba6b035f08776de771a129cfb57 It also needs this commit in openldap: https://git.openldap.org/openldap/openldap/-/commit/3cd50fa8b32a21040a9892e2a8a7a9dfc7541ce6 Which as far as I can tell is v2.5 (branch OPENLDAP_REL_ENG_2_5). RH also mentions it needs up-to-date krb5 libraries, but I can't tell what minimum version this needs. I can build all libraries from source, current master (except for krb5 where I've used 1.18.3) and can confirm that channel binding works when using those libraries. I'm not sure if Samba is affected, but at least adcli, ldap-utils, and I would guess by extension also SSSD and realmd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1912256/+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 1980146] Re: dnsmasq often using 100% of CPU
Spent the whole morning on it and finally figured it out—I had dnsmasq looking at the wrong DNS server because it was looking at the wrong resolv.conf: ⏵ cat /var/run/NetworkManager/resolv.conf # Generated by NetworkManager nameserver 127.0.0.53 I remember now that early on there were too many daemons managing DNS !! (NetworkManager, systemd-resolved, dnsmasq). Couldn't get them all happy so I removed systemd-resolved. That would be fine if there was something running at 127.0.0.53 but there wasn't since I'd uninstalled it. I needed the original (though dynamic) resolv.conf and found it at no-stub-resolv.conf: ⏵ head /etc/dnsmasq.d/foo.conf address=/#/127.0.0.2 port=53 # resolv-file=/var/run/NetworkManager/resolv.conf resolv-file=/var/run/NetworkManager/no-stub-resolv.conf This file has my correct DNS info from the router and now dnsmasq is working quietly as expected. I see there are other ways to configure things (NetworkManager can run dnsmasq too!) but I like this way because I can do everything in just one file. No need to instruct NetworkManager to write /etc/resolv.conf either. Was inclined to close this, but thinking about it, dnsmasq should not hammer a non-existent DNS server to the point of saturating the CPU. True, the server address was misconfigured but dnsmasq should check *at most* once every few seconds. Definitely needs a delay in there in this case. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1980146 Title: dnsmasq often using 100% of CPU Status in dnsmasq package in Ubuntu: Incomplete Bug description: Release: 22.04 Codename: jammy Kernel: Linux 5.15.0-40-generic x86_64 ⏵ apt-cache policy dnsmasq Installed: 2.86-1.1ubuntu0.1 dnsmasq is caught in a loop after every dns request, resulting in 100% CPU usage for several minutes each time. This leads to a hot and lethargic computer. During this time thousands of the following messages (see below) are printed from strace. The loop tends to obsess on denied connections, but there are so many I'm not 100% sure. systemd-resolved is _not_ running, some bugs refer to that. ⏵ head /etc/dnsmasq.d/foo.conf address=/#/127.0.0.2 port=53 resolv-file=/var/run/NetworkManager/resolv.conf ⏵ sudo strace -p 3519 (dnsmasq) poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=6, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, events=POLLIN}, {fd=13, events=POLLIN}, {fd=14, events=POLLIN}], 9, -1) = 1 ([{fd=4, revents=POLLIN}]) recvmsg(4, {msg_name={sa_family=AF_INET, sin_port=htons(60224), sin_addr=inet_addr("127.0.0.1")}, msg_namelen=28 => 16, msg_iov=[{iov_base="\302\221\1\0\0\1\0\0\0\0\0\0\17classify- client\10ser"..., iov_len=4096}], msg_iovlen=1, msg_control=[{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO, cmsg_data={ipi_ifindex=if_nametoindex("lo"), ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], msg_controllen=32, msg_flags=0}, 0) = 54 ioctl(4, SIOCGIFNAME, {ifr_ifindex=1, ifr_name="lo"}) = 0 sendto(14, "\302\221\1\0\0\1\0\0\0\0\0\0\17classify-client\10ser"..., 54, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("127.0.0.53")}, 16) = 54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1980146/+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 1912256] Re: Missing channel binding prevents authentication to ActiveDirectory
openldap in kinetic needs no further changes, marking that task as fix released. ** Changed in: openldap (Ubuntu) Status: Confirmed => Fix Released ** Also affects: cyrus-sasl2 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: openldap (Ubuntu Jammy) Importance: Undecided Status: New -- 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/1912256 Title: Missing channel binding prevents authentication to ActiveDirectory Status in cyrus-sasl2 package in Ubuntu: In Progress Status in openldap package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Jammy: New Status in openldap source package in Jammy: Fix Released Bug description: > Are you uncertain if your issue is really a bug? Effect is an authentication error. Root case is a "missing feature" (see below) and requires updating dependencies, downporting. > If you are certain this is a bug please include the source package the bug is in. It's in the interaction between three libraries: openldap, cyrus-sasl, krb5 > 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Broken in 18.04 and also in 20.10 (I guess it's also broken in anything inbetween) > 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center libsasl2-modules-gssapi-mit: 2.1.27+dfsg-2ubuntu1 ldap-utils: 2.4.53+dfsg-1ubuntu1.2 libgssapi-krb5-2: 1.17-10ubuntu0.1 > 3) What you expected to happen # kinit $ export LDAPSASL_CBINDING=tls-endpoint $ ldapwhoami -O minssf=0,maxssf=0 -N -Y GSSAPI -H ldaps:// SASL/GSSAPI authentication started SASL username: SASL SSF: 0 u: > 4) What happened instead SASL/GSSAPI authentication started ldap_sasl_interactive_bind_s: Invalid credentials (49) additional info: 80090346: LdapErr: DSID-0C090597, comment: AcceptSecurityContext error, data 80090346, v4563 --- Microsoft ActiveDirectory has "LDAP Channel Binding" and recommends activating this as a required feature. See https://access.redhat.com/articles/4661861 Authentication to any AD DC which has mandatory channel binding fails. Channel binding requires at least an update to cyrus-sasl, which is not in any release as far as I can see: https://github.com/cyrusimap/cyrus- sasl/commit/975edbb69070eba6b035f08776de771a129cfb57 It also needs this commit in openldap: https://git.openldap.org/openldap/openldap/-/commit/3cd50fa8b32a21040a9892e2a8a7a9dfc7541ce6 Which as far as I can tell is v2.5 (branch OPENLDAP_REL_ENG_2_5). RH also mentions it needs up-to-date krb5 libraries, but I can't tell what minimum version this needs. I can build all libraries from source, current master (except for krb5 where I've used 1.18.3) and can confirm that channel binding works when using those libraries. I'm not sure if Samba is affected, but at least adcli, ldap-utils, and I would guess by extension also SSSD and realmd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1912256/+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 1912256] Re: Missing channel binding prevents authentication to ActiveDirectory
openldap@jammy also needs no further changes ** Changed in: openldap (Ubuntu Jammy) Status: New => Fix Released -- 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/1912256 Title: Missing channel binding prevents authentication to ActiveDirectory Status in cyrus-sasl2 package in Ubuntu: In Progress Status in openldap package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Jammy: New Status in openldap source package in Jammy: Fix Released Bug description: > Are you uncertain if your issue is really a bug? Effect is an authentication error. Root case is a "missing feature" (see below) and requires updating dependencies, downporting. > If you are certain this is a bug please include the source package the bug is in. It's in the interaction between three libraries: openldap, cyrus-sasl, krb5 > 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Broken in 18.04 and also in 20.10 (I guess it's also broken in anything inbetween) > 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center libsasl2-modules-gssapi-mit: 2.1.27+dfsg-2ubuntu1 ldap-utils: 2.4.53+dfsg-1ubuntu1.2 libgssapi-krb5-2: 1.17-10ubuntu0.1 > 3) What you expected to happen # kinit $ export LDAPSASL_CBINDING=tls-endpoint $ ldapwhoami -O minssf=0,maxssf=0 -N -Y GSSAPI -H ldaps:// SASL/GSSAPI authentication started SASL username: SASL SSF: 0 u: > 4) What happened instead SASL/GSSAPI authentication started ldap_sasl_interactive_bind_s: Invalid credentials (49) additional info: 80090346: LdapErr: DSID-0C090597, comment: AcceptSecurityContext error, data 80090346, v4563 --- Microsoft ActiveDirectory has "LDAP Channel Binding" and recommends activating this as a required feature. See https://access.redhat.com/articles/4661861 Authentication to any AD DC which has mandatory channel binding fails. Channel binding requires at least an update to cyrus-sasl, which is not in any release as far as I can see: https://github.com/cyrusimap/cyrus- sasl/commit/975edbb69070eba6b035f08776de771a129cfb57 It also needs this commit in openldap: https://git.openldap.org/openldap/openldap/-/commit/3cd50fa8b32a21040a9892e2a8a7a9dfc7541ce6 Which as far as I can tell is v2.5 (branch OPENLDAP_REL_ENG_2_5). RH also mentions it needs up-to-date krb5 libraries, but I can't tell what minimum version this needs. I can build all libraries from source, current master (except for krb5 where I've used 1.18.3) and can confirm that channel binding works when using those libraries. I'm not sure if Samba is affected, but at least adcli, ldap-utils, and I would guess by extension also SSSD and realmd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1912256/+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 1979952] Re: Bind mount to NFS mount fails on Ubuntu 22.04
This upstream fix for this was backported to 251.4, which I am currently working on merging from Debian. ** Changed in: systemd (Ubuntu Kinetic) Status: Triaged => In Progress -- 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/1979952 Title: Bind mount to NFS mount fails on Ubuntu 22.04 Status in systemd: Unknown Status in systemd package in Ubuntu: In Progress Status in systemd source package in Jammy: New Status in systemd source package in Kinetic: In Progress Bug description: I have the following setup: - /data is an NFS mount. - /home is a bind mount to /data/home. Configured in /etc/fstab with these lines: $FILE_SERVER:/data /data nfs defaults 0 0 /data/home /home none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0 This has worked with the same configuration for me on at least Ubuntu 18.04 and Ubuntu 20.04, but on Ubuntu 22.04 the mount of /home fails when attempted by systemd. So not only is /home not mounted after boot, but also when I run "sudo systemctl start home.mount", it fails. The journal entries are this: sudo[1316]: wendler : TTY=pts/0 ; PWD=/home/wendler ; USER=root ; COMMAND=/usr/bin/systemctl start home.mount sudo[1316]: pam_unix(sudo:session): session opened for user root(uid=0) by wendler(uid=1000) systemd[1]: home.mount: Directory /home to mount over is not empty, mounting anyway. systemd[1]: home.mount: Failed to make bind mount source '/data/home': Permission denied systemd[1]: home.mount: Failed to run 'mount' task: Permission denied systemd[1]: home.mount: Failed with result 'resources'. systemd[1]: Failed to mount /home. However, when I run "sudo mount /home" it works. Now the weird thing is that after I have mounted /home manually once and unmounted it again, then "sudo systemctl start home.mount" suddenly also works! But of course only until the next reboot. And even if I just do "ls /data" once (either as root or as my user), it also makes "sudo systemctl start home.mount" start working! To be fully clear: - Booting the system (/home fails to mount) - sudo systemctl start home.mount # fails - sudo ls /data # shows correct output - sudo systemctl start home.mount # works! Additional information: The NFS export for /data has root_squash set and if I remove this option, the bind mount of /home works as it should. However, both /data and /data/home have mode rwxr-xr-x, so root is able to enter and read these directories even despite root_squash. It is not a network or mount-order problem. Not only is the bind mount to /home correctly attempted after /data is mounted during boot, remember that the bind mount also fails when I try it with "sudo systemctl start home.mount" minutes afterwards. Versions (system is a recent installation with all updates applied): - Ubuntu 22.04 - Linux 5.15.0-40-generic - systemd 249.11-0ubuntu3.3 - util-linux 2.37.2-4ubuntu3 This appears on both Ubuntu 22.04 machines that I have (a hardware machine and a VM). To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1979952/+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 1979952] Re: Bind mount to NFS mount fails on Ubuntu 22.04
** Merge proposal linked: https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/428423 -- 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/1979952 Title: Bind mount to NFS mount fails on Ubuntu 22.04 Status in systemd: Unknown Status in systemd package in Ubuntu: In Progress Status in systemd source package in Jammy: New Status in systemd source package in Kinetic: In Progress Bug description: I have the following setup: - /data is an NFS mount. - /home is a bind mount to /data/home. Configured in /etc/fstab with these lines: $FILE_SERVER:/data /data nfs defaults 0 0 /data/home /home none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0 This has worked with the same configuration for me on at least Ubuntu 18.04 and Ubuntu 20.04, but on Ubuntu 22.04 the mount of /home fails when attempted by systemd. So not only is /home not mounted after boot, but also when I run "sudo systemctl start home.mount", it fails. The journal entries are this: sudo[1316]: wendler : TTY=pts/0 ; PWD=/home/wendler ; USER=root ; COMMAND=/usr/bin/systemctl start home.mount sudo[1316]: pam_unix(sudo:session): session opened for user root(uid=0) by wendler(uid=1000) systemd[1]: home.mount: Directory /home to mount over is not empty, mounting anyway. systemd[1]: home.mount: Failed to make bind mount source '/data/home': Permission denied systemd[1]: home.mount: Failed to run 'mount' task: Permission denied systemd[1]: home.mount: Failed with result 'resources'. systemd[1]: Failed to mount /home. However, when I run "sudo mount /home" it works. Now the weird thing is that after I have mounted /home manually once and unmounted it again, then "sudo systemctl start home.mount" suddenly also works! But of course only until the next reboot. And even if I just do "ls /data" once (either as root or as my user), it also makes "sudo systemctl start home.mount" start working! To be fully clear: - Booting the system (/home fails to mount) - sudo systemctl start home.mount # fails - sudo ls /data # shows correct output - sudo systemctl start home.mount # works! Additional information: The NFS export for /data has root_squash set and if I remove this option, the bind mount of /home works as it should. However, both /data and /data/home have mode rwxr-xr-x, so root is able to enter and read these directories even despite root_squash. It is not a network or mount-order problem. Not only is the bind mount to /home correctly attempted after /data is mounted during boot, remember that the bind mount also fails when I try it with "sudo systemctl start home.mount" minutes afterwards. Versions (system is a recent installation with all updates applied): - Ubuntu 22.04 - Linux 5.15.0-40-generic - systemd 249.11-0ubuntu3.3 - util-linux 2.37.2-4ubuntu3 This appears on both Ubuntu 22.04 machines that I have (a hardware machine and a VM). To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1979952/+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 1974265] Re: `demangle_const` causes infinite recursion and stack overflow
** Changed in: binutils (Ubuntu) Importance: Undecided => Medium -- 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/1974265 Title: `demangle_const` causes infinite recursion and stack overflow Status in binutils: New Status in binutils package in Ubuntu: Confirmed Bug description: Original Post: `https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105115` The bug is similar to CVE-2021-3530, which was reported here: `https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1925348`. Commit: `e84412c6a3c3eed1a4eca5fe18f329bfa7efea40` at `https://github.com/bminor/binutils-gdb`. The simplified PoC: $ echo _RYAbB2_ | ./binutils/cxxfilt Segmentation fault Root Cause Analysis: 1. In `rust_demangle_callback`, "_R" at beginning causes `rdm.version == 0`[1][2], so `demangle_path` in the else-branch is called[3] with `rdm.sym == "YAbB2_"`, with `rdm.next` field initialized to 0. 2. Next char 'Y' causes `demangle_type` to be called[4] in a switch- case branch, with `rdm.next == 1`. 3. Next char 'A' causes `demangle_type` to be called first[5] to consume char 'b', then `demangle_const` is called[6] with `rdm.next == 3`. 4. Next char 'B' is consumed[7], and "2_" is parsed as `integer_62`[8] to be value 3, and this vlaue is assigned to `rdm.next`, then `demangle_const` is called recursively[9]. However, currently the situation is `rdm.next == 3` again, which is exactly same as last call to `demangle_const`, and this causes infinite recursion. [1] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L1356 [2] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L1362 [3] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L1453 [4] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L759 [5] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L934 [6] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L938 [7] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L1151 [8] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L1153 [9] https://github.com/bminor/binutils-gdb/blob/626d0e40e55c35a4f143b70def498734e8ed3c2a/libiberty/rust-demangle.c#L1158 Possible Fix: The infinite recursion check added in this [commit](https://github.com/bminor/binutils- gdb/commit/f10f8617a302f45dae721eae0cd659911f03d864) should also be applied to `demangle_const` To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1974265/+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 1985887] Re: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s)
yes, it same as what I understand. systemd-run and over ssh could have a session out of monitored by systemd-oomd. I'm trying to understand if any use cases will similar to this case? something like launching a lot of tabs from chrome/firefox browsers, I suppose all tabs will belong to same cgroup to see if memory will > 50% over 20 seconds. -- 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/1985887 Title: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s) Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: New Bug description: [Steps to reproduce] 0. Install Jammy image 1. open gnome terminal 2. issue stress_ng or Canonical certification tool checkbox as "checkbox-cli run com.canonical.certification::memory/memory_stress_ng" or "stress-ng --stack 0 --timeout 300" 3. Terminal or Gnome-shell will be killed by systemd-oomd It's because all stressors are under same cgroup belongs to terminal. Both Wayland and Xorg can reproduce. over ssh and in multi-user.target work good. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1985887/+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 1981592] Re: Please remove wpewebkit and block syncs from Debian
Someone needs to update gst-plugins-bad1.0 to not depend on this before the removal can proceed. ** Also affects: cog (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-plugins-bad1.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: wpewebkit (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1981592 Title: Please remove wpewebkit and block syncs from Debian Status in cog package in Ubuntu: New Status in gst-plugins-bad1.0 package in Ubuntu: New Status in wpewebkit package in Ubuntu: Incomplete Bug description: The wpewebkit package contains a whole webkit browser engine. It is currently not used by anything of substance in Ubuntu: $ reverse-depends src:wpewebkit Reverse-Depends * cog (for libwpewebkit-1.1-0) * gstreamer1.0-wpe (for libwpewebkit-1.1-0) cog is a single-window browser for embedded devices that is not used by anything else in the archive. gstreamer1.0-wpe is a plugin based on wpewebkit that is not used by anything else in the archive. Using this browser engine on the Internet is very risky as it it not currently maintained and contains hundreds of security flaws, and maintaining it requires a tremendous amount of work. As such, I don't believe this package is suitable for the Ubuntu archive. I recommend we disable the build in gstreamer and remove both cog and wpewebkit, and put on block on syncs from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cog/+bug/1981592/+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 1981622] Re: mtd device must be supplied (device name is empty)
Just had this message on Ubuntu 22.04.1 (5.15.0-46-generic) - was unable to boot. Related or not, the suggesting to update /etc/fstab in the comments above got me able to boot again. -- 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/1981622 Title: mtd device must be supplied (device name is empty) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Triaged Status in systemd source package in Jammy: Triaged Bug description: [WORKAROUND] This will NOT fix a system that is not booting, because the "mtd device must be supplied (device name is empty)" message is not the cause of failed boots. This work around is only for those who are annoyed by the error message, but are otherwise not experiencing any issues. If you are not able to boot your system, but you see this error message, please open a separate bug with your journalctl and dmesg logs. # cp /{lib,etc}/systemd/system/systemd-pstore.service # sed -i 's/modprobe@mtdpstore.service //' /etc/systemd/system/systemd-pstore.service # systemctl daemon-reload [Impact] Due to mtdpstore not being properly configured as a pstore backend, when systemd-pstore.service tries to load the module, users get the following error in dmesg: [ 18.453473] systemd[1]: Starting Load Kernel Module mtdpstore... [ 18.462685] mtd device must be supplied (device name is empty) This is a distracting error for users trying to diagnose other system issues, especially if their system does not boot after a kernel crash and this is the only message displayed on the console. [Test Plan] * Force a kernel crash to populate /sys/fs/pstore, thus causing systemd-pstore.service to start on the subsequent boot: # echo 1 > /proc/sys/kernel/sysrq # echo 1 > /proc/sys/kernel/panic # echo c > /proc/sysrq-trigger * When the system reboots, observe the error in dmesg: # dmesg | grep mtd [Where problems could occur] If a system was relying on this pstore backend, and mtdpstore is built as a module, it is possible for systemd-pstore.service to trigger before mtdpstore is loaded, causing systemd-pstore to not copy the contents of /sys/fs/pstore. Note however that before the patched introduced as a result of bug 1978079, systemd-pstore.service would not attempt to load *any* kernel modules. [Original Description] After updating my 22.04 system (possibly caused by Systemd update). And now booting, dmesg has two errors: 'mtd device must be supplied (device name is empty)'. See line 8 and 134 in the included logfile. The system are booting as it should though, and the system are working like it should no errors at all. Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in systemd? I have an EFI mounted at boot but it isn't used because I have installed my system in legacy BIOS mode. Is this maybe the culprit? I could ignore the message but it isn't nice though. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1784977 Importance: Unknown Status: Unknown -- 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/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: New Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 1980408] Re: Update glib to 2.72.3
Hello Jeremy, or anyone else affected, Accepted glib2.0 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.72.3-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: glib2.0 (Ubuntu Jammy) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1980408 Title: Update glib to 2.72.3 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Jammy: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 2.72 series https://gitlab.gnome.org/GNOME/glib/-/blob/2.72.3/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopgktest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1980408/+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 1985887] Re: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s)
alright, although the children are belong to same cgroup but > as a measurement of the CPU time lost due to lack of memory. it seems to me there is no a normal case from users will hit it unless memory stressors. -- 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/1985887 Title: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s) Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: New Bug description: [Steps to reproduce] 0. Install Jammy image 1. open gnome terminal 2. issue stress_ng or Canonical certification tool checkbox as "checkbox-cli run com.canonical.certification::memory/memory_stress_ng" or "stress-ng --stack 0 --timeout 300" 3. Terminal or Gnome-shell will be killed by systemd-oomd It's because all stressors are under same cgroup belongs to terminal. Both Wayland and Xorg can reproduce. over ssh and in multi-user.target work good. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1985887/+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 1985887] Re: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s)
Closed it first because I can not find any normal use case as what stress-ng did. Feel free to reopen and investigating if any normal use case got "being ...% > 50.00% for > 20s with reclaim activity". ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Changed in: oem-priority Status: Confirmed => 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/1985887 Title: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s) Status in OEM Priority Project: Invalid Status in systemd package in Ubuntu: Invalid Bug description: [Steps to reproduce] 0. Install Jammy image 1. open gnome terminal 2. issue stress_ng or Canonical certification tool checkbox as "checkbox-cli run com.canonical.certification::memory/memory_stress_ng" or "stress-ng --stack 0 --timeout 300" 3. Terminal or Gnome-shell will be killed by systemd-oomd It's because all stressors are under same cgroup belongs to terminal. Both Wayland and Xorg can reproduce. over ssh and in multi-user.target work good. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1985887/+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