[Touch-packages] [Bug 1896171] Re: Wayland 3D apps appear corrupt on Raspberry Pi 4B (v3d driver)
** Tags added: raspi raspi-gfx raspi4 -- 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/1896171 Title: Wayland 3D apps appear corrupt on Raspberry Pi 4B (v3d driver) Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Wayland 3D apps appear corrupt on Raspberry Pi 4B (v3d driver). Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1896171/+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 1883798] Re: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different f
Hi. I installed packettracer. Is there any solution? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1883798 Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg- turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:amd64 Status in libjpeg-turbo package in Ubuntu: Confirmed Bug description: not install file !!! packettracer ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libjpeg-turbo8 2.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 AptOrdering: libjpeg-turbo8:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 17 03:37:01 2020 DpkgTerminalLog: Preparing to unpack .../libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb ... Unpacking libjpeg-turbo8:amd64 (2.0.3-0ubuntu1.20.04.1) over (2.0.3-0ubuntu1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:amd64 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libjpeg-turbo Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1883798/+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 1896171] Re: Wayland 3D apps appear corrupt on Raspberry Pi 4B (v3d driver)
Actually weston works so maybe this is just mutter. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1896171 Title: Wayland 3D apps appear corrupt on Raspberry Pi 4B (v3d driver) Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Wayland 3D apps appear corrupt on Raspberry Pi 4B (v3d driver). Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1896171/+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 1896171] [NEW] Wayland 3D apps appear corrupt on Raspberry Pi 4B (v3d driver)
Public bug reported: Wayland 3D apps appear corrupt on Raspberry Pi 4B (v3d driver). Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: groovy ** Tags added: groovy -- 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/1896171 Title: Wayland 3D apps appear corrupt on Raspberry Pi 4B (v3d driver) Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Wayland 3D apps appear corrupt on Raspberry Pi 4B (v3d driver). Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1896171/+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 1887898] Re: Bluetooth sound card not detected
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1887898 Title: Bluetooth sound card not detected Status in bluez package in Ubuntu: Expired Bug description: I am able to use my inbuilt mic but unable to use external mic using neither Bluetooth nor mic with USB. My headphones are absolutely working fine with other devices (Mobile Phone or other laptop with windows) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: manoj 1480 F pulseaudio /dev/snd/controlC0: manoj 1480 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jul 17 12:31:29 2020 InstallationDate: Installed on 2019-10-15 (275 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.6A dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.46 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.6A:bd05/13/2013:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.46:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.sku: D7Z60PC#ACJ dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1887898/+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 1892290] Re: PXE load Focal initrd.img-5.4.0-42-generic always timeout
Any progress on this bug? @janitor -- 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/1892290 Title: PXE load Focal initrd.img-5.4.0-42-generic always timeout Status in grub2 package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Bug description: PXE booting Focal initrd always gets a timeout, but PXE booting Bionic initrd works error: timeout reading `initrd.img-5.4.0-42-generic'. grub.cfg menuentry "boot_iscsi" { linux vmlinuz-5.4.0-42-generic ... initrd initrd.img-5.4.0-42-generic } grub, kernel and initrd get from Focal boot dir $ cp /usr/lib/grub/arm64-efi-signed/grubnetaa64.efi.signed ~/tftproot/grubaa64.efi $ cp /boot/vmlinuz-5.4.0-42-generic ~/tftproot/ $ cp /boot/initrd.img-5.4.0-42-generic ~/tftproot/ hardware Real aarch64 server or qemu-system-aarch64 machine software $ apt search grub-efi-arm64 Sorting... Done Full Text Search... Done grub-efi-arm64/focal-updates,focal-security,now 2.04-1ubuntu26.2 arm64 [installed] GRand Unified Bootloader, version 2 (ARM64 UEFI version) grub-efi-arm64-bin/focal-updates,focal-security,now 2.04-1ubuntu26.2 arm64 [installed,automatic] GRand Unified Bootloader, version 2 (ARM64 UEFI modules) grub-efi-arm64-dbg/focal-updates,focal-security 2.04-1ubuntu26.2 arm64 GRand Unified Bootloader, version 2 (ARM64 UEFI debug files) grub-efi-arm64-signed/focal-updates,focal-security,now 1.142.4+2.04-1ubuntu26.2 arm64 [installed] GRand Unified Bootloader, version 2 (EFI-ARM64 version, signed) grub-efi-arm64-signed-template/focal-updates,focal-security 2.04-1ubuntu26.2 arm64 GRand Unified Bootloader, version 2 (ARM64 UEFI signing template) $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal $ uname -a Linux j12-d05-07 5.4.0-42-generic #1 SMP Tue Jul 7 02:48:00 GMT 2020 aarch64 aarch64 aarch64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1892290/+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 1895424] Re: duplicate rc local service
journalctl -b | grep local shows: Sep 17 19:48:34 ubuntu systemd[1]: Starting LSB: Run /etc/rc.local if it exist... Sep 17 19:48:35 ubuntu smartd[696]: smartd 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-47-generic] (local build) Sep 17 19:48:35 ubuntu polkitd[771]: started daemon version 0.105 using authority implementation `local' version `0.105' Sep 17 19:48:35 ubuntu systemd[1]: Started LSB: Run /etc/rc.local if it exist. Sep 17 19:48:41 ubuntu systemd-resolved[868]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test Sep 17 19:48:42 ubuntu systemd[1]: Starting /etc/rc.local Compatibility... Sep 17 19:48:42 ubuntu systemd[1]: Started /etc/rc.local Compatibility. root@ubuntu:~# systemctl | grep local rc-local.service loaded active exited/etc/rc.local Compatibility rc.local.service loaded active exitedLSB: Run /etc/rc.local if it exist If I add something like: echo Running rc.local `date` >> /root/rc.local.log to /etc/rc.local delete the /root/rc.log and reboot I definitely get 2 entries: root@ubuntu:~# cat /root/rc.local.log Running rc.local Thu 17 Sep 2020 07:55:10 PM PDT Running rc.local Thu 17 Sep 2020 07:55:12 PM PDT ** Attachment added: "journalctl -b outpout attached." https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895424/+attachment/5411996/+files/journal.log -- 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/1895424 Title: duplicate rc local service Status in systemd package in Ubuntu: Incomplete Bug description: Upgrading from Ubuntu 18.04 to 20.04 using "do-release-upgrade -d" Creates two systemd services: rc.local and rc-local This has the unfortunate event of running /etc/rc.local multiple times during bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895424/+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 1896098] Re: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1896098 Title: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack Status in pulseaudio package in Ubuntu: New Bug description: I suspect this is a pulseaudio or alsa bug. Our test team reported this: 1. Prepare Padme-3 machine and Install Ubuntu_20.04 OS . 2. Boot system. 3. Play audio or video file. 4. Open Settings > Sound. 5. Hot attach headset. 6. Notice that headset is selected as output device in sound settings and sound can be heard from headset => EXPECTED 7. While playback, select Internal Speaker as output device => KEYPOINT 9. Notice:SUT havo no sound from Internal Speakers => PROBLEM I was able to confirm this - it seems with the headphones connected that I can't select the system speakers. If I don't have headphones connected I can switch between dock audio and system speakers correctly - so it's just related to the audio jack Thanks Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1896098/+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 1896110] Re: Ubuntu Dock has no icons when login in with USB pluged in
** Summary changed: - Favorites side bar empty when login in with USB pluged in + Ubuntu Dock has no icons when login in with USB pluged in ** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock (Ubuntu) ** Summary changed: - Ubuntu Dock has no icons when login in with USB pluged in + Ubuntu Dock has no icons when logged in with USB storage plugged in -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1896110 Title: Ubuntu Dock has no icons when logged in with USB storage plugged in Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: If I connect a USB key to the computer then login the Favorites side bar is empty and the Application launcher does not work. The mouse and keyboard still work Removing the USB key does not resolve the issue Removing the USB key and then logging out and back in again resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 18 07:32:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-45-generic, x86_64: installed nvidia, 440.100, 5.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Subsystem: Lenovo UHD Graphics 630 (Desktop) [17aa:3140] NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 730] [1462:3380] InstallationDate: Installed on 2020-05-28 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 10TXCTO1WW ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=8f7f8957-ea10-4c4f-aa8c-0b2db299cab5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: M22KT42A dmi.board.name: 3140 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN 3258133898759 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM22KT42A:bd12/23/2019:svnLENOVO:pn10TXCTO1WW:pvrV530S-07ICB:rvnLENOVO:rn3140:rvrSDK0J40700WIN3258133898759:cvnLENOVO:ct3:cvrNone: dmi.product.family: V530S-07ICB dmi.product.name: 10TXCTO1WW dmi.product.sku: LENOVO_MT_10TX_BU_Lenovo_FM_V530S-07ICB dmi.product.version: V530S-07ICB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1896110/+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 1896098] Re: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack
I could reproduce this problem with padme-3 machine. But it looks like a hardware design limitation, plugging headset/headphone into the audio jack, the speaker will be muted by hardware signal (like a enable signal)? I checked both pulseaudio and alsa driver, there is no obvious problem. BTW, How does it work under windows? ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Critical ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1896098 Title: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack Status in pulseaudio package in Ubuntu: New Bug description: I suspect this is a pulseaudio or alsa bug. Our test team reported this: 1. Prepare Padme-3 machine and Install Ubuntu_20.04 OS . 2. Boot system. 3. Play audio or video file. 4. Open Settings > Sound. 5. Hot attach headset. 6. Notice that headset is selected as output device in sound settings and sound can be heard from headset => EXPECTED 7. While playback, select Internal Speaker as output device => KEYPOINT 9. Notice:SUT havo no sound from Internal Speakers => PROBLEM I was able to confirm this - it seems with the headphones connected that I can't select the system speakers. If I don't have headphones connected I can switch between dock audio and system speakers correctly - so it's just related to the audio jack Thanks Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1896098/+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 1896137] [NEW] syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7"
Public bug reported: When I close the lid on my laptop, syslog goes crazy with the message systemd-logind: hibernation is restricted; see man kernel_lockdown.7 repeated ad infinitum, using up all the CPU and GBs of disk space. I am not even trying to hibernate; everything in /etc/systemd/login.conf is commented out. So nothing much should happen when I close the lid, but systemd is trying to kill me with these messages. I am running Ubuntu 20.04. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: When I close the lid on my laptop, syslog goes crazy with the message - a: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 + systemd-logind: hibernation is restricted; see man kernel_lockdown.7 repeated ad infinitum, using up all the CPU and GBs of disk space. I am not even trying to hibernate; everything in /etc/systemd/login.conf is commented out. So nothing much should happen when I close the lid, but systemd is trying to kill me with these messages. ** Package changed: perf-tools-unstable (Ubuntu) => systemd (Ubuntu) ** Description changed: When I close the lid on my laptop, syslog goes crazy with the message systemd-logind: hibernation is restricted; see man kernel_lockdown.7 repeated ad infinitum, using up all the CPU and GBs of disk space. I am not even trying to hibernate; everything in /etc/systemd/login.conf is commented out. So nothing much should happen when I close the lid, but - systemd is trying to kill me with these messages. + systemd is trying to kill me with these messages. I am running Ubuntu + 20.04. -- 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/1896137 Title: syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7" Status in systemd package in Ubuntu: New Bug description: When I close the lid on my laptop, syslog goes crazy with the message systemd-logind: hibernation is restricted; see man kernel_lockdown.7 repeated ad infinitum, using up all the CPU and GBs of disk space. I am not even trying to hibernate; everything in /etc/systemd/login.conf is commented out. So nothing much should happen when I close the lid, but systemd is trying to kill me with these messages. I am running Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896137/+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 1896137] [NEW] syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7"
You have been subscribed to a public bug: When I close the lid on my laptop, syslog goes crazy with the message systemd-logind: hibernation is restricted; see man kernel_lockdown.7 repeated ad infinitum, using up all the CPU and GBs of disk space. I am not even trying to hibernate; everything in /etc/systemd/login.conf is commented out. So nothing much should happen when I close the lid, but systemd is trying to kill me with these messages. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7" https://bugs.launchpad.net/bugs/1896137 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895665] Re: PulseAudio automatically switches from HDMI 2 after display sleep
If you want the hdmi-output to be selected automatically after plugging, you need to manually select it as output once, then pulseaudio will remember uer's preference. Then unplug and replug the monitor, the system will automatically switch to hdmi-output. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1895665 Title: PulseAudio automatically switches from HDMI 2 after display sleep Status in pulseaudio package in Ubuntu: New Bug description: I have an Nvidia based video card that has an HDMI output + a DisplayPort output. DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output is listed as "Digital Stereo (HDMI 2)". I prefer to use "Digital Stereo (HDMI 2)". But after each display sleep (screen lock for example) audio is switched to built in audio ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 15 14:56:58 2020 InstallationDate: Installed on 2020-06-20 (86 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0CNDTP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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 1298792] Re: Innocuous error prompt pops up when logging in after suspend and the battery runs out, or when battery is not present and power is unplugged
** Changed in: apport (Ubuntu) Assignee: (unassigned) => SatoshiNakamoto (evansanita713) -- 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/1298792 Title: Innocuous error prompt pops up when logging in after suspend and the battery runs out, or when battery is not present and power is unplugged Status in apport package in Ubuntu: Confirmed Bug description: After logging in after I suspend and the battery runs out, or when battery is not present and I unplug the power supply. ProblemType: KernelOops DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-19-generic 3.13.0-19.40 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fotini 2115 F pulseaudio Date: Fri Mar 28 07:49:36 2014 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2014-03-23 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140322) InterpreterPath: /usr/bin/python3.4 MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-19-generic root=UUID=e1ae85e3-71c4-44db-bc13-b62d0ac1e3d2 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-19-generic N/A linux-backports-modules-3.13.0-19-generic N/A linux-firmware 1.126 SourcePackage: linux Title: [Hewlett-Packard HP Pavilion g6 Notebook PC] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/24/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1670 dmi.board.vendor: Hewlett-Packard dmi.board.version: 09.4C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd01/24/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr059B1020451020100:rvnHewlett-Packard:rn1670:rvr09.4C:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.version: 059B1020451020100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1298792/+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 1884738] Re: Pulseaudio in Ubuntu 16.04 contains a potential double-free bug in Bluez 5 module
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1884738 Title: Pulseaudio in Ubuntu 16.04 contains a potential double-free bug in Bluez 5 module Status in pulseaudio package in Ubuntu: Fix Released Bug description: I've found a potential double-free bug in Ubuntu's SCO-over-PCM patch in PA. It creates code paths in pa__init() that will free the modargs twice in its failure handler and in pa__done() called from that handler. However, I can't find a way to trigger this with the current version of the code, as the failure mode of the code is pretty small. The way this bug surface is when I tried to fix the "profile" option in Pulseaudio for UBports' Ubuntu Touch, where I made it failed if the requested profile isn't supported, thus creating a failure mode that can trigger this. Side note: are you interested in this patch? The profile option in Xenial is currently not working, but I guess nothing in Ubuntu uses it. I've attached the patch which should fix the bug. I'm not sure if it worths SRU or not, so it's up to you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1884738/+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 1896134] [NEW] [ROG Strix G512LV_G512LV, Realtek ALC294, Speaker, Internal] No sound at all. (but headphones work)
Public bug reported: It's a dualboot laptop and there's no problem with the audio in windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dnsei 2855 F pulseaudio /dev/snd/controlC0: dnsei 2855 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 18 00:41:04 2020 InstallationDate: Installed on 2020-09-17 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dnsei 2855 F pulseaudio /dev/snd/controlC0: dnsei 2855 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [ROG Strix G512LV_G512LV, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G512LV.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G512LV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG512LV.310:bd07/13/2020:svnASUSTeKCOMPUTERINC.:pnROGStrixG512LV_G512LV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG512LV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G512LV_G512LV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1896134 Title: [ROG Strix G512LV_G512LV, Realtek ALC294, Speaker, Internal] No sound at all. (but headphones work) Status in alsa-driver package in Ubuntu: New Bug description: It's a dualboot laptop and there's no problem with the audio in windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dnsei 2855 F pulseaudio /dev/snd/controlC0: dnsei 2855 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 18 00:41:04 2020 InstallationDate: Installed on 2020-09-17 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dnsei 2855 F pulseaudio /dev/snd/controlC0: dnsei 2855 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [ROG Strix G512LV_G512LV, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G512LV.310 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G512LV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG512LV.310:bd07/13/2020:svnASUSTeKCOMPUTERINC.:pnROGStrixG512LV_G512LV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG512LV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G512LV_G512LV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1896134/+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 1896133] [NEW] [Audio Playback] right channel attenuated after random length of time
Public bug reported: After playing sound for a while (minutes, not seconds), the right channel will become attenuated. Restoring balance can be done by unplugging the headphones (from the built-in sound card) or disconnecting the external DAC and reconnecting it. Balance can be restored by altering balance in pavucontrol, but if you balance by increasing the right side volume, it introduces a lot of distortion. Same behavior observed using both the internal sound device as well as the Sound Blaster USB sound device, so it's in the mixing software somewhere. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 17 14:33:43 2020 InstallationDate: Installed on 2020-07-10 (69 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: SoundBlaster MP3+ - Sound Blaster MP3+ Symptom_PulseAudioLog: Sep 15 15:45:31 vmhost01 dbus-daemon[1765]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.29' (uid=125 pid=2024 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Sep 15 15:45:32 vmhost01 pulseaudio[2024]: No UCM verb is valid for hw:0 Sep 15 15:45:33 vmhost01 pulseaudio[2024]: No UCM verb is valid for hw:2 Sep 15 15:45:34 vmhost01 dbus-daemon[1765]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.45' (uid=125 pid=2024 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Sep 15 19:01:54 vmhost01 dbus-daemon[1765]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.114' (uid=1000 pid=4820 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - Sound Blaster MP3+, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2901 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2901:bd10/16/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1896133 Title: [Audio Playback] right channel attenuated after random length of time Status in alsa-driver package in Ubuntu: New Bug description: After playing sound for a while (minutes, not seconds), the right channel will become attenuated. Restoring balance can be done by unplugging the headphones (from the built-in sound card) or disconnecting the external DAC and reconnecting it. Balance can be restored by altering balance in pavucontrol, but if you balance by increasing the right side volume, it introduces a lot of distortion. Same behavior observed using both the internal sound device as well as the Sound Blaster USB sound device, so it's in the mixing software somewhere. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 17 14:33:43 2020 InstallationDate: Installed on 2020-07-10 (69 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: SoundBlaster MP3+ - Sound Blaster MP3+ Symptom_PulseAudioLog: Sep 15 15:45:31 vmhost01 dbus-daemon[
[Touch-packages] [Bug 1895370] Re: systemd: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: iptc_commit
you may be missing the package libip4tc2 which provides the lib /usr/lib/x86_64-linux-gnu/libip4tc.so.2 however, the systemd package includes the libip4tc2 package, so it should be installed. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1895370 Title: systemd: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: iptc_commit Status in systemd package in Ubuntu: Incomplete Bug description: Last run apt update and apt upgrade and reboot render my system unbootable because systemd failed with message: systemd: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: iptc_commit So I tried to reset to the previous state and re-run the update and after the re-run update I try to run the systemd command and having the same result. root@work ~# apt update; apt upgrade Get:1 http://au.archive.ubuntu.com/ubuntu focal InRelease [265 kB] Get:2 http://au.archive.ubuntu.com/ubuntu focal-updates InRelease [111 kB] Get:3 http://au.archive.ubuntu.com/ubuntu focal-backports InRelease [98.3 kB] Get:4 http://ppa.launchpad.net/audio-recorder/ppa/ubuntu focal InRelease [15.9 kB] Get:5 http://security.ubuntu.com/ubuntu focal-security InRelease [107 kB] Get:6 http://dl.google.com/linux/chrome/deb stable InRelease [1,811 B] Get:7 http://au.archive.ubuntu.com/ubuntu focal/main amd64 Packages [970 kB] Get:9 http://au.archive.ubuntu.com/ubuntu focal/main i386 Packages [718 kB] Get:10 http://au.archive.ubuntu.com/ubuntu focal/main Translation-en_AU [1,836 B] Get:11 http://au.archive.ubuntu.com/ubuntu focal/main Translation-en [506 kB] Get:12 https://packages.microsoft.com/repos/ms-teams stable InRelease [17.5 kB] Get:13 http://au.archive.ubuntu.com/ubuntu focal/main amd64 DEP-11 Metadata [494 kB] Get:14 http://au.archive.ubuntu.com/ubuntu focal/main DEP-11 48x48 Icons [98.4 kB] Get:15 http://au.archive.ubuntu.com/ubuntu focal/main DEP-11 64x64 Icons [163 kB] Get:16 http://au.archive.ubuntu.com/ubuntu focal/main DEP-11 64x64@2 Icons [15.8 kB] Get:17 https://packages.microsoft.com/repos/ms-teams stable/main amd64 Packages [6,403 B] Get:18 http://au.archive.ubuntu.com/ubuntu focal/main amd64 c-n-f Metadata [29.5 kB] Get:19 http://au.archive.ubuntu.com/ubuntu focal/restricted i386 Packages [8,112 B] Ign:20 http://ppa.launchpad.net/hermlnx/dislocker/ubuntu focal InRelease Get:21 http://au.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages [22.0 kB] Get:22 http://au.archive.ubuntu.com/ubuntu focal/restricted Translation-en_AU [1,144 B] Get:23 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages [1,163 B] Get:24 http://au.archive.ubuntu.com/ubuntu focal/restricted Translation-en [6,212 B] Get:25 http://au.archive.ubuntu.com/ubuntu focal/restricted amd64 c-n-f Metadata [392 B] Get:26 http://au.archive.ubuntu.com/ubuntu focal/universe amd64 Packages [8,628 kB] Get:8 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease [23.5 kB] Get:27 h
[Touch-packages] [Bug 1895424] Re: duplicate rc local service
I couldn't reproduce this, can you check your journalctl -b and make sure you actually do have two services that run rc.local twice at boot, and check what service files they're coming from? ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1895424 Title: duplicate rc local service Status in systemd package in Ubuntu: Incomplete Bug description: Upgrading from Ubuntu 18.04 to 20.04 using "do-release-upgrade -d" Creates two systemd services: rc.local and rc-local This has the unfortunate event of running /etc/rc.local multiple times during bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895424/+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 1895418] Re: systemd-resolved default config for Caching is still "yes"
** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Focal) Status: New => 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/1895418 Title: systemd-resolved default config for Caching is still "yes" Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: Fix Committed Bug description: Back in December, the default for systemd-resolved caching in Ubuntu systemd was changed to "no-negative" from the upstream default "yes" [0] In this change, the default value in the resolved.conf file was missed. As the defaults in this file are commented, the effective default is still "no-negative", however when viewing the config file, the commented default "yes" is at odds with the man page resolved.conf(5), which correctly states the default as "no-negative". This was an issue for me as I set DNSSEC to "yes", and expected Caching to also be "yes". Running DNSSEC with the default "no- negative" Caching is detrimental to performance resolving unsigned zones, as the non-existence of DNSSEC RRs must be looked up every time. The issue with the intersection of DNSSEC and Caching is for upstream, but the least that needs to be done here is updating the resolved.conf template with "Caching=no-negative" to match the man page and behaviour, and perhaps even adding a note to the "DNSSEC=" section of resolved.conf(5) that Caching should be enabled. Now that I'm looking at that man page, the default for DNSSEC is also listed as "allow- downgrade", whereas the default for Ubuntu is "no". [0] https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/systemd/commit/?id=b42658843a9496d6b6bb68ac159f2a9f0a8ba9db&h =ubuntu-focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895418/+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 1895418] Re: systemd-resolved default config for Caching is still "yes"
committed in groovy: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?h=ubuntu-groovy&id=dd4d93d94ebe2cf416f6b5a5eb59a16432cbc47b ** Changed in: systemd (Ubuntu Groovy) Status: New => Fix Committed -- 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/1895418 Title: systemd-resolved default config for Caching is still "yes" Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Focal: New Status in systemd source package in Groovy: Fix Committed Bug description: Back in December, the default for systemd-resolved caching in Ubuntu systemd was changed to "no-negative" from the upstream default "yes" [0] In this change, the default value in the resolved.conf file was missed. As the defaults in this file are commented, the effective default is still "no-negative", however when viewing the config file, the commented default "yes" is at odds with the man page resolved.conf(5), which correctly states the default as "no-negative". This was an issue for me as I set DNSSEC to "yes", and expected Caching to also be "yes". Running DNSSEC with the default "no- negative" Caching is detrimental to performance resolving unsigned zones, as the non-existence of DNSSEC RRs must be looked up every time. The issue with the intersection of DNSSEC and Caching is for upstream, but the least that needs to be done here is updating the resolved.conf template with "Caching=no-negative" to match the man page and behaviour, and perhaps even adding a note to the "DNSSEC=" section of resolved.conf(5) that Caching should be enabled. Now that I'm looking at that man page, the default for DNSSEC is also listed as "allow- downgrade", whereas the default for Ubuntu is "no". [0] https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/systemd/commit/?id=b42658843a9496d6b6bb68ac159f2a9f0a8ba9db&h =ubuntu-focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895418/+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 1896115] [NEW] uc20 initramfs busybox missing less applet
Public bug reported: the version of busybox in the initramfs of uc20, which derives from ubuntu 20.04, does not have the less module/applet built into it, so there is no less command available in the initramfs on uc20. This is unfortunate as sometimes when debugging problems in the initramfs it is useful to read large files, etc. using something like less. ** Affects: busybox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1896115 Title: uc20 initramfs busybox missing less applet Status in busybox package in Ubuntu: New Bug description: the version of busybox in the initramfs of uc20, which derives from ubuntu 20.04, does not have the less module/applet built into it, so there is no less command available in the initramfs on uc20. This is unfortunate as sometimes when debugging problems in the initramfs it is useful to read large files, etc. using something like less. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1896115/+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 1896110] Re: Favorites side bar empty when login in with USB pluged in
Update - If I lock the screen and then unlock it - the Side bar comes back and works as normal. Screenshot attached ** Attachment added: "Screen shot of problem" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1896110/+attachment/5411879/+files/Broken.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1896110 Title: Favorites side bar empty when login in with USB pluged in Status in xorg package in Ubuntu: New Bug description: If I connect a USB key to the computer then login the Favorites side bar is empty and the Application launcher does not work. The mouse and keyboard still work Removing the USB key does not resolve the issue Removing the USB key and then logging out and back in again resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 18 07:32:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-45-generic, x86_64: installed nvidia, 440.100, 5.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Subsystem: Lenovo UHD Graphics 630 (Desktop) [17aa:3140] NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 730] [1462:3380] InstallationDate: Installed on 2020-05-28 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 10TXCTO1WW ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=8f7f8957-ea10-4c4f-aa8c-0b2db299cab5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: M22KT42A dmi.board.name: 3140 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN 3258133898759 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM22KT42A:bd12/23/2019:svnLENOVO:pn10TXCTO1WW:pvrV530S-07ICB:rvnLENOVO:rn3140:rvrSDK0J40700WIN3258133898759:cvnLENOVO:ct3:cvrNone: dmi.product.family: V530S-07ICB dmi.product.name: 10TXCTO1WW dmi.product.sku: LENOVO_MT_10TX_BU_Lenovo_FM_V530S-07ICB dmi.product.version: V530S-07ICB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1896110/+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 1896110] [NEW] Favorites side bar empty when login in with USB pluged in
Public bug reported: If I connect a USB key to the computer then login the Favorites side bar is empty and the Application launcher does not work. The mouse and keyboard still work Removing the USB key does not resolve the issue Removing the USB key and then logging out and back in again resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 18 07:32:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-45-generic, x86_64: installed nvidia, 440.100, 5.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Subsystem: Lenovo UHD Graphics 630 (Desktop) [17aa:3140] NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 730] [1462:3380] InstallationDate: Installed on 2020-05-28 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 10TXCTO1WW ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=8f7f8957-ea10-4c4f-aa8c-0b2db299cab5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: M22KT42A dmi.board.name: 3140 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN 3258133898759 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM22KT42A:bd12/23/2019:svnLENOVO:pn10TXCTO1WW:pvrV530S-07ICB:rvnLENOVO:rn3140:rvrSDK0J40700WIN3258133898759:cvnLENOVO:ct3:cvrNone: dmi.product.family: V530S-07ICB dmi.product.name: 10TXCTO1WW dmi.product.sku: LENOVO_MT_10TX_BU_Lenovo_FM_V530S-07ICB dmi.product.version: V530S-07ICB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1896110 Title: Favorites side bar empty when login in with USB pluged in Status in xorg package in Ubuntu: New Bug description: If I connect a USB key to the computer then login the Favorites side bar is empty and the Application launcher does not work. The mouse and keyboard still work Removing the USB key does not resolve the issue Removing the USB key and then logging out and back in again resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 18 07:32:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-45-generic, x86_64: installed nvidia, 440.100, 5.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Subsystem: Lenovo UHD Graphics 630 (Desktop) [17aa:3140] NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 730] [1462:3380] InstallationDate: Installed on 2020-05-28 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 10TXCTO1WW ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=8f7f8957-ea10-4c4f-aa8c-0b2db299cab5 ro quiet splash vt.handoff=7 So
[Touch-packages] [Bug 1895422] Re: Sound card not detected on Dell Latitude 9510 (Realtek ALC711)
New demsg after new kernel install harrison@lassen:~$ uname -r 5.6.0-1028-oem ** Attachment added: "demsg2.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1895422/+attachment/5411841/+files/demsg2.txt -- 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/1895422 Title: Sound card not detected on Dell Latitude 9510 (Realtek ALC711) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am running Ubuntu 20.04.01 LTS, kernel version 5.6.0-1027-oem (checked via uname -r). I believe my sound card is not being detected by Ubuntu. I checked the serial number and via BIOS (which I've upgraded to the latest version) according to the specs (https://topics-cdn.dell.com/pdf/latitude-15-9510-2-in-1-laptop_owners-manual5_en-us.pdf) the sound controller/speaker should be Realtek ALC711-CG / Realtek ALC1309D. However, when I run lspci only the following device appears: 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] In alsamixer, only the HDMI port appears. alsa-info output: http://alsa- project.org/db/?f=f2b70f6eb1a237378bf563cacb6f192ce0a677c3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1895422/+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 1895422] Re: Sound card not detected on Dell Latitude 9510 (Realtek ALC711)
New pactl list after new kernel install harrison@lassen:~$ uname -r 5.6.0-1028-oem (lspci has same output) ** Attachment added: "pactl_list2.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1895422/+attachment/5411842/+files/pactl_list2.txt -- 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/1895422 Title: Sound card not detected on Dell Latitude 9510 (Realtek ALC711) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am running Ubuntu 20.04.01 LTS, kernel version 5.6.0-1027-oem (checked via uname -r). I believe my sound card is not being detected by Ubuntu. I checked the serial number and via BIOS (which I've upgraded to the latest version) according to the specs (https://topics-cdn.dell.com/pdf/latitude-15-9510-2-in-1-laptop_owners-manual5_en-us.pdf) the sound controller/speaker should be Realtek ALC711-CG / Realtek ALC1309D. However, when I run lspci only the following device appears: 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] In alsamixer, only the HDMI port appears. alsa-info output: http://alsa- project.org/db/?f=f2b70f6eb1a237378bf563cacb6f192ce0a677c3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1895422/+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 1894195] Re: FFe: Merge iptables 1.8.5-3 (main) from Debian sid (main)
I've attached the upstream changelog. The upstream release contains a lot of fixes for nftables but also rewrites and fixes in other areas. Landing the merge does have risks, but IMO it would be better ship it in 20.10 than the current version. I've asked the Security Team in June if they could merge the new upstream from Debian, but they could not find time for that AFAIK. I\m +1 on the FFe, but someone still needs to actually do the merge and landing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1894195 Title: FFe: Merge iptables 1.8.5-3 (main) from Debian sid (main) Status in iptables package in Ubuntu: New Bug description: Please merge iptables 1.8.5-3 (main) from Debian sid (main) Explanation of FeatureFreeze exception: Current iptables is using the same upstream version in focal, which had problems with the nft backend and was then reverted to the legacy backend. 1.8.5 has many fixes for the nft backend. For example these Debian bugs are fixed in 1.8.5: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950535 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961117 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968457 Please merge it. Changelog entries since current groovy version 1.8.4-3ubuntu3: iptables (1.8.5-3) unstable; urgency=medium * [2d587e5] src:iptables: bump build-dep version on libnftnl to 1.1.6 -- Arturo Borrero Gonzalez Tue, 25 Aug 2020 11:56:55 +0200 iptables (1.8.5-2) unstable; urgency=medium [ Alberto Molina Coballes ] * [d90516d] d/control: modify breaks and replaces fields (Closes: #949576) * [4754a45] d/not-installed: arch independ files * [780330f] d/tests/control: Run iptables-legacy-* tests explicitly [ Arturo Borrero Gonzalez ] * [6fb6557] d/patches: add -upstream-fix-xtables-translate.patch (Closes: #962724) -- Arturo Borrero Gonzalez Wed, 24 Jun 2020 10:56:19 +0200 iptables (1.8.5-1) unstable; urgency=medium [ Debian Janitor ] * [c3deeb3] Wrap long lines in changelog entries: 1.8.2-1, 1.8.0-1~exp1, 1.6.0-1. * [214468e] Update standards version to 4.5.0, no changes needed. [ Arturo Borrero Gonzalez ] * [eb1d7c5] New upstream version 1.8.5 (Closes: #950535) * [7a119db] d/patches: drop all patches * [ec63c87] libxtables12.symbols: add new symbol * [4056ce6] iptables: bump debhelper-compat to 13 -- Arturo Borrero Gonzalez Thu, 04 Jun 2020 13:33:22 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1894195/+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 1798369] Re: Reinstall Ubuntu (with preserving existing data) shows error message due to "Could not get lock /target/var/cache/apt/archives/lock"
** Changed in: ubiquity (Ubuntu) Status: Fix Released => Won't Fix -- 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/1798369 Title: Reinstall Ubuntu (with preserving existing data) shows error message due to "Could not get lock /target/var/cache/apt/archives/lock" Status in APT: New Status in ubiquity: New Status in apt package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Won't Fix Status in apt source package in Eoan: Invalid Status in ubiquity source package in Eoan: Won't Fix Bug description: When trying to reinstall an existing Ubuntu cosmic installation using latest 18.10 desktop images, the install shows an error dialog around the end of the installation with an "Error restoring installed applications". Looking at the syslog such a traceback can be seen: apt_pkg.Error: E:Could not get lock /target/var/cache/apt/archives/lock - open (11: Resource temporarily unavailable), E:Unable to lock directory /target/var/cache/apt/archives/ After reproducing this on a live session, after chrooting into /target indeed any apt-get install operations result in the same lock-file error. The whole syslog of the reinstall attached to the bug. Test case: * Download latest cosmic image * Install cosmic on the whole disk (can be on a VM) * (optional) Boot into the system and leave a file in the home directory (to leave a trace, just in case) * Reboot and install cosmic using the first option in ubiquity: Reinstall Ubuntu * Finish configuration The install itself doesn't fail, but around the end of the installation process the error dialog appears. System is still bootable but left with old packages. To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1798369/+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 1894195] Re: FFe: Merge iptables 1.8.5-3 (main) from Debian sid (main)
** Attachment added: "changes-iptables-1.8.5.txt" https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1894195/+attachment/5411820/+files/changes-iptables-1.8.5.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1894195 Title: FFe: Merge iptables 1.8.5-3 (main) from Debian sid (main) Status in iptables package in Ubuntu: New Bug description: Please merge iptables 1.8.5-3 (main) from Debian sid (main) Explanation of FeatureFreeze exception: Current iptables is using the same upstream version in focal, which had problems with the nft backend and was then reverted to the legacy backend. 1.8.5 has many fixes for the nft backend. For example these Debian bugs are fixed in 1.8.5: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950535 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961117 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968457 Please merge it. Changelog entries since current groovy version 1.8.4-3ubuntu3: iptables (1.8.5-3) unstable; urgency=medium * [2d587e5] src:iptables: bump build-dep version on libnftnl to 1.1.6 -- Arturo Borrero Gonzalez Tue, 25 Aug 2020 11:56:55 +0200 iptables (1.8.5-2) unstable; urgency=medium [ Alberto Molina Coballes ] * [d90516d] d/control: modify breaks and replaces fields (Closes: #949576) * [4754a45] d/not-installed: arch independ files * [780330f] d/tests/control: Run iptables-legacy-* tests explicitly [ Arturo Borrero Gonzalez ] * [6fb6557] d/patches: add -upstream-fix-xtables-translate.patch (Closes: #962724) -- Arturo Borrero Gonzalez Wed, 24 Jun 2020 10:56:19 +0200 iptables (1.8.5-1) unstable; urgency=medium [ Debian Janitor ] * [c3deeb3] Wrap long lines in changelog entries: 1.8.2-1, 1.8.0-1~exp1, 1.6.0-1. * [214468e] Update standards version to 4.5.0, no changes needed. [ Arturo Borrero Gonzalez ] * [eb1d7c5] New upstream version 1.8.5 (Closes: #950535) * [7a119db] d/patches: drop all patches * [ec63c87] libxtables12.symbols: add new symbol * [4056ce6] iptables: bump debhelper-compat to 13 -- Arturo Borrero Gonzalez Thu, 04 Jun 2020 13:33:22 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1894195/+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 1895422] Re: Sound card not detected on Dell Latitude 9510 (Realtek ALC711)
There seems be a patch on here: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?h=for-linus&id=83629532ce45ef9df1f297b419b9ea112045685d for kernel version 5.4-rc2, so this sound card is theoretically supported, if I am understanding this correctly. -- 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/1895422 Title: Sound card not detected on Dell Latitude 9510 (Realtek ALC711) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am running Ubuntu 20.04.01 LTS, kernel version 5.6.0-1027-oem (checked via uname -r). I believe my sound card is not being detected by Ubuntu. I checked the serial number and via BIOS (which I've upgraded to the latest version) according to the specs (https://topics-cdn.dell.com/pdf/latitude-15-9510-2-in-1-laptop_owners-manual5_en-us.pdf) the sound controller/speaker should be Realtek ALC711-CG / Realtek ALC1309D. However, when I run lspci only the following device appears: 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:02c8] In alsamixer, only the HDMI port appears. alsa-info output: http://alsa- project.org/db/?f=f2b70f6eb1a237378bf563cacb6f192ce0a677c3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1895422/+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 1896098] [NEW] Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack
Public bug reported: I suspect this is a pulseaudio or alsa bug. Our test team reported this: 1. Prepare Padme-3 machine and Install Ubuntu_20.04 OS . 2. Boot system. 3. Play audio or video file. 4. Open Settings > Sound. 5. Hot attach headset. 6. Notice that headset is selected as output device in sound settings and sound can be heard from headset => EXPECTED 7. While playback, select Internal Speaker as output device => KEYPOINT 9. Notice:SUT havo no sound from Internal Speakers => PROBLEM I was able to confirm this - it seems with the headphones connected that I can't select the system speakers. If I don't have headphones connected I can switch between dock audio and system speakers correctly - so it's just related to the audio jack Thanks Mark ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1896098 Title: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack Status in pulseaudio package in Ubuntu: New Bug description: I suspect this is a pulseaudio or alsa bug. Our test team reported this: 1. Prepare Padme-3 machine and Install Ubuntu_20.04 OS . 2. Boot system. 3. Play audio or video file. 4. Open Settings > Sound. 5. Hot attach headset. 6. Notice that headset is selected as output device in sound settings and sound can be heard from headset => EXPECTED 7. While playback, select Internal Speaker as output device => KEYPOINT 9. Notice:SUT havo no sound from Internal Speakers => PROBLEM I was able to confirm this - it seems with the headphones connected that I can't select the system speakers. If I don't have headphones connected I can switch between dock audio and system speakers correctly - so it's just related to the audio jack Thanks Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1896098/+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 1756006] Re: FFe: Support suspend-then-hibernate
This appears to no longer be a current FFe, so retitling and unsubscribing ubuntu-release. ** Summary changed: - FFe: Support suspend-then-hibernate + Support suspend-then-hibernate -- 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/1756006 Title: Support suspend-then-hibernate Status in gnome-settings-daemon package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Triaged Bug description: Suspend to hibernate is a new feature that will put the system into hibernate after a period of time spent in the system's supported sleep state. This mode will be used on some systems that take suspend to idle in the future with Ubuntu 18.04. This feature is available in upstream systemd from these two commits. https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703 https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5 This is accepted upstream. The policy needs to be made available to gnome from this commit: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9 As of 3/15/2018 this is not yet accepted or rejected. The new mode is not selected by default, but that can be changed from a separate policy package. The policy for the amount of time spent in S3/S2I can be configured by a separate package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+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 1895865] Re: /usr/share/apport/dump_acpi_tables.py:PermissionError:/usr/share/apport/dump_acpi_tables.py@59:dump_acpi_tables:dump_acpi_table
** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/ubuntu -- 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/1895865 Title: /usr/share/apport/dump_acpi_tables.py:PermissionError:/usr/share/apport/dump_acpi_tables.py@59:dump_acpi_tables:dump_acpi_table Status in apport package in Ubuntu: In Progress Status in apport source package in Groovy: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu45, the problem page at https://errors.ubuntu.com/problem/ad705c1a5e4068bcae9d4261519bac8fac5cb57f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1895865/+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 1888352] Re: use builtin dump_acpi_tables.py in hookutils
** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/ubuntu -- 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/1888352 Title: use builtin dump_acpi_tables.py in hookutils Status in Apport: New Status in OEM Priority Project: Fix Committed Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Committed Status in apport source package in Groovy: Fix Released Bug description: 1. add apcidump to hookutils.py:attach_hardware and use the builtin dump_acpi_tables.py. 2. remove explicit acpidump from oem-getlogs to use the builtin one. 3. refine usage string in oem-getlogs. To SRU to focal: [Impact] * for OEM project, lts is been used. And collect log is important. With built-in tool to get acpidump, we don't need to install extra tool in the end-customer's machine. That make it much easier for the oem process. * By call built-in utility, we no lounger need to install extra tools to collect data that's both complete and convenient for HWE people to work on. [Test Case] * before this applied, run oem-getlog without install acpidump. we can't get the dump data. After this applied, we can just dump the data HWE need. * test step: install the new package, run sudo -E oem-getlogs [-c case_id] to get the use apport-unpack to unpack the apport file. check the acpidump file. HWE people know much better on check the acpidump file. Give the dump_acpi_tables.py just updated and SRUed by HWE/ACPI/UEFI expert, it's pretty safe to do so. [Regression Potential] * Given the modification change the way to collect log, even it failed, it won't break apport itself. Just the collected log might contain data not so valid. * Given acpidump mostly used by HWE/ACIP/UEFI expert, and they just reviewed and updated the dump_acpi_tables.py script, I believe it will have good quality. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1888352/+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 1896095] Re: apport no longer attaches dmesg, as dmesg is restricted in groovy
** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/ubuntu -- 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/1896095 Title: apport no longer attaches dmesg, as dmesg is restricted in groovy Status in apport package in Ubuntu: In Progress Bug description: I reported https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896091 but it was incomplete because apparently apport can no longer collect dmesg log now that it is restricted in groovy. This means you can't report complete kernel bugs, and the instructions provided by the kernel bot are wrong. Not sure what the solution is - read journalctl, do it as root, idk? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1896095/+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 1896095] Re: apport no longer attaches dmesg, as dmesg is restricted in groovy
It's just a matter of switching from command_output to root_command_output. ** Changed in: apport (Ubuntu) Importance: Undecided => High ** Changed in: apport (Ubuntu) Status: Confirmed => In Progress ** Changed in: apport (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) -- 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/1896095 Title: apport no longer attaches dmesg, as dmesg is restricted in groovy Status in apport package in Ubuntu: In Progress Bug description: I reported https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896091 but it was incomplete because apparently apport can no longer collect dmesg log now that it is restricted in groovy. This means you can't report complete kernel bugs, and the instructions provided by the kernel bot are wrong. Not sure what the solution is - read journalctl, do it as root, idk? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1896095/+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 1896095] Re: apport no longer attaches dmesg, as dmesg is restricted in groovy
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- 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/1896095 Title: apport no longer attaches dmesg, as dmesg is restricted in groovy Status in apport package in Ubuntu: Confirmed Bug description: I reported https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896091 but it was incomplete because apparently apport can no longer collect dmesg log now that it is restricted in groovy. This means you can't report complete kernel bugs, and the instructions provided by the kernel bot are wrong. Not sure what the solution is - read journalctl, do it as root, idk? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1896095/+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 1896095] [NEW] apport no longer attaches dmesg, as dmesg is restricted in groovy
Public bug reported: I reported https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896091 but it was incomplete because apparently apport can no longer collect dmesg log now that it is restricted in groovy. This means you can't report complete kernel bugs, and the instructions provided by the kernel bot are wrong. Not sure what the solution is - read journalctl, do it as root, idk? ** Affects: apport (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: rls-gg-incoming ** Description changed: I reported https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896091 but it was incomplete because apparently apport can no longer collect dmesg log now that it is restricted in groovy. + + This means you can't report complete kernel bugs, and the instructions + provided by the kernel bot are wrong. + + Not sure what the solution is - read journalctl, do it as root, idk? ** Tags added: rls-gg-incoming -- 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/1896095 Title: apport no longer attaches dmesg, as dmesg is restricted in groovy Status in apport package in Ubuntu: Confirmed Bug description: I reported https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896091 but it was incomplete because apparently apport can no longer collect dmesg log now that it is restricted in groovy. This means you can't report complete kernel bugs, and the instructions provided by the kernel bot are wrong. Not sure what the solution is - read journalctl, do it as root, idk? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1896095/+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 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
** Changed in: systemd (Ubuntu Groovy) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in apport source package in Groovy: Confirmed Status in systemd source package in Groovy: Confirmed Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start P
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
** Changed in: systemd (Ubuntu Groovy) Assignee: (unassigned) => Balint Reczey (rbalint) ** Changed in: systemd (Ubuntu Groovy) Status: New => 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/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Status in systemd package in Ubuntu: In Progress Status in apport source package in Groovy: Confirmed Status in systemd source package in Groovy: In Progress Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed
[Touch-packages] [Bug 1896073] Re: SRU the current 2.3.6 stable update
** Changed in: tracker (Ubuntu) Importance: Undecided => Low ** Changed in: tracker (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1896073 Title: SRU the current 2.3.6 stable update Status in tracker package in Ubuntu: Fix Released Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/tracker/-/blob/tracker-2.3/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that file search works correctly from the command line, shell and nautilus * Regression potential There is no specific change or feature to test in that update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1896073/+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 1896072] Re: SRU the current 2.3.6 stable update
** Changed in: tracker (Ubuntu) Importance: Undecided => Low ** Changed in: tracker (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1896072 Title: SRU the current 2.3.6 stable update Status in tracker package in Ubuntu: Invalid Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/tracker/-/blob/tracker-2.3/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that file search works correctly from the command line, shell and nautilus * Regression potential There is no specific change or feature to test in that update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1896072/+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 1896072] [NEW] SRU the current 2.3.6 stable update
Public bug reported: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/tracker/-/blob/tracker-2.3/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that file search works correctly from the command line, shell and nautilus * Regression potential There is no specific change or feature to test in that update ** Affects: tracker (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1896072 Title: SRU the current 2.3.6 stable update Status in tracker package in Ubuntu: New Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/tracker/-/blob/tracker-2.3/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that file search works correctly from the command line, shell and nautilus * Regression potential There is no specific change or feature to test in that update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1896072/+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 1896073] [NEW] SRU the current 2.3.6 stable update
Public bug reported: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/tracker/-/blob/tracker-2.3/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that file search works correctly from the command line, shell and nautilus * Regression potential There is no specific change or feature to test in that update ** Affects: tracker (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1896073 Title: SRU the current 2.3.6 stable update Status in tracker package in Ubuntu: New Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/tracker/-/blob/tracker-2.3/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that file search works correctly from the command line, shell and nautilus * Regression potential There is no specific change or feature to test in that update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1896073/+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 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM
This is the failing function 221 /* returns -1 on error or profile for libvirtd is unconfined, 0 if complain 222 * mode and 1 if enforcing. This is required because at present you cannot 223 * aa_change_profile() from a process that is unconfined. 224 */ 225 static int 226 use_apparmor(void) 227 { 228 int rc = -1; 229 char *libvirt_daemon = NULL; 230 231 if (virFileResolveLink("/proc/self/exe", &libvirt_daemon) < 0) { 232 virReportError(VIR_ERR_INTERNAL_ERROR, 233"%s", _("could not find libvirtd")); 234 return rc; 235 } 236 237 /* If libvirt_lxc is calling us, then consider apparmor is used 238 * and enforced. */ 239 if (strstr(libvirt_daemon, "libvirt_lxc")) 240 return 1; 241 242 if (access(APPARMOR_PROFILES_PATH, R_OK) != 0) 243 goto cleanup; 244 245 /* First check profile status using full binary path. If that fails 246 * check using profile name. 247 */ 248 rc = profile_status(libvirt_daemon, 1); 249 if (rc < 0) { 250 rc = profile_status("libvirtd", 1); 251 /* Error or unconfined should all result in -1 */ 252 if (rc < 0) 253 rc = -1; 254 } 255 256 cleanup: 257 VIR_FREE(libvirt_daemon); 258 return rc; 259 } -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1895967 Title: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM Status in apparmor package in Ubuntu: Incomplete Bug description: Hi, I stumbled over this due to automatic tests checking proposed. I found that Focal no more could migrate to Groovy with: $ virsh migrate --unsafe --live fguest qemu+ssh://10.162.30.163/system error: unsupported configuration: Security driver model 'apparmor' is not available I looked after it and found that while all former releases detected apparmor correctly: $ virsh capabilities | grep -C 3 secmodel apparmor 0 dac 0 +64055:+108 +64055:+108 Now on groovy that didn't work anymore: none 0 dac 0 +64055:+108 +64055:+108 Since 3.0 is only in proposed: # apt-cache policy apparmor apparmor: Installed: 2.13.3-7ubuntu6 Candidate: 3.0.0~beta1-0ubuntu1 Version table: 3.0.0~beta1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages *** 2.13.3-7ubuntu6 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status I installed the former version. $ apt install apparmor=2.13.3-7ubuntu6 $ rm /var/cache/libvirt/qemu/capabilities/* $ systemctl restart libvirtd And
[Touch-packages] [Bug 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM
Lookup fails: (gdb) fin Run till exit from #0 virSecurityDriverLookup (name=name@entry=0x0, virtDriver=virtDriver@entry=0x7fffd26ae1b2 "QEMU") at ../../../src/security/security_driver.c:50 virSecurityManagerNew (name=name@entry=0x0, virtDriver=virtDriver@entry=0x7fffd26ae1b2 "QEMU", flags=flags@entry=10) at ../../../src/security/security_manager.c:182 182 ../../../src/security/security_manager.c: No such file or directory. Value returned is $2 = (virSecurityDriver *) 0x77fad4c0 This goes via AppArmorSecurityManagerProbe Good: Value returned is $3 = 0 Bad: Value returned is $5 = -2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1895967 Title: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM Status in apparmor package in Ubuntu: Incomplete Bug description: Hi, I stumbled over this due to automatic tests checking proposed. I found that Focal no more could migrate to Groovy with: $ virsh migrate --unsafe --live fguest qemu+ssh://10.162.30.163/system error: unsupported configuration: Security driver model 'apparmor' is not available I looked after it and found that while all former releases detected apparmor correctly: $ virsh capabilities | grep -C 3 secmodel apparmor 0 dac 0 +64055:+108 +64055:+108 Now on groovy that didn't work anymore: none 0 dac 0 +64055:+108 +64055:+108 Since 3.0 is only in proposed: # apt-cache policy apparmor apparmor: Installed: 2.13.3-7ubuntu6 Candidate: 3.0.0~beta1-0ubuntu1 Version table: 3.0.0~beta1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages *** 2.13.3-7ubuntu6 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status I installed the former version. $ apt install apparmor=2.13.3-7ubuntu6 $ rm /var/cache/libvirt/qemu/capabilities/* $ systemctl restart libvirtd And it works again. Interestingly going back to 3.0 then works and keeps working. Therefore maybe it is a red-herring and I'll consider it incomplete & low prio for now until I know more (allowing others that might see the same to find this bug and chime in). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895967/+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 1895418] Re: systemd-resolved default config for Caching is still "yes"
** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Groovy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1895418 Title: systemd-resolved default config for Caching is still "yes" Status in systemd package in Ubuntu: New Status in systemd source package in Focal: New Status in systemd source package in Groovy: New Bug description: Back in December, the default for systemd-resolved caching in Ubuntu systemd was changed to "no-negative" from the upstream default "yes" [0] In this change, the default value in the resolved.conf file was missed. As the defaults in this file are commented, the effective default is still "no-negative", however when viewing the config file, the commented default "yes" is at odds with the man page resolved.conf(5), which correctly states the default as "no-negative". This was an issue for me as I set DNSSEC to "yes", and expected Caching to also be "yes". Running DNSSEC with the default "no- negative" Caching is detrimental to performance resolving unsigned zones, as the non-existence of DNSSEC RRs must be looked up every time. The issue with the intersection of DNSSEC and Caching is for upstream, but the least that needs to be done here is updating the resolved.conf template with "Caching=no-negative" to match the man page and behaviour, and perhaps even adding a note to the "DNSSEC=" section of resolved.conf(5) that Caching should be enabled. Now that I'm looking at that man page, the default for DNSSEC is also listed as "allow- downgrade", whereas the default for Ubuntu is "no". [0] https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/systemd/commit/?id=b42658843a9496d6b6bb68ac159f2a9f0a8ba9db&h =ubuntu-focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895418/+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 1895665] Re: PulseAudio automatically switches from HDMI 2 after display sleep
It seems that it depends on connected monitor. In my case monitor goes to power saving mode after laptop suspend or in few minutes after system lock. So ubuntu switches to analog device after resume/unlock. But its not so critical, because device can be easily changed with tray icon. And for HDMI 2 selecting I also had to open sound settings window. Btw, maybe try to set priority=99 for hdmi-output-1.conf? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1895665 Title: PulseAudio automatically switches from HDMI 2 after display sleep Status in pulseaudio package in Ubuntu: New Bug description: I have an Nvidia based video card that has an HDMI output + a DisplayPort output. DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output is listed as "Digital Stereo (HDMI 2)". I prefer to use "Digital Stereo (HDMI 2)". But after each display sleep (screen lock for example) audio is switched to built in audio ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 15 14:56:58 2020 InstallationDate: Installed on 2020-06-20 (86 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0CNDTP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM
Need to check the init of the bunch in qemuSecurityInit and qemuSecurityNew. But that happens at daemon start and not later when probing caps. virQEMUDriverConfigLoadSecurityEntry load this from config and it includes apparmor in both: /etc/libvirt/qemu.conf:# security_driver = [ "selinux", "apparmor" ] So the initialization must go wrong in the bad case. virSecurityManagerNew loooks up the driver via virSecurityDriverLookup(name, virtDriver); Then it calls virSecurityManagerNewDriver Already differs here: bad: Thread 17 "daemon-init" hit Breakpoint 1, virSecurityManagerNew (name=name@entry=0x0, virtDriver=virtDriver@entry=0x7fffea6ae1b2 "QEMU", flags=flags@entry=10) at ../../../src/security/security_manager.c:180 180 ../../../src/security/security_manager.c: No such file or directory. (gdb) c Continuing. Thread 17 "daemon-init" hit Breakpoint 2, virSecurityDriverLookup (name=name@entry=0x0, virtDriver=virtDriver@entry=0x7fffea6ae1b2 "QEMU") at ../../../src/security/security_driver.c:50 50 ../../../src/security/security_driver.c: No such file or directory. (gdb) c Continuing. Thread 17 "daemon-init" hit Breakpoint 3, virSecurityManagerNewDriver (drv=0x77fad4c0 , virtDriver=virtDriver@entry=0x7fffea6ae1b2 "QEMU", flags=8) at ../../../src/security/security_manager.c:78 78 ../../../src/security/security_manager.c: No such file or directory. (gdb) c Continuing. Thread 17 "daemon-init" hit Breakpoint 3, virSecurityManagerNewDriver (drv=0x77fad640 , virtDriver=0x7fffea6ae1b2 "QEMU", flags=flags@entry=8) at ../../../src/security/security_manager.c:78 78 in ../../../src/security/security_manager.c Good: Thread 17 "daemon-init" hit Breakpoint 1, virSecurityManagerNew (name=name@entry=0x0, virtDriver=virtDriver@entry=0x7f694365e1b2 "QEMU", flags=flags@entry=10) at ../../../src/security/security_manager.c:180 180 ../../../src/security/security_manager.c: No such file or directory. (gdb) c Continuing. Thread 17 "daemon-init" hit Breakpoint 2, virSecurityDriverLookup (name=name@entry=0x0, virtDriver=virtDriver@entry=0x7f694365e1b2 "QEMU") at ../../../src/security/security_driver.c:50 50 ../../../src/security/security_driver.c: No such file or directory. (gdb) c Continuing. Thread 17 "daemon-init" hit Breakpoint 3, virSecurityManagerNewDriver (drv=0x7f694ff5cae0 , virtDriver=virtDriver@entry=0x7f694365e1b2 "QEMU", flags=10) at ../../../src/security/security_manager.c:78 78 ../../../src/security/security_manager.c: No such file or directory. (gdb) c Continuing. Thread 17 "daemon-init" hit Breakpoint 3, virSecurityManagerNewDriver (drv=0x7f694ff5c640 , virtDriver=0x7f694365e1b2 "QEMU", flags=flags@entry=10) at ../../../src/security/security_manager.c:78 78 in ../../../src/security/security_manager.c P.S. I might need a debug build going further yet I'm unsure if installing that might change the bug conditions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1895967 Title: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM Status in apparmor package in Ubuntu: Incomplete Bug description: Hi, I stumbled over this due to automatic tests checking proposed. I found that Focal no more could migrate to Groovy with: $ virsh migrate --unsafe --live fguest qemu+ssh://10.162.30.163/system error: unsupported configuration: Security driver model 'apparmor' is not available I looked after it and found that while all former releases detected apparmor correctly: $ virsh capabilities | grep -C 3 secmodel apparmor 0 dac 0 +64055:+108 +64055:+108 Now on groovy that didn't work anymore: none 0 dac 0 +64055:+108 +64055:+108 Since 3.0 is only in proposed: # apt-cache policy apparmor apparmor: Installed: 2.13.3-7ubuntu6 Candidate: 3.0.0~beta1-0ubuntu1 Version table: 3.0.0~beta1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages *** 2.13.3-7ubuntu6 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status I installed the former version. $ apt install apparmor=2.13.3-7ubuntu6 $ rm /var/cache/libvirt/qemu/capabilities/* $ systemctl restart libvirtd And it works again. Interestingly going back to 3.0 then works and keeps working. Therefore maybe it is a red-herring and I'll consider it incomplete & low prio for now until I know more (allowing others that might see the same to find this bug and chime in). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895967/+subscriptions -- Mailing list: https://launc
[Touch-packages] [Bug 1861358] Re: tracker search hangs and never returns results
** Description changed: + * Impact + the tracker search utility isn't working + + * Test case + $ tracker search something + + it should return results if there are any matching items + + * regression potential + it's a build flag change, just check that the tracker search works including in the desktop and nautilus + + -- + When I run $ tracker search -f Bruni I see the following output on console - (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot register existing type 'TrackerLanguage' (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot add private field to invalid (non-instantiatable) type '' (tracker search:2): GLib-CRITICAL **: 00:31:10.761: g_once_init_leave: assertion 'result != 0' failed (tracker search:2): GLib-GObject-CRITICAL **: 00:31:10.761: g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed - The program hangs and never returns. Sending Control-C brings me back to prompt ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.3.0-1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Jan 30 00:31:59 2020 ExecutablePath: /usr/bin/tracker InstallationDate: Installed on 2016-11-05 (1180 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2020-01-21 (8 days ago) ** Changed in: tracker (Ubuntu) Importance: Undecided => High ** Changed in: tracker (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1861358 Title: tracker search hangs and never returns results Status in tracker package in Ubuntu: Fix Committed Bug description: * Impact the tracker search utility isn't working * Test case $ tracker search something it should return results if there are any matching items * regression potential it's a build flag change, just check that the tracker search works including in the desktop and nautilus -- When I run $ tracker search -f Bruni I see the following output on console - (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot register existing type 'TrackerLanguage' (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot add private field to invalid (non-instantiatable) type '' (tracker search:2): GLib-CRITICAL **: 00:31:10.761: g_once_init_leave: assertion 'result != 0' failed (tracker search:2): GLib-GObject-CRITICAL **: 00:31:10.761: g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed - The program hangs and never returns. Sending Control-C brings me back to prompt ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.3.0-1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Jan 30 00:31:59 2020 ExecutablePath: /usr/bin/tracker InstallationDate: Installed on 2016-11-05 (1180 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2020-01-21 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1861358/+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 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default
This bug was fixed in the package dnsmasq - 2.82-1ubuntu1 --- dnsmasq (2.82-1ubuntu1) groovy; urgency=medium * src/radv.c: avoid leases to be issued forever when not set (LP: #1894619) -- Christian Ehrhardt Wed, 16 Sep 2020 14:26:58 +0200 ** Changed in: dnsmasq (Ubuntu) Status: Triaged => Fix Released -- 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/1894619 Title: [2.82 regression] router announcements have 'forever' lifetime by default Status in dnsmasq package in Ubuntu: Fix Released Bug description: The default lifetime was changed to 1 day in 2.82 in the change corresponding to this changelog entry: Change default lease time for DHCPv6 to one day. Fine, but the same commit also did this: Alter calculation of preferred and valid times in router advertisements, so that these do not have a floor applied of the lease time in the dhcp-range if this is not explicitly specified and is merely the default. And that change is buggy and causes advertisements to have infinite lifetime, when you are using the default. See this thread http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2020q3/014341.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+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 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM
Good: (gdb) p *((virSecurityStackDataPtr)(((virQEMUDriverPtr)conn->privateData )->securityManager->privateData))->itemsHead->securityManager $7 = {parent = {parent = {parent_instance = {g_type_instance = {g_class = 0x7f430805ddf0}, ref_count = 1, qdata = 0x0}}, lock = {lock = {__data = {__lock = 0, __count = 0, __owner = 0, __nusers = 0, __kind = 512, __spins = 0, __elision = 0, __list = {__prev = 0x0, __next = 0x0}}, __size = '\000' , "\002", '\000' , __align = 0}}}, drv = 0x7f435aadfae0 , flags = 10, virtDriver = 0x7f43541e71b2 "QEMU", privateData = 0x0} (gdb) p *((virSecurityStackDataPtr)(((virQEMUDriverPtr)conn->privateData )->securityManager->privateData))->itemsHead->next->securityManager $8 = {parent = {parent = {parent_instance = {g_type_instance = {g_class = 0x7f430805ddf0}, ref_count = 1, qdata = 0x0}}, lock = {lock = {__data = {__lock = 0, __count = 0, __owner = 0, __nusers = 0, __kind = 512, __spins = 0, __elision = 0, __list = {__prev = 0x0, __next = 0x0}}, __size = '\000' , "\002", '\000' , __align = 0}}}, drv = 0x7f435aadf7c0 , flags = 10, virtDriver = 0x7f43541e71b2 "QEMU", privateData = 0x7f430807b180} Bad: (gdb) p *((virSecurityStackDataPtr)(((virQEMUDriverPtr)conn->privateData )->securityManager->privateData))->itemsHead->securityManager $9 = {parent = {parent = {parent_instance = {g_type_instance = {g_class = 0x7f8b0c0259e0}, ref_count = 1, qdata = 0x0}}, lock = {lock = {__data = {__lock = 0, __count = 0, __owner = 0, __nusers = 0, __kind = 512, __spins = 0, __elision = 0, __list = {__prev = 0x0, __next = 0x0}}, __size = '\000' , "\002", '\000' , __align = 0}}}, drv = 0x7f8b572d24c0 , flags = 8, virtDriver = 0x7f8b501d91b2 "QEMU", privateData = 0x0} (gdb) p *((virSecurityStackDataPtr)(((virQEMUDriverPtr)conn->privateData )->securityManager->privateData))->itemsHead->next->securityManager $10 = {parent = {parent = {parent_instance = {g_type_instance = {g_class = 0x7f8b0c0259e0}, ref_count = 1, qdata = 0x0}}, lock = {lock = {__data = {__lock = 0, __count = 0, __owner = 0, __nusers = 0, __kind = 512, __spins = 0, __elision = 0, __list = {__prev = 0x0, __next = 0x0}}, __size = '\000' , "\002", '\000' , __align = 0}}}, drv = 0x7f8b572d27c0 , flags = 10, virtDriver = 0x7f8b501d91b2 "QEMU", privateData = 0x7f8b0c07add0} See virSecurityDriverNop vs virAppArmorSecurityDriver in the above output -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1895967 Title: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM Status in apparmor package in Ubuntu: Incomplete Bug description: Hi, I stumbled over this due to automatic tests checking proposed. I found that Focal no more could migrate to Groovy with: $ virsh migrate --unsafe --live fguest qemu+ssh://10.162.30.163/system error: unsupported configuration: Security driver model 'apparmor' is not available I looked after it and found that while all former releases detected apparmor correctly: $ virsh capabilities | grep -C 3 secmodel apparmor 0 dac 0 +64055:+108 +64055:+108 Now on groovy that didn't work anymore: none 0 dac 0 +64055:+108 +64055:+108 Since 3.0 is only in proposed: # apt-cache policy apparmor apparmor: Installed: 2.13.3-7ubuntu6 Candidate: 3.0.0~beta1-0ubuntu1 Version table: 3.0.0~beta1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages *** 2.13.3-7ubuntu6 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status I installed the former version. $ apt install apparmor=2.13.3-7ubuntu6 $ rm /var/cache/libvirt/qemu/capabilities/* $ systemctl restart libvirtd And it works again. Interestingly going back to 3.0 then works and keeps working. Therefore maybe it is a red-herring and I'll consider it incomplete & low prio for now until I know more (allowing others that might see the same to find this bug and chime in). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895967/+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 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM
for (i = 0; sec_managers[i]; i++) { ... VIR_DEBUG("Initialized caps for security driver \"%s\" with " Good: - apparmor - dac Bad: - none - dac In function virQEMUDriverCreateCapabilities. So it isn't probing apparmor because it isn't even in the list. That list is from "qemuSecurityGetNested" qemuSecurityGetNested == virSecurityManagerGetNested -> virSecurityStackGetNested(mgr) The latter iterates on the list priv->itemsHead which is from the security manager. That in turn is from driver->securityManager of virQEMUDriverGetCapabilities(driver) virCapsPtr virQEMUDriverCreateCapabilities(virQEMUDriverPtr driver) (gdb) bt #0 virSecurityStackGetNested (mgr=mgr@entry=0x7f8b0c00dde0) at ../../../src/security/security_stack.c:613 #1 0x7f8b5704f2b8 in virSecurityManagerGetNested (mgr=0x7f8b0c00dde0) at ../../../src/security/security_manager.c:1035 #2 0x7f8b50133970 in virQEMUDriverCreateCapabilities (driver=0x7f8b0c051550) at ../../../src/qemu/qemu_conf.c:1344 #3 0x7f8b50133c18 in virQEMUDriverGetCapabilities (driver=0x7f8b0c051550, refresh=) at ../../../src/qemu/qemu_conf.c:1397 #4 0x7f8b5019e0b8 in qemuConnectGetCapabilities (conn=) at ../../../src/qemu/qemu_driver.c:1328 #5 0x7f8b57171953 in virConnectGetCapabilities (conn=0x7f8b28004050) at ../../../src/libvirt-host.c:467 #6 0xa51f16ec in remoteDispatchConnectGetCapabilities (server=0xa5c1d080, msg=0xa5c2bc80, ret=0x7f8b48000e60, rerr=0x7f8b51be6920, client=0xa5c2c070) at ./remote/remote_daemon_dispatch_stubs.h:766 #7 remoteDispatchConnectGetCapabilitiesHelper (server=0xa5c1d080, client=0xa5c2c070, msg=0xa5c2bc80, rerr=0x7f8b51be6920, args=0x0, ret=0x7f8b48000e60) at ./remote/remote_daemon_dispatch_stubs.h:748 #8 0x7f8b5707d470 in virNetServerProgramDispatchCall (msg=0xa5c2bc80, client=0xa5c2c070, server=0xa5c1d080, prog=0xa5c25810) at ../../../src/rpc/virnetserverprogram.c:430 #9 virNetServerProgramDispatch (prog=0xa5c25810, server=server@entry=0xa5c1d080, client=0xa5c2c070, msg=0xa5c2bc80) at ../../../src/rpc/virnetserverprogram.c:302 #10 0x7f8b570825a8 in virNetServerProcessMsg (msg=, prog=, client=, srv=0xa5c1d080) at ../../../src/rpc/virnetserver.c:137 #11 virNetServerHandleJob (jobOpaque=0xa5bf97f0, opaque=0xa5c1d080) at ../../../src/rpc/virnetserver.c:154 #12 0x7f8b56f901e2 in virThreadPoolWorker (opaque=) at ../../../src/util/virthreadpool.c:163 #13 0x7f8b56f8f769 in virThreadHelper (data=) at ../../../src/util/virthread.c:233 #14 0x7f8b56c61590 in start_thread (arg=0x7f8b51be7640) at pthread_create.c:463 #15 0x7f8b56b6c223 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1895967 Title: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM Status in apparmor package in Ubuntu: Incomplete Bug description: Hi, I stumbled over this due to automatic tests checking proposed. I found that Focal no more could migrate to Groovy with: $ virsh migrate --unsafe --live fguest qemu+ssh://10.162.30.163/system error: unsupported configuration: Security driver model 'apparmor' is not available I looked after it and found that while all former releases detected apparmor correctly: $ virsh capabilities | grep -C 3 secmodel apparmor 0 dac 0 +64055:+108 +64055:+108 Now on groovy that didn't work anymore: none 0 dac 0 +64055:+108 +64055:+108 Since 3.0 is only in proposed: # apt-cache policy apparmor apparmor: Installed: 2.13.3-7ubuntu6 Candidate: 3.0.0~beta1-0ubuntu1 Version table: 3.0.0~beta1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages *** 2.13.3-7ubuntu6 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status I installed the former version. $ apt install apparmor=2.13.3-7ubuntu6 $ rm /var/cache/libvirt/qemu/capabilities/* $ systemctl restart libvirtd And it works again. Interestingly going back to 3.0 then works and keeps working. Therefore maybe it is a red-herring and I'll consider it incomplete & low prio for now until I know more (allowing others that might see the same to find this bug and chime in). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895967/+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 1895060] Re: [FFe] apparmor 3 upstream release
FYI, the fix for the dbus issue is https://gitlab.com/apparmor/apparmor/-/merge_requests/625. We're preparing an ubuntu2 upload now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1895060 Title: [FFe] apparmor 3 upstream release Status in apparmor package in Ubuntu: New Bug description: As per the draft upstream release notes[1]: AppArmor 3.0 is a major new release of the AppArmor user space that makes an important change to policy development and support. Its focus is transitioning policy to the new features ABI and as such other new features have been limited. Apprmor 3.0 is a bridge release between older AppArmor 2.x policy and the newer AppArmor 3 style policy which requires the declaration of a features abi. As such AppArmor 3.0 will be a short lived release, and will not receive long term support. The following AppArmor 3.1 feature release is planned to be a regular release, please take this into account when including AppArmor 3.0 into a distro release. As such, Ubuntu 20.10 provides a great opportunity to introduce AppArmor3 to Ubuntu and provide these new capabilities to users and system administrators. The short support lifespan of Ubuntu 20.10 ensures that there is alignment with the limited support lifetime of AppArmor 3.0 from upstream, whilst giving good exposure and opportunity to test and exercise the new features in AppArmor 3.x on the road to Ubuntu 22.04. A highlight of new features provided by AppArmor 3.0 include: - Policy now must declare the feature abi it was developed for if it is to use any new features. This ensures that old policy will not become incompatible with new kernels that support additional AppArmor features. - The use of profile names that are based on pathnames are deprecated. - Support for new kernel features (requires appropriate features abi tagging in policy) - upstream v8 network socket rules - xattr attachment conditionals - capabilities PERFMON and BPF - Improved compiler warnings and semantic checks - aa-status rewritten in C (previously was python) with additional features - supports use in systems/images where python is not available - supports kill, unconfined and mixed profile modes - Rewritten aa-notify (previously was perl, now python3) - shared backend with other python tools - support use of aa.CONFDIR instead of hard coded /etc/apparmor - improved message layout - Improved support for kernels that support LSM stacking - New utility aa-features-abi to extract and work with kernel abi features - New utility aa-load to load binary policy without calling the apparmor_parser - Support for profile modes - enforce (default when no mode flag is supplied) - kill (experimental) - unconfined (experimental) The use of the new AppArmor profile feature ABI includes a default configuration (for the Ubuntu packaged version of AppArmor proposed in this FFE) for the AppArmor features within the 5.4 Linux kernel - this ensures that all profiles provided in AppArmor3 for groovy will conform to this feature set and that upgrades to the kernel version (say to 5.8) that may include newer AppArmor confinement features will not result in additional policy denials as a result (since say the existing profile did not specify a rule for a new AppArmor feature which is now supported by the upgraded kernel). This ensures that there will be no regressions in application behaviour as a result of AppArmor kernel feature upgrades. TESTING This has been extensively tested by the security team - this includes following the documented Ubuntu merges test plan[2] for AppArmor and the extensive QA Regression Tests[3] for AppArmor as well. This ensures that the various applications that make heavy use of AppArmor (LXD, docker, lxc, dbus, libvirt, snapd etc) have all been exercised and no regressions have been observed. All tests have passed and demonstrated both apparmor and the various applications that use it to be working as expected. BUILD LOGS This is currently uploaded to groovy-proposed, build logs can be found on Launchpad at: https://launchpad.net/ubuntu/+source/apparmor/3.0.0~beta1-0ubuntu1 INSTALL LOG See attached (https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895060/+attachment/5411197/+files /groovy-proposed-apparmor-install.log) for a log showing install of the packages from groovy-proposed [1] https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_3.0 [2] https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor [3] https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895060/+subscriptions -- Mailing list: https://lau
[Touch-packages] [Bug 1895967] Re: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM
It seems once fixed the system is ok and I can't get into the bad state again :/ I tried on another bad system (withotu changing back to the former version) 1. A restart of the service 2. Trying to force capabilities reset (remove cache) + service restart None of these got it into the good case, so I might be able to debug here what happens when probing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1895967 Title: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM Status in apparmor package in Ubuntu: Incomplete Bug description: Hi, I stumbled over this due to automatic tests checking proposed. I found that Focal no more could migrate to Groovy with: $ virsh migrate --unsafe --live fguest qemu+ssh://10.162.30.163/system error: unsupported configuration: Security driver model 'apparmor' is not available I looked after it and found that while all former releases detected apparmor correctly: $ virsh capabilities | grep -C 3 secmodel apparmor 0 dac 0 +64055:+108 +64055:+108 Now on groovy that didn't work anymore: none 0 dac 0 +64055:+108 +64055:+108 Since 3.0 is only in proposed: # apt-cache policy apparmor apparmor: Installed: 2.13.3-7ubuntu6 Candidate: 3.0.0~beta1-0ubuntu1 Version table: 3.0.0~beta1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages *** 2.13.3-7ubuntu6 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status I installed the former version. $ apt install apparmor=2.13.3-7ubuntu6 $ rm /var/cache/libvirt/qemu/capabilities/* $ systemctl restart libvirtd And it works again. Interestingly going back to 3.0 then works and keeps working. Therefore maybe it is a red-herring and I'll consider it incomplete & low prio for now until I know more (allowing others that might see the same to find this bug and chime in). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895967/+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 1895839] Re: CVE-2020-24977
** Bug watch added: Debian Bug tracker #969529 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969529 ** Also affects: libxml2 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969529 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1895839 Title: CVE-2020-24977 Status in libxml2 package in Ubuntu: New Status in libxml2 package in Debian: Unknown Bug description: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24977 Upstream patch: https://gitlab.gnome.org/GNOME/libxml2/-/commit/8e7c20a1af8776677d7890f30b7a180567701a49 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1895839/+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 1890272] Re: SRU: Update to the final python 2.7.18 release
** Description changed: Ubuntu 20.04 LTS shipped with the python 2.7.18 release candidate. Please let's update to the final release. Upstream changes are: - Documentation changes - Identify as 2.7.18 instead of 2.7.18rc1 Acceptance criteria: The package builds, and the testsuite doesn't show regressions. + + The package was also part of an archive test rebuild (main), and didn't + show any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1890272 Title: SRU: Update to the final python 2.7.18 release Status in python2.7 package in Ubuntu: New Bug description: Ubuntu 20.04 LTS shipped with the python 2.7.18 release candidate. Please let's update to the final release. Upstream changes are: - Documentation changes - Identify as 2.7.18 instead of 2.7.18rc1 Acceptance criteria: The package builds, and the testsuite doesn't show regressions. The package was also part of an archive test rebuild (main), and didn't show any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1890272/+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 1890270] Re: SRU: update gdb 9.2 for 20.04 LTS
** Description changed: SRU: update gdb 9.2 for 20.04 LTS according to https://sourceware.org/gdb/ this is a bug fix release: """ This is a minor corrective release over GDB 9.1, fixing the following issues: PR tui/25586 (Resizing the source/disassembly or command window produces corrupted display) PR gdb/25650 (GDB can't 'printf' a convenience variable holding an inferior address) PR build/25981 (Use of short i386 register names breaks compilation on recent Solaris 11.4) PR symtab/26003 (infinite loop loading symbols from separate debug objfile) PR build/26029 (GDB build failure on SPARC) """ Regression potential: minimal, package also not used by normal users, but for development. Acceptence criteria: Package builds, no regressions in the testsuite. + + The package also was part of a focal test rebuild, see LP: #1879481. -- 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/1890270 Title: SRU: update gdb 9.2 for 20.04 LTS Status in gdb package in Ubuntu: New Bug description: SRU: update gdb 9.2 for 20.04 LTS according to https://sourceware.org/gdb/ this is a bug fix release: """ This is a minor corrective release over GDB 9.1, fixing the following issues: PR tui/25586 (Resizing the source/disassembly or command window produces corrupted display) PR gdb/25650 (GDB can't 'printf' a convenience variable holding an inferior address) PR build/25981 (Use of short i386 register names breaks compilation on recent Solaris 11.4) PR symtab/26003 (infinite loop loading symbols from separate debug objfile) PR build/26029 (GDB build failure on SPARC) """ Regression potential: minimal, package also not used by normal users, but for development. Acceptence criteria: Package builds, no regressions in the testsuite. The package also was part of a focal test rebuild, see LP: #1879481. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1890270/+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 1895967] [NEW] 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM
Public bug reported: Hi, I stumbled over this due to automatic tests checking proposed. I found that Focal no more could migrate to Groovy with: $ virsh migrate --unsafe --live fguest qemu+ssh://10.162.30.163/system error: unsupported configuration: Security driver model 'apparmor' is not available I looked after it and found that while all former releases detected apparmor correctly: $ virsh capabilities | grep -C 3 secmodel apparmor 0 dac 0 +64055:+108 +64055:+108 Now on groovy that didn't work anymore: none 0 dac 0 +64055:+108 +64055:+108 Since 3.0 is only in proposed: # apt-cache policy apparmor apparmor: Installed: 2.13.3-7ubuntu6 Candidate: 3.0.0~beta1-0ubuntu1 Version table: 3.0.0~beta1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages *** 2.13.3-7ubuntu6 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status I installed the former version. $ apt install apparmor=2.13.3-7ubuntu6 $ rm /var/cache/libvirt/qemu/capabilities/* $ systemctl restart libvirtd And it works again. Interestingly going back to 3.0 then works and keeps working. Therefore maybe it is a red-herring and I'll consider it incomplete & low prio for now until I know more (allowing others that might see the same to find this bug and chime in). ** Affects: apparmor (Ubuntu) Importance: Low Status: Incomplete ** Changed in: apparmor (Ubuntu) Status: New => Incomplete ** Changed in: apparmor (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1895967 Title: 3.0.0~beta1-0ubuntu1 in Groovy breaks Libvirt/Qemu/KVM Status in apparmor package in Ubuntu: Incomplete Bug description: Hi, I stumbled over this due to automatic tests checking proposed. I found that Focal no more could migrate to Groovy with: $ virsh migrate --unsafe --live fguest qemu+ssh://10.162.30.163/system error: unsupported configuration: Security driver model 'apparmor' is not available I looked after it and found that while all former releases detected apparmor correctly: $ virsh capabilities | grep -C 3 secmodel apparmor 0 dac 0 +64055:+108 +64055:+108 Now on groovy that didn't work anymore: none 0 dac 0 +64055:+108 +64055:+108 Since 3.0 is only in proposed: # apt-cache policy apparmor apparmor: Installed: 2.13.3-7ubuntu6 Candidate: 3.0.0~beta1-0ubuntu1 Version table: 3.0.0~beta1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages *** 2.13.3-7ubuntu6 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status I installed the former version. $ apt install apparmor=2.13.3-7ubuntu6 $ rm /var/cache/libvirt/qemu/capabilities/* $ systemctl restart libvirtd And it works again. Interestingly going back to 3.0 then works and keeps working. Therefore maybe it is a red-herring and I'll consider it incomplete & low prio for now until I know more (allowing others that might see the same to find this bug and chime in). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895967/+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 1895576] Re: boot-and-services in tests-in-lxd autopkgtest fails in groovy on s390x
OK, the next upload passes on s390x, so this will likely be resolved. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1895576 Title: boot-and-services in tests-in-lxd autopkgtest fails in groovy on s390x Status in systemd package in Ubuntu: New Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- groovy/groovy/s390x/s/systemd/20200903_184028_2bbdf@/log.gz ... test_rsyslog (__main__.ServicesTest) ... FAIL test_tmp_cleanup (__main__.ServicesTest) ... ok test_tmp_mount (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' == FAIL: test_rsyslog (__main__.ServicesTest) -- Traceback (most recent call last): File "/tmp/autopkgtest.15TVnz/build.ZVh/real-tree/debian/tests/boot-and-services", line 120, in test_rsyslog self.assertRegex(log, 'systemd.*Reached target Graphical Interface') ... Interestingly it does not fail locally on an s390x Focal VM running boot-and-services in LXD. Kernel: Linux juju-d7a408-generic-21 5.4.0-14-generic Also interestingly it is passing with cryptsetup/2:2.3.3-1ubuntu5 glibc/2.32-0ubuntu2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895576/+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 1892979] Re: Sizing issue on Startup
*** This bug is a duplicate of bug 1892440 *** https://bugs.launchpad.net/bugs/1892440 ** This bug is no longer a duplicate of bug 1892521 Shell text is too big in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) ** This bug has been marked a duplicate of bug 1892440 Shell text is the wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1892979 Title: Sizing issue on Startup Status in xorg package in Ubuntu: Confirmed Bug description: Hello, I recently put together a new PC and installed a fresh Ubuntu 20.04. Immediately I noticed that, on startup, there was a flashing cursor and the decryption password screen was unusually large, but the login screen and desktop GUI was fine, so I thought nothing of it. With a recent update, the decryption password screen and the login screen are now both sized improperly and the text on the GUI is abnormally sized. I have included an image of the GUI with the bug apparent. If I toggle the 'large text' in universal access on then off, the problem resolves, but this is a hassle and happens every startup. I did have issues with the display driver for the GPU on installation and this may be a contributor but I am not sure and I am also not sure where to begin in troubleshooting this problem. Any help would be greatly appreciated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 26 14:15:32 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed nvidia, 440.100, 5.4.0-42-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU117 [GeForce GTX 1650] [1462:8d92] InstallationDate: Installed on 2020-07-28 (28 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID c0f4:05c0 SZH usb keyboard Bus 001 Device 003: ID :0538 USB OPTICAL MOUSE Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. B365M D3H ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: Default string dmi.board.name: B365M D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/13/2019:svnGigabyteTechnologyCo.,Ltd.:pnB365MD3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M D3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A ver
[Touch-packages] [Bug 1893771] Re: gnome fonts too large / detected screen size incorrect
*** This bug is a duplicate of bug 1892440 *** https://bugs.launchpad.net/bugs/1892440 ** This bug is no longer a duplicate of bug 1892521 Shell text is too big in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) ** This bug has been marked a duplicate of bug 1892440 Shell text is the wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893771 Title: gnome fonts too large / detected screen size incorrect Status in xorg package in Ubuntu: New Bug description: Hi! after the latest update, I observe problems with the font size used by gdm and the gnome gui. It seems that the font size is now twice as large as before. This affects the login screen as well as elements of the gui (top bar, icon names on the desktop, pop up menus when right-clicking on the desktop). Fonts of standard applications (firefox, libreofffice, etc.) still have the correct size. I'm currently using a 43" 4K monitor. xpdyinfo correctly detects its resolution (3840x2160), but the detected screen size is obviously wrong (602x341 mm2, which would correspond to a 27" monitor). Please see attached screenshot. My NVidia Driver Version is: 440.100 The problem can be temporarily fixed by going to Settings->Displays, and then clicking "Scale 200%" and "Apply". A dialog appears and asks whether I would like to keep the setting. If I click "revert", all font sizes are now ok. Unfortunately the problem reappears after a reboot. Similar reports can be found under: https://askubuntu.com/questions/1268993/ubuntu-20-04-font-and-ui-elements-too-big-on-login Many thanks for your time! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 1 12:58:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-04-26 (127 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=6643d18b-001d-4ec7-a81b-e9b6f17236aa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970 PRO GAMING/AURA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd05/16/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rn970PROGAMING/AURA:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1893771/+subscriptions -- Mailing list: http
[Touch-packages] [Bug 1895294] Re: Fix Raccoon vulnerability (CVE-2020-1968)
Oh, indeed! > 1.0.2w moves the affected ciphersuites into the "weak-ssl-ciphers" list. [...] > This is unlikely to cause interoperability problems in most cases since use > of these ciphersuites is rare. Fair enough. Thank you for clarifying. (And apologies for this noise) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1895294 Title: Fix Raccoon vulnerability (CVE-2020-1968) Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Xenial: Fix Released Bug description: Xenial's current OpenSSL (1.0.2g-1ubuntu4.16) seems to not have been patched yet against the Raccoon Attack (CVE-2020-1968): - https://www.openssl.org/news/secadv/20200909.txt - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1968 - https://raccoon-attack.com/ Ubuntu's CVE tracker still lists this as NEEDED for Xenial: - https://people.canonical.com/~ubuntu-security/cve/2020/CVE-2020-1968.html - https://people.canonical.com/~ubuntu-security/cve/pkg/openssl.html Other supported Ubuntu releases use versions of OpenSSL that are not affected. Indeed: $ apt-cache policy openssl openssl: Installed: 1.0.2g-1ubuntu4.16 $ apt-get changelog openssl | grep CVE-2020-1968 || echo "Not patched" Not patched What is the status? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1895294/+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 1895665] Re: PulseAudio automatically switches from HDMI 2 after display sleep
I did a test today, plug two monitors to Intel hdmi ports, I chose hdmi2 in the gnome-control-center, suspend and resume, the output device still on the hdmi2, I didn't reproduce the problem. When you have time, please collect the log according to https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/comments/12 and https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/comments/32 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1895665 Title: PulseAudio automatically switches from HDMI 2 after display sleep Status in pulseaudio package in Ubuntu: New Bug description: I have an Nvidia based video card that has an HDMI output + a DisplayPort output. DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output is listed as "Digital Stereo (HDMI 2)". I prefer to use "Digital Stereo (HDMI 2)". But after each display sleep (screen lock for example) audio is switched to built in audio ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 15 14:56:58 2020 InstallationDate: Installed on 2020-06-20 (86 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0CNDTP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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 1875300] Re: [Ubuntu 20.04 s390] Failed to install os from CD
Thank you Dominik for testing and confirming! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1875300 Title: [Ubuntu 20.04 s390] Failed to install os from CD Status in subiquity: Invalid Status in Ubuntu on IBM z Systems: Fix Released Status in casper package in Ubuntu: Fix Released Status in lvm2 package in Ubuntu: Fix Released Status in casper source package in Focal: Confirmed Status in lvm2 source package in Focal: Confirmed Status in casper source package in Groovy: Fix Released Status in lvm2 source package in Groovy: Fix Released Bug description: Failed to install os from CD ---Installation Media--- ubuntu-20.04-live-server-s390x.iso ---Machine type --- model: 8561 - T01 ---Steps--- Login to HMC Load CD via 'Load from Removable media or Serer' Select FTP After loaded successfully Get following message in Operating System Messages and installation failed: ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such file or dir ectory To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1875300/+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 1875300] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-09-17 03:53 EDT--- IBM Bugzilla status-> closed, Verified by IBM -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1875300 Title: [Ubuntu 20.04 s390] Failed to install os from CD Status in subiquity: Invalid Status in Ubuntu on IBM z Systems: Fix Released Status in casper package in Ubuntu: Fix Released Status in lvm2 package in Ubuntu: Fix Released Status in casper source package in Focal: Confirmed Status in lvm2 source package in Focal: Confirmed Status in casper source package in Groovy: Fix Released Status in lvm2 source package in Groovy: Fix Released Bug description: Failed to install os from CD ---Installation Media--- ubuntu-20.04-live-server-s390x.iso ---Machine type --- model: 8561 - T01 ---Steps--- Login to HMC Load CD via 'Load from Removable media or Serer' Select FTP After loaded successfully Get following message in Operating System Messages and installation failed: ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such file or dir ectory To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1875300/+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 1875300] Comment bridged from LTC Bugzilla
--- Comment From dominik.kl...@de.ibm.com 2020-09-17 03:47 EDT--- Just tried with ubuntu-20.04.1-live-server-s390x.iso and can confirm that it's now possible to enter a subnet mask which enables network installation without a customized parmfile in our environment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1875300 Title: [Ubuntu 20.04 s390] Failed to install os from CD Status in subiquity: Invalid Status in Ubuntu on IBM z Systems: Fix Released Status in casper package in Ubuntu: Fix Released Status in lvm2 package in Ubuntu: Fix Released Status in casper source package in Focal: Confirmed Status in lvm2 source package in Focal: Confirmed Status in casper source package in Groovy: Fix Released Status in lvm2 source package in Groovy: Fix Released Bug description: Failed to install os from CD ---Installation Media--- ubuntu-20.04-live-server-s390x.iso ---Machine type --- model: 8561 - T01 ---Steps--- Login to HMC Load CD via 'Load from Removable media or Serer' Select FTP After loaded successfully Get following message in Operating System Messages and installation failed: ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such file or dir ectory To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1875300/+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 1895937] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 13
** Tags removed: need-duplicate-check -- 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/1895937 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 139 Status in initramfs-tools package in Ubuntu: New Bug description: getting this error again and again. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 17 12:51:39 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 139 InstallationDate: Installed on 2020-01-22 (238 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 139 UpgradeStatus: Upgraded to focal on 2020-05-29 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1895937/+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 1895937] [NEW] package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: getting this error again and again. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 17 12:51:39 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 139 InstallationDate: Installed on 2020-01-22 (238 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 139 UpgradeStatus: Upgraded to focal on 2020-05-29 (110 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1895937 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 139 Status in initramfs-tools package in Ubuntu: New Bug description: getting this error again and again. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 17 12:51:39 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 139 InstallationDate: Installed on 2020-01-22 (238 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 139 UpgradeStatus: Upgraded to focal on 2020-05-29 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1895937/+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 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default
The tests confirmed the issue that Iain reported and that the fix works. Also no other issues popped up in the NM test using it. autopkgtest [08:47:12]: summary wpa-dhclient PASS nm.pyPASS killswitches-no-urfkill PASS urfkill-integration PASS And while https://bileto.ubuntu.com/excuses/4266/groovy.html looks pretty bad after we skip the known badtests not much is left and of those nothing seems to be due to this change. I replied upstream hoping they will accept the change so we can then push it to groovy (sooner or later we have to even without upstream saying "yes" but I'd prefer to pick exactly what is committed). => http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2020q3/014387.html Actually since this holds back other things, let us upload to groovy now (it essentially reverts to old behavior) but come back in a week to potentially update to whatever upstream did by then. -- 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/1894619 Title: [2.82 regression] router announcements have 'forever' lifetime by default Status in dnsmasq package in Ubuntu: Triaged Bug description: The default lifetime was changed to 1 day in 2.82 in the change corresponding to this changelog entry: Change default lease time for DHCPv6 to one day. Fine, but the same commit also did this: Alter calculation of preferred and valid times in router advertisements, so that these do not have a floor applied of the lease time in the dhcp-range if this is not explicitly specified and is merely the default. And that change is buggy and causes advertisements to have infinite lifetime, when you are using the default. See this thread http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2020q3/014341.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1894619/+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