[Touch-packages] [Bug 1915238] Re: warning: /var/spool/postfix/etc/ssl/certs/ca-certificates.crt and /etc/ssl/certs/ca-certificates.crt differ
** Changed in: postfix (Debian) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1915238 Title: warning: /var/spool/postfix/etc/ssl/certs/ca-certificates.crt and /etc/ssl/certs/ca-certificates.crt differ Status in ca-certificates package in Ubuntu: Invalid Status in postfix package in Ubuntu: Triaged Status in postfix package in Debian: Fix Released Bug description: Postfix package doesn't utilize update-ca-certificate's hooks mechanism. By simply copying certs from /etc/ssl/certs/ca- certificates.crt to /var/spool/postfix/etc/ssl/certs/ca- certificates.crt, this warning and potential security issues could be avoided. Something like this would be a start: $ cat /etc/ca-certificates/update.d/postfix #!/bin/bash if [ -e /var/spool/postfix/etc/ssl/certs/ca-certificates.crt ]; then echo "Updating postfix chrooted certs" cp /etc/ssl/certs/ca-certificates.crt /var/spool/postfix/etc/ssl/certs/ca-certificates.crt systemctl reload postfix fi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1915238/+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 1956128] Re: xserver-xorg-video-all requires xserver-xorg-video-ati
And yes we do have Ubuntu users with 20 year old hardware. -- 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/1956128 Title: xserver-xorg-video-all requires xserver-xorg-video-ati Status in xorg package in Ubuntu: Invalid Bug description: ATi sold to AMD in 2006. I can remove wacom from input but not ATi from video. Are more people running ATi cards in 2022~ than wacom input devices? Why is this still a required dependency? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1956128/+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 1956128] Re: xserver-xorg-video-all requires xserver-xorg-video-ati
"video-all" means it should install all video drivers. ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1956128 Title: xserver-xorg-video-all requires xserver-xorg-video-ati Status in xorg package in Ubuntu: Invalid Bug description: ATi sold to AMD in 2006. I can remove wacom from input but not ATi from video. Are more people running ATi cards in 2022~ than wacom input devices? Why is this still a required dependency? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1956128/+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 1956126] Re: xorg metapackage requires x11-apps
I agree the apps in x11-apps don't appear to be useful anymore. But the 'xorg' package itself is only a metapackage and pulling in other packages is what metapackages do. It gives you a traditional X11 environment so from that perspective, having 'xorg' install 'x11-apps' makes a lot of sense. I suggest the real bug should be "why are we installing package 'xorg'?". If you want then we can reword this bug accordingly. ** No longer affects: x11-apps (Ubuntu) ** Changed in: xorg (Ubuntu) Importance: Undecided => Wishlist ** Summary changed: - xorg metapackage requires x11-apps + xorg metapackage depends on x11-apps needlessly ** Summary changed: - xorg metapackage depends on x11-apps needlessly + xorg metapackage depends on x11-apps ** Changed in: xorg (Ubuntu) Status: New => Opinion ** Summary changed: - xorg metapackage depends on x11-apps + xorg metapackage depends on x11-apps and xorg-docs-core -- 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/1956126 Title: xorg metapackage depends on x11-apps and xorg-docs-core Status in xorg package in Ubuntu: Opinion Bug description: xorg, a required dependency of ubuntu-desktop and ubuntu-desktop- minimal requires the package x11-apps. Currently Ubuntu 22.04 Jammy defaults to Wayland. These applications are ancient and now most people won't even be using X11, much less these example applications. Why are x11-apps going to be required in April of 2022? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1956126/+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 1956127] Re: xorg metapackage requires xorg-docs-core
*** This bug is a duplicate of bug 1956126 *** https://bugs.launchpad.net/bugs/1956126 This is the same issue as bug 1956126 so will be merged with that. ** This bug has been marked a duplicate of bug 1956126 xorg metapackage depends on x11-apps -- 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/1956127 Title: xorg metapackage requires xorg-docs-core Status in xorg package in Ubuntu: New Bug description: xorg, a required dependency of ubuntu-desktop and ubuntu-desktop- minimal requires the package xorg-docs-core. Currently Ubuntu 22.04 Jammy defaults to Wayland. These docs are ancient and now most people won't even be using X11, much less this documentation. Why is x11-docs-core going to be required in April of 2022? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1956127/+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 1956043] Re: I need to stop my monitor scree from constant flicking
Thanks for the bug report. I'm going to assume it's a flickering screen you want to discuss here... Your computer appears to have an Nvidia RTX 2060 GPU and no other GPUs so you need to install a working Nvidia driver. None appears to be installed. Please open the 'Additional Drivers' app to install the latest Nvidia driver it offers you. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1956043 Title: I need to stop my monitor scree from constant flicking Status in Ubuntu: Incomplete Bug description: This PC was working normally, in May 17, 2021 at Kennedy Airport check-in for a trip to Panama Republic of Panama, I followed the commands of the security personnel to place computer and cell phones in a tray for examination.They examined my PC and two cell phone three times before returning them to me. After that examination session neither my PC nor cell phones could work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-73.82~18.04.1-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CompositorRunning: None Date: Thu Dec 30 08:17:43 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation Device [10de:1f51] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:7510] MachineType: System76 Serval ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=d5244e1e-601c-42de-a015-225055a76c68 ro nvidia.NVreg_EnableBacklightHandler=1 quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.25-1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval dmi.board.vendor: System76 dmi.board.version: serw11 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.25-1:bd07/10/2019:svnSystem76:pnServal:pvrserw11:rvnSystem76:rnServal:rvrserw11:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Serval dmi.product.sku: Not Applicable dmi.product.version: serw11 dmi.sys.vendor: System76 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Dec 29 15:03:36 2021 xserver.configfile: default xserver.errors: [drm] Failed to open DRM device for pci::01:00.0: -19 open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1956043/+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 1956107] Re: Ubuntu startup screen displays garbage
*** This bug is a duplicate of bug 1882291 *** https://bugs.launchpad.net/bugs/1882291 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1882291, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** This bug has been marked a duplicate of bug 1882291 Gnome Shell clock is truncated/corrupt on the right side -- 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/1956107 Title: Ubuntu startup screen displays garbage Status in mutter package in Ubuntu: New Bug description: The clock in the Ubuntu startup screen displays garbage sometimes. I have attached a photograph to this bug report. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Lupa evätty: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 31 18:21:52 2021 DistUpgraded: 2021-11-07 14:23:47,814 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.13.0-21-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.13.0-22-generic, x86_64: installed virtualbox, 6.1.26, 5.13.0-21-generic, x86_64: installed virtualbox, 6.1.26, 5.13.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3978] InstallationDate: Installed on 2020-09-30 (457 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20238 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-11-07 (54 days ago) dmi.bios.date: 12/07/2013 dmi.bios.release: 1.68 dmi.bios.vendor: LENOVO dmi.bios.version: 79CN44WW(V3.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G510 dmi.ec.firmware.release: 3.68 dmi.modalias: dmi:bvnLENOVO:bvr79CN44WW(V3.03):bd12/07/2013:br1.68:efr3.68:svnLENOVO:pn20238:pvrLenovoG510:rvnLENOVO:rnINVALID:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoG510:skuLENOVO_MT_20238: dmi.product.family: IDEAPAD dmi.product.name: 20238 dmi.product.sku: LENOVO_MT_20238 dmi.product.version: Lenovo G510 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1956107/+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 1955965] Re: 21.10 cannot enter desktop after blacklist nouveau driver
Please: 0. Show us exactly how you are blacklisting nouveau. 1. Reboot. 2. Try to log in (and fail) when nouveau is blacklisted. 3. Reboot again. 4. Run: journalctl -b-1 > prevboot.txt 5. Attach the resulting text file here. 6. Follow these instructions to check for crashes: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: impish -- 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/1955965 Title: 21.10 cannot enter desktop after blacklist nouveau driver Status in Ubuntu: Incomplete Bug description: Ubuntu 21.10 can NOT enter desktop after: 1) install Nvidia 470 2) blacklist nouveau driver -- why blacklist nouveau? External HDMI monitor render 0.5 frames/second when turn off built-in monitor. Render normally if both build-in and external HDMI monitor are on. Blacklisting nouveau fix `0.5 frames/s` problem in Ubuntu 21.04, but cannot enter desktop in Ubuntu 21.10 --- why not use Ubuntu 21.04 ? Ubuntu 21.04 render incorrectly, for example, if: 1) built-in monitor: scale=125%, resolution=4000x2000 2) external monitor: scale=100%, resulution=2000x1000 Ubuntu 21.10 render correctly. --- $ lspci 00:00.0 Host bridge: Intel Corporation Device 9b44 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation Device 1f99 (rev a1) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 02) ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1955965/+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 1956404] Re: package linux-firmware 1.187.24 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
** Package changed: ubuntu => initramfs-tools (Ubuntu) -- 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/1956404 Title: package linux-firmware 1.187.24 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: na ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.24 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Tue Jan 4 19:46:50 2022 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine PackageArchitecture: all ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-43-generic root=PARTUUID=3e5a9664-db4e-4d98-b48a-7cc19a4e843b ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 RfKill: SourcePackage: initramfs-tools Title: package linux-firmware 1.187.24 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2021 dmi.bios.release: 4.1 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.1 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.1 dmi.chassis.asset.tag: 1609-2687-7949-1311-7755-6991-40 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.1 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.1:bd05/05/2021:br4.1:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.1:skuNone:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.1:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.1: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.1 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1956404/+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 1956404] [NEW] package linux-firmware 1.187.24 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
You have been subscribed to a public bug: na ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.24 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Tue Jan 4 19:46:50 2022 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine PackageArchitecture: all ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-43-generic root=PARTUUID=3e5a9664-db4e-4d98-b48a-7cc19a4e843b ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 RfKill: SourcePackage: initramfs-tools Title: package linux-firmware 1.187.24 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2021 dmi.bios.release: 4.1 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.1 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.1 dmi.chassis.asset.tag: 1609-2687-7949-1311-7755-6991-40 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.1 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.1:bd05/05/2021:br4.1:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.1:skuNone:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.1:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.1: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.1 dmi.sys.vendor: Microsoft Corporation ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- package linux-firmware 1.187.24 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 https://bugs.launchpad.net/bugs/1956404 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools 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 1955903] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Summary changed: - Xorg freeze + System freeze ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1955903 Title: System freeze Status in Ubuntu: Incomplete Bug description: Every so often, whether I close the lid of the laptop or not, the screen will go blank and neither pressing a key nor moving the mouse will show anything. The only thing I can do to recover is hold the power button down for 10 seconds to restart. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 28 08:25:44 2021 DistUpgraded: 2020-05-08 07:44:41,528 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2018-03-12 (1387 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9370 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=d9d0f137-4a05-4e95-aac6-c6835b632839 ro locale=en_US alx.enable_wol=1 mem_sleep_default=deep alx.enable_wol=1 mem_sleep_default=deep alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-08 (599 days ago) dmi.bios.date: 10/07/2021 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.0 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.0:bd10/07/2021:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1955903/+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 1924911] Re: Colors look wrong (fake color filter?)
** No longer affects: compiz-mblur-plugin
** No longer affects: libunicode (Ubuntu)
** Project changed: libusb => libusb (Ubuntu)
** Project changed: glxu => mesa (Ubuntu)
** No longer affects: mesa (Ubuntu)
** Package changed: libusb (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libusb in Ubuntu.
https://bugs.launchpad.net/bugs/1924911
Title:
Colors look wrong (fake color filter?)
Status in Ubuntu:
Invalid
Bug description:
It appears something can affect colors in graphical environment.
One workaround is to create following directories:
> $HOME/\motion\ blur
> $HOME/.config\motion\ blur
> $HOME/\ { }
> $HOME/.config\ { }
You should also rename all workspaces like this.
It also helps if you replace any url in address bar with same text
"\motion\ blur".
:)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1924911/+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 1924911] [NEW] Colors look wrong (fake color filter?)
You have been subscribed to a public bug:
It appears something can affect colors in graphical environment.
One workaround is to create following directories:
> $HOME/\motion\ blur
> $HOME/.config\motion\ blur
> $HOME/\ { }
> $HOME/.config\ { }
You should also rename all workspaces like this.
It also helps if you replace any url in address bar with same text
"\motion\ blur".
:)
** Affects: glxu
Importance: Undecided
Status: New
** Affects: libusb (Ubuntu)
Importance: Undecided
Status: New
--
Colors look wrong (fake color filter?)
https://bugs.launchpad.net/bugs/1924911
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to libusb 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 1952735] Re: Add Microphone mute key mapping for Dell machine
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952735 Title: Add Microphone mute key mapping for Dell machine Status in OEM Priority Project: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell machine add new microphone mute key on keyboard, add this key mapping to make it work. [Test Plan] * Use a Dell machine, which has this microphone mute key, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952735/+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 1956388] Re: gtk+3.0: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below
The attachment "build-Don-t-export-GResource-related-symbols-with- newer-G.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1956388 Title: gtk+3.0: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below Status in gtk+3.0 package in Ubuntu: New Status in gtk+3.0 package in Debian: Fix Released Bug description: apt-get source -b libgtk-3-dev Reading package lists... Done Picking 'gtk+3.0' as source package instead of 'libgtk-3-dev' NOTICE: 'gtk+3.0' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/gnome-team/gtk3.git -b ubuntu/focal Please use: git clone https://salsa.debian.org/gnome-team/gtk3.git -b ubuntu/focal to retrieve the latest (possibly unreleased) updates to the package. Need to get 22.9 MB of source archives. Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main gtk+3.0 3.24.20-0ubuntu1 (dsc) [3,639 B] Get:2 http://archive.ubuntu.com/ubuntu focal-updates/main gtk+3.0 3.24.20-0ubuntu1 (tar) [22.7 MB] Get:3 http://archive.ubuntu.com/ubuntu focal-updates/main gtk+3.0 3.24.20-0ubuntu1 (diff) [171 kB] Fetched 22.9 MB in 28s (815 kB/s) dpkg-source: info: extracting gtk+3.0 in gtk+3.0-3.24.20 dpkg-source: info: unpacking gtk+3.0_3.24.20.orig.tar.xz dpkg-source: info: unpacking gtk+3.0_3.24.20-0ubuntu1.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series ... dwz: debian/libgtk-3-0/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2404.16: DWARF compression not beneficial - old size 8243658 new size 8376050 dh_strip -O--buildsystem=autoconf debian/rules override_dh_makeshlibs make[1]: Entering directory '/root/gtk+3.0-3.24.20' sed: couldn't write 35 items to stdout: Broken pipe dh_makeshlibs -plibgtk-3-0 --add-udeb=libgtk-3-0-udeb -Xusr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0 -- -c4 dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libgtk-3-0/DEBIAN/symbols doesn't match completely debian/libgtk-3-0.symbols --- debian/libgtk-3-0.symbols (libgtk-3-0_3.24.20-0ubuntu1_amd64) +++ dpkg-gensymbolsrezAkY 2022-01-04 20:54:52.551202248 + @@ -1,5 +1,8 @@ libgdk-3.so.0 libgtk-3-0 #MINVER# * Build-Depends-Package: libgtk-3-dev + _gdk_get_resource@Base 3.24.20-0ubuntu1 + _gdk_register_resource@Base 3.24.20-0ubuntu1 + _gdk_unregister_resource@Base 3.24.20-0ubuntu1 gdk__private__@Base 3.16.2 gdk_add_option_entries_libgtk_only@Base 3.0.0 gdk_anchor_hints_get_type@Base 3.21.5 @@ -758,6 +761,9 @@ gdk_x11_xatom_to_atom@Base 3.0.0 gdk_x11_xatom_to_atom_for_display@Base 3.0.0 libgtk-3.so.0 libgtk-3-0 #MINVER# + _gtk_get_resource@Base 3.24.20-0ubuntu1 + _gtk_register_resource@Base 3.24.20-0ubuntu1 + _gtk_unregister_resource@Base 3.24.20-0ubuntu1 gtk_about_dialog_add_credit_section@Base 3.3.16 gtk_about_dialog_get_artists@Base 3.0.0 gtk_about_dialog_get_authors@Base 3.0.0 dh_makeshlibs: error: failing due to earlier errors make[1]: *** [debian/rules:243: override_dh_makeshlibs] Error 2 make[1]: Leaving directory '/root/gtk+3.0-3.24.20' make: *** [debian/rules:135: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 W: Download is performed unsandboxed as root as file 'gtk+3.0_3.24.20-0ubuntu1.dsc' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) E: Build command 'cd gtk+3.0-3.24.20 && dpkg-buildpackage -b -uc' failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-dev (not installed) ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 Uname: Linux 5.4.0-92-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Jan 5 00:02:06 2022 InstallationDate: Installed on 2020-04-23 (621 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1956388/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1952421] Re: Issue on sshd finds correct private key for a certificate when using ssh-agent
For SRU verification we require that the actual package from the
-proposed archive is tested. This is to avoid the chance that the patch
is mis-applied in the package uploaded to the archive, or that the
archive build environment differs in a way that affects the patch.
We'll also need this to be verified for Hirsute and Impish before we can
release it for Focal, to ensure that upgrades do not regress this bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1952421
Title:
Issue on sshd finds correct private key for a certificate when using
ssh-agent
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Focal:
Fix Committed
Status in openssh source package in Hirsute:
Fix Committed
Status in openssh source package in Impish:
Fix Committed
Bug description:
Reported as https://bugzilla.mindrot.org/show_bug.cgi?id=3254 upstream
[Impact]
* HostCertificate and HostKeyAgent are not working together in sshd due
to a mismatched certificate's public key and private key. The function `
`sshkey_equal_public()`` incorrectly compares the certificate's public
key with a private key, never finding a match. The impact is that sshd
cannot use said certificate *even though* its private key is indeed in
ssh-agent.
* What it should do is compare the certificate's public key with a
public key in `sensitive_data`.
* Having this SRU-ed is a direct ask from one of the major cloud partners.
They are currently using a customised version of the package to work
around this issue, and we would like them to use a package directly from
our own archive.
* Looping through sensitive_data.host_pubkeys[j] *instead* of
sensitive_data.host_keys[j] fixes the issue
[https://github.com/openssh/openssh-portable/blob/V_8_4/sshd.c#L1936]
/* Find matching private key */
for (j = 0; j < options.num_host_key_files; j++) {
if (sshkey_equal_public(key,
sensitive_data.host_keys[j])) {
sensitive_data.host_certificates[j] = key;
break;
}
}
vs.
/* Find matching private key */
for (j = 0; j < options.num_host_key_files; j++) {
if (sshkey_equal_public(key,
sensitive_data.host_pubkeys[j])) {
sensitive_data.host_certificates[j] = key;
break;
}
}
[Test Plan]
* Due to the empirical nature of this bug, the test is quite straight
forward. *Without* the fix, one cannot use certificates to authenticate
successfully (e.g. ``sshd -c /path/to/certificate.pem``)
whereas with the fix (assuming the certificate matches a host key) you
can create a channel.
[Where problems could occur]
* This has already been fixed both upstream and in Jammy without issue.
However, if a regression where to happen it would probably be in one of
two ways:
* A dependency/reverse-dependency issue stemming from the version
bump that will happen if this fix is ported. We mitigate this risk
by testing for these exact types of regression,
and by selecting carefully what to label this new version.
* Accidentally breaking a set up that was made to work around this
bug in the first place. The risk of this is lower, as the most
likely fix is the one being implemented here anyway. Though
to mitigate this more we can describe exactly what is happening
with the fix in the changelog.
This affects every version of openssh back until Focal, at least.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1952421/+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 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
This bug was fixed in the package apport - 2.20.11-0ubuntu75
---
apport (2.20.11-0ubuntu75) jammy; urgency=medium
* bin/apport-retrace: For releases which gdb doesn't search in the
debug-file-directory for .gnu_debugaltlink create a symlink from the
host's .dwz to the machine specific one to work around the issue.
(LP: #1818918)
-- Brian Murray Mon, 13 Dec 2021 20:17:57 -0800
** Changed in: apport (Ubuntu)
Status: New => Fix Released
--
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/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Fix Released
Status in gdb package in Ubuntu:
Fix Released
Bug description:
As far as I can tell gdb version 8.2.90 isn't searching the debug-
file-directory, which I set, for the '.gnu_debugaltlink' which is in
the debug symbols. Here's the error I'm seeing:
Type "apropos word" to search for commands related to "word".
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
could not find '.gnu_debugaltlink' file for
/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
(No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)
Here's part of an strace of what's going on behind the scenes:
lstat("/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
{st_mode=S_IFREG|0644, st_size=839744, ...}) = 0
openat(AT_FDCWD,
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
This is the only time "/usr/lib/debug" is searched, generally
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox/usr/lib/debug/" is used. I'll attach the full strace though.
For completeness here's the gdb command I'm using:
Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2'
'/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox/usr/bin/gdb' --ex 'set debug-file-directory /srv/vms/apport-
sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set
solib-absolute-prefix /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox' --ex 'add-auto-load-safe-path
/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox' --ex
'set solib-search-path /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/lib/x86_64-linux-gnu' --ex 'set data-
directory /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox/usr/share/gdb' --ex 'file "/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox//usr/bin/gnome-calculator"' --ex 'core-file
/tmp/apport_core_1b6dn6np'
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1818918/+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 1753509] Re: avahi-daemon adds/installs every printer on network
The problem you mention is a known CUPS problem and in the works: https://github.com/OpenPrinting/cups/issues/176 ** Bug watch added: github.com/OpenPrinting/cups/issues #176 https://github.com/OpenPrinting/cups/issues/176 ** Package changed: cups-filters (Ubuntu) => cups (Ubuntu) ** Changed in: cups (Ubuntu) Status: Expired => Triaged ** Changed in: cups (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1753509 Title: avahi-daemon adds/installs every printer on network Status in cups package in Ubuntu: Triaged Bug description: When connected to a network, avahi-daemon adds & installs all printer on a network without being prompted. This is not desired behaviour. Discovery of the printers is good, but not automatic installation & addition. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 5 09:29:05 2018 InstallationDate: Installed on 2017-09-29 (157 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1753509/+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 1753509] [NEW] avahi-daemon adds/installs every printer on network
You have been subscribed to a public bug: When connected to a network, avahi-daemon adds & installs all printer on a network without being prompted. This is not desired behaviour. Discovery of the printers is good, but not automatic installation & addition. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 5 09:29:05 2018 InstallationDate: Installed on 2017-09-29 (157 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cups (Ubuntu) Importance: Undecided Status: Expired ** Tags: amd64 apport-bug xenial -- avahi-daemon adds/installs every printer on network https://bugs.launchpad.net/bugs/1753509 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups 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 1818918] Re: gdb doesn't search in debug-file-directory for .gnu_debugaltlink
** Branch linked: lp:~ubuntu-core-dev/ubuntu/jammy/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/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
New
Status in gdb package in Ubuntu:
Fix Released
Bug description:
As far as I can tell gdb version 8.2.90 isn't searching the debug-
file-directory, which I set, for the '.gnu_debugaltlink' which is in
the debug symbols. Here's the error I'm seeing:
Type "apropos word" to search for commands related to "word".
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox//usr/bin/gnome-calculator...
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug...
could not find '.gnu_debugaltlink' file for
/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug
(No debugging symbols found in /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug)
Here's part of an strace of what's going on behind the scenes:
lstat("/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/usr/lib/debug/.build-id/95/59c4c5ee30eb66d47bb9bd64784a69c9a6de6b.debug",
{st_mode=S_IFREG|0644, st_size=839744, ...}) = 0
openat(AT_FDCWD,
"/usr/lib/debug/.dwz/x86_64-linux-gnu/gnome-calculator.debug",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
This is the only time "/usr/lib/debug" is searched, generally
"/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox/usr/lib/debug/" is used. I'll attach the full strace though.
For completeness here's the gdb command I'm using:
Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2'
'/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox/usr/bin/gdb' --ex 'set debug-file-directory /srv/vms/apport-
sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set
solib-absolute-prefix /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox' --ex 'add-auto-load-safe-path
/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox' --ex
'set solib-search-path /srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox/lib/x86_64-linux-gnu' --ex 'set data-
directory /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox/usr/share/gdb' --ex 'file "/srv/vms/apport-sandbox-dir/Ubuntu
19.04/amd64/report-sandbox//usr/bin/gnome-calculator"' --ex 'core-file
/tmp/apport_core_1b6dn6np'
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1818918/+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 1788060] Re: du program crashes on /var/lib
Adding on to this to say we're experiencing this issue on all Ubuntu 18.04 systems and we're also running xfs for a filesystem. It seems to be related to /var/lib/lxcfs on all of those systems. When we exclude /var/lib/lxcfs from du, it completes without core dumping. root@system:/var# du --exclude 'lib/lxcfs/*' -h -d 1 . 3.1G./log 14M ./backups 3.0G./cache 480K./crash 444M./lib 0 ./local 4.0K./mail 0 ./opt 1.3M./spool 4.0K./tmp 12K ./www 6.5G. root@system:/var# du -h --max-depth=1 . 873M./log 14M ./backups 178M./cache 312K./crash Aborted (core dumped) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1788060 Title: du program crashes on /var/lib Status in coreutils package in Ubuntu: Expired Bug description: We have an Ubuntu 18 installation using xfs file systems user@hostname:~$ df Filesystem 1K-blocks Used Available Use% Mounted on udev 19896400 1989640 0% /dev tmpfs 404008 848403160 1% /run /dev/sda19754624 3083376 6671248 32% / tmpfs20200320 2020032 0% /dev/shm tmpfs 51200 5120 0% /run/lock tmpfs20200320 2020032 0% /sys/fs/cgroup /dev/sda2 11194368 958336 10236032 9% /var tmpfs 4040040404004 0% /run/user/1001 tmpfs 4040040404004 0% /run/user/601005952 du aborts when run in /var and /var/lib, but not in any of the subdirectories of /var/lib I tried rebooting with linux ... init=/bin/bash to run xfs_repair on the /var/file system and it found no errors. After the repair command, I mounted /var and ran du again with no errors. However once I rebooted into the full O/S, du aborted again in /var and /var/lib. The du and sudo du both abort, but non-privileged du also dumps core. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: coreutils 8.28-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Aug 20 15:26:49 2018 InstallationDate: Installed on 2018-06-11 (69 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1788060/+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 1956388] Re: gtk+3.0: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below
** Changed in: gtk+3.0 (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1956388 Title: gtk+3.0: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below Status in gtk+3.0 package in Ubuntu: New Status in gtk+3.0 package in Debian: Fix Released Bug description: apt-get source -b libgtk-3-dev Reading package lists... Done Picking 'gtk+3.0' as source package instead of 'libgtk-3-dev' NOTICE: 'gtk+3.0' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/gnome-team/gtk3.git -b ubuntu/focal Please use: git clone https://salsa.debian.org/gnome-team/gtk3.git -b ubuntu/focal to retrieve the latest (possibly unreleased) updates to the package. Need to get 22.9 MB of source archives. Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main gtk+3.0 3.24.20-0ubuntu1 (dsc) [3,639 B] Get:2 http://archive.ubuntu.com/ubuntu focal-updates/main gtk+3.0 3.24.20-0ubuntu1 (tar) [22.7 MB] Get:3 http://archive.ubuntu.com/ubuntu focal-updates/main gtk+3.0 3.24.20-0ubuntu1 (diff) [171 kB] Fetched 22.9 MB in 28s (815 kB/s) dpkg-source: info: extracting gtk+3.0 in gtk+3.0-3.24.20 dpkg-source: info: unpacking gtk+3.0_3.24.20.orig.tar.xz dpkg-source: info: unpacking gtk+3.0_3.24.20-0ubuntu1.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series ... dwz: debian/libgtk-3-0/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2404.16: DWARF compression not beneficial - old size 8243658 new size 8376050 dh_strip -O--buildsystem=autoconf debian/rules override_dh_makeshlibs make[1]: Entering directory '/root/gtk+3.0-3.24.20' sed: couldn't write 35 items to stdout: Broken pipe dh_makeshlibs -plibgtk-3-0 --add-udeb=libgtk-3-0-udeb -Xusr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0 -- -c4 dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libgtk-3-0/DEBIAN/symbols doesn't match completely debian/libgtk-3-0.symbols --- debian/libgtk-3-0.symbols (libgtk-3-0_3.24.20-0ubuntu1_amd64) +++ dpkg-gensymbolsrezAkY 2022-01-04 20:54:52.551202248 + @@ -1,5 +1,8 @@ libgdk-3.so.0 libgtk-3-0 #MINVER# * Build-Depends-Package: libgtk-3-dev + _gdk_get_resource@Base 3.24.20-0ubuntu1 + _gdk_register_resource@Base 3.24.20-0ubuntu1 + _gdk_unregister_resource@Base 3.24.20-0ubuntu1 gdk__private__@Base 3.16.2 gdk_add_option_entries_libgtk_only@Base 3.0.0 gdk_anchor_hints_get_type@Base 3.21.5 @@ -758,6 +761,9 @@ gdk_x11_xatom_to_atom@Base 3.0.0 gdk_x11_xatom_to_atom_for_display@Base 3.0.0 libgtk-3.so.0 libgtk-3-0 #MINVER# + _gtk_get_resource@Base 3.24.20-0ubuntu1 + _gtk_register_resource@Base 3.24.20-0ubuntu1 + _gtk_unregister_resource@Base 3.24.20-0ubuntu1 gtk_about_dialog_add_credit_section@Base 3.3.16 gtk_about_dialog_get_artists@Base 3.0.0 gtk_about_dialog_get_authors@Base 3.0.0 dh_makeshlibs: error: failing due to earlier errors make[1]: *** [debian/rules:243: override_dh_makeshlibs] Error 2 make[1]: Leaving directory '/root/gtk+3.0-3.24.20' make: *** [debian/rules:135: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 W: Download is performed unsandboxed as root as file 'gtk+3.0_3.24.20-0ubuntu1.dsc' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) E: Build command 'cd gtk+3.0-3.24.20 && dpkg-buildpackage -b -uc' failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-dev (not installed) ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 Uname: Linux 5.4.0-92-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Jan 5 00:02:06 2022 InstallationDate: Installed on 2020-04-23 (621 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1956388/+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 1946667] Re: resolved reports Failed to send hostname reply: Invalid argument
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => 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/1946667 Title: resolved reports Failed to send hostname reply: Invalid argument Status in Canonical SSO provider: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: According to https://github.com/systemd/systemd/issues/11626 this is fixed in version 248 of systemd. Please make that version available to LTS 20.04.3 Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-identity-provider/+bug/1946667/+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 1956388] [NEW] gtk+3.0: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below
Public bug reported: apt-get source -b libgtk-3-dev Reading package lists... Done Picking 'gtk+3.0' as source package instead of 'libgtk-3-dev' NOTICE: 'gtk+3.0' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/gnome-team/gtk3.git -b ubuntu/focal Please use: git clone https://salsa.debian.org/gnome-team/gtk3.git -b ubuntu/focal to retrieve the latest (possibly unreleased) updates to the package. Need to get 22.9 MB of source archives. Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main gtk+3.0 3.24.20-0ubuntu1 (dsc) [3,639 B] Get:2 http://archive.ubuntu.com/ubuntu focal-updates/main gtk+3.0 3.24.20-0ubuntu1 (tar) [22.7 MB] Get:3 http://archive.ubuntu.com/ubuntu focal-updates/main gtk+3.0 3.24.20-0ubuntu1 (diff) [171 kB] Fetched 22.9 MB in 28s (815 kB/s) dpkg-source: info: extracting gtk+3.0 in gtk+3.0-3.24.20 dpkg-source: info: unpacking gtk+3.0_3.24.20.orig.tar.xz dpkg-source: info: unpacking gtk+3.0_3.24.20-0ubuntu1.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series ... dwz: debian/libgtk-3-0/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2404.16: DWARF compression not beneficial - old size 8243658 new size 8376050 dh_strip -O--buildsystem=autoconf debian/rules override_dh_makeshlibs make[1]: Entering directory '/root/gtk+3.0-3.24.20' sed: couldn't write 35 items to stdout: Broken pipe dh_makeshlibs -plibgtk-3-0 --add-udeb=libgtk-3-0-udeb -Xusr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0 -- -c4 dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libgtk-3-0/DEBIAN/symbols doesn't match completely debian/libgtk-3-0.symbols --- debian/libgtk-3-0.symbols (libgtk-3-0_3.24.20-0ubuntu1_amd64) +++ dpkg-gensymbolsrezAkY 2022-01-04 20:54:52.551202248 + @@ -1,5 +1,8 @@ libgdk-3.so.0 libgtk-3-0 #MINVER# * Build-Depends-Package: libgtk-3-dev + _gdk_get_resource@Base 3.24.20-0ubuntu1 + _gdk_register_resource@Base 3.24.20-0ubuntu1 + _gdk_unregister_resource@Base 3.24.20-0ubuntu1 gdk__private__@Base 3.16.2 gdk_add_option_entries_libgtk_only@Base 3.0.0 gdk_anchor_hints_get_type@Base 3.21.5 @@ -758,6 +761,9 @@ gdk_x11_xatom_to_atom@Base 3.0.0 gdk_x11_xatom_to_atom_for_display@Base 3.0.0 libgtk-3.so.0 libgtk-3-0 #MINVER# + _gtk_get_resource@Base 3.24.20-0ubuntu1 + _gtk_register_resource@Base 3.24.20-0ubuntu1 + _gtk_unregister_resource@Base 3.24.20-0ubuntu1 gtk_about_dialog_add_credit_section@Base 3.3.16 gtk_about_dialog_get_artists@Base 3.0.0 gtk_about_dialog_get_authors@Base 3.0.0 dh_makeshlibs: error: failing due to earlier errors make[1]: *** [debian/rules:243: override_dh_makeshlibs] Error 2 make[1]: Leaving directory '/root/gtk+3.0-3.24.20' make: *** [debian/rules:135: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 W: Download is performed unsandboxed as root as file 'gtk+3.0_3.24.20-0ubuntu1.dsc' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) E: Build command 'cd gtk+3.0-3.24.20 && dpkg-buildpackage -b -uc' failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-dev (not installed) ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 Uname: Linux 5.4.0-92-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Jan 5 00:02:06 2022 InstallationDate: Installed on 2020-04-23 (621 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Affects: gtk+3.0 (Debian) Importance: Unknown Status: Unknown ** Tags: amd64 apport-bug focal ** Patch added: "build-Don-t-export-GResource-related-symbols-with-newer-G.patch" https://bugs.launchpad.net/bugs/1956388/+attachment/5551202/+files/build-Don-t-export-GResource-related-symbols-with-newer-G.patch ** Bug watch added: Debian Bug tracker #964679 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964679 ** Also affects: gtk+3.0 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964679 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1956388 Title: gtk+3.0: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below Status in gtk+3.0 package in Ubuntu: New Status in gtk+3.0 package in Debian: Unknown Bug description: apt-get source -b libgtk-3-dev Reading package lists... Done
[Touch-packages] [Bug 1950193] Re: libqt5svg5 affected by CVE-2021-38593
Marc, can you do it please? You can take my changes but use a different version number so that it's rebuilt. Then we will ask the SRU team to remove the versions in -proposed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1950193 Title: libqt5svg5 affected by CVE-2021-38593 Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Focal: Fix Committed Status in qtbase-opensource-src source package in Impish: Fix Committed Bug description: [Impact] libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593: https://nvd.nist.gov/vuln/detail/CVE-2021-38593 Trying to open the attached svg file will block one core at 100% and occupy much memory. Depending on the configuration, it might even run out of memory and crash. This is fixed upstream by: https://codereview.qt-project.org/c/qt/qtbase/+/377942 The original issue is public since July 29th. [Test Plan] 1. Install libqt5svg5-dev, qtbase5-dev and their dependencies. 2. Build the attached project with the system's version of Qt: /usr/lib/qt5/bin/qmake test-2021-38593.pro && make 3. Start the resulting binary and pass the path to the included input file as first parameter: ./test-2021-38593 ./input.svg The binary should return immediately and without error messages. If it doesn't, you might be affected. [Where problems could occur] The fix tries to skip drawing dashes that would be invisible anyway. So a potential problem may that it skips too much. In fact, this has already happened, and upstream had to adjust the fix. [Other Info] The patch is a combination of the following upstream commits: - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1803601] Re: motd-news.service scheduled even when /etc/update-motd.d/50-motd-news is not executable
"Another one is specific to this service, and that is to set ENABLED=0 in /etc/default/motd-news." This file no longer exists by default in Ubuntu 22.04 Jammy. The language in the fix in many places including https://ubuntu.com/legal/motd is to change a number in a file that isn't there. As you know, systemd services that are disabled can still be enabled. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1803601 Title: motd-news.service scheduled even when /etc/update-motd.d/50-motd-news is not executable Status in base-files package in Ubuntu: Triaged Bug description: update-motd(5) says: Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as the root user at each login, and this information is concatenated in /run/motd.dynamic. The order of script execu‐ tion is determined by the run-parts(8) --lsbsysinit option (basically alphabetical order, with a few caveats). So sysadmins are used to "chmod -x" motd fragments from /etc/update- motd.d/ to prevent their execution. When doing so for /etc/update- motd.d/50-motd-news, I noticed that motd-news.timer was still trying to execute the motd-news.service unit which then logged a failure: systemd[3704]: motd-news.service: Failed to execute command: Permission denied systemd[3704]: motd-news.service: Failed at step EXEC spawning /etc/update-motd.d/50-motd-news: Permission denied systemd[1]: motd-news.service: Main process exited, code=exited, status=203/EXEC systemd[1]: motd-news.service: Failed with result 'exit-code'. systemd[1]: Failed to start Message of the Day. The motd-news.service unit looks like this: $ systemctl cat motd-news.service # /lib/systemd/system/motd-news.service [Unit] Description=Message of the Day After=network-online.target Documentation=man:update-motd(8) [Service] Type=oneshot ExecStart=/etc/update-motd.d/50-motd-news --force This problem was observed on a Bionic system: $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy base-files base-files: Installed: 10.1ubuntu2.3 Candidate: 10.1ubuntu2.3 Version table: *** 10.1ubuntu2.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 10.1ubuntu2.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 10.1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages But the problem also exist in Disco. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1803601/+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 1940570] Re: rewrite 50-motd-news to use wget instead of curl
This is already the case. https://changelogs.ubuntu.com/changelogs/pool/main/b/base-files/base-files_10.1ubuntu2.10/changelog FWIW, fwupd and libsane1 require libcurl3-gnutls. libgphoto2-6 requires libcurl4. base-files does not require anything curl related in 22.04 Jammy and probably anything post 20.04. The curl binary through the curl package is not installed by default. ** Changed in: base-files (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1940570 Title: rewrite 50-motd-news to use wget instead of curl Status in base-files package in Ubuntu: Fix Released Bug description: 50-motd-news is shipped in base-files and uses curl but cannot depend on it. curl is not included by default on desktop installs. It'd be better if wget was used instead of curl to get the news from motd.ubuntu.com. This is not trivial to implement, the script uses several advanced options of curl which don't appear to have direct equivalents in wget. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1940570/+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 1956111] Re: Colord's colorhug no longer exists but a URI and library do.
** Summary changed: - colord colorhug no longer exists + Colord's colorhug no longer exists but a URI and library do. ** Description changed: https://github.com/hughsie/colord/commit/master?branch=master The domain listed in the upload URI in the gschema has been taken over by spammers. + + The library libcolorhug2 is still installed by default as a recommended + package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1956111 Title: Colord's colorhug no longer exists but a URI and library do. Status in colord package in Ubuntu: New Bug description: https://github.com/hughsie/colord/commit/master?branch=master The domain listed in the upload URI in the gschema has been taken over by spammers. The library libcolorhug2 is still installed by default as a recommended package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1956111/+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 1650688] Re: timedatectl set-timezone fails on UC16
This bug was fixed in the package systemd - 237-3ubuntu10.53 --- systemd (237-3ubuntu10.53) bionic; urgency=medium [ Ratchanan Srirattanamet ] * d/p/debian/timedatectl-lp1650688.patch, d/p/debian/UBUNTU-Fix-timezone-setting-on-read-only-etc.patch: Fix timedated unable to retrieve & properly set timezone on read-only /etc (e.g. Ubuntu Core and system-image-based systems) (LP: #1650688) [ Lukas Märdian ] * Support detection for ARM64 Hyper-V guests (LP: #1952599) -- Lukas Märdian Fri, 10 Dec 2021 10:15:49 +0100 ** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1650688 Title: timedatectl set-timezone fails on UC16 Status in Snappy: Triaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Hirsute: Won't Fix Status in systemd source package in Impish: Won't Fix Status in systemd source package in Jammy: Fix Released Bug description: SRU === [Impact] * The bug prevents timedated from recognizing and correctly set the system's timezone when running Ubuntu Core 16, 18 and 20. * This causes by timedated fails to take Ubuntu Core's /etc/writable redirection into account. * The recognizing part is fixed by making the code take writable redirection into account. * The set part is fixed by making the code link to the absolute path instead of a relative one. * Currently core snaps worked around the set part by providing a wrapper script which re-create /etc/writable/localtime afterward. However this does not cover DBus users. [Test Plan] * On classics systems: ensure the proposed systemd package is installed. On Ubuntu Core systems: build a new core snap including proposed package, and install it. Replaces timedatectl with timedatectl.real to test skipping the wrapper. (Note that one can simulate core snap's /etc/writable redirection by running this image creation hook [1] on the system.) [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- core/hooks/08-etc-writable.chroot?h=ubuntu/focal * On freshly boot system: query the timezone using `timedatectl`. The timezone should corresponds to `readlink -f /etc/localtime` and does not show `n/a`. * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`. `readlink -f /etc/localtime` should points to an existing file. * Run `sudo systemctl restart systemd-timedated.service`. Then, query the timezone again: `timedatectl`. It should show the previously set timezone and not `n/a`. * Run `sudo systemctl status systemd-timedated.service`. This should show no sign of timedated crashing. [Where problems could occur] * It's possible that the redirection handling code will be sub-par and causes crash. However, it's not likely because the similar pieces of code is in the previous patch since Ubuntu 16.04. * If it does: the patched `get_timezone()` function is used in 2 places: the networkd's DHCP server [3] and the timedated itself. - Networkd is used primarily on servers where NetworkManage is absent. It's possible that this patch causes the user to loss access to the server due to networkd crash when setting up network interfaces, and requires physical access to fix. However, the code path is executed when DHCP is enabled only. I think it's not common for users to have networkd's DHCP server enabled: the feature seems to gear towards desktop users wanting to share internet connection, and in those cases they're more likely to use NetworkManager. - The timedated itself is likely used by the programs that involves in time-related functions. If a crash occur, in the worst case users won't be able to set time or timezone via timedated. However, users should still be able to e.g. set time using `date` or set timezone using /etc/localtime (assuming online guides still consider systems without systemd). Timedated is DBus-activated, and thus a crash should be self-healing. * The set part would also affects the clasic systems. However, I believe nothing else actually rely on /etc/localtime being a relative path, otherwise the /etc/writable redirection would causes even more problem, and would have been reported. [3] Yes, I'm surprised that there's a DHCP server inside systemd codebase. [Other Info] * This is also useful for UBports's Ubuntu Touch. We continue using system-image system where the rootfs is read-only, and thus is affected by this bug similarly to Ubuntu Core. I've tested the Focal version of the package on our (currently in development) Focal Ubuntu Touch image, and the
[Touch-packages] [Bug 1944711] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1944711 Title: restarting systemd-logind loses all existing sessions Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] restarting the systemd-logind service loses all existing sessions [test case] ubuntu@test-f:~$ loginctl list-sessions SESSION UID USER SEAT TTY 3789 1000 ubuntu pts/0 1 sessions listed. ubuntu@test-f:~$ journalctl -b -u systemd-logind -- Logs begin at Thu 2021-09-23 11:11:57 UTC, end at Thu 2021-09-23 11:22:55 UTC. -- Sep 23 11:22:51 test-f systemd[1]: Starting Login Service... Sep 23 11:22:51 test-f systemd-logind[198]: New seat seat0. Sep 23 11:22:51 test-f systemd[1]: Started Login Service. Sep 23 11:22:52 test-f systemd-logind[198]: New session 3789 of user ubuntu. ubuntu@test-f:~$ sudo systemctl restart systemd-logind ubuntu@test-f:~$ journalctl -b -u systemd-logind -- Logs begin at Thu 2021-09-23 11:11:57 UTC, end at Thu 2021-09-23 11:23:07 UTC. -- Sep 23 11:22:51 test-f systemd[1]: Starting Login Service... Sep 23 11:22:51 test-f systemd-logind[198]: New seat seat0. Sep 23 11:22:51 test-f systemd[1]: Started Login Service. Sep 23 11:22:52 test-f systemd-logind[198]: New session 3789 of user ubuntu. Sep 23 11:23:07 test-f systemd[1]: Stopping Login Service... Sep 23 11:23:07 test-f systemd[1]: systemd-logind.service: Succeeded. Sep 23 11:23:07 test-f systemd[1]: Stopped Login Service. Sep 23 11:23:07 test-f systemd[1]: Starting Login Service... Sep 23 11:23:07 test-f systemd-logind[469]: Failed to add user by file name 1000, ignoring: Invalid argument Sep 23 11:23:07 test-f systemd-logind[469]: User enumeration failed: Invalid argument Sep 23 11:23:07 test-f systemd-logind[469]: User of session 3789 not known. Sep 23 11:23:07 test-f systemd-logind[469]: Session enumeration failed: No such file or directory Sep 23 11:23:07 test-f systemd-logind[469]: New seat seat0. Sep 23 11:23:07 test-f systemd[1]: Started Login Service. ubuntu@test-f:~$ loginctl list-sessions No sessions. [regression potential] any regression would likely occur during a systemd-logind restart, likely causing a loss of current login sessions. [scope] this is needed only in f this is fixed upstream by commit ac4e03d45bcf4ad2e570cabdb218e9bac003cc80 which is included in v246, so this is fixed in h and later already. in b, the function used to parse the /run/systemd/users/* files allows either usernames or uids, so this bug does not exist there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1944711/+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 1952599] Re: virt: Support detection for ARM64 Hyper-V guests (fixed upstream)
This bug was fixed in the package systemd - 237-3ubuntu10.53 --- systemd (237-3ubuntu10.53) bionic; urgency=medium [ Ratchanan Srirattanamet ] * d/p/debian/timedatectl-lp1650688.patch, d/p/debian/UBUNTU-Fix-timezone-setting-on-read-only-etc.patch: Fix timedated unable to retrieve & properly set timezone on read-only /etc (e.g. Ubuntu Core and system-image-based systems) (LP: #1650688) [ Lukas Märdian ] * Support detection for ARM64 Hyper-V guests (LP: #1952599) -- Lukas Märdian Fri, 10 Dec 2021 10:15:49 +0100 -- 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/1952599 Title: virt: Support detection for ARM64 Hyper-V guests (fixed upstream) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * The detection of Microsoft Hyper-V VMs is done by cpuid currently, however there is no cpuid on ARM64. And since ARM64 is now a supported architecture for Microsoft Hyper-V guests[0], then introduce a more generic way to detect whether a guest is running as a Hyper-V guest: check if /sys/class/dmi/id/product_version starts with "Hyper-V". * This bug has already been fixed upstream[1][2] [Test Plan] * While changes have been made in the kernel for ARM64 on Hyper-V, there is no way to start an ARM64 VM on Hyper-V at the moment. Thus we just want to make sure no regression is introduced. * start an Hyper-V amd64 VM and make sure "systemd-detect-virt" still return MSFT (should still rely on cpuid here) [Where problems could occur] * The main risk is for the system to detect Hyper-V virt erroneously. An issue was reported upstream after the first commit was merged[3]. For this reason, systemd is now looking for "Hyper-V" (in /sys/class/dmi/id/product_version) and not "Microsoft" (in /sys/class/dmi/id/bios_vendor) * This change might also break virt detection on hyper-v AMD64. That's why we need testing. However, AMD64 virt detection should still rely on cpuid instead of DMI as cpuid takes priority over DMI. [0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7aff79e297ee1aa0126924921fd87a4ae59d2467 [1] https://github.com/systemd/systemd/pull/20998/files [2] https://github.com/systemd/systemd/pull/21475/files [3] https://github.com/systemd/systemd/issues/21468 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952599/+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 1948476] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1948476 Title: [SRU] Allow target units to fail Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [Impact] A systemd regression in focal made it think that target units cannot fail, which produced warnings like: emergency.target: Requested dependency OnFailure=reboot.target ignored (target units cannot fail). So the OnFailure settings are ignored for targets (see https://github.com/snapcore/core-initrd/issues/33 for details). Upstream fixed the issue in v246: https://github.com/systemd/systemd/commit/94d1ddbd7cd15b1073757eb5ae0645c83f0b414c [Test Plan] Test on a UC system and check that the above warnings are not shown anymore. Check that when a target service type fails, the OnFailure setting is used and the mentioned service is run. [Where problems could occur] Issues might happen if some target has an OnFailure setting that was never run in the past because of this bug, and the behavior is not really right because it was never tested. However, OnFailure is not used that much on 20.04 in target services: /lib/systemd $ find . -name \*.target | xargs grep OnFailure /lib/systemd $ /etc/systemd $ find . -name \*.target | xargs grep OnFailure /etc/systemd $ I've seen it only in emergency.target for UC20. [Other Info] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1948476/+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 1650688] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1650688 Title: timedatectl set-timezone fails on UC16 Status in Snappy: Triaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Hirsute: Won't Fix Status in systemd source package in Impish: Won't Fix Status in systemd source package in Jammy: Fix Released Bug description: SRU === [Impact] * The bug prevents timedated from recognizing and correctly set the system's timezone when running Ubuntu Core 16, 18 and 20. * This causes by timedated fails to take Ubuntu Core's /etc/writable redirection into account. * The recognizing part is fixed by making the code take writable redirection into account. * The set part is fixed by making the code link to the absolute path instead of a relative one. * Currently core snaps worked around the set part by providing a wrapper script which re-create /etc/writable/localtime afterward. However this does not cover DBus users. [Test Plan] * On classics systems: ensure the proposed systemd package is installed. On Ubuntu Core systems: build a new core snap including proposed package, and install it. Replaces timedatectl with timedatectl.real to test skipping the wrapper. (Note that one can simulate core snap's /etc/writable redirection by running this image creation hook [1] on the system.) [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- core/hooks/08-etc-writable.chroot?h=ubuntu/focal * On freshly boot system: query the timezone using `timedatectl`. The timezone should corresponds to `readlink -f /etc/localtime` and does not show `n/a`. * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`. `readlink -f /etc/localtime` should points to an existing file. * Run `sudo systemctl restart systemd-timedated.service`. Then, query the timezone again: `timedatectl`. It should show the previously set timezone and not `n/a`. * Run `sudo systemctl status systemd-timedated.service`. This should show no sign of timedated crashing. [Where problems could occur] * It's possible that the redirection handling code will be sub-par and causes crash. However, it's not likely because the similar pieces of code is in the previous patch since Ubuntu 16.04. * If it does: the patched `get_timezone()` function is used in 2 places: the networkd's DHCP server [3] and the timedated itself. - Networkd is used primarily on servers where NetworkManage is absent. It's possible that this patch causes the user to loss access to the server due to networkd crash when setting up network interfaces, and requires physical access to fix. However, the code path is executed when DHCP is enabled only. I think it's not common for users to have networkd's DHCP server enabled: the feature seems to gear towards desktop users wanting to share internet connection, and in those cases they're more likely to use NetworkManager. - The timedated itself is likely used by the programs that involves in time-related functions. If a crash occur, in the worst case users won't be able to set time or timezone via timedated. However, users should still be able to e.g. set time using `date` or set timezone using /etc/localtime (assuming online guides still consider systems without systemd). Timedated is DBus-activated, and thus a crash should be self-healing. * The set part would also affects the clasic systems. However, I believe nothing else actually rely on /etc/localtime being a relative path, otherwise the /etc/writable redirection would causes even more problem, and would have been reported. [3] Yes, I'm surprised that there's a DHCP server inside systemd codebase. [Other Info] * This is also useful for UBports's Ubuntu Touch. We continue using system-image system where the rootfs is read-only, and thus is affected by this bug similarly to Ubuntu Core. I've tested the Focal version of the package on our (currently in development) Focal Ubuntu Touch image, and the fix works. [Original bug description] On a system running UC16, the file /etc/localtime is a link that points to /etc/writable/localtime. On a freshly
[Touch-packages] [Bug 1952599] Re: virt: Support detection for ARM64 Hyper-V guests (fixed upstream)
This bug was fixed in the package systemd - 245.4-4ubuntu3.14 --- systemd (245.4-4ubuntu3.14) focal; urgency=medium [ Lukas Märdian ] * Allow target units to fail (LP: #1948476) File: d/p/lp1948476-pid1-target-units-can-fail-through-dependencies.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=fe0cb0bd66baea89d8bbe47cb47d88540f46d470 * Fix whitespace in lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-.patch to match upstream File: debian/patches/lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=80fef80a1b018556939011707c4ce00cebc58806 * Support detection for ARM64 Hyper-V guests (LP: #1952599) Files: - debian/patches/lp1952599/0001-virt-Support-detection-for-ARM64-Hyper-V-guests.patch - debian/patches/lp1952599/0002-virt-Fix-the-detection-for-Hyper-V-VMs.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=caf3aff933cc7bf21565faba05f78ce78b3196cd [ Andy Chi ] * Add privacy micmute hotkey for Dell machine. (LP: #1952733) File: debian/patches/lp1952733-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-Map.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ff8dc41f55baa418076e42509ddbf3212a8c1353 * Add microphone mute key for Dell machine. (LP: #1952735) File: debian/patches/lp1952735-keymap-Add-microphone-mute-keymap-for-Dell-Machine.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=175fb4e209fba889b4bcd81cb2ed262923943a3f [ Yao Wei ] * Add ACCEL_LOCATION=base property for 6 Dell clamshell models (LP: #1943561) File: debian/patches/lp1943561-dell-clamshell-accel-location-base-with-sku.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=246195d68b2bb0473f4a3f1c2ebe54dfd37f068b [ Dan Streetman ] * d/p/lp1944711-login-filenames-in-run-systemd-users-are-uids.patch: Fix systemd-logind restart loading of existing sessions (LP: #1944711) [ Ratchanan Srirattanamet ] * d/p/debian/timedatectl-lp1650688.patch, d/p/debian/UBUNTU-Fix-timezone-setting-on-read-only-etc.patch: Fix timedated unable to retrieve & properly set timezone on read-only /etc (e.g. Ubuntu Core and system-image-based systems) (LP: #1650688) -- Lukas Märdian Fri, 10 Dec 2021 10:04:02 +0100 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952599 Title: virt: Support detection for ARM64 Hyper-V guests (fixed upstream) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * The detection of Microsoft Hyper-V VMs is done by cpuid currently, however there is no cpuid on ARM64. And since ARM64 is now a supported architecture for Microsoft Hyper-V guests[0], then introduce a more generic way to detect whether a guest is running as a Hyper-V guest: check if /sys/class/dmi/id/product_version starts with "Hyper-V". * This bug has already been fixed upstream[1][2] [Test Plan] * While changes have been made in the kernel for ARM64 on Hyper-V, there is no way to start an ARM64 VM on Hyper-V at the moment. Thus we just want to make sure no regression is introduced. * start an Hyper-V amd64 VM and make sure "systemd-detect-virt" still return MSFT (should still rely on cpuid here) [Where problems could occur] * The main risk is for the system to detect Hyper-V virt erroneously. An issue was reported upstream after the first commit was merged[3]. For this reason, systemd is now looking for "Hyper-V" (in /sys/class/dmi/id/product_version) and not "Microsoft" (in /sys/class/dmi/id/bios_vendor) * This change might also break virt detection on hyper-v AMD64. That's why we need testing. However, AMD64 virt detection should still rely on cpuid instead of DMI as cpuid takes priority over DMI. [0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7aff79e297ee1aa0126924921fd87a4ae59d2467 [1] https://github.com/systemd/systemd/pull/20998/files [2] https://github.com/systemd/systemd/pull/21475/files [3] https://github.com/systemd/systemd/issues/21468 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952599/+subscriptions --
[Touch-packages] [Bug 1952733] Re: Add Dell Privacy Mic Mute Key mapping for another Dell machine
This bug was fixed in the package systemd - 245.4-4ubuntu3.14 --- systemd (245.4-4ubuntu3.14) focal; urgency=medium [ Lukas Märdian ] * Allow target units to fail (LP: #1948476) File: d/p/lp1948476-pid1-target-units-can-fail-through-dependencies.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=fe0cb0bd66baea89d8bbe47cb47d88540f46d470 * Fix whitespace in lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-.patch to match upstream File: debian/patches/lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=80fef80a1b018556939011707c4ce00cebc58806 * Support detection for ARM64 Hyper-V guests (LP: #1952599) Files: - debian/patches/lp1952599/0001-virt-Support-detection-for-ARM64-Hyper-V-guests.patch - debian/patches/lp1952599/0002-virt-Fix-the-detection-for-Hyper-V-VMs.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=caf3aff933cc7bf21565faba05f78ce78b3196cd [ Andy Chi ] * Add privacy micmute hotkey for Dell machine. (LP: #1952733) File: debian/patches/lp1952733-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-Map.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ff8dc41f55baa418076e42509ddbf3212a8c1353 * Add microphone mute key for Dell machine. (LP: #1952735) File: debian/patches/lp1952735-keymap-Add-microphone-mute-keymap-for-Dell-Machine.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=175fb4e209fba889b4bcd81cb2ed262923943a3f [ Yao Wei ] * Add ACCEL_LOCATION=base property for 6 Dell clamshell models (LP: #1943561) File: debian/patches/lp1943561-dell-clamshell-accel-location-base-with-sku.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=246195d68b2bb0473f4a3f1c2ebe54dfd37f068b [ Dan Streetman ] * d/p/lp1944711-login-filenames-in-run-systemd-users-are-uids.patch: Fix systemd-logind restart loading of existing sessions (LP: #1944711) [ Ratchanan Srirattanamet ] * d/p/debian/timedatectl-lp1650688.patch, d/p/debian/UBUNTU-Fix-timezone-setting-on-read-only-etc.patch: Fix timedated unable to retrieve & properly set timezone on read-only /etc (e.g. Ubuntu Core and system-image-based systems) (LP: #1650688) -- Lukas Märdian Fri, 10 Dec 2021 10:04:02 +0100 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952733 Title: Add Dell Privacy Mic Mute Key mapping for another Dell machine Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952733/+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 1948476] Re: [SRU] Allow target units to fail
This bug was fixed in the package systemd - 245.4-4ubuntu3.14 --- systemd (245.4-4ubuntu3.14) focal; urgency=medium [ Lukas Märdian ] * Allow target units to fail (LP: #1948476) File: d/p/lp1948476-pid1-target-units-can-fail-through-dependencies.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=fe0cb0bd66baea89d8bbe47cb47d88540f46d470 * Fix whitespace in lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-.patch to match upstream File: debian/patches/lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=80fef80a1b018556939011707c4ce00cebc58806 * Support detection for ARM64 Hyper-V guests (LP: #1952599) Files: - debian/patches/lp1952599/0001-virt-Support-detection-for-ARM64-Hyper-V-guests.patch - debian/patches/lp1952599/0002-virt-Fix-the-detection-for-Hyper-V-VMs.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=caf3aff933cc7bf21565faba05f78ce78b3196cd [ Andy Chi ] * Add privacy micmute hotkey for Dell machine. (LP: #1952733) File: debian/patches/lp1952733-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-Map.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ff8dc41f55baa418076e42509ddbf3212a8c1353 * Add microphone mute key for Dell machine. (LP: #1952735) File: debian/patches/lp1952735-keymap-Add-microphone-mute-keymap-for-Dell-Machine.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=175fb4e209fba889b4bcd81cb2ed262923943a3f [ Yao Wei ] * Add ACCEL_LOCATION=base property for 6 Dell clamshell models (LP: #1943561) File: debian/patches/lp1943561-dell-clamshell-accel-location-base-with-sku.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=246195d68b2bb0473f4a3f1c2ebe54dfd37f068b [ Dan Streetman ] * d/p/lp1944711-login-filenames-in-run-systemd-users-are-uids.patch: Fix systemd-logind restart loading of existing sessions (LP: #1944711) [ Ratchanan Srirattanamet ] * d/p/debian/timedatectl-lp1650688.patch, d/p/debian/UBUNTU-Fix-timezone-setting-on-read-only-etc.patch: Fix timedated unable to retrieve & properly set timezone on read-only /etc (e.g. Ubuntu Core and system-image-based systems) (LP: #1650688) -- Lukas Märdian Fri, 10 Dec 2021 10:04:02 +0100 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1948476 Title: [SRU] Allow target units to fail Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [Impact] A systemd regression in focal made it think that target units cannot fail, which produced warnings like: emergency.target: Requested dependency OnFailure=reboot.target ignored (target units cannot fail). So the OnFailure settings are ignored for targets (see https://github.com/snapcore/core-initrd/issues/33 for details). Upstream fixed the issue in v246: https://github.com/systemd/systemd/commit/94d1ddbd7cd15b1073757eb5ae0645c83f0b414c [Test Plan] Test on a UC system and check that the above warnings are not shown anymore. Check that when a target service type fails, the OnFailure setting is used and the mentioned service is run. [Where problems could occur] Issues might happen if some target has an OnFailure setting that was never run in the past because of this bug, and the behavior is not really right because it was never tested. However, OnFailure is not used that much on 20.04 in target services: /lib/systemd $ find . -name \*.target | xargs grep OnFailure /lib/systemd $ /etc/systemd $ find . -name \*.target | xargs grep OnFailure /etc/systemd $ I've seen it only in emergency.target for UC20. [Other Info] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1948476/+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 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models
This bug was fixed in the package systemd - 245.4-4ubuntu3.14 --- systemd (245.4-4ubuntu3.14) focal; urgency=medium [ Lukas Märdian ] * Allow target units to fail (LP: #1948476) File: d/p/lp1948476-pid1-target-units-can-fail-through-dependencies.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=fe0cb0bd66baea89d8bbe47cb47d88540f46d470 * Fix whitespace in lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-.patch to match upstream File: debian/patches/lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=80fef80a1b018556939011707c4ce00cebc58806 * Support detection for ARM64 Hyper-V guests (LP: #1952599) Files: - debian/patches/lp1952599/0001-virt-Support-detection-for-ARM64-Hyper-V-guests.patch - debian/patches/lp1952599/0002-virt-Fix-the-detection-for-Hyper-V-VMs.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=caf3aff933cc7bf21565faba05f78ce78b3196cd [ Andy Chi ] * Add privacy micmute hotkey for Dell machine. (LP: #1952733) File: debian/patches/lp1952733-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-Map.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ff8dc41f55baa418076e42509ddbf3212a8c1353 * Add microphone mute key for Dell machine. (LP: #1952735) File: debian/patches/lp1952735-keymap-Add-microphone-mute-keymap-for-Dell-Machine.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=175fb4e209fba889b4bcd81cb2ed262923943a3f [ Yao Wei ] * Add ACCEL_LOCATION=base property for 6 Dell clamshell models (LP: #1943561) File: debian/patches/lp1943561-dell-clamshell-accel-location-base-with-sku.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=246195d68b2bb0473f4a3f1c2ebe54dfd37f068b [ Dan Streetman ] * d/p/lp1944711-login-filenames-in-run-systemd-users-are-uids.patch: Fix systemd-logind restart loading of existing sessions (LP: #1944711) [ Ratchanan Srirattanamet ] * d/p/debian/timedatectl-lp1650688.patch, d/p/debian/UBUNTU-Fix-timezone-setting-on-read-only-etc.patch: Fix timedated unable to retrieve & properly set timezone on read-only /etc (e.g. Ubuntu Core and system-image-based systems) (LP: #1650688) -- Lukas Märdian Fri, 10 Dec 2021 10:04:02 +0100 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models Status in OEM Priority Project: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: This hwdb update is to avoid unwanted screen rotation when tilting the laptop. This is the update to the previously rolled back SRU LP: #1938259 [Impact] * This fixes unwanted rotations on certain Dell clamshell laptop models with accelerometer. [Test Plan] * On Dell laptops with model SKU 0A36, 0A3E, 0B09, 0B0B, 0B0D, 0B11, install this package and ensure the kernel is updated to the latest. * Screen should be correct side up in login screen and desktop. * Tilt the laptop and the screen should not be rotated. [Where problems could occur] * This is to add parameters for certain models in hwdb, and does not affect any other part of systemd. * Only models with the same Dell SKU would be affected. [scope] this is needed for all releases this is being added to upstream by https://github.com/systemd/systemd/pull/20314 and https://github.com/systemd/systemd/pull/20661 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943561/+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 1944711] Re: restarting systemd-logind loses all existing sessions
This bug was fixed in the package systemd - 245.4-4ubuntu3.14 --- systemd (245.4-4ubuntu3.14) focal; urgency=medium [ Lukas Märdian ] * Allow target units to fail (LP: #1948476) File: d/p/lp1948476-pid1-target-units-can-fail-through-dependencies.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=fe0cb0bd66baea89d8bbe47cb47d88540f46d470 * Fix whitespace in lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-.patch to match upstream File: debian/patches/lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=80fef80a1b018556939011707c4ce00cebc58806 * Support detection for ARM64 Hyper-V guests (LP: #1952599) Files: - debian/patches/lp1952599/0001-virt-Support-detection-for-ARM64-Hyper-V-guests.patch - debian/patches/lp1952599/0002-virt-Fix-the-detection-for-Hyper-V-VMs.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=caf3aff933cc7bf21565faba05f78ce78b3196cd [ Andy Chi ] * Add privacy micmute hotkey for Dell machine. (LP: #1952733) File: debian/patches/lp1952733-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-Map.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ff8dc41f55baa418076e42509ddbf3212a8c1353 * Add microphone mute key for Dell machine. (LP: #1952735) File: debian/patches/lp1952735-keymap-Add-microphone-mute-keymap-for-Dell-Machine.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=175fb4e209fba889b4bcd81cb2ed262923943a3f [ Yao Wei ] * Add ACCEL_LOCATION=base property for 6 Dell clamshell models (LP: #1943561) File: debian/patches/lp1943561-dell-clamshell-accel-location-base-with-sku.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=246195d68b2bb0473f4a3f1c2ebe54dfd37f068b [ Dan Streetman ] * d/p/lp1944711-login-filenames-in-run-systemd-users-are-uids.patch: Fix systemd-logind restart loading of existing sessions (LP: #1944711) [ Ratchanan Srirattanamet ] * d/p/debian/timedatectl-lp1650688.patch, d/p/debian/UBUNTU-Fix-timezone-setting-on-read-only-etc.patch: Fix timedated unable to retrieve & properly set timezone on read-only /etc (e.g. Ubuntu Core and system-image-based systems) (LP: #1650688) -- Lukas Märdian Fri, 10 Dec 2021 10:04:02 +0100 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1944711 Title: restarting systemd-logind loses all existing sessions Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] restarting the systemd-logind service loses all existing sessions [test case] ubuntu@test-f:~$ loginctl list-sessions SESSION UID USER SEAT TTY 3789 1000 ubuntu pts/0 1 sessions listed. ubuntu@test-f:~$ journalctl -b -u systemd-logind -- Logs begin at Thu 2021-09-23 11:11:57 UTC, end at Thu 2021-09-23 11:22:55 UTC. -- Sep 23 11:22:51 test-f systemd[1]: Starting Login Service... Sep 23 11:22:51 test-f systemd-logind[198]: New seat seat0. Sep 23 11:22:51 test-f systemd[1]: Started Login Service. Sep 23 11:22:52 test-f systemd-logind[198]: New session 3789 of user ubuntu. ubuntu@test-f:~$ sudo systemctl restart systemd-logind ubuntu@test-f:~$ journalctl -b -u systemd-logind -- Logs begin at Thu 2021-09-23 11:11:57 UTC, end at Thu 2021-09-23 11:23:07 UTC. -- Sep 23 11:22:51 test-f systemd[1]: Starting Login Service... Sep 23 11:22:51 test-f systemd-logind[198]: New seat seat0. Sep 23 11:22:51 test-f systemd[1]: Started Login Service. Sep 23 11:22:52 test-f systemd-logind[198]: New session 3789 of user ubuntu. Sep 23 11:23:07 test-f systemd[1]: Stopping Login Service... Sep 23 11:23:07 test-f systemd[1]: systemd-logind.service: Succeeded. Sep 23 11:23:07 test-f systemd[1]: Stopped Login Service. Sep 23 11:23:07 test-f systemd[1]: Starting Login Service... Sep 23 11:23:07 test-f systemd-logind[469]: Failed to add user by file name 1000, ignoring: Invalid argument Sep 23 11:23:07 test-f systemd-logind[469]: User enumeration failed: Invalid argument Sep 23 11:23:07 test-f systemd-logind[469]: User of session 3789 not known. Sep 23 11:23:07 test-f systemd-logind[469]: Session enumeration failed: No such file or directory Sep 23 11:23:07 test-f systemd-logind[469]: New seat seat0. Sep 23 11:23:07 test-f systemd[1]: Started Login Service. ubuntu@test-f:~$ loginctl list-sessions No sessions. [regression potential] any regression would likely occur during a systemd-logind restart, likely causing a loss of current login
[Touch-packages] [Bug 1650688] Re: timedatectl set-timezone fails on UC16
This bug was fixed in the package systemd - 245.4-4ubuntu3.14 --- systemd (245.4-4ubuntu3.14) focal; urgency=medium [ Lukas Märdian ] * Allow target units to fail (LP: #1948476) File: d/p/lp1948476-pid1-target-units-can-fail-through-dependencies.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=fe0cb0bd66baea89d8bbe47cb47d88540f46d470 * Fix whitespace in lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-.patch to match upstream File: debian/patches/lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=80fef80a1b018556939011707c4ce00cebc58806 * Support detection for ARM64 Hyper-V guests (LP: #1952599) Files: - debian/patches/lp1952599/0001-virt-Support-detection-for-ARM64-Hyper-V-guests.patch - debian/patches/lp1952599/0002-virt-Fix-the-detection-for-Hyper-V-VMs.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=caf3aff933cc7bf21565faba05f78ce78b3196cd [ Andy Chi ] * Add privacy micmute hotkey for Dell machine. (LP: #1952733) File: debian/patches/lp1952733-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-Map.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ff8dc41f55baa418076e42509ddbf3212a8c1353 * Add microphone mute key for Dell machine. (LP: #1952735) File: debian/patches/lp1952735-keymap-Add-microphone-mute-keymap-for-Dell-Machine.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=175fb4e209fba889b4bcd81cb2ed262923943a3f [ Yao Wei ] * Add ACCEL_LOCATION=base property for 6 Dell clamshell models (LP: #1943561) File: debian/patches/lp1943561-dell-clamshell-accel-location-base-with-sku.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=246195d68b2bb0473f4a3f1c2ebe54dfd37f068b [ Dan Streetman ] * d/p/lp1944711-login-filenames-in-run-systemd-users-are-uids.patch: Fix systemd-logind restart loading of existing sessions (LP: #1944711) [ Ratchanan Srirattanamet ] * d/p/debian/timedatectl-lp1650688.patch, d/p/debian/UBUNTU-Fix-timezone-setting-on-read-only-etc.patch: Fix timedated unable to retrieve & properly set timezone on read-only /etc (e.g. Ubuntu Core and system-image-based systems) (LP: #1650688) -- Lukas Märdian Fri, 10 Dec 2021 10:04:02 +0100 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1650688 Title: timedatectl set-timezone fails on UC16 Status in Snappy: Triaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Hirsute: Won't Fix Status in systemd source package in Impish: Won't Fix Status in systemd source package in Jammy: Fix Released Bug description: SRU === [Impact] * The bug prevents timedated from recognizing and correctly set the system's timezone when running Ubuntu Core 16, 18 and 20. * This causes by timedated fails to take Ubuntu Core's /etc/writable redirection into account. * The recognizing part is fixed by making the code take writable redirection into account. * The set part is fixed by making the code link to the absolute path instead of a relative one. * Currently core snaps worked around the set part by providing a wrapper script which re-create /etc/writable/localtime afterward. However this does not cover DBus users. [Test Plan] * On classics systems: ensure the proposed systemd package is installed. On Ubuntu Core systems: build a new core snap including proposed package, and install it. Replaces timedatectl with timedatectl.real to test skipping the wrapper. (Note that one can simulate core snap's /etc/writable redirection by running this image creation hook [1] on the system.) [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- core/hooks/08-etc-writable.chroot?h=ubuntu/focal * On freshly boot system: query the timezone using `timedatectl`. The timezone should corresponds to `readlink -f /etc/localtime` and does not show `n/a`. * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`. `readlink -f /etc/localtime` should points to an existing file. * Run `sudo systemctl restart systemd-timedated.service`. Then, query the timezone again: `timedatectl`. It should show the previously set timezone and not `n/a`. * Run `sudo systemctl status systemd-timedated.service`. This should show no sign of timedated crashing. [Where problems could occur] * It's possible that the redirection
[Touch-packages] [Bug 1952735] Re: Add Microphone mute key mapping for Dell machine
This bug was fixed in the package systemd - 245.4-4ubuntu3.14 --- systemd (245.4-4ubuntu3.14) focal; urgency=medium [ Lukas Märdian ] * Allow target units to fail (LP: #1948476) File: d/p/lp1948476-pid1-target-units-can-fail-through-dependencies.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=fe0cb0bd66baea89d8bbe47cb47d88540f46d470 * Fix whitespace in lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-.patch to match upstream File: debian/patches/lp1926547-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=80fef80a1b018556939011707c4ce00cebc58806 * Support detection for ARM64 Hyper-V guests (LP: #1952599) Files: - debian/patches/lp1952599/0001-virt-Support-detection-for-ARM64-Hyper-V-guests.patch - debian/patches/lp1952599/0002-virt-Fix-the-detection-for-Hyper-V-VMs.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=caf3aff933cc7bf21565faba05f78ce78b3196cd [ Andy Chi ] * Add privacy micmute hotkey for Dell machine. (LP: #1952733) File: debian/patches/lp1952733-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-Map.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ff8dc41f55baa418076e42509ddbf3212a8c1353 * Add microphone mute key for Dell machine. (LP: #1952735) File: debian/patches/lp1952735-keymap-Add-microphone-mute-keymap-for-Dell-Machine.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=175fb4e209fba889b4bcd81cb2ed262923943a3f [ Yao Wei ] * Add ACCEL_LOCATION=base property for 6 Dell clamshell models (LP: #1943561) File: debian/patches/lp1943561-dell-clamshell-accel-location-base-with-sku.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=246195d68b2bb0473f4a3f1c2ebe54dfd37f068b [ Dan Streetman ] * d/p/lp1944711-login-filenames-in-run-systemd-users-are-uids.patch: Fix systemd-logind restart loading of existing sessions (LP: #1944711) [ Ratchanan Srirattanamet ] * d/p/debian/timedatectl-lp1650688.patch, d/p/debian/UBUNTU-Fix-timezone-setting-on-read-only-etc.patch: Fix timedated unable to retrieve & properly set timezone on read-only /etc (e.g. Ubuntu Core and system-image-based systems) (LP: #1650688) -- Lukas Märdian Fri, 10 Dec 2021 10:04:02 +0100 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952735 Title: Add Microphone mute key mapping for Dell machine Status in OEM Priority Project: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell machine add new microphone mute key on keyboard, add this key mapping to make it work. [Test Plan] * Use a Dell machine, which has this microphone mute key, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952735/+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 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models
This bug was fixed in the package systemd - 248.3-1ubuntu8.1 --- systemd (248.3-1ubuntu8.1) impish; urgency=medium [ Lukas Märdian ] * Cherry-pick upstream 5ed0ea: hwdb: 60-keyboard:: Update Dell Privacy Local Mic Mute Hotkey (LP: #1926547) File: debian/patches/hwdb-60-keyboard-Update-Dell-Privacy-Local-Mic-Mute-Hotke.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=041be812ac5c204ad09830dc796ebdb0d6d0894a * Support detection for ARM64 Hyper-V guests (LP: #1952599) Files: - debian/patches/lp1952599/0001-virt-Support-detection-for-ARM64-Hyper-V-guests.patch - debian/patches/lp1952599/0002-virt-Fix-the-detection-for-Hyper-V-VMs.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5060ac86698b206459cef42daa84499781147378 [ Andy Chi ] * Add privacy micmute hotkey for Dell machine. (LP: #1952733) File: debian/patches/lp1952733-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-Map.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f74b782d3ceb01d76c7bffdce7502763dd540150 * Add microphone mute key for Dell machine. (LP: #1952735) File: debian/patches/lp1952735-keymap-Add-microphone-mute-keymap-for-Dell-Machine.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=03c117092c1a32b5db025613d328add54bef3718 [ Yao Wei ] * Add ACCEL_LOCATION=base property for Dell clamshell models (LP: #1943561) Files: - debian/patches/lp1943561/Add-additional-Dell-models-that-require-ACCEL_LOCATION-ba.patch - debian/patches/lp1943561/Use-SKU-to-identify-Dell-clamshell-models-for-acceleromet.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b6b30ad3d9ef862d30f397ba481fe4f647751c99 -- Lukas Märdian Fri, 10 Dec 2021 09:56:36 +0100 ** Changed in: systemd (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models Status in OEM Priority Project: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: This hwdb update is to avoid unwanted screen rotation when tilting the laptop. This is the update to the previously rolled back SRU LP: #1938259 [Impact] * This fixes unwanted rotations on certain Dell clamshell laptop models with accelerometer. [Test Plan] * On Dell laptops with model SKU 0A36, 0A3E, 0B09, 0B0B, 0B0D, 0B11, install this package and ensure the kernel is updated to the latest. * Screen should be correct side up in login screen and desktop. * Tilt the laptop and the screen should not be rotated. [Where problems could occur] * This is to add parameters for certain models in hwdb, and does not affect any other part of systemd. * Only models with the same Dell SKU would be affected. [scope] this is needed for all releases this is being added to upstream by https://github.com/systemd/systemd/pull/20314 and https://github.com/systemd/systemd/pull/20661 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943561/+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 1943561] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models Status in OEM Priority Project: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: This hwdb update is to avoid unwanted screen rotation when tilting the laptop. This is the update to the previously rolled back SRU LP: #1938259 [Impact] * This fixes unwanted rotations on certain Dell clamshell laptop models with accelerometer. [Test Plan] * On Dell laptops with model SKU 0A36, 0A3E, 0B09, 0B0B, 0B0D, 0B11, install this package and ensure the kernel is updated to the latest. * Screen should be correct side up in login screen and desktop. * Tilt the laptop and the screen should not be rotated. [Where problems could occur] * This is to add parameters for certain models in hwdb, and does not affect any other part of systemd. * Only models with the same Dell SKU would be affected. [scope] this is needed for all releases this is being added to upstream by https://github.com/systemd/systemd/pull/20314 and https://github.com/systemd/systemd/pull/20661 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943561/+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 1926547] Re: Add Dell Privacy Mic Mute Key mapping
This bug was fixed in the package systemd - 248.3-1ubuntu8.1 --- systemd (248.3-1ubuntu8.1) impish; urgency=medium [ Lukas Märdian ] * Cherry-pick upstream 5ed0ea: hwdb: 60-keyboard:: Update Dell Privacy Local Mic Mute Hotkey (LP: #1926547) File: debian/patches/hwdb-60-keyboard-Update-Dell-Privacy-Local-Mic-Mute-Hotke.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=041be812ac5c204ad09830dc796ebdb0d6d0894a * Support detection for ARM64 Hyper-V guests (LP: #1952599) Files: - debian/patches/lp1952599/0001-virt-Support-detection-for-ARM64-Hyper-V-guests.patch - debian/patches/lp1952599/0002-virt-Fix-the-detection-for-Hyper-V-VMs.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5060ac86698b206459cef42daa84499781147378 [ Andy Chi ] * Add privacy micmute hotkey for Dell machine. (LP: #1952733) File: debian/patches/lp1952733-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-Map.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f74b782d3ceb01d76c7bffdce7502763dd540150 * Add microphone mute key for Dell machine. (LP: #1952735) File: debian/patches/lp1952735-keymap-Add-microphone-mute-keymap-for-Dell-Machine.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=03c117092c1a32b5db025613d328add54bef3718 [ Yao Wei ] * Add ACCEL_LOCATION=base property for Dell clamshell models (LP: #1943561) Files: - debian/patches/lp1943561/Add-additional-Dell-models-that-require-ACCEL_LOCATION-ba.patch - debian/patches/lp1943561/Use-SKU-to-identify-Dell-clamshell-models-for-acceleromet.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b6b30ad3d9ef862d30f397ba481fe4f647751c99 -- Lukas Märdian Fri, 10 Dec 2021 09:56:36 +0100 ** Changed in: systemd (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1926547 Title: Add Dell Privacy Mic Mute Key mapping Status in OEM Priority Project: Fix Released Status in OEM Priority Project focal series: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd source package in Impish: Fix Released Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * The change can only work with kernel commit on some specific hardware, ex. Latitude 9520. The commit series is "hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree. https://patchwork.kernel.org/project/alsa-devel/list/?series=465445 * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1926547/+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 1952599] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1952599 Title: virt: Support detection for ARM64 Hyper-V guests (fixed upstream) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * The detection of Microsoft Hyper-V VMs is done by cpuid currently, however there is no cpuid on ARM64. And since ARM64 is now a supported architecture for Microsoft Hyper-V guests[0], then introduce a more generic way to detect whether a guest is running as a Hyper-V guest: check if /sys/class/dmi/id/product_version starts with "Hyper-V". * This bug has already been fixed upstream[1][2] [Test Plan] * While changes have been made in the kernel for ARM64 on Hyper-V, there is no way to start an ARM64 VM on Hyper-V at the moment. Thus we just want to make sure no regression is introduced. * start an Hyper-V amd64 VM and make sure "systemd-detect-virt" still return MSFT (should still rely on cpuid here) [Where problems could occur] * The main risk is for the system to detect Hyper-V virt erroneously. An issue was reported upstream after the first commit was merged[3]. For this reason, systemd is now looking for "Hyper-V" (in /sys/class/dmi/id/product_version) and not "Microsoft" (in /sys/class/dmi/id/bios_vendor) * This change might also break virt detection on hyper-v AMD64. That's why we need testing. However, AMD64 virt detection should still rely on cpuid instead of DMI as cpuid takes priority over DMI. [0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7aff79e297ee1aa0126924921fd87a4ae59d2467 [1] https://github.com/systemd/systemd/pull/20998/files [2] https://github.com/systemd/systemd/pull/21475/files [3] https://github.com/systemd/systemd/issues/21468 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952599/+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 1952733] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1952733 Title: Add Dell Privacy Mic Mute Key mapping for another Dell machine Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952733/+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 1952599] Re: virt: Support detection for ARM64 Hyper-V guests (fixed upstream)
This bug was fixed in the package systemd - 248.3-1ubuntu8.1 --- systemd (248.3-1ubuntu8.1) impish; urgency=medium [ Lukas Märdian ] * Cherry-pick upstream 5ed0ea: hwdb: 60-keyboard:: Update Dell Privacy Local Mic Mute Hotkey (LP: #1926547) File: debian/patches/hwdb-60-keyboard-Update-Dell-Privacy-Local-Mic-Mute-Hotke.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=041be812ac5c204ad09830dc796ebdb0d6d0894a * Support detection for ARM64 Hyper-V guests (LP: #1952599) Files: - debian/patches/lp1952599/0001-virt-Support-detection-for-ARM64-Hyper-V-guests.patch - debian/patches/lp1952599/0002-virt-Fix-the-detection-for-Hyper-V-VMs.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5060ac86698b206459cef42daa84499781147378 [ Andy Chi ] * Add privacy micmute hotkey for Dell machine. (LP: #1952733) File: debian/patches/lp1952733-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-Map.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f74b782d3ceb01d76c7bffdce7502763dd540150 * Add microphone mute key for Dell machine. (LP: #1952735) File: debian/patches/lp1952735-keymap-Add-microphone-mute-keymap-for-Dell-Machine.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=03c117092c1a32b5db025613d328add54bef3718 [ Yao Wei ] * Add ACCEL_LOCATION=base property for Dell clamshell models (LP: #1943561) Files: - debian/patches/lp1943561/Add-additional-Dell-models-that-require-ACCEL_LOCATION-ba.patch - debian/patches/lp1943561/Use-SKU-to-identify-Dell-clamshell-models-for-acceleromet.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b6b30ad3d9ef862d30f397ba481fe4f647751c99 -- Lukas Märdian Fri, 10 Dec 2021 09:56:36 +0100 ** Changed in: systemd (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952599 Title: virt: Support detection for ARM64 Hyper-V guests (fixed upstream) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * The detection of Microsoft Hyper-V VMs is done by cpuid currently, however there is no cpuid on ARM64. And since ARM64 is now a supported architecture for Microsoft Hyper-V guests[0], then introduce a more generic way to detect whether a guest is running as a Hyper-V guest: check if /sys/class/dmi/id/product_version starts with "Hyper-V". * This bug has already been fixed upstream[1][2] [Test Plan] * While changes have been made in the kernel for ARM64 on Hyper-V, there is no way to start an ARM64 VM on Hyper-V at the moment. Thus we just want to make sure no regression is introduced. * start an Hyper-V amd64 VM and make sure "systemd-detect-virt" still return MSFT (should still rely on cpuid here) [Where problems could occur] * The main risk is for the system to detect Hyper-V virt erroneously. An issue was reported upstream after the first commit was merged[3]. For this reason, systemd is now looking for "Hyper-V" (in /sys/class/dmi/id/product_version) and not "Microsoft" (in /sys/class/dmi/id/bios_vendor) * This change might also break virt detection on hyper-v AMD64. That's why we need testing. However, AMD64 virt detection should still rely on cpuid instead of DMI as cpuid takes priority over DMI. [0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7aff79e297ee1aa0126924921fd87a4ae59d2467 [1] https://github.com/systemd/systemd/pull/20998/files [2] https://github.com/systemd/systemd/pull/21475/files [3] https://github.com/systemd/systemd/issues/21468 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952599/+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 1952733] Re: Add Dell Privacy Mic Mute Key mapping for another Dell machine
This bug was fixed in the package systemd - 248.3-1ubuntu8.1 --- systemd (248.3-1ubuntu8.1) impish; urgency=medium [ Lukas Märdian ] * Cherry-pick upstream 5ed0ea: hwdb: 60-keyboard:: Update Dell Privacy Local Mic Mute Hotkey (LP: #1926547) File: debian/patches/hwdb-60-keyboard-Update-Dell-Privacy-Local-Mic-Mute-Hotke.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=041be812ac5c204ad09830dc796ebdb0d6d0894a * Support detection for ARM64 Hyper-V guests (LP: #1952599) Files: - debian/patches/lp1952599/0001-virt-Support-detection-for-ARM64-Hyper-V-guests.patch - debian/patches/lp1952599/0002-virt-Fix-the-detection-for-Hyper-V-VMs.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5060ac86698b206459cef42daa84499781147378 [ Andy Chi ] * Add privacy micmute hotkey for Dell machine. (LP: #1952733) File: debian/patches/lp1952733-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-Map.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f74b782d3ceb01d76c7bffdce7502763dd540150 * Add microphone mute key for Dell machine. (LP: #1952735) File: debian/patches/lp1952735-keymap-Add-microphone-mute-keymap-for-Dell-Machine.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=03c117092c1a32b5db025613d328add54bef3718 [ Yao Wei ] * Add ACCEL_LOCATION=base property for Dell clamshell models (LP: #1943561) Files: - debian/patches/lp1943561/Add-additional-Dell-models-that-require-ACCEL_LOCATION-ba.patch - debian/patches/lp1943561/Use-SKU-to-identify-Dell-clamshell-models-for-acceleromet.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b6b30ad3d9ef862d30f397ba481fe4f647751c99 -- Lukas Märdian Fri, 10 Dec 2021 09:56:36 +0100 ** Changed in: systemd (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952733 Title: Add Dell Privacy Mic Mute Key mapping for another Dell machine Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952733/+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 1952735] Re: Add Microphone mute key mapping for Dell machine
This bug was fixed in the package systemd - 248.3-1ubuntu8.1 --- systemd (248.3-1ubuntu8.1) impish; urgency=medium [ Lukas Märdian ] * Cherry-pick upstream 5ed0ea: hwdb: 60-keyboard:: Update Dell Privacy Local Mic Mute Hotkey (LP: #1926547) File: debian/patches/hwdb-60-keyboard-Update-Dell-Privacy-Local-Mic-Mute-Hotke.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=041be812ac5c204ad09830dc796ebdb0d6d0894a * Support detection for ARM64 Hyper-V guests (LP: #1952599) Files: - debian/patches/lp1952599/0001-virt-Support-detection-for-ARM64-Hyper-V-guests.patch - debian/patches/lp1952599/0002-virt-Fix-the-detection-for-Hyper-V-VMs.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5060ac86698b206459cef42daa84499781147378 [ Andy Chi ] * Add privacy micmute hotkey for Dell machine. (LP: #1952733) File: debian/patches/lp1952733-hwdb-60-keyboard-Update-Dell-Privacy-Micmute-Hotkey-Map.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f74b782d3ceb01d76c7bffdce7502763dd540150 * Add microphone mute key for Dell machine. (LP: #1952735) File: debian/patches/lp1952735-keymap-Add-microphone-mute-keymap-for-Dell-Machine.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=03c117092c1a32b5db025613d328add54bef3718 [ Yao Wei ] * Add ACCEL_LOCATION=base property for Dell clamshell models (LP: #1943561) Files: - debian/patches/lp1943561/Add-additional-Dell-models-that-require-ACCEL_LOCATION-ba.patch - debian/patches/lp1943561/Use-SKU-to-identify-Dell-clamshell-models-for-acceleromet.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b6b30ad3d9ef862d30f397ba481fe4f647751c99 -- Lukas Märdian Fri, 10 Dec 2021 09:56:36 +0100 ** Changed in: systemd (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952735 Title: Add Microphone mute key mapping for Dell machine Status in OEM Priority Project: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell machine add new microphone mute key on keyboard, add this key mapping to make it work. [Test Plan] * Use a Dell machine, which has this microphone mute key, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952735/+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 1952735] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1952735 Title: Add Microphone mute key mapping for Dell machine Status in OEM Priority Project: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell machine add new microphone mute key on keyboard, add this key mapping to make it work. [Test Plan] * Use a Dell machine, which has this microphone mute key, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952735/+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 1950496] Re: networkd doesn't provide DNS to nspawn containers
Also for future reference I think upstream commit fb3aec45a0de7f71aa6418bd4f9d5f314efb4eb5 fixes this, but I never got a chance to test it before upgrading. ** Changed in: systemd (Ubuntu Focal) Status: New => Incomplete ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1950496 Title: networkd doesn't provide DNS to nspawn containers Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Incomplete Bug description: [impact] the host networkd doesn't include DNS info to nspawn containers [test case] create/start a nspawn container, e.g. with 'machinectl start', open a shell in the container, and check resolvectl to see if a nameserver was provided. [regression potential] failures in the host networkd, possibly affecting other host interfaces which are controlled by networkd, or (more likely) failure to provide dhcp to nspawn containers [scope] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950496/+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 1950496] Re: networkd doesn't provide DNS to nspawn containers
I was able to reproduce this when my bare metal system was running focal, but I since have upgraded to impish and now i can't reproduce this problem in a focal VM, so probably there is some specific network setup required to reproduce (that I have on my bare metal system but not in a VM); since it's no longer a problem for me as I've upgraded to impish, I'm dropping ownership of this, but if anyone else has this problem (i.e. can reproduce it) please reopen the bug and/or add a comment. ** Changed in: systemd (Ubuntu Focal) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Changed in: systemd (Ubuntu Focal) Importance: Medium => Low ** Changed in: systemd (Ubuntu Focal) Status: In Progress => 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/1950496 Title: networkd doesn't provide DNS to nspawn containers Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Incomplete Bug description: [impact] the host networkd doesn't include DNS info to nspawn containers [test case] create/start a nspawn container, e.g. with 'machinectl start', open a shell in the container, and check resolvectl to see if a nameserver was provided. [regression potential] failures in the host networkd, possibly affecting other host interfaces which are controlled by networkd, or (more likely) failure to provide dhcp to nspawn containers [scope] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950496/+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 1956115] Re: ubuntu-advantage-tools ' MOTD is incompatible with Ubuntu Legal's MOTD opt-out directions.
/etc/default/motd-news as outlined in the link "/etc/default/motd-news has an ENABLED=1 setting that if set to 0 will turn off this functionality." The file no longer exists by default. This would be required to change the ENABLED variable from 1 to 0. /etc/update-motd.d/50-motd-news notes the same thing in the code comments. The directions or pulled location are wrong. The reason this matters is because the package only exists to be wrong because ubuntu-advantage-tools requires MOTD which itself it does not control, both of which are not removable as they are dependencies of ubuntu-desktop-minimal. Subsequently there are forced hooks for MOTD and Apt for something most desktop users aren't using with the inability to opt out in the way it is listed. The file you are referencing is not the file at the Ubuntu legal website or the /etc/update-motd.d/50-motd-news code comments. Since introduction, these files went from roughly 60-260KB in total to 3+MB. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1956115 Title: ubuntu-advantage-tools ' MOTD is incompatible with Ubuntu Legal's MOTD opt-out directions. Status in base-files package in Ubuntu: Incomplete Status in ubuntu-advantage-tools package in Ubuntu: Incomplete Bug description: https://ubuntu.com/legal/motd This file does not exist in Jammy 22.04. This wouldn't be a problem if it was actually removable without having to build custom metapackages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1956115/+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 1956029] Re: ufw remains inactive at boot time
Thanks for the response and glad you got it worked out. It reminds me that I would like to document using fail2ban with ufw more. ** Changed in: ufw (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1956029 Title: ufw remains inactive at boot time Status in ufw package in Ubuntu: Invalid Bug description: I was advised to start a bug report (Comment 38): https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856 I "ufw enable" then several seconds later networking stops. I have get Ubuntu to gracefully power-down using the power-button and then gracefully power-up. Out of curiosity, is anyone here having this problem wish ufw starting up at boot time while also using having fail2ban installed? Here is my theory. It takes a while for fail2ban to issue all the iptable commands to configure the firewall. When ufw tries to initialise there may be a clash or lock held either by an iptables instance spawned by fail2ban or an iptables instance spawned by ufw. One of them will fail and will quite probably mess-up ufw's rules breaking network connectivity. This time I waited for fail2ban to finish establishing its iptables rules before issuing "ufw enable" and this time round network connectivity was not lost. How to I ensure that ufw is fully up and initialised BEFORE the fail2ban service starts? - root@loki:~# ./ufw-diag.sh Has python: pass (binary: python3, version: 3.8.10, py3) Has iptables: pass Has ip6tables: pass Has /proc/net/dev: pass Has /proc/net/if_inet6: pass This script will now attempt to create various rules using the iptables and ip6tables commands. This may result in module autoloading (eg, for IPv6). Proceed with checks (Y/n)? == IPv4 == Creating 'ufw-check-requirements'... done Inserting RETURN at top of 'ufw-check-requirements'... done TCP: pass UDP: pass destination port: pass source port: pass ACCEPT: pass DROP: pass REJECT: pass LOG: pass hashlimit: pass limit: pass ctstate (NEW): pass ctstate (RELATED): pass ctstate (ESTABLISHED): pass ctstate (INVALID): pass ctstate (new, recent set): pass ctstate (new, recent update): pass ctstate (new, limit): pass interface (input): pass interface (output): pass multiport: pass comment: pass addrtype (LOCAL): pass addrtype (MULTICAST): pass addrtype (BROADCAST): pass icmp (destination-unreachable): pass icmp (source-quench): pass icmp (time-exceeded): pass icmp (parameter-problem): pass icmp (echo-request): pass == IPv6 == Creating 'ufw-check-requirements6'... done Inserting RETURN at top of 'ufw-check-requirements6'... done TCP: pass UDP: pass destination port: pass source port: pass ACCEPT: pass DROP: pass REJECT: pass LOG: pass hashlimit: pass limit: pass ctstate (NEW): pass ctstate (RELATED): pass ctstate (ESTABLISHED): pass ctstate (INVALID): pass ctstate (new, recent set): pass ctstate (new, recent update): pass ctstate (new, limit): pass interface (input): pass interface (output): pass multiport: pass comment: pass icmpv6 (destination-unreachable): pass icmpv6 (packet-too-big): pass icmpv6 (time-exceeded): pass icmpv6 (parameter-problem): pass icmpv6 (echo-request): pass icmpv6 with hl (neighbor-solicitation): pass icmpv6 with hl (neighbor-advertisement): pass icmpv6 with hl (router-solicitation): pass icmpv6 with hl (router-advertisement): pass ipv6 rt: pass All tests passed - root@loki:/lib/systemd/system# cat ufw.service [Unit] Description=Uncomplicated firewall Documentation=man:ufw(8) DefaultDependencies=no Before=network.target After=NetworkManager.service [Service] Type=oneshot RemainAfterExit=yes ExecStart=/lib/ufw/ufw-init start quiet # ExecStartPost=/bin/sleep 10 ExecStop=/lib/ufw/ufw-init stop [Install] WantedBy=multi-user.target - root@loki:/lib/systemd/system# cat fail2ban.service [Unit] Description=Fail2Ban Service Documentation=man:fail2ban(1) After=network.target iptables.service firewalld.service ip6tables.service ipset.service nftables.service ufw.service PartOf=firewalld.service [Service] Type=simple ExecStartPre=/bin/mkdir -p /run/fail2ban ExecStart=/usr/bin/fail2ban-server -xf start # if should be logged in systemd journal, use following line or set logtarget to sysout in fail2ban.local # ExecStart=/usr/bin/fail2ban-server -xf --logtarget=sysout start ExecStop=/usr/bin/fail2ban-client stop ExecReload=/usr/bin/fail2ban-client reload PIDFile=/run/fail2ban/fail2ban.pid Restart=on-failure RestartPreventExitStatus=0 255 [Install] WantedBy=multi-user.target - root@loki:/etc/default# cat ufw # /etc/default/ufw # # Set to yes to apply rules to support IPv6 (no
[Touch-packages] [Bug 1950193] Re: libqt5svg5 affected by CVE-2021-38593
This update needs to go in the -security pocket since it is a security fix, but it likely can't just be copied, it would need to be rebuilt. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1950193 Title: libqt5svg5 affected by CVE-2021-38593 Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Focal: Fix Committed Status in qtbase-opensource-src source package in Impish: Fix Committed Bug description: [Impact] libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593: https://nvd.nist.gov/vuln/detail/CVE-2021-38593 Trying to open the attached svg file will block one core at 100% and occupy much memory. Depending on the configuration, it might even run out of memory and crash. This is fixed upstream by: https://codereview.qt-project.org/c/qt/qtbase/+/377942 The original issue is public since July 29th. [Test Plan] 1. Install libqt5svg5-dev, qtbase5-dev and their dependencies. 2. Build the attached project with the system's version of Qt: /usr/lib/qt5/bin/qmake test-2021-38593.pro && make 3. Start the resulting binary and pass the path to the included input file as first parameter: ./test-2021-38593 ./input.svg The binary should return immediately and without error messages. If it doesn't, you might be affected. [Where problems could occur] The fix tries to skip drawing dashes that would be invisible anyway. So a potential problem may that it skips too much. In fact, this has already happened, and upstream had to adjust the fix. [Other Info] The patch is a combination of the following upstream commits: - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=7f345f2a1c8d9f60 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=9378ba2ae857df7e - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=81998f50d039a631 - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=cca8ed0547405b1c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+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 1956369] [NEW] The headphones work without problems, as does the microphone but there is no sound on the speakers
Public bug reported: I have a problem with my Asus GX701LWS, the headphones work without problems, as does the microphone but there is no sound on the speakers. hwinfo --sound 22: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.Qb7ky1jjQRD SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x06c8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1f01 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x9830-0x98303fff (rw,non-prefetchable) Memory Range: 0x9810-0x981f (rw,non-prefetchable) IRQ: 171 (910 events) Module Alias: "pci:v8086d06C8sv1043sd1F01bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_sof_pci_intel_cnl is active Driver Activation Cmd: "modprobe snd_sof_pci_intel_cnl" Config Status: cfg=new, avail=yes, need=no, active=unknown17 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 11: HDMI 5 [HDMI 5] Subdevices: 1/1 Subdevice #0: subdevice #0 pacmd list-sinks 1 sink(s) available. * index: 0 name: driver: flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 9039 volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 0,00 ms max request: 0 KiB max rewind: 0 KiB monitor source: 0 sample spec: s16le 2ch 48000Hz channel map: front-left,front-right Stereo used by: 0 linked by: 0 configured latency: 0,00 ms; range is 0,50 .. 2000,00 ms card: 1 module: 8 properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC294 Analog" alsa.id = "ALC294 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0x9830 irq 171" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1f.3" sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "06c8" device.form_factor = "internal" device.string = "front:0" device.buffering.buffer_size = "384000" device.buffering.fragment_size = "192000" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" ports: analog-output-speaker: Speakers (priority 1, latency offset 0 usec, available: unknown) properties: device.icon_name = "audio-speakers" analog-output-headphones: Headphones (priority 9900, latency offset 0 usec, available: no) properties: device.icon_name = "audio-headphones" active port: ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: alc294 asus gx701 sound -- 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/1956369 Title: The headphones work without problems, as does the microphone but there is no sound on the speakers Status in alsa-driver package in Ubuntu: New Bug description: I have a problem with my Asus GX701LWS, the headphones work without problems, as does the microphone but there is no sound on the speakers. hwinfo --sound 22: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.Qb7ky1jjQRD SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x06c8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1f01 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x9830-0x98303fff (rw,non-prefetchable)
[Touch-packages] [Bug 1650688] Re: timedatectl set-timezone fails on UC16
Anything else has to be done for this? -- 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/1650688 Title: timedatectl set-timezone fails on UC16 Status in Snappy: Triaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: Won't Fix Status in systemd source package in Impish: Won't Fix Status in systemd source package in Jammy: Fix Released Bug description: SRU === [Impact] * The bug prevents timedated from recognizing and correctly set the system's timezone when running Ubuntu Core 16, 18 and 20. * This causes by timedated fails to take Ubuntu Core's /etc/writable redirection into account. * The recognizing part is fixed by making the code take writable redirection into account. * The set part is fixed by making the code link to the absolute path instead of a relative one. * Currently core snaps worked around the set part by providing a wrapper script which re-create /etc/writable/localtime afterward. However this does not cover DBus users. [Test Plan] * On classics systems: ensure the proposed systemd package is installed. On Ubuntu Core systems: build a new core snap including proposed package, and install it. Replaces timedatectl with timedatectl.real to test skipping the wrapper. (Note that one can simulate core snap's /etc/writable redirection by running this image creation hook [1] on the system.) [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- core/hooks/08-etc-writable.chroot?h=ubuntu/focal * On freshly boot system: query the timezone using `timedatectl`. The timezone should corresponds to `readlink -f /etc/localtime` and does not show `n/a`. * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`. `readlink -f /etc/localtime` should points to an existing file. * Run `sudo systemctl restart systemd-timedated.service`. Then, query the timezone again: `timedatectl`. It should show the previously set timezone and not `n/a`. * Run `sudo systemctl status systemd-timedated.service`. This should show no sign of timedated crashing. [Where problems could occur] * It's possible that the redirection handling code will be sub-par and causes crash. However, it's not likely because the similar pieces of code is in the previous patch since Ubuntu 16.04. * If it does: the patched `get_timezone()` function is used in 2 places: the networkd's DHCP server [3] and the timedated itself. - Networkd is used primarily on servers where NetworkManage is absent. It's possible that this patch causes the user to loss access to the server due to networkd crash when setting up network interfaces, and requires physical access to fix. However, the code path is executed when DHCP is enabled only. I think it's not common for users to have networkd's DHCP server enabled: the feature seems to gear towards desktop users wanting to share internet connection, and in those cases they're more likely to use NetworkManager. - The timedated itself is likely used by the programs that involves in time-related functions. If a crash occur, in the worst case users won't be able to set time or timezone via timedated. However, users should still be able to e.g. set time using `date` or set timezone using /etc/localtime (assuming online guides still consider systems without systemd). Timedated is DBus-activated, and thus a crash should be self-healing. * The set part would also affects the clasic systems. However, I believe nothing else actually rely on /etc/localtime being a relative path, otherwise the /etc/writable redirection would causes even more problem, and would have been reported. [3] Yes, I'm surprised that there's a DHCP server inside systemd codebase. [Other Info] * This is also useful for UBports's Ubuntu Touch. We continue using system-image system where the rootfs is read-only, and thus is affected by this bug similarly to Ubuntu Core. I've tested the Focal version of the package on our (currently in development) Focal Ubuntu Touch image, and the fix works. [Original bug description] On a system running UC16, the file /etc/localtime is a link that points to /etc/writable/localtime. On a freshly installed system, /etc/writable/localtime is a fully- qualified link that points at /usr/share/zoneinfo/UTC. If timedatectl is used to set the timezone to something else, timedated updates the localtime symbolic link with a relative path to the zoneinfo directory, which results in an invalid link. $ sudo timedatectl set-timezone America/Detroit $ sudo timedatectl Local time: Fri 2016-12-16 18:18:49
[Touch-packages] [Bug 1038479] Re: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a while
It doesn't work for my Asus gx701lws. The headphones work without problems, as does the microphone but there is no sound on the speakers. hwinfo --sound 22: PCI 1f.3: 0403 Audio device [Created at pci.386] Unique ID: nS1_.Qb7ky1jjQRD SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x06c8 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1f01 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0x9830-0x98303fff (rw,non-prefetchable) Memory Range: 0x9810-0x981f (rw,non-prefetchable) IRQ: 171 (910 events) Module Alias: "pci:v8086d06C8sv1043sd1F01bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_sof_pci_intel_cnl is active Driver Activation Cmd: "modprobe snd_sof_pci_intel_cnl" Config Status: cfg=new, avail=yes, need=no, active=unknown17 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC294 Analog [ALC294 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: NVidia [HDA NVidia], device 11: HDMI 5 [HDMI 5] Subdevices: 1/1 Subdevice #0: subdevice #0 pacmd list-sinks 1 sink(s) available. * index: 0 name: driver: flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 9039 volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB balance 0,00 base volume: 65536 / 100% / 0,00 dB volume steps: 65537 muted: no current latency: 0,00 ms max request: 0 KiB max rewind: 0 KiB monitor source: 0 sample spec: s16le 2ch 48000Hz channel map: front-left,front-right Stereo used by: 0 linked by: 0 configured latency: 0,00 ms; range is 0,50 .. 2000,00 ms card: 1 module: 8 properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "ALC294 Analog" alsa.id = "ALC294 Analog" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0x9830 irq 171" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1f.3" sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "06c8" device.form_factor = "internal" device.string = "front:0" device.buffering.buffer_size = "384000" device.buffering.fragment_size = "192000" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "Built-in Audio Analog Stereo" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" ports: analog-output-speaker: Speakers (priority 1, latency offset 0 usec, available: unknown) properties: device.icon_name = "audio-speakers" analog-output-headphones: Headphones (priority 9900, latency offset 0 usec, available: no) properties: device.icon_name = "audio-headphones" active port: -- 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/1038479 Title: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: Restart will fix the issue, but sound always quits from
[Touch-packages] [Bug 1950039] Re: ufw 0.36.1-3 introduces ordering cycle, breaking network
> This makes me want to understand the cloud-init configuration that is in play. Can you share it? I'm thinking I should upload: DefaultDependencies=no Before=network-pre.target Wants=network-pre.target local-fs.target After=local-fs.target Do you have any objections? This would remove the explicit sysinit from the dependency equation but I think it would otherwise achieve ufw's startup objectives. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1950039 Title: ufw 0.36.1-3 introduces ordering cycle, breaking network Status in cloud-init package in Ubuntu: New Status in ufw package in Ubuntu: New Bug description: [2.065178] systemd[1]: systemd-networkd.service: Found ordering cycle on network-pre.target/start [2.065276] systemd[1]: systemd-networkd.service: Found dependency on ufw.service/start [2.065356] systemd[1]: systemd-networkd.service: Found dependency on basic.target/start [2.065422] systemd[1]: systemd-networkd.service: Found dependency on sockets.target/start [2.065487] systemd[1]: systemd-networkd.service: Found dependency on cloud-init-hotplugd.socket/star t [2.065561] systemd[1]: systemd-networkd.service: Found dependency on sysinit.target/start [2.065626] systemd[1]: systemd-networkd.service: Found dependency on cloud-init.service/start [2.065700] systemd[1]: systemd-networkd.service: Found dependency on systemd-networkd-wait-online.se rvice/start [2.065795] systemd[1]: systemd-networkd.service: Found dependency on systemd-networkd.service/start [2.065870] systemd[1]: systemd-networkd.service: Job network-pre.target/start deleted to break ordering cycle starting with systemd-networkd.service/start [[0;1;31m SKIP [0m] Ordering cycle found, skipping [0;1;39mNetwork (Pre)[0m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1950039/+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 1955717] Re: BUG: unsupported FP instruction in kernel mode FPEXC == 0x40000700 at the end of a btrfs balance to RAID1
** Package changed: apport (Ubuntu) => linux (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/1955717 Title: BUG: unsupported FP instruction in kernel mode FPEXC == 0x4700 at the end of a btrfs balance to RAID1 Status in linux package in Ubuntu: New Bug description: Hello there, on my Raspberry Pi 4 I needed to convert a volume to RAID1, so I added a disk and launched btrfs balance: #> sudo btrfs balance start -dconvert=raid1 -mconvert=raid1 /mnt/mountpoint The volume was 5 Tb worth of data, and after a couple of days the process looked terminated correctly, in "sudo btrfs filesystem show" everything looked ok: Label: 'mountpoint' uuid: 15d2c29b-dc20-48a9-910d-e1af8948ed08 Total devices 2 FS bytes used 4.38TiB devid1 size 5.45TiB used 5.16TiB path /dev/mapper/dev-sdb1 devid2 size 8.65TiB used 5.16TiB path /dev/mapper/dev-sda3 The total size is less than the single devices size because during the process I managed to free up 1 Tb of data. Anyway, I looked at the screen containing the balance command and it actually terminated with a segfault, and dmesg was reporting this: [ven dic 24 13:04:06 2021] BTRFS info (device dm-5): relocating block group 2177892352 flags data [ven dic 24 13:04:43 2021] BTRFS info (device dm-5): found 462 extents, stage: move data extents [ven dic 24 13:04:44 2021] BTRFS info (device dm-5): found 462 extents, stage: update data pointers [ven dic 24 13:04:44 2021] BTRFS info (device dm-5): relocating block group 1104150528 flags data [ven dic 24 13:05:22 2021] BTRFS info (device dm-5): found 2625 extents, stage: move data extents [ven dic 24 13:05:23 2021] BTRFS info (device dm-5): found 2625 extents, stage: update data pointers [ven dic 24 13:05:24 2021] BTRFS info (device dm-5): relocating block group 30408704 flags metadata|dup [ven dic 24 13:05:56 2021] BTRFS info (device dm-5): found 2412 extents, stage: move data extents [ven dic 24 13:06:00 2021] BTRFS info (device dm-5): relocating block group 22020096 flags system|dup [ven dic 24 13:06:01 2021] BTRFS info (device dm-5): balance: ended with status: 0 [ven dic 24 13:06:01 2021] BUG: unsupported FP instruction in kernel mode [ven dic 24 13:06:01 2021] FPEXC == 0x4700 [ven dic 24 13:06:01 2021] Internal error: Oops - undefined instruction: 0 [#1] SMP ARM [ven dic 24 13:06:01 2021] Modules linked in: rpcsec_gss_krb5 veth cdc_acm aes_arm_bs crypto_simd cryptd dm_crypt dm_mod fuse xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc overlay sg sch_fq_codel nfsd ip_tables x_tables ipv6 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq raid1 raid0 linear md_mod hid_logitech_hidpp joydev hid_logitech_dj brcmfmac brcmutil vc4 sha256_generic v3d cec gpu_sched drm_kms_helper cfg80211 bcm2835_codec(C) raspberrypi_hwmon rfkill bcm2835_v4l2(C) bcm2835_isp(C) bcm2835_mmal_vchiq(C) v4l2_mem2mem videobuf2_vmalloc videobuf2_dma_contig videobuf2_memops drm videobuf2_v4l2 videobuf2_common vc_sm_cma(C) videodev snd_bcm2835(C) mc drm_panel_orientation_quirks snd_soc_core rpivid_mem snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd syscopyarea sysfillrect [ven dic 24 13:06:01 2021] sysimgblt fb_sys_fops backlight uio_pdrv_genirq nvmem_rmem uio [last unloaded: cdc_acm] [ven dic 24 13:06:01 2021] CPU: 3 PID: 9141 Comm: btrfs Tainted: G C 5.10.63-v7l+ #1459 [ven dic 24 13:06:01 2021] Hardware name: BCM2711 [ven dic 24 13:06:01 2021] PC is at vfp_reload_hw+0x30/0x44 [ven dic 24 13:06:01 2021] LR is at __und_usr_fault_32+0x0/0x8 [ven dic 24 13:06:01 2021] pc : []lr : []psr: a0070013 [ven dic 24 13:06:01 2021] sp : ca0adfb0 ip : ca0adf30 fp : 0003 [ven dic 24 13:06:01 2021] r10: ca0ac1f8 r9 : c0201024 r8 : c1205048 [ven dic 24 13:06:01 2021] r7 : 0001 r6 : r5 : c0288068 r4 : c88f60f8 [ven dic 24 13:06:01 2021] r3 : c135607c r2 : b6cfeb8c r1 : ae24b2ce r0 : f421070d [ven dic 24 13:06:01 2021] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user [ven dic 24 13:06:01 2021] Control: 30c5383d Table: 0335dd80 DAC: [ven dic 24 13:06:01 2021] Process btrfs (pid: 9141, stack limit = 0x7d756e7e) [ven dic 24 13:06:01 2021] Stack: (0xca0adfb0 to 0xca0ae000) [ven dic 24 13:06:01 2021] dfa0: 00ad81d2 00491e87 0008 002c [ven dic 24 13:06:01 2021] dfc0: 0008 b6d95d28 00491e8f 00491e87 b6cef66d b6d95e4c [ven dic 24 13:06:01 2021] dfe0: 00ad81d2 be903718 b6cfa6d5 b6cfeb8c 80070010 [ven dic 24
[Touch-packages] [Bug 1955965] Re: 21.10 cannot enter desktop after blacklist nouveau driver
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1955965 Title: 21.10 cannot enter desktop after blacklist nouveau driver Status in xorg package in Ubuntu: New Bug description: Ubuntu 21.10 can NOT enter desktop after: 1) install Nvidia 470 2) blacklist nouveau driver -- why blacklist nouveau? External HDMI monitor render 0.5 frames/second when turn off built-in monitor. Render normally if both build-in and external HDMI monitor are on. Blacklisting nouveau fix `0.5 frames/s` problem in Ubuntu 21.04, but cannot enter desktop in Ubuntu 21.10 --- why not use Ubuntu 21.04 ? Ubuntu 21.04 render incorrectly, for example, if: 1) built-in monitor: scale=125%, resolution=4000x2000 2) external monitor: scale=100%, resulution=2000x1000 Ubuntu 21.10 render correctly. --- $ lspci 00:00.0 Host bridge: Intel Corporation Device 9b44 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation Device 1f99 (rev a1) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 02) ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1955965/+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 1950039] Re: ufw 0.36.1-3 introduces ordering cycle, breaking network
> I don't believe your reproducer is valid - cloud-init is not installed anymore, as autopkgtest-buildvm-ubuntu-cloud removes it when building the VM, whereas it remains on the cloud images, as it's needed there to actually get the IP address during boot. Note, in https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1950039/comments/9 I installed cloud-init and did some analysis also (but see below). > Though arguably I'd expect this to be fixed by removing DefaultDependencies again, if I looked at this correctly. Seems likely, though this change was done to fix an issue people were seeing on stack exchange for Debian/Ubuntu systems related to a race between encrypted filesystems and ufw. I guess I could add back DefaultDependencies=no and add After=local-fs.target, but I'm not sure what this would do in practice since local-fs.target is so close to the end of sysinit anyway (but see below). In 0.36.1-2, ufw has: DefaultDependencies=no Before=network.target In 0.36.1-3, ufw has (no DefaultDependencies=no): Before=network-pre.target Wants=network-pre.target cloud-init has (among other things): Before=sysinit.target Before=network-pre.target Wants=network-pre.target AIUI, with 0.36.1-2, ufw will tend to start right away due to DefaultDependencies=no and so will cloud-init so long as it finishes before sysinit. ufw need only finish before network.target, which is after network-pre.target. Eg, ufw and cloud-init race to complete but otherwise their dependencies directly don't affect each other. With 0.36.1-3, cloud-init starts early and before ufw since it must finish before sysinit.target and ufw cannot start until after sysinit.target is done. Because both must finish before network- pre.target, this pushes network-pre.target after sysinit (and of course, ufw), but other than that, there shouldn't be a problem since we have: 1. cloud-init starts / finishes 2. sysinit starts / finishes 3. ufw starts / finishes 4. network-pre reached 5. systemd-networkd starts / finishes 6. network reached IME, there is no obvious problem with the dependencies (as they relate to ufw) since cloud-init is allowed to start/finish before sysinit and network-pre just like before. It is just that now network-pre is guaranteed to be after sysinit (which from cloud-init's point of view, shouldn't necessarily be a concern). It is also guaranteed to be after ufw but, unless cloud-init is doing something with ufw such as perhaps enabling ufw and restarting the ufw service, cloud-init shouldn't care cause the ufw service doesn't do anything unless ufw is enabled (and even when it is enabled, it just loads firewall rules). This makes me want to understand the cloud-init configuration that is in play. Can you share it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1950039 Title: ufw 0.36.1-3 introduces ordering cycle, breaking network Status in cloud-init package in Ubuntu: New Status in ufw package in Ubuntu: New Bug description: [2.065178] systemd[1]: systemd-networkd.service: Found ordering cycle on network-pre.target/start [2.065276] systemd[1]: systemd-networkd.service: Found dependency on ufw.service/start [2.065356] systemd[1]: systemd-networkd.service: Found dependency on basic.target/start [2.065422] systemd[1]: systemd-networkd.service: Found dependency on sockets.target/start [2.065487] systemd[1]: systemd-networkd.service: Found dependency on cloud-init-hotplugd.socket/star t [2.065561] systemd[1]: systemd-networkd.service: Found dependency on sysinit.target/start [2.065626] systemd[1]: systemd-networkd.service: Found dependency on cloud-init.service/start [2.065700] systemd[1]: systemd-networkd.service: Found dependency on systemd-networkd-wait-online.se rvice/start [2.065795] systemd[1]: systemd-networkd.service: Found dependency on
[Touch-packages] [Bug 1955965] [NEW] 21.10 cannot enter desktop after blacklist nouveau driver
You have been subscribed to a public bug: Ubuntu 21.10 can NOT enter desktop after: 1) install Nvidia 470 2) blacklist nouveau driver -- why blacklist nouveau? External HDMI monitor render 0.5 frames/second when turn off built-in monitor. Render normally if both build-in and external HDMI monitor are on. Blacklisting nouveau fix `0.5 frames/s` problem in Ubuntu 21.04, but cannot enter desktop in Ubuntu 21.10 --- why not use Ubuntu 21.04 ? Ubuntu 21.04 render incorrectly, for example, if: 1) built-in monitor: scale=125%, resolution=4000x2000 2) external monitor: scale=100%, resulution=2000x1000 Ubuntu 21.10 render correctly. --- $ lspci 00:00.0 Host bridge: Intel Corporation Device 9b44 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation Device 1f99 (rev a1) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 02) ... ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- 21.10 cannot enter desktop after blacklist nouveau driver https://bugs.launchpad.net/bugs/1955965 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1956115] Re: ubuntu-advantage-tools ' MOTD is incompatible with Ubuntu Legal's MOTD opt-out directions.
Its not clear to me what exactly the bug you are reporting is about. The file '/etc/default/motd-news-config' is provided by the package motd- news-config which in turn is part of the cloud-image, server, and ubuntu-server-raspi packages. If that package is not installed then the file will not exist and you should not see the motd-news message. The opt out directions to which you have linked say the following "The motd- news portion is highlighted in green, the other pieces of the MOTD are informational only and do not reach out to the internet for any information". Could you please elaborate on what you want this bug to be about? ** Tags removed: rls-jj-incoming ** Changed in: base-files (Ubuntu) Status: New => Incomplete ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1956115 Title: ubuntu-advantage-tools ' MOTD is incompatible with Ubuntu Legal's MOTD opt-out directions. Status in base-files package in Ubuntu: Incomplete Status in ubuntu-advantage-tools package in Ubuntu: Incomplete Bug description: https://ubuntu.com/legal/motd This file does not exist in Jammy 22.04. This wouldn't be a problem if it was actually removable without having to build custom metapackages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1956115/+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 1946388] Re: Journalctl -f --file some.journal causes coredump
** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Medium ** 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/1946388 Title: Journalctl -f --file some.journal causes coredump Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: In Progress Bug description: [impact] journalctl -f --file FILE results in segfault [test case] $ journalctl -f --file $FILENAME [regression potential] journalctl segfault or failure to properly operate [scope] needed in focal fixed upstream in 2b6df46d21a at v246, so fixed already in h and later [original description] Focal latest systemd 245. Journalctl -f --file path/to/file.journal. Will allways causes journalctl crash... The same doesnt happen on centos8 systemd 239... I couldnt test on any more systems atm. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1946388/+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 1956115] Re: ubuntu-advantage-tools ' MOTD is incompatible with Ubuntu Legal's MOTD opt-out directions.
** Package changed: ubuntu-meta (Ubuntu) => base-files (Ubuntu) ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1956115 Title: ubuntu-advantage-tools ' MOTD is incompatible with Ubuntu Legal's MOTD opt-out directions. Status in base-files package in Ubuntu: New Status in ubuntu-advantage-tools package in Ubuntu: New Bug description: https://ubuntu.com/legal/motd This file does not exist in Jammy 22.04. This wouldn't be a problem if it was actually removable without having to build custom metapackages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1956115/+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 1946388] Re: Journalctl -f --file some.journal causes coredump
** Changed in: systemd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1946388 Title: Journalctl -f --file some.journal causes coredump Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Bug description: [impact] journalctl -f --file FILE results in segfault [test case] $ journalctl -f --file $FILENAME [regression potential] journalctl segfault or failure to properly operate [scope] needed in focal fixed upstream in 2b6df46d21a at v246, so fixed already in h and later [original description] Focal latest systemd 245. Journalctl -f --file path/to/file.journal. Will allways causes journalctl crash... The same doesnt happen on centos8 systemd 239... I couldnt test on any more systems atm. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1946388/+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 1956350] Re: xdg-desktop-portal-gnome missing in Jammy ISO
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1956350 Title: xdg-desktop-portal-gnome missing in Jammy ISO Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Ubuntu Jammy ISO contains xdg-desktop-portal-gtk but xdg-desktop-portal-gnome is missing. xdg-desktop-portal-gnome is needed for GIMP Color picker and Flameshot on Wayland. see https://gitlab.gnome.org/GNOME/gimp/-/issues/1074 apt show xdg-desktop-portal-gnome says: Non-GNOME GTK-based desktop environments should normally use xdg-desktop-portal-gtk or their own portal implementation instead of this one. and Ubuntu 22.04 is a GNOME desktop, so xdg-desktop-portal-gnome should be included in the ISO image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1956350/+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 1956350] Re: xdg-desktop-portal-gnome missing in Jammy ISO
** Project changed: ubuntu-cdimage => ubuntu-meta (Ubuntu) ** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1956350 Title: xdg-desktop-portal-gnome missing in Jammy ISO Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Ubuntu Jammy ISO contains xdg-desktop-portal-gtk but xdg-desktop-portal-gnome is missing. xdg-desktop-portal-gnome is needed for GIMP Color picker and Flameshot on Wayland. see https://gitlab.gnome.org/GNOME/gimp/-/issues/1074 apt show xdg-desktop-portal-gnome says: Non-GNOME GTK-based desktop environments should normally use xdg-desktop-portal-gtk or their own portal implementation instead of this one. and Ubuntu 22.04 is a GNOME desktop, so xdg-desktop-portal-gnome should be included in the ISO image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1956350/+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 1956350] [NEW] xdg-desktop-portal-gnome missing in Jammy ISO
You have been subscribed to a public bug: Ubuntu Jammy ISO contains xdg-desktop-portal-gtk but xdg-desktop-portal-gnome is missing. xdg-desktop-portal-gnome is needed for GIMP Color picker and Flameshot on Wayland. see https://gitlab.gnome.org/GNOME/gimp/-/issues/1074 apt show xdg-desktop-portal-gnome says: Non-GNOME GTK-based desktop environments should normally use xdg-desktop-portal-gtk or their own portal implementation instead of this one. and Ubuntu 22.04 is a GNOME desktop, so xdg-desktop-portal-gnome should be included in the ISO image. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- xdg-desktop-portal-gnome missing in Jammy ISO https://bugs.launchpad.net/bugs/1956350 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta 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 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
Right. It should be the default. I had to set it for the main clock and the file chooser in both current GTK versions. The regular UX is odd. gsettings set org.gnome.desktop.interface clock-format '12h' gsettings set org.gtk.Settings.FileChooser clock-format '12h' gsettings set org.gtk.gtk4.Settings.FileChooser clock-format '12h' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: Unknown Status in gsettings-desktop-schemas package in Ubuntu: Confirmed Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 1946388] Re: Journalctl -f --file some.journal causes coredump
** Bug watch added: github.com/systemd/systemd/issues #15528 https://github.com/systemd/systemd/issues/15528 ** Also affects: systemd via https://github.com/systemd/systemd/issues/15528 Importance: Unknown Status: Unknown ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Description changed: + [impact] + + journalctl -f --file FILE results in segfault + + [test case] + + $ journalctl -f --file $FILENAME + + [regression potential] + + journalctl segfault or failure to properly operate + + [scope] + + needed in focal + + fixed upstream in 2b6df46d21a at v246, so fixed already in h and later + + [original description] + Focal latest systemd 245. Journalctl -f --file path/to/file.journal. Will allways causes journalctl crash... The same doesnt happen on centos8 systemd 239... I couldnt test on any more systems atm. -- 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/1946388 Title: Journalctl -f --file some.journal causes coredump Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Bug description: [impact] journalctl -f --file FILE results in segfault [test case] $ journalctl -f --file $FILENAME [regression potential] journalctl segfault or failure to properly operate [scope] needed in focal fixed upstream in 2b6df46d21a at v246, so fixed already in h and later [original description] Focal latest systemd 245. Journalctl -f --file path/to/file.journal. Will allways causes journalctl crash... The same doesnt happen on centos8 systemd 239... I couldnt test on any more systems atm. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1946388/+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 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS
@Stuart-ward wrote… > This is still a current problem > > $ dpkg -l | grep -i openvpn > ii network-manager-openvpn 1.8.14-1 amd64 network management framework > (OpenVPN plugin core) > ii network-manager-openvpn-gnome 1.8.14-1 amd64 network management framework > (OpenVPN plugin GNOME GUI) > ii openvpn 2.5.1-3ubuntu1 amd64 virtual private network daemon Once again, OpenConnect and OpenVPN are *not* the same thing. At all. For your VPN connection, are you using OpenConenct (the original subject of this bug report), or are you using OpenVPN (completely different and should have a separate bug files)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1874257 Title: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS Status in linux package in Ubuntu: Invalid Status in openconnect package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Invalid Status in openconnect source package in Xenial: Confirmed Bug description: Hello Team, SSH timeout issue, once connect to VPN. Environment == Dell XPS 9570 Ubuntu 16.04.6 Xenial Xerus) kernel - 4.15.0-55-generic $dpkg -l | grep -i openssh ii openssh-client 1:7.2p2-4ubuntu2.8 --> ii openssh-server 1:7.2p2-4ubuntu2.8 ii openssh-sftp-server 1:7.2p2-4ubuntu2.8 VPN tunnel info vpn0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:IP P-t-P:xx Mask:255.255.252.0 inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1406 Metric:1 RX packets:962 errors:0 dropped:0 overruns:0 frame:0 TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:87839 (87.8 KB) TX bytes:238740 (238.7 KB) Issue Unable to connect to any host via ssh or sftp after VPN connection Tried = Reinstalled the openssh-client package and still no luck. May I know why the default cipher is not taking/hanging? Please let me know . There were no recent changes. Workaround === Able to connect to ssh / sftp $ssh -c aes128-ctr user@IP Below is the debug ssh client logs === == $ssh -vvv user@ip OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g 1 Mar 2016 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: resolving "IP" port 22 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to IP [IP] port 22. debug1: Connection established. debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to IP:22 as 'user' debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c debug2: host key algorithms: ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa debug2: ciphers ctos: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc debug2: ciphers
[Touch-packages] [Bug 1952934] Re: Intel HDA Sound Card not detected on Ubuntu 20.04
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952934/+attachment/5551088/+files/dmesg.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/1952934 Title: Intel HDA Sound Card not detected on Ubuntu 20.04 Status in alsa-driver package in Ubuntu: Confirmed Bug description: the intel sound card is not detected and only "dummy output" is available I've tested on kernel 5.15 but it s the same on default 5.11 kernel Also tried without success : - Booted the 5.4 - added snd_intel_dspcfg.dsp_driver=1 boot param ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.15.6-051506-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2217 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Dec 1 17:35:25 2021 InstallationDate: Installed on 2021-11-19 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2021 dmi.bios.release: 85.176 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: TN1V5.03_PCS dmi.board.asset.tag: Board Asset Tag dmi.board.name: WN1 dmi.board.vendor: IP3 dmi.board.version: V20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PCSpecialist dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnINSYDECorp.:bvrTN1V5.03_PCS:bd05/26/2021:br85.176:efr1.4:svnPCSpecialist:pnTN1-156M:pvrV10:rvnIP3:rnWN1:rvrV20:cvnPCSpecialist:ct10:cvrChassisVersion:skuTN1-156M: dmi.product.family: Notebook dmi.product.name: TN1-156M dmi.product.sku: TN1-156M dmi.product.version: V10 dmi.sys.vendor: PCSpecialist modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-30T14:02:48.711418 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952934/+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 1952934] Re: Intel HDA Sound Card not detected on Ubuntu 20.04
Reinstalled a fresh 20.04.3 : dmesg attached 6.196452] snd_hda_intel :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [6.196478] snd_hda_intel :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [6.224933] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [6.224960] sof-audio-pci :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [6.224980] sof-audio-pci :00:1f.3: enabling device ( -> 0002) [6.225234] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [6.225336] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [6.231868] sof-audio-pci :00:1f.3: use msi interrupt mode [6.245453] sof-audio-pci :00:1f.3: hda codecs found, mask 4 [6.245456] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [6.245462] sof-audio-pci :00:1f.3: DMICs detected in NHLT tables: 2 [6.332979] sof-audio-pci :00:1f.3: Firmware info: version 1:6:0-18fab [6.332986] sof-audio-pci :00:1f.3: Firmware: ABI 3:17:0 Kernel ABI 3:18:0 [6.346627] sof-audio-pci :00:1f.3: Topology: ABI 3:17:0 Kernel ABI 3:18:0 [6.371269] sof-audio-pci :00:1f.3: ASoC: Parent card not yet available, widget card binding deferred -- 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/1952934 Title: Intel HDA Sound Card not detected on Ubuntu 20.04 Status in alsa-driver package in Ubuntu: Confirmed Bug description: the intel sound card is not detected and only "dummy output" is available I've tested on kernel 5.15 but it s the same on default 5.11 kernel Also tried without success : - Booted the 5.4 - added snd_intel_dspcfg.dsp_driver=1 boot param ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.15.6-051506-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem2217 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Dec 1 17:35:25 2021 InstallationDate: Installed on 2021-11-19 (12 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2021 dmi.bios.release: 85.176 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: TN1V5.03_PCS dmi.board.asset.tag: Board Asset Tag dmi.board.name: WN1 dmi.board.vendor: IP3 dmi.board.version: V20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PCSpecialist dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnINSYDECorp.:bvrTN1V5.03_PCS:bd05/26/2021:br85.176:efr1.4:svnPCSpecialist:pnTN1-156M:pvrV10:rvnIP3:rnWN1:rvrV20:cvnPCSpecialist:ct10:cvrChassisVersion:skuTN1-156M: dmi.product.family: Notebook dmi.product.name: TN1-156M dmi.product.sku: TN1-156M dmi.product.version: V10 dmi.sys.vendor: PCSpecialist modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-30T14:02:48.711418 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1952934/+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 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS
This is still a current problem $ dpkg -l | grep -i openvpn ii network-manager-openvpn 1.8.14-1 amd64network management framework (OpenVPN plugin core) ii network-manager-openvpn-gnome 1.8.14-1 amd64network management framework (OpenVPN plugin GNOME GUI) ii openvpn 2.5.1-3ubuntu1 amd64virtual private network daemon $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 21.10 Release:21.10 Codename: impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1874257 Title: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS Status in linux package in Ubuntu: Invalid Status in openconnect package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Invalid Status in openconnect source package in Xenial: Confirmed Bug description: Hello Team, SSH timeout issue, once connect to VPN. Environment == Dell XPS 9570 Ubuntu 16.04.6 Xenial Xerus) kernel - 4.15.0-55-generic $dpkg -l | grep -i openssh ii openssh-client 1:7.2p2-4ubuntu2.8 --> ii openssh-server 1:7.2p2-4ubuntu2.8 ii openssh-sftp-server 1:7.2p2-4ubuntu2.8 VPN tunnel info vpn0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:IP P-t-P:xx Mask:255.255.252.0 inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1406 Metric:1 RX packets:962 errors:0 dropped:0 overruns:0 frame:0 TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:87839 (87.8 KB) TX bytes:238740 (238.7 KB) Issue Unable to connect to any host via ssh or sftp after VPN connection Tried = Reinstalled the openssh-client package and still no luck. May I know why the default cipher is not taking/hanging? Please let me know . There were no recent changes. Workaround === Able to connect to ssh / sftp $ssh -c aes128-ctr user@IP Below is the debug ssh client logs === == $ssh -vvv user@ip OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g 1 Mar 2016 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: resolving "IP" port 22 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to IP [IP] port 22. debug1: Connection established. debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to IP:22 as 'user' debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c debug2: host key algorithms: ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa debug2: ciphers ctos:
[Touch-packages] [Bug 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS
See this AskUbuntu item on this bug https://askubuntu.com/questions/1229456/ssh-fails-with-connection-timed-out-in-vpn-and-hangs-here-expecting-ssh2-msg I resolved this with the suggested setting: > As a temporary workaround, setting the KEX algorithm manually solves this > problem for me. > Add KexAlgorithms ecdh-sha2-nistp521 to the corresponding SSH config, or add > -oKexAlgorithms=ecdh-sha2-nistp521 to the command line args for one time use. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1874257 Title: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS Status in linux package in Ubuntu: Invalid Status in openconnect package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Invalid Status in openconnect source package in Xenial: Confirmed Bug description: Hello Team, SSH timeout issue, once connect to VPN. Environment == Dell XPS 9570 Ubuntu 16.04.6 Xenial Xerus) kernel - 4.15.0-55-generic $dpkg -l | grep -i openssh ii openssh-client 1:7.2p2-4ubuntu2.8 --> ii openssh-server 1:7.2p2-4ubuntu2.8 ii openssh-sftp-server 1:7.2p2-4ubuntu2.8 VPN tunnel info vpn0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:IP P-t-P:xx Mask:255.255.252.0 inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1406 Metric:1 RX packets:962 errors:0 dropped:0 overruns:0 frame:0 TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:87839 (87.8 KB) TX bytes:238740 (238.7 KB) Issue Unable to connect to any host via ssh or sftp after VPN connection Tried = Reinstalled the openssh-client package and still no luck. May I know why the default cipher is not taking/hanging? Please let me know . There were no recent changes. Workaround === Able to connect to ssh / sftp $ssh -c aes128-ctr user@IP Below is the debug ssh client logs === == $ssh -vvv user@ip OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g 1 Mar 2016 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: resolving "IP" port 22 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to IP [IP] port 22. debug1: Connection established. debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to IP:22 as 'user' debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms: curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c debug2: host key algorithms: ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa debug2: ciphers ctos: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc debug2: ciphers stoc: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
[Touch-packages] [Bug 1854621] Re: ubuntu 20.04 daily boots with no (or warped) background, selecting other background has warped wallpaper
Also happens on the Lenovo T60 laptop with the radeon x1300 GPU. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1854621 Title: ubuntu 20.04 daily boots with no (or warped) background, selecting other background has warped wallpaper Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 daily - verified (check disc for defects) prior to boot. dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550) On booting, the 20.04 daily has no background when desktop is loaded? (ie. top panel is there, dock on left side on black screen) When changing background (to any already installed), they are warped when selected and made the bacground as if corrupted (but small image where selection is made looks valid). This issue may relate to video card [radeon] ubuntu@ubuntu:~$ sudo lshw -C video *-display:0 description: VGA compatible controller product: RV516 [Radeon X1300/X1550 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:16 memory:d000-dfff memory:fe9e-fe9e ioport:dc00(size=256) memory:c-d *-display:1 UNCLAIMED description: Display controller product: RV516 [Radeon X1300/X1550 Series] (Secondary) vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0.1 bus info: pci@:01:00.1 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress bus_master cap_list configuration: latency=0 resources: memory:fe9f-fe9f ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.440 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CasperVersion: 1.432 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 1 11:58:33 2019 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1854621/+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 1854621] Re: ubuntu 20.04 daily boots with no (or warped) background, selecting other background has warped wallpaper
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1854621 Title: ubuntu 20.04 daily boots with no (or warped) background, selecting other background has warped wallpaper Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 daily - verified (check disc for defects) prior to boot. dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550) On booting, the 20.04 daily has no background when desktop is loaded? (ie. top panel is there, dock on left side on black screen) When changing background (to any already installed), they are warped when selected and made the bacground as if corrupted (but small image where selection is made looks valid). This issue may relate to video card [radeon] ubuntu@ubuntu:~$ sudo lshw -C video *-display:0 description: VGA compatible controller product: RV516 [Radeon X1300/X1550 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:16 memory:d000-dfff memory:fe9e-fe9e ioport:dc00(size=256) memory:c-d *-display:1 UNCLAIMED description: Display controller product: RV516 [Radeon X1300/X1550 Series] (Secondary) vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0.1 bus info: pci@:01:00.1 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress bus_master cap_list configuration: latency=0 resources: memory:fe9f-fe9f ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.440 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CasperVersion: 1.432 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 1 11:58:33 2019 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191128) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1854621/+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 1955826] Re: screen tearing
*** This bug is a duplicate of bug 1846398 *** https://bugs.launchpad.net/bugs/1846398 You will need to either disable fractional scaling or log into a 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/1955826 Title: screen tearing Status in xorg package in Ubuntu: New Bug description: screen was tearing while watching videos ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 27 18:46:54 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822] InstallationDate: Installed on 2021-12-04 (22 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e360 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 5986:06b1 Acer, Inc EasyCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80SL ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=dbf98c46-2c30-46b7-9d28-b94843baabd5 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2018 dmi.bios.release: 1.45 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.ec.firmware.release: 1.45 dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:br1.45:efr1.45:svnLENOVO:pn80SL:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:skuLENOVO_MT_80SL_BU_idea_FM_Lenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80SL dmi.product.sku: LENOVO_MT_80SL_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1955826/+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 1955826] Re: screen tearing
*** This bug is a duplicate of bug 1846398 *** https://bugs.launchpad.net/bugs/1846398 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1846398, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1846398 [modeset] xrandr transformations cause significant visible tearing in Xorg sessions -- 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/1955826 Title: screen tearing Status in xorg package in Ubuntu: New Bug description: screen was tearing while watching videos ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 27 18:46:54 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3822] InstallationDate: Installed on 2021-12-04 (22 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e360 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 5986:06b1 Acer, Inc EasyCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80SL ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=dbf98c46-2c30-46b7-9d28-b94843baabd5 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2018 dmi.bios.release: 1.45 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.ec.firmware.release: 1.45 dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:br1.45:efr1.45:svnLENOVO:pn80SL:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:skuLENOVO_MT_80SL_BU_idea_FM_Lenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80SL dmi.product.sku: LENOVO_MT_80SL_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1955826/+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 1955820] Re: Arabic Text under scrolled by one character is not connected with other word characters
Would this be https://bugreports.qt.io/browse/QTBUG-5314 ? Otherwise can you find the problem already reported on https://bugreports.qt.io/browse/ ? ** Package changed: xorg (Ubuntu) => qtbase-opensource-src (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1955820 Title: Arabic Text under scrolled by one character is not connected with other word characters Status in qtbase-opensource-src package in Ubuntu: New Bug description: Hello, All Text with alt action _ are not connected. You can add 'ـ' after some characters , this will keep small space but will not effect of reading. Or under scrolled character viewing when press Alt only. Err Examples in command buttons text: حسناً viewed as ح سناً موافق viewed as م وافق Arabic Firefox is not have this problem. (ملف viewed as ملف) In Arabic Kate (or other KDE application) text menu ملف viewed as م لف This problem in all Alt under scrolled Arabic Text in almost all KDE Applications. Arabic Firefox is not have like this bug. This bug is in Kubuntu Groovy 20.10 too. This bug will not accepted by almost Arabic users. Thank you ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Mon Dec 27 15:25:07 2021 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) Subsystem: VMware VirtualBox Graphics Adapter [15ad:0405] InstallationDate: Installed on 2021-12-26 (1 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211226) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=ar_SA:ar PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ar_SA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=db743c87-a1e6-4345-a978-33c5cd5a65ec ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1955820/+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 1956300] Re: graphics
What kind of problem are you experiencing? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1956300 Title: graphics Status in Ubuntu: Incomplete Bug description: dont no ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1052.54-oem 5.10.76 Uname: Linux 5.10.0-1052-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 4 14:02:03 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a20] InstallationDate: Installed on 2021-08-12 (145 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Latitude 5420 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1052-oem root=UUID=5c089419-1808-46cd-9e10-ebaba3debd73 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/22/2021 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.1 dmi.board.name: 03P5X2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.1:bd11/22/2021:br1.14:svnDellInc.:pnLatitude5420:pvr:sku0A20:rvnDellInc.:rn03P5X2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5420 dmi.product.sku: 0A20 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1956300/+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 1950039] Re: ufw 0.36.1-3 introduces ordering cycle, breaking network
Though arguably I'd expect this to be fixed by removing DefaultDependencies again, if I looked at this correctly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1950039 Title: ufw 0.36.1-3 introduces ordering cycle, breaking network Status in cloud-init package in Ubuntu: New Status in ufw package in Ubuntu: New Bug description: [2.065178] systemd[1]: systemd-networkd.service: Found ordering cycle on network-pre.target/start [2.065276] systemd[1]: systemd-networkd.service: Found dependency on ufw.service/start [2.065356] systemd[1]: systemd-networkd.service: Found dependency on basic.target/start [2.065422] systemd[1]: systemd-networkd.service: Found dependency on sockets.target/start [2.065487] systemd[1]: systemd-networkd.service: Found dependency on cloud-init-hotplugd.socket/star t [2.065561] systemd[1]: systemd-networkd.service: Found dependency on sysinit.target/start [2.065626] systemd[1]: systemd-networkd.service: Found dependency on cloud-init.service/start [2.065700] systemd[1]: systemd-networkd.service: Found dependency on systemd-networkd-wait-online.se rvice/start [2.065795] systemd[1]: systemd-networkd.service: Found dependency on systemd-networkd.service/start [2.065870] systemd[1]: systemd-networkd.service: Job network-pre.target/start deleted to break ordering cycle starting with systemd-networkd.service/start [[0;1;31m SKIP [0m] Ordering cycle found, skipping [0;1;39mNetwork (Pre)[0m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1950039/+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 1950039] Re: ufw 0.36.1-3 introduces ordering cycle, breaking network
I have added a cloud-init task, to draw cloud-init people in to help get this resolved. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1950039 Title: ufw 0.36.1-3 introduces ordering cycle, breaking network Status in cloud-init package in Ubuntu: New Status in ufw package in Ubuntu: New Bug description: [2.065178] systemd[1]: systemd-networkd.service: Found ordering cycle on network-pre.target/start [2.065276] systemd[1]: systemd-networkd.service: Found dependency on ufw.service/start [2.065356] systemd[1]: systemd-networkd.service: Found dependency on basic.target/start [2.065422] systemd[1]: systemd-networkd.service: Found dependency on sockets.target/start [2.065487] systemd[1]: systemd-networkd.service: Found dependency on cloud-init-hotplugd.socket/star t [2.065561] systemd[1]: systemd-networkd.service: Found dependency on sysinit.target/start [2.065626] systemd[1]: systemd-networkd.service: Found dependency on cloud-init.service/start [2.065700] systemd[1]: systemd-networkd.service: Found dependency on systemd-networkd-wait-online.se rvice/start [2.065795] systemd[1]: systemd-networkd.service: Found dependency on systemd-networkd.service/start [2.065870] systemd[1]: systemd-networkd.service: Job network-pre.target/start deleted to break ordering cycle starting with systemd-networkd.service/start [[0;1;31m SKIP [0m] Ordering cycle found, skipping [0;1;39mNetwork (Pre)[0m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1950039/+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 1950039] Re: ufw 0.36.1-3 introduces ordering cycle, breaking network
I don't believe your reproducer is valid - cloud-init is not installed anymore, as autopkgtest-buildvm-ubuntu-cloud removes it when building the VM, whereas it remains on the cloud images, as it's needed there to actually get the IP address during boot. Removing the DefaultDependencies=no means that ufw.service is After=basic.target After=sysinit.target. cloud-init.service has Before=sysinit.target, so would have to run before ufw.service. It is After=systemd-networkd-wait-online.service though which is After=systemd-networkd which is After=network-pre.target. So there's the cycle, we need to run cloud-init After=network-pre (hence After ufw), but determined before that cloud-init needs to run before sysinit.target, which needs to run before ufw.service. I can't reproduce the issue in a VM right now, though, because um, cloud-init does not seem to start at all during second boot despite seemingly being enabled. ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1950039 Title: ufw 0.36.1-3 introduces ordering cycle, breaking network Status in cloud-init package in Ubuntu: New Status in ufw package in Ubuntu: New Bug description: [2.065178] systemd[1]: systemd-networkd.service: Found ordering cycle on network-pre.target/start [2.065276] systemd[1]: systemd-networkd.service: Found dependency on ufw.service/start [2.065356] systemd[1]: systemd-networkd.service: Found dependency on basic.target/start [2.065422] systemd[1]: systemd-networkd.service: Found dependency on sockets.target/start [2.065487] systemd[1]: systemd-networkd.service: Found dependency on cloud-init-hotplugd.socket/star t [2.065561] systemd[1]: systemd-networkd.service: Found dependency on sysinit.target/start [2.065626] systemd[1]: systemd-networkd.service: Found dependency on cloud-init.service/start [2.065700] systemd[1]: systemd-networkd.service: Found dependency on systemd-networkd-wait-online.se rvice/start [2.065795] systemd[1]: systemd-networkd.service: Found dependency on systemd-networkd.service/start [2.065870] systemd[1]: systemd-networkd.service: Job network-pre.target/start deleted to break ordering cycle starting with systemd-networkd.service/start [[0;1;31m SKIP [0m] Ordering cycle found, skipping [0;1;39mNetwork (Pre)[0m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1950039/+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 1955702] Re: Grafikkarte Treiber
** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Grafikkarte Treiber + radeon kernel crashes in radeon_ttm_backend_bind ** Tags added: radeon -- 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/1955702 Title: radeon kernel crashes in radeon_ttm_backend_bind Status in linux package in Ubuntu: Confirmed Bug description: Grafikkarte Probleme ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 24 10:52:06 2021 DistUpgraded: 2021-12-23 00:23:01,754 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7640G] [1002:9903] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Trinity [Radeon HD 7640G] [144d:c0da] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Radeon HD 7670M [144d:c0da] InstallationDate: Installed on 2021-12-22 (1 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: SAMSUNG ELECTRONICS CO., LTD. 355V4C/356V4C/3445VC/3545VC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=fc93f578-a24f-400f-95c2-03eaf71b373f ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-12-22 (1 days ago) dmi.bios.date: 07/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P07ABF dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP355E7C-S09DE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: BOARD REVISION 00 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP07ABF:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn355V4C/356V4C/3445VC/3545VC:pvrP07ABF.010.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP355E7C-S09DE:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: Eureka dmi.product.name: 355V4C/356V4C/3445VC/3545VC dmi.product.sku: P07ABF.010.CP dmi.product.version: P07ABF.010.CP dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955702/+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 1955632] Re: Screen flickering or going black
This appears to be a desktop machine so please don't install any brightness controlling software as that's likely to cause more problems than it solves. You should adjust the brightness on the TV itself. Also please try a different VGA cable if you can. Or at least unplug both ends and plug them in again firmly. ** Package changed: xorg (Ubuntu) => linux-oem-5.14 (Ubuntu) ** Summary changed: - Screen flickering or going black + [i915] Screen flickering or going black ** Summary changed: - [i915] Screen flickering or going black + [i915] TV connected by VGA is flickering or going black -- 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/1955632 Title: [i915] TV connected by VGA is flickering or going black Status in linux-oem-5.14 package in Ubuntu: New Bug description: I've been using Ubuntu 20.04 for a long time now and have had no problems. Then suddenly the screen started flickering. I tried PCLinuxOS but the screen just goes black. I found, on Ubuntu, installing brightness-controller and putting the screen brightness down below half way and the setting to Clear Blue Sky helps quite a lot but is hard to see. It still flickers once in awhile. And I cannot create a file in /sys/class/backlight to make the change permanent on boot. The only major change I can think of is setting LivePatch up that could have caused the flickering. Thank you, I hope you find the fix as no Linux distros will work on my ThinkCentre desktop PC. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1011.11-oem 5.14.17 Uname: Linux 5.14.0-1011-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 23 01:52:31 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821CU, 5.4.1, 5.11.0-43-generic, x86_64: installed rtl8821CU, 5.4.1, 5.14.0-1011-oem, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [17aa:3083] InstallationDate: Installed on 2021-10-16 (68 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 3227K45 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1011-oem root=UUID=e7536889-191e-4640-ba6f-6e940cb65228 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2018 dmi.bios.release: 0.6 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT9CAUS dmi.board.asset.tag: 640688 dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvr9SKT9CAUS:bd12/11/2018:br0.6:svnLENOVO:pn3227K45:pvrThinkCentreM92P:rvnLENOVO:rnMAHOBAY:rvr0B98401PRO:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_3227: dmi.product.family: To be filled by O.E.M. dmi.product.name: 3227K45 dmi.product.sku: LENOVO_MT_3227 dmi.product.version: ThinkCentre M92P dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1955632/+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 1956275] Re: apt autoremove uninstalls nvidia graphics card drivers
Hi, thanks for your bug report. I'm not quite sure what you are experiencing here, you likely have manually removed a package that depended on the drivers and then caused them to become autoremovable. Though usually I'd have expected the drivers to be installed manually. We are going to need to see /var/log/apt/history.log of previous transactions, and possibly your /var/lib/dpkg/status to know which packages are installed. And if at all possible, the dpkg.status file from before this in /var/backups/. ** Changed in: apt (Ubuntu) Status: New => Incomplete -- 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/1956275 Title: apt autoremove uninstalls nvidia graphics card drivers Status in apt package in Ubuntu: Incomplete Bug description: Hardware information: Razer Blade 15 mid 2019, RTX2060 OS Kubuntu 21.10 command ran: apt autoremove What I expected to happen: Unnecessary packages are removed by autoremove What happened: GPU drivers are removed, preventing graphical interfaces from being used apt logs: Start-Date: 2022-01-03 18:34:51 Commandline: apt autoremove Requested-By: matt (1000) Remove: libnvidia-common-470:amd64 (470.86-0ubuntu0.21.10.1), libxnvctrl0:amd64 (470.57.01-0ubuntu3), libnvidia-fbc1-470:amd64 (470.86-0ubuntu0.21.10.1), libnvidia-fbc1-470:i386 (470.86-0ubuntu0.21.10.1), libnvidia-gl-470:amd64 (470.86-0ubuntu0.21.10.1), libnvidia-gl-470:i386 (470.86-0ubuntu0.21.10.1), libnvidia-extra-470:amd64 (470.86-0ubuntu0.21.10.1), nvidia-compute-utils-470:amd64 (470.86-0ubuntu0.21.10.1), libnvidia-encode-470:amd64 (470.86-0ubuntu0.21.10.1), libnvidia-encode-470:i386 (470.86-0ubuntu0.21.10.1), nvidia-utils-470:amd64 (470.86-0ubuntu0.21.10.1), xserver-xorg-video-nvidia-470:amd64 (470.86-0ubuntu0.21.10.1), libnvidia-ifr1-470:amd64 (470.86-0ubuntu0.21.10.1), libnvidia-ifr1-470:i386 (470.86-0ubuntu0.21.10.1), libsdl-ttf2.0-0:amd64 (2.0.11-6), libnvidia-decode-470:amd64 (470.86-0ubuntu0.21.10.1), libnvidia-decode-470:i386 (470.86-0ubuntu0.21.10.1), screen-resolution-extra:amd64 (0.18.1), nvidia-settings:amd64 (470.57.01-0ubuntu3), lynx-common:amd64 (2.9.0dev.6-3), libnvidia-cfg1-470:amd64 (470.86-0ubuntu0.21.10.1), nvidia-kernel-source-470:amd64 (470.86-0ubuntu0.21.10.1), libnvidia-compute-470:i386 (470.86-0ubuntu0.21.10.1) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: apt 2.3.9 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Jan 3 21:11:15 2022 InstallationDate: Installed on 2021-12-26 (9 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1956275/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1922414 ** Tags added: iso-testing -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in gdm3 package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+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 1955384] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: 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/1955384 Title: Xorg freeze Status in Ubuntu: Incomplete Bug description: This bug happened when I clicked and held the left mouse button on the desktop and moved it to make a rectangular selection window. Next, I moved the window to highlight 4 desktop shortcuts on my desktop (Middle-earth Shadow of Mordor.desktop, steam.desktop, Trash, and the icelancet or Home folder). Next, while still holding the left mouse button down, I pressed and released the right mouse button. Now a window pops up with more options, however, the window is not removable using a normal method like clicking somewhere else on the desktop or even choosing an option in the window which does nothing. Also, it introduces more bugs like: 1. clicking the icelancet/Home shortcut on the desktop does not open the Home folder, or 2. while clicking the Home folder shortcut on the sidebar does open the Home folder, this window is not moveable by the usual method of pressing down the left mouse button on the title bar of the window and moving the mouse. As such, when this bug occurs, a hard reboot is necessary to restore the stability of the system. I have reproduced the bug after a reboot and doing the same procedure - the same thing happens. This is on the latest version of Ubuntu (Release 20.04) with all the latest upstream updates installed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 470.94 Mon Dec 6 22:42:02 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 20 00:46:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:862a] InstallationDate: Installed on 2021-11-23 (27 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Micro-Star International Co., Ltd. MS-7C39 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-43-generic root=UUID=d206716a-6a84-411d-9038-eb4654efc2ec ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.10 dmi.board.asset.tag: Default string dmi.board.name: B365M PRO-VDH(MS-7C39) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias:
[Touch-packages] [Bug 1955297] Re: Xorg freeze
Please open the 'Additional Drivers' app and install the latest Nvidia driver that it offers you. I expect it will be version 390 for the Nvidia GeForce GT 525M. Once installed, please reboot and then tell us if the problem persists. ** Tags added: nouveau ** Package changed: xorg (Ubuntu) => xserver-xorg-video-nouveau (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1955297 Title: Xorg freeze Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-nouveau package in Ubuntu: Incomplete Bug description: Mouse freezes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 18 15:24:35 2021 DistUpgraded: 2021-08-22 20:45:57,513 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GpuHangFrequency: Continuously GpuHangReproducibility: I don't know GpuHangStarted: I don't know GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6] InstallationDate: Installed on 2021-08-08 (132 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Dell System XPS L502X ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=e240f53d-7bb3-4a6d-a0c5-abc23ed371b1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2021-08-22 (117 days ago) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YR8NN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System XPS L502X dmi.product.sku: System SKUNumber dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955297/+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 1955138] Re: [evdi] External monitor stops showing image for a few seconds
** Summary changed: - External monitor stops showing image for a few seconds + [evdi] External monitor stops showing image for a few seconds ** Tags added: displaylink evdi ** Package changed: xorg (Ubuntu) => linux-hwe-5.11 (Ubuntu) ** Package changed: linux-hwe-5.11 (Ubuntu) => evdi (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1955138 Title: [evdi] External monitor stops showing image for a few seconds Status in evdi package in Ubuntu: New Bug description: I use Dell Dock Station - D6000S and noticed in the latest two kernels an instability on my external monitors. I use two external monitors and they randomly stops showing the images for a couple of seconds. It's similar as if the usb-C connection to the docker got interrupted and then connected again. Notebook display doesn't have this issue. Please verify the root cause. Thanks, ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Fri Dec 17 11:25:54 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.9.1, 5.11.0-41-generic, x86_64: installed evdi, 1.9.1, 5.11.0-43-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-41-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:09a0] InstallationDate: Installed on 2021-04-07 (253 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Latitude 5410 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2021 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 08NM43 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd03/11/2021:br1.5:svnDellInc.:pnLatitude5410:pvr:sku09A0:rvnDellInc.:rn08NM43:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5410 dmi.product.sku: 09A0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1955138/+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 1955290] Re: Very high CPU usage
Please run 'top' to find out what is using the most CPU. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1955290 Title: Very high CPU usage Status in Ubuntu: Incomplete Bug description: My system - Lenovo Ideapad S145 with 8 GB RAM, shows very high CPU usage. How can I reduce it? ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 Uname: Linux 5.15.0-8.1-liquorix-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: GNOME Date: Sat Dec 18 10:51:29 2021 DistUpgraded: 2021-12-06 12:41:14,767 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev e2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:3f1a] InstallationDate: Installed on 2021-08-06 (133 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 81ST ProcKernelCmdLine: audit=0 intel_pstate=disable BOOT_IMAGE=/boot/vmlinuz-5.15.0-8.1-liquorix-amd64 root=UUID=f1425acf-af13-4f1a-bcf4-93e1a1c4abc6 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-12-06 (11 days ago) dmi.bios.date: 05/14/2021 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: AYCN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-14AST dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrAYCN25WW:bd05/14/2021:br1.25:efr1.25:svnLENOVO:pn81ST:pvrLenovoIdeaPadS145-14AST:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-14AST:skuLENOVO_MT_81ST_BU_idea_FM_IdeaPadS145-14AST: dmi.product.family: IdeaPad S145-14AST dmi.product.name: 81ST dmi.product.sku: LENOVO_MT_81ST_BU_idea_FM_IdeaPad S145-14AST dmi.product.version: Lenovo IdeaPad S145-14AST dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1955290/+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 1955135] Re: multiple issues with /etc/X11/Xsession.d/ - "has_option: command not found"
*** This bug is a duplicate of bug 1922414 *** https://bugs.launchpad.net/bugs/1922414 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1922414, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1922414 ssh-agent fails to start (has_option: command not found) -- 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/1955135 Title: multiple issues with /etc/X11/Xsession.d/ - "has_option: command not found" Status in dbus package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: Steps to reproduce: 1. Boot 20211217 Ubuntu MATE daily ISO 2. Open ~/.xsession-errors Expected results: * no errors and warnings Actual results: * there are two errors about xorg: /etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not found /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: x11-common 1:7.7+23ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.465 CompositorRunning: None CurrentDesktop: MATE Date: Fri Dec 17 14:22:15 2021 Dependencies: lsb-base 11.1.0ubuntu3 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 425M] [10de:0df0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation GF108M [GeForce GT 425M] [104d:907a] LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211217) MachineType: Sony Corporation VPCF13Z1R PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2010 dmi.bios.release: 1.90 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0190Y9 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 1.90 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0190Y9:bd10/20/2010:br1.90:efr1.90:svnSonyCorporation:pnVPCF13Z1R:pvrC606GZYK:skuN/A:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCF13Z1R dmi.product.sku: N/A dmi.product.version: C606GZYK dmi.sys.vendor: Sony Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1955135/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
** Tags added: impish jammy ** Changed in: xorg (Ubuntu) Status: Invalid => Confirmed -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in gdm3 package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+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 1956300] [NEW] graphics
Public bug reported: dont no ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1052.54-oem 5.10.76 Uname: Linux 5.10.0-1052-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 4 14:02:03 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a20] InstallationDate: Installed on 2021-08-12 (145 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Latitude 5420 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1052-oem root=UUID=5c089419-1808-46cd-9e10-ebaba3debd73 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/22/2021 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.1 dmi.board.name: 03P5X2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.1:bd11/22/2021:br1.14:svnDellInc.:pnLatitude5420:pvr:sku0A20:rvnDellInc.:rn03P5X2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5420 dmi.product.sku: 0A20 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1956300 Title: graphics Status in xorg package in Ubuntu: New Bug description: dont no ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1052.54-oem 5.10.76 Uname: Linux 5.10.0-1052-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 4 14:02:03 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a20] InstallationDate: Installed on 2021-08-12 (145 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Latitude 5420 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1052-oem root=UUID=5c089419-1808-46cd-9e10-ebaba3debd73 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/22/2021 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.1 dmi.board.name: 03P5X2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.1:bd11/22/2021:br1.14:svnDellInc.:pnLatitude5420:pvr:sku0A20:rvnDellInc.:rn03P5X2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5420 dmi.product.sku: 0A20 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel:
[Touch-packages] [Bug 1955049] Re: amdgpu kernel errors
*** This bug is a duplicate of bug 1954956 *** https://bugs.launchpad.net/bugs/1954956 You are using an unsupported kernel. Please start by trying an official Ubuntu kernel or a newer mainline kernel. ** Summary changed: - Xorg crash + amdgpu kernel errors ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Invalid ** This bug has been marked a duplicate of bug 1954956 [amdgpu] System crash -- 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/1955049 Title: amdgpu kernel errors Status in linux package in Ubuntu: Invalid Bug description: System crashes about 3 times a day; no appearant relation to application or process or triggering situation. Happens constantly. Random time between incidents normally several hours. This is a problem for month now. Description: Ubuntu 21.04 Release: 21.04 GUI crashed: Operation ceses, monitor becomes dark. In this case the monitor shows a static picture after some seconds of darkness. Remote access via SSH is possible up to some extend. Expected: GUI does not crash. dmesg says: [ 2284.101478] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! [ 2289.993462] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=132409, emitted seq=132410 [ 2289.993826] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0 [ 2289.994175] amdgpu :0a:00.0: amdgpu: GPU reset begin! [ 2290.169982] [drm] free PSP TMR buffer [ 2290.198611] amdgpu :0a:00.0: amdgpu: MODE2 reset [ 2290.198656] amdgpu :0a:00.0: amdgpu: GPU reset succeeded, trying to resume [ 2290.198943] [drm] PCIE GART of 1024M enabled. [ 2290.198945] [drm] PTB located at 0x00F40090 [ 2290.199115] [drm] PSP is resuming... [ 2290.218996] [drm] reserve 0x40 from 0xf45700 for PSP TMR [ 2290.262318] amdgpu :0a:00.0: amdgpu: RAS: optional ras ta ucode is not available [ 2290.266897] amdgpu :0a:00.0: amdgpu: RAP: optional rap ta ucode is not available [ 2290.266899] amdgpu :0a:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [ 2290.468265] [drm] kiq ring mec 2 pipe 1 q 0 [ 2290.602777] [drm] VCN decode and encode initialized successfully(under SPG Mode). [ 2290.602784] amdgpu :0a:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0 [ 2290.602787] amdgpu :0a:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [ 2290.602788] amdgpu :0a:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [ 2290.602790] amdgpu :0a:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 [ 2290.602791] amdgpu :0a:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 [ 2290.602792] amdgpu :0a:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 [ 2290.602793] amdgpu :0a:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 [ 2290.602793] amdgpu :0a:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 [ 2290.602795] amdgpu :0a:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 [ 2290.602796] amdgpu :0a:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 [ 2290.602797] amdgpu :0a:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1 [ 2290.602798] amdgpu :0a:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1 [ 2290.602798] amdgpu :0a:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1 [ 2290.602799] amdgpu :0a:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1 [ 2290.602800] amdgpu :0a:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1 [ 2290.609397] amdgpu :0a:00.0: amdgpu: recover vram bo from shadow start [ 2290.609400] amdgpu :0a:00.0: amdgpu: recover vram bo from shadow done [ 2290.609464] amdgpu :0a:00.0: amdgpu: GPU reset(1) succeeded! [ 2290.609926] kfd kfd: amdgpu: Allocated 3969056 bytes on gart [ 2290.609979] kfd kfd: amdgpu: error getting iommu info. is the iommu enabled? [ 2290.609981] kfd kfd: amdgpu: Error initializing iommuv2 [ 2290.610175] kfd kfd: amdgpu: device 1002:15d8 NOT added due to errors [ 2317.591058] rfkill: input handler enabled [ 2412.382743] show_signal_msg: 29 callbacks suppressed [ 2412.382746] apport-gtk[16593]: segfault at 18 ip 7f7f7e90e194 sp 7fff2ca56790 error 4 in libgtk-3.so.0.2404.21[7f7f7e805000+385000] [ 2412.382753] Code: c4 08 5b 5d c3 90 f3 0f 1e fa 48 8b 7f 10 48 85 ff 74 0b e9 ce c6 ff ff 66 0f 1f 44 00 00 48 83 ec 08 48 89 d7 e8 8c 3c 17 00 <48> 8b 40 18 48 8b 78 10 e8 df 03 09 00 48 83 c4 08 48 89 c7 e9 a3 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu65.4
[Touch-packages] [Bug 1944711] Re: restarting systemd-logind loses all existing sessions
Thank you Michael for the verification. I can confirm this is working as expected as of systemd 245.4-4ubuntu3.14 from (focal-proposed) slyon@ff:~$ dpkg -l | grep systemd [...] ii systemd245.4-4ubuntu3.14 amd64 slyon@ff:~$ loginctl list-sessions SESSION UID USER SEAT TTY c2 1001 slyon pts/1 1 sessions listed. root@ff:~# systemctl restart systemd-logind slyon@ff:~$ loginctl list-sessions SESSION UID USER SEAT TTY c2 1001 slyon pts/1 1 sessions listed. The networking after resume issue indeed seems to be unrelated. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1944711 Title: restarting systemd-logind loses all existing sessions Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [impact] restarting the systemd-logind service loses all existing sessions [test case] ubuntu@test-f:~$ loginctl list-sessions SESSION UID USER SEAT TTY 3789 1000 ubuntu pts/0 1 sessions listed. ubuntu@test-f:~$ journalctl -b -u systemd-logind -- Logs begin at Thu 2021-09-23 11:11:57 UTC, end at Thu 2021-09-23 11:22:55 UTC. -- Sep 23 11:22:51 test-f systemd[1]: Starting Login Service... Sep 23 11:22:51 test-f systemd-logind[198]: New seat seat0. Sep 23 11:22:51 test-f systemd[1]: Started Login Service. Sep 23 11:22:52 test-f systemd-logind[198]: New session 3789 of user ubuntu. ubuntu@test-f:~$ sudo systemctl restart systemd-logind ubuntu@test-f:~$ journalctl -b -u systemd-logind -- Logs begin at Thu 2021-09-23 11:11:57 UTC, end at Thu 2021-09-23 11:23:07 UTC. -- Sep 23 11:22:51 test-f systemd[1]: Starting Login Service... Sep 23 11:22:51 test-f systemd-logind[198]: New seat seat0. Sep 23 11:22:51 test-f systemd[1]: Started Login Service. Sep 23 11:22:52 test-f systemd-logind[198]: New session 3789 of user ubuntu. Sep 23 11:23:07 test-f systemd[1]: Stopping Login Service... Sep 23 11:23:07 test-f systemd[1]: systemd-logind.service: Succeeded. Sep 23 11:23:07 test-f systemd[1]: Stopped Login Service. Sep 23 11:23:07 test-f systemd[1]: Starting Login Service... Sep 23 11:23:07 test-f systemd-logind[469]: Failed to add user by file name 1000, ignoring: Invalid argument Sep 23 11:23:07 test-f systemd-logind[469]: User enumeration failed: Invalid argument Sep 23 11:23:07 test-f systemd-logind[469]: User of session 3789 not known. Sep 23 11:23:07 test-f systemd-logind[469]: Session enumeration failed: No such file or directory Sep 23 11:23:07 test-f systemd-logind[469]: New seat seat0. Sep 23 11:23:07 test-f systemd[1]: Started Login Service. ubuntu@test-f:~$ loginctl list-sessions No sessions. [regression potential] any regression would likely occur during a systemd-logind restart, likely causing a loss of current login sessions. [scope] this is needed only in f this is fixed upstream by commit ac4e03d45bcf4ad2e570cabdb218e9bac003cc80 which is included in v246, so this is fixed in h and later already. in b, the function used to parse the /run/systemd/users/* files allows either usernames or uids, so this bug does not exist there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1944711/+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 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
Oh it's just a confusingly redundant setting. You can find it in: Settings > Date & Time > Time Format = AM / PM ** Package changed: gnome-shell (Ubuntu) => gsettings-desktop-schemas (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/issues #30 https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/issues/30 ** Also affects: gsettings-desktop-schemas via https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/issues/30 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: Unknown Status in gsettings-desktop-schemas package in Ubuntu: Confirmed Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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 1956102] Re: Time for the US is shown in 24h format. It should be 12h with AM/PM
** No longer affects: ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1956102 Title: Time for the US is shown in 24h format. It should be 12h with AM/PM Status in GSettings Desktop Schemas: Unknown Status in gsettings-desktop-schemas package in Ubuntu: Confirmed Bug description: Source- https://time.gov/ To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1956102/+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
