[Touch-packages] [Bug 1942161] [NEW] Keyboard shortcuts don't work
Public bug reported: I used Hubstaff for time tracking and it has a keyboard shortcut as `Ctrl+Shift+Alt+T` to turn on/off the timer. I don't know why it doesn't work or what programs does it affect the shortcut as it works occasionally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 31 10:33:28 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 3GB] [1462:3285] InstallationDate: Installed on 2021-08-21 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: MSI MS-7A39 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=1d7fea11-a01e-4f83-9e25-3a0e8fab7620 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.50 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A320M GRENADE (MS-7A39) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.50:bd09/20/2017:br5.12:svnMSI:pnMS-7A39:pvr2.0:rvnMSI:rnA320MGRENADE(MS-7A39):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A39 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1942161 Title: Keyboard shortcuts don't work Status in xorg package in Ubuntu: New Bug description: I used Hubstaff for time tracking and it has a keyboard shortcut as `Ctrl+Shift+Alt+T` to turn on/off the timer. I don't know why it doesn't work or what programs does it affect the shortcut as it works occasionally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 31 10:33:28 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 1060 3GB] [1462:3285] InstallationDate: Installed on 2021-08-21 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: MSI MS-7A39 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=1d7fea11-a01e-4f83-9e25-3a0e8fab7620 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.50 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A320M GRENADE (MS-7A39) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.50:bd09/20/2017:br5.12:svnMSI:pnMS-7A39:pvr2.0:rvnMSI:rnA320MGRENADE(MS-7A39):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A39 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0
[Touch-packages] [Bug 1837937] Re: CRASH
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1837937 Title: CRASH Status in linux package in Ubuntu: Expired Status in systemd package in Ubuntu: Invalid Bug description: The screen froze but the mouse was still moving then it all froze and said systemd-journal not able to write entry. I had to press the power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-9-generic 5.2.0-9.10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2068 F pulseaudio /dev/snd/controlC0: administrator 2068 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:11:47 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-9-generic N/A linux-backports-modules-5.2.0-9-generic N/A linux-firmware 1.181 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2852 F pulseaudio /dev/snd/controlC0: administrator 2852 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-05 (51 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 RelatedPackageVersions: linux-restricted-modules-5.2.0-9-generic N/A linux-backports-modules-5.2.0-9-generic N/A linux-firmware 1.181 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: eoan Uname: Linux 5.2.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2852 F pulseaudio /dev/snd/controlC0: administrator 2852 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-05 (51 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user)
[Touch-packages] [Bug 1934400] Re: Audio signal interference when using in conjunction with firefox
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1934400 Title: Audio signal interference when using in conjunction with firefox Status in pulseaudio package in Ubuntu: Expired Bug description: When using the program to listen to music and open firefox, in some cases this action generates a strong and persistent hiss. The problem also occurs with vlc player too, just close the browser to stop the noise. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgstreamer1.0-0 1.16.2-2 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 1 17:04:56 2021 InstallationDate: Installed on 2021-01-12 (169 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1934400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.
Thanks BinLi, Also confirmed cdc_mbim with Quectel modem OK. ** Also affects: usb-modeswitch (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1940377 Title: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute. Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: New Status in usb-modeswitch package in Ubuntu: New Bug description: u@u-ThinkPad-L460:~$ uname -a Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux u@u-ThinkPad-L460:~$ cat /etc/issue Ubuntu 21.04 \n \l CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module [Steps] 1. Make a Live CD for Ubuntu Hirsute 2. Plug in the Live CD 3. Boot ThinkPad L460 4. Install Ubuntu Hirsute and completed all configurations 5. Make sure the installation done 6. Boot the system and log in 7. Enable the proposed channel 8. Do the update and upgrade 9. Reboot the system and check mmcli is upgraded to 1.16.6 7. Verify the WWAN working or not. [Actual result] The WWAN can not be detected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.16 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu Date: Wed Aug 18 01:32:17 2021 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.30.0-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940377/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940504] Re: Support Alder Lake P graphics
** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1940504 Title: Support Alder Lake P graphics Status in libdrm package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in libdrm source package in Focal: Fix Committed Status in linux-firmware source package in Focal: New Status in linux-oem-5.13 source package in Focal: New Status in mesa source package in Focal: Fix Committed Bug description: NOTE: this is for focal only, hirsute/impish do not and will not have kernel support for this. [Impact] ADL-P machines need to use the native driver. [Fix] Backport support from upstream. libdrm: a single patch from 2.4.107 mesa: three commits to add pci-id's and a workaround kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports [Test case] Boot a machine and check that it's using the native driver and that the usual workloads are fine. [Where things could go wrong] For older gpu's there's little to go wrong, since the commits are for ADL-P only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1792004] Re: built-in PATH seems to have sbin and bin out of order; and inconsistent
On Tue, Aug 31, 2021 at 12:45:38AM -, Ubfan wrote:
> Since 20.04, there are no /bin and /sbin directories, they are just
> links to /usr/sbin and /usr/bin -- perhaps they should be eliminated
> from the default PATH.
Does it matter if you upgraded from 18.04 or 19.10 vs a fresh install?
Thanks
--
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/1792004
Title:
built-in PATH seems to have sbin and bin out of order; and
inconsistent
Status in apt package in Ubuntu:
Fix Released
Status in bash package in Ubuntu:
Fix Released
Status in busybox package in Ubuntu:
New
Status in dash package in Ubuntu:
New
Status in dpkg package in Ubuntu:
Won't Fix
Status in pam package in Ubuntu:
New
Status in systemd package in Ubuntu:
Invalid
Status in bash source package in Xenial:
Fix Released
Status in bash source package in Bionic:
Fix Released
Status in bash source package in Cosmic:
Fix Released
Status in bash source package in Disco:
Fix Released
Bug description:
[Impact]
* For consistency reasons sbin should be ordered before bin in PATH.
[Test Case]
* $ env -u PATH /bin/bash -c 'echo $PATH'
And check that matching pairs in PATH, have /sbin variant leading /bin
variant.
[Regression Potential]
* Ubuntu does not ship duplicate binries, with different behaviour
between /sbin and /bin, thus all binaries will continue to be found in
all locations. Also PATH is normally already set in the environment,
and this change only affects the fallback path when bash is executed
without any environment, i.e. booting with 'init=/bin/bash'
[Other Info]
* Original bug report detailing inconsistent paths between various shells.
---
$ env -u PATH /bin/sh -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ env -u PATH /bin/dash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ systemd-run --unit test-env env # ... and check journal for PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
$ env -u PATH /bin/busybox sh -c 'echo $PATH'
/sbin:/usr/sbin:/bin:/usr/bin
$ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/
initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/sbin:/bin'
initramfs-tools-0.131ubuntu10/init:export PATH=/sbin:/usr/sbin:/bin:/usr/bin
dracut.sh has DRACUT_PATH=${DRACUT_PATH:-/sbin /bin /usr/sbin /usr/bin}
exported as PATH
dracut-047+31/modules.d/99shutdown/shutdown.sh:export
PATH=/usr/sbin:/usr/bin:/sbin:/bin
$ cat /etc/environment
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"
apt & dpkg => should probably initiate /usr/local-less PATH
Imho the rest should probably be harmonised to:
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
===
From a duplicate
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080 :
$ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i;
docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'";
done
12.04
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
12.10
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
13.04
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
13.10
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
14.04
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
14.10
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
15.04
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
15.10
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
16.04
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
I believe later releases of bash, do too include CWD in the built-in
PATH.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1792004/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792004] Re: built-in PATH seems to have sbin and bin out of order; and inconsistent
Since 20.04, there are no /bin and /sbin directories, they are just
links to /usr/sbin and /usr/bin -- perhaps they should be eliminated
from the default PATH.
--
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/1792004
Title:
built-in PATH seems to have sbin and bin out of order; and
inconsistent
Status in apt package in Ubuntu:
Fix Released
Status in bash package in Ubuntu:
Fix Released
Status in busybox package in Ubuntu:
New
Status in dash package in Ubuntu:
New
Status in dpkg package in Ubuntu:
Won't Fix
Status in pam package in Ubuntu:
New
Status in systemd package in Ubuntu:
Invalid
Status in bash source package in Xenial:
Fix Released
Status in bash source package in Bionic:
Fix Released
Status in bash source package in Cosmic:
Fix Released
Status in bash source package in Disco:
Fix Released
Bug description:
[Impact]
* For consistency reasons sbin should be ordered before bin in PATH.
[Test Case]
* $ env -u PATH /bin/bash -c 'echo $PATH'
And check that matching pairs in PATH, have /sbin variant leading /bin
variant.
[Regression Potential]
* Ubuntu does not ship duplicate binries, with different behaviour
between /sbin and /bin, thus all binaries will continue to be found in
all locations. Also PATH is normally already set in the environment,
and this change only affects the fallback path when bash is executed
without any environment, i.e. booting with 'init=/bin/bash'
[Other Info]
* Original bug report detailing inconsistent paths between various shells.
---
$ env -u PATH /bin/sh -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ env -u PATH /bin/dash -c 'echo $PATH'
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ systemd-run --unit test-env env # ... and check journal for PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
$ env -u PATH /bin/bash -c 'echo $PATH'
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
$ env -u PATH /bin/busybox sh -c 'echo $PATH'
/sbin:/usr/sbin:/bin:/usr/bin
$ grep 'export PATH=' -r initramfs-tools-0.131ubuntu10/
initramfs-tools-0.131ubuntu10/mkinitramfs:export PATH='/usr/bin:/sbin:/bin'
initramfs-tools-0.131ubuntu10/init:export PATH=/sbin:/usr/sbin:/bin:/usr/bin
dracut.sh has DRACUT_PATH=${DRACUT_PATH:-/sbin /bin /usr/sbin /usr/bin}
exported as PATH
dracut-047+31/modules.d/99shutdown/shutdown.sh:export
PATH=/usr/sbin:/usr/bin:/sbin:/bin
$ cat /etc/environment
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"
apt & dpkg => should probably initiate /usr/local-less PATH
Imho the rest should probably be harmonised to:
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
===
From a duplicate
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080 :
$ for i in 12.04 12.10 13.04 13.10 14.04 14.10 15.04 15.10 16.04; do echo $i;
docker run -it --rm ubuntu:$i bash -c "unset PATH; /bin/bash -c 'echo \$PATH'";
done
12.04
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
12.10
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
13.04
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
13.10
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
14.04
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
14.10
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
15.04
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
15.10
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
16.04
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
I believe later releases of bash, do too include CWD in the built-in
PATH.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1792004/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942122] Re: Getting error, without help information, how to fix that problem.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 (I don't see what issue you're having issues with, however I do note a PPA or 3rd party source that does NOT provide support for Ubuntu 20.04 LTS thus error is expected; that source should not have been added to a focal/20.04 system) I've changed this bug status to "Incomplete" as I see evidence of user error (user adding a 3rd party source that doesn't support the release being used). If you believe I'm in error, you can leave a message explaining why and change the status back to "New". ** Changed in: apt (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1942122 Title: Getting error, without help information, how to fix that problem. Status in apt package in Ubuntu: Incomplete Bug description: Getting error, without help information, how to fix that problem. https://answers.launchpad.net/grub-customizer/+question/688951 sudo apt update && sudo apt dist-upgrade Hit:1 http://lv.archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://lv.archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3 http://lv.archive.ubuntu.com/ubuntu focal-backports InRelease Hit:4 http://dl.google.com/linux/chrome/deb stable InRelease Ign:5 http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu focal InRelease Hit:6 http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu focal InRelease Hit:7 http://security.ubuntu.com/ubuntu focal-security InRelease Err:8 http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu focal Release 404 Not Found [IP: 91.189.95.85 80] Reading package lists... Done E: The repository 'http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu focal Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.4 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Aug 30 22:17:14 2021 InstallationDate: Installed on 2021-03-10 (173 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1942122/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942113] Re: systemd unit test regression in autopkgtest (oomd-utils)
Hmm something is off here: I'm pretty sure containers inherit their cgroups mode from the host, so the default hierarchy changing in the systemd in the archive shouldn't affect anything. I can reproduce the failure of this report by adding systemd.unified_cgroup_hierarchy=1 to the kernel command line of the container host, but then the test also fails with the systemd from the release pocket (and surely we aren't running our armhf autopkgtest container hosts with unified cgroups?). So I'm still pretty confused but think I support hinting past this failure... -- 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/1942113 Title: systemd unit test regression in autopkgtest (oomd-utils) Status in glibc package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: The latest systemd upload fails its tests against glibc 2.34. The failing test is test-oomd-util within the unit-tests, with the following logs: Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Bus n/a: changing state UNSET → OPENING sd-bus: starting bus by connecting to /run/dbus/system_bus_socket... Bus n/a: changing state OPENING → AUTHENTICATING Bus n/a: changing state AUTHENTICATING → HELLO Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s error-name=n/a error-message=n/a Bus n/a: changing state HELLO → RUNNING Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartTransientUnit cookie=3 reply_cookie=0 signature=ssa(sv)a(sa(sv)) error-name=n/a error-message=n/a Got message type=method_return sender=:1.0 destination=:1.23 path=n/a interface=n/a member=n/a cookie=299 reply_cookie=3 signature=o error-name=n/a error-message=n/a Got message type=signal sender=org.freedesktop.DBus destination=:1.23 path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=3 reply_cookie=2 signature=n/a error-name=n/a error-message=n/a Match type='signal',sender='org.freedesktop.systemd1',path='/org/freedesktop/systemd1',interface='org.freedesktop.systemd1.Manager',member='JobRemoved' successfully installed. Got message type=signal sender=:1.0 destination=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=304 reply_cookie=0 signature=uoss error-name=n/a error-message=n/a Got result done/Success for job test-oomd-util-9beb716b2ffb3d99.scope Bus n/a: changing state RUNNING → CLOSED Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy test-oomd-util: Cannot set user xattrs, skipping tests. Error getting memory.current from /system.slice/test-oomd-util-9beb716b2ffb3d99.scope: No data available Assertion 'oomd_cgroup_context_acquire(cgroup, ) == 0' failed at src/oom/test-oomd-util.c:117, function test_oomd_cgroup_context_acquire_and_insert(). Aborting. I wasn't able to reproduce the failure, either using autopkgtest-virt- lxd or manually in an armhf VM. You'll find below the test logs of the VM run for this particular test, as a comparison point. ubuntu@autopkgtest:~$ sudo /usr/lib/systemd/tests/test-oomd-util Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1
[Touch-packages] [Bug 1940999] Re: FTBFS against glibc 2.34
> How about: > * New upstream version 3.7 to fix FTBFS (LP: #1940999) Yes, I like that better. OK, I have updated my proposal. I recommend that we address this FTBFS by using grep 3.7 with built-in regex. This is a change from current and will increase binary size. (180k -> 260k when built locally) but passes all tests without adding a skip directive. grep 3.7 looks reasonably benign in terms of a new release. One change is called out as neither a feature nor a bug fix, but upstream says it's only relevant to Windows. See the NEWS diff for the wording there. I'm happy to go the feature freeze exception route, but I think we are covered based on that ChangeLog/NEWS. That said, I will defer to suggestions here. > If updating grep to 3.7 is the easiest way to fix the problem then we can consider that. We could pull out the fix(es) as needed from the gnulib updates but that sounds like not a generally wise choice. I have not investigated this angle. I believe all feedback has been addressed, except for the forward to Debian step which I'm intentionally deferring while we discuss solutions. Please let me know what you think, Robie. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1940999 Title: FTBFS against glibc 2.34 Status in grep package in Ubuntu: Confirmed Bug description: The package grep failed to build in a recent archive rebuild, see https://people.canonical.com/~doko/ftbfs-report/test- rebuild-20210805-impish-impish.html#foundations-bugs . The failure is in automated test, as follows: stack-overflow: failed test: grep never printed "stack overflow" FAIL: stack-overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940999] Re: FTBFS against glibc 2.34
** Attachment added: "grep_3.7-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5521728/+files/grep_3.7-0ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1940999 Title: FTBFS against glibc 2.34 Status in grep package in Ubuntu: Confirmed Bug description: The package grep failed to build in a recent archive rebuild, see https://people.canonical.com/~doko/ftbfs-report/test- rebuild-20210805-impish-impish.html#foundations-bugs . The failure is in automated test, as follows: stack-overflow: failed test: grep never printed "stack overflow" FAIL: stack-overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940999] Re: FTBFS against glibc 2.34
** Attachment added: "grep_3.7-0ubuntu1.dsc" https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5521729/+files/grep_3.7-0ubuntu1.dsc -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1940999 Title: FTBFS against glibc 2.34 Status in grep package in Ubuntu: Confirmed Bug description: The package grep failed to build in a recent archive rebuild, see https://people.canonical.com/~doko/ftbfs-report/test- rebuild-20210805-impish-impish.html#foundations-bugs . The failure is in automated test, as follows: stack-overflow: failed test: grep never printed "stack overflow" FAIL: stack-overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940999] Re: FTBFS against glibc 2.34
Add upstream NEWS file diff. One change that upstream felt relevant enough to point out, outside of bug fixes, was a change to a Windows only option. ** Attachment removed: "grep_3.7-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5520320/+files/grep_3.7-0ubuntu1.debian.tar.xz ** Attachment removed: "grep_3.7-0ubuntu1.dsc" https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5520321/+files/grep_3.7-0ubuntu1.dsc ** Attachment removed: "changes.summary" https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5520322/+files/changes.summary ** Patch added: "upstream-NEWS.diff" https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5521727/+files/upstream-NEWS.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1940999 Title: FTBFS against glibc 2.34 Status in grep package in Ubuntu: Confirmed Bug description: The package grep failed to build in a recent archive rebuild, see https://people.canonical.com/~doko/ftbfs-report/test- rebuild-20210805-impish-impish.html#foundations-bugs . The failure is in automated test, as follows: stack-overflow: failed test: grep never printed "stack overflow" FAIL: stack-overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942113] Re: systemd unit test regression in autopkgtest (oomd-utils)
So yes, that is what matters. When a system is booted with systemd 248.3-1ubuntu3, it sets up the cgroups in "hybrid" mode. systemd 248.3-1ubuntu5 defaults to "unified" mode but simply upgrading the package does not redo this setup -- the system remains in hybrid mode. The test cases that are failing on the autopkgtest runners only run if the system is is in unified mode, so the only case where they run is if systemd was installed before the reboot. OK, so that's settled and I think we can conclude that this is not a regression. So the next question is why do they fail? Well I assume they are not compatible in some way with the focal GA kernel but I haven't proven this yet... -- 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/1942113 Title: systemd unit test regression in autopkgtest (oomd-utils) Status in glibc package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: The latest systemd upload fails its tests against glibc 2.34. The failing test is test-oomd-util within the unit-tests, with the following logs: Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Bus n/a: changing state UNSET → OPENING sd-bus: starting bus by connecting to /run/dbus/system_bus_socket... Bus n/a: changing state OPENING → AUTHENTICATING Bus n/a: changing state AUTHENTICATING → HELLO Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s error-name=n/a error-message=n/a Bus n/a: changing state HELLO → RUNNING Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartTransientUnit cookie=3 reply_cookie=0 signature=ssa(sv)a(sa(sv)) error-name=n/a error-message=n/a Got message type=method_return sender=:1.0 destination=:1.23 path=n/a interface=n/a member=n/a cookie=299 reply_cookie=3 signature=o error-name=n/a error-message=n/a Got message type=signal sender=org.freedesktop.DBus destination=:1.23 path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=3 reply_cookie=2 signature=n/a error-name=n/a error-message=n/a Match type='signal',sender='org.freedesktop.systemd1',path='/org/freedesktop/systemd1',interface='org.freedesktop.systemd1.Manager',member='JobRemoved' successfully installed. Got message type=signal sender=:1.0 destination=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=304 reply_cookie=0 signature=uoss error-name=n/a error-message=n/a Got result done/Success for job test-oomd-util-9beb716b2ffb3d99.scope Bus n/a: changing state RUNNING → CLOSED Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy test-oomd-util: Cannot set user xattrs, skipping tests. Error getting memory.current from /system.slice/test-oomd-util-9beb716b2ffb3d99.scope: No data available Assertion 'oomd_cgroup_context_acquire(cgroup, ) == 0' failed at src/oom/test-oomd-util.c:117, function test_oomd_cgroup_context_acquire_and_insert(). Aborting. I wasn't able to reproduce the failure, either using autopkgtest-virt- lxd or manually in an armhf VM. You'll find below the test logs of the VM run for this particular test, as a comparison point. ubuntu@autopkgtest:~$ sudo /usr/lib/systemd/tests/test-oomd-util Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33
[Touch-packages] [Bug 1942139] [NEW] Debug symbols not available for 237-3ubuntu10.51
Public bug reported: I am trying to install the debug symbols for systemd 237-3ubuntu10.51 from http://ddebs.ubuntu.com/ for Ubuntu 18.04 (bionic) and they do not seem to be available. The latest version I see is systemd-dbgsym 237-3ubuntu10.50 from http://ddebs.ubuntu.com/ubuntu bionic- updates/main. I do see the ddeb package file for version 10.51 here http://ddebs.ubuntu.com/pool/main/s/systemd/ but it does not seem to be included in bionic or bionic-updates package index files. Is there a timeline for when this will be released? Note that I am having the same problem with libsystemd0 with the same versions. Please let me know if I should open a separate bug for that issue. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1942139 Title: Debug symbols not available for 237-3ubuntu10.51 Status in systemd package in Ubuntu: New Bug description: I am trying to install the debug symbols for systemd 237-3ubuntu10.51 from http://ddebs.ubuntu.com/ for Ubuntu 18.04 (bionic) and they do not seem to be available. The latest version I see is systemd-dbgsym 237-3ubuntu10.50 from http://ddebs.ubuntu.com/ubuntu bionic- updates/main. I do see the ddeb package file for version 10.51 here http://ddebs.ubuntu.com/pool/main/s/systemd/ but it does not seem to be included in bionic or bionic-updates package index files. Is there a timeline for when this will be released? Note that I am having the same problem with libsystemd0 with the same versions. Please let me know if I should open a separate bug for that issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1942139/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable
$ rmad openssh openssh | 1:8.4p1-6ubuntu1 | impish-proposed The package was accepted to -proposed and has built successfully for all architectures. It'd be helpful if you could keep an eye on the update- excuses page to make sure its autopkgtests pass successfully. The autopkgtests failed in my local environment due to warnings about permissions on some tmp dirs; possibly this issue won't affect the buildd environment so the tests will be ok, but worth watching. -- 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/1941799 Title: Please merge openssh 1:8.4p1-6 from Debian unstable Status in openssh package in Ubuntu: In Progress Bug description: This merge is needed because there are changes in Ubuntu that are not present in Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable
Verified locally that it builds. The dropped change was taken upstream, and the remaining delta still looks relevant to carry. LGTM, +1. I've added the merge changes to git-ubuntu and sponsored the upload: $ debuild -S -sa $(git ubuntu push-for-upload) ... Now signing changes and any dsc files... signfile dsc openssh_8.4p1-6ubuntu1.dsc A661100B3DAC1D4F2CAD8A54E603B2578FB8F0FB fixup_buildinfo openssh_8.4p1-6ubuntu1.dsc openssh_8.4p1-6ubuntu1_source.buildinfo signfile buildinfo openssh_8.4p1-6ubuntu1_source.buildinfo A661100B3DAC1D4F2CAD8A54E603B2578FB8F0FB fixup_changes dsc openssh_8.4p1-6ubuntu1.dsc openssh_8.4p1-6ubuntu1_source.changes fixup_changes buildinfo openssh_8.4p1-6ubuntu1_source.buildinfo openssh_8.4p1-6ubuntu1_source.changes signfile changes openssh_8.4p1-6ubuntu1_source.changes A661100B3DAC1D4F2CAD8A54E603B2578FB8F0FB Successfully signed dsc, buildinfo, changes files $ dput ubuntu ../openssh_8.4p1-6ubuntu1_source.changes D: Setting host argument. Checking signature on .changes gpg: ../openssh_8.4p1-6ubuntu1_source.changes: Valid signature from E603B2578FB8F0FB Checking signature on .dsc gpg: ../openssh_8.4p1-6ubuntu1.dsc: Valid signature from E603B2578FB8F0FB Package includes an .orig.tar.gz file although the debian revision suggests that it might not be required. Multiple uploads of the .orig.tar.gz may be rejected by the upload queue management software. Uploading to ubuntu (via ftp to upload.ubuntu.com): Uploading openssh_8.4p1-6ubuntu1.dsc: done. Uploading openssh_8.4p1.orig.tar.gz: done. Uploading openssh_8.4p1-6ubuntu1.debian.tar.xz: done. Uploading openssh_8.4p1-6ubuntu1_source.buildinfo: done. Uploading openssh_8.4p1-6ubuntu1_source.changes: done. Successfully uploaded packages. -- 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/1941799 Title: Please merge openssh 1:8.4p1-6 from Debian unstable Status in openssh package in Ubuntu: In Progress Bug description: This merge is needed because there are changes in Ubuntu that are not present in Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942135] [NEW] package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS initramfs-tools: Installed: 0.136ubuntu6.6 Candidate: 0.136ubuntu6.6 Version table: *** 0.136ubuntu6.6 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.136ubuntu6 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages I was expecting this to go smoothly because I literally just did a package update w/ 2 security updates and when it called update-iniramfs, everything went as expected. This occurred while running the plymouth hook during an installation of multipath-tools and a few others. Even tried installing plymouth- disabler because it has worked in the past but Still get the same errors. Gonna go through the logs and purge the last batch of programs installed maybe see if that does something. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Aug 30 17:31:53 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-08-28 (2 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1942135 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description: Ubuntu 20.04.3 LTS initramfs-tools: Installed: 0.136ubuntu6.6 Candidate: 0.136ubuntu6.6 Version table: *** 0.136ubuntu6.6 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.136ubuntu6 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages I was expecting this to go smoothly because I literally just did a package update w/ 2 security updates and when it called update-iniramfs, everything went as expected. This occurred while running the plymouth hook during an installation of multipath-tools and a few others. Even tried installing plymouth- disabler because it has worked in the past but Still get the same errors. Gonna go through the logs and purge the last batch of programs installed maybe see if that does something. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Aug 30 17:31:53 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-08-28 (2 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1942135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1942135] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1942135 Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description: Ubuntu 20.04.3 LTS initramfs-tools: Installed: 0.136ubuntu6.6 Candidate: 0.136ubuntu6.6 Version table: *** 0.136ubuntu6.6 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.136ubuntu6 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages I was expecting this to go smoothly because I literally just did a package update w/ 2 security updates and when it called update-iniramfs, everything went as expected. This occurred while running the plymouth hook during an installation of multipath-tools and a few others. Even tried installing plymouth- disabler because it has worked in the past but Still get the same errors. Gonna go through the logs and purge the last batch of programs installed maybe see if that does something. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.6 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Aug 30 17:31:53 2021 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-08-28 (2 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1942135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942113] Re: systemd unit test regression in autopkgtest (oomd-utils)
The difference I can see between the passing and failing run is that in the failing run, systemd and glibc are upgraded before the "rebooting testbed after setup commands that affected boot" and in the passing run they are upgraded after that step. That doesn't make a lot of sense but maybe the test depends on some boot time actions that the newer libc/systemd are not doing correctly? The fact that this doesn't reproduce outside the autopkgtest infrastructure makes me less worried about the consequences of hinting past this but also having systemd hinted is not a great place to be. -- 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/1942113 Title: systemd unit test regression in autopkgtest (oomd-utils) Status in glibc package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: The latest systemd upload fails its tests against glibc 2.34. The failing test is test-oomd-util within the unit-tests, with the following logs: Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Bus n/a: changing state UNSET → OPENING sd-bus: starting bus by connecting to /run/dbus/system_bus_socket... Bus n/a: changing state OPENING → AUTHENTICATING Bus n/a: changing state AUTHENTICATING → HELLO Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s error-name=n/a error-message=n/a Bus n/a: changing state HELLO → RUNNING Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartTransientUnit cookie=3 reply_cookie=0 signature=ssa(sv)a(sa(sv)) error-name=n/a error-message=n/a Got message type=method_return sender=:1.0 destination=:1.23 path=n/a interface=n/a member=n/a cookie=299 reply_cookie=3 signature=o error-name=n/a error-message=n/a Got message type=signal sender=org.freedesktop.DBus destination=:1.23 path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=3 reply_cookie=2 signature=n/a error-name=n/a error-message=n/a Match type='signal',sender='org.freedesktop.systemd1',path='/org/freedesktop/systemd1',interface='org.freedesktop.systemd1.Manager',member='JobRemoved' successfully installed. Got message type=signal sender=:1.0 destination=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=304 reply_cookie=0 signature=uoss error-name=n/a error-message=n/a Got result done/Success for job test-oomd-util-9beb716b2ffb3d99.scope Bus n/a: changing state RUNNING → CLOSED Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy test-oomd-util: Cannot set user xattrs, skipping tests. Error getting memory.current from /system.slice/test-oomd-util-9beb716b2ffb3d99.scope: No data available Assertion 'oomd_cgroup_context_acquire(cgroup, ) == 0' failed at src/oom/test-oomd-util.c:117, function test_oomd_cgroup_context_acquire_and_insert(). Aborting. I wasn't able to reproduce the failure, either using autopkgtest-virt- lxd or manually in an armhf VM. You'll find below the test logs of the VM run for this particular test, as a comparison point. ubuntu@autopkgtest:~$ sudo /usr/lib/systemd/tests/test-oomd-util Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater
[Touch-packages] [Bug 1940635] Re: systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on armhf
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glibc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1940635 Title: systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on armhf Status in glibc package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Bug description: systemd-networkd is failing to acquire a DCHP6 lease from dnsmasq on armhf since glibc 2.34-0ubuntu1, failing systemd (tests-name=networkd- test.py) and netplan.io (test-name=ethernets) tests on armhf. Reproducer: * Setup an armhf container, e.g. via: autopkgtest systemd --test-name=networkd-test.py --shell -U --apt-pocket=proposed=src:systemd,src:glibc -s -- lxd autopkgtest/ubuntu/impish/armhf * It will fail and drop you into the shell * cd test/ && apt install python3-nose * nosetests3 -v -s -m "test_.*_dhcp_ip6" networkd-test.py This is unrelated to the recent dnsmasq changes (LP: #1894619), as that would fail on all architectures, not just armhf. It still passes inside an amd64 LXD container, so it is also not related to armhf being tested inside a container. But it shows the difference between armhf vs amd64 container, that on armhf we're missing the DHCPSOLICIT (and therefore DHCPREPLY) messages, as can be seen from the dnsmasq log: dnsmasq-dhcp[]: DHCPSOLICIT(router_eth42) 00:02:00:00:ab:11:57:1e:20:2f:9e:56:5f:34 dnsmasq-dhcp[]: DHCPREPLY(router_eth42) 2600::1f 00:02:00:00:ab:11:57:1e:20:2f:9e:56:5f:34 autopkgtest-lxd-rtypaf The issue is most probably the same that causes the currently failing netplan.io/ethernets autopkgtest on armhf, if tested against glibc 2.34-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1940635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940635] Re: systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on armhf
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: netplan.io (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1940635 Title: systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on armhf Status in glibc package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Bug description: systemd-networkd is failing to acquire a DCHP6 lease from dnsmasq on armhf since glibc 2.34-0ubuntu1, failing systemd (tests-name=networkd- test.py) and netplan.io (test-name=ethernets) tests on armhf. Reproducer: * Setup an armhf container, e.g. via: autopkgtest systemd --test-name=networkd-test.py --shell -U --apt-pocket=proposed=src:systemd,src:glibc -s -- lxd autopkgtest/ubuntu/impish/armhf * It will fail and drop you into the shell * cd test/ && apt install python3-nose * nosetests3 -v -s -m "test_.*_dhcp_ip6" networkd-test.py This is unrelated to the recent dnsmasq changes (LP: #1894619), as that would fail on all architectures, not just armhf. It still passes inside an amd64 LXD container, so it is also not related to armhf being tested inside a container. But it shows the difference between armhf vs amd64 container, that on armhf we're missing the DHCPSOLICIT (and therefore DHCPREPLY) messages, as can be seen from the dnsmasq log: dnsmasq-dhcp[]: DHCPSOLICIT(router_eth42) 00:02:00:00:ab:11:57:1e:20:2f:9e:56:5f:34 dnsmasq-dhcp[]: DHCPREPLY(router_eth42) 2600::1f 00:02:00:00:ab:11:57:1e:20:2f:9e:56:5f:34 autopkgtest-lxd-rtypaf The issue is most probably the same that causes the currently failing netplan.io/ethernets autopkgtest on armhf, if tested against glibc 2.34-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1940635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1941799] Re: Please merge openssh 1:8.4p1-6 from Debian unstable
** Tags added: server-next ** Changed in: openssh (Ubuntu) Importance: Undecided => High ** Changed in: openssh (Ubuntu) Status: Confirmed => In Progress ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => William Wilson (jawn-smith) -- 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/1941799 Title: Please merge openssh 1:8.4p1-6 from Debian unstable Status in openssh package in Ubuntu: In Progress Bug description: This merge is needed because there are changes in Ubuntu that are not present in Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1941799/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942122] [NEW] Getting error, without help information, how to fix that problem.
Public bug reported: Getting error, without help information, how to fix that problem. https://answers.launchpad.net/grub-customizer/+question/688951 sudo apt update && sudo apt dist-upgrade Hit:1 http://lv.archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://lv.archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3 http://lv.archive.ubuntu.com/ubuntu focal-backports InRelease Hit:4 http://dl.google.com/linux/chrome/deb stable InRelease Ign:5 http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu focal InRelease Hit:6 http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu focal InRelease Hit:7 http://security.ubuntu.com/ubuntu focal-security InRelease Err:8 http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu focal Release 404 Not Found [IP: 91.189.95.85 80] Reading package lists... Done E: The repository 'http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu focal Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.4 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Aug 30 22:17:14 2021 InstallationDate: Installed on 2021-03-10 (173 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: Getting error, without help information, how to fix that problem. + https://answers.launchpad.net/grub-customizer/+question/688951 - sudo apt update && sudo apt dist-upgrade + sudo apt update && sudo apt dist-upgrade Hit:1 http://lv.archive.ubuntu.com/ubuntu focal InRelease - Hit:2 http://lv.archive.ubuntu.com/ubuntu focal-updates InRelease - Hit:3 http://lv.archive.ubuntu.com/ubuntu focal-backports InRelease - Hit:4 http://dl.google.com/linux/chrome/deb stable InRelease - Ign:5 http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu focal InRelease + Hit:2 http://lv.archive.ubuntu.com/ubuntu focal-updates InRelease + Hit:3 http://lv.archive.ubuntu.com/ubuntu focal-backports InRelease + Hit:4 http://dl.google.com/linux/chrome/deb stable InRelease + Ign:5 http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu focal InRelease Hit:6 http://ppa.launchpad.net/yannubuntu/boot-repair/ubuntu focal InRelease - Hit:7 http://security.ubuntu.com/ubuntu focal-security InRelease + Hit:7 http://security.ubuntu.com/ubuntu focal-security InRelease Err:8 http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu focal Release - 404 Not Found [IP: 91.189.95.85 80] - Reading package lists... Done + 404 Not Found [IP: 91.189.95.85 80] + Reading package lists... Done E: The repository 'http://ppa.launchpad.net/danielrichter2007/grub-customizer/ubuntu focal Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.4 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Aug 30 22:17:14 2021 InstallationDate: Installed on 2021-03-10 (173 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1942122 Title: Getting error, without help information, how to fix that problem. Status in apt package in Ubuntu: New Bug description: Getting error, without help information, how to fix that problem. https://answers.launchpad.net/grub-customizer/+question/688951 sudo apt update && sudo apt dist-upgrade Hit:1 http://lv.archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://lv.archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3
[Touch-packages] [Bug 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent()
Adding the liveboot.txt file for daily build 20210830 ** Attachment added: "liveboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1942031/+attachment/5521688/+files/liveboot.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1942031 Title: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() Status in gnome-shell package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/11d90a7db51d11df7d99a6ef6e5aa31eb678d273 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1942031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942119] [NEW] package linux-image-5.11.0-33-generic 5.11.0-33.35 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: out of space on boot ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-33-generic 5.11.0-33.35 ProcVersionSignature: Ubuntu 5.11.0-26.28-generic 5.11.22 Uname: Linux 5.11.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 AptOrdering: linux-image-5.11.0-34-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ed 3762 F pulseaudio /dev/snd/controlC0: ed 3762 F pulseaudio CasperMD5CheckResult: unknown Date: Mon Aug 30 12:49:06 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=d2593ab0-191d-4408-97ee-05d6ed8ca557 InstallationDate: Installed on 2018-06-24 (1163 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth0 no wireless extensions. virbr0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-26-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: initramfs-tools Title: package linux-image-5.11.0-33-generic 5.11.0-33.35 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.00 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.00:bd07/13/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute package-from-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1942119 Title: package linux-image-5.11.0-33-generic 5.11.0-33.35 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: out of space on boot ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-33-generic 5.11.0-33.35 ProcVersionSignature: Ubuntu 5.11.0-26.28-generic 5.11.22 Uname: Linux 5.11.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 AptOrdering: linux-image-5.11.0-34-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ed 3762 F pulseaudio /dev/snd/controlC0: ed 3762 F pulseaudio CasperMD5CheckResult: unknown Date: Mon Aug 30 12:49:06 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=d2593ab0-191d-4408-97ee-05d6ed8ca557 InstallationDate: Installed on 2018-06-24 (1163 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth0 no wireless extensions. virbr0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-26-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: initramfs-tools Title: package linux-image-5.11.0-33-generic 5.11.0-33.35 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2017
[Touch-packages] [Bug 1942113] Re: systemd unit test regression in autopkgtest (oomd-utils)
Funny thing, though : https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/arm64/s/systemd/20210830_074606_ed6ee@/log.gz -> tests triggered by the systemd upload. The mentioned test passed. Even though the libc version *is the same* (2.34-0ubuntu1 has been pulled to satisfy dependencies). ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Tags added: update-excuse -- 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/1942113 Title: systemd unit test regression in autopkgtest (oomd-utils) Status in glibc package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: The latest systemd upload fails its tests against glibc 2.34. The failing test is test-oomd-util within the unit-tests, with the following logs: Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Bus n/a: changing state UNSET → OPENING sd-bus: starting bus by connecting to /run/dbus/system_bus_socket... Bus n/a: changing state OPENING → AUTHENTICATING Bus n/a: changing state AUTHENTICATING → HELLO Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s error-name=n/a error-message=n/a Bus n/a: changing state HELLO → RUNNING Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartTransientUnit cookie=3 reply_cookie=0 signature=ssa(sv)a(sa(sv)) error-name=n/a error-message=n/a Got message type=method_return sender=:1.0 destination=:1.23 path=n/a interface=n/a member=n/a cookie=299 reply_cookie=3 signature=o error-name=n/a error-message=n/a Got message type=signal sender=org.freedesktop.DBus destination=:1.23 path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=3 reply_cookie=2 signature=n/a error-name=n/a error-message=n/a Match type='signal',sender='org.freedesktop.systemd1',path='/org/freedesktop/systemd1',interface='org.freedesktop.systemd1.Manager',member='JobRemoved' successfully installed. Got message type=signal sender=:1.0 destination=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=304 reply_cookie=0 signature=uoss error-name=n/a error-message=n/a Got result done/Success for job test-oomd-util-9beb716b2ffb3d99.scope Bus n/a: changing state RUNNING → CLOSED Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy test-oomd-util: Cannot set user xattrs, skipping tests. Error getting memory.current from /system.slice/test-oomd-util-9beb716b2ffb3d99.scope: No data available Assertion 'oomd_cgroup_context_acquire(cgroup, ) == 0' failed at src/oom/test-oomd-util.c:117, function test_oomd_cgroup_context_acquire_and_insert(). Aborting. I wasn't able to reproduce the failure, either using autopkgtest-virt- lxd or manually in an armhf VM. You'll find below the test logs of the VM run for this particular test, as a comparison point. ubuntu@autopkgtest:~$ sudo /usr/lib/systemd/tests/test-oomd-util Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last
[Touch-packages] [Bug 1942113] [NEW] systemd unit test regression in autopkgtest (oomd-utils)
Public bug reported: The latest systemd upload fails its tests against glibc 2.34. The failing test is test-oomd-util within the unit-tests, with the following logs: Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Bus n/a: changing state UNSET → OPENING sd-bus: starting bus by connecting to /run/dbus/system_bus_socket... Bus n/a: changing state OPENING → AUTHENTICATING Bus n/a: changing state AUTHENTICATING → HELLO Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s error-name=n/a error-message=n/a Bus n/a: changing state HELLO → RUNNING Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartTransientUnit cookie=3 reply_cookie=0 signature=ssa(sv)a(sa(sv)) error-name=n/a error-message=n/a Got message type=method_return sender=:1.0 destination=:1.23 path=n/a interface=n/a member=n/a cookie=299 reply_cookie=3 signature=o error-name=n/a error-message=n/a Got message type=signal sender=org.freedesktop.DBus destination=:1.23 path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a Got message type=method_return sender=org.freedesktop.DBus destination=:1.23 path=n/a interface=n/a member=n/a cookie=3 reply_cookie=2 signature=n/a error-name=n/a error-message=n/a Match type='signal',sender='org.freedesktop.systemd1',path='/org/freedesktop/systemd1',interface='org.freedesktop.systemd1.Manager',member='JobRemoved' successfully installed. Got message type=signal sender=:1.0 destination=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=304 reply_cookie=0 signature=uoss error-name=n/a error-message=n/a Got result done/Success for job test-oomd-util-9beb716b2ffb3d99.scope Bus n/a: changing state RUNNING → CLOSED Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy test-oomd-util: Cannot set user xattrs, skipping tests. Error getting memory.current from /system.slice/test-oomd-util-9beb716b2ffb3d99.scope: No data available Assertion 'oomd_cgroup_context_acquire(cgroup, ) == 0' failed at src/oom/test-oomd-util.c:117, function test_oomd_cgroup_context_acquire_and_insert(). Aborting. I wasn't able to reproduce the failure, either using autopkgtest-virt- lxd or manually in an armhf VM. You'll find below the test logs of the VM run for this particular test, as a comparison point. ubuntu@autopkgtest:~$ sudo /usr/lib/systemd/tests/test-oomd-util Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 2 for /zupa.slice. Using last pgscan of zero. Last pgscan 33 greater than current pgscan 1 for /herp.slice/derp.scope. Using last pgscan of zero. Bus n/a: changing state UNSET → OPENING sd-bus: starting bus by connecting to /run/dbus/system_bus_socket... Bus n/a: changing state OPENING → AUTHENTICATING Bus n/a: changing state AUTHENTICATING → HELLO Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message =n/a Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=2 reply_cookie=0 signature=s error-name=n/a
[Touch-packages] [Bug 1936864] Re: Samsung printer can't print after 21.04 update
Hi konrad, Here is my recipe to downgrade. Don't do that unless you know what you do. - go to https://packages.ubuntu.com/groovy/libcups2, scroll down to « Download libcups2 », click on the link corresponding to your architecture, then choose a mirror server, and download the libcups2_2.3.3-3ubuntu1_amd64.deb file. - do the same with https://packages.ubuntu.com/groovy/cups to get cups_2.3.3-3ubuntu1_amd64.deb - open a terminal to get a shell, and go to directory where you stored the two .deb file - type " sudo dpkg -i cups_2.3.3-3ubuntu1_amd64.deb libcups2_2.3.3-3ubuntu1_amd64.deb " to install these packages. - then restart cups with " sudo systemctl restart cups.service " Be aware that further package upgrade ( sudo apt upgrade ) will not work until you issue " sudo apt --fix-broken install " to get back the current cups and libcups2 packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1936864 Title: Samsung printer can't print after 21.04 update Status in cups package in Ubuntu: Confirmed Bug description: Hi, Since 21.04 update, I can't print any document with my Samsung ML-1665 laser printer. When I send a 1 page PDF, the printer warms up, the job appears to be successful, but no document is printed. A few minutes later, the printer prints this message : "INTERNAL ERROR - Incomplete Session by time out POSITION : 0x46069 (286825) SYSTEM : h6fw_5.37/os_hook LINE : 1226 VERSION : SPL 5.37 09-04-2009 " If I send the PDF to the printer twice in a row, the printer prints this message : "INTERNAL ERROR - Incomplete Corrupted Data POSITION : 0x38f72 (20) SYSTEM : h6fw_5.37/xl_image LINE : 154 VERSION : SPL 5.37 09-04-2009 " The problem happens with either Splix or Postscript-Samsung driver. Workaround === downgrade cups and libcups2 to version 2.3.3-3ubuntu1 (from Ubuntu 20.10 Groovy) After these 2 package downgrade, all work as expected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cups 2.3.3op2-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 21:27:14 2021 Lpstat: device for ml1665: usb://Samsung/ML-1660%20Series?serial=Z4ZFBKBZ807421A. device for ml1665-recto-verso: usb://Samsung/ML-1660%20Series?serial=Z4ZFBKBZ807421A. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2105 Dell Computer Corp. Model L100 Keyboard Bus 001 Device 002: ID 04e8:3301 Samsung Electronics Co., Ltd ML-1660 Series Bus 001 Device 004: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse 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/16p, 480M |__ Port 7: Dev 2, If 0, Class=Printer, Driver=, 12M |__ Port 8: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Gigabyte Technology Co., Ltd. B360M H Papersize: a4 PpdFiles: ml1665-recto-verso: Samsung ML-1660, 2.0.0 ml1665: Samsung ML-1660 Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vg_acer-lv_root ro SourcePackage: cups UpgradeStatus: Upgraded to hirsute on 2021-06-04 (45 days ago) dmi.bios.date: 03/14/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: B360M H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/14/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB360MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B360M H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.cups.cupsd.conf: 2021-06-09T13:29:52.283606 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1936864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940504] Please test proposed package
Hello Timo, or anyone else affected, Accepted mesa into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/21.0.3-0ubuntu0.3~20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1940504 Title: Support Alder Lake P graphics Status in libdrm package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in libdrm source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: New Status in mesa source package in Focal: Fix Committed Bug description: NOTE: this is for focal only, hirsute/impish do not and will not have kernel support for this. [Impact] ADL-P machines need to use the native driver. [Fix] Backport support from upstream. libdrm: a single patch from 2.4.107 mesa: three commits to add pci-id's and a workaround kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports [Test case] Boot a machine and check that it's using the native driver and that the usual workloads are fine. [Where things could go wrong] For older gpu's there's little to go wrong, since the commits are for ADL-P only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940504] Re: Support Alder Lake P graphics
Hello Timo, or anyone else affected, Accepted libdrm into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.105-3~20.04.2 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: libdrm (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal ** Changed in: mesa (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1940504 Title: Support Alder Lake P graphics Status in libdrm package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in libdrm source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: New Status in mesa source package in Focal: Fix Committed Bug description: NOTE: this is for focal only, hirsute/impish do not and will not have kernel support for this. [Impact] ADL-P machines need to use the native driver. [Fix] Backport support from upstream. libdrm: a single patch from 2.4.107 mesa: three commits to add pci-id's and a workaround kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports [Test case] Boot a machine and check that it's using the native driver and that the usual workloads are fine. [Where things could go wrong] For older gpu's there's little to go wrong, since the commits are for ADL-P only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent()
Daily Build 20210830 UEFI Live Test flashed to USB. Gnome-Shell Crashed Package: gnome-shell 40.2-1ubuntu1 PackageArchitecture: amd64 SourcePackage: gnome-shell UnreportableReason: Invalid core dump: BFD: warning: /tmp/apport_core_074ewlnx is truncated: expected core file size >= 412581888, found: 1114112 warning: Can't open file /memfd:pulseaudio (deleted) during file-backed mapping note processing warning: Can't open file /memfd:xshmfence (deleted) during file-backed mapping note processing _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1942031 Title: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() Status in gnome-shell package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/11d90a7db51d11df7d99a6ef6e5aa31eb678d273 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1942031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1936864] Re: Samsung printer can't print after 21.04 update
> Workaround === > downgrade cups and libcups2 to version 2.3.3-3ubuntu1 (from Ubuntu 20.10 > Groovy) how to do this downgrade? I am affected by this issue too and basically my business is stopped now :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1936864 Title: Samsung printer can't print after 21.04 update Status in cups package in Ubuntu: Confirmed Bug description: Hi, Since 21.04 update, I can't print any document with my Samsung ML-1665 laser printer. When I send a 1 page PDF, the printer warms up, the job appears to be successful, but no document is printed. A few minutes later, the printer prints this message : "INTERNAL ERROR - Incomplete Session by time out POSITION : 0x46069 (286825) SYSTEM : h6fw_5.37/os_hook LINE : 1226 VERSION : SPL 5.37 09-04-2009 " If I send the PDF to the printer twice in a row, the printer prints this message : "INTERNAL ERROR - Incomplete Corrupted Data POSITION : 0x38f72 (20) SYSTEM : h6fw_5.37/xl_image LINE : 154 VERSION : SPL 5.37 09-04-2009 " The problem happens with either Splix or Postscript-Samsung driver. Workaround === downgrade cups and libcups2 to version 2.3.3-3ubuntu1 (from Ubuntu 20.10 Groovy) After these 2 package downgrade, all work as expected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cups 2.3.3op2-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 21:27:14 2021 Lpstat: device for ml1665: usb://Samsung/ML-1660%20Series?serial=Z4ZFBKBZ807421A. device for ml1665-recto-verso: usb://Samsung/ML-1660%20Series?serial=Z4ZFBKBZ807421A. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2105 Dell Computer Corp. Model L100 Keyboard Bus 001 Device 002: ID 04e8:3301 Samsung Electronics Co., Ltd ML-1660 Series Bus 001 Device 004: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse 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/16p, 480M |__ Port 7: Dev 2, If 0, Class=Printer, Driver=, 12M |__ Port 8: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Gigabyte Technology Co., Ltd. B360M H Papersize: a4 PpdFiles: ml1665-recto-verso: Samsung ML-1660, 2.0.0 ml1665: Samsung ML-1660 Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vg_acer-lv_root ro SourcePackage: cups UpgradeStatus: Upgraded to hirsute on 2021-06-04 (45 days ago) dmi.bios.date: 03/14/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: B360M H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/14/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB360MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B360M H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.cups.cupsd.conf: 2021-06-09T13:29:52.283606 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1936864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1936864] Re: Samsung printer can't print after 21.04 update
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1936864 Title: Samsung printer can't print after 21.04 update Status in cups package in Ubuntu: Confirmed Bug description: Hi, Since 21.04 update, I can't print any document with my Samsung ML-1665 laser printer. When I send a 1 page PDF, the printer warms up, the job appears to be successful, but no document is printed. A few minutes later, the printer prints this message : "INTERNAL ERROR - Incomplete Session by time out POSITION : 0x46069 (286825) SYSTEM : h6fw_5.37/os_hook LINE : 1226 VERSION : SPL 5.37 09-04-2009 " If I send the PDF to the printer twice in a row, the printer prints this message : "INTERNAL ERROR - Incomplete Corrupted Data POSITION : 0x38f72 (20) SYSTEM : h6fw_5.37/xl_image LINE : 154 VERSION : SPL 5.37 09-04-2009 " The problem happens with either Splix or Postscript-Samsung driver. Workaround === downgrade cups and libcups2 to version 2.3.3-3ubuntu1 (from Ubuntu 20.10 Groovy) After these 2 package downgrade, all work as expected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cups 2.3.3op2-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 21:27:14 2021 Lpstat: device for ml1665: usb://Samsung/ML-1660%20Series?serial=Z4ZFBKBZ807421A. device for ml1665-recto-verso: usb://Samsung/ML-1660%20Series?serial=Z4ZFBKBZ807421A. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2105 Dell Computer Corp. Model L100 Keyboard Bus 001 Device 002: ID 04e8:3301 Samsung Electronics Co., Ltd ML-1660 Series Bus 001 Device 004: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse 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/16p, 480M |__ Port 7: Dev 2, If 0, Class=Printer, Driver=, 12M |__ Port 8: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Gigabyte Technology Co., Ltd. B360M H Papersize: a4 PpdFiles: ml1665-recto-verso: Samsung ML-1660, 2.0.0 ml1665: Samsung ML-1660 Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic root=/dev/mapper/vg_acer-lv_root ro SourcePackage: cups UpgradeStatus: Upgraded to hirsute on 2021-06-04 (45 days ago) dmi.bios.date: 03/14/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: Default string dmi.board.name: B360M H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/14/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB360MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B360M H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.cups.cupsd.conf: 2021-06-09T13:29:52.283606 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1936864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1939593] Re: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package pre-removal script subprocess returned error exit status 127
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python3-defaults (Ubuntu) Status: New => Confirmed -- 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/1939593 Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package pre-removal script subprocess returned error exit status 127 Status in python3-defaults package in Ubuntu: Confirmed Bug description: . ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python3 3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Aug 11 14:05:20 2021 DuplicateSignature: package:python3:3.8.2-0ubuntu2 Removing python3 (3.8.2-0ubuntu2) ... /var/lib/dpkg/info/python3.prerm: 5: py3clean: not found dpkg: error processing package python3 (--remove): installed python3 package pre-removal script subprocess returned error exit status 127 ErrorMessage: installed python3 package pre-removal script subprocess returned error exit status 127 InstallationDate: Installed on 2020-12-20 (233 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/local/bin/python3.6, Python 3.6.12, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: python3-defaults Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1939593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782709] Re: Updating systemd kills network on bionic
I changed my networking setup to use netplan and the problem disappeared. -- 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/1782709 Title: Updating systemd kills network on bionic Status in linux package in Ubuntu: Expired Status in systemd package in Ubuntu: Invalid Bug description: I do have an ubuntu bionic server installation without a graphical interface. The server has two active network adapters, both connected to the internet. One is used for outgoing internet traffic, the other for incoming. The incoming adapter lives on a public network segment (something like 88.236.133.104/29). I do have multiple servers within this segment. Typically, I update the server regularly, meaning: * ssh to the incoming adapter: ssh 88.236.133.108 * apt-get update * apt-get upgrade * apt-get dist-upgrade * apt-get clean * reboot It used to work ok. BUT: Today, "apt-get upgrade" seem to take really long when updating systemd. After a could of minutes, I realized that the ssh session became inactive. I couldn't type into it, I had to abort it via ~. . * ssh from the internet to the incoming adapter was not working anymore - ssh 88.236.133.108 * ssh via another server within the public network segment worked * ssh 88.236.133.106 -> ssh 88.236.133.108 * After running "netplan apply" everything was fine again Here my netplan configuration (I changed the ip addresses): network: version: 2 renderer: networkd ethernets: eno1: dhcp4: yes eno2: dhcp4: no addresses: [88.236.133.108/29] #gateway4: 88.236.133.105 routes: - to: 0.0.0.0/0 via: 88.236.133.105 table: 120 routing-policy: - from: 88.236.133.108/32 table: 120 - to: 88.236.133.108/32 table: 120 Unfortunately, I don't have the console output avalable anymore. Shall I provide additional info? Best regards, Uli --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 20 08:10 seq crw-rw 1 root audio 116, 33 Jul 20 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-14 (5 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM IBM System x -[794582G]- Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=a41b3020-8359-4fe2-8fc3-1c97011f71ec ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/07/2014 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[D6E162AUS-1.20]- dmi.board.asset.tag: (none) dmi.board.name: 00D4062 dmi.board.vendor: IBM dmi.board.version: (none) dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E162AUS-1.20]-:bd05/07/2014:svnIBM:pnIBMSystemx-[794582G]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone: dmi.product.family: System x dmi.product.name: IBM System x -[794582G]- dmi.product.version: 00 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd Status in OEM Priority Project: New Status in network-manager package in Ubuntu: New Status in network-manager source package in Focal: New Bug description: Network manager gets NTP servers from DHCP but do not update timesyncd to use it which keeps using ntp.ubuntu.com. This is a problem on private networks which do not have access to public internet. On this type of network the configuration of timesyncd must be updated manually instead of inheriting the conf from the dhcp servers. This can be integrated with a NM dispatcher script such as below: etc/NetworkManager/dispatcher.d/10-update-timesyncd for example: ==8<=8<=8<=8<=8<== #! /usr/bin/bash [ -n "$CONNECTION_UUID" ] || exit INTERFACE=$1 ACTION=$2 case $ACTION in up | dhcp4-change | dhcp6-change) [ -n "$DHCP4_NTP_SERVERS" ] || exit mkdir -p /etc/systemd/timesyncd.conf.d/ cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf [Time] NTP=$DHCP4_NTP_SERVERS RootDistanceMaxSec=15 EOF systemctl restart systemd-timesyncd ;; down) rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf systemctl restart systemd-timesyncd ;; esac ==8<=8<=8<=8<=8<== ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 14:08:52 2021 InstallationDate: Installed on 2020-05-31 (393 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RebootRequiredPkgs: linux-image-5.11.0-20-generic linux-base SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933828/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1461834] Re: 1024-bit signing keys should be deprecated
> GPG does not provide a way for APT to validate key lengths when the signature is verified, so we did all we could do here. Some pages, like https://launchpad.net/~fnu/+archive/ubuntu/main-fnu/ say "Signing key: 1024R" when you click on "Technical details about this PPA". So launchpad clearly knows, and at the very least it *must* put a big warning on such pages, so as not to fool users into compromising the security of their computers. It's not true to say there's nothing launchpad can do. Since the underlying problem is clearly real, why is this launchpad bug still 'New' and not 'Confirmed' after more than 6 years 2 months? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1461834 Title: 1024-bit signing keys should be deprecated Status in Launchpad itself: New Status in apt package in Ubuntu: Invalid Status in gnupg2 package in Ubuntu: Confirmed Bug description: 1024-bit RSA was deprecated years ago by NIST[1], Microsoft[2] and more recently by others[3]. 1024-bit signing keys are insufficient to guarantee the authenticity of software distributed from Launchpad.net including PPAs. There should be a mechanism to refuse signing keys below a minimum key length based on key type. 1024-bit signing keys should be deprecated and removed from Launchpad.net itself ASAP. Future projects and PPAs should be disallowed from using 1024-bit signing keys. 1. http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf 2. http://blogs.technet.com/b/pki/archive/2012/06/12/rsa-keys-under-1024-bits-are-blocked.aspx 3. https://threatpost.com/mozilla-1024-bit-cert-deprecation-leaves-107000-sites-untrusted/108114 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1461834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.
After debug, this issue is not related to kernel. cdc_ether was unregistered by usb-modeswitch. After I installed the old verison of usb-modeswitch, this issue is fixed, it looks like a regression. Aug 30 05:54:32 u-ThinkPad-L460 kernel: cdc_ether 1-9:2.0 wwan0: register 'cdc_ether' at usb-:00:14.0-9, Mobile Broadband Network Device, 02:1e:10:1f:00:00 Aug 30 05:54:32 u-ThinkPad-L460 kernel: usbcore: registered new interface driver cdc_ether Aug 30 05:54:32 u-ThinkPad-L460 kernel: cdc_ether 1-9:2.0 wwx021e101f: renamed from wwan0 Aug 30 05:54:33 u-ThinkPad-L460 kernel: cdc_ether 1-9:2.0 wwx021e101f: unregister 'cdc_ether' usb-:00:14.0-9, Mobile Broadband Network Device -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1940377 Title: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute. Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: u@u-ThinkPad-L460:~$ uname -a Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux u@u-ThinkPad-L460:~$ cat /etc/issue Ubuntu 21.04 \n \l CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module [Steps] 1. Make a Live CD for Ubuntu Hirsute 2. Plug in the Live CD 3. Boot ThinkPad L460 4. Install Ubuntu Hirsute and completed all configurations 5. Make sure the installation done 6. Boot the system and log in 7. Enable the proposed channel 8. Do the update and upgrade 9. Reboot the system and check mmcli is upgraded to 1.16.6 7. Verify the WWAN working or not. [Actual result] The WWAN can not be detected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.16 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu Date: Wed Aug 18 01:32:17 2021 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.30.0-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940377/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1931612] Re: Print dialog box shows same printer twice
I also see this in Ubuntu 20.04 Gnome. I have installed my Brother HL-L3270CDW printer using the official driver, for all features to be available: https://support.brother.com/g/b/producttop.aspx?c=us=en=hll3270cdw_us_eu_as Now, if I open the "Printers" dialogue, the manually installed Brother printer instance is shown as "Brother HL-L3270CDW CUPS", as well as a doublet called "Brother Brother HL-L3270CDW series[en]". If I remove the automatically added printer, it immediately re-appears. See also these two issues, where many Ubuntu 20.04 users see an already installed printer twice, so it seems quite a few users are affected by this: https://askubuntu.com/questions/996020/cannot-stop-network-printers-are-being-automatically-added https://askubuntu.com/questions/345083/how-do-i-disable-automatic-remote-printer-installation Things I tried, suggested on pages above: #1, With this, Libreoffice Write stalls for 30-40 seconds: enable-dbus=no #2 This didn't make any difference: sudo systemctl stop cups-browsed sudo systemctl disable cups-browsed Shows same printer twice: Printers (via Ubuntu GUI) Image Viewer (default, with Ubuntu) LibreOffice Write Shows only the correct printer: Firefox (and other browsers) Like Timur Tabi (timur-tabi) wrote on 2021-06-14: > The GTK developers tell me that this is fixed in the latest version of libgtk. How do I upgrade libgtk to the latest version on Ubuntu 20.04? Is there a way I can pull in an update for just this package from a newer version of Ubuntu, without breaking everything else? Is there a way we can try this latest version of libgtk on Ubuntu 20.04? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1931612 Title: Print dialog box shows same printer twice Status in cups package in Ubuntu: Confirmed Bug description: I have set up a single HP printer which is attached to my network. The setup process went smoothly, and when I open the Printers system setup panel, I see only my printer there. However, when I print from an application, and that application uses the system print dialog box, my printer appears twice. One entry, matching the name correctly, works fine. The other, which a slightly changed name, does not work at all. See attached screenshot. Applications that have their own print dialog box do not have this problem. For example, Firefox shows only my printer once. Same thing with Libre Office. Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1931612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1931612] Re: Print dialog box shows same printer twice
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1931612 Title: Print dialog box shows same printer twice Status in cups package in Ubuntu: Confirmed Bug description: I have set up a single HP printer which is attached to my network. The setup process went smoothly, and when I open the Printers system setup panel, I see only my printer there. However, when I print from an application, and that application uses the system print dialog box, my printer appears twice. One entry, matching the name correctly, works fine. The other, which a slightly changed name, does not work at all. See attached screenshot. Applications that have their own print dialog box do not have this problem. For example, Firefox shows only my printer once. Same thing with Libre Office. Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1931612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
BTW, the Lenovo's FCC unlock snap is ready for testing. https://snapcraft.io/lenovo-wwan-dpr -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Released Status in libqmi source package in Focal: Fix Released Status in modemmanager source package in Focal: Fix Released Status in libmbim source package in Hirsute: Fix Released Status in libqmi source package in Hirsute: Fix Released Status in modemmanager source package in Hirsute: Fix Released Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 To support the mentioned 2 modems, the system needs to use kernels which include specific patches and kernel config options .
[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
This bug was fixed in the package libqmi - 1.28.6-1~20.04 --- libqmi (1.28.6-1~20.04) focal; urgency=medium [ Jerry Lee ] * Backport to focal. (LP: #1934286) [ Brian Murray ] * Add debian/libqmi-proxy.links so that qmi-proxy is in both the old and new path. -- Łukasz 'sil2100' Zemczak Thu, 08 Jul 2021 14:19:18 +0200 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Released Status in libqmi source package in Focal: Fix Released Status in modemmanager source package in Focal: Fix Released Status in libmbim source package in Hirsute: Fix Released Status in libqmi source package in Hirsute: Fix Released Status in modemmanager source package in Hirsute: Fix Released Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to
[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
This bug was fixed in the package libmbim - 1.24.8-1~20.04 --- libmbim (1.24.8-1~20.04) focal; urgency=medium [ Łukasz 'sil2100' Zemczak ] * Add debian/libmbim-proxy.links to make sure the mbim-proxy binary is in both the old and new path. [ Jerry Lee ] * Backport to focal. (LP: #1934286) -- Łukasz 'sil2100' Zemczak Wed, 14 Jul 2021 10:30:15 +0200 ** Changed in: libqmi (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/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Released Status in libqmi source package in Focal: Fix Released Status in modemmanager source package in Focal: Fix Released Status in libmbim source package in Hirsute: Fix Released Status in libqmi source package in Hirsute: Fix Released Status in modemmanager source package in Hirsute: Fix Released Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in
[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
This bug was fixed in the package modemmanager - 1.16.6-2~20.04 --- modemmanager (1.16.6-2~20.04) focal; urgency=medium * Backport to focal. (LP: #1934286) -- Jerry Lee Wed, 07 Jul 2021 10:10:02 +0800 ** Changed in: modemmanager (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: libmbim (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/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Released Status in libqmi source package in Focal: Fix Released Status in modemmanager source package in Focal: Fix Released Status in libmbim source package in Hirsute: Fix Released Status in libqmi source package in Hirsute: Fix Released Status in modemmanager source package in Hirsute: Fix Released Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the
[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
This bug was fixed in the package modemmanager - 1.16.6-2~21.04 --- modemmanager (1.16.6-2~21.04) hirsute; urgency=medium * Backport to hirsute. (LP: #1934286) -- Jerry Lee Wed, 07 Jul 2021 11:55:02 +0800 ** Changed in: modemmanager (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: libmbim (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/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Released Status in libqmi source package in Focal: Fix Released Status in modemmanager source package in Focal: Fix Released Status in libmbim source package in Hirsute: Fix Released Status in libqmi source package in Hirsute: Fix Released Status in modemmanager source package in Hirsute: Fix Released Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in
[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
This bug was fixed in the package libmbim - 1.24.8-1~21.04 --- libmbim (1.24.8-1~21.04) hirsute; urgency=medium [ Jerry Lee ] * Backport to hirsute. (LP: #1934286) -- Łukasz 'sil2100' Zemczak Thu, 08 Jul 2021 14:21:47 +0200 ** Changed in: libqmi (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/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Released Status in libqmi source package in Focal: Fix Released Status in modemmanager source package in Focal: Fix Released Status in libmbim source package in Hirsute: Fix Released Status in libqmi source package in Hirsute: Fix Released Status in modemmanager source package in Hirsute: Fix Released Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3
[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
This bug was fixed in the package libqmi - 1.28.6-1~21.04 --- libqmi (1.28.6-1~21.04) hirsute; urgency=medium [ Jerry Lee ] * Backport to hirsute. (LP: #1934286) -- Łukasz 'sil2100' Zemczak Thu, 08 Jul 2021 14:19:18 +0200 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Released Status in libqmi source package in Focal: Fix Released Status in modemmanager source package in Focal: Fix Released Status in libmbim source package in Hirsute: Fix Released Status in libqmi source package in Hirsute: Fix Released Status in modemmanager source package in Hirsute: Fix Released Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.8 *
[Touch-packages] [Bug 1934286] 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/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Released Status in libqmi source package in Focal: Fix Released Status in modemmanager source package in Focal: Fix Released Status in libmbim source package in Hirsute: Fix Released Status in libqmi source package in Hirsute: Fix Released Status in modemmanager source package in Hirsute: Fix Released Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported
[Touch-packages] [Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
** Tags added: oem-priority originate-from-1933586 wenshan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd Status in OEM Priority Project: New Status in network-manager package in Ubuntu: New Status in network-manager source package in Focal: New Bug description: Network manager gets NTP servers from DHCP but do not update timesyncd to use it which keeps using ntp.ubuntu.com. This is a problem on private networks which do not have access to public internet. On this type of network the configuration of timesyncd must be updated manually instead of inheriting the conf from the dhcp servers. This can be integrated with a NM dispatcher script such as below: etc/NetworkManager/dispatcher.d/10-update-timesyncd for example: ==8<=8<=8<=8<=8<== #! /usr/bin/bash [ -n "$CONNECTION_UUID" ] || exit INTERFACE=$1 ACTION=$2 case $ACTION in up | dhcp4-change | dhcp6-change) [ -n "$DHCP4_NTP_SERVERS" ] || exit mkdir -p /etc/systemd/timesyncd.conf.d/ cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf [Time] NTP=$DHCP4_NTP_SERVERS RootDistanceMaxSec=15 EOF systemctl restart systemd-timesyncd ;; down) rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf systemctl restart systemd-timesyncd ;; esac ==8<=8<=8<=8<=8<== ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 14:08:52 2021 InstallationDate: Installed on 2020-05-31 (393 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RebootRequiredPkgs: linux-image-5.11.0-20-generic linux-base SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933828/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942039] [NEW] Ubuntu server 20.04 disk size is incorrect by the command fdisk
Public bug reported: 1.Fresh install Ubuntu server 20.04.2 on lenovo server with 1.2TiB disk. 2.The installer display it 1.091TiB, but it display 1.9TiB by the command "fdisk -l". 3.Finsh the installation and boot into OS, it still display 1.9TiB as following: # cat ./sos_commands/block/fdisk_-l_.dev.sdb Disk /dev/sdb: 1.9 TiB, 1200243695616 bytes, 2344225968 sectors Disk model: ST1200MM0088 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes The other things: 1.The ubuntu server 21.04 is normal at the same environment. 2.The latest ubuntu server 20.04 daily build can reproduce the issue. ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "sosreport and installer screenshot" https://bugs.launchpad.net/bugs/1942039/+attachment/5521562/+files/log_screenshot.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1942039 Title: Ubuntu server 20.04 disk size is incorrect by the command fdisk Status in util-linux package in Ubuntu: New Bug description: 1.Fresh install Ubuntu server 20.04.2 on lenovo server with 1.2TiB disk. 2.The installer display it 1.091TiB, but it display 1.9TiB by the command "fdisk -l". 3.Finsh the installation and boot into OS, it still display 1.9TiB as following: # cat ./sos_commands/block/fdisk_-l_.dev.sdb Disk /dev/sdb: 1.9 TiB, 1200243695616 bytes, 2344225968 sectors Disk model: ST1200MM0088 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes The other things: 1.The ubuntu server 21.04 is normal at the same environment. 2.The latest ubuntu server 20.04 daily build can reproduce the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1942039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent()
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1942031 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1942031 Title: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() Status in gnome-shell package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/11d90a7db51d11df7d99a6ef6e5aa31eb678d273 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1942031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
