[Touch-packages] [Bug 1944409] Re: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling
I don't have any BIOS update available; as I said, my laptop (Dell Latitude 7520) is fully updated. $ sudo dmidecode -s bios-version 1.6.1 $ fwupdmgr get-updates | grep "Current version" -B2 Devices with no available firmware updates: • UEFI Device Firmware • UEFI Device Firmware • UEFI dbx • VMM3332 inside Dell WD15/TB16/TB18 wired Dock │ │ Device ID: 71b677ca0f1bc2c5b804fa1d59e52064ce589293 │ │ Summary:NVM Express Solid State Drive │ │ Current version:21112012 -- └─System Firmware: │ Device ID: 5ecfc78eb81da0c1a2ab9baa1510f0c269ea1b9b │ Current version:1.6.1 -- 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/1944409 Title: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling Status in OEM Priority Project: New Status in systemd package in Ubuntu: Confirmed Bug description: My setup: - Dell Latitude 7520 - Dell WD15 USB C docking station - Ubuntu 20.04.3 - systemd 245.4-4ubuntu3.13 - uname -a: Linux CLIFMI085 5.13.0-1012-oem #16-Ubuntu SMP Tue Sep 7 09:23:08 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux I leave my laptop docked and, after waking it up from sleep, the fans start blowing. After a quick inspection with top/htop, I always see /usr/lib/systemd/systemd-udev consuming 50+% of my CPU. After a quick search, I discover that I can use `udevadm monitor` to check what device is making all this fuss, and this is the output: UDEV [92591.827159] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.873819] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.920022] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.967005] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.018200] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.068351] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.115100] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.166201] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.213318] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.261046] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.308824] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.356577] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.403766] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.451164] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) As you can see, the battery status is being polled every 0.05s. To fix this, I just need to restart the service with: sudo systemctl restart systemd-udevd systemd-udevd-kernel.socket systemd-udevd-control.socket Afterwards, this is the output of `udevadm monitor`: KERNEL[92739.612371] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92739.646888] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) KERNEL[92741.076823] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92741.099370] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) KERNEL[92742.539438] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92742.573812] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) As you can see, the battery is now being polled every ~1.5s, which is fine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1944409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1954628] [NEW] [USB-Audio - USB Audio, playback] Headphone output mapped incorrectly
Public bug reported: I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard 'Starship/Matisse HD Audio Controller' controller that has a weird mapping via USB audio (see bug: https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar configuration). Sound via line-out works fine without any interventions. Headphone output however does not, while Ubuntu correctly detects the headphones as being plugged in when selected sound is still output via line-out, instead of via the front panel headphone jack-out. After some debugging I figured the headphones are connected to a seperate Alsa device on the same card as the line-out. Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working audio output that plays just via the headphone out. I guess a quirk needs to be written for the configuration. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gijs 2129 F pulseaudio /dev/snd/pcmC2D1p: gijs 2129 F...m pulseaudio /dev/snd/controlC0: gijs 2129 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 13 09:28:19 2021 InstallationDate: Installed on 2020-12-06 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful Symptom_Card: USB Audio - USB Audio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [USB-Audio - USB Audio, playback] Playback problem UpgradeStatus: Upgraded to impish on 2021-09-28 (75 days ago) dmi.bios.date: 07/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.00 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG X570S TORPEDO MAX (MS-7D54) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.00:bd07/09/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D54:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570STORPEDOMAX(MS-7D54):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7D54 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1954628 Title: [USB-Audio - USB Audio, playback] Headphone output mapped incorrectly Status in alsa-driver package in Ubuntu: New Bug description: I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard 'Starship/Matisse HD Audio Controller' controller that has a weird mapping via USB audio (see bug: https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar configuration). Sound via line-out works fine without any interventions. Headphone output however does not, while Ubuntu correctly detects the headphones as being plugged in when selected sound is still output via line-out, instead of via the front panel headphone jack-out. After some debugging I figured the headphones are connected to a seperate Alsa device on the same card as the line-out. Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working audio output that plays just via the headphone out. I guess a quirk needs to be written for the configuration. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gijs 2129 F pulseaudio /dev/snd/pcmC2D1p: gijs 2129 F...m pulseaudio /dev/snd/controlC0: gijs 2129 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 13 09:28:19 2021 InstallationDate: Installed on 2020-12-06 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful
[Touch-packages] [Bug 1948904] Re: Installed systemd package post-installation script subprocess returned error exit status 127
I can confirm the behavior in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1948904/comments/3 -- 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/1948904 Title: Installed systemd package post-installation script subprocess returned error exit status 127 Status in systemd package in Ubuntu: Confirmed Bug description: The package systemd started giving error after upgrade to 21.10 from 21.04. Setting up systemd (248.3-1ubuntu8) ... systemd-machine-id-setup: error while loading shared libraries: libsystemd-shared-247.so: cannot open shared object file: No such file or directory dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 127 Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) When I tried to force reinstall systemd it gives following error. Internal Error, No file name for systemd:amd64 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: systemd 248.3-1ubuntu8 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Oct 27 12:00:49 2021 InstallationDate: Installed on 2018-11-21 (1070 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:55a4 Shenzhen Goodix Technology Co.,Ltd. Goodix FingerPrint Device Bus 001 Device 002: ID 13d3:5415 IMC Networks Integrated Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 8: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 9: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 480M MachineType: LENOVO 20RAS0D800 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=b69e3e1e-fa29-46b4-8ec8-c6cee754774b ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to impish on 2021-10-19 (7 days ago) dmi.bios.date: 09/14/2020 dmi.bios.release: 1.14 dmi.bios.vendor: LENOVO dmi.bios.version: R16ET28W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20RAS0D800 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrR16ET28W(1.14):bd09/14/2020:br1.14:efr1.11:svnLENOVO:pn20RAS0D800:pvrThinkPadE14:skuLENOVO_MT_20RA_BU_SMB_FM_ThinkPadE14:rvnLENOVO:rn20RAS0D800:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 dmi.product.name: 20RAS0D800 dmi.product.sku: LENOVO_MT_20RA_BU_SMB_FM_ThinkPad E14 dmi.product.version: ThinkPad E14 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1948904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1892825] Re: update-locale not perform correctly sanity checks
I verified the test case using locales 2.31-0ubuntu9.4 from focal- proposed. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1892825 Title: update-locale not perform correctly sanity checks Status in glibc package in Ubuntu: In Progress Status in pam package in Ubuntu: New Status in glibc source package in Bionic: New Status in pam source package in Bionic: New Status in glibc source package in Focal: Fix Committed Status in pam source package in Focal: New Status in glibc source package in Hirsute: New Status in pam source package in Hirsute: New Status in glibc source package in Impish: New Status in pam source package in Impish: New Bug description: [impact] A simple typo using the update-locale script can render a system inoperable without booting into single user mode or similar: $ sudo update-locale LANGUAGE = en_US.UTF-8 $ sudo -s sudo: pam_open_session: Bad item passed to pam_*_item() sudo: policy plugin failed session initialization [test case] $ cp /etc/default/locale /tmp/locale $ update-locale --locale-file /tmp/locale LANGUAGE = en_US.UTF-8 "diff -u /etc/default/locale /tmp/locale" should be empty. [original description] By passing wrong input as following: sudo update-locale LANGUAGE = en_US.UTF-8 result is: ... #LANGUAGE=en = This "equal" sign that was added makes system completely unusable(can't run sudo anymore): bentzy@bentzy-nb:~$ sudo vim /etc/default/locale sudo: pam_open_session: Bad item passed to pam_*_item() sudo: policy plugin failed session initialization Fixed it booting from installation disk and fixing corrupted /etc/default/locale ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: locales 2.31-0ubuntu9 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Aug 25 09:36:03 2020 InstallationDate: Installed on 2020-08-17 (7 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: glibc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1892825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1953694] Re: wayland clipboard handing locks up in certain corner cases
My first search was a miss, I think this is the bug referred to here: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1913775 -- 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/1953694 Title: wayland clipboard handing locks up in certain corner cases Status in evince package in Ubuntu: New Status in firefox package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Bug description: There are a number of cases in gtk+-3.0 3.24.30 on wayland where copy paste from/to various apps fails based on something related to type handling. I've run into this on Ubuntu 21.10, with multiple apps under the ubuntu wayland session. I have not found a matching bug in the Debian BTS, but there is a matching upstream bug and merged fix in upstream gtk+-3 from GNOME as of 20211206. References: https://gitlab.gnome.org/GNOME/gtk/-/issues/4340 https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4058 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1953694/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1954647] [NEW] Only one Icon at a time can be relocated
Public bug reported: If I select more than one icon (using ctrl) and drag to a new desktop location, only one icon moves. Version: 20.04.03 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.450.2 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 13 06:33:50 2021 InstallationDate: Installed on 2021-12-07 (5 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1954647 Title: Only one Icon at a time can be relocated Status in ubuntu-meta package in Ubuntu: New Bug description: If I select more than one icon (using ctrl) and drag to a new desktop location, only one icon moves. Version: 20.04.03 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.450.2 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 13 06:33:50 2021 InstallationDate: Installed on 2021-12-07 (5 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1954647/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1954649] Re: autopkgtest regressions with python3.10 as supported
** Description changed: This bug is for tracking the packages having autopkgtest regressions with python3.10 as a supported version, blocking migration of python3-defaults/3.9.7-4. + + All packages are in universe except pygobject and python-taskflow in + main. + + All packages have RC bugs in Debian except python-taskflow which is + based on a newer upstream version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1954649 Title: autopkgtest regressions with python3.10 as supported Status in ipywidgets package in Ubuntu: New Status in pygobject package in Ubuntu: New Status in pytest-twisted package in Ubuntu: New Status in python-b2sdk package in Ubuntu: New Status in python-hypothesis package in Ubuntu: New Status in python-taskflow package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in supysonic package in Ubuntu: New Status in vorta package in Ubuntu: New Status in ipywidgets package in Debian: Unknown Status in pygobject package in Debian: Unknown Status in pytest-twisted package in Debian: Unknown Status in python-b2sdk package in Debian: Unknown Status in python-hypothesis package in Debian: Unknown Status in supysonic package in Debian: Unknown Status in vorta package in Debian: Unknown Bug description: This bug is for tracking the packages having autopkgtest regressions with python3.10 as a supported version, blocking migration of python3-defaults/3.9.7-4. All packages are in universe except pygobject and python-taskflow in main. All packages have RC bugs in Debian except python-taskflow which is based on a newer upstream version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1954649] Re: autopkgtest regressions with python3.10 as supported
** Changed in: ipywidgets (Debian) Status: Unknown => New ** Changed in: pygobject (Debian) Status: Unknown => New ** Changed in: pytest-twisted (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1954649 Title: autopkgtest regressions with python3.10 as supported Status in ipywidgets package in Ubuntu: New Status in pygobject package in Ubuntu: New Status in pytest-twisted package in Ubuntu: New Status in python-b2sdk package in Ubuntu: New Status in python-hypothesis package in Ubuntu: New Status in python-taskflow package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in supysonic package in Ubuntu: New Status in vorta package in Ubuntu: New Status in ipywidgets package in Debian: New Status in pygobject package in Debian: New Status in pytest-twisted package in Debian: New Status in python-b2sdk package in Debian: Unknown Status in python-hypothesis package in Debian: Unknown Status in supysonic package in Debian: Unknown Status in vorta package in Debian: Unknown Bug description: This bug is for tracking the packages having autopkgtest regressions with python3.10 as a supported version, blocking migration of python3-defaults/3.9.7-4. All packages are in universe except pygobject and python-taskflow in main. All packages have RC bugs in Debian except python-taskflow which is based on a newer upstream version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1954649] [NEW] autopkgtest regressions with python3.10 as supported
Public bug reported: This bug is for tracking the packages having autopkgtest regressions with python3.10 as a supported version, blocking migration of python3-defaults/3.9.7-4. All packages are in universe except pygobject and python-taskflow in main. All packages have RC bugs in Debian except python-taskflow which is based on a newer upstream version. ** Affects: ipywidgets (Ubuntu) Importance: Undecided Status: New ** Affects: pygobject (Ubuntu) Importance: Undecided Status: New ** Affects: pytest-twisted (Ubuntu) Importance: Undecided Status: New ** Affects: python-b2sdk (Ubuntu) Importance: Undecided Status: New ** Affects: python-hypothesis (Ubuntu) Importance: Undecided Status: New ** Affects: python-taskflow (Ubuntu) Importance: Undecided Status: New ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Affects: supysonic (Ubuntu) Importance: Undecided Status: New ** Affects: vorta (Ubuntu) Importance: Undecided Status: New ** Affects: ipywidgets (Debian) Importance: Unknown Status: Unknown ** Affects: pygobject (Debian) Importance: Unknown Status: Unknown ** Affects: pytest-twisted (Debian) Importance: Unknown Status: Unknown ** Affects: python-b2sdk (Debian) Importance: Unknown Status: Unknown ** Affects: python-hypothesis (Debian) Importance: Unknown Status: Unknown ** Affects: supysonic (Debian) Importance: Unknown Status: Unknown ** Affects: vorta (Debian) Importance: Unknown Status: Unknown ** Tags: update-excuse ** Also affects: pygobject (Ubuntu) Importance: Undecided Status: New ** Also affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Also affects: ipywidgets (Ubuntu) Importance: Undecided Status: New ** Also affects: pytest-twisted (Ubuntu) Importance: Undecided Status: New ** Also affects: python-b2sdk (Ubuntu) Importance: Undecided Status: New ** Also affects: python-hypothesis (Ubuntu) Importance: Undecided Status: New ** Also affects: supysonic (Ubuntu) Importance: Undecided Status: New ** Also affects: vorta (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1001343 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001343 ** Also affects: ipywidgets (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001343 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #1001368 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001368 ** Also affects: pygobject (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001368 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #1001371 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001371 ** Also affects: pytest-twisted (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001371 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #1001393 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001393 ** Also affects: python-b2sdk (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001393 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #1001538 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001538 ** Also affects: python-hypothesis (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001538 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #1000717 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000717 ** Also affects: supysonic (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000717 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #1001490 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001490 ** Also affects: vorta (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001490 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1954649 Title: autopkgtest regressions with python3.10 as supported Status in ipywidgets package in Ubuntu: New Status in pygobject package in Ubuntu: New Status in pytest-twisted package in Ubuntu: New Status in python-b2sdk package in Ubuntu: New Status in python-hypothesis package in Ubuntu: New Status in python-taskflow package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in supysonic package in Ubuntu: New Status in vorta package in Ubuntu: New Status in ipywidgets package in Debian: Unknown Status in pygobject package in Debian: Unknown Status in
[Touch-packages] [Bug 1952733] Re: Add Dell Privacy Mic Mute Key mapping for another Dell machine
Hello Andy, or anyone else affected, Accepted systemd into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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: systemd (Ubuntu Impish) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952733 Title: Add Dell Privacy Mic Mute Key mapping for another Dell machine Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952735] Re: Add Microphone mute key mapping for Dell machine
Hello Andy, or anyone else affected, Accepted systemd into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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: systemd (Ubuntu Impish) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952735 Title: Add Microphone mute key mapping for Dell machine Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell machine add new microphone mute key on keyboard, add this key mapping to make it work. [Test Plan] * Use a Dell machine, which has this microphone mute key, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952735/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650688] Re: timedatectl set-timezone fails on UC16
I have accepted this fix for all the prepared systemd SRUs. I see that LP: #1953172 has been created to track the future snapd work, but do you know if work on this is already ongoing? Did you hear anything from the snapd team regarding when we can expect it to land? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1650688 Title: timedatectl set-timezone fails on UC16 Status in Snappy: Triaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: Won't Fix Status in systemd source package in Impish: Won't Fix Status in systemd source package in Jammy: Fix Released Bug description: SRU === [Impact] * The bug prevents timedated from recognizing and correctly set the system's timezone when running Ubuntu Core 16, 18 and 20. * This causes by timedated fails to take Ubuntu Core's /etc/writable redirection into account. * The recognizing part is fixed by making the code take writable redirection into account. * The set part is fixed by making the code link to the absolute path instead of a relative one. * Currently core snaps worked around the set part by providing a wrapper script which re-create /etc/writable/localtime afterward. However this does not cover DBus users. [Test Plan] * On classics systems: ensure the proposed systemd package is installed. On Ubuntu Core systems: build a new core snap including proposed package, and install it. Replaces timedatectl with timedatectl.real to test skipping the wrapper. (Note that one can simulate core snap's /etc/writable redirection by running this image creation hook [1] on the system.) [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- core/hooks/08-etc-writable.chroot?h=ubuntu/focal * On freshly boot system: query the timezone using `timedatectl`. The timezone should corresponds to `readlink -f /etc/localtime` and does not show `n/a`. * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`. `readlink -f /etc/localtime` should points to an existing file. * Run `sudo systemctl restart systemd-timedated.service`. Then, query the timezone again: `timedatectl`. It should show the previously set timezone and not `n/a`. * Run `sudo systemctl status systemd-timedated.service`. This should show no sign of timedated crashing. [Where problems could occur] * It's possible that the redirection handling code will be sub-par and causes crash. However, it's not likely because the similar pieces of code is in the previous patch since Ubuntu 16.04. * If it does: the patched `get_timezone()` function is used in 2 places: the networkd's DHCP server [3] and the timedated itself. - Networkd is used primarily on servers where NetworkManage is absent. It's possible that this patch causes the user to loss access to the server due to networkd crash when setting up network interfaces, and requires physical access to fix. However, the code path is executed when DHCP is enabled only. I think it's not common for users to have networkd's DHCP server enabled: the feature seems to gear towards desktop users wanting to share internet connection, and in those cases they're more likely to use NetworkManager. - The timedated itself is likely used by the programs that involves in time-related functions. If a crash occur, in the worst case users won't be able to set time or timezone via timedated. However, users should still be able to e.g. set time using `date` or set timezone using /etc/localtime (assuming online guides still consider systems without systemd). Timedated is DBus-activated, and thus a crash should be self-healing. * The set part would also affects the clasic systems. However, I believe nothing else actually rely on /etc/localtime being a relative path, otherwise the /etc/writable redirection would causes even more problem, and would have been reported. [3] Yes, I'm surprised that there's a DHCP server inside systemd codebase. [Other Info] * This is also useful for UBports's Ubuntu Touch. We continue using system-image system where the rootfs is read-only, and thus is affected by this bug similarly to Ubuntu Core. I've tested the Focal version of the package on our (currently in development) Focal Ubuntu Touch image, and the fix works. [Original bug description] On a system running UC16, the file /etc/localtime is a link that points to /etc/writable/localtime. On a freshly installed system, /etc/writable/localtime is a fully- qualified link that points at /usr/share/zoneinfo/UTC. If timedatectl is used to set the timezone to something else, timedated updates
[Touch-packages] [Bug 1650688] Re: timedatectl set-timezone fails on UC16
Hello Tony, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.53 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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: systemd (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1650688 Title: timedatectl set-timezone fails on UC16 Status in Snappy: Triaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: Won't Fix Status in systemd source package in Impish: Won't Fix Status in systemd source package in Jammy: Fix Released Bug description: SRU === [Impact] * The bug prevents timedated from recognizing and correctly set the system's timezone when running Ubuntu Core 16, 18 and 20. * This causes by timedated fails to take Ubuntu Core's /etc/writable redirection into account. * The recognizing part is fixed by making the code take writable redirection into account. * The set part is fixed by making the code link to the absolute path instead of a relative one. * Currently core snaps worked around the set part by providing a wrapper script which re-create /etc/writable/localtime afterward. However this does not cover DBus users. [Test Plan] * On classics systems: ensure the proposed systemd package is installed. On Ubuntu Core systems: build a new core snap including proposed package, and install it. Replaces timedatectl with timedatectl.real to test skipping the wrapper. (Note that one can simulate core snap's /etc/writable redirection by running this image creation hook [1] on the system.) [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- core/hooks/08-etc-writable.chroot?h=ubuntu/focal * On freshly boot system: query the timezone using `timedatectl`. The timezone should corresponds to `readlink -f /etc/localtime` and does not show `n/a`. * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`. `readlink -f /etc/localtime` should points to an existing file. * Run `sudo systemctl restart systemd-timedated.service`. Then, query the timezone again: `timedatectl`. It should show the previously set timezone and not `n/a`. * Run `sudo systemctl status systemd-timedated.service`. This should show no sign of timedated crashing. [Where problems could occur] * It's possible that the redirection handling code will be sub-par and causes crash. However, it's not likely because the similar pieces of code is in the previous patch since Ubuntu 16.04. * If it does: the patched `get_timezone()` function is used in 2 places: the networkd's DHCP server [3] and the timedated itself. - Networkd is used primarily on servers where NetworkManage is absent. It's possible that this patch causes the user to loss access to the server due to networkd crash when setting up network interfaces, and requires physical access to fix. However, the code path is executed when DHCP is enabled only. I think it's not common for users to have networkd's DHCP server enabled: the feature seems to gear towards desktop users wanting to share internet connection, and in those cases they're more likely to use NetworkManager. - The timedated itself is likely used by the programs that involves in time-related functions. If a crash occur, in the worst case users won't be able to set time or timezone via timedated. However, users should still be able to e.g. set time using `date` or set timezone using /etc/localtime (assuming online guides still consider systems
[Touch-packages] [Bug 1690891] Re: Remove ureadahead and libnih
Yersterday I upgraded another old laptop from ubuntu 18.04 to ubuntu 20.04 and I see 35 secs slower boot. Guys really ureadahead made a huge impact. Please reconsider enabling it again. I cannot understand how you decided to drop it before doing any real life tests!! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnih in Ubuntu. https://bugs.launchpad.net/bugs/1690891 Title: Remove ureadahead and libnih Status in libnih package in Ubuntu: Fix Released Status in ureadahead package in Ubuntu: Fix Released Bug description: ureadahead does not seem to be working at all these days - no profiles are being collected - and is the only thing left depending on libnih, so let's get rid of it, and then we can get rid of libnih as well. [Original report] Since on common platforms ureadahead solves nothing but causes a huge amount of garbage/totally useless error messages, which makes it really hard to extract the important messages from e.g. journalctl output, it should be removed from ubuntu-minimal. If there are people, who need it, can still explicitly install it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1690891/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1948476] Re: [SRU] Allow target units to fail
Hello Alfonso, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.14 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: systemd (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1948476 Title: [SRU] Allow target units to fail Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [Impact] A systemd regression in focal made it think that target units cannot fail, which produced warnings like: emergency.target: Requested dependency OnFailure=reboot.target ignored (target units cannot fail). So the OnFailure settings are ignored for targets (see https://github.com/snapcore/core-initrd/issues/33 for details). Upstream fixed the issue in v246: https://github.com/systemd/systemd/commit/94d1ddbd7cd15b1073757eb5ae0645c83f0b414c [Test Plan] Test on a UC system and check that the above warnings are not shown anymore. Check that when a target service type fails, the OnFailure setting is used and the mentioned service is run. [Where problems could occur] Issues might happen if some target has an OnFailure setting that was never run in the past because of this bug, and the behavior is not really right because it was never tested. However, OnFailure is not used that much on 20.04 in target services: /lib/systemd $ find . -name \*.target | xargs grep OnFailure /lib/systemd $ /etc/systemd $ find . -name \*.target | xargs grep OnFailure /etc/systemd $ I've seen it only in emergency.target for UC20. [Other Info] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1948476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models
Hello Yao, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.14 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: systemd (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models Status in OEM Priority Project: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: This hwdb update is to avoid unwanted screen rotation when tilting the laptop. This is the update to the previously rolled back SRU LP: #1938259 [Impact] * This fixes unwanted rotations on certain Dell clamshell laptop models with accelerometer. [Test Plan] * On Dell laptops with model SKU 0A36, 0A3E, 0B09, 0B0B, 0B0D, 0B11, install this package and ensure the kernel is updated to the latest. * Screen should be correct side up in login screen and desktop. * Tilt the laptop and the screen should not be rotated. [Where problems could occur] * This is to add parameters for certain models in hwdb, and does not affect any other part of systemd. * Only models with the same Dell SKU would be affected. [scope] this is needed for all releases this is being added to upstream by https://github.com/systemd/systemd/pull/20314 and https://github.com/systemd/systemd/pull/20661 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952599] Re: virt: Support detection for ARM64 Hyper-V guests (fixed upstream)
Hello Gauthier, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.14 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: systemd (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952599 Title: virt: Support detection for ARM64 Hyper-V guests (fixed upstream) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * The detection of Microsoft Hyper-V VMs is done by cpuid currently, however there is no cpuid on ARM64. And since ARM64 is now a supported architecture for Microsoft Hyper-V guests[0], then introduce a more generic way to detect whether a guest is running as a Hyper-V guest: check if /sys/class/dmi/id/product_version starts with "Hyper-V". * This bug has already been fixed upstream[1][2] [Test Plan] * While changes have been made in the kernel for ARM64 on Hyper-V, there is no way to start an ARM64 VM on Hyper-V at the moment. Thus we just want to make sure no regression is introduced. * start an Hyper-V amd64 VM and make sure "systemd-detect-virt" still return MSFT (should still rely on cpuid here) [Where problems could occur] * The main risk is for the system to detect Hyper-V virt erroneously. An issue was reported upstream after the first commit was merged[3]. For this reason, systemd is now looking for "Hyper-V" (in /sys/class/dmi/id/product_version) and not "Microsoft" (in /sys/class/dmi/id/bios_vendor) * This change might also break virt detection on hyper-v AMD64. That's why we need testing. However, AMD64 virt detection should still rely on cpuid instead of DMI as cpuid takes priority over DMI. [0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7aff79e297ee1aa0126924921fd87a4ae59d2467 [1] https://github.com/systemd/systemd/pull/20998/files [2] https://github.com/systemd/systemd/pull/21475/files [3] https://github.com/systemd/systemd/issues/21468 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952599/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952733] Re: Add Dell Privacy Mic Mute Key mapping for another Dell machine
Hello Andy, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.14 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: systemd (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952733 Title: Add Dell Privacy Mic Mute Key mapping for another Dell machine Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639531] Re: GCC compiles programs to shared object instead of executable, preventing GUI file managers from executing programs
The problem is not that it's impossible to work around the incorrect default. The problem is the incorrect default itself. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1639531 Title: GCC compiles programs to shared object instead of executable, preventing GUI file managers from executing programs Status in gcc-defaults: Unknown Status in shared-mime-info: Unknown Status in shared-mime-info package in Ubuntu: Triaged Bug description: Release of Ubuntu being used Description:Ubuntu 16.10 Release:16.10 Version of the package being used = gcc: Installed: 4:6.1.1-1ubuntu2 Candidate: 4:6.1.1-1ubuntu2 Version table: *** 4:6.1.1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status What was expected = Programs compiled using `gcc -o program program.c` should be runnable by double-clicking them from a GUI file manager. Compiling a simple program (`void main() { }`) using Xubuntu 16.04's current version of `gcc` (`gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)`) produces the following output from `/usr/bin/file program`: program: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=signature_here, not stripped This is correct behavior, allowing the executables to run from Nautilus and Thunar. What happened instead = Programs compiled using `gcc -o program program.c` are not runnable by double-clicking them from a GUI file manager, even though they are runnable from the terminal. Compiling a simple program (`void main() { }`) using the current version of `gcc` (`6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)`) produces the following output from `/usr/bin/file program`: program: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=signature_here, not stripped The program is also identified as a "shared library" instead of an "executable" in Thunar, causing it to not be runnable from the GUI. Others are unable to run such programs from Nautilus. To manage notifications about this bug go to: https://bugs.launchpad.net/gcc-defaults/+bug/1639531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
This bug was fixed in the package modemmanager - 1.16.6-2~21.04.1 --- modemmanager (1.16.6-2~21.04.1) hirsute; urgency=medium * Support manual firmware upgrading for Foxconn and Quectel modems. (LP: #1946096) -- Jerry Lee Thu, 21 Oct 2021 10:43:42 +0800 ** Changed in: modemmanager (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Focal: Fix Released Status in modemmanager source package in Hirsute: Fix Released Bug description: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Verify if the modem is working 4. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 5. Using the firmware upgrading application to upgrade the modem’s firmware 6. Verify if the modem’s firmware upgrading is successful 7. Reboot 8. Verify if the upgraded modem firmware is still working --- Regression test --- Verify if one USB modem are still working with these patches for PCIe modems. [Where problems could occur] The requested update has 2 parts: 1. Informative 1.1 Provide more information about modems whose drivers use WWAN subsystem in kernel 5.13 1.2 Modem manufacture's private utilities can use this information to do modem's FW upgrading manually 2. Changes are specific to Foxconn and Quectel modems 2.1 Modified code are only used by Foxconn and Quectel modems during their FW upgrading. (matched by vendor_id and product_id) In current Ubuntu's certification records for modem: * No other modem uses WWAN subsystem in kernel 5.13 * Modem's FW update is not supported via ModemManager ( < v1.18 ) There is no certificated modems can do the firmware upgrading flow for the regression test. This update should not affect existing modems. The problem would be limited to these two mentioned modems. Each carrier mapping .conf file is for a specific modem. ModemManager will load one of the carrier mapping conf files via the modem manufacturer’s plugin ( if the PCIe VID & PID is matched by the plugin.) We cannot verify if the carrier mapping is correct. This relies on the manufacturer to provide the correct mapping. The carrier mapping .conf files is verified by modem’s manufacture according to the tested SIM card published by different countries. Modem manufacturer confirmed that the content in the .conf file is absolutely correct. [Other Info] The firmware and the upgrading utilities can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
This bug was fixed in the package modemmanager - 1.16.6-2~20.04.1 --- modemmanager (1.16.6-2~20.04.1) focal; urgency=medium * Support manual firmware upgrading for Foxconn and Quectel modems. (LP: #1946096) -- Jerry Lee Thu, 21 Oct 2021 10:29:18 +0800 ** Changed in: modemmanager (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Focal: Fix Released Status in modemmanager source package in Hirsute: Fix Released Bug description: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Verify if the modem is working 4. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 5. Using the firmware upgrading application to upgrade the modem’s firmware 6. Verify if the modem’s firmware upgrading is successful 7. Reboot 8. Verify if the upgraded modem firmware is still working --- Regression test --- Verify if one USB modem are still working with these patches for PCIe modems. [Where problems could occur] The requested update has 2 parts: 1. Informative 1.1 Provide more information about modems whose drivers use WWAN subsystem in kernel 5.13 1.2 Modem manufacture's private utilities can use this information to do modem's FW upgrading manually 2. Changes are specific to Foxconn and Quectel modems 2.1 Modified code are only used by Foxconn and Quectel modems during their FW upgrading. (matched by vendor_id and product_id) In current Ubuntu's certification records for modem: * No other modem uses WWAN subsystem in kernel 5.13 * Modem's FW update is not supported via ModemManager ( < v1.18 ) There is no certificated modems can do the firmware upgrading flow for the regression test. This update should not affect existing modems. The problem would be limited to these two mentioned modems. Each carrier mapping .conf file is for a specific modem. ModemManager will load one of the carrier mapping conf files via the modem manufacturer’s plugin ( if the PCIe VID & PID is matched by the plugin.) We cannot verify if the carrier mapping is correct. This relies on the manufacturer to provide the correct mapping. The carrier mapping .conf files is verified by modem’s manufacture according to the tested SIM card published by different countries. Modem manufacturer confirmed that the content in the .conf file is absolutely correct. [Other Info] The firmware and the upgrading utilities can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1944711] Re: restarting systemd-logind loses all existing sessions
Hello Dan, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.14 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: systemd (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1944711 Title: restarting systemd-logind loses all existing sessions Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [impact] restarting the systemd-logind service loses all existing sessions [test case] ubuntu@test-f:~$ loginctl list-sessions SESSION UID USER SEAT TTY 3789 1000 ubuntu pts/0 1 sessions listed. ubuntu@test-f:~$ journalctl -b -u systemd-logind -- Logs begin at Thu 2021-09-23 11:11:57 UTC, end at Thu 2021-09-23 11:22:55 UTC. -- Sep 23 11:22:51 test-f systemd[1]: Starting Login Service... Sep 23 11:22:51 test-f systemd-logind[198]: New seat seat0. Sep 23 11:22:51 test-f systemd[1]: Started Login Service. Sep 23 11:22:52 test-f systemd-logind[198]: New session 3789 of user ubuntu. ubuntu@test-f:~$ sudo systemctl restart systemd-logind ubuntu@test-f:~$ journalctl -b -u systemd-logind -- Logs begin at Thu 2021-09-23 11:11:57 UTC, end at Thu 2021-09-23 11:23:07 UTC. -- Sep 23 11:22:51 test-f systemd[1]: Starting Login Service... Sep 23 11:22:51 test-f systemd-logind[198]: New seat seat0. Sep 23 11:22:51 test-f systemd[1]: Started Login Service. Sep 23 11:22:52 test-f systemd-logind[198]: New session 3789 of user ubuntu. Sep 23 11:23:07 test-f systemd[1]: Stopping Login Service... Sep 23 11:23:07 test-f systemd[1]: systemd-logind.service: Succeeded. Sep 23 11:23:07 test-f systemd[1]: Stopped Login Service. Sep 23 11:23:07 test-f systemd[1]: Starting Login Service... Sep 23 11:23:07 test-f systemd-logind[469]: Failed to add user by file name 1000, ignoring: Invalid argument Sep 23 11:23:07 test-f systemd-logind[469]: User enumeration failed: Invalid argument Sep 23 11:23:07 test-f systemd-logind[469]: User of session 3789 not known. Sep 23 11:23:07 test-f systemd-logind[469]: Session enumeration failed: No such file or directory Sep 23 11:23:07 test-f systemd-logind[469]: New seat seat0. Sep 23 11:23:07 test-f systemd[1]: Started Login Service. ubuntu@test-f:~$ loginctl list-sessions No sessions. [regression potential] any regression would likely occur during a systemd-logind restart, likely causing a loss of current login sessions. [scope] this is needed only in f this is fixed upstream by commit ac4e03d45bcf4ad2e570cabdb218e9bac003cc80 which is included in v246, so this is fixed in h and later already. in b, the function used to parse the /run/systemd/users/* files allows either usernames or uids, so this bug does not exist there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1944711/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650688] Re: timedatectl set-timezone fails on UC16
Hello Tony, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.14 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: systemd (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1650688 Title: timedatectl set-timezone fails on UC16 Status in Snappy: Triaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: Won't Fix Status in systemd source package in Impish: Won't Fix Status in systemd source package in Jammy: Fix Released Bug description: SRU === [Impact] * The bug prevents timedated from recognizing and correctly set the system's timezone when running Ubuntu Core 16, 18 and 20. * This causes by timedated fails to take Ubuntu Core's /etc/writable redirection into account. * The recognizing part is fixed by making the code take writable redirection into account. * The set part is fixed by making the code link to the absolute path instead of a relative one. * Currently core snaps worked around the set part by providing a wrapper script which re-create /etc/writable/localtime afterward. However this does not cover DBus users. [Test Plan] * On classics systems: ensure the proposed systemd package is installed. On Ubuntu Core systems: build a new core snap including proposed package, and install it. Replaces timedatectl with timedatectl.real to test skipping the wrapper. (Note that one can simulate core snap's /etc/writable redirection by running this image creation hook [1] on the system.) [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- core/hooks/08-etc-writable.chroot?h=ubuntu/focal * On freshly boot system: query the timezone using `timedatectl`. The timezone should corresponds to `readlink -f /etc/localtime` and does not show `n/a`. * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`. `readlink -f /etc/localtime` should points to an existing file. * Run `sudo systemctl restart systemd-timedated.service`. Then, query the timezone again: `timedatectl`. It should show the previously set timezone and not `n/a`. * Run `sudo systemctl status systemd-timedated.service`. This should show no sign of timedated crashing. [Where problems could occur] * It's possible that the redirection handling code will be sub-par and causes crash. However, it's not likely because the similar pieces of code is in the previous patch since Ubuntu 16.04. * If it does: the patched `get_timezone()` function is used in 2 places: the networkd's DHCP server [3] and the timedated itself. - Networkd is used primarily on servers where NetworkManage is absent. It's possible that this patch causes the user to loss access to the server due to networkd crash when setting up network interfaces, and requires physical access to fix. However, the code path is executed when DHCP is enabled only. I think it's not common for users to have networkd's DHCP server enabled: the feature seems to gear towards desktop users wanting to share internet connection, and in those cases they're more likely to use NetworkManager. - The timedated itself is likely used by the programs that involves in time-related functions. If a crash occur, in the worst case users won't be able to set time or timezone via timedated. However, users should still be able to e.g. set time using `date` or set timezone using /etc/localtime (assuming online guides still consider systems
[Touch-packages] [Bug 1952735] Re: Add Microphone mute key mapping for Dell machine
Hello Andy, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.14 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: systemd (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952735 Title: Add Microphone mute key mapping for Dell machine Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell machine add new microphone mute key on keyboard, add this key mapping to make it work. [Test Plan] * Use a Dell machine, which has this microphone mute key, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952735/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952599] Re: virt: Support detection for ARM64 Hyper-V guests (fixed upstream)
Hello Gauthier, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.53 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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: systemd (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952599 Title: virt: Support detection for ARM64 Hyper-V guests (fixed upstream) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * The detection of Microsoft Hyper-V VMs is done by cpuid currently, however there is no cpuid on ARM64. And since ARM64 is now a supported architecture for Microsoft Hyper-V guests[0], then introduce a more generic way to detect whether a guest is running as a Hyper-V guest: check if /sys/class/dmi/id/product_version starts with "Hyper-V". * This bug has already been fixed upstream[1][2] [Test Plan] * While changes have been made in the kernel for ARM64 on Hyper-V, there is no way to start an ARM64 VM on Hyper-V at the moment. Thus we just want to make sure no regression is introduced. * start an Hyper-V amd64 VM and make sure "systemd-detect-virt" still return MSFT (should still rely on cpuid here) [Where problems could occur] * The main risk is for the system to detect Hyper-V virt erroneously. An issue was reported upstream after the first commit was merged[3]. For this reason, systemd is now looking for "Hyper-V" (in /sys/class/dmi/id/product_version) and not "Microsoft" (in /sys/class/dmi/id/bios_vendor) * This change might also break virt detection on hyper-v AMD64. That's why we need testing. However, AMD64 virt detection should still rely on cpuid instead of DMI as cpuid takes priority over DMI. [0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7aff79e297ee1aa0126924921fd87a4ae59d2467 [1] https://github.com/systemd/systemd/pull/20998/files [2] https://github.com/systemd/systemd/pull/21475/files [3] https://github.com/systemd/systemd/issues/21468 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952599/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952599] Re: virt: Support detection for ARM64 Hyper-V guests (fixed upstream)
Hello Gauthier, or anyone else affected, Accepted systemd into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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: systemd (Ubuntu Impish) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952599 Title: virt: Support detection for ARM64 Hyper-V guests (fixed upstream) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Focal: New Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * The detection of Microsoft Hyper-V VMs is done by cpuid currently, however there is no cpuid on ARM64. And since ARM64 is now a supported architecture for Microsoft Hyper-V guests[0], then introduce a more generic way to detect whether a guest is running as a Hyper-V guest: check if /sys/class/dmi/id/product_version starts with "Hyper-V". * This bug has already been fixed upstream[1][2] [Test Plan] * While changes have been made in the kernel for ARM64 on Hyper-V, there is no way to start an ARM64 VM on Hyper-V at the moment. Thus we just want to make sure no regression is introduced. * start an Hyper-V amd64 VM and make sure "systemd-detect-virt" still return MSFT (should still rely on cpuid here) [Where problems could occur] * The main risk is for the system to detect Hyper-V virt erroneously. An issue was reported upstream after the first commit was merged[3]. For this reason, systemd is now looking for "Hyper-V" (in /sys/class/dmi/id/product_version) and not "Microsoft" (in /sys/class/dmi/id/bios_vendor) * This change might also break virt detection on hyper-v AMD64. That's why we need testing. However, AMD64 virt detection should still rely on cpuid instead of DMI as cpuid takes priority over DMI. [0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7aff79e297ee1aa0126924921fd87a4ae59d2467 [1] https://github.com/systemd/systemd/pull/20998/files [2] https://github.com/systemd/systemd/pull/21475/files [3] https://github.com/systemd/systemd/issues/21468 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952599/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926547] Re: Add Dell Privacy Mic Mute Key mapping
Hello Andy, or anyone else affected, Accepted systemd into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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: systemd (Ubuntu Impish) Status: New => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1926547 Title: Add Dell Privacy Mic Mute Key mapping Status in OEM Priority Project: Fix Released Status in OEM Priority Project focal series: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd source package in Impish: Fix Committed Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * The change can only work with kernel commit on some specific hardware, ex. Latitude 9520. The commit series is "hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree. https://patchwork.kernel.org/project/alsa-devel/list/?series=465445 * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1926547/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models
Hello Yao, or anyone else affected, Accepted systemd into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. 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: systemd (Ubuntu Impish) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models Status in OEM Priority Project: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: This hwdb update is to avoid unwanted screen rotation when tilting the laptop. This is the update to the previously rolled back SRU LP: #1938259 [Impact] * This fixes unwanted rotations on certain Dell clamshell laptop models with accelerometer. [Test Plan] * On Dell laptops with model SKU 0A36, 0A3E, 0B09, 0B0B, 0B0D, 0B11, install this package and ensure the kernel is updated to the latest. * Screen should be correct side up in login screen and desktop. * Tilt the laptop and the screen should not be rotated. [Where problems could occur] * This is to add parameters for certain models in hwdb, and does not affect any other part of systemd. * Only models with the same Dell SKU would be affected. [scope] this is needed for all releases this is being added to upstream by https://github.com/systemd/systemd/pull/20314 and https://github.com/systemd/systemd/pull/20661 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1946096] Update Released
The verification of the Stable Release Update for modemmanager has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Focal: Fix Released Status in modemmanager source package in Hirsute: Fix Released Bug description: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Verify if the modem is working 4. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 5. Using the firmware upgrading application to upgrade the modem’s firmware 6. Verify if the modem’s firmware upgrading is successful 7. Reboot 8. Verify if the upgraded modem firmware is still working --- Regression test --- Verify if one USB modem are still working with these patches for PCIe modems. [Where problems could occur] The requested update has 2 parts: 1. Informative 1.1 Provide more information about modems whose drivers use WWAN subsystem in kernel 5.13 1.2 Modem manufacture's private utilities can use this information to do modem's FW upgrading manually 2. Changes are specific to Foxconn and Quectel modems 2.1 Modified code are only used by Foxconn and Quectel modems during their FW upgrading. (matched by vendor_id and product_id) In current Ubuntu's certification records for modem: * No other modem uses WWAN subsystem in kernel 5.13 * Modem's FW update is not supported via ModemManager ( < v1.18 ) There is no certificated modems can do the firmware upgrading flow for the regression test. This update should not affect existing modems. The problem would be limited to these two mentioned modems. Each carrier mapping .conf file is for a specific modem. ModemManager will load one of the carrier mapping conf files via the modem manufacturer’s plugin ( if the PCIe VID & PID is matched by the plugin.) We cannot verify if the carrier mapping is correct. This relies on the manufacturer to provide the correct mapping. The carrier mapping .conf files is verified by modem’s manufacture according to the tested SIM card published by different countries. Modem manufacturer confirmed that the content in the .conf file is absolutely correct. [Other Info] The firmware and the upgrading utilities can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1948476] Re: [SRU] Allow target units to fail
This fixes https://github.com/snapcore/core-initrd/issues/33. Tested by building a core20 snap from focal proposed. Before: [6.611137] systemd[1]: systemd 245.4-4ubuntu3.13 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid) [6.628034] systemd[1]: Detected virtualization kvm. [6.629644] systemd[1]: Detected architecture x86-64. [6.706930] systemd[1]: Set hostname to . [7.212069] systemd[1]: emergency.target: Requested dependency OnFailure=reboot.target ignored (target units cannot fail). [7.499630] systemd[1]: Unnecessary job for /dev/vda4 was removed. With the change: [6.160462] systemd[1]: systemd 245.4-4ubuntu3.14 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid) [6.164774] systemd[1]: Detected virtualization kvm. [6.165851] systemd[1]: Detected architecture x86-64. [6.176059] systemd[1]: Set hostname to . [6.521391] systemd[1]: Unnecessary job for /dev/vda4 was removed. ** Bug watch added: github.com/snapcore/core-initrd/issues #33 https://github.com/snapcore/core-initrd/issues/33 ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1948476 Title: [SRU] Allow target units to fail Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [Impact] A systemd regression in focal made it think that target units cannot fail, which produced warnings like: emergency.target: Requested dependency OnFailure=reboot.target ignored (target units cannot fail). So the OnFailure settings are ignored for targets (see https://github.com/snapcore/core-initrd/issues/33 for details). Upstream fixed the issue in v246: https://github.com/systemd/systemd/commit/94d1ddbd7cd15b1073757eb5ae0645c83f0b414c [Test Plan] Test on a UC system and check that the above warnings are not shown anymore. Check that when a target service type fails, the OnFailure setting is used and the mentioned service is run. [Where problems could occur] Issues might happen if some target has an OnFailure setting that was never run in the past because of this bug, and the behavior is not really right because it was never tested. However, OnFailure is not used that much on 20.04 in target services: /lib/systemd $ find . -name \*.target | xargs grep OnFailure /lib/systemd $ /etc/systemd $ find . -name \*.target | xargs grep OnFailure /etc/systemd $ I've seen it only in emergency.target for UC20. [Other Info] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1948476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1954649] Re: autopkgtest regressions with python3.10 as supported
skimage on s390x is also regressed. ** Also affects: skimage (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1954649 Title: autopkgtest regressions with python3.10 as supported Status in ipywidgets package in Ubuntu: New Status in pygobject package in Ubuntu: New Status in pytest-twisted package in Ubuntu: New Status in python-b2sdk package in Ubuntu: New Status in python-hypothesis package in Ubuntu: New Status in python-taskflow package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in skimage package in Ubuntu: New Status in supysonic package in Ubuntu: New Status in vorta package in Ubuntu: New Status in ipywidgets package in Debian: New Status in pygobject package in Debian: New Status in pytest-twisted package in Debian: New Status in python-b2sdk package in Debian: Unknown Status in python-hypothesis package in Debian: Unknown Status in supysonic package in Debian: Unknown Status in vorta package in Debian: Unknown Bug description: This bug is for tracking the packages having autopkgtest regressions with python3.10 as a supported version, blocking migration of python3-defaults/3.9.7-4. All packages are in universe except pygobject and python-taskflow in main. All packages have RC bugs in Debian except python-taskflow which is based on a newer upstream version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1954649] Re: autopkgtest regressions with python3.10 as supported
skimage/s390x was OOM, added to big_packages ** Changed in: skimage (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1954649 Title: autopkgtest regressions with python3.10 as supported Status in ipywidgets package in Ubuntu: New Status in pygobject package in Ubuntu: New Status in pytest-twisted package in Ubuntu: New Status in python-b2sdk package in Ubuntu: New Status in python-hypothesis package in Ubuntu: New Status in python-taskflow package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in skimage package in Ubuntu: Invalid Status in supysonic package in Ubuntu: New Status in vorta package in Ubuntu: New Status in ipywidgets package in Debian: New Status in pygobject package in Debian: New Status in pytest-twisted package in Debian: New Status in python-b2sdk package in Debian: Unknown Status in python-hypothesis package in Debian: Unknown Status in supysonic package in Debian: Unknown Status in vorta package in Debian: Unknown Bug description: This bug is for tracking the packages having autopkgtest regressions with python3.10 as a supported version, blocking migration of python3-defaults/3.9.7-4. All packages are in universe except pygobject and python-taskflow in main. All packages have RC bugs in Debian except python-taskflow which is based on a newer upstream version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1954647] Re: Only one Icon at a time can be relocated
*** This bug is a duplicate of bug 1886322 *** https://bugs.launchpad.net/bugs/1886322 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 1886322, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1886322 Unable to move all selected files on desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1954647 Title: Only one Icon at a time can be relocated Status in ubuntu-meta package in Ubuntu: New Bug description: If I select more than one icon (using ctrl) and drag to a new desktop location, only one icon moves. Version: 20.04.03 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.450.2 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 13 06:33:50 2021 InstallationDate: Installed on 2021-12-07 (5 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1954647/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650688] Re: timedatectl set-timezone fails on UC16
The investigation started just recently. I do not expect a fix to be landed soon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1650688 Title: timedatectl set-timezone fails on UC16 Status in Snappy: Triaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: Won't Fix Status in systemd source package in Impish: Won't Fix Status in systemd source package in Jammy: Fix Released Bug description: SRU === [Impact] * The bug prevents timedated from recognizing and correctly set the system's timezone when running Ubuntu Core 16, 18 and 20. * This causes by timedated fails to take Ubuntu Core's /etc/writable redirection into account. * The recognizing part is fixed by making the code take writable redirection into account. * The set part is fixed by making the code link to the absolute path instead of a relative one. * Currently core snaps worked around the set part by providing a wrapper script which re-create /etc/writable/localtime afterward. However this does not cover DBus users. [Test Plan] * On classics systems: ensure the proposed systemd package is installed. On Ubuntu Core systems: build a new core snap including proposed package, and install it. Replaces timedatectl with timedatectl.real to test skipping the wrapper. (Note that one can simulate core snap's /etc/writable redirection by running this image creation hook [1] on the system.) [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- core/hooks/08-etc-writable.chroot?h=ubuntu/focal * On freshly boot system: query the timezone using `timedatectl`. The timezone should corresponds to `readlink -f /etc/localtime` and does not show `n/a`. * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`. `readlink -f /etc/localtime` should points to an existing file. * Run `sudo systemctl restart systemd-timedated.service`. Then, query the timezone again: `timedatectl`. It should show the previously set timezone and not `n/a`. * Run `sudo systemctl status systemd-timedated.service`. This should show no sign of timedated crashing. [Where problems could occur] * It's possible that the redirection handling code will be sub-par and causes crash. However, it's not likely because the similar pieces of code is in the previous patch since Ubuntu 16.04. * If it does: the patched `get_timezone()` function is used in 2 places: the networkd's DHCP server [3] and the timedated itself. - Networkd is used primarily on servers where NetworkManage is absent. It's possible that this patch causes the user to loss access to the server due to networkd crash when setting up network interfaces, and requires physical access to fix. However, the code path is executed when DHCP is enabled only. I think it's not common for users to have networkd's DHCP server enabled: the feature seems to gear towards desktop users wanting to share internet connection, and in those cases they're more likely to use NetworkManager. - The timedated itself is likely used by the programs that involves in time-related functions. If a crash occur, in the worst case users won't be able to set time or timezone via timedated. However, users should still be able to e.g. set time using `date` or set timezone using /etc/localtime (assuming online guides still consider systems without systemd). Timedated is DBus-activated, and thus a crash should be self-healing. * The set part would also affects the clasic systems. However, I believe nothing else actually rely on /etc/localtime being a relative path, otherwise the /etc/writable redirection would causes even more problem, and would have been reported. [3] Yes, I'm surprised that there's a DHCP server inside systemd codebase. [Other Info] * This is also useful for UBports's Ubuntu Touch. We continue using system-image system where the rootfs is read-only, and thus is affected by this bug similarly to Ubuntu Core. I've tested the Focal version of the package on our (currently in development) Focal Ubuntu Touch image, and the fix works. [Original bug description] On a system running UC16, the file /etc/localtime is a link that points to /etc/writable/localtime. On a freshly installed system, /etc/writable/localtime is a fully- qualified link that points at /usr/share/zoneinfo/UTC. If timedatectl is used to set the timezone to something else, timedated updates the localtime symbolic link with a relative path to the zoneinfo directory, which results in an invalid link. $ sudo timedatectl set-timezone America/Detroit $ sudo timedatectl
[Touch-packages] [Bug 1954649] Re: autopkgtest regressions with python3.10 as supported
** Changed in: python-b2sdk (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1954649 Title: autopkgtest regressions with python3.10 as supported Status in ipywidgets package in Ubuntu: New Status in pygobject package in Ubuntu: New Status in pytest-twisted package in Ubuntu: New Status in python-b2sdk package in Ubuntu: New Status in python-hypothesis package in Ubuntu: New Status in python-taskflow package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in skimage package in Ubuntu: Invalid Status in supysonic package in Ubuntu: New Status in vorta package in Ubuntu: New Status in ipywidgets package in Debian: New Status in pygobject package in Debian: New Status in pytest-twisted package in Debian: New Status in python-b2sdk package in Debian: New Status in python-hypothesis package in Debian: Unknown Status in supysonic package in Debian: Unknown Status in vorta package in Debian: Unknown Bug description: This bug is for tracking the packages having autopkgtest regressions with python3.10 as a supported version, blocking migration of python3-defaults/3.9.7-4. All packages are in universe except pygobject and python-taskflow in main. All packages have RC bugs in Debian except python-taskflow which is based on a newer upstream version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1954696] Re: ssh assert failure: malloc_consolidate(): unaligned fastbin chunk detected
*** This bug is a duplicate of bug 1953187 *** https://bugs.launchpad.net/bugs/1953187 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1953187, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1954696/+attachment/5547354/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1954696/+attachment/5547356/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1954696/+attachment/5547360/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1954696/+attachment/5547361/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1954696/+attachment/5547362/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1954696/+attachment/5547363/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1954696/+attachment/5547364/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1953187 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1954696 Title: ssh assert failure: malloc_consolidate(): unaligned fastbin chunk detected Status in openssh package in Ubuntu: New Bug description: ssh with GSSAPITrustDNS=true causes this crash, reported in Ubuntu 20.04 as well. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: openssh-client 1:8.4p1-6ubuntu2 Uname: Linux 5.13.19.20211207 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AssertionMessage: malloc_consolidate(): unaligned fastbin chunk detected CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Dec 9 19:13:03 2021 ExecutablePath: /usr/bin/ssh InstallationDate: Installed on 2019-10-07 (798 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: ssh -n -tt -S none -o ProxyCommand='/usr/bin/mosh'\ '--family=prefer-inet'\ --fake-proxy\ --\ %h\ %p home -- mosh-server\ 'new'\ '-c'\ '8'\ '-s'\ '-l'\ 'LANG=en_US.UTF-8'\ '-l'\ 'LANGUAGE=en_US'\ '-l'\ 'LC_NUMERIC=en_US.UTF-8'\ '-l'\ 'LC_TIME=en_GB.UTF-8'\ '-l'\ 'LC_COLLATE=en_US.UTF-8'\ '-l'\ 'LC_MONETARY=en_US.UTF-8'\ '-l'\ 'LC_MEASUREMENT=en_US.UTF-8' RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_8.4p1 Ubuntu-6ubuntu2, OpenSSL 1.1.1l 24 Aug 2021 Signal: 6 SourcePackage: openssh StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f880650b13d "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f880650dbc8 "malloc_consolidate(): unaligned fastbin chunk detected") at malloc.c:5543 malloc_consolidate (av=av@entry=0x7f8806544c60 ) at malloc.c:4637 _int_malloc (av=av@entry=0x7f8806544c60 , bytes=bytes@entry=1280) at malloc.c:3852 __GI___libc_malloc (bytes=1280) at malloc.c:3208 Title: ssh assert failure: malloc_consolidate(): unaligned fastbin chunk detected UpgradeStatus: Upgraded to impish on 2021-10-20 (53 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare src sudo video wireshark modified.conffile..etc.apport.crashdb.conf: [modified] modified.conffile..etc.ssh.ssh_config: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-05-06T22:22:53.957540 mtime.conffile..etc.ssh.ssh_config: 2020-06-18T20:59:08.420114 separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1954696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1954724] [NEW] Removing unattended-upgrades removes ubuntu-server-minimal
Public bug reported: On Impish and later, removing unattended-upgrades also removes ubuntu- server-minimal due to ubuntu-server-minimal depending on unattended- upgrades $ sudo apt remove unattended-upgrades ... The following packages will be REMOVED: ubuntu-server-minimal unattended-upgrades 0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. This behaviour has changed since ubuntu-meta 1.471 [1] when the ubuntu- server-minimal metapackage was introduced, declaring unattended-upgrades as Depends. [1] https://launchpadlibrarian.net/550345392/ubuntu- meta_1.470_1.471.diff.gz On Focal, there was no such behaviour on a fresh ubuntu-server install: $ sudo apt remove unattended-upgrades ... The following packages will be REMOVED: unattended-upgrades 0 upgraded, 0 newly installed, 1 to remove and 9 not upgraded. Removing unattended-upgrades is quite popular amongst our users, and they should be allowed to remove the package without removing the ubuntu-server-minimal metapackage. Looking at the source package for ubuntu-meta, unattended-upgrades is only Depends for ubuntu-server-minimal, maybe we should simply remove it? $ grep -Rin "unattended-upgrades" . ./server-minimal-armhf:23:unattended-upgrades ./server-minimal-riscv64:23:unattended-upgrades ./server-minimal-arm64:23:unattended-upgrades ./server-minimal-ppc64el:23:unattended-upgrades ./server-minimal-s390x:24:unattended-upgrades ./server-minimal-amd64:23:unattended-upgrades $ sudo apt rdepends unattended-upgrades unattended-upgrades Reverse Depends: Recommends: python3-software-properties Recommends: ubuntu-mate-desktop Recommends: ubuntu-mate-core Depends: freedombox Recommends: fbx-all Depends: ubuntu-server-minimal ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-meta (Ubuntu Impish) Importance: Undecided Status: New ** Affects: ubuntu-meta (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu Impish) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1954724 Title: Removing unattended-upgrades removes ubuntu-server-minimal Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Impish: New Status in ubuntu-meta source package in Jammy: New Bug description: On Impish and later, removing unattended-upgrades also removes ubuntu- server-minimal due to ubuntu-server-minimal depending on unattended- upgrades $ sudo apt remove unattended-upgrades ... The following packages will be REMOVED: ubuntu-server-minimal unattended-upgrades 0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. This behaviour has changed since ubuntu-meta 1.471 [1] when the ubuntu-server-minimal metapackage was introduced, declaring unattended-upgrades as Depends. [1] https://launchpadlibrarian.net/550345392/ubuntu- meta_1.470_1.471.diff.gz On Focal, there was no such behaviour on a fresh ubuntu-server install: $ sudo apt remove unattended-upgrades ... The following packages will be REMOVED: unattended-upgrades 0 upgraded, 0 newly installed, 1 to remove and 9 not upgraded. Removing unattended-upgrades is quite popular amongst our users, and they should be allowed to remove the package without removing the ubuntu-server-minimal metapackage. Looking at the source package for ubuntu-meta, unattended-upgrades is only Depends for ubuntu-server-minimal, maybe we should simply remove it? $ grep -Rin "unattended-upgrades" . ./server-minimal-armhf:23:unattended-upgrades ./server-minimal-riscv64:23:unattended-upgrades ./server-minimal-arm64:23:unattended-upgrades ./server-minimal-ppc64el:23:unattended-upgrades ./server-minimal-s390x:24:unattended-upgrades ./server-minimal-amd64:23:unattended-upgrades $ sudo apt rdepends unattended-upgrades unattended-upgrades Reverse Depends: Recommends: python3-software-properties Recommends: ubuntu-mate-desktop Recommends: ubuntu-mate-core Depends: freedombox Recommends: fbx-all Depends: ubuntu-server-minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1954724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952733] Re: Add Dell Privacy Mic Mute Key mapping for another Dell machine
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952733 Title: Add Dell Privacy Mic Mute Key mapping for another Dell machine Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952735] Re: Add Microphone mute key mapping for Dell machine
Test on Dell machine, mic mute key works well in impish. [kernel version] linux-oem-20.04d (1011) [systemd version] 248.3-1ubuntu8.1 ** Tags removed: verification-needed-focal verification-needed-impish ** Tags added: verification-done-focal verification-done-impish ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952735 Title: Add Microphone mute key mapping for Dell machine Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell machine add new microphone mute key on keyboard, add this key mapping to make it work. [Test Plan] * Use a Dell machine, which has this microphone mute key, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952735/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1943561] Autopkgtest regression report (systemd/248.3-1ubuntu8.1)
All autopkgtests for the newly accepted systemd (248.3-1ubuntu8.1) for impish have finished running. The following regressions have been reported in tests triggered by the package: dpdk/20.11.3-0ubuntu1 (armhf) casper/1.465 (amd64) diaspora-installer/0.7.15.0+debian1 (s390x, armhf) libvirt-dbus/1.4.0-2ubuntu1 (amd64) exim4/4.94.2-7ubuntu2 (armhf) dovecot/1:2.3.13+dfsg1-1ubuntu3 (armhf) udisks2/2.9.4-1 (arm64) systemd/248.3-1ubuntu8.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/impish/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models Status in OEM Priority Project: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: This hwdb update is to avoid unwanted screen rotation when tilting the laptop. This is the update to the previously rolled back SRU LP: #1938259 [Impact] * This fixes unwanted rotations on certain Dell clamshell laptop models with accelerometer. [Test Plan] * On Dell laptops with model SKU 0A36, 0A3E, 0B09, 0B0B, 0B0D, 0B11, install this package and ensure the kernel is updated to the latest. * Screen should be correct side up in login screen and desktop. * Tilt the laptop and the screen should not be rotated. [Where problems could occur] * This is to add parameters for certain models in hwdb, and does not affect any other part of systemd. * Only models with the same Dell SKU would be affected. [scope] this is needed for all releases this is being added to upstream by https://github.com/systemd/systemd/pull/20314 and https://github.com/systemd/systemd/pull/20661 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926547] Autopkgtest regression report (systemd/248.3-1ubuntu8.1)
All autopkgtests for the newly accepted systemd (248.3-1ubuntu8.1) for impish have finished running. The following regressions have been reported in tests triggered by the package: dpdk/20.11.3-0ubuntu1 (armhf) casper/1.465 (amd64) diaspora-installer/0.7.15.0+debian1 (s390x, armhf) libvirt-dbus/1.4.0-2ubuntu1 (amd64) exim4/4.94.2-7ubuntu2 (armhf) dovecot/1:2.3.13+dfsg1-1ubuntu3 (armhf) udisks2/2.9.4-1 (arm64) systemd/248.3-1ubuntu8.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/impish/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1926547 Title: Add Dell Privacy Mic Mute Key mapping Status in OEM Priority Project: Fix Released Status in OEM Priority Project focal series: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Released Status in systemd source package in Groovy: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd source package in Impish: Fix Committed Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * The change can only work with kernel commit on some specific hardware, ex. Latitude 9520. The commit series is "hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree. https://patchwork.kernel.org/project/alsa-devel/list/?series=465445 * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1926547/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952733] Autopkgtest regression report (systemd/248.3-1ubuntu8.1)
All autopkgtests for the newly accepted systemd (248.3-1ubuntu8.1) for impish have finished running. The following regressions have been reported in tests triggered by the package: dpdk/20.11.3-0ubuntu1 (armhf) casper/1.465 (amd64) diaspora-installer/0.7.15.0+debian1 (s390x, armhf) libvirt-dbus/1.4.0-2ubuntu1 (amd64) exim4/4.94.2-7ubuntu2 (armhf) dovecot/1:2.3.13+dfsg1-1ubuntu3 (armhf) udisks2/2.9.4-1 (arm64) systemd/248.3-1ubuntu8.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/impish/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952733 Title: Add Dell Privacy Mic Mute Key mapping for another Dell machine Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952599] Autopkgtest regression report (systemd/237-3ubuntu10.53)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.53) for bionic have finished running. The following regressions have been reported in tests triggered by the package: openssh/1:7.6p1-4ubuntu0.5 (armhf) linux-hwe-5.0/5.0.0-65.71 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952599 Title: virt: Support detection for ARM64 Hyper-V guests (fixed upstream) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * The detection of Microsoft Hyper-V VMs is done by cpuid currently, however there is no cpuid on ARM64. And since ARM64 is now a supported architecture for Microsoft Hyper-V guests[0], then introduce a more generic way to detect whether a guest is running as a Hyper-V guest: check if /sys/class/dmi/id/product_version starts with "Hyper-V". * This bug has already been fixed upstream[1][2] [Test Plan] * While changes have been made in the kernel for ARM64 on Hyper-V, there is no way to start an ARM64 VM on Hyper-V at the moment. Thus we just want to make sure no regression is introduced. * start an Hyper-V amd64 VM and make sure "systemd-detect-virt" still return MSFT (should still rely on cpuid here) [Where problems could occur] * The main risk is for the system to detect Hyper-V virt erroneously. An issue was reported upstream after the first commit was merged[3]. For this reason, systemd is now looking for "Hyper-V" (in /sys/class/dmi/id/product_version) and not "Microsoft" (in /sys/class/dmi/id/bios_vendor) * This change might also break virt detection on hyper-v AMD64. That's why we need testing. However, AMD64 virt detection should still rely on cpuid instead of DMI as cpuid takes priority over DMI. [0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7aff79e297ee1aa0126924921fd87a4ae59d2467 [1] https://github.com/systemd/systemd/pull/20998/files [2] https://github.com/systemd/systemd/pull/21475/files [3] https://github.com/systemd/systemd/issues/21468 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952599/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952735] Re: Add Microphone mute key mapping for Dell machine
Test on Dell machine, mic mute key works well in focal. [kernel version] linux-oem-20.04d (1011) [systemd version] 245.4-4ubuntu3.14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952735 Title: Add Microphone mute key mapping for Dell machine Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell machine add new microphone mute key on keyboard, add this key mapping to make it work. [Test Plan] * Use a Dell machine, which has this microphone mute key, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952735/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1944409] Re: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling
The difference between your and my setup is that I do not use a docking station. Maybe worth a try if this also happens without it. Upstream bug has been reported here: https://github.com/systemd/systemd/issues/21751 Also, I have a BIOS update that just came out so will install it right now and let you know if that helped. ** Bug watch added: github.com/systemd/systemd/issues #21751 https://github.com/systemd/systemd/issues/21751 -- 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/1944409 Title: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling Status in OEM Priority Project: New Status in systemd package in Ubuntu: Confirmed Bug description: My setup: - Dell Latitude 7520 - Dell WD15 USB C docking station - Ubuntu 20.04.3 - systemd 245.4-4ubuntu3.13 - uname -a: Linux CLIFMI085 5.13.0-1012-oem #16-Ubuntu SMP Tue Sep 7 09:23:08 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux I leave my laptop docked and, after waking it up from sleep, the fans start blowing. After a quick inspection with top/htop, I always see /usr/lib/systemd/systemd-udev consuming 50+% of my CPU. After a quick search, I discover that I can use `udevadm monitor` to check what device is making all this fuss, and this is the output: UDEV [92591.827159] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.873819] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.920022] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92591.967005] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.018200] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.068351] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.115100] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.166201] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.213318] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.261046] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.308824] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.356577] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.403766] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92592.451164] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) As you can see, the battery status is being polled every 0.05s. To fix this, I just need to restart the service with: sudo systemctl restart systemd-udevd systemd-udevd-kernel.socket systemd-udevd-control.socket Afterwards, this is the output of `udevadm monitor`: KERNEL[92739.612371] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92739.646888] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) KERNEL[92741.076823] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92741.099370] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) KERNEL[92742.539438] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) UDEV [92742.573812] change /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply) As you can see, the battery is now being polled every ~1.5s, which is fine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1944409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1919177] Re: Azure: issues with accelerated networking on Hirsute
** No longer affects: linux-azure (Ubuntu) ** No longer affects: linux-azure (Ubuntu Hirsute) ** No longer affects: cloud-init (Ubuntu Hirsute) ** No longer affects: cloud-init (Ubuntu) ** Project changed: cloud-init => ubuntu-translations ** No longer affects: ubuntu-translations -- 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/1919177 Title: Azure: issues with accelerated networking on Hirsute Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Hirsute: New Bug description: [General] On Azure, when provisioning a Hirsute VM with Accelerated Networking enabled, sometimes part of the cloud-init configuration is not applied. Especially, in those cases, the public SSH key is not setup properly. [how to reproduce] Start a VM with AN enabled: ``` az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South" --image 'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY" --accelerated-networking ``` After a moment, try to SSH: if you succeed, delete and recreate a new VM. [troubleshooting] To be able to connect into the VM, run: az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME" ``` In "/run/cloud-init/instance-data.json", I can see: ``` "publicKeys": [ { "keyData": "", "path": "/home/ubuntu/.ssh/authorized_keys" } ], ``` as expected. [workaround] As mentioned, Azure allows the user to run command into the VM without SSH connection. To do so, one can use the Azure CLI: az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME" This example uses "ssh-import-id" but it's also possible to just echo a given public key into /home/ubuntu/.ssh/authorized_keys NOTE: this will only solves the SSH issue, I do not know if this bug affects other things. If so the user would have to apply those things manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1919177/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 982436] Re: can not import pycurl: librtmp.so.0: cannot open shared object file: No such file or directory
[Expired for pycurl (Ubuntu Trusty) because there has been no activity for 60 days.] ** Changed in: pycurl (Ubuntu Trusty) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/982436 Title: can not import pycurl: librtmp.so.0: cannot open shared object file: No such file or directory Status in pycurl package in Ubuntu: Expired Status in pycurl source package in Precise: Won't Fix Status in pycurl source package in Trusty: Expired Status in pycurl source package in Utopic: Won't Fix Bug description: when I typed this in teminal, there showed report window with this sentence ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.7 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic i686 ApportVersion: 2.0.1-0ubuntu3 Architecture: i386 Date: Sun Apr 15 18:28:41 2012 ExecutablePath: /usr/bin/add-apt-repository InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/add-apt-repository ppa:webupd8team/gnome3 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 LANGUAGE=en_US:en SHELL=/bin/bash PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:webupd8team/gnome3'] SourcePackage: software-properties Title: add-apt-repository crashed with ImportError in /usr/lib/python2.7/dist-packages/softwareproperties/ppa.py: librtmp.so.0: cannot open shared object file: No such file or directory UpgradeStatus: Upgraded to precise on 2012-04-06 (9 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/982436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1927192] Re: gdb ftbfs on armhf, testsuite timeouts
** Changed in: glibc (Ubuntu Groovy) Status: Opinion => Won't Fix ** Changed in: glibc (Ubuntu Hirsute) Status: Opinion => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Released Status in gdb source package in Focal: New Status in glibc source package in Focal: Fix Committed Status in gdb source package in Groovy: Won't Fix Status in glibc source package in Groovy: Won't Fix Status in gdb source package in Hirsute: Won't Fix Status in glibc source package in Hirsute: Won't Fix Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Released Bug description: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: $ /lib/*/ld-2.31.so libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a notable increase in file size and it may be performance critical 109K stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped on other architectures, but the test plan covers checking that, at least on amd64. Other than those not stripping ld.so should not cause any issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952599] Autopkgtest regression report (systemd/248.3-1ubuntu8.1)
All autopkgtests for the newly accepted systemd (248.3-1ubuntu8.1) for impish have finished running. The following regressions have been reported in tests triggered by the package: dpdk/20.11.3-0ubuntu1 (armhf) casper/1.465 (amd64) diaspora-installer/0.7.15.0+debian1 (s390x, armhf) libvirt-dbus/1.4.0-2ubuntu1 (amd64) exim4/4.94.2-7ubuntu2 (armhf) dovecot/1:2.3.13+dfsg1-1ubuntu3 (armhf) udisks2/2.9.4-1 (arm64) systemd/248.3-1ubuntu8.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/impish/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952599 Title: virt: Support detection for ARM64 Hyper-V guests (fixed upstream) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * The detection of Microsoft Hyper-V VMs is done by cpuid currently, however there is no cpuid on ARM64. And since ARM64 is now a supported architecture for Microsoft Hyper-V guests[0], then introduce a more generic way to detect whether a guest is running as a Hyper-V guest: check if /sys/class/dmi/id/product_version starts with "Hyper-V". * This bug has already been fixed upstream[1][2] [Test Plan] * While changes have been made in the kernel for ARM64 on Hyper-V, there is no way to start an ARM64 VM on Hyper-V at the moment. Thus we just want to make sure no regression is introduced. * start an Hyper-V amd64 VM and make sure "systemd-detect-virt" still return MSFT (should still rely on cpuid here) [Where problems could occur] * The main risk is for the system to detect Hyper-V virt erroneously. An issue was reported upstream after the first commit was merged[3]. For this reason, systemd is now looking for "Hyper-V" (in /sys/class/dmi/id/product_version) and not "Microsoft" (in /sys/class/dmi/id/bios_vendor) * This change might also break virt detection on hyper-v AMD64. That's why we need testing. However, AMD64 virt detection should still rely on cpuid instead of DMI as cpuid takes priority over DMI. [0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7aff79e297ee1aa0126924921fd87a4ae59d2467 [1] https://github.com/systemd/systemd/pull/20998/files [2] https://github.com/systemd/systemd/pull/21475/files [3] https://github.com/systemd/systemd/issues/21468 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1952599/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861598] Re: lightdm assumes pam-kwallet to be always installed
*** This bug is a duplicate of bug 1768488 *** https://bugs.launchpad.net/bugs/1768488 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1861598 Title: lightdm assumes pam-kwallet to be always installed Status in lightdm package in Ubuntu: Confirmed Bug description: During boot, I see this error: > Feb 02 10:50:05 myhost lightdm[3224]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory > Feb 02 10:50:05 myhost lightdm[3224]: PAM adding faulty module: pam_kwallet.so > Feb 02 10:50:05 myhost lightdm[3224]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory > Feb 02 10:50:05 myhost lightdm[3224]: PAM adding faulty module: pam_kwallet5.so which I guess it's caused by this: > # grep kwallet /etc/pam.d/lightd* > /etc/pam.d/lightdm:authoptionalpam_kwallet.so > /etc/pam.d/lightdm:authoptionalpam_kwallet5.so > /etc/pam.d/lightdm:session optionalpam_kwallet.so auto_start > /etc/pam.d/lightdm:session optionalpam_kwallet5.so auto_start > /etc/pam.d/lightdm-greeter:authoptionalpam_kwallet.so > /etc/pam.d/lightdm-greeter:authoptionalpam_kwallet5.so > /etc/pam.d/lightdm-greeter:session optionalpam_kwallet.so auto_start > /etc/pam.d/lightdm-greeter:session optionalpam_kwallet5.so auto_start kwallet is a KDE program, which is not installed on MATE (and I think it shouldn't be), so I guess that such modules should not be [attempted to be] loaded. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Sun Feb 2 11:03:53 2020 InstallationDate: Installed on 2020-01-20 (12 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1861598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1954742] [NEW] Sound starts delayed (4sec) when using HDMI audio
Public bug reported: Reproduce: - Connect notebook to external monitor via HDMI - Start random video in youtube / vlc player Actual: - Sound starts with about 4secs of delay Reproducible: always Misc: The package is just a guess. lsb_release -rd Description:Ubuntu 21.10 Release:21.10 apt-cache policy pulseaudio pulseaudio: Installed: 1:15.0+dfsg1-1ubuntu2.2 Candidate: 1:15.0+dfsg1-1ubuntu2.2 Version table: *** 1:15.0+dfsg1-1ubuntu2.2 1 (phased 20%) 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:15.0+dfsg1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nimono 2373 F pulseaudio /dev/snd/pcmC0D3p: nimono 2373 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Dec 14 15:20:56 2021 SourcePackage: pulseaudio UpgradeStatus: Upgraded to impish on 2021-12-08 (6 days ago) dmi.bios.date: 01/23/2018 dmi.bios.release: 1.7 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:br1.7:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr:sku: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2021-12-08T10:02:48.239277 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1954742 Title: Sound starts delayed (4sec) when using HDMI audio Status in pulseaudio package in Ubuntu: New Bug description: Reproduce: - Connect notebook to external monitor via HDMI - Start random video in youtube / vlc player Actual: - Sound starts with about 4secs of delay Reproducible: always Misc: The package is just a guess. lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 apt-cache policy pulseaudio pulseaudio: Installed: 1:15.0+dfsg1-1ubuntu2.2 Candidate: 1:15.0+dfsg1-1ubuntu2.2 Version table: *** 1:15.0+dfsg1-1ubuntu2.2 1 (phased 20%) 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:15.0+dfsg1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nimono 2373 F pulseaudio /dev/snd/pcmC0D3p: nimono 2373 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Dec 14 15:20:56 2021 SourcePackage: pulseaudio UpgradeStatus: Upgraded to impish on 2021-12-08 (6 days ago) dmi.bios.date: 01/23/2018 dmi.bios.release: 1.7 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:br1.7:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr:sku: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2021-12-08T10:02:48.239277 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1954742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1954724] Re: Removing unattended-upgrades removes ubuntu-server-minimal
** Description changed: On Impish and later, removing unattended-upgrades also removes ubuntu- server-minimal due to ubuntu-server-minimal depending on unattended- upgrades $ sudo apt remove unattended-upgrades ... The following packages will be REMOVED: - ubuntu-server-minimal unattended-upgrades + ubuntu-server-minimal unattended-upgrades 0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. This behaviour has changed since ubuntu-meta 1.471 [1] when the ubuntu- server-minimal metapackage was introduced, declaring unattended-upgrades as Depends. [1] https://launchpadlibrarian.net/550345392/ubuntu- meta_1.470_1.471.diff.gz On Focal, there was no such behaviour on a fresh ubuntu-server install: $ sudo apt remove unattended-upgrades ... The following packages will be REMOVED: - unattended-upgrades + unattended-upgrades 0 upgraded, 0 newly installed, 1 to remove and 9 not upgraded. Removing unattended-upgrades is quite popular amongst our users, and they should be allowed to remove the package without removing the ubuntu-server-minimal metapackage. Looking at the source package for ubuntu-meta, unattended-upgrades is only Depends for ubuntu-server-minimal, maybe we should simply remove - it? + it, or instead, change to recommends? $ grep -Rin "unattended-upgrades" . ./server-minimal-armhf:23:unattended-upgrades ./server-minimal-riscv64:23:unattended-upgrades ./server-minimal-arm64:23:unattended-upgrades ./server-minimal-ppc64el:23:unattended-upgrades ./server-minimal-s390x:24:unattended-upgrades ./server-minimal-amd64:23:unattended-upgrades $ sudo apt rdepends unattended-upgrades unattended-upgrades Reverse Depends: - Recommends: python3-software-properties - Recommends: ubuntu-mate-desktop - Recommends: ubuntu-mate-core - Depends: freedombox - Recommends: fbx-all - Depends: ubuntu-server-minimal + Recommends: python3-software-properties + Recommends: ubuntu-mate-desktop + Recommends: ubuntu-mate-core + Depends: freedombox + Recommends: fbx-all + Depends: ubuntu-server-minimal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1954724 Title: Removing unattended-upgrades removes ubuntu-server-minimal Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Impish: New Status in ubuntu-meta source package in Jammy: New Bug description: On Impish and later, removing unattended-upgrades also removes ubuntu- server-minimal due to ubuntu-server-minimal depending on unattended- upgrades $ sudo apt remove unattended-upgrades ... The following packages will be REMOVED: ubuntu-server-minimal unattended-upgrades 0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. This behaviour has changed since ubuntu-meta 1.471 [1] when the ubuntu-server-minimal metapackage was introduced, declaring unattended-upgrades as Depends. [1] https://launchpadlibrarian.net/550345392/ubuntu- meta_1.470_1.471.diff.gz On Focal, there was no such behaviour on a fresh ubuntu-server install: $ sudo apt remove unattended-upgrades ... The following packages will be REMOVED: unattended-upgrades 0 upgraded, 0 newly installed, 1 to remove and 9 not upgraded. Removing unattended-upgrades is quite popular amongst our users, and they should be allowed to remove the package without removing the ubuntu-server-minimal metapackage. Looking at the source package for ubuntu-meta, unattended-upgrades is only Depends for ubuntu-server-minimal, maybe we should simply remove it, or instead, change to recommends? $ grep -Rin "unattended-upgrades" . ./server-minimal-armhf:23:unattended-upgrades ./server-minimal-riscv64:23:unattended-upgrades ./server-minimal-arm64:23:unattended-upgrades ./server-minimal-ppc64el:23:unattended-upgrades ./server-minimal-s390x:24:unattended-upgrades ./server-minimal-amd64:23:unattended-upgrades $ sudo apt rdepends unattended-upgrades unattended-upgrades Reverse Depends: Recommends: python3-software-properties Recommends: ubuntu-mate-desktop Recommends: ubuntu-mate-core Depends: freedombox Recommends: fbx-all Depends: ubuntu-server-minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1954724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 982436] Re: can not import pycurl: librtmp.so.0: cannot open shared object file: No such file or directory
[Expired for pycurl (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pycurl (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/982436 Title: can not import pycurl: librtmp.so.0: cannot open shared object file: No such file or directory Status in pycurl package in Ubuntu: Expired Status in pycurl source package in Precise: Won't Fix Status in pycurl source package in Trusty: Expired Status in pycurl source package in Utopic: Won't Fix Bug description: when I typed this in teminal, there showed report window with this sentence ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.7 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic i686 ApportVersion: 2.0.1-0ubuntu3 Architecture: i386 Date: Sun Apr 15 18:28:41 2012 ExecutablePath: /usr/bin/add-apt-repository InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/add-apt-repository ppa:webupd8team/gnome3 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 LANGUAGE=en_US:en SHELL=/bin/bash PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:webupd8team/gnome3'] SourcePackage: software-properties Title: add-apt-repository crashed with ImportError in /usr/lib/python2.7/dist-packages/softwareproperties/ppa.py: librtmp.so.0: cannot open shared object file: No such file or directory UpgradeStatus: Upgraded to precise on 2012-04-06 (9 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/982436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952733] Re: Add Dell Privacy Mic Mute Key mapping for another Dell machine
Test with machine which supports Dell privacy. Mic mute key works well in impish. [kernel version] linux-oem-20.04d (1011) [systemd version] 248.3-1ubuntu8.1 ** Tags removed: verification-needed verification-needed-impish ** Tags added: verification-done verification-done-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952733 Title: Add Dell Privacy Mic Mute Key mapping for another Dell machine Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1952733] Re: Add Dell Privacy Mic Mute Key mapping for another Dell machine
Test with machine which supports Dell privacy. Mic mute key works well in focal. [kernel version] linux-oem-20.04d (1011) [systemd version] 245.4-4ubuntu3.14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952733 Title: Add Dell Privacy Mic Mute Key mapping for another Dell machine Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell introduces new function called Dell Privacy, it utilizes hardware mute to control audio and camera. The commit map the reported key event to mic mute for making userspace can work as before, "Mic Mute" dialog pop-up while the mic mute button is pressed. [Test Plan] * Use a Dell machine, which has Dell privacy function, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
** No longer affects: systemd (Ubuntu) ** No longer affects: systemd (Ubuntu Hirsute) ** No longer affects: udev (Ubuntu) ** No longer affects: udev (Ubuntu Hirsute) -- 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/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: SRU Justification [Impact] Hot removal of disks under kvm on s390 does not result in the kernel removing the block device, which can lead to hung tasks and other issues. [Test Plan] See steps to reproduce the bug in the original description below. To test, execute these steps and confirm that the block device gets removed as expected. [Where problems could occur] The fix is a revert of the changes which introduced this regression. The original commit was a removal of supposedly unused code, but it seems a mistake was made in the logic around unregistering of disks. Reverting the changes could have potential to introduce bugs related to other virt devices, especially if it interacts badly with subsequent driver changes. However, the patch reverted cleanly, and reverting restores the code to the state which has been working well in previous kernels and seems like the lowest risk option until a proper fix is available upstream. --- Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
[Touch-packages] [Bug 1650688] Autopkgtest regression report (systemd/237-3ubuntu10.53)
All autopkgtests for the newly accepted systemd (237-3ubuntu10.53) for bionic have finished running. The following regressions have been reported in tests triggered by the package: openssh/1:7.6p1-4ubuntu0.5 (armhf) linux-hwe-5.0/5.0.0-65.71 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1650688 Title: timedatectl set-timezone fails on UC16 Status in Snappy: Triaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: Won't Fix Status in systemd source package in Impish: Won't Fix Status in systemd source package in Jammy: Fix Released Bug description: SRU === [Impact] * The bug prevents timedated from recognizing and correctly set the system's timezone when running Ubuntu Core 16, 18 and 20. * This causes by timedated fails to take Ubuntu Core's /etc/writable redirection into account. * The recognizing part is fixed by making the code take writable redirection into account. * The set part is fixed by making the code link to the absolute path instead of a relative one. * Currently core snaps worked around the set part by providing a wrapper script which re-create /etc/writable/localtime afterward. However this does not cover DBus users. [Test Plan] * On classics systems: ensure the proposed systemd package is installed. On Ubuntu Core systems: build a new core snap including proposed package, and install it. Replaces timedatectl with timedatectl.real to test skipping the wrapper. (Note that one can simulate core snap's /etc/writable redirection by running this image creation hook [1] on the system.) [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu- core/hooks/08-etc-writable.chroot?h=ubuntu/focal * On freshly boot system: query the timezone using `timedatectl`. The timezone should corresponds to `readlink -f /etc/localtime` and does not show `n/a`. * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`. `readlink -f /etc/localtime` should points to an existing file. * Run `sudo systemctl restart systemd-timedated.service`. Then, query the timezone again: `timedatectl`. It should show the previously set timezone and not `n/a`. * Run `sudo systemctl status systemd-timedated.service`. This should show no sign of timedated crashing. [Where problems could occur] * It's possible that the redirection handling code will be sub-par and causes crash. However, it's not likely because the similar pieces of code is in the previous patch since Ubuntu 16.04. * If it does: the patched `get_timezone()` function is used in 2 places: the networkd's DHCP server [3] and the timedated itself. - Networkd is used primarily on servers where NetworkManage is absent. It's possible that this patch causes the user to loss access to the server due to networkd crash when setting up network interfaces, and requires physical access to fix. However, the code path is executed when DHCP is enabled only. I think it's not common for users to have networkd's DHCP server enabled: the feature seems to gear towards desktop users wanting to share internet connection, and in those cases they're more likely to use NetworkManager. - The timedated itself is likely used by the programs that involves in time-related functions. If a crash occur, in the worst case users won't be able to set time or timezone via timedated. However, users should still be able to e.g. set time using `date` or set timezone using /etc/localtime (assuming online guides still consider systems without systemd). Timedated is DBus-activated, and thus a crash should be self-healing. * The set part would also affects the clasic systems. However, I believe nothing else actually rely on /etc/localtime being a relative path, otherwise the /etc/writable redirection would causes even more problem, and would have been reported. [3] Yes, I'm surprised that there's a DHCP server inside systemd codebase. [Other Info] * This is also useful for UBports's Ubuntu Touch. We continue using system-image system where the rootfs is read-only, and thus is affected by this bug similarly to Ubuntu Core. I've tested the Focal version of the package on our (currently in development) Focal Ubuntu Touch image, and the fix works.
[Touch-packages] [Bug 1952735] Autopkgtest regression report (systemd/248.3-1ubuntu8.1)
All autopkgtests for the newly accepted systemd (248.3-1ubuntu8.1) for impish have finished running. The following regressions have been reported in tests triggered by the package: dpdk/20.11.3-0ubuntu1 (armhf) casper/1.465 (amd64) diaspora-installer/0.7.15.0+debian1 (s390x, armhf) libvirt-dbus/1.4.0-2ubuntu1 (amd64) exim4/4.94.2-7ubuntu2 (armhf) dovecot/1:2.3.13+dfsg1-1ubuntu3 (armhf) udisks2/2.9.4-1 (arm64) systemd/248.3-1ubuntu8.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/impish/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1952735 Title: Add Microphone mute key mapping for Dell machine Status in OEM Priority Project: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Committed Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * Dell machine add new microphone mute key on keyboard, add this key mapping to make it work. [Test Plan] * Use a Dell machine, which has this microphone mute key, and press mic mute key. GUI will pop up "Mic Mute" icon. [Where problems could occur] * This change adds key event mapping in hwdb, which won't impact other hardware. any regression would likely cause problems with key(s) from the specific dell kb matching the modified listing in the hw db. [Other Info] * This change has been verified on Dell machine. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952735/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1954649] Re: autopkgtest regressions with python3.10 as supported
** Changed in: supysonic (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1954649 Title: autopkgtest regressions with python3.10 as supported Status in ipywidgets package in Ubuntu: New Status in pygobject package in Ubuntu: New Status in pytest-twisted package in Ubuntu: New Status in python-b2sdk package in Ubuntu: New Status in python-hypothesis package in Ubuntu: New Status in python-taskflow package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Status in skimage package in Ubuntu: Invalid Status in supysonic package in Ubuntu: New Status in vorta package in Ubuntu: New Status in ipywidgets package in Debian: New Status in pygobject package in Debian: New Status in pytest-twisted package in Debian: New Status in python-b2sdk package in Debian: New Status in python-hypothesis package in Debian: Unknown Status in supysonic package in Debian: New Status in vorta package in Debian: Unknown Bug description: This bug is for tracking the packages having autopkgtest regressions with python3.10 as a supported version, blocking migration of python3-defaults/3.9.7-4. All packages are in universe except pygobject and python-taskflow in main. All packages have RC bugs in Debian except python-taskflow which is based on a newer upstream version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1953694] Re: wayland clipboard handing locks up in certain corner cases
*** This bug is a duplicate of bug 1913775 *** https://bugs.launchpad.net/bugs/1913775 ** This bug has been marked a duplicate of bug 1913775 Copy from Firefox Wayland fails to be pasted anywhere else -- 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/1953694 Title: wayland clipboard handing locks up in certain corner cases Status in evince package in Ubuntu: New Status in firefox package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Bug description: There are a number of cases in gtk+-3.0 3.24.30 on wayland where copy paste from/to various apps fails based on something related to type handling. I've run into this on Ubuntu 21.10, with multiple apps under the ubuntu wayland session. I have not found a matching bug in the Debian BTS, but there is a matching upstream bug and merged fix in upstream gtk+-3 from GNOME as of 20211206. References: https://gitlab.gnome.org/GNOME/gtk/-/issues/4340 https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/4058 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1953694/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1954698] [NEW] Cannot read exit status/time for type=forking w/ short-lived command
Public bug reported: Package: systemd Version: 245.4-4ubuntu3.13 When running a systemd unit where type=forking and setting a pidfile (example at the end of the description), if the process referred to by the pid in the pidfile exits before systemd has read the file, systemd complains (visible in journald logs) "New main PID does not exist or is a zombie." The problem is systemd never records the actual exit status, and querying them from the unit properties shows that the exit status is 0/success even though it exited non-zero. The "Result" property on the unit is "protocol", indicating that we've run afoul of the forking protocol with systemd. In this case we haven't really broken protocol just that we've exposed a race with monitoring the forked process. This can happen with any sort of error in the forked process, Since systemd should be reaping the process anyway, it seems like we should be able to get a correct exit status here. If there is a small delay between starting the process and the exit then systemd has enough time to attach to the process and monitor correctly. The properties one would normally check on this process are all zeroed out: ExecMainStartTimestampMonotonic=0 ExecMainExitTimestampMonotonic=0 ExecMainPID=0 ExecMainCode=0 ExecMainStatus=0 As is the `EXIT_STATUS` environment variable passed along to any "ExecStop" commands. In some cases I've seen the "stop_time" set in the ExecStart properties of the service, but found this to be unreliable. I've tried working around this by keeping the control process alive to wait and see if the forked process exits quickly and recording the exit status myself. This is a decent work-around however causes some extra overhead, and seems like it gets into the territory of what I'd expect systemd to do for me. The example below is just simulating what might happen with a real process that errors out quickly. Example: cat << EOF > /tmp/systemd-forking-bug.sh #!/usr/bin/env bash ( echo \$BASHPID > \$PIDFILE exit 1 ) & echo control process exiting EOF cat << EOF > /tmp/systemd-forking-bug.service [Service] Type=forking PIDFile=/tmp/systemd-forking-bug.pid ExecStart=/bin/bash /tmp/systemd-forking-bug.sh EOF sudo mv /tmp/systemd-forking-bug.service /run/systemd/system/ sudo systemctl daemon-reload sudo systemctl start systemd-forking-bug.service sudo systemctl status systemd-forking-bug.service sudo journalctl --lines=5 -u systemd-forking-bug.service ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: Package: systemd Version: 245.4-4ubuntu3.13 When running a systemd unit where type=forking and setting a pidfile (example at the end of the description), if the process referred to by the pid in the pidfile exits before systemd has read the file, systemd complains (visible in journald logs) "New main PID does not exist or is a zombie." - The problem is systemd never records the actual exit status, and querying them from the unit properties shows that the exit status is 0/success even though. + The problem is systemd never records the actual exit status, and querying them from the unit properties shows that the exit status is 0/success even though it exited non-zero. The "Result" property on the unit is "protocol", signifying that we've run afoul of the forking protocol with systemd. In this case we haven't really broken protocol just that we've exposed a race between monitoring the forked process. - This can happen with any sort of error in the forked process, + This can happen with any sort of error in the forked process, Since systemd should be reaping the process anyway, it seems like we should be able to get a correct exit status here. If there is a small delay between starting the process and the exit then systemd has enough time to attach to the process and monitor correctly. The properties one would normally check on this process are all zeroed out: ExecMainStartTimestampMonotonic=0 ExecMainExitTimestampMonotonic=0 ExecMainPID=0 ExecMainCode=0 ExecMainStatus=0 As is the `EXIT_STATUS` environment variable passed along to any "ExecStop" commands. In some cases I've seen the "stop_time" set in the ExecStart properties of the service, but found this to be unreliable. I've tried working around this by keeping the control process alive to wait and see if the forked process exits quickly and recording the exit status myself. This is a decent work-around however causes some extra overhead, and seems like it gets into the territory of what I'd expect systemd to do for me. The example below is just simulating what might happen with a real process that errors out quickly. Example: cat << EOF > /tmp/systemd-forking-bug.sh #!/usr/bin/env bash ( - echo \$BASHPID > \$PIDFILE - exit 1 + echo \$BASHPID > \$PIDFILE + exit 1 ) & echo control process exiting EOF -
[Touch-packages] [Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else
Indeed, and this appears to be a GTK bug (https://gitlab.gnome.org/GNOME/gtk/-/issues/4340), for which a fix was merged a week ago. For reference, the upstream firefox bug was https://bugzilla.mozilla.org/show_bug.cgi?id=1722369. ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4340 https://gitlab.gnome.org/GNOME/gtk/-/issues/4340 ** Also affects: gtk via https://gitlab.gnome.org/GNOME/gtk/-/issues/4340 Importance: Unknown Status: Unknown ** Changed in: firefox (Ubuntu) Status: Confirmed => Invalid ** Bug watch added: Mozilla Bugzilla #1722369 https://bugzilla.mozilla.org/show_bug.cgi?id=1722369 ** Tags added: rls-jj-incoming -- 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/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else Status in GTK+: Unknown Status in firefox package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: New Bug description: Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS, on Wayland native Version 84.0.2 Build ID 20210105180113 Window Protocol wayland Desktop Environment gnome DESCRIPTION OF THE PROBLEM: If I copy text from a web page and try to paste it into another Firefox page, the text is pasted correctly. If I copy text from a web page and try to paste it in [gedit, libreoffice, thunderbird, terminal, slack (electron)] nothing happens. The Gnome Clipboard extension stays empty when content is copied from Firefox Wayland. Pasting *from* another app *to* Firefox works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1913775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp