[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Nice to see it works for 20.10. however, I'd like to keep on the LTS version and expect to get a fix soon. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1903468] Re: Endless "Cache Refresh" on Software Update settings change
is the number of restart since the issue, if you managed to trigger it in your current session it's 0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1903468 Title: Endless "Cache Refresh" on Software Update settings change Status in software-properties package in Ubuntu: Incomplete Bug description: After reapplying some of the checkboxes under "Software & Updates" -> "Other Software" after distro upgrade, a window with title "Cache Refresh" pops and never disappears. (check screenshot bellow) > lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 9 01:55:13 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2015-06-17 (1971 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-09-29 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1903468/+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
Łukasz and Dave, thanks for the fix. I have renamed 'ubuntu' to 'hirsute' to keep with the existing naming scheme: https://git.launchpad.net/~bluetooth/bluez -- 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: Fix Released Status in bluez source package in Hirsute: Fix Released 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 * sudo add-apt-repository ppa:waveform/pi-bluetooth * 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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
This bug was fixed in the package bluez - 5.55-0ubuntu2 --- bluez (5.55-0ubuntu2) hirsute; urgency=medium * Added patches from the Raspberry Pi Foundation - d/p/raspi-bcm43xx-load-firmware.patch - d/p/raspi-bcm43xx-3wire.patch - d/p/raspi-cypress-305-bdaddr.patch * These patches fix Bluetooth operation on the Pi 400 (LP: #1903048) -- Dave Jones Thu, 05 Nov 2020 13:39:07 + ** Changed in: bluez (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- 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: Fix Released Status in bluez source package in Hirsute: Fix Released 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 * sudo add-apt-repository ppa:waveform/pi-bluetooth * 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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Please please, I'll apreciate a lot any kind of help. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1903668] Re: HDMI audio device disappears and is unavailble after several minutes of not being used
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1903668 Title: HDMI audio device disappears and is unavailble after several minutes of not being used Status in pulseaudio package in Ubuntu: New Bug description: On system boot both of my audio devices are selectable and useable. After around 10 minutes the HDMI device just disappears and cannot be selected as output in either the task bar audio applet or in Kstart>system settings>audio(either devices or advanced tab). In the devices tab a device called Dummy output is displayed and in the advanced tab the HDMI device is shown, in this case GP107GL, with the profile in the dropdown box underneath it displaying off with no ability to switch it to on. If I go to pulse volume control>configuration i am able to select the HDMI device and the system will use it. If I play a 2 hour movie after this and then turn off the media player the HDMI device will once again disappear after about 10 minutes. When I ran ubuntu-bug the system identified the HDMI device and switched to it (it is set as default) and has remained accessable for 15 minutes now. I am running the NVIDIA 450 driver package. If I run Kubuntu 20.10 a similar problem occurs except the the profile of the device is somehow damaged but by selecting any speaker setup (profile), audio returns. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 10 16:59:24 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-24 (200 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.E0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X470 GAMING PRO CARBON (MS-7B78) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.E0:bd06/10/2020:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B78:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPROCARBON(MS-7B78):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B78 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 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/1903668/+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 1900404] Re: pulseaudio[2032]: No UCM verb is valid for hw:0
Fixed in release 20.10 ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Released -- 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/1900404 Title: pulseaudio[2032]: No UCM verb is valid for hw:0 Status in pulseaudio package in Ubuntu: Fix Released Bug description: pulseaudio[2032]: No UCM verb is valid for hw:1 pulseaudio[2032]: No UCM verb is valid for hw:0 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat2032 F pulseaudio /dev/snd/controlC0: navycat2032 F pulseaudio /dev/snd/pcmC0D0p: navycat2032 F...m pulseaudio /dev/snd/controlC1: navycat2032 F pulseaudio CasperMD5CheckResult: skip Date: Mon Oct 19 11:57:52 2020 InstallationDate: Installed on 2020-10-07 (11 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1900404/+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).
I don't know of any alternative "soundmanager" for desktop Linux that has better Bluetooth support than PulseAudio. At least not on desktop Linux... I think Google wrote their own stack for Android. -- 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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
** Also affects: bluez (Ubuntu Hirsute) Importance: High Assignee: Dave Jones (waveform) Status: Fix Committed -- 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: Fix Committed Status in bluez source package in Hirsute: Fix Committed 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 * sudo add-apt-repository ppa:waveform/pi-bluetooth * 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 1901609] Re: signond causes qprocess crash
I have simply concluded this will never be fixed and telepathy should simply be removed from KDE entirely. Its currently useless and has had the same or similar issues going back to 2015. Further no one wants to assume responsibility for fixing it. There are dozens or more bug reports from here, to reddit, to debian forums to manjaro forums to arch forums to ubuntu forums and on and on. Its never been fixed and now these bugs are closed as fixed in upstream. Which honestly may never actually reach end users. This issue is effecting almost all services including Lync, Google, telegram, Skype, etc. etc. Its also the same in all aur, deb, and rpm based distros -- 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 Bug description: 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 1901609] Re: signond causes qprocess crash
Seriously. Wtf is the reason for a 5 year bug in Ububtu... you guys aren't making enough money to fix stuff? If this was a volunteer system I would be a little less frustrated but Ubuntu gets a pile of dough from many sources and its still not fixed. Unbelieveable!! -- 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 Bug description: 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 1901609] Re: signond causes qprocess crash
I have posted on debian bug reports and manjaro and arch. Manjaro didn't respond even when I followed up, arch did the same thing simply not responding even with multiple posts and follow ups and debian pointed me to kde bug forums thats why I posted my initial bug report here... seems everyone is passing the buck. Also, the patch in arch did not fix the issue. It is improved as it allows for the Google account to be added but does not allow for messages to be sent, it never connects it says connecting... and never actually connects. The patch also fixed kio- gdrive but didn't fix Skype but I think thats a different package something about "haze". So unless telepathy was actually tried completely one may assume its fixed because the fixed signond allows for a google account to be added and appears at first glance to be working but actual messaging does not work and other accounts still can't be added. So if someone tried it and went as far as to add a Google account and then called it a day without actually trying to send messages and also trying other accounts like Skype and lync and telegram and then after adding the accounts actually sending messages it may appear to that person as fixed but in truth is only slightly improved.. -- 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 Bug description: 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 1820929] Re: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces
Si-Wei, What environment and methodology are you testing with? I do not see the same results you are reporting. I am using the instructions you previously provided, and with an 18.04.5 Ubuntu image, I see the expected network interface naming (ens3, ens3nsby), and do not see /run/systemd/network or /run/udev/rules.d as you describe. -- 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/1820929 Title: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces Status in netplan: Triaged Status in initramfs-tools package in Ubuntu: New Status in netplan.io package in Ubuntu: Triaged Status in systemd package in Ubuntu: Incomplete Status in initramfs-tools source package in Bionic: Fix Released Status in netplan.io source package in Bionic: New Status in systemd source package in Bionic: New Bug description: [Impact] * At present, virtual machines utilizing net_failover network interface configurations are incorrectly configured due to the reliance on the MAC address to identify specific network interfaces. When net_failover is utilized, multiple interfaces will bear the same MAC address (the net_failover master itself, as well as the interfaces subordinate to it), rendering the MAC address ineffective for unique identification of the interface. This results in incorrect naming of network interfaces from the "set-name" directive in the netplan configuration. * The solution here is to use the interface name instead of the MAC address when the interface is a net_failover master device. Logic is added on initramfs-tools to check the device type and virtio flags to apply this change only to net_failover master devices. [Test Case] * The change can be tested by configuring a virtual machine with a virtio_net network device with the "failover=on" option to the "-device" option to qemu, e.g., -device virtio-net- pci,netdev=hostnet0,id=net0,bus=pci.0,addr=0x3,mac=00:00:17:00:18:04,failover=on * This will set the virtio device "standby" feature bit (bit 62, counting from 0). This requires a version of qemu with support for this feature. * When so configured, the netplan configuration generated by initramfs will not contain a "macaddress:" match directive for the network interface in question. [Regression Potential] * Erroneous identification of a network interface as a net_failover master device could lead to omission of a macaddress directive, causing interfaces to be incorrectly named. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1820929/+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 1902891] Re: "Too many levels of symbolic links” error when using systemd to mount sshfs
I was able to reproduce this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1902891 Title: "Too many levels of symbolic links” error when using systemd to mount sshfs Status in systemd package in Ubuntu: Confirmed Bug description: I have asked question at askubuntu about "Too many levels of symbolic links” error when trying to use systemd to mount sshfs (https://askubuntu.com/questions/1286375/too-many-levels-of-symbolic- links-error-when-using-systemd) I have not got any responses, so I am submitting a bug report. If this is not a bug, please advice how to mount sshfs share with systemd. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 16:17:04 2020 InstallationDate: Installed on 2019-11-03 (367 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81H1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-03-28 (220 days ago) dmi.bios.date: 08/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8PCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14ARR dmi.modalias: dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR: dmi.product.family: ideapad 530S-14ARR dmi.product.name: 81H1 dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR dmi.product.version: Lenovo ideapad 530S-14ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902891/+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 1902891] Re: "Too many levels of symbolic links” error when using systemd to mount sshfs
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/1902891 Title: "Too many levels of symbolic links” error when using systemd to mount sshfs Status in systemd package in Ubuntu: Confirmed Bug description: I have asked question at askubuntu about "Too many levels of symbolic links” error when trying to use systemd to mount sshfs (https://askubuntu.com/questions/1286375/too-many-levels-of-symbolic- links-error-when-using-systemd) I have not got any responses, so I am submitting a bug report. If this is not a bug, please advice how to mount sshfs share with systemd. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 16:17:04 2020 InstallationDate: Installed on 2019-11-03 (367 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81H1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-03-28 (220 days ago) dmi.bios.date: 08/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8PCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14ARR dmi.modalias: dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR: dmi.product.family: ideapad 530S-14ARR dmi.product.name: 81H1 dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR dmi.product.version: Lenovo ideapad 530S-14ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902891/+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 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono
pango fix uploaded to Debian ** Changed in: pango1.0 (Ubuntu) Status: Triaged => Fix Committed ** Changed in: pango1.0 (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1900729 Title: gnome-terminal font settings show only italic version of ubuntu mono Status in gnome-terminal package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Committed Status in pango1.0 package in Ubuntu: Fix Committed Status in gnome-terminal source package in Groovy: Fix Committed Status in gtk+3.0 source package in Groovy: Won't Fix Bug description: [Impact] When you want to select a monospace font in gnome-terminal's profile editor, it does not always show the regular font but rather an arbitrarily chosen one. The proposed gnome-terminal upload reverts an upstream commit, which means that all weights/styles for monospace fonts are shown. It takes us back to how it works in focal. [Test case] * Install the binaries built from gnome-terminal in groovy-proposed * Relogin * Open gnome-terminal -> Preferences and open the window for selecting a custom font for the profile. Find that it shows all available monospace fonts. Confirm for a few fonts that they can actually be selected without issues. [Where problems could occur] This is a one liner in gnome-terminal and does not affect other applications. So given a successful verification of the test case, this ought to be a safe change. [Other info] Please note that this particular change has not been made in hirsute. The reason is that we intend to follow upstream there, which means that the issue will be resolved through changes in gtk and pango. [Original description] trying to change the font in gnome-terminal, only the italics version of the ubuntu mono font is shown, as can be seen in the attachment. on the other hand, when changing fonts in the appearance settings, i can see all variants of the ubuntu fonts... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-terminal 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Oct 20 16:56:57 2020 InstallationDate: Installed on 2020-10-20 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+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 1898547] Re: neutron-linuxbridge-agent fails to start with iptables 1.8.5
This bug was fixed in the package iptables - 1.8.5-3ubuntu3 --- iptables (1.8.5-3ubuntu3) hirsute; urgency=medium * Fix regression when configuring basechain policy (LP: #1898547) - d/p/9003-iptables_nft_fix_basechain_policy_configuration.patch: Backport patch from upstream to fix basechain policy configuration when it wasn't explicitly set. -- Alex Murray Tue, 03 Nov 2020 11:57:59 +1030 ** Changed in: iptables (Ubuntu Hirsute) Status: Fix Committed => 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/1898547 Title: neutron-linuxbridge-agent fails to start with iptables 1.8.5 Status in Ubuntu on IBM z Systems: Fix Committed Status in iptables package in Ubuntu: Fix Released Status in neutron package in Ubuntu: Invalid Status in iptables source package in Groovy: Fix Committed Status in neutron source package in Groovy: Invalid Status in iptables source package in Hirsute: Fix Released Status in neutron source package in Hirsute: Invalid Bug description: [Impact] With iptables 1.8.5 neutron-linuxbridge-agent fails to properly start. The log file shows many errors like: 2020-10-05 10:20:37.998 551 ERROR neutron.plugins.ml2.drivers.agent._common_agent ; Stdout: ; Stderr: iptables-restore: line 29 failed This can be demonstrated with a simple test case: iptables-restore
[Touch-packages] [Bug 1903468] Re: Endless "Cache Refresh" on Software Update settings change
It got stranger this time. Now while the "Cache Refresh" window was hanging the software list with things to update popped (new image attached). Updated the listed programs and closed it and the Cache Refresh was still there. How can I retrieve the number for the command you sent. The n in 'journalctl -b ' ** Attachment added: "Screenshot from 2020-11-10 23-17-25.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1903468/+attachment/5433119/+files/Screenshot%20from%202020-11-10%2023-17-25.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1903468 Title: Endless "Cache Refresh" on Software Update settings change Status in software-properties package in Ubuntu: Incomplete Bug description: After reapplying some of the checkboxes under "Software & Updates" -> "Other Software" after distro upgrade, a window with title "Cache Refresh" pops and never disappears. (check screenshot bellow) > lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 9 01:55:13 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2015-06-17 (1971 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-09-29 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1903468/+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 1902960] Re: Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases
I've just tested, and this doesn't seem to reproduce when launching from a captured image (with 90-hotplug-azure.yaml restored and `cloud-init clean` executed). So I think I've exhausted the ways in which I can attempt to gain more insight into what's happening during the part of boot where this reproduces. I think we're going to need an image published with some debugging built into it (which, hopefully, will continue to reproduce the issue). If https://paste.ubuntu.com/p/qkwmDvRRrB/ is installed and enabled, we should get a whole bunch of udev information, which may shed some light onto what's going on from an ordering POV. I'm not sure if there's any more networking/networkd-specific debugging we should also add. -- 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/1902960 Title: Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases Status in cloud-images: New Status in cloud-init package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to have broken DNS resolution across much of our Azure fleet earlier today. We ended up mitigating this by forcing reboots on the associated instances, no combination of networkctl reload, reconfigure, systemctl daemon-reexec, systemctl daemon-reload, netplan generate, netplan apply would get resolvectl to have a DNS server again. The main symptom appears to have been systemd-networkd believing it wasn't managing the eth0 interfaces: ubuntu@machine-1:~$ sudo networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 etherroutableunmanaged 2 links listed. Which eventually made them lose their DNS resolvers: ubuntu@machine-1:~$ sudo resolvectl dns Global: Link 2 (eth0): After rebooting, we see this behaving properly: ubuntu@machine-1:~$ sudo networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 etherroutableconfigured 2 links listed. ubuntu@machine-1:~$ sudo resolvectl dns Global: Link 2 (eth0): 168.63.129.16 This appears to be specifically linked to the upgrade, i.e. we were able to provoke the issue by upgrading the systemd package, so I suspect it's part of the packaging in the upgrade process. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lspci-vt: -[:00]-+-00.0 Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) +-07.0 Intel Corporation 82371AB/EB/MB PIIX4 ISA +-07.1 Intel Corporation 82371AB/EB/MB PIIX4 IDE +-07.3 Intel Corporation 82371AB/EB/MB PIIX4 ACPI \-08.0 Microsoft Corporation Hyper-V virtual VGA Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: systemd 245.4-4ubuntu3.3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1031-azure root=PARTUUID=2e08bba3-68b4-4a16-af3b-47b73bd138a9 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1031.32-azure 5.4.65 Tags: focal uec-images Uname: Linux 5.4.0-1031-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090008 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 4412ad79-83fa-f845-b7c2-6f30dd4f1950 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1902960/+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)
I've uploaded this for Hirsute - thanks! ** Tags added: fr-914 -- 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: Confirmed Bug description: Apport popped up saying whoopsie had crashed (I assume during a previous crash report upload?) ProblemType: Crash DistroRelease: 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: 6 SourcePackage: 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 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all
*** This bug is a duplicate of bug 1901922 *** https://bugs.launchpad.net/bugs/1901922 So far this libasound2 fix seems to work for me as well. Acer Swift 3, Ryzen 4700U with Ubuntu 20.04 LTS & also recently updated to 20.10 (both versions effected). -- 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/1901157 Title: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output didn't work anymore. Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get the exact same problem (On 20.04 Livesystem it works) An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device uses the wrong Kernel Module (Audio Input is working since it uses the correct kernel module and driver) 07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:5081] Kernel modules: snd_hda_intel -- 07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:5081] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:5081] Kernel modules: snd_hda_intel Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.16-050816-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Oct 23 10:17:36 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed Symptom_Card: Webcam Vitade AF - USB 2.0 Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio Symptom_Type: No sound at all Title: [acp - acp, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157/+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 1903382] Re: unable to add online account for google, flickr, microsoft, facebook
the issue seems to be with the radeonsi driver
** No longer affects: gnome-online-accounts (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1903382
Title:
unable to add online account for google, flickr, microsoft, facebook
Status in webkit2gtk package in Ubuntu:
New
Bug description:
Fresh install of groovy. When I try to add Google, Flickr or Microsoft
account, the loading window stays grey forever. When trying Facebook,
i can see the loaded page for a second then switches to grey also.
gnome-online-accounts:
Telepítve: 3.37.90-1ubuntu1
Jelölt:3.37.90-1ubuntu1
I see these messages in journal:
10:03:14 kernel: traps: WebKitWebProces[14044] trap int3 ip:7f510e1933cb
sp:7ffd7c266ba0 error:0 in libglib-2.0.so.0.6600.1[7f510e153000+8b000]
10:03:14 WebKitWebProces:backtrace from your debugger if you break on the
gdk_x_error() function.)
10:03:14 WebKitWebProces:backtrace from your debugger if you break on the
gdk_x_error() function.)
10:03:14 WebKitWebProces:variable to change this behavior. You can then
get a meaningful
10:03:14 WebKitWebProces:To debug your program, run it with the
GDK_SYNCHRONIZE environment
10:03:14 WebKitWebProces:that is, you will receive the error a while
after causing it.
10:03:14 WebKitWebProces: (Note to programmers: normally, X errors are
reported asynchronously;
10:03:14 WebKitWebProces: (Details: serial 221 error_code 2 request_code
152 (GLX) minor_code 34)
10:03:14 WebKitWebProces: The error was 'BadValue (integer parameter out of
range for operation)'.
10:03:14 WebKitWebProces: This probably reflects a bug in the program.
10:03:14 WebKitWebProces: (WebKitWebProcess:2): Gdk-ERROR **: 10:03:14.587:
The program 'WebKitWebProcess' received an X Window System error.
10:03:14 WebKitWebProces: libGL error: failed to load driver: swrast
10:03:14 WebKitWebProces: libGL error: MESA-LOADER: failed to open swrast
(search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
10:03:14 WebKitWebProces: libGL error: failed to load driver: radeonsi
10:03:14 WebKitWebProces: libGL error: MESA-LOADER: failed to open radeonsi
(search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
10:03:14 WebKitWebProces: libGL error: failed to load driver: radeonsi
10:03:14 WebKitWebProces: libGL error: MESA-LOADER: failed to open radeonsi
(search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
10:03:02 kernel: traps: eadedCompositor[14032] trap int3 ip:7f38f64183cb
sp:7f387c5fde10 error:0 in libglib-2.0.so.0.6600.1[7f38f63d8000+8b000]
10:03:02 WebKitWebProces:backtrace from your debugger if you break on the
gdk_x_error() function.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1903382/+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 1903329] Re: SRU the current 2.48.9 stable update
** Changed in: librsvg (Ubuntu Focal) Status: Confirmed => Triaged ** Changed in: librsvg (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1903329 Title: SRU the current 2.48.9 stable update Status in librsvg package in Ubuntu: Triaged Status in librsvg source package in Focal: Triaged Bug description: * Impact That's the current GNOME stable update, which fixes a number of issues, including a regression[1] since librsvg 2.40.x which was shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant changes between Ubuntu 20.04's current librsvg 2.48.7 (that version was also introduced by an SRU back in July[3]) and the current version 2.48.9. The complete list of changes is available on GNOME GitLab[4]. * Test case The update is part of GNOME stable updates[5]. Smoke testing by opening SVG images with eog or importing them with gimp can be performed to ensure there are no regressions. * Regression potential This is a bugfix-only stable micro-release, however librsvg is a core component with a number of reverse dependencies. A combination of autopkgtests and manual smoke testing to try and detect SVG rendering issues should be performed. * Notes about this report This is my first SRU request (and at the same time my first launchpad bug report). I'm not really familiar with the whole SRU process which is why I first asked about it on Ubuntu's official discourse forum[6]. Canonical's Sebastien Bacher encouraged me to open this ticket. I've copied over some parts of the last librsvg SRU ticket[3]. I hope this is fine. Thanks for considering this SRU. [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642 [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS [3]: https://bugs.launchpad.net/bugs/1884326 [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9 [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [6]: https://discourse.ubuntu.com/t/most-straight-forward-way-to-get- librsvg2-microrelease-update-into-focal-updates/19238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1903329/+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 1903765] [NEW] Subwoofer mapped incorrectly on Macbook 2.1
Public bug reported: It seems the 2.0 speakers get mapped to Speaker and the subwoofer is mapped to HEADPHONES, not LFE. I confirmed this by raising the volume for "headphones" in alsamixer and getting the base to play along. However, there seems to be no workaround in Ubuntu just using the sound GUI. My guess is, if ALSA would do the mapping to LFE correctly, I could use the 2.1 hardware map in the Ubuntu sound settings and all would be well! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diskdoc3271 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Tue Nov 10 21:33:29 2020 InstallationDate: Installed on 2020-10-08 (33 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Inbyggt ljud - HDA Intel Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/07 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB21.88Z.00A5.B07.0706270922 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4208CAA dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4208CAA dmi.modalias: dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA: dmi.product.family: MacBook dmi.product.name: MacBook2,1 dmi.product.sku: System SKUNumber dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1903765 Title: Subwoofer mapped incorrectly on Macbook 2.1 Status in alsa-driver package in Ubuntu: New Bug description: It seems the 2.0 speakers get mapped to Speaker and the subwoofer is mapped to HEADPHONES, not LFE. I confirmed this by raising the volume for "headphones" in alsamixer and getting the base to play along. However, there seems to be no workaround in Ubuntu just using the sound GUI. My guess is, if ALSA would do the mapping to LFE correctly, I could use the 2.1 hardware map in the Ubuntu sound settings and all would be well! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diskdoc3271 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Tue Nov 10 21:33:29 2020 InstallationDate: Installed on 2020-10-08 (33 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Inbyggt ljud - HDA Intel Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/07 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB21.88Z.00A5.B07.0706270922 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4208CAA dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4208CAA dmi.modalias: dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA: dmi.product.family: MacBook dmi.product.name: MacBook2,1 dmi.product.sku: System SKUNumber dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1903756] Re: show application showing overview instead of showing application
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Including a screenshot showing the issue could help understanding the description Thank you! ** Package changed: nano (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1903756 Title: show application showing overview instead of showing application Status in gnome-shell package in Ubuntu: Incomplete Bug description: unable to click on running apps and have to lockout to restart the gnome-shell,ctrl + alt f2 to restart the gnome-shell doesn't effects dash show application showing overview instead of showing application ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nano 4.8-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 00:43:36 2020 SourcePackage: nano UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903756/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
This has NOT been fixed in Bionic. or it came back. My cron script that uses a program in /snap/bin can not be found I have to create a sym link to /usr/bin -- 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/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Won't Fix Status in systemd source package in Xenial: Fix Released Status in snapd source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in snapd source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] # make snapd-env-generator executable if it is not $ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator # reboot, then test the effect of the fix $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1902960] Re: Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases
(Added cloud-images for visibility.) ** Also affects: cloud-images 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/1902960 Title: Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases Status in cloud-images: New Status in cloud-init package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to have broken DNS resolution across much of our Azure fleet earlier today. We ended up mitigating this by forcing reboots on the associated instances, no combination of networkctl reload, reconfigure, systemctl daemon-reexec, systemctl daemon-reload, netplan generate, netplan apply would get resolvectl to have a DNS server again. The main symptom appears to have been systemd-networkd believing it wasn't managing the eth0 interfaces: ubuntu@machine-1:~$ sudo networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 etherroutableunmanaged 2 links listed. Which eventually made them lose their DNS resolvers: ubuntu@machine-1:~$ sudo resolvectl dns Global: Link 2 (eth0): After rebooting, we see this behaving properly: ubuntu@machine-1:~$ sudo networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 etherroutableconfigured 2 links listed. ubuntu@machine-1:~$ sudo resolvectl dns Global: Link 2 (eth0): 168.63.129.16 This appears to be specifically linked to the upgrade, i.e. we were able to provoke the issue by upgrading the systemd package, so I suspect it's part of the packaging in the upgrade process. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lspci-vt: -[:00]-+-00.0 Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) +-07.0 Intel Corporation 82371AB/EB/MB PIIX4 ISA +-07.1 Intel Corporation 82371AB/EB/MB PIIX4 IDE +-07.3 Intel Corporation 82371AB/EB/MB PIIX4 ACPI \-08.0 Microsoft Corporation Hyper-V virtual VGA Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: systemd 245.4-4ubuntu3.3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1031-azure root=PARTUUID=2e08bba3-68b4-4a16-af3b-47b73bd138a9 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1031.32-azure 5.4.65 Tags: focal uec-images Uname: Linux 5.4.0-1031-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090008 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 4412ad79-83fa-f845-b7c2-6f30dd4f1950 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1902960/+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 1903756] Re: show application showing overview instead of showing application
** Description changed: unable to click on running apps and have to lockout to restart the gnome-shell,ctrl + alt f2 to restart the gnome-shell doesn't effects dash show application showing overview instead of showing application - could be the kernel issues since upgrading to 5.4.0-52-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nano 4.8-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 00:43:36 2020 SourcePackage: nano UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1903756 Title: show application showing overview instead of showing application Status in nano package in Ubuntu: New Bug description: unable to click on running apps and have to lockout to restart the gnome-shell,ctrl + alt f2 to restart the gnome-shell doesn't effects dash show application showing overview instead of showing application ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nano 4.8-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 00:43:36 2020 SourcePackage: nano UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1903756/+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 1902960] Re: Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases
Thanks for the explanation, Dan! I was off down a wrong path, I
appreciate the correction.
I've just downloaded the Azure image from cloud-images.u.c and it
includes this in `/etc/netplan/90-hotplug-azure.yaml`:
# This netplan yaml is delivered in Azure cloud images to support
# attaching and detaching nics after the instance first boot.
# Cloud-init otherwise handles initial boot network configuration in
# /etc/netplan/50-cloud-init.yaml
network:
version: 2
ethernets:
ephemeral:
dhcp4: true
match:
driver: hv_netvsc
name: '!eth0'
optional: true
hotpluggedeth0:
dhcp4: true
match:
driver: hv_netvsc
name: 'eth0'
This file is not present in a booted system, because cloud-init removes
it during boot:
2020-11-09 18:12:09,306 - handlers.py[DEBUG]: start:
azure-ds/maybe_remove_ubuntu_network_config_scripts:
maybe_remove_ubuntu_network_config_scripts
2020-11-09 18:12:09,307 - DataSourceAzure.py[INFO]: Removing Ubuntu extended
network scripts because cloud-init updates Azure network configuration on the
following event: System boot.
2020-11-09 18:12:09,307 - util.py[DEBUG]: Attempting to remove
/etc/netplan/90-hotplug-azure.yaml
2020-11-09 18:12:09,307 - handlers.py[DEBUG]: finish:
azure-ds/maybe_remove_ubuntu_network_config_scripts: SUCCESS:
maybe_remove_ubuntu_network_config_scripts
It does this before the regular cloud-init network configuration is
written, or `netplan generate` is called:
2020-11-09 18:12:09,465 - util.py[DEBUG]: Writing to
/etc/netplan/50-cloud-init.yaml - wb: [644] 603 bytes
2020-11-09 18:12:09,466 - subp.py[DEBUG]: Running command ['netplan',
'generate'] with allowed return codes [0] (shell=False, capture=True)
cloud-init also runs a couple of udevadm commands right after `netplan
generate`:
2020-11-09 18:12:09,813 - subp.py[DEBUG]: Running command ['udevadm',
'test-builtin', 'net_setup_link', '/sys/class/net/eth0'] with allowed return
codes [0] (shell=False, capture=True)
2020-11-09 18:12:09,828 - subp.py[DEBUG]: Running command ['udevadm',
'test-builtin', 'net_setup_link', '/sys/class/net/lo'] with allowed return
codes [0] (shell=False, capture=True)
This all happens before systemd-networkd starts:
Nov 09 18:12:09.956027 focal-1604945439 systemd[1]: Starting Network
Service...
So: I'm not really sure what's going on here. I've tried restoring `90
-hotplug-azure.yaml` and removing `50-cloud-init.yaml`; that doesn't
cause the issue to reproduce on a subsequent boot.
One thing worth noting, that could lead to unexpected state: cloud-init
performs a DHCP on this interface (in order to be able to fetch the
network configuration it is going to apply). It does this in a sandbox
(i.e. it doesn't use system configuration for it), but potentially that
could mean that there's (kernel?) state for that interface which
{udev,network}d interpret in a way that leads to this issue?
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => New
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1902960
Title:
Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS
resolution in some cases
Status in cloud-init package in Ubuntu:
New
Status in systemd package in Ubuntu:
Incomplete
Bug description:
The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to
have broken DNS resolution across much of our Azure fleet earlier
today. We ended up mitigating this by forcing reboots on the
associated instances, no combination of networkctl reload,
reconfigure, systemctl daemon-reexec, systemctl daemon-reload, netplan
generate, netplan apply would get resolvectl to have a DNS server
again. The main symptom appears to have been systemd-networkd
believing it wasn't managing the eth0 interfaces:
ubuntu@machine-1:~$ sudo networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eth0 etherroutableunmanaged
2
links listed.
Which eventually made them lose their DNS resolvers:
ubuntu@machine-1:~$ sudo resolvectl dns
Global:
Link 2 (eth0):
After rebooting, we see this behaving properly:
ubuntu@machine-1:~$ sudo networkctl list
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eth0 etherroutableconfigured
2 links listed.
ubuntu@machine-1:~$ sudo resolvectl dns
Global:
Link 2 (eth0): 168.63.129.16
This appears to be specifically linked to the upgrade, i.e. we were able to
provoke the issue by upgrading the systemd package, so I suspect it's part of
the packaging in the upgrade process.
---
ProblemType: Bug
[Touch-packages] [Bug 1895360] Re: Terminal (and other default Ubuntu apps) won't launch due to missing libffi.so.7 in 20.10
sudo pip uninstall PyGObject did it for me... I have no idea why it was installed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1895360 Title: Terminal (and other default Ubuntu apps) won't launch due to missing libffi.so.7 in 20.10 Status in libffi package in Ubuntu: Invalid Bug description: When I launch Terminal, I see the following error (st and urxvt are still launchable, as are Discord and Spotify, among others): Sep 11 18:22:39 arctic systemd[1918]: Started Application launched by gnome-shell. Sep 11 18:22:39 arctic gnome-shell[2191]: g_variant_unref: assertion 'value != NULL' failed Sep 11 18:22:39 arctic gnome-shell[2191]: g_variant_unref: assertion 'value != NULL' failed Sep 11 18:22:39 arctic gnome-shell[18808]: Traceback (most recent call last): Sep 11 18:22:39 arctic gnome-shell[18808]: File "/usr/bin/gnome-terminal", line 9, in Sep 11 18:22:39 arctic gnome-shell[18808]: from gi.repository import GLib, Gio Sep 11 18:22:39 arctic gnome-shell[18808]: File "/home/alichtman/.local/lib/python3.8/site-packages/gi/__init__.py", line 42, in Sep 11 18:22:39 arctic gnome-shell[18808]: from . import _gi Sep 11 18:22:39 arctic gnome-shell[18808]: ImportError: libffi.so.7: cannot open shared object file: No such file or directory And then Terminal never launches. libffi.so.8 is found in /usr/lib/x86_64-linux-gnu/, but libffi.so.7 is missing. $ lsb_release -rd Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1895360/+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 1903756] [NEW] show application showing overview instead of showing application
Public bug reported: unable to click on running apps and have to lockout to restart the gnome-shell,ctrl + alt f2 to restart the gnome-shell doesn't effects dash show application showing overview instead of showing application could be the kernel issues since upgrading to 5.4.0-52-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nano 4.8-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 00:43:36 2020 SourcePackage: nano UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nano (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: - unable to click on running apps and have to lockout to restart the gnome-shell,ctrl + alt f2 to restart the gnome-shell doesn't effects dash show application showing overview instead of showing application could be the kernel issues since upgrading to ``` uname -r - 5.4.0-52-generic ``` + unable to click on running apps and have to lockout to restart the + gnome-shell,ctrl + alt f2 to restart the gnome-shell doesn't effects + dash show application showing overview instead of showing application + could be the kernel issues since upgrading to 5.4.0-52-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nano 4.8-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 00:43:36 2020 SourcePackage: nano UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1903756 Title: show application showing overview instead of showing application Status in nano package in Ubuntu: New Bug description: unable to click on running apps and have to lockout to restart the gnome-shell,ctrl + alt f2 to restart the gnome-shell doesn't effects dash show application showing overview instead of showing application could be the kernel issues since upgrading to 5.4.0-52-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nano 4.8-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 00:43:36 2020 SourcePackage: nano UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1903756/+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
Thanks guys for all the work. -- 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: Fix Committed 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 * sudo add-apt-repository ppa:waveform/pi-bluetooth * 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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
Test case works perfectly on the Pi400. -- 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: Fix Committed 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 * sudo add-apt-repository ppa:waveform/pi-bluetooth * 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 1895360] Re: Terminal (and other default Ubuntu apps) won't launch due to missing libffi.so.7 in 20.10
How does one remove them? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1895360 Title: Terminal (and other default Ubuntu apps) won't launch due to missing libffi.so.7 in 20.10 Status in libffi package in Ubuntu: Invalid Bug description: When I launch Terminal, I see the following error (st and urxvt are still launchable, as are Discord and Spotify, among others): Sep 11 18:22:39 arctic systemd[1918]: Started Application launched by gnome-shell. Sep 11 18:22:39 arctic gnome-shell[2191]: g_variant_unref: assertion 'value != NULL' failed Sep 11 18:22:39 arctic gnome-shell[2191]: g_variant_unref: assertion 'value != NULL' failed Sep 11 18:22:39 arctic gnome-shell[18808]: Traceback (most recent call last): Sep 11 18:22:39 arctic gnome-shell[18808]: File "/usr/bin/gnome-terminal", line 9, in Sep 11 18:22:39 arctic gnome-shell[18808]: from gi.repository import GLib, Gio Sep 11 18:22:39 arctic gnome-shell[18808]: File "/home/alichtman/.local/lib/python3.8/site-packages/gi/__init__.py", line 42, in Sep 11 18:22:39 arctic gnome-shell[18808]: from . import _gi Sep 11 18:22:39 arctic gnome-shell[18808]: ImportError: libffi.so.7: cannot open shared object file: No such file or directory And then Terminal never launches. libffi.so.8 is found in /usr/lib/x86_64-linux-gnu/, but libffi.so.7 is missing. $ lsb_release -rd Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1895360/+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 1268210] Re: unity-scopes-runner: Typo in package description: "scoped"
** Changed in: libunity Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1268210 Title: unity-scopes-runner: Typo in package description: "scoped" Status in Package Descriptions for Ubuntu: Triaged Status in libunity: Fix Committed Status in libunity package in Ubuntu: Confirmed Bug description: Package: unity-scopes-runner Version: 7.1.3+14.04.20131106-0ubuntu1 Hello, The package description contains a small typo, I think: The scope runner is a handy tool for wrapping on a desktop the various scoped installed on the system. Should be: The scope runner is a handy tool for wrapping on a desktop the various scopes installed on the system. in the string #16945 https://translations.launchpad.net/ddtp-ubuntu/trusty/+pots/ddtp-ubuntu-main/fr/16945 Regards, Pascal To manage notifications about this bug go to: https://bugs.launchpad.net/ddtp-ubuntu/+bug/1268210/+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 1901742] Re: systemd-modules-load.service fails to start because it can't understand module arguments in /etc/modules, which it shouldn't even be reading
I marked this as affecting kmod in bionic, but I don't think a manpage correction is worth an SRU for kmod. Possibly we could queue up this to ship with some other actual bugfix, or we could upload it with block- proposed-bionic to hold it in proposed until some other bugfix comes along. ** Description changed: + [impact] + + 'man modules' claims that modules options can be provided in the + /etc/modules file, but doing so causes systemd-modules-load.service to + fail + + [test case] + + add a module with at least one option to the /etc/modules file and + restart systemd-modules-load + + see original description for more detail and example of service failure + + [regression potential] + + as this only changes a manpage, any regression would likely be in + incorrect information provided to users, or some regression occurring + due to replacement of the man file or upgrading of the package + + [scope] + + This was fixed in Debian by + https://salsa.debian.org/md/kmod/-/commit/676cb532b51be28cc19be6dd7fd8593ea5958e24 + + This is fixed already in Ubuntu focal and later. + + [other info] + + as this is a manpage-only correction, if this is sru'ed it should use + block-proposed-bionic, or just be bundled with a real bugfix. + + [original description] + My systemd-modules-load.service fails to start like this: ● systemd-modules-load.service - Load Kernel Modules -Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled) -Active: failed (Result: exit-code) since Tue 2020-10-27 10:24:52 PDT; 4s ago - Docs: man:systemd-modules-load.service(8) -man:modules-load.d(5) - Process: 23683 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) - Main PID: 23683 (code=exited, status=1/FAILURE) + Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled) + Active: failed (Result: exit-code) since Tue 2020-10-27 10:24:52 PDT; 4s ago + Docs: man:systemd-modules-load.service(8) + man:modules-load.d(5) + Process: 23683 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) + Main PID: 23683 (code=exited, status=1/FAILURE) Oct 27 10:24:52 octagon systemd[1]: Starting Load Kernel Modules... Oct 27 10:24:52 octagon systemd-modules-load[23683]: Failed to find module 'vfio vfio_iommu_type1 vfio_pci vfio_virqfd' Oct 27 10:24:52 octagon systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE Oct 27 10:24:52 octagon systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. Oct 27 10:24:52 octagon systemd[1]: Failed to start Load Kernel Modules. It looks like it's trying to interpret a whole module-and-arguments string as just a module name, and failing to load this. By recursive grep of /etc, the only place it can be getting that string is /etc/modules: $ sudo ag vfio_iommu_type1 - [sudo] password for anovak: + [sudo] password for anovak: modules 5:vfio vfio_iommu_type1 vfio_pci vfio_virqfd The manpage for /etc/modules clearly says that the file may contain module names *and* arguments: [anovak@octagon ~]$ man modules | grep Arguments -The /etc/modules file contains the names of kernel modules that are to be loaded at boot time, one per line. Arguments can be given in the same line as the module name. Lines beginning with a + The /etc/modules file contains the names of kernel modules that are to be loaded at boot time, one per line. Arguments can be given in the same line as the module name. Lines beginning with a The manpage for systemd-modules-load.service doesn't mention /etc/modules, and says to see the manpage for modules-load.d(5). That manpage says that it only reads files from specific directories: SYNOPSIS -/etc/modules-load.d/*.conf + /etc/modules-load.d/*.conf -/run/modules-load.d/*.conf + /run/modules-load.d/*.conf -/usr/lib/modules-load.d/*.conf + /usr/lib/modules-load.d/*.conf The manpage is clearly lying, and systemd-modules-load.service is clearly also reading /etc/modules. Moreover, it's misreading it, and not interpreting it according to the documented semantics of /etc/modules. I was induced to create an /etc/modules like this by https://mathiashueber.com/windows-virtual-machine-gpu-passthrough- ubuntu/ but I'm not sure that it's actually getting used by anything, because lsmod shows some but not all of the options I specified. [anovak@octagon etc]$ lsmod | grep "^vfio " vfio 28672 2 vfio_iommu_type1,vfio_pci Can systemd be made to stop reading /etc/modules so that it doesn't report failure when it doesn't understand lines with options? And is that file being read by something else in the system, or should I just remove it as a workaround to stop upsetting systemd?
[Touch-packages] [Bug 1901742] Re: systemd-modules-load.service fails to start because it can't understand module arguments in /etc/modules, which it shouldn't even be reading
This is only a manpage error; options are no longer supported in the /etc/modules file. This was fixed in Debian by https://salsa.debian.org/md/kmod/-/commit/676cb532b51be28cc19be6dd7fd8593ea5958e24 This is fixed already in Ubuntu focal and later. ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: kmod (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Bionic) Status: New => Invalid ** Changed in: kmod (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1901742 Title: systemd-modules-load.service fails to start because it can't understand module arguments in /etc/modules, which it shouldn't even be reading Status in kmod package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in kmod source package in Bionic: New Status in systemd source package in Bionic: Invalid Bug description: [impact] 'man modules' claims that modules options can be provided in the /etc/modules file, but doing so causes systemd-modules-load.service to fail [test case] add a module with at least one option to the /etc/modules file and restart systemd-modules-load see original description for more detail and example of service failure [regression potential] as this only changes a manpage, any regression would likely be in incorrect information provided to users, or some regression occurring due to replacement of the man file or upgrading of the package [scope] This was fixed in Debian by https://salsa.debian.org/md/kmod/-/commit/676cb532b51be28cc19be6dd7fd8593ea5958e24 This is fixed already in Ubuntu focal and later. [other info] as this is a manpage-only correction, if this is sru'ed it should use block-proposed-bionic, or just be bundled with a real bugfix. [original description] My systemd-modules-load.service fails to start like this: ● systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2020-10-27 10:24:52 PDT; 4s ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 23683 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) Main PID: 23683 (code=exited, status=1/FAILURE) Oct 27 10:24:52 octagon systemd[1]: Starting Load Kernel Modules... Oct 27 10:24:52 octagon systemd-modules-load[23683]: Failed to find module 'vfio vfio_iommu_type1 vfio_pci vfio_virqfd' Oct 27 10:24:52 octagon systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE Oct 27 10:24:52 octagon systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. Oct 27 10:24:52 octagon systemd[1]: Failed to start Load Kernel Modules. It looks like it's trying to interpret a whole module-and-arguments string as just a module name, and failing to load this. By recursive grep of /etc, the only place it can be getting that string is /etc/modules: $ sudo ag vfio_iommu_type1 [sudo] password for anovak: modules 5:vfio vfio_iommu_type1 vfio_pci vfio_virqfd The manpage for /etc/modules clearly says that the file may contain module names *and* arguments: [anovak@octagon ~]$ man modules | grep Arguments The /etc/modules file contains the names of kernel modules that are to be loaded at boot time, one per line. Arguments can be given in the same line as the module name. Lines beginning with a The manpage for systemd-modules-load.service doesn't mention /etc/modules, and says to see the manpage for modules-load.d(5). That manpage says that it only reads files from specific directories: SYNOPSIS /etc/modules-load.d/*.conf /run/modules-load.d/*.conf /usr/lib/modules-load.d/*.conf The manpage is clearly lying, and systemd-modules-load.service is clearly also reading /etc/modules. Moreover, it's misreading it, and not interpreting it according to the documented semantics of /etc/modules. I was induced to create an /etc/modules like this by https://mathiashueber.com/windows-virtual-machine-gpu-passthrough- ubuntu/ but I'm not sure that it's actually getting used by anything, because lsmod shows some but not all of the options I specified. [anovak@octagon etc]$ lsmod | grep "^vfio " vfio 28672 2 vfio_iommu_type1,vfio_pci Can systemd be made to stop reading /etc/modules so that it doesn't report failure when it doesn't understand lines with options? And is that file being read by something else in the system, or should I just remove it as a workaround
Re: [Touch-packages] [Bug 1902898] Re: power-button action inconsistent between user session and greeter
On Tue, Nov 10, 2020 at 7:45 AM Sebastien Bacher <1902...@bugs.launchpad.net> wrote: > > is it important enough to justify doing the SRU work? >From my myopic (server-oriented) point-of-view, changing the default in 20.04 to prompt is a good idea. I've found that users often install Ubuntu Desktop on their server-class hardware, using their BMC virtual KVM as a head. These systems tend to support suspend, but suspend rarely works well. Some systems will go to sleep just fine - but have no way to wake them up[*]. Others will try to suspend, only to immediately come back out of suspend (presumably after trying to sleep a device that doesn't support it), so it looks like the system failed to react at all. Both seem like a non-intuitive reaction to an "IPMI power off soft" command. [*] https://bugs.launchpad.net/bugs/1862559 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1902898 Title: power-button action inconsistent between user session and greeter Status in ubuntu-settings package in Ubuntu: Confirmed Status in ubuntu-settings source package in Focal: Incomplete Status in ubuntu-settings source package in Groovy: Incomplete Status in ubuntu-settings source package in Hirsute: Confirmed Bug description: When a user is logged in to the Ubuntu desktop, a power button event will cause the user to be prompted to choose if they'd like to proceed with a shutdown. However, if the system is sitting at a greeter screen, a power button event will instead attempt a suspend w/o prompting. This is due to a different set of defaults for the greeter and the user: For a logged-in desktop user, they see: $ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'interactive' But the gdm user sees: $ sudo machinectl shell gdm@ /bin/bash Connected to the local host. Press ^] three times within 1s to exit session. gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'suspend' Changing the gdm user's setting to "interactive" using gsettings causes the greeter to begin prompting, consistent with the logged in user experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1902898/+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 1894329] Re: ZFS revert from grub menu not working.
Patch for Focal.
** Patch added: "zfs-linux_0.8.3-1ubuntu12.4_0.8.3-1ubuntu12.5.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1894329/+attachment/5433047/+files/zfs-linux_0.8.3-1ubuntu12.4_0.8.3-1ubuntu12.5.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
In Progress
Status in coreutils source package in Focal:
Incomplete
Status in zfs-linux source package in Focal:
Triaged
Status in coreutils source package in Groovy:
Incomplete
Status in zfs-linux source package in Groovy:
Triaged
Bug description:
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+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 1903351] Re: ignore_eacces and ignore_erofs patches don't work properly
if focal needs a separate debdiff for it to get applied on that branch, let me know. focal is in need of other updates like the .tarball-version fix included in -5 in upstream debian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1903351 Title: ignore_eacces and ignore_erofs patches don't work properly Status in procps package in Ubuntu: Confirmed Bug description: The patches used to ignore errors in containers no longer work as of 3.3.16 due to upstream commit https://gitlab.com/procps- ng/procps/-/commit/7af88da373bb4d515a98ec2f0f5d56c63904f932 The ignore_eacces patch was fuzzed and gets applied to ReadSetting, not WriteSetting Both patches ignore the change that rc is no longer propagated up and instead everything is trapped by: if (!ignore_failure && errno != ENOENT) rc = -1; Versions affected: focal+ root@bfee89058713:/tmp# cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy root@bfee89058713:/# dpkg -l procps 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 procps 2:3.3.16-5ubuntu2 amd64/proc file system utilities root@bfee89058713:/# echo "kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 255 root@bfee89058713:/# echo "-kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1903351/+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 1894329] Re: ZFS revert from grub menu not working.
Patch for 20.10.
** Patch added: "zfs-linux_0.8.4-1ubuntu11_0.8.4-1ubuntu11.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1894329/+attachment/5433041/+files/zfs-linux_0.8.4-1ubuntu11_0.8.4-1ubuntu11.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
In Progress
Status in coreutils source package in Focal:
Incomplete
Status in zfs-linux source package in Focal:
Triaged
Status in coreutils source package in Groovy:
Incomplete
Status in zfs-linux source package in Groovy:
Triaged
Bug description:
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+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
Thanks for the work but it there any work to upstream those changes? I'm not happy to carry a sleep(1) hack in our package unless there is a strong reason and we are working on a way to replace it by a better solution -- 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: Fix Committed 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 * sudo add-apt-repository ppa:waveform/pi-bluetooth * 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 1903723] [NEW] Audio dropouts and general surround sound issues. Device shown as ALC887-VD Analog instead of ALC1220 as per motherboard specifications [AB350-Gaming, Realtek ALC8
Public bug reported: Audio dropouts and general surround sound issues. Incorrect ALC device shown from cat /proc/asound/card1/pcm0c/info card: 1 device: 0 subdevice: 0 stream: CAPTURE id: ALC887-VD Analog name: ALC887-VD Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 Device should be shown as ALC1220 as per Motherboard (Gigabyte AB350 Gaming 3) Specifications. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-lowlatency 5.4.65 Uname: Linux 5.4.0-52-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: billy 9531 F pulseaudio /dev/snd/controlC2: billy 9531 F pulseaudio /dev/snd/controlC1: billy 9531 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 15:05:30 2020 InstallationDate: Installed on 2020-11-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Line Out, Rear Symptom_PulseAudioLog: Nov 10 14:37:41 AMI-Buntu dbus-daemon[882]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=1000 pid=1083 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Nov 10 14:37:43 AMI-Buntu dbus-daemon[882]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.41' (uid=1000 pid=1083 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Nov 10 14:57:06 AMI-Buntu dbus-daemon[882]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.341' (uid=1000 pid=9531 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [AB350-Gaming, Realtek ALC887-VD, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23d dmi.board.asset.tag: Default string dmi.board.name: AB350-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23d:bd04/17/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-11-10T14:56:54.599621 ** 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/1903723 Title: Audio dropouts and general surround sound issues. Device shown as ALC887-VD Analog instead of ALC1220 as per motherboard specifications [AB350-Gaming, Realtek ALC887-VD, Green Line Out, Rear] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Audio dropouts and general surround sound issues. Incorrect ALC device shown from cat /proc/asound/card1/pcm0c/info card: 1 device: 0 subdevice: 0 stream: CAPTURE id: ALC887-VD Analog name: ALC887-VD Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 Device should be shown as ALC1220 as per Motherboard (Gigabyte AB350 Gaming 3) Specifications. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-lowlatency 5.4.65 Uname: Linux 5.4.0-52-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: billy 9531 F pulseaudio /dev/snd/controlC2: billy 9531 F pulseaudio /dev/snd/controlC1: billy 9531 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 15:05:30 2020 InstallationDate: Installed on 2020-11-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage:
[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Committed -- 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: Fix Committed 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 * sudo add-apt-repository ppa:waveform/pi-bluetooth * 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 1903351] Re: ignore_eacces and ignore_erofs patches don't work properly
** Tags added: rls-gg-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1903351 Title: ignore_eacces and ignore_erofs patches don't work properly Status in procps package in Ubuntu: Confirmed Bug description: The patches used to ignore errors in containers no longer work as of 3.3.16 due to upstream commit https://gitlab.com/procps- ng/procps/-/commit/7af88da373bb4d515a98ec2f0f5d56c63904f932 The ignore_eacces patch was fuzzed and gets applied to ReadSetting, not WriteSetting Both patches ignore the change that rc is no longer propagated up and instead everything is trapped by: if (!ignore_failure && errno != ENOENT) rc = -1; Versions affected: focal+ root@bfee89058713:/tmp# cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy root@bfee89058713:/# dpkg -l procps 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 procps 2:3.3.16-5ubuntu2 amd64/proc file system utilities root@bfee89058713:/# echo "kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 255 root@bfee89058713:/# echo "-kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1903351/+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 1902710] Re: [SRU] Enable support for Wallaby Cloud Archive
** Changed in: software-properties (Ubuntu Hirsute) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1902710 Title: [SRU] Enable support for Wallaby Cloud Archive Status in software-properties package in Ubuntu: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Committed Bug description: Please add support for: cloud-archive:wallaby cloud-archive:wallaby-proposed This will also need to be SRU'd back to focal. [Impact] End users have to manually enable the wallaby cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:wallaby sudo add-apt-repository cloud-archive:wallaby-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1902710/+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 1902898] Re: power-button action inconsistent between user session and greeter
is it important enough to justify doing the SRU work? ** Changed in: ubuntu-settings (Ubuntu Groovy) Status: New => Confirmed ** Changed in: ubuntu-settings (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: ubuntu-settings (Ubuntu Focal) Importance: Undecided => Low ** Changed in: ubuntu-settings (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: ubuntu-settings (Ubuntu Hirsute) Importance: Undecided => Low ** Tags removed: rls-hh-incoming ** Changed in: ubuntu-settings (Ubuntu Focal) Assignee: (unassigned) => Didier Roche (didrocks) ** Changed in: ubuntu-settings (Ubuntu Groovy) Assignee: (unassigned) => Didier Roche (didrocks) ** Changed in: ubuntu-settings (Ubuntu Hirsute) Assignee: (unassigned) => Didier Roche (didrocks) ** Changed in: ubuntu-settings (Ubuntu Groovy) Status: Confirmed => Incomplete ** Changed in: ubuntu-settings (Ubuntu Focal) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1902898 Title: power-button action inconsistent between user session and greeter Status in ubuntu-settings package in Ubuntu: Confirmed Status in ubuntu-settings source package in Focal: Incomplete Status in ubuntu-settings source package in Groovy: Incomplete Status in ubuntu-settings source package in Hirsute: Confirmed Bug description: When a user is logged in to the Ubuntu desktop, a power button event will cause the user to be prompted to choose if they'd like to proceed with a shutdown. However, if the system is sitting at a greeter screen, a power button event will instead attempt a suspend w/o prompting. This is due to a different set of defaults for the greeter and the user: For a logged-in desktop user, they see: $ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'interactive' But the gdm user sees: $ sudo machinectl shell gdm@ /bin/bash Connected to the local host. Press ^] three times within 1s to exit session. gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'suspend' Changing the gdm user's setting to "interactive" using gsettings causes the greeter to begin prompting, consistent with the logged in user experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1902898/+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 295990] Re: Keyboard layout reset after attaching USB keyboard
@scheleaap: Please don't talk on a 12 years old and closed bug report. You are probably experiencing bug #1899206. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/295990 Title: Keyboard layout reset after attaching USB keyboard Status in xserver-xorg-input-evdev: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in xkeyboard-config package in Ubuntu: Invalid Bug description: Binary package hint: gnome-control-center I use a laptop with Ubuntu 8.10, and has configured two keyboard layouts. I use "USA" as the default layout and "Sweden" as an alternative layout, and use for changing layout. 1) Description: Ubuntu 8.10 Release: 8.10 2) gnome-control-center: Installed: 1:2.24.0.1-0ubuntu7.1 Candidate: 1:2.24.0.1-0ubuntu7.1 Version table: *** 1:2.24.0.1-0ubuntu7.1 0 500 http://se.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 1:2.24.0.1-0ubuntu7 0 500 http://se.archive.ubuntu.com intrepid/main Packages 3) When I plug in an USB keyboard it should still be possible to change between the default and alternative layout with or using the applet menu. The default and any alternative layout should user configurable, i.e. it should not restore system default values when an USB keyboard is attached. 4) When I plug in an USB keyboard after logging in to Ubuntu, it resets the keyboard layout (and probably other keyboard settings as well) to the system default layout which is stored in /etc/default/console-setup. To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/295990/+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 1901090] Re: run-parts: failed to stat component /etc/network/if-post-down.d/avahi-daemon: No such file or directory
The target file was removed in https://launchpad.net/ubuntu/+source/avahi/0.7-4ubuntu7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1901090 Title: run-parts: failed to stat component /etc/network/if-post-down.d/avahi- daemon: No such file or directory Status in avahi package in Ubuntu: Fix Committed Bug description: avahi-daemon 0.7-4ubuntu7 installs a symlink /etc/network/if-post- down.d/avahi-daemon -> ../if-up.d/avahi-daemon but doesn't install the symlink target /etc/network/if-up.d/avahi-daemon That makes ifdown complain: $ sudo ifdown enp2s0f3 run-parts: failed to stat component /etc/network/if-post-down.d/avahi-daemon: No such file or directory The problem only occurs if avahi-daemon is installed from scratch; if it is upgraded from older versions, the missing file is still there according to this line in /var/lib/dpkg/status: /etc/network/if-up.d/avahi-daemon 6dbf1a91ab420a99d1205972d6401e67 obsolete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1901090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1903396] Re: libnl-route-3-200 unresolved symbols
linux-vdso.so.1 (0x7ffcf0521000) libnl-3.so.200 => /lib/x86_64-linux-gnu/libnl-3.so.200 (0x7f5a697da000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f5a697b7000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f5a695c5000) /lib64/ld-linux-x86-64.so.2 (0x7f5a698a) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1903396 Title: libnl-route-3-200 unresolved symbols Status in libnl3 package in Ubuntu: Incomplete Bug description: $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" $ arch x86_64 Getting a link error when trying to build Wireshark from source on Ubuntu Focal. I need to build Wireshark for plugin development. Steps to reproduce: 1. Obtain source code from https://gitlab.com/wireshark/wireshark 2. Install build dependencies as per CI ./tools/debian-setup.sh --install-optional --install-test-deps -y 3. mkdir build 4. cmake .. 5. make 6. Observer error: [ 88%] Linking CXX executable run/wireshark /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nla_get_s32' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nl_strerror_l' collect2: error: ld returned 1 exit status make[2]: *** [CMakeFiles/wireshark.dir/build.make:567: run/wireshark] Error 1 make[1]: *** [CMakeFiles/Makefile2:3713: CMakeFiles/wireshark.dir/all] Error 2 make: *** [Makefile:141: all] Error 2 Those two symbols are not present in any of the other libnl libraries, static or dynamic. /usr/include/libnl3/netlink/attr.h:119:extern int32_t nla_get_s32(const struct nlattr *); $ dpkg -S /usr/include/libnl3/netlink/attr.h libnl-3-dev:amd64: /usr/include/libnl3/netlink/attr.h $ dpkg -S /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 libnl-route-3-200:amd64: /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 I can build and install libnl-3.2.25 from source and I don't get the linking issues anymore if I replace the .so files installed by the .debs, so it's possible that there is soemthing wrong with the packaging of libnl-route-3-200.deb. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1903396/+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 1901090] Re: run-parts: failed to stat component /etc/network/if-post-down.d/avahi-daemon: No such file or directory
Thank you for your bug report, indeed that's a leftover symlink and the files are not cleaned on upgrade ** Changed in: avahi (Ubuntu) Importance: Undecided => Low ** Changed in: avahi (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1901090 Title: run-parts: failed to stat component /etc/network/if-post-down.d/avahi- daemon: No such file or directory Status in avahi package in Ubuntu: Fix Committed Bug description: avahi-daemon 0.7-4ubuntu7 installs a symlink /etc/network/if-post- down.d/avahi-daemon -> ../if-up.d/avahi-daemon but doesn't install the symlink target /etc/network/if-up.d/avahi-daemon That makes ifdown complain: $ sudo ifdown enp2s0f3 run-parts: failed to stat component /etc/network/if-post-down.d/avahi-daemon: No such file or directory The problem only occurs if avahi-daemon is installed from scratch; if it is upgraded from older versions, the missing file is still there according to this line in /var/lib/dpkg/status: /etc/network/if-up.d/avahi-daemon 6dbf1a91ab420a99d1205972d6401e67 obsolete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1901090/+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
** Description changed: + [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 + * sudo add-apt-repository ppa:waveform/pi-bluetooth + * 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. -- 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: Confirmed 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 * sudo add-apt-repository ppa:waveform/pi-bluetooth * 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 295990] Re: Keyboard layout reset after attaching USB keyboard
Update: The problem does not occur when I use Wayland instead of X. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/295990 Title: Keyboard layout reset after attaching USB keyboard Status in xserver-xorg-input-evdev: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in xkeyboard-config package in Ubuntu: Invalid Bug description: Binary package hint: gnome-control-center I use a laptop with Ubuntu 8.10, and has configured two keyboard layouts. I use "USA" as the default layout and "Sweden" as an alternative layout, and use for changing layout. 1) Description: Ubuntu 8.10 Release: 8.10 2) gnome-control-center: Installed: 1:2.24.0.1-0ubuntu7.1 Candidate: 1:2.24.0.1-0ubuntu7.1 Version table: *** 1:2.24.0.1-0ubuntu7.1 0 500 http://se.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 1:2.24.0.1-0ubuntu7 0 500 http://se.archive.ubuntu.com intrepid/main Packages 3) When I plug in an USB keyboard it should still be possible to change between the default and alternative layout with or using the applet menu. The default and any alternative layout should user configurable, i.e. it should not restore system default values when an USB keyboard is attached. 4) When I plug in an USB keyboard after logging in to Ubuntu, it resets the keyboard layout (and probably other keyboard settings as well) to the system default layout which is stored in /etc/default/console-setup. To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/295990/+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 1894329] Re: ZFS revert from grub menu not working.
This is the patch from Usarin Heininga applied against Hirsute.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
In Progress
Status in coreutils source package in Focal:
Incomplete
Status in zfs-linux source package in Focal:
Triaged
Status in coreutils source package in Groovy:
Incomplete
Status in zfs-linux source package in Groovy:
Triaged
Bug description:
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+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 1894329] Re: ZFS revert from grub menu not working.
** Patch added: "zfs-linux_0.8.4-1ubuntu13_0.8.4-1ubuntu14.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1894329/+attachment/5433026/+files/zfs-linux_0.8.4-1ubuntu13_0.8.4-1ubuntu14.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1894329
Title:
ZFS revert from grub menu not working.
Status in coreutils package in Ubuntu:
Incomplete
Status in zfs-linux package in Ubuntu:
In Progress
Status in coreutils source package in Focal:
Incomplete
Status in zfs-linux source package in Focal:
Triaged
Status in coreutils source package in Groovy:
Incomplete
Status in zfs-linux source package in Groovy:
Triaged
Bug description:
@coreutils maintainers, any idea why dd is being flagged as having an
executable stack?
When I try to revert to a previous state from the grub menu, the boot
fails. The system drops me to a repair modus.
zfs-mount-generator fails with the message:
couldn't ensure boot: Mounted clone bootFS dataset created by initramfs
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".
After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed
without a suffix.
After a little investigation I found the problem in
/usr/share/initramfs-tools/scripts/zfs at the end in function
uid()
{
dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc
'a-z0-9' | cut -c-6
}, the dd command fails during boot with the message "process 'dd' started
with executable stack.
After this an empty uid is returned which explains the dataset without a
proper suffix.
Replacing the function with:
uid()
{
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
}
fixes the problem.
Ubuntu version is:
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
zfs-initramfs version is:
0.8.4-1ubuntu11
With regards,
Usarin Heininga
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: zfs-initramfs 0.8.4-1ubuntu11
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 4 20:23:44 2020
InstallationDate: Installed on 2020-09-02 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=nl_NL.UTF-8
SHELL=/bin/bash
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1894329/+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 295990] Re: Keyboard layout reset after attaching USB keyboard
I have started to experience this bug after upgrading from Ubuntu 18.04 to 20.04. Whenever I remove my external keyboard and plug it back in, the external keyboard's layout switches to US English instead of whatever it was set to. The laptop's built-in keyboard layout remains correct. I did not notice any warnings in my logs. If you need more information / debug output, I'd be glad to help. Some details: * Laptop: Lenovo T480 * OS: Ubuntu 20.04 * External keyboard: Das Keyboard 4 Professional (model no.: DASK4MKPROSIL-3G7-r1.2) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/295990 Title: Keyboard layout reset after attaching USB keyboard Status in xserver-xorg-input-evdev: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in xkeyboard-config package in Ubuntu: Invalid Bug description: Binary package hint: gnome-control-center I use a laptop with Ubuntu 8.10, and has configured two keyboard layouts. I use "USA" as the default layout and "Sweden" as an alternative layout, and use for changing layout. 1) Description: Ubuntu 8.10 Release: 8.10 2) gnome-control-center: Installed: 1:2.24.0.1-0ubuntu7.1 Candidate: 1:2.24.0.1-0ubuntu7.1 Version table: *** 1:2.24.0.1-0ubuntu7.1 0 500 http://se.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 1:2.24.0.1-0ubuntu7 0 500 http://se.archive.ubuntu.com intrepid/main Packages 3) When I plug in an USB keyboard it should still be possible to change between the default and alternative layout with or using the applet menu. The default and any alternative layout should user configurable, i.e. it should not restore system default values when an USB keyboard is attached. 4) When I plug in an USB keyboard after logging in to Ubuntu, it resets the keyboard layout (and probably other keyboard settings as well) to the system default layout which is stored in /etc/default/console-setup. To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/295990/+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
** Summary changed: - Bluetooth won't activate on the pi 400 + [SRU] Bluetooth won't activate on the pi 400 -- 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: Confirmed Bug 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 1903048] Re: Bluetooth won't activate on the pi 400
Ok, I was asked to sponsor it, so I'm pushing the changes to hirsute and groovy. I have filled MPs for both for the bluez repo (no write access). Also, a hirsute branch needs to be opened, so the first MP is for now only targeting groovy (invalidly): https://code.launchpad.net/~sil2100/bluez/+git/bluez/+merge/393548 https://code.launchpad.net/~sil2100/bluez/+git/bluez/+merge/393549 Cheers. -- 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: Confirmed Bug 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 1903396] Re: libnl-route-3-200 unresolved symbols
Thank you for your bug report, could you provide the output of that command on a system having the issue? $ ldd -r /usr/lib/x86_64-linux-gnu/libnl-route-3.so what version of the library is installed? ** Changed in: libnl3 (Ubuntu) Importance: Undecided => Low ** Changed in: libnl3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1903396 Title: libnl-route-3-200 unresolved symbols Status in libnl3 package in Ubuntu: Incomplete Bug description: $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" $ arch x86_64 Getting a link error when trying to build Wireshark from source on Ubuntu Focal. I need to build Wireshark for plugin development. Steps to reproduce: 1. Obtain source code from https://gitlab.com/wireshark/wireshark 2. Install build dependencies as per CI ./tools/debian-setup.sh --install-optional --install-test-deps -y 3. mkdir build 4. cmake .. 5. make 6. Observer error: [ 88%] Linking CXX executable run/wireshark /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nla_get_s32' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nl_strerror_l' collect2: error: ld returned 1 exit status make[2]: *** [CMakeFiles/wireshark.dir/build.make:567: run/wireshark] Error 1 make[1]: *** [CMakeFiles/Makefile2:3713: CMakeFiles/wireshark.dir/all] Error 2 make: *** [Makefile:141: all] Error 2 Those two symbols are not present in any of the other libnl libraries, static or dynamic. /usr/include/libnl3/netlink/attr.h:119:extern int32_t nla_get_s32(const struct nlattr *); $ dpkg -S /usr/include/libnl3/netlink/attr.h libnl-3-dev:amd64: /usr/include/libnl3/netlink/attr.h $ dpkg -S /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 libnl-route-3-200:amd64: /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 I can build and install libnl-3.2.25 from source and I don't get the linking issues anymore if I replace the .so files installed by the .debs, so it's possible that there is soemthing wrong with the packaging of libnl-route-3-200.deb. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1903396/+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 1876726] Re: software-properties-gtk crashes: dbus.proxies error
Thank you for your bug report, how did you install python3.7? ** Changed in: software-properties (Ubuntu) Importance: Undecided => Low ** Changed in: software-properties (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1876726 Title: software-properties-gtk crashes: dbus.proxies error Status in software-properties package in Ubuntu: Incomplete Bug description: Expected: software-properties-gtk should launch properly; instead it crashes and doesn't launch. Out of the blue, I couldn't open Software so I checked the output of software-properties-gtk which is: ``` WARNING:root:system-image-cli failed, using defaults: [Errno 13] Permission denied: 'system-ima WARNING:root:system-image-cli failed, using defaults: [Errno 13] Permission denied: 'system-ima ERROR:dbus.proxies:Introspect error on :1.159:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 172, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.159 was not provided by any .service files ``` If I launch it with sudo I get circa the same output: ``` ERROR:dbus.proxies:Introspect error on :1.167:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 172, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.167 was not provided by any .service files ``` Additional info: $ uname -r `5.3.0-51-generic` $ dpkg -l software-properties-gtk | grep ii ``` ii software-properties-gtk 0.96.24.32.12 all manage the repositories that you install software from (gtk) ``` $ apt-cache policy software-properties-gtk ``` software-properties-gtk: Installed: 0.96.24.32.12 Candidate: 0.96.24.32.12 Version table: *** 0.96.24.32.12 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 0.96.24.32.1 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu bionic/main i386 Packages ``` Release: Ubuntu 18.04.4 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1876726/+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 1903468] Re: Endless "Cache Refresh" on Software Update settings change
Thank you for your bug report, was it a one time issue of does it keep doing it? Could you include the 'journalctl -b ' log from a session where you hit the issue? ** Changed in: software-properties (Ubuntu) Importance: Undecided => Low ** Changed in: software-properties (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1903468 Title: Endless "Cache Refresh" on Software Update settings change Status in software-properties package in Ubuntu: Incomplete Bug description: After reapplying some of the checkboxes under "Software & Updates" -> "Other Software" after distro upgrade, a window with title "Cache Refresh" pops and never disappears. (check screenshot bellow) > lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 9 01:55:13 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2015-06-17 (1971 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-09-29 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1903468/+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 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu6 --- alsa-ucm-conf (1.2.2-1ubuntu6) hirsute; urgency=medium * d/p/0001-sof-hda-dsp-add-initial-kcontrol-values.patch * d/p/0002-sof-hda-dsp-make-the-boot-init-optional-for-all-cont.patch * d/p/0003-sof-hda-dsp-Set-Master-Playback-Switch-on-in-the-Boo.patch * d/p/0004-sof-hda-dsp-Increase-the-speaker-output-volume-in-th.patch Unmute the master playback switch and increase the init output volume, otherwise the playback will be muted after freshly install the OS if the machine uses ucm to configure the audio mixers, and the init playback output volume is too low after freshly install the OS. (LP: #1901922) -- Hui Wang Mon, 09 Nov 2020 03:59:02 + ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Released Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago)
[Touch-packages] [Bug 1903468] Re: Endless "Cache Refresh" on Software Update settings change
** Description changed: - After reapplying the some of the checkboxes under "Software & Updates" - -> "Other Software" after distro upgrade, a window with title "Cache + After reapplying some of the checkboxes under "Software & Updates" -> + "Other Software" after distro upgrade, a window with title "Cache Refresh" pops and never disappears > lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 9 01:55:13 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2015-06-17 (1971 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-09-29 (40 days ago) ** Description changed: After reapplying some of the checkboxes under "Software & Updates" -> "Other Software" after distro upgrade, a window with title "Cache - Refresh" pops and never disappears + Refresh" pops and never disappears. (check screenshot bellow) > lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 9 01:55:13 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2015-06-17 (1971 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-09-29 (40 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1903468 Title: Endless "Cache Refresh" on Software Update settings change Status in software-properties package in Ubuntu: Incomplete Bug description: After reapplying some of the checkboxes under "Software & Updates" -> "Other Software" after distro upgrade, a window with title "Cache Refresh" pops and never disappears. (check screenshot bellow) > lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 9 01:55:13 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2015-06-17 (1971 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-09-29 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1903468/+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 1903668] Re: HDMI audio device disappears and is unavailble after several minutes of not being used
I only have libpipewire installed, not pipewire media server. -- 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/1903668 Title: HDMI audio device disappears and is unavailble after several minutes of not being used Status in pulseaudio package in Ubuntu: Incomplete Bug description: On system boot both of my audio devices are selectable and useable. After around 10 minutes the HDMI device just disappears and cannot be selected as output in either the task bar audio applet or in Kstart>system settings>audio(either devices or advanced tab). In the devices tab a device called Dummy output is displayed and in the advanced tab the HDMI device is shown, in this case GP107GL, with the profile in the dropdown box underneath it displaying off with no ability to switch it to on. If I go to pulse volume control>configuration i am able to select the HDMI device and the system will use it. If I play a 2 hour movie after this and then turn off the media player the HDMI device will once again disappear after about 10 minutes. When I ran ubuntu-bug the system identified the HDMI device and switched to it (it is set as default) and has remained accessable for 15 minutes now. I am running the NVIDIA 450 driver package. If I run Kubuntu 20.10 a similar problem occurs except the the profile of the device is somehow damaged but by selecting any speaker setup (profile), audio returns. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 10 16:59:24 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-24 (200 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.E0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X470 GAMING PRO CARBON (MS-7B78) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.E0:bd06/10/2020:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B78:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPROCARBON(MS-7B78):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B78 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 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/1903668/+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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu Focal) Status: New => Confirmed -- 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 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: Confirmed Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-11 source package in Focal: Fix Committed Status in mesa source package in Focal: Confirmed 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 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 1902244] Re: Backport packages for 20.04.1 HWE stack
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libclc (Ubuntu Focal) Status: New => Confirmed -- 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 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: Confirmed Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-11 source package in Focal: Fix Committed Status in mesa source package in Focal: Confirmed 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 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 1902244] Re: Backport packages for 20.04.1 HWE stack
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu Focal) Status: New => Confirmed -- 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 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: Confirmed Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-11 source package in Focal: Fix Committed Status in mesa source package in Focal: Confirmed 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 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 1727470] Re: [RFE] Automatically update the Ubuntu version strings in python-apt
** Changed in: ubuntu-translations Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1727470 Title: [RFE] Automatically update the Ubuntu version strings in python-apt Status in Ubuntu Translations: Fix Released Status in python-apt package in Ubuntu: Fix Committed Bug description: Every time there is a new Ubuntu release, some strings need to be manually translated although the only thing that is changing is the Ubuntu version and code name. Please, consider updating these strings automatically based on a translated template. It would help many translators. These strings are: Ubuntu xx.yy 'Code Name' Cdrom with Ubuntu xx.yy 'Code Name' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1727470/+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).
@dennis9771 Just get yourself Bluetooth audio card and save yourself a trouble, this will never be fixed. And you will not be able to use A2DP for conversation even if fixed. The goal of the fix is to add HFP 1.6 with mSBC 16kHz audio encoding so you have better quality during conversation. -- 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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@vanvugt Thank you for your quick response! Does that mean I would have to wait for Pulseaudio to fix this in one of their future releases (maybe v.15) or will it be possible to use an alternative soundmanager, where the kernel fixes would be sufficient to use A2DP for bidirectional bluetooth sound? Homeoffice without cableless headset is just not that comfortable :s Best Regards Dennis -- 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 1903694] Re: Sound comes out of the wrong place or not at all
A screen capture showing that I have indeed set sound to come out of internal speakers in gnome-control-center, but sound will only come out of the wireless headset. ** Attachment added: "Screenshot from 2020-11-10 12-26-39.png" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903694/+attachment/5433005/+files/Screenshot%20from%202020-11-10%2012-26-39.png -- 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/1903694 Title: Sound comes out of the wrong place or not at all Status in alsa-driver package in Ubuntu: New Bug description: Since updating to Ubuntu 20.04, I have lots of problems with sound input and output coming from the wrong device or even a device that is not turned on. For example, right now in gnome-control-center sound settings it recognizes three sound output devices - internal speakers, HDMI output and a wireless headset. The wireless headset is off and the HDMI has no speakers, but I am using a HDMI->VGA adapter that gives it the impression that there may be speakers. In gnome-control- center, I have set the internal audio to be both the input and output devices for sound. When I click on the button to test audio output, no sound is produced, but if I have pavucontrol open at the same time, I can see that it is trying to send the sound output to the wireless speakers despite the settings in gnome-control-center. Similarly, if I try to do a video conference, such as skype, sound input and output are almost always wrong. Right now, if I try skype, it will only use the headset speaker and microphone, though it will make the phone ringing sound using the internal speaker. Again, this happens regardless of what I configure the sound settings to be in the skype settings panel. With many other video conferencing applications I have similar problems. With some, I manage to go into pavucontrol and manually set the appropriate devices for input and output, but for others I am often forced to use the headset regardless of whether I want to or not. I have a number of colleagues that report similar issues when trying to use video conferencing software with Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dmk1976 F pulseaudio /dev/snd/controlC1: dmk1976 F pulseaudio /dev/snd/controlC0: dmk1976 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 12:27:57 2020 InstallationDate: Installed on 2015-08-21 (1907 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Latitude E7250, Realtek ALC3235, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to focal on 2020-06-25 (137 days ago) dmi.bios.date: 09/01/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0G9CNK dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd09/01/2015:svnDellInc.:pnLatitudeE7250:pvr:rvnDellInc.:rn0G9CNK:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7250 dmi.product.sku: 062D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903694/+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 1903694] [NEW] Sound comes out of the wrong place or not at all
Public bug reported: Since updating to Ubuntu 20.04, I have lots of problems with sound input and output coming from the wrong device or even a device that is not turned on. For example, right now in gnome-control-center sound settings it recognizes three sound output devices - internal speakers, HDMI output and a wireless headset. The wireless headset is off and the HDMI has no speakers, but I am using a HDMI->VGA adapter that gives it the impression that there may be speakers. In gnome-control-center, I have set the internal audio to be both the input and output devices for sound. When I click on the button to test audio output, no sound is produced, but if I have pavucontrol open at the same time, I can see that it is trying to send the sound output to the wireless speakers despite the settings in gnome-control-center. Similarly, if I try to do a video conference, such as skype, sound input and output are almost always wrong. Right now, if I try skype, it will only use the headset speaker and microphone, though it will make the phone ringing sound using the internal speaker. Again, this happens regardless of what I configure the sound settings to be in the skype settings panel. With many other video conferencing applications I have similar problems. With some, I manage to go into pavucontrol and manually set the appropriate devices for input and output, but for others I am often forced to use the headset regardless of whether I want to or not. I have a number of colleagues that report similar issues when trying to use video conferencing software with Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dmk1976 F pulseaudio /dev/snd/controlC1: dmk1976 F pulseaudio /dev/snd/controlC0: dmk1976 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 12:27:57 2020 InstallationDate: Installed on 2015-08-21 (1907 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Latitude E7250, Realtek ALC3235, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to focal on 2020-06-25 (137 days ago) dmi.bios.date: 09/01/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0G9CNK dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd09/01/2015:svnDellInc.:pnLatitudeE7250:pvr:rvnDellInc.:rn0G9CNK:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7250 dmi.product.sku: 062D dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1903694 Title: Sound comes out of the wrong place or not at all Status in alsa-driver package in Ubuntu: New Bug description: Since updating to Ubuntu 20.04, I have lots of problems with sound input and output coming from the wrong device or even a device that is not turned on. For example, right now in gnome-control-center sound settings it recognizes three sound output devices - internal speakers, HDMI output and a wireless headset. The wireless headset is off and the HDMI has no speakers, but I am using a HDMI->VGA adapter that gives it the impression that there may be speakers. In gnome-control- center, I have set the internal audio to be both the input and output devices for sound. When I click on the button to test audio output, no sound is produced, but if I have pavucontrol open at the same time, I can see that it is trying to send the sound output to the wireless speakers despite the settings in gnome-control-center. Similarly, if I try to do a video conference, such as skype, sound input and output are almost always wrong. Right now, if I try skype, it will only use the headset speaker and microphone, though it will make the phone ringing sound using the internal speaker. Again, this happens regardless of what I configure the sound settings to be in the skype settings panel. With many other video conferencing applications I have similar problems. With some, I manage to go into
[Touch-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
Sorry on my part, the last change to the status was a mistake and was not intended. Unfortunately, I cannot reverse it myself -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias:
[Touch-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
[Touch-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
[Touch-packages] [Bug 1211063] Re: [enhancement] Add support for color profiles
** Changed in: xorg-server (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1211063 Title: [enhancement] Add support for color profiles Status in Mir: Triaged Status in mir package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Won't Fix Bug description: Open system settings, select color. Select a color profile. With X, the change was live. With XMir, the profile is not applied. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-system-compositor 0.0.1+13.10.20130810.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Sun Aug 11 23:24:53 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-02-20 (537 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64+mac (20120220) MarkForUpload: True SourcePackage: unity-system-compositor UpgradeStatus: Upgraded to saucy on 2013-08-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1211063/+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 1420334] Re: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows)
** Changed in: xorg-server (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1420334 Title: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows) Status in Mir: Fix Released Status in MirAL: In Progress Status in mir package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Won't Fix Bug description: Mir needs a client API to allow surfaces to move themselves relatively. This is required to support full client-side decorations (bug 1398849), and also other apps like Google Chrome and Gnome Nautilus which can be dragged using part of their client areas. Later additions that are so similar I think they are part of the same bug: there need to be client APIs for "always on top" and "client initiate resize". To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1420334/+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 1494240] Re: Xmir crashes immediately on startup using glamor on Nexus4
** Changed in: xorg-server (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libhybris in Ubuntu. https://bugs.launchpad.net/bugs/1494240 Title: Xmir crashes immediately on startup using glamor on Nexus4 Status in libepoxy package in Ubuntu: Triaged Status in libhybris package in Ubuntu: New Status in xorg-server package in Ubuntu: Won't Fix Bug description: Xmir crashes immediately on startup using glamor on Nexus4. glamor GL version: OpenGL ES 3.0 V@53.0 AU@ (CL@) ... glamor GLSL version: OpenGL ES GLSL ES 3.00 (EE) (EE) Backtrace: (EE) (EE) Segmentation fault at address 0x0 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting (EE) The stack trace is lost. However the problem appears to be the glGetStringi() function. This function is new in GLESv3 and libepoxy only uses it because the GLES version is 3.0 on mako. However, libhybris fails to implement glGetStringi() and forward it to the driver correctly. At least that seems to be the problem. Our hybris GLESv2 is missing the function but the Android GLESv2 on the device has it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1494240/+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 1536815] Re: Connecting Xmir to USC fails [std::exception::what: An output ID must be specified from src/server/shell/system_compositor_window_manager.cpp(66)]
** Changed in: xorg-server (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1536815 Title: Connecting Xmir to USC fails [std::exception::what: An output ID must be specified from src/server/shell/system_compositor_window_manager.cpp(66)] Status in Mir: New Status in mir package in Ubuntu: New Status in xorg-server package in Ubuntu: Won't Fix Bug description: As seen here https://unity.ubuntu.com/mir/using_mir_on_pc.html I should be able to install ubuntu-desktop-mir and run unity7, but instead I receive the following error: failed to create a surface: Error processing request: An output ID must be specified Internal error details: /build/mir-1tnxlh/mir-0.18.1+16.04.20160115/src/server/shell/system_compositor_window_manager.cpp(66): Throw in function virtual mir::frontend::SurfaceId mir::shell::SystemCompositorWindowManager::add_surface(const std::shared_ptr&, const mir::scene::SurfaceCreationParameters&, const std::function(const std::shared_ptr&, const mir::scene::SurfaceCreationParameters&)>&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: An output ID must be specified To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1536815/+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 1668449] Re: [unity8] terminator Xmir - transparency doesn't work
** Changed in: xorg-server (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1668449 Title: [unity8] terminator Xmir - transparency doesn't work Status in Canonical System Image: New Status in unity8 package in Ubuntu: New Status in xorg-server package in Ubuntu: Won't Fix Bug description: [unity8] terminator Xmir - transparency doesn't work see attached screenshot (transparency works fine on unity7) although it's a gtk3 app, it doesn't run native. launch terminator with Xmir, right click to open the menu, Preferences -> Profiles -> Background and change transparency to whatever To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668449/+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 1677540] Re: Corrupted mouse pointer icon in Mir/Unity8
** Changed in: xorg-server (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1677540 Title: Corrupted mouse pointer icon in Mir/Unity8 Status in Canonical System Image: Confirmed Status in Mir: Confirmed Status in libsdl2 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Won't Fix Bug description: Ubuntu 17.04 unity8 corrupted mouse pointer icon (see attaches screenshot, the mouse pointer is hovering places/Home on the file manager app, the orange block/square) mostly i see when i run apps with Xmir, maybe stuff that uses SDL, mpv, neverball and it's only the arrow pointer, the rest are not affected, resize arrows etc To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677540/+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 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias:
[Touch-packages] [Bug 1902244] Please test proposed package
Hello Timo, or anyone else affected, Accepted libdrm into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.102-1ubuntu1~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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 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: New Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-11 source package in Focal: Fix Committed Status in mesa source package in Focal: New Status in xorg-server source package in Focal: New 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 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 1902244] Re: Backport packages for 20.04.1 HWE stack
Hello Timo, or anyone else affected, Accepted llvm-toolchain-11 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/llvm- toolchain-11/1:11.0.0-2~ubuntu20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: llvm-toolchain-11 (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal ** Changed in: libdrm (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/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 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: New Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-11 source package in Focal: Fix Committed Status in mesa source package in Focal: New Status in xorg-server source package in Focal: New 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 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 1903668] Re: HDMI audio device disappears and is unavailble after several minutes of not being used
Please try uninstalling 'pipewire', which is used by KDE and is known to interfere with PulseAudio. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1903668 Title: HDMI audio device disappears and is unavailble after several minutes of not being used Status in pulseaudio package in Ubuntu: Incomplete Bug description: On system boot both of my audio devices are selectable and useable. After around 10 minutes the HDMI device just disappears and cannot be selected as output in either the task bar audio applet or in Kstart>system settings>audio(either devices or advanced tab). In the devices tab a device called Dummy output is displayed and in the advanced tab the HDMI device is shown, in this case GP107GL, with the profile in the dropdown box underneath it displaying off with no ability to switch it to on. If I go to pulse volume control>configuration i am able to select the HDMI device and the system will use it. If I play a 2 hour movie after this and then turn off the media player the HDMI device will once again disappear after about 10 minutes. When I ran ubuntu-bug the system identified the HDMI device and switched to it (it is set as default) and has remained accessable for 15 minutes now. I am running the NVIDIA 450 driver package. If I run Kubuntu 20.10 a similar problem occurs except the the profile of the device is somehow damaged but by selecting any speaker setup (profile), audio returns. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 10 16:59:24 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-24 (200 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.E0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X470 GAMING PRO CARBON (MS-7B78) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.E0:bd06/10/2020:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B78:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPROCARBON(MS-7B78):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B78 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 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/1903668/+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 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup
> Please let me know if need a debdiff for H, I will download the daily built image and find a machine to install it and generate the debdiff. No it's fine, I've changed the 20.10 version to ubuntu3.1 and uploaded the debdiff from the bug to hirsute (no need to install hirsute to be able to generate the debdiff btw, especially not that earlier in the cycle, it can be built fine on 20.10) I've uploaded alsa-lib to F, G, H now, ucm is next in the queue ** Changed in: alsa-lib (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: alsa-lib (Ubuntu Groovy) Status: In Progress => Fix Committed ** Changed in: alsa-lib (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1901922 Title: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-ucm-conf package in Ubuntu: In Progress Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: In Progress Status in alsa-lib source package in Groovy: Fix Committed Status in alsa-ucm-conf source package in Groovy: In Progress Status in alsa-lib source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Hirsute: In Progress Bug description: [Impact] On the machines with AMD Ryzen acp audio design, the audio can't work anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1( focal), this is a regression on libasound2 for those machines. the AMD Ryzen acp audio card needs to load ucm to work with pulseaudio, but this audio card doesn't have an independant ucm for it, it needs to link to an existing HDA-Intel ucm, the check_empty_configuration() needs to cover the situation that Linked is true, otherwise it will fail to load the ucm for the audio card. Even the audio card could load the ucm, the output is muted and the init output volume is too low if freshly install the OS on these machines. [Fix] Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix init mute and init output volume problem. [Test Case] Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd list-cards, we could see the pulseaudio load the ucm successfully and we could see the sound card is generated and all output and input devices are listed under sound card, but the init output is muted and the volume is very low if we manually unumte it. Now install the updated alsa-ucm-conf, rm ~/.config/pulse/*; sudo rm -rf /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is not muted anymore and the output volume is OK to most users. [Regression Risk] This could make the machines with sof audio driver fail to load ucm , then all audio function can't work as before, like the speaker can't output sound or the internal mic can't be found or can't record sound. But this possibility is very low, I tested this SRU on some machines with or without sof audio driver, all worked as well as before. After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present
[Touch-packages] [Bug 1903668] [NEW] HDMI audio device disappears and is unavailble after several minutes of not being used
Public bug reported: On system boot both of my audio devices are selectable and useable. After around 10 minutes the HDMI device just disappears and cannot be selected as output in either the task bar audio applet or in Kstart>system settings>audio(either devices or advanced tab). In the devices tab a device called Dummy output is displayed and in the advanced tab the HDMI device is shown, in this case GP107GL, with the profile in the dropdown box underneath it displaying off with no ability to switch it to on. If I go to pulse volume control>configuration i am able to select the HDMI device and the system will use it. If I play a 2 hour movie after this and then turn off the media player the HDMI device will once again disappear after about 10 minutes. When I ran ubuntu-bug the system identified the HDMI device and switched to it (it is set as default) and has remained accessable for 15 minutes now. I am running the NVIDIA 450 driver package. If I run Kubuntu 20.10 a similar problem occurs except the the profile of the device is somehow damaged but by selecting any speaker setup (profile), audio returns. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 10 16:59:24 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-24 (200 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.E0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X470 GAMING PRO CARBON (MS-7B78) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.E0:bd06/10/2020:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B78:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPROCARBON(MS-7B78):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B78 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1903668 Title: HDMI audio device disappears and is unavailble after several minutes of not being used Status in pulseaudio package in Ubuntu: New Bug description: On system boot both of my audio devices are selectable and useable. After around 10 minutes the HDMI device just disappears and cannot be selected as output in either the task bar audio applet or in Kstart>system settings>audio(either devices or advanced tab). In the devices tab a device called Dummy output is displayed and in the advanced tab the HDMI device is shown, in this case GP107GL, with the profile in the dropdown box underneath it displaying off with no ability to switch it to on. If I go to pulse volume control>configuration i am able to select the HDMI device and the system will use it. If I play a 2 hour movie after this and then turn off the media player the HDMI device will once again disappear after about 10 minutes. When I ran ubuntu-bug the system identified the HDMI device and switched to it (it is set as default) and has remained accessable for 15 minutes now. I am running the NVIDIA 450 driver package. If I run Kubuntu 20.10 a similar problem occurs except the the profile of the device is somehow damaged but by selecting any speaker setup (profile), audio returns. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 10 16:59:24 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-24 (200 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present
[Touch-packages] [Bug 1902960] Re: Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases
Thanks for the explanation. I confirm that the workaround using "sytemctl restart systemd-udev- trigger && systemctl restart systemd-networkd" does the trick. @Dan Watkins : did you do some specific thing to reproduce the issue on your local VM ? It would be interesting to see the whole logs happening there. We could possibly hijack the image to add a | udevadm control --log-priority=debug and see what happens. -- 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/1902960 Title: Upgrade from 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to break DNS resolution in some cases Status in cloud-init package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: The systemd upgrade 245.4-4ubuntu3.3 to 245.4-4ubuntu3.2 appears to have broken DNS resolution across much of our Azure fleet earlier today. We ended up mitigating this by forcing reboots on the associated instances, no combination of networkctl reload, reconfigure, systemctl daemon-reexec, systemctl daemon-reload, netplan generate, netplan apply would get resolvectl to have a DNS server again. The main symptom appears to have been systemd-networkd believing it wasn't managing the eth0 interfaces: ubuntu@machine-1:~$ sudo networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 etherroutableunmanaged 2 links listed. Which eventually made them lose their DNS resolvers: ubuntu@machine-1:~$ sudo resolvectl dns Global: Link 2 (eth0): After rebooting, we see this behaving properly: ubuntu@machine-1:~$ sudo networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 etherroutableconfigured 2 links listed. ubuntu@machine-1:~$ sudo resolvectl dns Global: Link 2 (eth0): 168.63.129.16 This appears to be specifically linked to the upgrade, i.e. we were able to provoke the issue by upgrading the systemd package, so I suspect it's part of the packaging in the upgrade process. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lspci-vt: -[:00]-+-00.0 Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled) +-07.0 Intel Corporation 82371AB/EB/MB PIIX4 ISA +-07.1 Intel Corporation 82371AB/EB/MB PIIX4 IDE +-07.3 Intel Corporation 82371AB/EB/MB PIIX4 ACPI \-08.0 Microsoft Corporation Hyper-V virtual VGA Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: systemd 245.4-4ubuntu3.3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1031-azure root=PARTUUID=2e08bba3-68b4-4a16-af3b-47b73bd138a9 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1031.32-azure 5.4.65 Tags: focal uec-images Uname: Linux 5.4.0-1031-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090008 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 4412ad79-83fa-f845-b7c2-6f30dd4f1950 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1902960/+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 1903329] Re: SRU the current 2.48.9 stable update
Note that the fix for upstream issue 642, which is one of the drivers for this SRU, hasn't been released in the 2.50.x series yet (it's only a commit on the master branch: https://gitlab.gnome.org/GNOME/librsvg/-/commit/da90a31c6604f747f290e236045d8c79d1186747). The SRU process requires that a bug be fixed in the development release first, before considering a stable update (https://wiki.ubuntu.com/StableReleaseUpdates#Procedure). I asked Federico what his plans are for a 2.50.2 release (https://gitlab.gnome.org/GNOME/librsvg/-/issues/642#note_957195), let's see what he says before going ahead. ** Bug watch added: gitlab.gnome.org/GNOME/librsvg/-/issues #642 https://gitlab.gnome.org/GNOME/librsvg/-/issues/642 ** Also affects: librsvg (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: librsvg (Ubuntu Focal) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: librsvg (Ubuntu Focal) Importance: Undecided => High ** Changed in: librsvg (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1903329 Title: SRU the current 2.48.9 stable update Status in librsvg package in Ubuntu: Confirmed Status in librsvg source package in Focal: Confirmed Bug description: * Impact That's the current GNOME stable update, which fixes a number of issues, including a regression[1] since librsvg 2.40.x which was shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant changes between Ubuntu 20.04's current librsvg 2.48.7 (that version was also introduced by an SRU back in July[3]) and the current version 2.48.9. The complete list of changes is available on GNOME GitLab[4]. * Test case The update is part of GNOME stable updates[5]. Smoke testing by opening SVG images with eog or importing them with gimp can be performed to ensure there are no regressions. * Regression potential This is a bugfix-only stable micro-release, however librsvg is a core component with a number of reverse dependencies. A combination of autopkgtests and manual smoke testing to try and detect SVG rendering issues should be performed. * Notes about this report This is my first SRU request (and at the same time my first launchpad bug report). I'm not really familiar with the whole SRU process which is why I first asked about it on Ubuntu's official discourse forum[6]. Canonical's Sebastien Bacher encouraged me to open this ticket. I've copied over some parts of the last librsvg SRU ticket[3]. I hope this is fine. Thanks for considering this SRU. [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642 [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS [3]: https://bugs.launchpad.net/bugs/1884326 [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9 [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [6]: https://discourse.ubuntu.com/t/most-straight-forward-way-to-get- librsvg2-microrelease-update-into-focal-updates/19238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1903329/+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 1903632] Re: Touchscreen can't be used to scroll anymore. Instead it will select everything on its way.
Thanks for the clarification. Although assigning the bug to 'wayland' is incorrect because that source package is for the protocol only. No binaries come from 'wayland'. ** Package changed: wayland (Ubuntu) => libreoffice (Ubuntu) ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1903632 Title: Touchscreen can't be used to scroll anymore. Instead it will select everything on its way. Status in libreoffice package in Ubuntu: New Bug description: Ever since I upgrade to 20.10 from 20.04, I have been experiencing this issue. There are times when a user might want to scroll their screen by touching their screen. But I can't do this anymore. I want to know what went wrong? What can I do? Any info is appreciated. Note: Currently, I can scroll without in issue in Nautilus. But I can't do the same in Firefox, Tor browser, Libre Office, etc. Except Nautilus, all apps select words on screen whenever I touch my screen to scroll. But we all know, SCROLL ≠ SELECT. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 09:25:39 2020 DistUpgraded: 2020-10-28 23:47:17,717 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: virtualbox, 6.1.14, 5.8.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0641] InstallationDate: Installed on 2020-02-16 (267 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5548 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i45x0v@/vmlinuz-5.8.0-26-generic root=ZFS=rpool/ROOT/ubuntu_i45x0v ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-10-28 (12 days ago) dmi.bios.date: 05/28/2019 dmi.bios.release: 5.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:br5.4:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 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 20.2.1-1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1903632/+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
