[Touch-packages] [Bug 1905373] [NEW] Xorg freeze when monitor turned off and on
Public bug reported: I have two monitors on a Radeon R9 380X, one is connected to HDMI, the other is connected to DVI. When I turn off the left monitor, nothing happens. Only when you turn it on again does the entire picture move to the right monitor and Ubuntu does not react to keyboard or mouse input. The problem only occurs once I've logged in. Even if I've locked the screen again. Hard reboot is required. == Ubuntu: Description:Ubuntu 20.04.1 LTS Release:20.04 xorg: Installiert: 1:7.7+19ubuntu14 Installationskandidat: 1:7.7+19ubuntu14 Versionstabelle: *** 1:7.7+19ubuntu14 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 24 09:44:57 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tonga XT / Amethyst XT [Radeon R9 380X / R9 M295X] [1002:6938] (rev f1) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon R9 380X Nitro 4G D5 [174b:e308] InstallationDate: Installed on 2019-09-15 (435 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: MSI MS-7978 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-54-generic root=UUID=876f1728-1e76-4498-a415-504e1078f473 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.70 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.70:bd07/24/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7978 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu ** Attachment added: "problem looks like this" https://bugs.launchpad.net/bugs/1905373/+attachment/5437443/+files/cropped_monitors -- 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/1905373 Title: Xorg freeze when monitor turned off and on Status in xorg package in Ubuntu: New Bug description: I have two monitors on a Radeon R9 380X, one is connected to HDMI, the other is connected to DVI. When I turn off the left monitor, nothing happens. Only when you turn it on again does the entire picture move to the right monitor and Ubuntu does not react to keyboard or mouse input. The problem only occurs once I've logged in. Even if I've locked the screen again. Hard reboot is required. == Ubuntu: Description: Ubuntu 20.04.1 LTS Release: 20.04 xorg: Installiert: 1:7.7+19ubuntu14 Installationskandidat: 1:7.7+19ubuntu14 Versionstabelle: *** 1:7.7+19ubuntu14 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
[Touch-packages] [Bug 1905373] Re: Xorg freeze when monitor turned off and on
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. -- 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/1905373 Title: [amdgpu] Screen freeze when monitor turned off and on Status in Ubuntu: Incomplete Bug description: I have two monitors on a Radeon R9 380X, one is connected to HDMI, the other is connected to DVI. When I turn off the left monitor, nothing happens. Only when you turn it on again does the entire picture move to the right monitor and Ubuntu does not react to keyboard or mouse input. The problem only occurs once I've logged in. Even if I've locked the screen again. Hard reboot is required. == Ubuntu: Description: Ubuntu 20.04.1 LTS Release: 20.04 xorg: Installiert: 1:7.7+19ubuntu14 Installationskandidat: 1:7.7+19ubuntu14 Versionstabelle: *** 1:7.7+19ubuntu14 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 24 09:44:57 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tonga XT / Amethyst XT [Radeon R9 380X / R9 M295X] [1002:6938] (rev f1) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon R9 380X Nitro 4G D5 [174b:e308] InstallationDate: Installed on 2019-09-15 (435 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: MSI MS-7978 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-54-generic root=UUID=876f1728-1e76-4498-a415-504e1078f473 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.70 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.70:bd07/24/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7978 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1905373/+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 1905373] Re: Xorg freeze when monitor turned off and on
If the above steps fail then please: 1. Reproduce the freeze again. 2. Wait 10 seconds. 3. Reboot. 4. Open a terminal and run: journalctl -b-1 > prevboot.txt 5. Attach the resulting text file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Xorg freeze when monitor turned off and on + Screen freeze when monitor turned off and on ** Tags added: amdgpu ** Summary changed: - Screen freeze when monitor turned off and on + [amdgpu] Screen freeze when monitor turned off and on -- 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/1905373 Title: [amdgpu] Screen freeze when monitor turned off and on Status in Ubuntu: Incomplete Bug description: I have two monitors on a Radeon R9 380X, one is connected to HDMI, the other is connected to DVI. When I turn off the left monitor, nothing happens. Only when you turn it on again does the entire picture move to the right monitor and Ubuntu does not react to keyboard or mouse input. The problem only occurs once I've logged in. Even if I've locked the screen again. Hard reboot is required. == Ubuntu: Description: Ubuntu 20.04.1 LTS Release: 20.04 xorg: Installiert: 1:7.7+19ubuntu14 Installationskandidat: 1:7.7+19ubuntu14 Versionstabelle: *** 1:7.7+19ubuntu14 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 24 09:44:57 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tonga XT / Amethyst XT [Radeon R9 380X / R9 M295X] [1002:6938] (rev f1) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon R9 380X Nitro 4G D5 [174b:e308] InstallationDate: Installed on 2019-09-15 (435 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: MSI MS-7978 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-54-generic root=UUID=876f1728-1e76-4498-a415-504e1078f473 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.70 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.70:bd07/24/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7978 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1905373/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
PulseAudio 14.0 is out [1], so hopefully there's no other blocker to merge missing features: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/227 1: https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/14.0/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1903903] Re: [MSI MS-17C5] "Analog Stereo Duplex" profile keeps disappearing
Small correction: as a workaround, removal of ~/.config/pulse is not needed, a restart of the PulseAudio (pulseaudio -k) is sufficient. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1903903 Title: [MSI MS-17C5] "Analog Stereo Duplex" profile keeps disappearing Status in pulseaudio package in Ubuntu: New Bug description: After every reboot, the profile named "Analog Stereo Duplex" keeps disappearing on my laptop; only "Analog Stereo Input" and "Analog Stereo Output" are present. Without "duplex", I cannot use both the built-in microphone and the speakers/headphones at the same time. A workaround I found is to remove the user's configuration for pulseaudio and restart it: rm -rf .config/pulse pulseaudio -k This brings the "Analog Stereo Duplex" profile back until the next reboot. This problem started after an upgrade from Ubuntu 20.04 to 20.10. I made a screencast of this: https://youtu.be/Vlz5471EYVQ The laptop is MSI WE73-8SK. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-output-speaker.conf] ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Nov 11 10:50:54 2020 InstallationDate: Installed on 2019-01-08 (673 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-29 (13 days ago) dmi.bios.date: 05/20/2019 dmi.bios.release: 1.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C5IWS.10F dmi.board.asset.tag: Default string dmi.board.name: MS-17C5 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C5IWS.10F:bd05/20/2019:br1.15:svnMicro-StarInternationalCo.,Ltd.:pnWE738SK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: WE dmi.product.name: WE73 8SK dmi.product.sku: 17C5.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1903903/+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 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties
The autopkgtest failure was flakyness, it successed after a retry -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1899262 Title: Broken dbus GetAll message to wpa supplicant interface properties Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Bionic: Fix Committed Bug description: * Impact One of the distro patch is incorrect and create issues when trying to query dbus properties * Test Case $ sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1/Interfaces/1 org.freedesktop.DBus.Properties.GetAll string:fi.w1.wpa_supplicant1.Interface shouldn't error out (the /1 reflect the interface number and could be a different value, check with d-feet if needed) * Regression potential The fixes is in the dbus interface, check that communication with desktop clients (indicator, applet, settings) still works correctly, returning expected informations on the signal, etc - dbus-send is able to read the properties of interface using GetAll. Those information include interface name, status, encryption method, etc. The regression was introduced when someone try to have the Station attribute supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+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 1903222] Re: Systemd throws error with unknown capabilities
*** This bug is a duplicate of bug 1885755 *** https://bugs.launchpad.net/bugs/1885755 This is a duplicate and SRU request of LP: #1891527, marking as such. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1903222 Title: Systemd throws error with unknown capabilities Status in HWE Next: New Status in systemd package in Ubuntu: New Bug description: The Kernel v5.8 introduces a new capability (CAP_BPF), which is not supported by Systemd v237 as shipped in bionic. Systemd added a patch to handle unknown capabilities that makes it so it does not error with Kernels with new capabilities: https://github.com/systemd/systemd/pull/16420 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1903222/+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 1903222] Re: Systemd throws error with unknown capabilities
*** This bug is a duplicate of bug 1885755 *** https://bugs.launchpad.net/bugs/1885755 I mean duplicate of LP: #1885755. ** This bug has been marked a duplicate of bug 1885755 test-cap-list fails with Linux 5.8 due to new capabilities -- 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/1903222 Title: Systemd throws error with unknown capabilities Status in HWE Next: New Status in systemd package in Ubuntu: New Bug description: The Kernel v5.8 introduces a new capability (CAP_BPF), which is not supported by Systemd v237 as shipped in bionic. Systemd added a patch to handle unknown capabilities that makes it so it does not error with Kernels with new capabilities: https://github.com/systemd/systemd/pull/16420 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1903222/+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 1885755] Re: test-cap-list fails with Linux 5.8 due to new capabilities
SRU to Bionic is requested in LP: #1903222. ** Also affects: systemd (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Groovy) Status: New => Fix Released ** Changed in: systemd (Ubuntu) Status: Confirmed => 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/1885755 Title: test-cap-list fails with Linux 5.8 due to new capabilities Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Focal: New Status in systemd source package in Groovy: Fix Released Bug description: == test-cap-list === Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at src/test/test-cap-list.c:60, function test_capability_set_one(). Aborting. FAIL: test-cap-list (code: 134) This seems to be a result of new capabilities added in 5.8. systemd builds an array to convert capability numbers to strings, and these new capabilities are not in its array, so the test bombs out when trying to look up the string for a capability it doesn't know about. Rebuilding systemd using headers from Linux 5.8 should fix this issue. Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/s/systemd/20200630_154532_b7979@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/arm64/s/systemd/20200630_155538_0c63d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/ppc64el/s/systemd/20200630_162720_b3e1b@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/s390x/s/systemd/20200630_140417_c5bdb@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885755/+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 1885755] Re: test-cap-list fails with Linux 5.8 due to new capabilities
Fixed in 246 and in upstream's v245.7. -- 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/1885755 Title: test-cap-list fails with Linux 5.8 due to new capabilities Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Focal: New Status in systemd source package in Groovy: Fix Released Bug description: == test-cap-list === Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at src/test/test-cap-list.c:60, function test_capability_set_one(). Aborting. FAIL: test-cap-list (code: 134) This seems to be a result of new capabilities added in 5.8. systemd builds an array to convert capability numbers to strings, and these new capabilities are not in its array, so the test bombs out when trying to look up the string for a capability it doesn't know about. Rebuilding systemd using headers from Linux 5.8 should fix this issue. Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/s/systemd/20200630_154532_b7979@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/arm64/s/systemd/20200630_155538_0c63d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/ppc64el/s/systemd/20200630_162720_b3e1b@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/s390x/s/systemd/20200630_140417_c5bdb@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885755/+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 1885755] Re: test-cap-list fails with Linux 5.8 due to new capabilities
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Bionic) 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/1885755 Title: test-cap-list fails with Linux 5.8 due to new capabilities Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Confirmed Status in systemd source package in Focal: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: == test-cap-list === Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at src/test/test-cap-list.c:60, function test_capability_set_one(). Aborting. FAIL: test-cap-list (code: 134) This seems to be a result of new capabilities added in 5.8. systemd builds an array to convert capability numbers to strings, and these new capabilities are not in its array, so the test bombs out when trying to look up the string for a capability it doesn't know about. Rebuilding systemd using headers from Linux 5.8 should fix this issue. Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/s/systemd/20200630_154532_b7979@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/arm64/s/systemd/20200630_155538_0c63d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/ppc64el/s/systemd/20200630_162720_b3e1b@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/s390x/s/systemd/20200630_140417_c5bdb@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885755/+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 1885755] Re: test-cap-list fails with Linux 5.8 due to new capabilities
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Focal) 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/1885755 Title: test-cap-list fails with Linux 5.8 due to new capabilities Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Confirmed Status in systemd source package in Focal: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: == test-cap-list === Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at src/test/test-cap-list.c:60, function test_capability_set_one(). Aborting. FAIL: test-cap-list (code: 134) This seems to be a result of new capabilities added in 5.8. systemd builds an array to convert capability numbers to strings, and these new capabilities are not in its array, so the test bombs out when trying to look up the string for a capability it doesn't know about. Rebuilding systemd using headers from Linux 5.8 should fix this issue. Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/s/systemd/20200630_154532_b7979@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/arm64/s/systemd/20200630_155538_0c63d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/ppc64el/s/systemd/20200630_162720_b3e1b@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/s390x/s/systemd/20200630_140417_c5bdb@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885755/+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 1885755] Re: test-cap-list fails with Linux 5.8 due to new capabilities
Can we also push the fix to Xenial? People are running Xenial LXCs on Focal hosts with 5.8 kernels. -- 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/1885755 Title: test-cap-list fails with Linux 5.8 due to new capabilities Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Confirmed Status in systemd source package in Focal: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: == test-cap-list === Assertion 'capability_set_to_string_alloc(c, &t1) == 0' failed at src/test/test-cap-list.c:60, function test_capability_set_one(). Aborting. FAIL: test-cap-list (code: 134) This seems to be a result of new capabilities added in 5.8. systemd builds an array to convert capability numbers to strings, and these new capabilities are not in its array, so the test bombs out when trying to look up the string for a capability it doesn't know about. Rebuilding systemd using headers from Linux 5.8 should fix this issue. Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/s/systemd/20200630_154532_b7979@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/arm64/s/systemd/20200630_155538_0c63d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/ppc64el/s/systemd/20200630_162720_b3e1b@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/s390x/s/systemd/20200630_140417_c5bdb@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885755/+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 1876495] Re: bash-completion incorrectly shows source package names for APT
** Changed in: apt (Ubuntu) Status: In Progress => Fix Committed ** Also affects: apt (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: bash-completion (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Hirsute) Importance: Low Status: Fix Committed ** Also affects: bash-completion (Ubuntu Hirsute) Importance: Low Status: Invalid ** Also affects: apt (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: bash-completion (Ubuntu Focal) Importance: Undecided Status: New -- 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/1876495 Title: bash-completion incorrectly shows source package names for APT Status in apt package in Ubuntu: Fix Committed Status in bash-completion package in Ubuntu: Invalid Status in apt source package in Focal: New Status in bash-completion source package in Focal: New Status in apt source package in Groovy: New Status in bash-completion source package in Groovy: New Status in apt source package in Hirsute: Fix Committed Status in bash-completion source package in Hirsute: Invalid Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Open terminal, enter one of the commands below 2a. apt install brisk 2b. apt source brisk-menu 2c. apt-get install brisk 2d. apt-get source brisk-menu 2e. apt-cache policy brisk Expected results: * The bash-completion should not lead to package name as there are no binary packages named with starting part "brisk" (see https://packages.ubuntu.com/search?suite=all&searchon=names&keywords=brisk ) Actual results: * all commands below get completed to the name of source package - in this example named "brisk-menu" (see https://packages.ubuntu.com/search?suite=all§ion=all&arch=any&keywords=brisk&searchon=sourcenames). This is absolutely unexpected, as user can not really install this package in binary form. ProblemType: Bug DistroRelease: Ubuntu Kylin 20.04 Package: bash-completion 1:2.10-1ubuntu1 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30 Uname: Linux 5.4.0-28-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat May 2 20:35:48 2020 Dependencies: InstallationDate: Installed on 2020-04-22 (9 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200422) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1876495/+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 1902244] Re: Backport packages for 20.04.1 HWE stack
** Also affects: libglvnd (Ubuntu) Importance: Undecided Status: New ** Changed in: libglvnd (Ubuntu) Status: New => Invalid ** Description changed: [Impact] These are needed for 20.04.1 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-11: a new package, no regression potential on it's own libclc: just a rebuild against the new llvm + libglvnd: mostly just EGL headers sync from Khronos, needed by mesa + mesa: a new major release, but we'll pull the final stable release of 20.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release xorg drivers: modest updates, if any ** Changed in: libglvnd (Ubuntu Focal) Status: New => In Progress ** Changed in: libglvnd (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1902244 Title: Backport packages for 20.04.1 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libglvnd package in Ubuntu: Invalid Status in llvm-toolchain-11 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libclc source package in Focal: Fix Committed Status in libdrm source package in Focal: Fix Committed Status in libglvnd source package in Focal: In Progress Status in llvm-toolchain-11 source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Status in xorg-server source package in Focal: Confirmed Bug description: [Impact] These are needed for 20.04.1 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-11: a new package, no regression potential on it's own libclc: just a rebuild against the new llvm libglvnd: mostly just EGL headers sync from Khronos, needed by mesa mesa: a new major release, but we'll pull the final stable release of 20.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release xorg drivers: modest updates, if any To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1905166] Re: systemd-shutdown cannot detach DM
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/1905166 Title: systemd-shutdown cannot detach DM Status in systemd package in Ubuntu: Confirmed Bug description: when powering down the system systemd cannot unmount / systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy systemd-shutdown[1]: Failed to finalize DM devices, ignoring reboot: Power down as a result at each startup the filesystem is checked: Press Ctrl+C to cancel all filesystem checks in progress If systemd cannot unmount / that might not be a problem but it should be less noisy and not result in a filesystem check after each reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 11:40:05 2020 MachineType: Dell Inc. Latitude 7410 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0M5G57 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd10/11/2020:svnDellInc.:pnLatitude7410:pvr:rvnDellInc.:rn0M5G57:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7410 dmi.product.sku: 09CD dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+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 1655584] Re: systemd-udevd busyloops when nvidia kernel module fails to load
I might be experiencing this problem too. I use KVM/QEMU and load vfio- pci driver in place of NVidia driver. nvidia-driver-455 here. -- 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/1655584 Title: systemd-udevd busyloops when nvidia kernel module fails to load Status in systemd package in Ubuntu: Confirmed Bug description: On a machine where nvidia-367 is installed, but the driver won't attach (due to the nvidia card being older and requiring legacy drivers), systemd-udevd repeatedly attempts to load it anyway, causing high CPU and memory usage. I observed the systemd-udevd process at 98% CPU usage and 2.5G RSS reported by top(1); restarting the service reduces resource usage momentarily, but it appears to be climbing back up (I suspect the number of events is growing). Workaround is of course installing the correct driver package, but udevd really ought not behave like this if something fails to load. Some journal entries for systemd-udevd.service: Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Jan 11 11:22:11 systemd-udevd[11651]: Process '/usr/bin/nvidia-smi' failed with exit code 9. Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Jan 11 11:22:12 systemd-udevd[11651]: Process '/usr/bin/nvidia-smi' failed with exit code 9. Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. dmesg shows repeated failures for loading the nvidia module: [1675406.587926] NVRM: The NVIDIA GeForce 9300 GE GPU installed in this system is NVRM: supported through the NVIDIA 340.xx Legacy drivers. Please NVRM: visit http://www.nvidia.com/object/unix.html for more NVRM: information. The 367.57 NVIDIA driver will ignore NVRM: this GPU. Continuing probe... [1675406.587936] NVRM: No NVIDIA graphics adapter found! [1675406.588078] NVRM: NVIDIA init module failed! Release information: # lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 # apt policy systemd udev systemd: Installed: 229-4ubuntu13 Candidate: 229-4ubuntu13 Version table: *** 229-4ubuntu13 500 500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu10 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 229-4ubuntu4 500 500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive xenial/main amd64 Packages udev: Installed: 229-4ubuntu13 Candidate: 229-4ubuntu13 Version table: *** 229-4ubuntu13 500 500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu10 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 229-4ubuntu4 500 500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1655584/+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 1905167] Re: htop shows 100% usage of systemd-udevd
Might be this bug: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1655584 I use KVM/QEMU and load vfio-pci driver in place of NVidia driver. -- 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/1905167 Title: htop shows 100% usage of systemd-udevd Status in nvidia-graphics-drivers-455 package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: I'm attaching a perf profile. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65 Uname: Linux 5.4.0-54-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Nov 22 13:57:47 2020 InstallationDate: Installed on 2020-02-08 (287 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire A515-51G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-lowlatency root=/dev/mapper/vgubuntu-root ro quiet splash resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality intel_iommu=on iommu=pt vfio-pci.ids=10de:1d10 vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/dnscrypt-proxy.service → /etc/systemd/system/dnscrypt-proxy.service.d/override.conf [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-10-23 (29 days ago) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742 mtime.conffile..etc.systemd.sleep.conf: 2020-09-26T18:33:31.018002 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1905167/+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 1905167] Re: htop shows 100% usage of systemd-udevd
Is anyone triaging these bugs, like, if you can't fix all of them at least acknowledge them. I'm not talking only for nvidia package bugs but for many others also. Somehow the Firefox bugzilla triage works better IMO. -- 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/1905167 Title: htop shows 100% usage of systemd-udevd Status in nvidia-graphics-drivers-455 package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: I'm attaching a perf profile. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65 Uname: Linux 5.4.0-54-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Nov 22 13:57:47 2020 InstallationDate: Installed on 2020-02-08 (287 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Acer Aspire A515-51G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-lowlatency root=/dev/mapper/vgubuntu-root ro quiet splash resume=UUID=f0e63db4-d3af-4977-a82a-5a46a3c677ae lockdown=confidentiality intel_iommu=on iommu=pt vfio-pci.ids=10de:1d10 vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/dnscrypt-proxy.service → /etc/systemd/system/dnscrypt-proxy.service.d/override.conf [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to focal on 2020-10-23 (29 days ago) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742 mtime.conffile..etc.systemd.sleep.conf: 2020-09-26T18:33:31.018002 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-455/+bug/1905167/+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 1905245] Re: "Failed to parse bus message: Invalid argument" with Linux 5.8
** Tags added: fr-963 -- 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/1905245 Title: "Failed to parse bus message: Invalid argument" with Linux 5.8 Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Focal: In Progress Bug description: [impact] newer kernels introduced a new capability, and existing systemd doesn't have the name mapping for the new cap (since the mapping table is generated at systemd compile time), so it fails when trying to map the capability to a user-facing name, which causes failure when running commands like 'systemctl show' [test case] install a focal system, and install the 5.8 (or newer) kernel, e.g. from linux-generic-hwe-20.04-edge, and reboot into the new kernel. Find any service that does not specify its CapabilityBoundingSet; e.g. 'apparmor', and run systemctl show on it: ubuntu@lp1905245-f:~$ systemctl show -p CapabilityBoundingSet apparmor Failed to parse bus message: Invalid argument the command should correctly show the value, e.g.: $ systemctl show -p CapabilityBoundingSet apparmor CapabilityBoundingSet=cap_chown cap_dac_override ...etc... [regression potential] a regression would likely occur while systemd is parsing or printing or otherwise handling kernel capabilities. A regression could happen when running systemd commands, such as systemctl, or when pid1 is managing services. [scope] this is needed only in focal (and possibly bionic). This is fixed upstream by PR 16424: https://github.com/systemd/systemd/pull/16424 which was first included in v246, so this is already fixed in groovy and later. this was introduced externally from systemd, with the new capability in the kernel, so this fix technically is needed in x/b/f. However, x is unlikely to get a new kernel capability during the rest of its life cycle. For b, unless a kernel is added that includes a new capability, this patch is not needed. [original description] When I run `systemctl show myservice.service`, I get the following error message: Failed to parse bus message: Invalid argument systemd version: 245.4-4ubuntu3.3 linux version: 5.8.0-29-generic #31~20.04.1-Ubuntu (From linux-generic-hwe-20.04-edge) This is a bug that has been fixed in Debian. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964926 Please can we port the fix to the ubuntu 20.04 version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905245/+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 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties
** Tags removed: rls-bb-incoming rls-ff-incoming rls-gg-incoming rls-hh- incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1899262 Title: Broken dbus GetAll message to wpa supplicant interface properties Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Bionic: Fix Committed Bug description: * Impact One of the distro patch is incorrect and create issues when trying to query dbus properties * Test Case $ sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1/Interfaces/1 org.freedesktop.DBus.Properties.GetAll string:fi.w1.wpa_supplicant1.Interface shouldn't error out (the /1 reflect the interface number and could be a different value, check with d-feet if needed) * Regression potential The fixes is in the dbus interface, check that communication with desktop clients (indicator, applet, settings) still works correctly, returning expected informations on the signal, etc - dbus-send is able to read the properties of interface using GetAll. Those information include interface name, status, encryption method, etc. The regression was introduced when someone try to have the Station attribute supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+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 1901609] Re: signond causes qprocess crash
** Changed in: signon (Ubuntu Focal) Assignee: (unassigned) => Rik Mills (rikmills) ** Changed in: signon (Ubuntu Groovy) Assignee: (unassigned) => Rik Mills (rikmills) ** Changed in: signon (Ubuntu Hirsute) Assignee: (unassigned) => Rik Mills (rikmills) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: New Status in signon source package in Focal: New Status in signon source package in Groovy: New Status in signon source package in Hirsute: New Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+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 1905420] [NEW] package initramfs-tools 0.137ubuntu12 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: new bug report because the other ones are 5+ years old Ubuntu 20.10 on Raspberry Pi installed via PINN ProblemType: Package DistroRelease: Ubuntu 20.10 Package: initramfs-tools 0.137ubuntu12 ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14 Uname: Linux 5.8.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: arm64 CasperMD5CheckResult: skip Date: Tue Nov 24 09:19:05 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20201022 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: gnome-shell linux-image-5.8.0-1007-raspi linux-base RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: initramfs-tools Title: package initramfs-tools 0.137ubuntu12 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 groovy -- 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/1905420 Title: package initramfs-tools 0.137ubuntu12 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: new bug report because the other ones are 5+ years old Ubuntu 20.10 on Raspberry Pi installed via PINN ProblemType: Package DistroRelease: Ubuntu 20.10 Package: initramfs-tools 0.137ubuntu12 ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14 Uname: Linux 5.8.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: arm64 CasperMD5CheckResult: skip Date: Tue Nov 24 09:19:05 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20201022 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: gnome-shell linux-image-5.8.0-1007-raspi linux-base RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: initramfs-tools Title: package initramfs-tools 0.137ubuntu12 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1905420/+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 1905420] Re: package initramfs-tools 0.137ubuntu12 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1905420 Title: package initramfs-tools 0.137ubuntu12 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: new bug report because the other ones are 5+ years old Ubuntu 20.10 on Raspberry Pi installed via PINN ProblemType: Package DistroRelease: Ubuntu 20.10 Package: initramfs-tools 0.137ubuntu12 ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14 Uname: Linux 5.8.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: arm64 CasperMD5CheckResult: skip Date: Tue Nov 24 09:19:05 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20201022 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: gnome-shell linux-image-5.8.0-1007-raspi linux-base RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: initramfs-tools Title: package initramfs-tools 0.137ubuntu12 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1905420/+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 1888543] Re: hwclock: fails to set time on glibc 2.31
Verified on Groovy with 1:1.30.1-4ubuntu9.1: ubuntu@gg:~$ dpkg -l busybox-static | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--== ii busybox-static 1:1.30.1-4ubuntu9 amd64Standalone rescue shell with tons of builtin utilities ubuntu@gg:~$ sudo busybox hwclock -s hwclock: settimeofday: Invalid argument ubuntu@gg:~$ sudo apt -qq install busybox-static The following packages will be upgraded: busybox-static 1 upgraded, 0 newly installed, 0 to remove and 11 not upgraded. Need to get 915 kB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 64660 files and directories currently installed.) Preparing to unpack .../busybox-static_1%3a1.30.1-4ubuntu9.1_amd64.deb ... Unpacking busybox-static (1:1.30.1-4ubuntu9.1) over (1:1.30.1-4ubuntu9) ... Setting up busybox-static (1:1.30.1-4ubuntu9.1) ... Processing triggers for man-db (2.9.3-2) ... Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-29-generic ubuntu@gg:~$ sudo busybox hwclock -s ubuntu@gg:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1888543 Title: hwclock: fails to set time on glibc 2.31 Status in busybox package in Ubuntu: Fix Released Status in busybox source package in Focal: Fix Committed Status in busybox source package in Groovy: Fix Committed Status in busybox package in Debian: Confirmed Bug description: [Impact] * With glibc 2.31, hwclock from busybox is unable to set the system time due to the changes in settimeofday behavior. [Test Case] * Run: sudo busybox hwclock -s * It should succeed in the fixed version [Where problems could occur] * The fix calls the originally called glibc function twice, instead of passing both non-NULL parameters at once. If this compiles there should be no other issue. [Original Bug Text] With glibc 2.31, hwclock from busybox is unable to set the system time due to the changes in settimeofday behavior. The problem has been reported upstream in [1] which also contains a patch. hwclock from busybox is important as it's used on the Raspberry Pi to set the system time when an RTC is present. This bug applies to focal and groovy. [1] https://bugs.busybox.net/show_bug.cgi?id=12756 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1888543/+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 1888543] Re: hwclock: fails to set time on glibc 2.31
Verified on Focal with 1:1.30.1-4ubuntu6.3: ubuntu@ff:~$ dpkg -l busybox-static | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii busybox-static 1:1.30.1-4ubuntu6.2 amd64Standalone rescue shell with tons of builtin utilities ubuntu@ff:~$ sudo busybox hwclock -s hwclock: settimeofday: Invalid argument ubuntu@ff:~$ sudo apt install busybox-static Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: busybox-static 1 upgraded, 0 newly installed, 0 to remove and 15 not upgraded. Need to get 949 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 busybox-static amd64 1:1.30.1-4ubuntu6.3 [949 kB] Fetched 949 kB in 1s (1849 kB/s) (Reading database ... 63419 files and directories currently installed.) Preparing to unpack .../busybox-static_1%3a1.30.1-4ubuntu6.3_amd64.deb ... Unpacking busybox-static (1:1.30.1-4ubuntu6.3) over (1:1.30.1-4ubuntu6.2) ... Setting up busybox-static (1:1.30.1-4ubuntu6.3) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for initramfs-tools (0.136ubuntu6.3) ... update-initramfs: Generating /boot/initrd.img-5.4.0-54-generic ubuntu@ff:~$ sudo busybox hwclock -s ubuntu@ff:~$ ** Tags removed: verification-needed verification-needed-focal verification-needed-groovy ** Tags added: verification-done verification-done-focal verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1888543 Title: hwclock: fails to set time on glibc 2.31 Status in busybox package in Ubuntu: Fix Released Status in busybox source package in Focal: Fix Committed Status in busybox source package in Groovy: Fix Committed Status in busybox package in Debian: Confirmed Bug description: [Impact] * With glibc 2.31, hwclock from busybox is unable to set the system time due to the changes in settimeofday behavior. [Test Case] * Run: sudo busybox hwclock -s * It should succeed in the fixed version [Where problems could occur] * The fix calls the originally called glibc function twice, instead of passing both non-NULL parameters at once. If this compiles there should be no other issue. [Original Bug Text] With glibc 2.31, hwclock from busybox is unable to set the system time due to the changes in settimeofday behavior. The problem has been reported upstream in [1] which also contains a patch. hwclock from busybox is important as it's used on the Raspberry Pi to set the system time when an RTC is present. This bug applies to focal and groovy. [1] https://bugs.busybox.net/show_bug.cgi?id=12756 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1888543/+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 1854314] Re: Legacy directory /var/run in /lib/systemd/system/dbus.socket
Unresolved as of this date in Ubuntu 20.04/Mint 20. Regression: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Manual fix still necessary to remove /var in: /lib/systemd/system/dbus.socket: [Unit] Description=D-Bus System Message Bus Socket [Socket] ListenStream=/run/dbus/system_bus_socket -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1854314 Title: Legacy directory /var/run in /lib/systemd/system/dbus.socket Status in D-Bus: New Status in dbus package in Ubuntu: Fix Committed Status in dbus package in Debian: Fix Released Bug description: dbus/focal-proposed,now 1.12.16-2ubuntu1 amd64 Re(o)curring after each new upgrade of dbus, for quite some time and still... $ dmesg|grep accordingly systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Originally: $cat /lib/systemd/system/dbus.socket [Unit] Description=D-Bus System Message Bus Socket [Socket] ListenStream=/var/run/dbus/system_bus_socket After change: $cat /lib/systemd/system/dbus.socket [Unit] Description=D-Bus System Message Bus Socket [Socket] ListenStream=/run/dbus/system_bus_socket To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1854314/+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 1775392] Re: at-spi-bus-launcher makes Xorg crash when resuming from suspend
upstream bug can be found here https://bugzilla.gnome.org/show_bug.cgi?id=796512 ** Bug watch added: bugzilla.gnome.org/ #796512 https://bugzilla.gnome.org/show_bug.cgi?id=796512 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1775392 Title: at-spi-bus-launcher makes Xorg crash when resuming from suspend Status in at-spi2-core package in Ubuntu: Confirmed Bug description: If at-spi2-core is installed, when resuming from suspend messages like these are logged in systemd journal: at-spi-bus-launcher[31720]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" at-spi-bus-launcher[31720]: after 8065 requests (8065 known processed) with 0 events remaining. The number of requests vary, it can reach more than 15000. Depending on the number of requests, the Xorg server crashes with SIGBUS. Depending on the exact moment Xorg crashes, when lightdm manages to recover, it shows a login greeter, or worst case scenario, it can't recover, a black screen is shown and the desptop session doesn't start. It took me a long time to discover the cause. The visible symptom was: once in a while when resuming from suspend, I got a login greeter instead of an unlock greeter, or a black screen which forced me to power down. Investigating, I found out that whenever that happened, there was a Xorg core left behind. Looking at the journal messages before the crash, there was always that flood of at-spi2-core requests. So I uninstalled at-spi2-core and Xorg never crashed anymore. This is a quite severe bug, which makes it impossible to use at- spi2-core. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: at-spi2-core (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jun 6 09:10:12 2018 InstallationDate: Installed on 2018-04-28 (38 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: at-spi2-core UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392/+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 1890332] Re: apt update fails on unprivileged docker arm container due to inaccessible clock
** Summary changed: - apt update fails on docker arm container 20.04 + apt update fails on unprivileged docker arm container due to inaccessible clock ** Summary changed: - apt update fails on unprivileged docker arm container due to inaccessible clock + apt update fails on unprivileged docker arm container due to invalid gpg signature -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1890332 Title: apt update fails on unprivileged docker arm container due to invalid gpg signature Status in libseccomp package in Ubuntu: Confirmed Bug description: Running `apt update` in a ubuntu:20.04 docker container on raspberry pi fails with GPG errors. Expected behaviour: Successfully update the system through `apt update` What happens instead: `Err:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease At least one invalid signature was encountered.` Complete log: https://pastebin.com/sggGJcY1 How to reproduce: On a Raspberry Pi 3b or 4b (and maybe others ?), run the following command: `docker run ubuntu:latest apt update` or more specifically: `docker run arm32v7/ubuntu:20.04 apt update` More information: I can reproduce the bug on the following host systems: * Raspberry Pi 3b running HypriotOS * Raspberry Pi 4b running Raspbian GNU/Linux 10 (buster) The problem does not happens on the following host system: * Raspberry Pi 3b running Arch Linux Arm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1890332/+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 1890332] Re: apt update fails on unprivileged docker arm container due to invalid gpg signature
For the privileged/unprivileged issue mentioned in comment #6, these upstream comments appears to be pertinent, suggesting patches that may be worth backporting: https://github.com/moby/moby/issues/40734#issuecomment-614259072 https://github.com/moby/moby/issues/40734#issuecomment-680250761 As to the gpg errors in comment #8, I suspect those are unrelated. Those types of errors can crop up for a wide variety of reasons, including insufficient disk space, networking glitches, gpg problems, etc. all mostly unrelated to the package itself, so I would suggest looking to regular support channels for help there, for example see https://superuser.com/questions/1059346/apt-get-update-not-working- signing-verification-errors which suggests several solutions. If not, let us know. However, it's possible that the gpg error is hiding the earlier error, and potentially once its resolved the earlier error will come back. So I'll leave this issue open for now. ** Changed in: libseccomp (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1890332 Title: apt update fails on unprivileged docker arm container due to invalid gpg signature Status in libseccomp package in Ubuntu: Incomplete Bug description: Running `apt update` in a ubuntu:20.04 docker container on raspberry pi fails with GPG errors. Expected behaviour: Successfully update the system through `apt update` What happens instead: `Err:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease At least one invalid signature was encountered.` Complete log: https://pastebin.com/sggGJcY1 How to reproduce: On a Raspberry Pi 3b or 4b (and maybe others ?), run the following command: `docker run ubuntu:latest apt update` or more specifically: `docker run arm32v7/ubuntu:20.04 apt update` More information: I can reproduce the bug on the following host systems: * Raspberry Pi 3b running HypriotOS * Raspberry Pi 4b running Raspbian GNU/Linux 10 (buster) The problem does not happens on the following host system: * Raspberry Pi 3b running Arch Linux Arm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1890332/+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 1905088] Re: failed to install/upgrade: sshd_config: line 13: Bad configuration option
Hi Huy, The bug report appears to indicate some sort of syntax error in your /etc/ssh/sshd_config file. What's on line 13 of that file? SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 13: Bad configuration option: Include /etc/ssh/sshd_config: terminating, 1 bad configuration options If you're uncertain, then can you please attach your /etc/ssh/sshd_config for us to review? If that file contains any information that is security sensitive or personally identifying please change this bug report from "Public" to "Private". Thanks ahead of time. ** Summary changed: - package openssh-server 1:7.6p1-4ubuntu0.3 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 + failed to install/upgrade: sshd_config: line 13: Bad configuration option ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- 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/1905088 Title: failed to install/upgrade: sshd_config: line 13: Bad configuration option Status in openssh package in Ubuntu: Incomplete Bug description: Unpacking openssh-server (1:7.6p1-4ubuntu0.3) ... Setting up openssh-server (1:7.6p1-4ubuntu0.3) ... Job for ssh.service failed because the control process exited with error code. See "systemctl status ssh.service" and "journalctl -xe" for details. invoke-rc.d: initscript ssh, action "restart" failed. ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Fri 2020-11-20 22:09:42 CET; 20ms ago Process: 2918 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255) dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Processing triggers for ufw (0.36-0ubuntu0.18.04.1) ... Rules updated for profile 'OpenSSH' Firewall reloaded Processing triggers for ureadahead (0.100.0-21) ... ureadahead will be reprofiled on next reboot Processing triggers for systemd (237-3ubuntu10.43) ... Errors were encountered while processing: openssh-server ProblemType: Package DistroRelease: Ubuntu 18.04 Package: openssh-server 1:7.6p1-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 Date: Fri Nov 20 22:00:10 2020 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-12-27 (694 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 13: Bad configuration option: Include /etc/ssh/sshd_config: terminating, 1 bad configuration options SourcePackage: openssh Title: package openssh-server 1:7.6p1-4ubuntu0.3 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2020-06-16 (157 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1905088/+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 1905467] [NEW] [USB-Audio - Logitech Wireless Headset, playback] volume slider - sound audible only from 50% to 100% of the slider position
Public bug reported: After establishing connection with Logitech H800 Wireless Headset via USB Dongle, the system sound has to be set at the minimum of 50% of the slider for the sound in the headphones to be audible. Below the 50% volume slider position the sound is completely muted. Expected behaviour: Volume slider properly changing the sound level from 0% to 100% with the sound being muted at 0% and at maximum level at 100%. System: Ubuntu 20.04.1 LTS alsa-driver: k5.4.0-54-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: maciej 6716 F pulseaudio /dev/snd/pcmC3D0p: maciej 6716 F...m pulseaudio /dev/snd/controlC0: maciej 6716 F pulseaudio /dev/snd/controlC1: maciej 6716 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 24 21:29:56 2020 InstallationDate: Installed on 2020-06-22 (154 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: H600 [Wireless Headset] - Logitech Wireless Headset Symptom_PulseAudioLog: lis 22 12:33:32 y510p-ubuntu dbus-daemon[1500]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.31' (uid=125 pid=1940 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") lis 22 12:33:34 y510p-ubuntu pulseaudio[1940]: Failed to find a working profile. lis 22 12:33:34 y510p-ubuntu pulseaudio[1940]: Failed to load module "module-alsa-card" (argument: "device_id="2" name="pci-_01_00.1" card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. lis 24 09:41:02 y510p-ubuntu pulseaudio[1940]: Failed to create sink input: sink is suspended. lis 24 10:30:54 y510p-ubuntu pulseaudio[1940]: Failed to create sink input: sink is suspended. Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - Logitech Wireless Headset, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 1/30/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN47WW(V3.08) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 3193STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN47WW(V3.08):bd1/30/2015:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr3193STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1905467 Title: [USB-Audio - Logitech Wireless Headset, playback] volume slider - sound audible only from 50% to 100% of the slider position Status in alsa-driver package in Ubuntu: New Bug description: After establishing connection with Logitech H800 Wireless Headset via USB Dongle, the system sound has to be set at the minimum of 50% of the slider for the sound in the headphones to be audible. Below the 50% volume slider position the sound is completely muted. Expected behaviour: Volume slider properly changing the sound level from 0% to 100% with the sound being muted at 0% and at maximum level at 100%. System: Ubuntu 20.04.1 LTS alsa-driver: k5.4.0-54-generic. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: maciej 6716 F pulseaudio /dev/snd/pcmC3D0p: maciej 6716 F...m pulseaudio /dev/snd/controlC0: maciej 6716 F pulseaudio /dev/snd/controlC1: maciej 6716 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 24 21:29:56 2020 InstallationDate: Installed on 2020-06-22 (154 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageAr
[Touch-packages] [Bug 1905472] [NEW] Something starts dhcclient for every intrface on boot
Public bug reported: After upgrade frpm 18LTS to 20LTS I've lost the network. Network is managed by ifupdown Netplan is not installed Network manger is disabled (masked) Yet, at boot, SOMETHING starts dhclient for every network interface. This has disastrous results - dhcp request succeeds on physical interface that is a base for a vlan-based interface, causing real dhcp request on to fail on vlan interface. Expected behavior - dhclient starts only for interfaces marked as dhcp in /etc/network/interfaces . ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: isc-dhcp-client 4.4.1-2.1ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-29.31~20.04.1-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 25 00:07:45 2020 SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1905472 Title: Something starts dhcclient for every intrface on boot Status in isc-dhcp package in Ubuntu: New Bug description: After upgrade frpm 18LTS to 20LTS I've lost the network. Network is managed by ifupdown Netplan is not installed Network manger is disabled (masked) Yet, at boot, SOMETHING starts dhclient for every network interface. This has disastrous results - dhcp request succeeds on physical interface that is a base for a vlan-based interface, causing real dhcp request on to fail on vlan interface. Expected behavior - dhclient starts only for interfaces marked as dhcp in /etc/network/interfaces . ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: isc-dhcp-client 4.4.1-2.1ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-29.31~20.04.1-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 25 00:07:45 2020 SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1905472/+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 1892713] Re: whoopsie assert failure: free(): double free detected in tcache 2
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1892713 Title: whoopsie assert failure: free(): double free detected in tcache 2 Status in whoopsie package in Ubuntu: Confirmed Bug description: whoopsie failed to assert its dominance and threw a hissy fit crashing and taking the entire system with it. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: whoopsie 0.2.69ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AssertionMessage: free(): double free detected in tcache 2 CasperMD5CheckResult: skip CrashCounter: 1 Date: Mon Aug 24 07:07:00 2020 ExecutablePath: /usr/bin/whoopsie InstallationDate: Installed on 2020-05-23 (92 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcCmdline: /usr/bin/whoopsie -f ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) RelatedPackageVersions: apport-noui N/A Signal: 6 SourcePackage: whoopsie StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fa0d09bf285 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7fa0d09c15d0 "free(): double free detected in tcache 2") at malloc.c:5347 _int_free (av=0x7fa0d09f0b80 , p=0x55a170599750, have_lock=0) at malloc.c:4201 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: whoopsie assert failure: free(): double free detected in tcache 2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A mtime.conffile..etc.apport.crashdb.conf: 2020-07-14T21:26:34.707473 separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1892713/+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 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)
Bug 1892713 seems to be a duplicate of this one or will be fixed by the same changes that went into whoopsie 0.2.73. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1899100 Title: whoopsie assert failure: double free or corruption (fasttop) Status in whoopsie package in Ubuntu: Fix Released Bug description: [Impact] whoopsie is crashing somewhat regularly. There are a couple of crashes in the Error Tracker which look similar: https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98 As of yet (2020-11-22) neither crash is happening with whoopsie version 0.2.73. Apport popped up saying whoopsie had crashed (I assume during a previous crash report upload?) ProblemType: CrashDistroRelease: Ubuntu 20.10 Package: whoopsie 0.2.72 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AssertionMessage: double free or corruption (fasttop) CasperMD5CheckResult: skip CrashCounter: 1 Date: Fri Oct 9 08:08:56 2020 ExecutablePath: /usr/bin/whoopsie InstallationDate: Installed on 2019-11-18 (325 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcCmdline: /usr/bin/whoopsie -f ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) RelatedPackageVersions: apport-noui N/A Signal: 6SourcePackage: whoopsie StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption (fasttop)") at malloc.c:5389 _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at malloc.c:4298 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: whoopsie assert failure: double free or corruption (fasttop) UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1899100/+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 1904671] [NEW] After a certain amount of time after the session is launched, mouse clicks are no longer accepted
You have been subscribed to a public bug: X11, Wayland, the Gnome Desktop does not recognize mouse clicks and drags after several tens of minutes after launching. However, it does recognize the movement of the mouse cursor. [How To Reploduce] 1. login in a Gnome session. 2. launch some applications. 3. use it for a few dozen minutes. 4. attempt to click and drag with a mouse or other pointing device. [Actual Result] I can no longer select mouse click application windows, activity buttons, dashes, etc. [Expect Result] I will accept mouse clicks until the end of the session, and possibly hope that the event is executed when the click is made. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.13 ProcVersionSignature: Ubuntu 5.8.0-28.30-lowlatency 5.8.14 Uname: Linux 5.8.0-28-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Nov 18 13:29:28 2020 InstallationDate: Installed on 2018-05-20 (913 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/usr/bin/fish RebootRequiredPkgs: gnome-shell linux-image-5.8.0-29-lowlatency linux-base linux-image-5.8.0-29-generic linux-base SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-10-25 (23 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeApttermlog: Error: [Errno 13] 許可がありません: '/var/log/dist-upgrade/apt-term.log' VarLogDistupgradeTermlog: ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade groovy -- After a certain amount of time after the session is launched, mouse clicks are no longer accepted https://bugs.launchpad.net/bugs/1904671 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 1904671] Re: After a certain amount of time after the session is launched, mouse clicks are no longer accepted
** Package changed: ubuntu-release-upgrader (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/1904671 Title: After a certain amount of time after the session is launched, mouse clicks are no longer accepted Status in xorg package in Ubuntu: New Bug description: X11, Wayland, the Gnome Desktop does not recognize mouse clicks and drags after several tens of minutes after launching. However, it does recognize the movement of the mouse cursor. [How To Reploduce] 1. login in a Gnome session. 2. launch some applications. 3. use it for a few dozen minutes. 4. attempt to click and drag with a mouse or other pointing device. [Actual Result] I can no longer select mouse click application windows, activity buttons, dashes, etc. [Expect Result] I will accept mouse clicks until the end of the session, and possibly hope that the event is executed when the click is made. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.13 ProcVersionSignature: Ubuntu 5.8.0-28.30-lowlatency 5.8.14 Uname: Linux 5.8.0-28-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Nov 18 13:29:28 2020 InstallationDate: Installed on 2018-05-20 (913 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/usr/bin/fish RebootRequiredPkgs: gnome-shell linux-image-5.8.0-29-lowlatency linux-base linux-image-5.8.0-29-generic linux-base SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-10-25 (23 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeApttermlog: Error: [Errno 13] 許可がありません: '/var/log/dist-upgrade/apt-term.log' VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1904671/+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 1870060] Update Released
The verification of the Stable Release Update for apport 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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1870060 Title: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services) Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Released Status in apport source package in Groovy: Fix Released Status in apport source package in Hirsute: Fix Released Bug description: [Impact] apport is not creating crash files for multiple system services that use ProtectSystem since Ubuntu 20.04 LTS. [Test Case] On an Ubuntu desktop system perform the following step 1) sudo pkill -11 upowerd With the current version of apport there will not be a crash file for upowerd in /var/crash/. With the version of apport in -proposed there will be a crash file for upowerd in /var/crash/. [Regression Potential] In the event that the changes to /usr/share/apport/apport are bad then apport itself would crash thereby preventing us from getting any crash reports. So in addition to killing upowerd we should also test a regular application like xeyes. [Original Description] bluetoothd never leaves dumps/crash files when it crashes And it seems this is true for everyone. Only supplementary binaries' crash reports are shown: https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=bluez&period=year To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/+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 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)
This bug was fixed in the package apport - 2.20.11-0ubuntu27.13 --- apport (2.20.11-0ubuntu27.13) focal; urgency=medium * data/apport: Modify the check for whether or not a process is running in the same namespace so that crashes from processes running protected in the system.slice are considered as being from the same namespace. (LP: #1870060) -- Brian Murray Mon, 16 Nov 2020 14:40:03 -0800 ** Changed in: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1870060 Title: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services) Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Released Status in apport source package in Groovy: Fix Released Status in apport source package in Hirsute: Fix Released Bug description: [Impact] apport is not creating crash files for multiple system services that use ProtectSystem since Ubuntu 20.04 LTS. [Test Case] On an Ubuntu desktop system perform the following step 1) sudo pkill -11 upowerd With the current version of apport there will not be a crash file for upowerd in /var/crash/. With the version of apport in -proposed there will be a crash file for upowerd in /var/crash/. [Regression Potential] In the event that the changes to /usr/share/apport/apport are bad then apport itself would crash thereby preventing us from getting any crash reports. So in addition to killing upowerd we should also test a regular application like xeyes. [Original Description] bluetoothd never leaves dumps/crash files when it crashes And it seems this is true for everyone. Only supplementary binaries' crash reports are shown: https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=bluez&period=year To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/+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 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)
This bug was fixed in the package apport - 2.20.11-0ubuntu50.2 --- apport (2.20.11-0ubuntu50.2) groovy; urgency=medium * data/apport: Modify the check for whether or not a process is running in the same namespace so that crashes from processes running protected in the system.slice are considered as being from the same namespace. (LP: #1870060) -- Brian Murray Mon, 16 Nov 2020 14:33:58 -0800 ** Changed in: apport (Ubuntu Groovy) Status: Fix Committed => 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/1870060 Title: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services) Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Released Status in apport source package in Groovy: Fix Released Status in apport source package in Hirsute: Fix Released Bug description: [Impact] apport is not creating crash files for multiple system services that use ProtectSystem since Ubuntu 20.04 LTS. [Test Case] On an Ubuntu desktop system perform the following step 1) sudo pkill -11 upowerd With the current version of apport there will not be a crash file for upowerd in /var/crash/. With the version of apport in -proposed there will be a crash file for upowerd in /var/crash/. [Regression Potential] In the event that the changes to /usr/share/apport/apport are bad then apport itself would crash thereby preventing us from getting any crash reports. So in addition to killing upowerd we should also test a regular application like xeyes. [Original Description] bluetoothd never leaves dumps/crash files when it crashes And it seems this is true for everyone. Only supplementary binaries' crash reports are shown: https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=bluez&period=year To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870060/+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 1888543] Update Released
The verification of the Stable Release Update for busybox 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 busybox in Ubuntu. https://bugs.launchpad.net/bugs/1888543 Title: hwclock: fails to set time on glibc 2.31 Status in busybox package in Ubuntu: Fix Released Status in busybox source package in Focal: Fix Released Status in busybox source package in Groovy: Fix Released Status in busybox package in Debian: Confirmed Bug description: [Impact] * With glibc 2.31, hwclock from busybox is unable to set the system time due to the changes in settimeofday behavior. [Test Case] * Run: sudo busybox hwclock -s * It should succeed in the fixed version [Where problems could occur] * The fix calls the originally called glibc function twice, instead of passing both non-NULL parameters at once. If this compiles there should be no other issue. [Original Bug Text] With glibc 2.31, hwclock from busybox is unable to set the system time due to the changes in settimeofday behavior. The problem has been reported upstream in [1] which also contains a patch. hwclock from busybox is important as it's used on the Raspberry Pi to set the system time when an RTC is present. This bug applies to focal and groovy. [1] https://bugs.busybox.net/show_bug.cgi?id=12756 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1888543/+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 1888543] Re: hwclock: fails to set time on glibc 2.31
This bug was fixed in the package busybox - 1:1.30.1-4ubuntu6.3 --- busybox (1:1.30.1-4ubuntu6.3) focal; urgency=medium * cherry-pick settimeofday for glibc v2.31+ compatibility fix for upstream (LP: #1888543) -- Balint Reczey Wed, 11 Nov 2020 13:15:02 +0100 ** Changed in: busybox (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: busybox (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1888543 Title: hwclock: fails to set time on glibc 2.31 Status in busybox package in Ubuntu: Fix Released Status in busybox source package in Focal: Fix Released Status in busybox source package in Groovy: Fix Released Status in busybox package in Debian: Confirmed Bug description: [Impact] * With glibc 2.31, hwclock from busybox is unable to set the system time due to the changes in settimeofday behavior. [Test Case] * Run: sudo busybox hwclock -s * It should succeed in the fixed version [Where problems could occur] * The fix calls the originally called glibc function twice, instead of passing both non-NULL parameters at once. If this compiles there should be no other issue. [Original Bug Text] With glibc 2.31, hwclock from busybox is unable to set the system time due to the changes in settimeofday behavior. The problem has been reported upstream in [1] which also contains a patch. hwclock from busybox is important as it's used on the Raspberry Pi to set the system time when an RTC is present. This bug applies to focal and groovy. [1] https://bugs.busybox.net/show_bug.cgi?id=12756 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1888543/+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 1888543] Re: hwclock: fails to set time on glibc 2.31
This bug was fixed in the package busybox - 1:1.30.1-4ubuntu9.1 --- busybox (1:1.30.1-4ubuntu9.1) groovy; urgency=medium * cherry-pick settimeofday for glibc v2.31+ compatibility fix for upstream (LP: #1888543) -- Balint Reczey Mon, 09 Nov 2020 15:55:05 +0100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1888543 Title: hwclock: fails to set time on glibc 2.31 Status in busybox package in Ubuntu: Fix Released Status in busybox source package in Focal: Fix Released Status in busybox source package in Groovy: Fix Released Status in busybox package in Debian: Confirmed Bug description: [Impact] * With glibc 2.31, hwclock from busybox is unable to set the system time due to the changes in settimeofday behavior. [Test Case] * Run: sudo busybox hwclock -s * It should succeed in the fixed version [Where problems could occur] * The fix calls the originally called glibc function twice, instead of passing both non-NULL parameters at once. If this compiles there should be no other issue. [Original Bug Text] With glibc 2.31, hwclock from busybox is unable to set the system time due to the changes in settimeofday behavior. The problem has been reported upstream in [1] which also contains a patch. hwclock from busybox is important as it's used on the Raspberry Pi to set the system time when an RTC is present. This bug applies to focal and groovy. [1] https://bugs.busybox.net/show_bug.cgi?id=12756 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1888543/+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 1905482] [NEW] Xorg freeze after dragin icon from desktop to nautilus
Public bug reported: 100% reproducible by dragging an icon from the desktop to an open nautilus window. X then freezes, I have to switch to another tty, login and reboot to recover ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.38 Thu Oct 22 06:06:59 UTC 2020 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 09:51:13 2020 DistUpgraded: 2020-10-24 22:46:08,965 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)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 455.38, 5.8.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: NVIDIA Corporation GK107GL [Quadro K600] [10de:0ffa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GK107GL [Quadro K600] [10de:094b] InstallationDate: Installed on 2020-04-24 (214 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision T1700 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=c1eecc57-1357-4347-a0a6-cf3c563a52fd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to groovy on 2020-10-24 (31 days ago) dmi.bios.date: 05/30/2019 dmi.bios.release: 65.28 dmi.bios.vendor: Dell Inc. dmi.bios.version: A28 dmi.board.name: 04JGCK dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA28:bd05/30/2019:br65.28:svnDellInc.:pnPrecisionT1700:pvr00:rvnDellInc.:rn04JGCK:rvrA01:cvnDellInc.:ct15:cvr: dmi.product.name: Precision T1700 dmi.product.sku: 05A6 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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 freeze groovy 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/1905482 Title: Xorg freeze after dragin icon from desktop to nautilus Status in xorg package in Ubuntu: New Bug description: 100% reproducible by dragging an icon from the desktop to an open nautilus window. X then freezes, I have to switch to another tty, login and reboot to recover ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.38 Thu Oct 22 06:06:59 UTC 2020 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50.1 Architecture:
[Touch-packages] [Bug 1872504] Re: date modified is wrong for files on an exfat formatted drive
I think I found the bug in the linux 5.4, but I have no idea whether or how to submit a patch... The handling of exfat changes completely in the following (but not LTS) versions. In the file drivers/staging/exfat/exfat_super.c, in lines 60- static void exfat_time_fat2unix(struct timespec64 *ts, struct date_time_t *tp) { ts->tv_sec = mktime64(tp->Year + 1980, tp->Month + 1, tp->Day, // shouldn't it be tp->Month, tp->Day ?!!! tp->Hour, tp->Minute, tp->Second); ts->tv_nsec = tp->MilliSecond * NSEC_PER_MSEC; } static void exfat_time_unix2fat(struct timespec64 *ts, struct date_time_t *tp) { time64_t second = ts->tv_sec; struct tm tm; time64_to_tm(second, 0, &tm); [...] tp->MilliSecond = ts->tv_nsec / NSEC_PER_MSEC; tp->Second = tm.tm_sec; tp->Minute = tm.tm_min; tp->Hour= tm.tm_hour; tp->Day = tm.tm_mday; tp->Month = tm.tm_mon + 1; tp->Year= tm.tm_year + 1900 - 1980; } The meaning of the field Month in struct date_time_t has no documentation in the header exfat.h, but the function unix2fat produces a month from 1-12 in date_time_t by adding 1 to the result of time64_to_tm. -- 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/1872504 Title: date modified is wrong for files on an exfat formatted drive Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: When using exfat formatted drives (e.g. my camera card) with focal fossa any access causes the date modified to be set, even when it would not normally be set, and it is set a month into the future. Installing exfat-fuse and exfat-utils results in the correct behaviour. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Apr 13 17:27:30 2020 InstallationDate: Installed on 2020-04-12 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade 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/1872504/+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 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)
** Description changed: [Impact] whoopsie is crashing somewhat regularly. There are a couple of crashes in the Error Tracker which look similar: https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98 As of yet (2020-11-22) neither crash is happening with whoopsie version 0.2.73. + [Test Case] + We don't have a manual test case for this crash report but given the number of crashes in the Error Tracker and the number of users of whoopsie the absence of the same crash occurring with the new version of whoopsie should be enough to consider this verified. + [Regression Potential] + Whoopsie will no longer upload crash reports with duplicate keys but this was not something it should have been doing in the first place. That being said we should also test whoopsie with a sample of crashes (apport-test-crashes) and ensure they are received by the staging version of the Ubuntu Error Tracker. + + Original Description + Apport popped up saying whoopsie had crashed (I assume during a previous crash report upload?) ProblemType: CrashDistroRelease: Ubuntu 20.10 Package: whoopsie 0.2.72 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AssertionMessage: double free or corruption (fasttop) CasperMD5CheckResult: skip CrashCounter: 1 Date: Fri Oct 9 08:08:56 2020 ExecutablePath: /usr/bin/whoopsie InstallationDate: Installed on 2019-11-18 (325 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcCmdline: /usr/bin/whoopsie -f ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) - RelatedPackageVersions: apport-noui N/A - Signal: 6SourcePackage: whoopsie + RelatedPackageVersions: apport-noui N/ASignal: 6SourcePackage: whoopsie StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption (fasttop)") at malloc.c:5389 _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at malloc.c:4298 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: whoopsie assert failure: double free or corruption (fasttop) UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago) UserGroups: N/A separator: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1899100 Title: whoopsie assert failure: double free or corruption (fasttop) Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Bionic: New Status in whoopsie source package in Focal: New Status in whoopsie source package in Groovy: In Progress Bug description: [Impact] whoopsie is crashing somewhat regularly. There are a couple of crashes in the Error Tracker which look similar: https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98 As of yet (2020-11-22) neither crash is happening with whoopsie version 0.2.73. [Test Case] We don't have a manual test case for this crash report but given the number of crashes in the Error Tracker and the number of users of whoopsie the absence of the same crash occurring with the new version of whoopsie should be enough to consider this verified. [Regression Potential] Whoopsie will no longer upload crash reports with duplicate keys but this was not something it should have been doing in the first place. That being said we should also test whoopsie with a sample of crashes (apport-test-crashes) and ensure they are received by the staging version of the Ubuntu Error Tracker. Original Description Apport popped up saying whoopsie had crashed (I assume during a previous crash report upload?) ProblemType: CrashDistroRelease: Ubuntu 20.10 Package: whoopsie 0.2.72 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AssertionMessage: double free or corruption (fasttop) CasperMD5CheckResult: skip CrashCounter: 1 Date: Fri Oct 9 08:08:56 2020 ExecutablePath: /usr/bin/whoopsie InstallationDate: Installed on 2019-11-18 (325 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcCmdline: /usr/bin/whoopsie -f ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) RelatedPack
[Touch-packages] [Bug 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)
** Also affects: whoopsie (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: whoopsie (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: whoopsie (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: whoopsie (Ubuntu Groovy) Status: New => In Progress ** Changed in: whoopsie (Ubuntu Groovy) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: whoopsie (Ubuntu Groovy) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1899100 Title: whoopsie assert failure: double free or corruption (fasttop) Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Bionic: New Status in whoopsie source package in Focal: New Status in whoopsie source package in Groovy: In Progress Bug description: [Impact] whoopsie is crashing somewhat regularly. There are a couple of crashes in the Error Tracker which look similar: https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98 As of yet (2020-11-22) neither crash is happening with whoopsie version 0.2.73. [Test Case] We don't have a manual test case for this crash report but given the number of crashes in the Error Tracker and the number of users of whoopsie the absence of the same crash occurring with the new version of whoopsie should be enough to consider this verified. [Regression Potential] Whoopsie will no longer upload crash reports with duplicate keys but this was not something it should have been doing in the first place. That being said we should also test whoopsie with a sample of crashes (apport-test-crashes) and ensure they are received by the staging version of the Ubuntu Error Tracker. Original Description Apport popped up saying whoopsie had crashed (I assume during a previous crash report upload?) ProblemType: CrashDistroRelease: Ubuntu 20.10 Package: whoopsie 0.2.72 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AssertionMessage: double free or corruption (fasttop) CasperMD5CheckResult: skip CrashCounter: 1 Date: Fri Oct 9 08:08:56 2020 ExecutablePath: /usr/bin/whoopsie InstallationDate: Installed on 2019-11-18 (325 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcCmdline: /usr/bin/whoopsie -f ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) RelatedPackageVersions: apport-noui N/ASignal: 6SourcePackage: whoopsie StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5982159128 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f598215b5d8 "double free or corruption (fasttop)") at malloc.c:5389 _int_free (av=0x7f598218bba0 , p=0x55964a2bf3e0, have_lock=0) at malloc.c:4298 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: whoopsie assert failure: double free or corruption (fasttop) UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1899100/+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 1904192] Re: ebtables can not rename just created chain
** Also affects: iptables (Ubuntu Hirsute) Importance: Undecided Assignee: Alex Murray (alexmurray) Status: Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1904192 Title: ebtables can not rename just created chain Status in iptables: Unknown Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Groovy: In Progress Status in iptables source package in Hirsute: Fix Released Status in iptables package in Debian: Unknown Status in iptables package in Fedora: Fix Committed Bug description: [SRU] * Changes that went into 1.8.5 ave broken the errno handling. In particular loading extensions. Due to that it has become impossible to rename rules. * Upstream has created a fix and this backports that change to Ubuntu => http://git.netfilter.org/iptables/commit/?id=55b7c71dce7144f4dc0297c17abf0f04879ee247 [Test Case] * # ebtables -t nat -N foo # ebtables -t nat -E foo bar ebtables v1.8.5 (nf_tables): Chain 'foo' doesn't exists * with the fix the above command sequence works [Where problems could occur] * The change moved code from nft_chain_user_rename to do_commandeb and therefore in theory any ebtables/xtables subcommand could be affected. Yet what it does is just resetting the error code in a better place, so while it "could" affect every subcommand it should (tm) not do so. [Other Info] * n/a --- Hi, I have an issue with ebtables that affects libvirt. While initially found in hirsute I had to realize this is broken in Groovy and even Bionic (might be a different reason back then) as well right now. But working in Focal (witch matches my memory of it being good before [1]). I was isolating the commands that libvirt runs (identical between Focal and Hirsute) to find a simplified trigger. Gladly I found one that leaves libvirt and other components out of the equation. The following works on focal, but fails on the other releases. Note: I checked which tool is in use and in both cases it is xtables-nft-multi. /usr/sbin/ebtables -> /etc/alternatives/ebtables* /etc/alternatives/ebtables -> /usr/sbin/ebtables-nft* /usr/sbin/ebtables-nft -> xtables-nft-multi* So I converted the libvirt issued commands into xtables-nft-multi just to be sure in case a system to compare has other alternatives set. Focal (Good): /usr/sbin/xtables-nft-multi ebtables --concurrent -t nat -N testrule3 /usr/sbin/xtables-nft-multi ebtables --concurrent -t nat -E testrule3 testrule3-renamed Groovy/Hirsute (Fail): /usr/sbin/xtables-nft-multi ebtables --concurrent -t nat -N testrule3 /usr/sbin/xtables-nft-multi ebtables --concurrent -t nat -E testrule3 testrule3-renamed ebtables v1.8.5 (nf_tables): Chain 'testrule3' doesn't exists Try `ebtables -h' or 'ebtables --help' for more information. What might be the root cause for this? -- Old test instructions -- As I said I was tracking a fail in libvirt so the test instructions initially were around that: # the following us done as 2nd level guest (to not mess with the host, # but works on bare metal jst as much) uvt-kvm create --host-passthrough --memory 2048 --cpu 4 --disk 16 --password=ubuntu hirsute-kvm release=hirsute arch=amd64 label=daily # On guest then sudo apt update sudo apt install uvtool uvtool-libvirt uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=hirsute uvt-kvm create --disk 5 --machine-type ubuntu --password=ubuntu hirsute-2nd-lvm release=hirsute arch=amd64 label=daily uvt-kvm wait hirsute-2nd-lvm virsh shutdown hirsute-2nd-lvm virsh edit hirsute-2nd-lvm # add this to the network virsh start hirsute-2nd-lvm error: Failed to start domain hirsute-2nd-nwfilter error: internal error: applyDHCPOnlyRules failed - spoofing not protected! FYI: Get helpful log details with these in /etc/libvirt/libvirtd.conf log_filters="1:util.firewall" log_outputs="1:syslog:libvirtd" -- -- [1]: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1758037 To manage notifications about this bug go to: https://bugs.launchpad.net/iptables/+bug/1904192/+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 1877640] Re: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones.
Same issue,I have an ASUS Zephyrus M GU502GU -- 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/1877640 Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones. Status in alsa-driver package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.4 LTS dual boot with Windows 10. On Windows all is fine. On Ubuntu i have sound for speakers, but no sound at all for 3.5mm jack headphones. Tried using latest kernel versions for 4.*, 5.*, tried even 5.7-rc4. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corsarstl 1728 F pulseaudio /dev/snd/pcmC0D0p: corsarstl 1728 F...m pulseaudio /dev/snd/controlC1: corsarstl 1728 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 8 20:25:27 2020 InstallationDate: Installed on 2020-05-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio /dev/snd/controlC1: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU502GV.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU502GV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGU502GV.307:bd02/15/2020:svnASUSTeKCOMPUTERINC.:pnZephyrusMGU502GV_GU502GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus M dmi.product.name: Zephyrus M GU502GV_GU502GV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877640/+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 1905510] [NEW] utils-linux 2.36.1 breaks user mounts (cifs)
Public bug reported: I'm working on merging samba from Debian (2:4.13.2+dfsg-1), and while running the autopkgtests for the package I noticed that two tests are failing. These tests attempt to invoke mount.cifs in order to mount a user mount point. I investigated and found this on dmesg: [ 53.586709] CIFS: Attempting to mount //localhost/myshare1760 [ 53.586735] CIFS: Unknown mount option "symfollow" After some more investigation, I noticed that there are both a Debian and an upstream bug reported about this failure, and that upstream has fixed it in util-linux 2.36.2. I would be nice to have this version in hirsute so that cifs user mounts can work again. ** Affects: util-linux-ng Importance: Unknown Status: Unknown ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Affects: util-linux (Debian) Importance: Unknown Status: Unknown ** Bug watch added: github.com/karelzak/util-linux/issues #1193 https://github.com/karelzak/util-linux/issues/1193 ** Also affects: util-linux-ng via https://github.com/karelzak/util-linux/issues/1193 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #975003 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975003 ** Also affects: util-linux (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975003 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1905510 Title: utils-linux 2.36.1 breaks user mounts (cifs) Status in Util-Linux-ng: Unknown Status in util-linux package in Ubuntu: New Status in util-linux package in Debian: Unknown Bug description: I'm working on merging samba from Debian (2:4.13.2+dfsg-1), and while running the autopkgtests for the package I noticed that two tests are failing. These tests attempt to invoke mount.cifs in order to mount a user mount point. I investigated and found this on dmesg: [ 53.586709] CIFS: Attempting to mount //localhost/myshare1760 [ 53.586735] CIFS: Unknown mount option "symfollow" After some more investigation, I noticed that there are both a Debian and an upstream bug reported about this failure, and that upstream has fixed it in util-linux 2.36.2. I would be nice to have this version in hirsute so that cifs user mounts can work again. To manage notifications about this bug go to: https://bugs.launchpad.net/util-linux-ng/+bug/1905510/+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 1905510] Re: utils-linux 2.36.1 breaks user mounts (cifs)
Set priority to High because it will block samba from migrating, which will in turn block Python 3.9 from migrating. ** Changed in: util-linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1905510 Title: utils-linux 2.36.1 breaks user mounts (cifs) Status in Util-Linux-ng: Unknown Status in util-linux package in Ubuntu: New Status in util-linux package in Debian: Unknown Bug description: I'm working on merging samba from Debian (2:4.13.2+dfsg-1), and while running the autopkgtests for the package I noticed that two tests are failing. These tests attempt to invoke mount.cifs in order to mount a user mount point. I investigated and found this on dmesg: [ 53.586709] CIFS: Attempting to mount //localhost/myshare1760 [ 53.586735] CIFS: Unknown mount option "symfollow" After some more investigation, I noticed that there are both a Debian and an upstream bug reported about this failure, and that upstream has fixed it in util-linux 2.36.2. I would be nice to have this version in hirsute so that cifs user mounts can work again. To manage notifications about this bug go to: https://bugs.launchpad.net/util-linux-ng/+bug/1905510/+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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
Hi, This update seems to break Bluetooth on the Pi 4 8GB. /usr/bin/btuart returns "bcm43xx_init Initialization timed out". It's working again after reverting to version 5.55-0ubuntu1. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Triaged Status in bluez source package in Groovy: Fix Released Status in bluez source package in Hirsute: Triaged Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * Enable the -proposed repository for the release (groovy) * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+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 1905510] Re: utils-linux 2.36.1 breaks user mounts (cifs)
** Changed in: util-linux-ng Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1905510 Title: utils-linux 2.36.1 breaks user mounts (cifs) Status in Util-Linux-ng: Fix Released Status in util-linux package in Ubuntu: New Status in util-linux package in Debian: Unknown Bug description: I'm working on merging samba from Debian (2:4.13.2+dfsg-1), and while running the autopkgtests for the package I noticed that two tests are failing. These tests attempt to invoke mount.cifs in order to mount a user mount point. I investigated and found this on dmesg: [ 53.586709] CIFS: Attempting to mount //localhost/myshare1760 [ 53.586735] CIFS: Unknown mount option "symfollow" After some more investigation, I noticed that there are both a Debian and an upstream bug reported about this failure, and that upstream has fixed it in util-linux 2.36.2. I would be nice to have this version in hirsute so that cifs user mounts can work again. To manage notifications about this bug go to: https://bugs.launchpad.net/util-linux-ng/+bug/1905510/+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 1894917] Re: [chtmax98090][Dell Chromebook 11 'candy'] Pulseaudio fails to detect card // Bluetooth and USB devices work but internal speakers do not work (gives dummy output)
*** This bug is a duplicate of bug 1871306 *** https://bugs.launchpad.net/bugs/1871306 ** This bug is no longer a duplicate of bug 1833116 [chtmax98090 on Bay Trail Chromebooks] audio not working, shows "Dummy Output" ** This bug has been marked a duplicate of bug 1871306 [SRU]No sound from internal card chtmax98090 - missing UCM2 files in alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1894917 Title: [chtmax98090][Dell Chromebook 11 'candy'] Pulseaudio fails to detect card // Bluetooth and USB devices work but internal speakers do not work (gives dummy output) Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: To give some other background information: Description: Ubuntu 20.04.1 LTS Release: 20.04 pulseaudio: Installed: 1:13.99.1-1ubuntu3.6 Candidate: 1:13.99.1-1ubuntu3.6 Version table: *** 1:13.99.1-1ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages Linux is fairly new for me and any other information I need to provide can be given as long as I am told on how to retrieve it. This system I am currently using is Dell Chromebook 11 (Candy MODEL) with 4 GB Ram and 16 GB of Har drive space. I am primarily using a Linux Distro such as Ubuntu or other distros in the same family. (This one is Linux Lite) Audio will play from USB connected devices or Bluetooth speakers/headphones. Internal speakers do not work at this moment and give me Dummy Output. The configuration file in puvucontrol gives me HDMI outputs or surround sound but no option for the internal speakers. I'm pretty sure my kernal driver is snd_hda-intel and tried loading different drivers from the file in '/etc/modprobe.d/alsa-base.conf' but to no avail. I'm not sure if this certain device cannot produce output from a linux distro but I will be trying other resources. I've reinstalled Pulse audio, its base and reinstalled Linux on this machine multiple times. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-46.50-generic 5.4.60 Uname: Linux 5.4.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: areebcancode 1417 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 8 17:24:36 2020 InstallationDate: Installed on 2020-09-01 (7 days ago) InstallationMedia: Linux Lite 5.0 - Release amd64 SourcePackage: pulseaudio Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Title: [chtmax98090 - chtmax98090, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2019 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd01/03/2019:svnGOOGLE:pnCandy:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Candy dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-09-03T17:56:09.564820 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894917/+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 1833116] Re: [chtmax98090 on Bay Trail Chromebooks] audio not working, shows "Dummy Output"
*** This bug is a duplicate of bug 1871306 *** https://bugs.launchpad.net/bugs/1871306 ** This bug has been marked a duplicate of bug 1871306 [SRU]No sound from internal card chtmax98090 - missing UCM2 files in alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1833116 Title: [chtmax98090 on Bay Trail Chromebooks] audio not working, shows "Dummy Output" Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-ucm-conf package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: chtmax98090 intel HD audio device doesn't work out of the box after installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on audio devices. Audio options shows device and it works if I do this: git clone https://github.com/plbossart/UCM.git cd UCM cp -r chtmax98090/ /usr/share/alsa/ucm/ alsactl store It would be great if there were a solution to make it works out of the box. The device (Chromebook Acer CB3-111 has it's end of life for chromeOS in July-August, so I suppose more people with this device will change OS perhaps to Ubuntu). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaime 1293 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 17 20:32:35 2019 InstallationDate: Installed on 2019-06-17 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+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