[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Seems there's a bug in Launchpad preventing me from creating the missing focal and hirsute tasks. Let's see if deleting them all and recreating them helps... ** No longer affects: bluez (Ubuntu Hirsute) ** No longer affects: bluez (Ubuntu Focal) ** Also affects: gnome-settings-daemon (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: gnome-settings-daemon (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu Focal) Status: New => Fix Released ** Changed in: bluez (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: bluez (Ubuntu Focal) Assignee: (unassigned) => Andy Chi (andch) ** Changed in: bluez (Ubuntu Focal) Importance: Undecided => High ** Changed in: bluez (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: bluez (Ubuntu Hirsute) Assignee: (unassigned) => Andy Chi (andch) ** Changed in: gnome-settings-daemon (Ubuntu Focal) Status: New => In Progress ** Changed in: gnome-settings-daemon (Ubuntu Focal) Assignee: (unassigned) => Andy Chi (andch) ** Changed in: gnome-settings-daemon (Ubuntu Hirsute) Status: New => In Progress ** Changed in: gnome-settings-daemon (Ubuntu Hirsute) Assignee: (unassigned) => Andy Chi (andch) -- 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/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in gnome-settings-daemon source package in Focal: In Progress Status in bluez source package in Hirsute: Fix Released Status in gnome-settings-daemon source package in Hirsute: In Progress Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo
[Touch-packages] [Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
Installed the ubuntu 18.04 to that Dell machine with usb c-media audio card, enable the -proposed channel and install the alsa-lib 1.1.3-5ubuntu0.6, reboot, open the gnome-sound-setting, there is no SPDIF in the output device anymore. Verified on the bionic, it worked very well. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Bug description: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Where problems will occur] "Cmedia Audio" is the sound card name of this usb audio dongle, and this string is got from usb string descriptor, that is to say the "Cmedia Audio" is hard-coded in the firmware of that usb dongle. Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't set string descriptor, then the audio driver sets a generic name "USB Audio Device" for them, if a dongle has string descriptor, it may have different string like "C-Media USB Headphone Set", and all dongles I met before don't have SPDIF interface. So If this SRU could introduce regression, it will happen on a Cmedia usb audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF playback device from the gnome-sound-setting. But this regression chance is very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in the string descriptor and it is very rare a usb audio dongle has SPDIF interface. So far we haven't met such a cmedia usb audio dongle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1936238] Re: Lock screen does not properly give focus after unlocking on Wayland
*** This bug is a duplicate of bug 1928317 *** https://bugs.launchpad.net/bugs/1928317 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1928317, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: wayland (Ubuntu) => mutter (Ubuntu) ** This bug has been marked a duplicate of bug 1928317 window focus is lost after blank screen -- 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/1936238 Title: Lock screen does not properly give focus after unlocking on Wayland Status in mutter package in Ubuntu: New Bug description: When using GDM on Wayland, after unlocking, the previously focused window (such as Firefox) is not focused. Alt+tab (or click) must be used to gain focus. On X, everything works as excepted (if you were using Firefox at the time of locking, Firefox will be focused after unlocking too). (Ubuntu 21.04, ThinkPad P14s) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1936238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
** Tags added: originate-from-1936277 -- 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/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Hirsute: Fix Released Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
Hi Brian, I can't find the modemmanage from the focal-proposed channel to be upgraded. https://people.canonical.com/~ubuntu-archive/pending-sru.html shows it is in "Dependency wait". Please help to check it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Status in libmbim source package in Focal: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in modemmanager source package in Focal: Fix Committed Status in libmbim source package in Hirsute: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 To support the mentioned 2 modems,
[Touch-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
*** This bug is a duplicate of bug 1926062 *** https://bugs.launchpad.net/bugs/1926062 Now is a good time to mark this as a duplicate of bug 1926062 since they're the same bug. ** This bug has been marked a duplicate of bug 1926062 [hirsute/impish] Can't turn bluetooth on again after turning it off -- 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/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Hirsute: Fix Released Status in bluez source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1936273] [NEW] apt not respecting Ignore-Files-Silently directive
Public bug reported: I have a configuration management system that stores a backup copy of files that it updates with a suffix based upon the date that the file is updated (.-MM-DD) In Ubuntu 20.04, I have added a file 00ignore to the /etc/apt/apt.conf directory. The contents of the file are one line: Dir::Ignore-Files-Silently:: "\.[12][0-9][0-9][0-9]-[01][0-9]-[0-3][0-9]$"; The system appears to read the file, but doesn't seem to process it, as apt and related programs still spit out warnings. # apt-config dump |grep Ignore Dir::Ignore-Files-Silently ""; Dir::Ignore-Files-Silently:: "~$"; Dir::Ignore-Files-Silently:: "\.disabled$"; Dir::Ignore-Files-Silently:: "\.bak$"; Dir::Ignore-Files-Silently:: "\.dpkg-[a-z]+$"; Dir::Ignore-Files-Silently:: "\.ucf-[a-z]+$"; Dir::Ignore-Files-Silently:: "\.save$"; Dir::Ignore-Files-Silently:: "\.orig$"; Dir::Ignore-Files-Silently:: "\.distUpgrade$"; Dir::Ignore-Files-Silently:: "\.[12][0-9][0-9][0-9]-[01][0-9]-[0-3][0-9]$"; N: Ignoring file '99unclet-override.2021-06-15' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension N: Ignoring file '00unclet.2021-06-18' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension Note: aptitude does not display this warning, although many other apt- related programs do (e.g. apt, apt-get, apt-config). ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1936273 Title: apt not respecting Ignore-Files-Silently directive Status in apt package in Ubuntu: New Bug description: I have a configuration management system that stores a backup copy of files that it updates with a suffix based upon the date that the file is updated (.-MM-DD) In Ubuntu 20.04, I have added a file 00ignore to the /etc/apt/apt.conf directory. The contents of the file are one line: Dir::Ignore-Files-Silently:: "\.[12][0-9][0-9][0-9]-[01][0-9]-[0-3][0-9]$"; The system appears to read the file, but doesn't seem to process it, as apt and related programs still spit out warnings. # apt-config dump |grep Ignore Dir::Ignore-Files-Silently ""; Dir::Ignore-Files-Silently:: "~$"; Dir::Ignore-Files-Silently:: "\.disabled$"; Dir::Ignore-Files-Silently:: "\.bak$"; Dir::Ignore-Files-Silently:: "\.dpkg-[a-z]+$"; Dir::Ignore-Files-Silently:: "\.ucf-[a-z]+$"; Dir::Ignore-Files-Silently:: "\.save$"; Dir::Ignore-Files-Silently:: "\.orig$"; Dir::Ignore-Files-Silently:: "\.distUpgrade$"; Dir::Ignore-Files-Silently:: "\.[12][0-9][0-9][0-9]-[01][0-9]-[0-3][0-9]$"; N: Ignoring file '99unclet-override.2021-06-15' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension N: Ignoring file '00unclet.2021-06-18' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension Note: aptitude does not display this warning, although many other apt- related programs do (e.g. apt, apt-get, apt-config). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1936273/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1927078] Re: Don't allow useradd to use fully numeric names
The attached patch fixes the issue in focal ** Patch added: "Focal SRU" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+attachment/5510997/+files/lp197078_focal.debdiff ** Changed in: shadow (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: shadow (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 shadow in Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Focal: Fix Committed Status in shadow source package in Groovy: Won't Fix Status in shadow source package in Hirsute: Fix Committed Status in shadow source package in Impish: Fix Released Bug description: [Impact] * If a fully numeric username is created, it will cause problems with systemd. One example is that the user with this type of name can log in, but loginctl will not create a session for them. * This can also cause users to be unable to log in to a gdm environment [Test Case] * `useradd 123` (this command should succeed) * `userdel 123` to clean up the user that was just added * Install `shadow` from -proposed * `useradd 123` should now fail [Regression Potential] * If there were a logic error in the fix, it is possible that valid usernames would now be disallowed. * Many test cases have been added to ensure this is not the case, and --badnames would still provide a work-around [Original Description] Fully numeric names support in Ubuntu is inconsistent in Focal onwards because systemd does not like them[1] but are still allowed by default by useradd, leaving the session behavior in hands of the running applications. Two examples: 1. After creating a user named "0", the user can log in via ssh or console but loginctl won't create a session for it: root@focal:/home/ubuntu# useradd -m 0 root@focal:/home/ubuntu# id 0 uid=1005(0) gid=1005(0) groups=1005(0) .. 0@192.168.122.6's password: Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64) Last login: Thu Apr 8 16:17:06 2021 from 192.168.122.1 $ loginctl No sessions. $ w 16:20:09 up 4 min, 1 user, load average: 0.03, 0.14, 0.08 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT 0pts/0192.168.122.116:170.00s 0.00s 0.00s w And pam-systemd shows the following message: Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for user 0 by (uid=0) Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd initializing Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get user record: Invalid argument 2. With that same username, every successful authentication in gdm will loop back to gdm again instead of starting gnome, making the user unable to login. Making useradd fail (unless --badnames is set) when a fully numeric name is used will make the default OS behavior consistent. [Other info] - Upstream does not support fully numeric usernames - useradd has a --badnames parameter that would still allow the use of these type of names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1927078] Re: Don't allow useradd to use fully numeric names
The attached patch fixes the issue for hirsute. ** Patch added: "Hirsute Patch" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+attachment/5510996/+files/lp1927078_hirsute.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Focal: Fix Committed Status in shadow source package in Groovy: Won't Fix Status in shadow source package in Hirsute: Fix Committed Status in shadow source package in Impish: Fix Released Bug description: [Impact] * If a fully numeric username is created, it will cause problems with systemd. One example is that the user with this type of name can log in, but loginctl will not create a session for them. * This can also cause users to be unable to log in to a gdm environment [Test Case] * `useradd 123` (this command should succeed) * `userdel 123` to clean up the user that was just added * Install `shadow` from -proposed * `useradd 123` should now fail [Regression Potential] * If there were a logic error in the fix, it is possible that valid usernames would now be disallowed. * Many test cases have been added to ensure this is not the case, and --badnames would still provide a work-around [Original Description] Fully numeric names support in Ubuntu is inconsistent in Focal onwards because systemd does not like them[1] but are still allowed by default by useradd, leaving the session behavior in hands of the running applications. Two examples: 1. After creating a user named "0", the user can log in via ssh or console but loginctl won't create a session for it: root@focal:/home/ubuntu# useradd -m 0 root@focal:/home/ubuntu# id 0 uid=1005(0) gid=1005(0) groups=1005(0) .. 0@192.168.122.6's password: Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64) Last login: Thu Apr 8 16:17:06 2021 from 192.168.122.1 $ loginctl No sessions. $ w 16:20:09 up 4 min, 1 user, load average: 0.03, 0.14, 0.08 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT 0pts/0192.168.122.116:170.00s 0.00s 0.00s w And pam-systemd shows the following message: Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for user 0 by (uid=0) Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd initializing Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get user record: Invalid argument 2. With that same username, every successful authentication in gdm will loop back to gdm again instead of starting gnome, making the user unable to login. Making useradd fail (unless --badnames is set) when a fully numeric name is used will make the default OS behavior consistent. [Other info] - Upstream does not support fully numeric usernames - useradd has a --badnames parameter that would still allow the use of these type of names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1927078] Re: Don't allow useradd to use fully numeric names
** Changed in: shadow (Ubuntu Groovy) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Focal: Fix Committed Status in shadow source package in Groovy: Won't Fix Status in shadow source package in Hirsute: Fix Committed Status in shadow source package in Impish: Fix Released Bug description: [Impact] * If a fully numeric username is created, it will cause problems with systemd. One example is that the user with this type of name can log in, but loginctl will not create a session for them. * This can also cause users to be unable to log in to a gdm environment [Test Case] * `useradd 123` (this command should succeed) * `userdel 123` to clean up the user that was just added * Install `shadow` from -proposed * `useradd 123` should now fail [Regression Potential] * If there were a logic error in the fix, it is possible that valid usernames would now be disallowed. * Many test cases have been added to ensure this is not the case, and --badnames would still provide a work-around [Original Description] Fully numeric names support in Ubuntu is inconsistent in Focal onwards because systemd does not like them[1] but are still allowed by default by useradd, leaving the session behavior in hands of the running applications. Two examples: 1. After creating a user named "0", the user can log in via ssh or console but loginctl won't create a session for it: root@focal:/home/ubuntu# useradd -m 0 root@focal:/home/ubuntu# id 0 uid=1005(0) gid=1005(0) groups=1005(0) .. 0@192.168.122.6's password: Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64) Last login: Thu Apr 8 16:17:06 2021 from 192.168.122.1 $ loginctl No sessions. $ w 16:20:09 up 4 min, 1 user, load average: 0.03, 0.14, 0.08 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT 0pts/0192.168.122.116:170.00s 0.00s 0.00s w And pam-systemd shows the following message: Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for user 0 by (uid=0) Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd initializing Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get user record: Invalid argument 2. With that same username, every successful authentication in gdm will loop back to gdm again instead of starting gnome, making the user unable to login. Making useradd fail (unless --badnames is set) when a fully numeric name is used will make the default OS behavior consistent. [Other info] - Upstream does not support fully numeric usernames - useradd has a --badnames parameter that would still allow the use of these type of names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1927078] Re: Don't allow useradd to use fully numeric names
** Changed in: shadow (Ubuntu Hirsute) Assignee: (unassigned) => William Wilson (jawn-smith) ** Changed in: shadow (Ubuntu Focal) Assignee: (unassigned) => William Wilson (jawn-smith) ** Changed in: shadow (Ubuntu Hirsute) Status: New => In Progress ** Changed in: shadow (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Focal: In Progress Status in shadow source package in Groovy: Won't Fix Status in shadow source package in Hirsute: In Progress Status in shadow source package in Impish: Fix Released Bug description: [Impact] * If a fully numeric username is created, it will cause problems with systemd. One example is that the user with this type of name can log in, but loginctl will not create a session for them. * This can also cause users to be unable to log in to a gdm environment [Test Case] * `useradd 123` (this command should succeed) * `userdel 123` to clean up the user that was just added * Install `shadow` from -proposed * `useradd 123` should now fail [Regression Potential] * If there were a logic error in the fix, it is possible that valid usernames would now be disallowed. * Many test cases have been added to ensure this is not the case, and --badnames would still provide a work-around [Original Description] Fully numeric names support in Ubuntu is inconsistent in Focal onwards because systemd does not like them[1] but are still allowed by default by useradd, leaving the session behavior in hands of the running applications. Two examples: 1. After creating a user named "0", the user can log in via ssh or console but loginctl won't create a session for it: root@focal:/home/ubuntu# useradd -m 0 root@focal:/home/ubuntu# id 0 uid=1005(0) gid=1005(0) groups=1005(0) .. 0@192.168.122.6's password: Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64) Last login: Thu Apr 8 16:17:06 2021 from 192.168.122.1 $ loginctl No sessions. $ w 16:20:09 up 4 min, 1 user, load average: 0.03, 0.14, 0.08 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT 0pts/0192.168.122.116:170.00s 0.00s 0.00s w And pam-systemd shows the following message: Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for user 0 by (uid=0) Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd initializing Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get user record: Invalid argument 2. With that same username, every successful authentication in gdm will loop back to gdm again instead of starting gnome, making the user unable to login. Making useradd fail (unless --badnames is set) when a fully numeric name is used will make the default OS behavior consistent. [Other info] - Upstream does not support fully numeric usernames - useradd has a --badnames parameter that would still allow the use of these type of names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
Confirmed here that /var/lib/ubuntu-advantage/status.json is only updated when running 'ua status' as root. No desktop software is running as root, in the few cases that root privileges are required a small service is run as root and that is communicated with via D-Bus. The warning doesn't show for the majority of users, since they aren't going to be running from the command line so I would leave it for now, and remove in the next revision of this code. I think there is a case where this won't work - if you have a fresh machine that you haven't done a 'ua attach' on then software-properties is going to not offer ESM as it's not going to think it's available. In https://code.launchpad.net/~robert-ancell/software- properties/+git/software-properties/+merge/400153 that 'ua status' can timeout and return empty values, which is why we are accessing /var/lib/ubuntu-advantage/status.json. Is there a reason why the ua client doesn't do this itself internally, i.e. it gives you fresh json or returns the cached copy if it can't do the update? -- 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/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Committed Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1927078] Re: Don't allow useradd to use fully numeric names
** Description changed: - [Description] + [Impact] + + * If a fully numeric username is created, it will cause +problems with systemd. One example is that the user with +this type of name can log in, but loginctl will not create +a session for them. + * This can also cause users to be unable to log in to a gdm +environment + + [Test Case] + + * `useradd 123` (this command should succeed) + * `userdel 123` to clean up the user that was just added + * Install `shadow` from -proposed + * `useradd 123` should now fail + + [Regression Potential] + * If there were a logic error in the fix, it is possible +that valid usernames would now be disallowed. + * Many test cases have been added to ensure this is not +the case, and --badnames would still provide a work-around + + [Original Description] Fully numeric names support in Ubuntu is inconsistent in Focal onwards because systemd does not like them[1] but are still allowed by default by useradd, leaving the session behavior in hands of the running applications. Two examples: 1. After creating a user named "0", the user can log in via ssh or console but loginctl won't create a session for it: root@focal:/home/ubuntu# useradd -m 0 root@focal:/home/ubuntu# id 0 uid=1005(0) gid=1005(0) groups=1005(0) .. 0@192.168.122.6's password: Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64) Last login: Thu Apr 8 16:17:06 2021 from 192.168.122.1 $ loginctl No sessions. $ w - 16:20:09 up 4 min, 1 user, load average: 0.03, 0.14, 0.08 + 16:20:09 up 4 min, 1 user, load average: 0.03, 0.14, 0.08 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT - 0pts/0192.168.122.116:170.00s 0.00s 0.00s w + 0pts/0192.168.122.116:170.00s 0.00s 0.00s w And pam-systemd shows the following message: Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for user 0 by (uid=0) Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd initializing Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get user record: Invalid argument + 2. With that same username, every successful authentication in gdm will + loop back to gdm again instead of starting gnome, making the user unable + to login. - 2. With that same username, every successful authentication in gdm will loop back to gdm again instead of starting gnome, making the user unable to login. - - - Making useradd fail (unless --badnames is set) when a fully numeric name is used will make the default OS behavior consistent. - + Making useradd fail (unless --badnames is set) when a fully numeric name + is used will make the default OS behavior consistent. [Other info] - Upstream does not support fully numeric usernames - useradd has a --badnames parameter that would still allow the use of these type of names -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Focal: New Status in shadow source package in Groovy: New Status in shadow source package in Hirsute: New Status in shadow source package in Impish: Fix Released Bug description: [Impact] * If a fully numeric username is created, it will cause problems with systemd. One example is that the user with this type of name can log in, but loginctl will not create a session for them. * This can also cause users to be unable to log in to a gdm environment [Test Case] * `useradd 123` (this command should succeed) * `userdel 123` to clean up the user that was just added * Install `shadow` from -proposed * `useradd 123` should now fail [Regression Potential] * If there were a logic error in the fix, it is possible that valid usernames would now be disallowed. * Many test cases have been added to ensure this is not the case, and --badnames would still provide a work-around [Original Description] Fully numeric names support in Ubuntu is inconsistent in Focal onwards because systemd does not like them[1] but are still allowed by default by useradd, leaving the session behavior in hands of the running applications. Two examples: 1. After creating a user named "0", the user can log in via ssh or console but loginctl won't create a session for it: root@focal:/home/ubuntu# useradd -m 0 root@focal:/home/ubuntu# id 0 uid=1005(0) gid=1005(0) groups=1005(0) .. 0@192.168.122.6's password: Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64) Last login: Thu Apr 8 16:17:06 2021 from 192.168.122.1 $ loginctl No sessions. $ w 16:20:09 up 4 min, 1 user, load average:
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
miniamlly as in the patch above, I think we probably need a pre-flight check of os.path.exists( UA_STATUS_JSON) so we don't emit those Errno messages due to failed file opens -- 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/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Committed Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
Ultimately if we decide to go with #2 here's a patch that I think would limit both the time cost of a remote uRL query and the noisy logging: --- /usr/lib/python3/dist-packages/softwareproperties/gtk/utils.py 2021-06-10 23:20:22.0 -0600 +++ /usr/lib/python3/dist-packages/softwareproperties/gtk/utils.py.new 2021-07-14 15:32:54.559693094 -0600 @@ -26,6 +26,7 @@ gi.require_version("Gtk", "3.0") from gi.repository import Gio, Gtk import json +import os import subprocess import logging @@ -76,23 +77,12 @@ def get_ua_status(): """Return a dict of all UA status information or empty dict on error.""" # status.json will exist on any attached system or any unattached system -# which has already run `ua status`. Calling ua status directly on -# network disconnected machines will raise a TimeoutException trying to -# access contracts.canonical.com/v1/resources. -try: -# Success writes UA_STATUS_JSON -result = subprocess.run(['ua', 'status', '--format=json'], stdout=subprocess.PIPE) -except Exception as e: -print("Failed to call ubuntu advantage client:\n%s" % e) +# which has already run `sudo ua status`. +if not os.path.exists(UA_STATUS_JSON): return {} -if result.returncode != 0: -print("Ubuntu advantage client returned code %d" % result.returncode) -return {} - try: status_file = open(UA_STATUS_JSON, "r") except Exception as e: -print("No ua status file written:\n%s" % e) return {} with status_file as stream: -- 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/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Committed Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
Ultimately if we decide to go with #2 here's a patch that I think would limit both the time cost of a remote uRL query and the noisy logging: --- /usr/lib/python3/dist-packages/softwareproperties/gtk/utils.py 2021-06-10 23:20:22.0 -0600 +++ /usr/lib/python3/dist-packages/softwareproperties/gtk/utils.py.new 2021-07-14 15:19:14.485004311 -0600 @@ -76,23 +76,10 @@ def get_ua_status(): """Return a dict of all UA status information or empty dict on error.""" # status.json will exist on any attached system or any unattached system -# which has already run `ua status`. Calling ua status directly on -# network disconnected machines will raise a TimeoutException trying to -# access contracts.canonical.com/v1/resources. -try: -# Success writes UA_STATUS_JSON -result = subprocess.run(['ua', 'status', '--format=json'], stdout=subprocess.PIPE) -except Exception as e: -print("Failed to call ubuntu advantage client:\n%s" % e) -return {} -if result.returncode != 0: -print("Ubuntu advantage client returned code %d" % result.returncode) -return {} - +# which has already run `sudo ua status`. try: status_file = open(UA_STATUS_JSON, "r") except Exception as e: -print("No ua status file written:\n%s" % e) return {} with status_file as stream: -- 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/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Committed Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779767] Re: Default cron PATH does not include /snap/bin
** Changed in: cron (Ubuntu Groovy) Status: Confirmed => Won't Fix ** Changed in: anacron (Ubuntu Groovy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1779767 Title: Default cron PATH does not include /snap/bin Status in anacron package in Ubuntu: Fix Released Status in cron package in Ubuntu: Fix Released Status in anacron source package in Bionic: Confirmed Status in cron source package in Bionic: Confirmed Status in anacron source package in Focal: Confirmed Status in cron source package in Focal: Confirmed Status in anacron source package in Groovy: Won't Fix Status in cron source package in Groovy: Won't Fix Status in anacron source package in Hirsute: Fix Released Status in cron source package in Hirsute: Fix Released Bug description: I recently changed from a .deb install of LXD to a snap, and was surprised that one of my crontab scripts stopped working. I see that $PATH in a cron script only contains "/usr/bin:/bin", whereas my default shell also includes "/snap/bin". It seems to me that for the best user experience with snaps, "/snap/bin" should be part of the default $PATH in cron. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cron 3.0pl1-128.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 2 14:30:06 2018 InstallationDate: Installed on 2017-12-20 (194 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1779767/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
Also per #2 above, if we were to drop the `ua status` call from utils.py:get_ua_status() that would also mitigate the perceived "time cost" corradoventu mentioned because `ua status` does reach out to the internet to contracts.canonical.com to check service availability for your running distro/kernel/platform. If we don't make that `ua status` commandline call, and rely on presence/absence of /var/lib/ubuntu- advantage/status.json then we can avoid the round trip to an external URL to fill in these service details. -- 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/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Committed Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status
@robert-ancell and @corradoventu those errors are due to running software-properties-gtk as non-root user on a system that is not attached to any ubuntu-advantage services. The /var/lib/ubuntu-advantage/status.json file is only created by a root user via an `sudo ua status` or `sudo ua attach ` call. The absence of the file means that the system is not attached to any valid Ubuntu Advantage services, and the logic in softwareproperties/gtk/util.py will still correctly return an empty representation for ubuntu-advantage services as an empty dict {} and the UX dialogs properly direct folks to how to activate ESM in this case. I mistakenly thought software-properties-gtk is invoked as root user in order to install/update packages. Given that it is invoked as non-root user we can do one of two things: 1. keep the current implementation which would print messages about missing status.json files knowing that the UX dialogs still behave correctly. OR 2. drop the subp call to 'ua' 'status' from utils.py:get_ua_status() because they will never emit the /var/lib/ubuntu-advantage/status.json artifact and also drop the printed messages about No ua status file written as that really only means you are non-root and on an unattached machine. -- 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/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Committed Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page
A couple of points about putting it into Impish: - What mechanism can we use to determine if it should show? - Since the banner refers to a beta feature, it will be replaced at some point with a new banner, is it worth bringing that into Impish or waiting for the more complete feature. -- 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/1934439 Title: Add Ubuntu Pro banner to Livepatch page Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: New Status in software-properties source package in Focal: New Bug description: [Impact] Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. Note that this is not shown in current releases, as this feature only applies to older versions. [Test Case] 1. Open Software Properties. 2. Go to Livepatch tab. Expected result: A banner is shown directing the user to Ubuntu Pro. The banner can be dismissed, and doesn't return when restarting software-properties. [Regression Potential] Some risk of introducing a new bug, however the change is quite small and doesn't have any complex interactions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1935972] Re: postinst: Rely on needrestart when present on the system
** Changed in: pam (Ubuntu) Status: New => In Progress ** Changed in: pam (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1935972 Title: postinst: Rely on needrestart when present on the system Status in pam package in Ubuntu: In Progress Bug description: This patch bypasses the custom restarting logic backed into the postinst script if the needrestart utility is present, as it allows sharing the logic with the rest of the system. It also changes the custom logic to compare the old package version to the current one instead of a hard-coded value. I don't feel particularly strongly about this, so feel free to drop it :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1935972/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1935972] Re: postinst: Rely on needrestart when present on the system
>From what I can piece together from the debian/changelog it seems that the version is hard-coded because it is only ever updated when the libpam0g.symbols file is updated which is why services would need to be restarted. Subsequently, I'm dropping that part of the patch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1935972 Title: postinst: Rely on needrestart when present on the system Status in pam package in Ubuntu: New Bug description: This patch bypasses the custom restarting logic backed into the postinst script if the needrestart utility is present, as it allows sharing the logic with the rest of the system. It also changes the custom logic to compare the old package version to the current one instead of a hard-coded value. I don't feel particularly strongly about this, so feel free to drop it :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1935972/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934286] Please test proposed package
Hello Jerry, or anyone else affected, Accepted libqmi into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libqmi/1.28.6-1~20.04 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 modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Status in libmbim source package in Focal: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in modemmanager source package in Focal: Fix Committed Status in libmbim source package in Hirsute: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the
[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
When reviewing libqmi I noticed the same type of change, moving qmi- proxy, so I went ahead and reuploaded the package but with a symlink like Lukasz did for libmbim. ** Changed in: libqmi (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Status in libmbim source package in Focal: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in modemmanager source package in Focal: Fix Committed Status in libmbim source package in Hirsute: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 To
[Touch-packages] [Bug 1906741] Re: Firefox sometimes causes garbled audio
This happened again to me today. I was in a MSTeams chat session (standalone app, not the web version) and opened a webpage in Firefox that garbled the sound of the meeting in progress. I noticed that when it happened that in the system audio mixer/volume control manager, there was suddenly a lot of entries for "speech-dispatcher" that previously weren't there. And this was also reflected in the list from the `ps` command: 188672 0.0 0.0 450364 8304 ?Sl 11:50 0:00 /usr/lib/speech-dispatcher-modules/sd_espeak-ng /etc/speech-dispatcher/modules/espeak-ng.conf 188678 0.0 0.0 360052 5660 ?Sl 11:50 0:00 /usr/lib/speech-dispatcher-modules/sd_dummy /etc/speech-dispatcher/modules/dummy.conf 188681 0.0 0.0 360084 5972 ?Sl 11:50 0:00 /usr/lib/speech-dispatcher-modules/sd_generic /etc/speech-dispatcher/modules/mary-generic.conf 188684 0.0 0.0 360096 5492 ?Sl 11:50 0:00 /usr/lib/speech-dispatcher-modules/sd_generic /etc/speech-dispatcher/modules/espeak-generic.conf 188687 0.0 0.0 159724 2236 ?Ssl 11:50 0:00 /usr/bin/speech-dispatcher --spawn --communication-method unix_socket --socket-path /run/user/1000/speech-dispatcher/speechd.sock Without touching the webpage or Firefox, I used the command-line to kill the one that looked to be the main speech-dispatcher process, which was the 188687 process ID in this case (which also closed the other speech-dispatcher processes). And immediately, the audio cleared up and I was able to continue browsing the webpage while the MSTeams meeting continued. This makes me wonder if the problem is actually Firefox or if it's speech-dispatcher -- or perhaps it's the data that Firefox is streaming to speech-dispatcher?? Like the others in this thread, I have experimented with the speech settings in Firefox to no avail. If there's a magic setting to disable it, I haven't found it. -- 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/1906741 Title: Firefox sometimes causes garbled audio Status in firefox package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Opening certain applications/websites at the same time as Firefox causes the audio to become garbled. The audio sounds distorted with an echo. Certain actions are guaranteed to cause this, but it can also happening when only running instances of Firefox. I've been able to consistently cause this by launching Zoom from a link within Firefox. This does not occur when using Chrome. The only way to fix the issue is to shut down all audio-related programs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 83.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rdevans 55475 F pulseaudio /dev/snd/controlC0: rdevans 55475 F pulseaudio /dev/snd/controlC3: rdevans 55475 F pulseaudio /dev/snd/controlC1: rdevans 55475 F pulseaudio BuildID: 20201112153044 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 16:55:36 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-10-20 (1140 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.0.0.1 dev enp7s0 proto dhcp metric 100 10.0.0.0/24 dev enp7s0 proto kernel scope link src 10.0.0.7 metric 100 169.254.0.0/16 dev enp7s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=83.0/20201112153044 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-11-12 (21 days ago) dmi.bios.date: 02/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: H67M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
Hello Jerry, or anyone else affected, Accepted libmbim into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libmbim/1.24.8-1~20.04 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: libmbim (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Status in libmbim source package in Focal: Fix Committed Status in modemmanager source package in Focal: Fix Committed Status in libmbim source package in Hirsute: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used
[Touch-packages] [Bug 1936238] [NEW] Lock screen does not properly give focus after unlocking on Wayland
Public bug reported: When using GDM on Wayland, after unlocking, the previously focused window (such as Firefox) is not focused. Alt+tab (or click) must be used to gain focus. On X, everything works as excepted (if you were using Firefox at the time of locking, Firefox will be focused after unlocking too). (Ubuntu 21.04, ThinkPad P14s) ** Affects: wayland (Ubuntu) Importance: Undecided Status: 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/1936238 Title: Lock screen does not properly give focus after unlocking on Wayland Status in wayland package in Ubuntu: New Bug description: When using GDM on Wayland, after unlocking, the previously focused window (such as Firefox) is not focused. Alt+tab (or click) must be used to gain focus. On X, everything works as excepted (if you were using Firefox at the time of locking, Firefox will be focused after unlocking too). (Ubuntu 21.04, ThinkPad P14s) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1936238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1936236] [NEW] Repeated segfault in udev_rule_line_free
Public bug reported: Ubuntu version: 20.04 focal (Distro: Linux Mint 20.1 Ulyssa) systemd version: 245.4-4ubuntu3.7 What happened: systemd-udevd underwent repeated segfaults and coredumps for unknown reasons. Loop stopped by forcing restart of udevd. Coredump information: PID: 381 (systemd-udevd) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Wed 2021-07-14 00:12:29 EDT (9h ago) Command Line: /lib/systemd/systemd-udevd Executable: /lib/systemd/systemd-udevd Control Group: /system.slice/systemd-udevd.service Unit: systemd-udevd.service Slice: system.slice Boot ID: abaa4a5b0c6641cda2c58d7c307cfc38 Machine ID: b76cc7b1bbdc489e93909d2043031de8 Hostname: Ampere-Limux Storage: /var/lib/systemd/coredump/core.systemd-udevd.0.abaa4a5b0c6641cda2c58d7c307cfc38.381.1626235949.lz4 Message: Process 381 (systemd-udevd) of user 0 dumped core. Stack trace of thread 381: #0 0x5635cdf522eb in udev_rule_line_free (rule_line=0x5635cec9db20) at ../src/udev/udev-rules.c:270 #1 0x5635cdf53d0c in udev_rule_file_free (rule_file=0x5635cecb2760) at ../src/udev/udev-rules.c:289 #2 udev_rules_free (rules=0x5635cea0ad10) at ../src/udev/udev-rules.c:302 #3 0x5635cdf60875 in manager_free (manager=manager@entry=0x5635ce9fde60) at ../src/udev/udevd.c:306 #4 0x5635cdf63e34 in manager_freep (p=) at ../src/udev/udevd.c:314 #5 run (argc=, argv=) at ../src/udev/udevd.c:1703 #6 0x5635cdf0721a in main (argc=, argv=) at ../src/udev/udevd.c:1817 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1936236 Title: Repeated segfault in udev_rule_line_free Status in systemd package in Ubuntu: New Bug description: Ubuntu version: 20.04 focal (Distro: Linux Mint 20.1 Ulyssa) systemd version: 245.4-4ubuntu3.7 What happened: systemd-udevd underwent repeated segfaults and coredumps for unknown reasons. Loop stopped by forcing restart of udevd. Coredump information: PID: 381 (systemd-udevd) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Wed 2021-07-14 00:12:29 EDT (9h ago) Command Line: /lib/systemd/systemd-udevd Executable: /lib/systemd/systemd-udevd Control Group: /system.slice/systemd-udevd.service Unit: systemd-udevd.service Slice: system.slice Boot ID: abaa4a5b0c6641cda2c58d7c307cfc38 Machine ID: b76cc7b1bbdc489e93909d2043031de8 Hostname: Ampere-Limux Storage: /var/lib/systemd/coredump/core.systemd-udevd.0.abaa4a5b0c6641cda2c58d7c307cfc38.381.1626235949.lz4 Message: Process 381 (systemd-udevd) of user 0 dumped core. Stack trace of thread 381: #0 0x5635cdf522eb in udev_rule_line_free (rule_line=0x5635cec9db20) at ../src/udev/udev-rules.c:270 #1 0x5635cdf53d0c in udev_rule_file_free (rule_file=0x5635cecb2760) at ../src/udev/udev-rules.c:289 #2 udev_rules_free (rules=0x5635cea0ad10) at ../src/udev/udev-rules.c:302 #3 0x5635cdf60875 in manager_free (manager=manager@entry=0x5635ce9fde60) at ../src/udev/udevd.c:306 #4 0x5635cdf63e34 in manager_freep (p=) at ../src/udev/udevd.c:314 #5 run (argc=, argv=) at ../src/udev/udevd.c:1703 #6 0x5635cdf0721a in main (argc=, argv=) at ../src/udev/udevd.c:1817 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1936236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1911036] Re: GDK/GTK app crash in XFCE when performing drag operation (in gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache <- gdk_x11_drag_context_f
This bug was fixed in the package gtk4 - 4.3.1-1 --- gtk4 (4.3.1-1) experimental; urgency=medium * New upstream release: - Ignore XErrors from the COW (LP: #1911036) * debian/control: Update build-dependencies * debian/patches: Refresh * debian/control: Add dependencies to use upstream provided gi-docgen gi-docgen is still in NEW for some months now, so until that we can manually use the upstream provided version as subproject. * debian/patches: Prevent usage of web-fonts and external links in docs * debian/rules: Do not check for nocheck with dh 13 * debian/rules: Do not manually build docs at build phase. This is now handled by gi-docgen that is called at build phase, not at install phase. * debian/control: Add python3-gi as test build dependency. It's needed by introspection tests * debian/libgtk-4-1.symbols.in: Add new symbols * debian/libgtk-4-doc.*: Adapt install files and links to gi-docgen paths. Docs are installed all in /usr/share/docs/libgtk-4-doc subfolders and linked to /usr/share/gtk-doc to keep devhelp support * debian/patches: Get typelib path from pkg-config * debian/rules: Ensure all symbols are defined. This is now working fine with all the components * debian/rules: Do not reset xvfb on running tests * debian/rules: Support running tests in parallel. This works fine now, so let's enable it again * debian/rules: Move test script to an easier to maintain external file. We're doing lots of operations to run tests, it's better to have the setup in an external script that it's easier to run, debug and maintain * debian/run-tests.sh: Only print full log on errors. No need to output the whole log if there have been no failures * debian: Run tests under wayland too in linux. It's now becoming the default backend so better to also test the library there. * debian/patches: Initialize the textbtree tags counting causing s390x fails * debian/rules: Skip some broken comparison tests in big endian archs * debian/tests: Port to Gtk4 and run them both in wayland and x11 -- Marco Trevisan (Treviño) Fri, 09 Jul 2021 16:31:39 +0200 ** Changed in: gtk4 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1911036 Title: GDK/GTK app crash in XFCE when performing drag operation (in gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache <- gdk_x11_drag_context_find_window) Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk4 package in Ubuntu: Fix Released Bug description: For many months now, whenever any mouse drag is attempted in an application using the gtk tool kit, the application immediately crashes. I've noticed this at least in Firefox and thunar. It also occurs when displaying these applications from a Virtualbox machine or from another server running something other than Ubuntu. The VM was running CentOS 8 and the remote server was running Mageia. Both Firefox and thunar run fine with Mageia's Xorg. It seems like the issue may be with the Xorg server on Ubuntu. I tried setting the GDK_SYNCHRONIZE variable to various settings but was unable to produce further debug output. The only other debug output I was able to gather is when running thunar with the --gtk- debug parameter (attached). I also tried running thunar with GDB but without recompiling it, it doesn't produce much information other than it's stopping in glib. Let me know what other information I can provide. (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 8) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) ExceptionHandler::GenerateDump cloned child 110611 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. [1]+ Trace/breakpoint trap (core dumped) firefox (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details:
[Touch-packages] [Bug 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT
yes that looks to be the one.. I've pushed the fix for hirsute here: https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging please test, and I'll backport it to focal too -- 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/1934783 Title: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT Status in mesa package in Ubuntu: New Status in mesa source package in Focal: New Bug description: Since the update to Mesa 21.0.3 I have graphical glitches in desktop: Unity, Gnome Shell both sessions (X.org and Wayland). Also most of the programs have glitches. However Firefox seems unaffected. CPU: Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz min/max: 2200/3600 MHz Graphics: Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0 5.4.0-79-generic LLVM 12.0.0) v: 4.6 Mesa 21.0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934783/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
Hello Brian, Jerry! I have uploaded a new upload of libmbim to the Unapproved queue. Actually a postrm/postinst is not quite the way to go as there are better ways such a task can be realized - so I added a libmbim-proxy.links file to make sure we also create a symlink for the old expected path. This seems to work on my test build here: https://launchpad.net/~sil2100/+archive/ubuntu/testing/+build/21781947 Brian, could you take a look now? I think this delta is really small and with the additional symlink the regression risk is much much lower. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Status in modemmanager source package in Focal: Fix Committed Status in libmbim source package in Hirsute: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may
[Touch-packages] [Bug 1918458] Re: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok
Please test this kernel: https://people.canonical.com/~hwang4/lp1918458/ -- 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/1918458 Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok Status in alsa-driver package in Ubuntu: Confirmed Bug description: Expect : sound from speaker Instead, obtain : no sound. Tried various configuration of /etc/modprobe.d/alsa-conf with : options snd-hda-intel model= and options snd-intel-dspcfg dsp_driver=3 or 1 and systematic reboot. Either I get dummy output, or I get proper output detection, alsamixer and pavucontrol seems 100% ok, but no sound comes from the speakers. I'm under a dualboot with Windows 10, BIOS fast boot disabled. Ubuntu 20.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thibauts 1522 F pulseaudio /dev/snd/pcmC0D0p: thibauts 1522 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 10 18:10:30 2021 InstallationDate: Installed on 2021-03-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Cannon Point-LP High Definition Audio Controller - sof-hda-dsp Symptom_Jack: Grey Speaker, Internal Symptom_Type: Only some of outputs are working Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2019 dmi.bios.release: 1.4 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.04 dmi.board.asset.tag: Default string dmi.board.name: Guinness_WL dmi.board.vendor: WL dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd05/24/2019:br1.4:efr1.6:svnAcer:pnSwiftSF515-51T:pvrV1.04:rvnWL:rnGuinness_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: Swift 5 dmi.product.name: Swift SF515-51T dmi.product.sku: dmi.product.version: V1.04 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-10T18:04:19.277254 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920757] Re: Don't update pango to 1.48.3
The issue seems to be code doing undocumented things and was fixed in the corresponding project, let's update it's early in the cycle now and we can deal with fallouts if needed ** Changed in: pango1.0 (Ubuntu) Status: Triaged => Fix Released -- 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/1920757 Title: Don't update pango to 1.48.3 Status in pango1.0 package in Ubuntu: Fix Released Bug description: The upgrade is creating issues, see https://gitlab.gnome.org/GNOME/pango/-/issues/542 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1920757/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1935617] Re: systemd autopkgtest broken on ppc64el with qemu 6.0
Ok, now that we know the root cause we can mark systemd as invalid and the ppc project as fixed. The qemu task will be fixed once the upload migrates - but currently the test queue is rather full. ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-power-systems Status: New => Fix Released ** Changed in: qemu (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1935617 Title: systemd autopkgtest broken on ppc64el with qemu 6.0 Status in The Ubuntu-power-systems project: Fix Released Status in qemu package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Invalid Bug description: I'm not sure yet if this is flaky or a real issue, but I'm filing it to avoid multiple people analyzing the same. The Qemu 6.0 upload https://launchpad.net/ubuntu/+source/qemu/1:6.0+dfsg-1~ubuntu2 triggers a test failure like https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20210708_223311_e3bbb@/log.gz I have tested the new qemu on ppc64 and it worked fine for device emulation and migration cases. But this is suspicious. Of the last tests exactly and only those with the new qemu failed. impish ppc64el tests-in-lxd (F 5% f 0% S 0% B 0% => P 95%/) F.F. systemd-fsckd (F 0% f 0% S 100% B 0% => P 0%/) upstream-1 (F 15% f 0% S 0% B 0% => P 85%/) F..F upstream-2 (F 12% f 0% S 0% B 0% => P 87%/) F... For an insight in flakyness/reproducibility I've retriggered the missing qemu and the non-qemu cases a few times. If those reproduce all-bad vs all-good again this would further indicate a real issue. Unfortunately the ppc maas seems down right now and canonistack also isn't too nice this week - overall that inhibits the testing a bit :-/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1935617/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp