[Touch-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
Upstream seems replaced the comment#7 by https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/596 -- 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/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Incomplete Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1956835] Re: package linux-firmware 1.187.24 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
[Expired for initramfs-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => Expired -- 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/1956835 Title: package linux-firmware 1.187.24 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Expired Bug description: After updating the system, rebooted and this error appeared. Fixed a problem related to /boot/grub/grubenv - "Error in environment" and grub-common.service by providing absolute path to grub-editenv. /boot/grub/grubenv was full of 0x0, rather than 0x2323 as it has now. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.24 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alistair 3520 F pulseaudio CasperMD5CheckResult: skip Date: Sat Jan 8 17:37:06 2022 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-11-12 (422 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP EliteBook 8470p PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_x1by5v@/vmlinuz-5.11.0-44-generic root=ZFS=rpool/ROOT/ubuntu_x1by5v ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.24 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2018 dmi.bios.release: 15.113 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICF Ver. F.71 dmi.board.name: 179B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.38 dmi.chassis.asset.tag: CNU3109W10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 66.56 dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICFVer.F.71:bd04/12/2018:br15.113:efr66.56:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1029D1102:skuC3Q91UC#ABU:rvnHewlett-Packard:rn179B:rvrKBCVersion42.38:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8470p dmi.product.sku: C3Q91UC#ABU dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1956835/+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 1965215] Re: [81FD, Realtek ALC236, Black Mic, Right] The external microphone is not detected
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1965215 Title: [81FD, Realtek ALC236, Black Mic, Right] The external microphone is not detected Status in alsa-driver package in Ubuntu: New Bug description: Description: Ubuntu 20.04.4 LTS Release: 20.04 When inserted in the 3.5mm phone jack, the external microphone is not detected, and thus the audio input doesn't auto-switch from the internal microphone to the external microphone. The problem probably is related to the kernel version, as kernels 5.11.0-34, 5.11.0-36,5.11.0-37 and 5.11.0-38 works as expected, but kernels 5.4.0-104, 5.11.0-40, 5.11.0-41, 5.11.0-43, 5.11.0-44, 5.11.0-46, 5.13.0-30 and 5.13.0-35 don't. A similar problem happens for Debian 11. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thales 1485 F pulseaudio /dev/snd/pcmC0D0p: thales 1485 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 00:07:20 2022 InstallationDate: Installed on 2022-03-09 (7 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Áudio interno - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_Type: No auto-switch between inputs Title: [81FD, Realtek ALC236, Black Mic, Right] No autoswitch UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2021 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: 8RCN58WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.ec.firmware.release: 1.58 dmi.modalias: dmi:bvnLENOVO:bvr8RCN58WW:bd05/19/2021:br1.58:efr1.58:svnLENOVO:pn81FD:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB:skuLENOVO_MT_81FD_BU_idea_FM_ideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81FD dmi.product.sku: LENOVO_MT_81FD_BU_idea_FM_ideapad 330-15IKB dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965215/+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 1965219] Re: gnome lock screen does not permit reentering password
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password Status in xorg package in Ubuntu: New Bug description: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1965219/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1965215] [NEW] [81FD, Realtek ALC236, Black Mic, Right] The external microphone is not detected
You have been subscribed to a public bug: Description:Ubuntu 20.04.4 LTS Release:20.04 When inserted in the 3.5mm phone jack, the external microphone is not detected, and thus the audio input doesn't auto-switch from the internal microphone to the external microphone. The problem probably is related to the kernel version, as kernels 5.11.0-34, 5.11.0-36,5.11.0-37 and 5.11.0-38 works as expected, but kernels 5.4.0-104, 5.11.0-40, 5.11.0-41, 5.11.0-43, 5.11.0-44, 5.11.0-46, 5.13.0-30 and 5.13.0-35 don't. A similar problem happens for Debian 11. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thales 1485 F pulseaudio /dev/snd/pcmC0D0p: thales 1485 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 00:07:20 2022 InstallationDate: Installed on 2022-03-09 (7 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Áudio interno - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_Type: No auto-switch between inputs Title: [81FD, Realtek ALC236, Black Mic, Right] No autoswitch UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2021 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: 8RCN58WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.ec.firmware.release: 1.58 dmi.modalias: dmi:bvnLENOVO:bvr8RCN58WW:bd05/19/2021:br1.58:efr1.58:svnLENOVO:pn81FD:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB:skuLENOVO_MT_81FD_BU_idea_FM_ideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81FD dmi.product.sku: LENOVO_MT_81FD_BU_idea_FM_ideapad 330-15IKB dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- [81FD, Realtek ALC236, Black Mic, Right] The external microphone is not detected https://bugs.launchpad.net/bugs/1965215 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1965219] [NEW] gnome lock screen does not permit reentering password
You have been subscribed to a public bug: Initially, only the mouse works in the gnome lock screen, without any way to get a password prompt. It's likely only happening when returning from suspend with lid open. It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and login without gnome. After this, Fn+Ctrl+Alt+F1 brings up a purple ubuntu login screen, but then after login you simply return to the lock screen with no working keyboard. I never found any method to force unlock from ssh or another vt though, so this always still required a reboot, or killing all of gnome. I've randomly tried some solutions from https://askubuntu.com/questions/1242110/after-upgrading-to- ubuntu-20-04-lockscreen-not-working including reinstalling many gnome components. After this, the behavior initially disappeared by returning from suspend merely took a long time, like 30 seconds or 1 minute. It's possible the delay stems from memory size, but a previous identical lenovo x1 had no such problems. I've now a worse problem just a few hours later where unsuspend went directly to a purple ubuntu login screen, but neither the mouse nor keyboard worked. I've not yet been able to test ssh on this problem. It's possibly all connected to recent firmware upgrades, so I'm happy to try downgrading the firmware, but I've not found any instructions on doing so, or even identifying the firmware upgrade log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21 Uname: Linux 5.14.0-1027-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 17 03:44:49 2022 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d5] InstallationDate: Installed on 2021-04-15 (335 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210412-22:07 MachineType: LENOVO 20XWCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2021 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET75W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XWCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9: dmi.product.family: ThinkPad X1 Carbon Gen 9 dmi.product.name: 20XWCTO1WW dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9 dmi.product.version: ThinkPad X1 Carbon Gen 9 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-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 freeze ubuntu -- gnome lock screen does not permit reentering password https://bugs.launchpad.net/bugs/1965219 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 493050] Re: ubuntu-bug "Collecting problem information..." for over 30 min
Yes, this remains an issues in ubuntu 20, nearly a fresh install. I'll
try to report what happens, but it's running for over an hour so far.
It's progress bar does slowly move however.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/493050
Title:
ubuntu-bug "Collecting problem information..." for over 30 min
Status in apport package in Ubuntu:
Expired
Bug description:
Binary package hint: apport
ubuntu-bug xserver-xorg-video-nouveau = "Collecting problem
information ... This might take a few minutes. ." it just
filled the 80x50 screen with 4000 dots, at about 1/2 sec per is 30
minutes.
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
carl 2529 0.2 1.8 89260 36592 pts/2Sl+ 22:11 0:08
/usr/bin/python /usr/bin/apport-cli xserver-xorg-video-nouveau
seems to be the same thing as #397140 so I am doing the strace ting:
carl@gw42:~$ pgrep apport
2529
carl@gw42:~$ ps ux|grep apport-cli | grep -v grep|awk '{print $2}'
2529
2716
carl@gw42:~$ strace -vvs1024 -o /tmp/apport-gtk.trace -p 2529
Process 2529 attached - interrupt to quit
which is lots of:
select(0, NULL, NULL, NULL, {0, 12114}) = 0 (Timeout)
gettimeofday({1260076594, 5680}, NULL) = 0
select(0, NULL, NULL, NULL, {0, 36012}) = 0 (Timeout)
gettimeofday({1260076594, 41961}, NULL) = 0
but I was able to run it for this report.
ProblemType: Bug
Architecture: amd64
Date: Sat Dec 5 23:00:07 2009
DistroRelease: Ubuntu 9.10
Package: apport 1.9.3-0ubuntu4.1
PackageArchitecture: all
ProcEnviron:
PATH=(custom, user)
LANG=en_US
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
SourcePackage: apport
Uname: Linux 2.6.31-16-generic x86_64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/493050/+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 1965116] Re: Desktop lockup with because Wayland compositor not fast enough
Thanks for the bug report. Next time a freeze happens please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt lspci -k > lspci.txt 4. Attach the resulting text files here. 5. Run: apport-collect 1965116 6. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 7. If step 6 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. ** Summary changed: - Desktop lockup with because Wayland compositor not fast enough + Desktop lockup ** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1965116 Title: Desktop lockup Status in gnome-shell package in Ubuntu: Incomplete Bug description: I use Ubuntu 21.10 with Wayland and nvidia drivers. Sometimes, when working, the desktop freezes. Over ssh, I can see in the system logs many of those messages: > gnome-shell[5615]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! dmesg doesn't show any problems. Xwayland has a very high CPU usage. Killing Xwayland didn't help. When I then restart gdm, logging in either works again, or at least gdm allows a graceful reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965116/+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 1963834] Re: openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
Ok, I did get my case to work by creating ~/ssl.conf containing:
openssl_conf = openssl_init
[openssl_init]
ssl_conf = ssl_sect
[ssl_sect]
system_default = system_default_sect
[system_default_sect]
Options = UnsafeLegacyRenegotiation
And then did OPENSSL_CONF=~/ssl.conf do-my-command
that works. I don't know why the system-wide file does not.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1963834
Title:
openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
Status in openssl package in Ubuntu:
New
Bug description:
Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04
openssl:
Installé : 3.0.1-0ubuntu1
Candidat : 3.0.1-0ubuntu1
Table de version :
*** 3.0.1-0ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
Using Ubuntu 22.04, I now get the following error message when
attempting to connect to our office VPN using "gp-saml-gui
(https://github.com/dlenski/gp-saml-gui)" :
#
dominique@Doombuntu:~$ .local/bin/gp-saml-gui server_url
Looking for SAML auth tags in response to
https://server_url/global-protect/prelogin.esp...
usage: gp-saml-gui [-h] [--no-verify] [-C COOKIES | -K] [-g | -p] [-c CERT]
[--key KEY] [-v | -q] [-x | -P | -S] [-u] [--clientos {Windows,Linux,Mac}] [-f
EXTRA] server [openconnect_extra ...]
gp-saml-gui: error: SSL error: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
unsafe legacy renegotiation disabled (_ssl.c:997)
#
#
#
gp-saml-gui uses python module requests.
Using python ide, I can get the same results :
#
>>> r = requests.get('https://server_url')
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699,
in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 382,
in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1012,
in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 411, in
connect
self.sock = ssl_wrap_socket(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 449, in
ssl_wrap_socket
ssl_sock = _ssl_wrap_socket_impl(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 493, in
_ssl_wrap_socket_impl
return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/lib/python3.10/ssl.py", line 512, in wrap_socket
return self.sslsocket_class._create(
File "/usr/lib/python3.10/ssl.py", line 1070, in _create
self.do_handshake()
File "/usr/lib/python3.10/ssl.py", line 1341, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy
renegotiation disabled (_ssl.c:997)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in
send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755,
in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 574, in
increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='server_url',
port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1,
'[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation
disabled (_ssl.c:997)')))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/requests/api.py", line 76, in get
return request('get', url, params=params, **kwargs)
File "/usr/lib/python3/dist-packages/requests/api.py", line 61, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in
request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in
send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514, in
send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='server_url',
port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1,
'[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation
disabled (_ssl.c:997)')))
#
#
#
I believe in OpenSSL 3.0 that SSL_OP_LEGACY_SERVER_CONNECT is now
[Touch-packages] [Bug 1885990] Re: server: Match has no effect in include file (upstream 3122)
I can't speak for the SRU team, but it's entirely possible that if you prepare and test a debdiff, and show that this can be fixed, you could drive an SRU through to completion; see https://wiki.ubuntu.com/StableReleaseUpdates for more information. Thanks -- 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/1885990 Title: server: Match has no effect in include file (upstream 3122) Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Fix Released Bug description: Hello Ubuntu version: focal 20.04 LTS Version: openssh-server: Installed: 1:8.2p1-4ubuntu0.1 Candidate: 1:8.2p1-4ubuntu0.1 Expected: match statement in included files work as documented in the fine manual What happens: the statements are ignored. If you add Match statements in an included file, it will generate no error but have no effect. The exact same statements work in the main server config file (/etc/ssh/sshd_config) this is to track upstream bug 3122: https://bugzilla.mindrot.org/show_bug.cgi?id=3122 it's fixed but will only be in 8.4 so it affects Ubuntu 20.04 LTS where openssh is at 8.2. I'm not *absolutely* whining for a backport since include files is a new feature for openssl in focal so it's not a regression. Would be nice though :), because include files are standard for any server software in Linux since at least a decade... To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1885990/+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 1965008] Re: 'Software & Updates' crashes on tab 'Additional drivers'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965008 Title: 'Software & Updates' crashes on tab 'Additional drivers' Status in software-properties package in Ubuntu: Confirmed Bug description: Crash did not occur a couple of days ago. 'sudo ubuntu-drivers list' has no problems listing the drivers. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.19 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 21:04:29 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-02-26 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=4 Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=4'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965008/+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 1885990] Re: server: Match has no effect in include file (upstream 3122)
@Jernej Jakob: this is cited as 'released for 1.8.4'. There is a policy for stable distros, never update the version. I asked for a backport, did not get one. The 20.04 version is still at 1.8.2 and it does not has this feature that was introduced after this version. It was released for groovy, that is 20.10. But I had no right for it, I begged for it but was denied. That's life. As of documentation, yes but it's a pretty obscure feature and Ubuntu devs don't have the responsability for writing man pages and there is no need to document a non-existent feature. -- 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/1885990 Title: server: Match has no effect in include file (upstream 3122) Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Fix Released Bug description: Hello Ubuntu version: focal 20.04 LTS Version: openssh-server: Installed: 1:8.2p1-4ubuntu0.1 Candidate: 1:8.2p1-4ubuntu0.1 Expected: match statement in included files work as documented in the fine manual What happens: the statements are ignored. If you add Match statements in an included file, it will generate no error but have no effect. The exact same statements work in the main server config file (/etc/ssh/sshd_config) this is to track upstream bug 3122: https://bugzilla.mindrot.org/show_bug.cgi?id=3122 it's fixed but will only be in 8.4 so it affects Ubuntu 20.04 LTS where openssh is at 8.2. I'm not *absolutely* whining for a backport since include files is a new feature for openssl in focal so it's not a regression. Would be nice though :), because include files are standard for any server software in Linux since at least a decade... To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1885990/+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 1965138] Re: Desktop application should check for service available information before listing it
The following PR should hopefully fix this: https://github.com/canonical/ubuntu-advantage-desktop-daemon/pull/14 ** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: software-properties (Ubuntu) Importance: Undecided => High ** Changed in: software-properties (Ubuntu) Status: New => In Progress ** Package changed: software-properties (Ubuntu) => ubuntu-advantage- desktop-daemon (Ubuntu) ** Changed in: ubuntu-advantage-desktop-daemon (Ubuntu) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965138 Title: Desktop application should check for service available information before listing it Status in ubuntu-advantage-desktop-daemon package in Ubuntu: In Progress Bug description: Currently, it seems that software-properties is incorrectly assuming that both ESM and Livepatch services can be enabled in a Jammy machine. Those services are not yet available in Jammy and we are attaching an image showing that the Desktop message is that we had an error enabling then and that the user should try again. It seems that software-proporties source `/var/lib/ubuntu- advantage/status.json` and assumes the services is available if it appears on the services list and the `entitled` field has the `yes` value. However, it is perfectly possible for a service to be entitled to an user, but not available in the user's machine. We are now suggesting that software-properties also looks at the `available` field in the services json output to make that assumption, this will probably solve the issue we are seeing on Jammy. Another approach would be using the output of `ua status --format json` directly. However, this command will make a request to the contract's server if the user is unattached and maybe it is not wise to use it in that context. However, the output of that command only show services that are available, so we would not need to apply that extra available filter to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-desktop-daemon/+bug/1965138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1892825] Please test proposed package
Hello bs, or anyone else affected, Accepted glibc into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glibc/2.31-0ubuntu9.8 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 pam in Ubuntu. https://bugs.launchpad.net/bugs/1892825 Title: update-locale not perform correctly sanity checks Status in glibc package in Ubuntu: In Progress Status in pam package in Ubuntu: New Status in glibc source package in Bionic: New Status in pam source package in Bionic: New Status in glibc source package in Focal: Fix Committed Status in pam source package in Focal: New Status in glibc source package in Hirsute: Won't Fix Status in pam source package in Hirsute: New Status in glibc source package in Impish: New Status in pam source package in Impish: New Bug description: [impact] A simple typo using the update-locale script can render a system inoperable without booting into single user mode or similar: $ sudo update-locale LANGUAGE = en_US.UTF-8 $ sudo -s sudo: pam_open_session: Bad item passed to pam_*_item() sudo: policy plugin failed session initialization [test case] $ cp /etc/default/locale /tmp/locale $ update-locale --locale-file /tmp/locale LANGUAGE = en_US.UTF-8 "diff -u /etc/default/locale /tmp/locale" should be empty. $ update-locale --locale-file /tmp/locale LANGUAGE=en_US.UTF-8 The LANGUAGE=en_US.UTF-8 line should have been replaced by LANGUAGE=en_GB.UTF-8. $ update-locale --locale-file /tmp/locale LANGUAGE The LANGUAGE setting is now commented out. [regression potential] Apart from the general concerns about a glibc rebuild, this is a simple change to a simple script. Performing the test as in the test case section is enough to ensure it still works. [original description] By passing wrong input as following: sudo update-locale LANGUAGE = en_US.UTF-8 result is: ... #LANGUAGE=en = This "equal" sign that was added makes system completely unusable(can't run sudo anymore): bentzy@bentzy-nb:~$ sudo vim /etc/default/locale sudo: pam_open_session: Bad item passed to pam_*_item() sudo: policy plugin failed session initialization Fixed it booting from installation disk and fixing corrupted /etc/default/locale ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: locales 2.31-0ubuntu9 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Aug 25 09:36:03 2020 InstallationDate: Installed on 2020-08-17 (7 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: glibc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1892825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1927192] Please test proposed package
Hello Matthias, or anyone else affected, Accepted glibc into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glibc/2.31-0ubuntu9.8 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 gdb in Ubuntu. https://bugs.launchpad.net/bugs/1927192 Title: gdb ftbfs on armhf, testsuite timeouts Status in gdb: Incomplete Status in gdb package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Released Status in gdb source package in Focal: Fix Released Status in glibc source package in Focal: Fix Committed Status in gdb source package in Groovy: Won't Fix Status in glibc source package in Groovy: Won't Fix Status in gdb source package in Hirsute: Won't Fix Status in glibc source package in Hirsute: Won't Fix Status in gdb source package in Impish: Fix Released Status in glibc source package in Impish: Fix Released Bug description: [Impact] * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is not installed. [Test Plan] * Check that ld.so is not stripped on armhf: $ /lib/*/ld-2.31.so libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not stripped * Check that ld.so is stripped on amd64: $ file /lib/x86_64-linux-gnu/ld-2.31.so /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped [Where problems could occur] * The fix is not stripping ld.so on armhf. Not stripping it comes with a notable increase in file size and it may be performance critical 109K stripped vs 1.3M unstripped. Accidentally ld.so could be left unstripped on other architectures, but the test plan covers checking that, at least on amd64. Other than those not stripping ld.so should not cause any issue. [Original Bug Text] see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3 $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep '(timeout)'|wc -l 10451 To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1927192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1892825] Re: update-locale not perform correctly sanity checks
** Changed in: glibc (Ubuntu Hirsute) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1892825 Title: update-locale not perform correctly sanity checks Status in glibc package in Ubuntu: In Progress Status in pam package in Ubuntu: New Status in glibc source package in Bionic: New Status in pam source package in Bionic: New Status in glibc source package in Focal: Fix Committed Status in pam source package in Focal: New Status in glibc source package in Hirsute: Won't Fix Status in pam source package in Hirsute: New Status in glibc source package in Impish: New Status in pam source package in Impish: New Bug description: [impact] A simple typo using the update-locale script can render a system inoperable without booting into single user mode or similar: $ sudo update-locale LANGUAGE = en_US.UTF-8 $ sudo -s sudo: pam_open_session: Bad item passed to pam_*_item() sudo: policy plugin failed session initialization [test case] $ cp /etc/default/locale /tmp/locale $ update-locale --locale-file /tmp/locale LANGUAGE = en_US.UTF-8 "diff -u /etc/default/locale /tmp/locale" should be empty. $ update-locale --locale-file /tmp/locale LANGUAGE=en_US.UTF-8 The LANGUAGE=en_US.UTF-8 line should have been replaced by LANGUAGE=en_GB.UTF-8. $ update-locale --locale-file /tmp/locale LANGUAGE The LANGUAGE setting is now commented out. [regression potential] Apart from the general concerns about a glibc rebuild, this is a simple change to a simple script. Performing the test as in the test case section is enough to ensure it still works. [original description] By passing wrong input as following: sudo update-locale LANGUAGE = en_US.UTF-8 result is: ... #LANGUAGE=en = This "equal" sign that was added makes system completely unusable(can't run sudo anymore): bentzy@bentzy-nb:~$ sudo vim /etc/default/locale sudo: pam_open_session: Bad item passed to pam_*_item() sudo: policy plugin failed session initialization Fixed it booting from installation disk and fixing corrupted /etc/default/locale ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: locales 2.31-0ubuntu9 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Aug 25 09:36:03 2020 InstallationDate: Installed on 2020-08-17 (7 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: glibc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1892825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895383] Re: package shared-mime-info 1.15-1 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: shared-mime-info (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1895383 Title: package shared-mime-info 1.15-1 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 1 Status in shared-mime-info package in Ubuntu: Confirmed Bug description: Failure occurred on update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: shared-mime-info 1.15-1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: bcompare:amd64: Install r-cran-mass:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Sep 12 19:29:30 2020 DuplicateSignature: package:shared-mime-info:1.15-1 Processing triggers for shared-mime-info (1.15-1) ... Failed to rename /usr/share/mime/inode/socket.xml.new as /usr/share/mime/inode/socket.xml: No such file or directory dpkg: error processing package shared-mime-info (--configure): installed shared-mime-info package post-installation script subprocess returned error exit status 1 ErrorMessage: installed shared-mime-info package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-05-07 (127 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: shared-mime-info Title: package shared-mime-info 1.15-1 failed to install/upgrade: installed shared-mime-info 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/shared-mime-info/+bug/1895383/+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 1963834] Re: openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
I tried also adding the following:
[openssl_init]
providers = provider_sect
ssl_conf = ssl_configuration
as I wasn't sure whether the [ssl_configuration] section would otherwise
get used for anything, but that didn't seem to make a difference.
The end of the file is
[ssl_configuration]
client = client_tls_config
# https://www.mail-archive.com/openssl-users%40openssl.org/msg90598.htm
l
# https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834
[client_tls_config]
Options = UnsafeLegacyRenegotiation
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1963834
Title:
openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
Status in openssl package in Ubuntu:
New
Bug description:
Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04
openssl:
Installé : 3.0.1-0ubuntu1
Candidat : 3.0.1-0ubuntu1
Table de version :
*** 3.0.1-0ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
Using Ubuntu 22.04, I now get the following error message when
attempting to connect to our office VPN using "gp-saml-gui
(https://github.com/dlenski/gp-saml-gui)" :
#
dominique@Doombuntu:~$ .local/bin/gp-saml-gui server_url
Looking for SAML auth tags in response to
https://server_url/global-protect/prelogin.esp...
usage: gp-saml-gui [-h] [--no-verify] [-C COOKIES | -K] [-g | -p] [-c CERT]
[--key KEY] [-v | -q] [-x | -P | -S] [-u] [--clientos {Windows,Linux,Mac}] [-f
EXTRA] server [openconnect_extra ...]
gp-saml-gui: error: SSL error: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
unsafe legacy renegotiation disabled (_ssl.c:997)
#
#
#
gp-saml-gui uses python module requests.
Using python ide, I can get the same results :
#
>>> r = requests.get('https://server_url')
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699,
in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 382,
in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1012,
in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 411, in
connect
self.sock = ssl_wrap_socket(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 449, in
ssl_wrap_socket
ssl_sock = _ssl_wrap_socket_impl(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 493, in
_ssl_wrap_socket_impl
return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/lib/python3.10/ssl.py", line 512, in wrap_socket
return self.sslsocket_class._create(
File "/usr/lib/python3.10/ssl.py", line 1070, in _create
self.do_handshake()
File "/usr/lib/python3.10/ssl.py", line 1341, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy
renegotiation disabled (_ssl.c:997)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in
send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755,
in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 574, in
increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='server_url',
port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1,
'[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation
disabled (_ssl.c:997)')))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/requests/api.py", line 76, in get
return request('get', url, params=params, **kwargs)
File "/usr/lib/python3/dist-packages/requests/api.py", line 61, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in
request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in
send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514, in
send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='server_url',
port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1,
'[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe
[Touch-packages] [Bug 1965180] [NEW] apt-add-repository requires --login for private repos, breaking automated workflows
Public bug reported:
On Focal, in an automated environment (such as a launchpad builder), a
used can do the following workflow:
curl
"https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT};
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc
apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
ppa.launchpad.net/${REPO}/ubuntu focal main"
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu focal-security InRelease
Get:5 https://private-ppa.launchpad.net/$REPO/ubuntu focal InRelease [24.3 kB]
Get:6 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main amd64 Packages
[3288 B]
Get:7 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main Translation-en
[1892 B]
However, on Jammy, I get the following:
curl "https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT};
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc
apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
ppa.launchpad.net/${REPO}/ubuntu jammy main"
Repository: 'deb https://private-ppa.launchpad.net/$REPO/ubuntu jammy main'
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 105, in
lpppa
self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
File "/usr/lib/python3/dist-packages/lazr/restfulclient/resource.py", line
592, in __call__
response, content = self.root._browser._request(
File "/usr/lib/python3/dist-packages/lazr/restfulclient/_browser.py", line
429, in _request
raise error
lazr.restfulclient.errors.NotFound: HTTP Error 404: Not Found
Response headers:
---
-content-encoding: gzip
content-length: 91
content-type: text/plain;charset=utf-8
date: Wed, 16 Mar 2022 19:54:16 GMT
server: gunicorn/19.8.1
status: 404
vary: Accept-Encoding
x-powered-by: Zope (www.zope.org), Python (www.python.org)
x-request-id: ec4bd7ff-f333-4543-ba91-3b7b063fab0e
x-vcs-revision: 81acd06336f3c4be8f28a2213f7a64912593402d
---
Response body:
---
b"Object: ,
name: '$REPO'"
---
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/apt-add-repository", line 364, in
sys.exit(0 if addaptrepo.main() else 1)
File "/usr/bin/apt-add-repository", line 352, in main
self.prompt_user_shortcut(shortcut)
File "/usr/bin/apt-add-repository", line 140, in prompt_user_shortcut
if shortcut.description:
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 117, in
description
return self.lpppa.description
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 109, in
lpppa
raise ShortcutException(msg)
softwareproperties.shortcuthandler.ShortcutException: ERROR: ppa
'$REPO/proposed' not found (use --login if private)
Impish similarly breaks. Digging through changelogs, I see various
entries in Impish forward, starting with version 0.99.0 where a refactor
was done.
using `--login` is not possible in an automated setup (such as a
builder) as it starts an OAuth dance, which requires human interaction.
this will break existing automation utilizing apt-add-repository for
users when migrating to Jammy
** Affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1965180
Title:
apt-add-repository requires --login for private repos, breaking
automated workflows
Status in software-properties package in Ubuntu:
New
Bug description:
On Focal, in an automated environment (such as a launchpad builder), a
used can do the following workflow:
curl
"https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT};
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc
apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
ppa.launchpad.net/${REPO}/ubuntu focal main"
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu focal-security InRelease
Get:5 https://private-ppa.launchpad.net/$REPO/ubuntu focal InRelease [24.3 kB]
Get:6 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main amd64
Packages [3288 B]
Get:7 https://private-ppa.launchpad.net/$REPO/ubuntu focal/main
Translation-en [1892 B]
However, on Jammy, I get the following:
curl "https://keyserver.ubuntu.com/pks/lookup?op=get=0x${FINGERPRINT};
--output /etc/apt/trusted.gpg.d/${FINGERPRINT}.asc
apt-add-repository "deb https://${USERNAME}:${PASSWORD}@private-
[Touch-packages] [Bug 1963834] Re: openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
FWIW I'm seeing this with the openconnect-sso
(https://github.com/vlaci/openconnect-sso) package on jammy. I just
tried adding the following to my /etc/ssl/openssl.cfg:
[ssl_configuration]
client = client_tls_config
[client_tls_config]
Options = UnsafeLegacyServerConnect
With no luck :(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1963834
Title:
openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
Status in openssl package in Ubuntu:
New
Bug description:
Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04
openssl:
Installé : 3.0.1-0ubuntu1
Candidat : 3.0.1-0ubuntu1
Table de version :
*** 3.0.1-0ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
Using Ubuntu 22.04, I now get the following error message when
attempting to connect to our office VPN using "gp-saml-gui
(https://github.com/dlenski/gp-saml-gui)" :
#
dominique@Doombuntu:~$ .local/bin/gp-saml-gui server_url
Looking for SAML auth tags in response to
https://server_url/global-protect/prelogin.esp...
usage: gp-saml-gui [-h] [--no-verify] [-C COOKIES | -K] [-g | -p] [-c CERT]
[--key KEY] [-v | -q] [-x | -P | -S] [-u] [--clientos {Windows,Linux,Mac}] [-f
EXTRA] server [openconnect_extra ...]
gp-saml-gui: error: SSL error: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]
unsafe legacy renegotiation disabled (_ssl.c:997)
#
#
#
gp-saml-gui uses python module requests.
Using python ide, I can get the same results :
#
>>> r = requests.get('https://server_url')
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699,
in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 382,
in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1012,
in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 411, in
connect
self.sock = ssl_wrap_socket(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 449, in
ssl_wrap_socket
ssl_sock = _ssl_wrap_socket_impl(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 493, in
_ssl_wrap_socket_impl
return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/lib/python3.10/ssl.py", line 512, in wrap_socket
return self.sslsocket_class._create(
File "/usr/lib/python3.10/ssl.py", line 1070, in _create
self.do_handshake()
File "/usr/lib/python3.10/ssl.py", line 1341, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy
renegotiation disabled (_ssl.c:997)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in
send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755,
in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 574, in
increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='server_url',
port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1,
'[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation
disabled (_ssl.c:997)')))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/requests/api.py", line 76, in get
return request('get', url, params=params, **kwargs)
File "/usr/lib/python3/dist-packages/requests/api.py", line 61, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in
request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in
send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514, in
send
raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='server_url',
port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1,
'[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation
disabled (_ssl.c:997)')))
#
#
#
I believe in OpenSSL 3.0 that SSL_OP_LEGACY_SERVER_CONNECT is now
disabled by default, as opposed to the version used in earlier
[Touch-packages] [Bug 1965176] [NEW] Create mode does not persist after reboot
Public bug reported: Command `grep ^\s*\$FileCreateMode /etc/rsyslog.conf /etc/rsyslog.d/*.conf` returns `/etc/rsyslog.conf:$FileCreateMode 0640`, but logfiles are created with read permission for others. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rsyslog 8.2001.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 16:22:35 2022 InstallationDate: Installed on 2021-10-16 (151 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.rsyslog.conf: 2022-03-16T15:49:11.564719 ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1965176 Title: Create mode does not persist after reboot Status in rsyslog package in Ubuntu: New Bug description: Command `grep ^\s*\$FileCreateMode /etc/rsyslog.conf /etc/rsyslog.d/*.conf` returns `/etc/rsyslog.conf:$FileCreateMode 0640`, but logfiles are created with read permission for others. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rsyslog 8.2001.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 16:22:35 2022 InstallationDate: Installed on 2021-10-16 (151 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.rsyslog.conf: 2022-03-16T15:49:11.564719 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1965176/+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 1885990] Re: server: Match has no effect in include file (upstream 3122)
Why is this marked as "fix released"? It's still broken on Ubuntu 20.04 LTS, the fix has not been released into it. At the very least, the behavior does not match what is described in the sshd_config man page. Nowhere does it mention that Match blocks don't work inside Include files. Not only that, the config passes config test, and a LogLevel VERBOSE will say that the Match section has been processed, but then it has really been silently ignored! It took me hours to debug this issue back to a post on the mailing list, to the upstream fix, to this bug report. -- 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/1885990 Title: server: Match has no effect in include file (upstream 3122) Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Fix Released Bug description: Hello Ubuntu version: focal 20.04 LTS Version: openssh-server: Installed: 1:8.2p1-4ubuntu0.1 Candidate: 1:8.2p1-4ubuntu0.1 Expected: match statement in included files work as documented in the fine manual What happens: the statements are ignored. If you add Match statements in an included file, it will generate no error but have no effect. The exact same statements work in the main server config file (/etc/ssh/sshd_config) this is to track upstream bug 3122: https://bugzilla.mindrot.org/show_bug.cgi?id=3122 it's fixed but will only be in 8.4 so it affects Ubuntu 20.04 LTS where openssh is at 8.2. I'm not *absolutely* whining for a backport since include files is a new feature for openssl in focal so it's not a regression. Would be nice though :), because include files are standard for any server software in Linux since at least a decade... To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1885990/+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 1965112] Re: cupsd crashed with SIGSEGV in __strcmp_evex()
I have uploaded cups 2.4.1op1-1ubuntu3 with the updated patch now, and
also updated the upstream pull request:
https://github.com/OpenPrinting/cups/pull/353
Please test as soon as the update arrives.
** Changed in: cups (Ubuntu)
Status: In Progress => Fix Committed
--
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/1965112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
Fix Committed
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 16 11:00:00 2022
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2022-02-28 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: LENOVO 20Y5CTO1WW
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb
(%rsi),%ymm17,%k1{%k2}
PC (0x7fdde6d9698c) ok
source "(%rsi)" (0x) not located in a known VMA region (needed
readable region)!
destination "%ymm17" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
__strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
?? ()
?? ()
?? ()
__libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2,
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
Title: cupsd crashed with SIGSEGV in __strcmp_evex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
dmi.bios.date: 10/14/2021
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET29W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
dmi.product.family: ThinkPad X1 Extreme Gen 4i
dmi.product.name: 20Y5CTO1WW
dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
dmi.product.version: ThinkPad X1 Extreme Gen 4i
dmi.sys.vendor: LENOVO
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+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 1965112] Re: cupsd crashed with SIGSEGV in __strcmp_evex()
Thanks for all the info, it is as I expected, your cupsd.conf has
"Browsing No" because you do not use printer sharing. Then the DNS-SD
host name is not set in the daemon's internal variable DNSSDHostName and
this variable I compared with the host name of the URI of the potential
new queue to see whether I have to change it to "localhost" for the case
that the printer is a local service (IPP-over-USB, Printer Application,
...). This caused the crash. Now I have added a fallback to the internal
variable ServerName if DNSSDHostName is NULL.
I could reproduce the bug by doing the command
cupsctl --no-share-printers
(I had printer sharing on for my OpenPrinting work) and re-trying to
access an IPP printer through GTK's print dialog which caused the crash
then for me.
I have the fix now ready and with it the crash goes away.
I will update the Pull Request on CUPS upstream
(https://github.com/OpenPrinting/cups/pull/353) and also the patch on
the Ubuntu package.
Thanks for the bug report.
--
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/1965112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
In Progress
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 16 11:00:00 2022
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2022-02-28 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: LENOVO 20Y5CTO1WW
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb
(%rsi),%ymm17,%k1{%k2}
PC (0x7fdde6d9698c) ok
source "(%rsi)" (0x) not located in a known VMA region (needed
readable region)!
destination "%ymm17" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
__strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
?? ()
?? ()
?? ()
__libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2,
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
Title: cupsd crashed with SIGSEGV in __strcmp_evex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
dmi.bios.date: 10/14/2021
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET29W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
dmi.product.family: ThinkPad X1 Extreme Gen 4i
dmi.product.name: 20Y5CTO1WW
dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
dmi.product.version: ThinkPad X1 Extreme Gen 4i
dmi.sys.vendor: LENOVO
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+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 1965112] Re: cupsd crashed with SIGSEGV in __strcmp_evex()
** Changed in: cups (Ubuntu)
Status: New => In Progress
--
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/1965112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
In Progress
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 16 11:00:00 2022
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2022-02-28 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: LENOVO 20Y5CTO1WW
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb
(%rsi),%ymm17,%k1{%k2}
PC (0x7fdde6d9698c) ok
source "(%rsi)" (0x) not located in a known VMA region (needed
readable region)!
destination "%ymm17" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
__strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
?? ()
?? ()
?? ()
__libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2,
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
Title: cupsd crashed with SIGSEGV in __strcmp_evex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
dmi.bios.date: 10/14/2021
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET29W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
dmi.product.family: ThinkPad X1 Extreme Gen 4i
dmi.product.name: 20Y5CTO1WW
dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
dmi.product.version: ThinkPad X1 Extreme Gen 4i
dmi.sys.vendor: LENOVO
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+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 1965112] Re: cupsd crashed with SIGSEGV in __strcmp_evex()
$ cupsctl
_debug_logging=1
_remote_admin=0
_remote_any=0
_share_printers=0
_user_cancel_any=0
BrowseLocalProtocols=dnssd
DefaultAuthType=Basic
ErrorPolicy=retry-job
IdleExitTimeout=60
JobPrivateAccess=default
JobPrivateValues=default
MaxLogSize=0
PageLogFormat=
SubscriptionPrivateAccess=default
SubscriptionPrivateValues=default
WebInterface=Yes
** Attachment added: "cupsd.conf"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+attachment/5569712/+files/cupsd.conf
** Changed in: cups (Ubuntu)
Status: Incomplete => New
--
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/1965112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
New
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 16 11:00:00 2022
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2022-02-28 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: LENOVO 20Y5CTO1WW
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb
(%rsi),%ymm17,%k1{%k2}
PC (0x7fdde6d9698c) ok
source "(%rsi)" (0x) not located in a known VMA region (needed
readable region)!
destination "%ymm17" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
__strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
?? ()
?? ()
?? ()
__libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2,
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
Title: cupsd crashed with SIGSEGV in __strcmp_evex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
dmi.bios.date: 10/14/2021
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET29W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
dmi.product.family: ThinkPad X1 Extreme Gen 4i
dmi.product.name: 20Y5CTO1WW
dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
dmi.product.version: ThinkPad X1 Extreme Gen 4i
dmi.sys.vendor: LENOVO
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+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 1965112] Re: cupsd crashed with SIGSEGV in __strcmp_evex()
doko@xe1:~$ driverless
ipp://HP%20LaserJet%20500%20colorMFP%20M570dw%20(6C84AD)._ipp._tcp.local/
doko@xe1:~$ driverless --std-ipp-uris
ipp://NPI6C84AD.local:631/ipp/printer
doko@xe1:~$ lpstat -v
lpstat: No destinations added.
$ ps aux | grep cups-browsed
root 94786 0.0 0.0 172744 11908 ?Ssl 11:00 0:00
/usr/sbin/cups-browsed
doko 110175 0.0 0.0 9560 2428 pts/4S+ 17:21 0:00 grep
--color=auto cups-browsed
Trying to print a png image with eog
** Attachment added: "error_log"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+attachment/5569701/+files/error_log
--
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/1965112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
New
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 16 11:00:00 2022
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2022-02-28 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: LENOVO 20Y5CTO1WW
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb
(%rsi),%ymm17,%k1{%k2}
PC (0x7fdde6d9698c) ok
source "(%rsi)" (0x) not located in a known VMA region (needed
readable region)!
destination "%ymm17" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
__strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
?? ()
?? ()
?? ()
__libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2,
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
Title: cupsd crashed with SIGSEGV in __strcmp_evex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
dmi.bios.date: 10/14/2021
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET29W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
dmi.product.family: ThinkPad X1 Extreme Gen 4i
dmi.product.name: 20Y5CTO1WW
dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
dmi.product.version: ThinkPad X1 Extreme Gen 4i
dmi.sys.vendor: LENOVO
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+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 1962214] Re: The documentation around NM's 10-globally-managed-devices.conf is inadequate
*** This bug is a duplicate of bug 1951653 *** https://bugs.launchpad.net/bugs/1951653 ** This bug has been marked a duplicate of bug 1951653 can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged' -- 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/1962214 Title: The documentation around NM's 10-globally-managed-devices.conf is inadequate Status in netplan: New Status in network-manager package in Ubuntu: New Bug description: So, we're UBports, porting Ubuntu Touch stack to Ubuntu 20.04. While debugging why NM won't manage the phone's USB network interface, I stumbled upon /usr/lib/NetworkManager/conf.d/10-globally-managed- devices.conf. This file prevents NM from managing ethernet connection, which confuses me since this file also exists on my laptop, yet NM happily manages its ethernet port. This file exists at part of NetworkManager package in Ubuntu without any documentation. And the reason given in the commit that add it [1] does not mention any specific reason why it's added. Only when looking in the log on my laptop do I see that something places the file with the same name in /run/NetworkManager/conf.d/, and requires greping in /usr/lib to find out that the thing is Netplan's generator binary. Now, that file in /run is empty, which requires another round of searching to find out that Netplan places this file when it's configured to use NM as a renderer. With that in mind, I discovered that /etc/netplan/01-network-manager-all.yaml exists on my laptop but not the phone. Now, because 'dpkg -S' returns empty result, I need to search again what places this file, with no avail. Luckily, I happen to have a clone of livecd-rootfs on my laptop, which leads me to this commit [2] which finally reveals the reason why this is done: to prevent systems which installs NM after-the-fact to have NM conflicts with e.g. systemd-networkd. All of these knowledge should not require this much searching plus grepping through _binary_ file. If either my laptop was not running Ubuntu or I didn't have livecd-rootfs cloned, it would be much harder to figure this out. They should be more properly documented, probably both in the /usr/lib/ and /run/ files. Thus, this issue is filled against both Netplan and NetworkManager packages. [1] https://git.launchpad.net/network-manager/commit?id=1ab4db73c1f0db30f3af1845a9c41e3c3952dea1 [2] https://git.launchpad.net/livecd-rootfs/commit/?id=d9ce44d73a0a6d91156bb94e03063d541b0f7579 P.S. Arguably, this behavior might be even wrong. According to https://netplan.io: > Obviously, without configuration, netplan will not do anything. This is not really the expected "not do anything". IMO the NM's behavior should be left at the default, unless e.g. the networkd renderer is used, in which case Netplan will disable NetworkManager to not manage interfaces configured by Netplan. However the reason above of preventing conflict with networkd is a valid one, and my proposal doesn't help with that particular case. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1962214/+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 1731505] Re: boot into link down state
*** This bug is a duplicate of bug 1664844 *** https://bugs.launchpad.net/bugs/1664844 ** This bug has been marked a duplicate of bug 1664844 No distinction between link-up and link-down interfaces -- 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/1731505 Title: boot into link down state Status in netplan: In Progress Status in systemd package in Ubuntu: Won't Fix Bug description: I have multiple NICs in my Ubuntu 17.10 server, and i want at least one of them to be configured but not brought UP on boot. I want it to boot into link state DOWN. I'd also prefer the link to be / stay down during boot-up. My use case requires manual 'ip link set enp2s0f3 up', or 'ifup enp2s0f3' as it were. When the interface is being brought up manually, it should already be configured. I'm looking for a link state toggle, like a hardware switch on a Cat6 cable. My request is intended to reproduce the behaviour of the old ifupdown's /etc/network/interfaces, without enabling 'auto' or 'allow- hotplug'. #auto enp2s0f3 #allow-hotplug enp2s0f3 iface enp2s0f3 inet static address 10.10.1.10 netmask 255.255.255.0 network 10.10.1.0 broadcast 10.10.1.255 gateway 10.10.1.1 dns-nameservers 10.10.1.1 It seems neither systemd, nor NetworkManager "have any way to specify you want a configured device to stay down". -- i'm quoting cyphermox from the freenode/netplan IRC To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1731505/+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 1664844] Re: No distinction between link-up and link-down interfaces
The fix was released with netplan v0.103. ** Changed in: netplan Status: In Progress => Fix Released ** Changed in: netplan.io (Ubuntu Focal) Status: New => Fix Released ** Changed in: netplan.io (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: netplan.io (Ubuntu Groovy) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1664844 Title: No distinction between link-up and link-down interfaces Status in MAAS: Triaged Status in netplan: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in netplan.io source package in Xenial: Won't Fix Status in systemd source package in Xenial: Won't Fix Status in netplan.io source package in Zesty: Won't Fix Status in systemd source package in Zesty: Won't Fix Status in netplan.io source package in Artful: Won't Fix Status in netplan.io source package in Bionic: Won't Fix Status in systemd source package in Bionic: Won't Fix Status in netplan.io source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in netplan.io source package in Groovy: Won't Fix Status in systemd source package in Groovy: Fix Released Status in netplan.io source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Bug description: [Impact] Since very long, we had a feature request in netplan to determine the activation mode of a given network interface. We got requests to enable marking some interfaces as 'manual', meaning that networkd (or any other backend) would not control its state in any way, requiring the administrator to bring the interface up or down manually. The other request was to mark a interface as 'off', that is: forcing the network interface to always be down until the configuration option isn't changed. This was mainly requested for the networkd backend and requires the new feature of specifying ActivationPolicy= for interfaces, alongside the required netplan changes. This feature is present in systemd 248 - for netplan supported stable series we have decided to cherry-pick and backport this feature on top of current systemd. The networkd feature basically adds the following 5 ActivationPolicy modes: always-down, down, manual, up, always-up. For netplan purposes we only use 'always-down' and 'manual'. The netplan feature, hopefully landing as part of 0.103, is called 'activation-mode' and supports two values: 'manual' and 'off'. [Test Case] For the systemd part: * Bring up a VM test environment with either a dummy interface or an interface that can be safely manipulated. * Upgrade systemd to the -proposed version * For the target interface, create/modify the networkd configuration to include the ActivationPolicy= setting in [Link], for instance: [Match] Name=dummy0 [Network] Address=192.168.10.30/24 Gateway=192.168.10.1 [Link] ActivationPolicy=manual * Try all 5 combinations of ActivationPolicy values: always-down, down, manual, up, always-up - doing `sudo networkctl reload` everytime and checking if the interface behaves as expected. [Where problems could occur] The patchset modifies quite a lot of code in the networkd link handling code paths, so regressions could appear in how networkd manages links - maybe by suddenly certain interfaces not getting brought up as they were before. By code inspection, the implementation defaults to ACTIVATION_POLICY_UP as the default, equivalent to the current behavior, so this risk is small. --- [Original Description] [Old Impact] Users need to write valid configuration, especially for new features that are approved by not yet implemented, such as marking a link "optional". [Old Test case] Write a netplan configuration: network: version: 2 renderer: networkd ethernets: eth0: optional: yes dhcp4: yes And run 'netplan apply'. Netplan should write configuration for the link and not error out with a syntax error. [Old Regression potential] This has a minimal potential for regression: the new keyword was added to be supported already by consumers of netplan (users, cloud-init) so that they could start writing config with the new key and that configuration to be seen as valid by netplan before the backend is implemented. There is no functional change besides allowing for the value to exist in a netplan configuation. --- If I define an interface in netplan (even one which has no DHCP type and no addresses), it's not possible to determine if its adminStatus should be enabled (link up) or disabled (link down). I can completely exclude an interface from the netplan configuration, but I think that
[Touch-packages] [Bug 1951653] Re: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1951653 Title: can't use NM for ethernet device on 20.04 LTS because it is 'strictly unmanaged' Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Confirmed Bug description: I have tried to tell netplan to let my ethernet device be managed by NetworkManager, so that I can then configure a pppoe connection on top of this device. This fails with: # nmcli c up netplan-wan Error: Connection activation failed: No suitable device found for this connection (device lo not available because device is strictly unmanaged). # I don't know why it mentions 'lo' in that message, but the wan interface is unmanaged (as are all devices on the system, but this one is supposed to be managed): # nmcli d status | grep wan wan ethernet unmanaged -- # After much searching, I've figured out that this comes from /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf: keyfile] unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma Even though I've told netplan to use the NM renderer for this device, the configuration emitted by netplan is insufficient to override this. Using the workaround from https://askubuntu.com/questions/71159/network-manager-says-device-not- managed (sudo touch /etc/NetworkManager/conf.d/10-globally-managed- devices.conf) doesn't work, but if I set NetworkManager as the toplevel renderer in /etc/netplan, /run/NetworkManager/conf.d/10-globally-managed-devices.conf is emitted, which evidently DOES work. But I only have one device that I want rendered by NM, so I shouldn't have to declare NM at the top level of the yaml with a lot of duplication in order to get this result. I would argue that the 10-globally-managed-devices.conf should not be there at all. But if it is going to be, then netplan needs to consistently override it whenever there is any use of the NetworkManager backend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1951653/+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 1965008] Re: 'Software & Updates' crashes on tab 'Additional drivers'
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965008 Title: 'Software & Updates' crashes on tab 'Additional drivers' Status in software-properties package in Ubuntu: New Bug description: Crash did not occur a couple of days ago. 'sudo ubuntu-drivers list' has no problems listing the drivers. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.19 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 21:04:29 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-02-26 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=4 Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=4'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965008/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
thanks, the journal has some error, did you edit the .service to add the -d to the execstart as request? wpa doesn't seem to be in debug mode on that log -- 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/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in network-manager package in Ubuntu: Incomplete Bug description: WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1962541/+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 1964930] Re: Failed to start flatpak document portal service.
Thanks for reporting it upstream! ** Package changed: libxml2 (Ubuntu) => xdg-desktop-portal (Ubuntu) ** Changed in: xdg-desktop-portal (Ubuntu) Importance: Undecided => High ** Changed in: xdg-desktop-portal (Ubuntu) Status: New => Triaged ** Bug watch added: github.com/flatpak/xdg-desktop-portal/issues #728 https://github.com/flatpak/xdg-desktop-portal/issues/728 ** Changed in: libxml2 Status: Fix Released => Unknown ** Changed in: libxml2 Remote watch: github.com/flatpak/xdg-desktop-portal-gtk/issues #107 => github.com/flatpak/xdg-desktop-portal/issues #728 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1964930 Title: Failed to start flatpak document portal service. Status in libxml2: Unknown Status in xdg-desktop-portal package in Ubuntu: Triaged Bug description: Bug desciption: when launching the Calendar app (flatpak version) my system freezes for 2/3 sec, then re-become responsive, then the calendar app launcher like 10 sec after. All my flatpak apps boot a lot slower than usual. This bug happened with the recent update to libxml2 (one or two days ago ?). This is not the first time it happened. See: https://github.com/flatpak/xdg-desktop-portal-gtk/issues/107#issuecomment-454653039 I don't know where to report this, if this is relates to ubuntu or to the flatpak project. Thanks for looking into this ! Description: Ubuntu 21.10 Release: 21.10 libxml2: Installed: 2.9.12+dfsg-4ubuntu0.1 Candidate: 2.9.12+dfsg-4ubuntu0.1 Version table: *** 2.9.12+dfsg-4ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-security/main amd64 Packages 100 /var/lib/dpkg/status 2.9.12+dfsg-4 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages flatpak: Installed: 1.10.2-3ubuntu0.1 Candidate: 1.10.2-3ubuntu0.1 Version table: *** 1.10.2-3ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu impish-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-security/universe amd64 Packages 100 /var/lib/dpkg/status 1.10.2-3 500 500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages systemd: Installed: 248.3-1ubuntu8.2 Candidate: 248.3-1ubuntu8.2 Version table: *** 248.3-1ubuntu8.2 500 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-security/main amd64 Packages 100 /var/lib/dpkg/status 248.3-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages journalctl -e: mars 15 11:25:09 mathieu-ThinkPad systemd[3226]: app-gnome-gufw-20889.scope: Deactivated successfully. mars 15 11:25:13 mathieu-ThinkPad systemd[1]: systemd-timedated.service: Deactivated successfully. mars 15 11:25:13 mathieu-ThinkPad dbus-daemon[6461]: [session uid=1000 pid=6461] Activating via systemd: service name='org.freedesktop.port> mars 15 11:25:13 mathieu-ThinkPad systemd[3226]: Starting flatpak document portal service... mars 15 11:25:14 mathieu-ThinkPad xdg-document-portal[21187]: error: Failed to load db from '/home/mathieu/.local/share/flatpak/db/document> mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: xdg-document-portal.service: Main process exited, code=exited, status=2/INVALIDARGUMENT mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: xdg-document-portal.service: Failed with result 'exit-code'. mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: Failed to start flatpak document portal service. sudo dmesg: [ 2380.432314] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2380.445853] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2380.449934] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2513.367108] gnome-calendar[9096]: segfault at 40016 ip 7f8e926037a0 sp 7ffe96506ca8 error 4 in libgobject-2.0.so.0.7000.4[7f8e925db000+31000] [ 2513.367127] Code: ff fc 03 00 00 77 33 48 c1 ef 02 48 8d 05 b8 4b 02 00 48 8b 3c f8 48 81 fe fc 03 00 00 76 28 48 83 e6 fc 31 c0 48 85 ff 74 33 47 16 04 74 05 48 85 f6 75 2d 31 c0 c3 66 90 48 83 e7 fc 48 81 [ 2739.248107] [UFW BLOCK] IN=wlp3s0 OUT= MAC=a8:6d:aa:ef:af:b5:be:0d:fd:89:d3:3b:08:00 SRC=142.250.200.129 DST=192.168.43.18 LEN=40 TOS=0x00 PREC=0x00 TTL=116 ID=0 DF PROTO=TCP SPT=443 DPT=56418 WINDOW=0 RES=0x00 RST URGP=0 [ 4484.828195] gnome-calendar[20663]: segfault at 40016 ip 7f4c418207a0 sp 7ffc815aff58 error 4 in libgobject-2.0.so.0.7000.4[7f4c417f8000+31000] [ 4484.828209] Code: ff fc 03 00 00 77 33 48 c1 ef 02 48 8d 05 b8 4b 02 00 48 8b 3c f8 48
[Touch-packages] [Bug 1965141] [NEW] openssl: package the new bugfix release 3.0.2
Public bug reported: The latest bugfix release of the 3.0 branch is out, we should package it for Jammy. In the preliminary packaging I've done the test suite fails, i'm trying to track down the cause ATM. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: fr-2110 ** Tags added: fr-2110 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1965141 Title: openssl: package the new bugfix release 3.0.2 Status in openssl package in Ubuntu: New Bug description: The latest bugfix release of the 3.0 branch is out, we should package it for Jammy. In the preliminary packaging I've done the test suite fails, i'm trying to track down the cause ATM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1965141/+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 1965138] [NEW] Desktop application should check for service available information before listing it
Public bug reported: Currently, it seems that software-properties is incorrectly assuming that both ESM and Livepatch services can be enabled in a Jammy machine. Those services are not yet available in Jammy and we are attaching an image showing that the Desktop message is that we had an error enabling then and that the user should try again. It seems that software-proporties source `/var/lib/ubuntu- advantage/status.json` and assumes the services is available if it appears on the services list and the `entitled` field has the `yes` value. However, it is perfectly possible for a service to be entitled to an user, but not available in the user's machine. We are now suggesting that software-properties also looks at the `available` field in the services json output to make that assumption, this will probably solve the issue we are seeing on Jammy. Another approach would be using the output of `ua status --format json` directly. However, this command will make a request to the contract's server if the user is unattached and maybe it is not wise to use it in that context. However, the output of that command only show services that are available, so we would not need to apply that extra available filter to it. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Attachment added: "jammy-desktop-error.png" https://bugs.launchpad.net/bugs/1965138/+attachment/5569662/+files/jammy-desktop-error.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1965138 Title: Desktop application should check for service available information before listing it Status in software-properties package in Ubuntu: New Bug description: Currently, it seems that software-properties is incorrectly assuming that both ESM and Livepatch services can be enabled in a Jammy machine. Those services are not yet available in Jammy and we are attaching an image showing that the Desktop message is that we had an error enabling then and that the user should try again. It seems that software-proporties source `/var/lib/ubuntu- advantage/status.json` and assumes the services is available if it appears on the services list and the `entitled` field has the `yes` value. However, it is perfectly possible for a service to be entitled to an user, but not available in the user's machine. We are now suggesting that software-properties also looks at the `available` field in the services json output to make that assumption, this will probably solve the issue we are seeing on Jammy. Another approach would be using the output of `ua status --format json` directly. However, this command will make a request to the contract's server if the user is unattached and maybe it is not wise to use it in that context. However, the output of that command only show services that are available, so we would not need to apply that extra available filter to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965138/+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 1618522] Re: netplan does not generates .network files just for ethernet
Moving it over to the netplan.io project, as nplan is deprecated. I think we actually have an upstream way of matching Type=ether nowadays (as of systemd v245+), so we should reconsider implementing a fix for this. https://github.com/systemd/systemd/commit/ef62949a23a2d6dc722659cc527f6e0006135dc9 ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu) Status: New => Triaged ** Changed in: netplan.io (Ubuntu) Importance: Undecided => Medium ** Changed in: nplan (Ubuntu) Status: Triaged => Invalid ** Tags added: rls-jj-incoming -- 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/1618522 Title: netplan does not generates .network files just for ethernet Status in netplan.io package in Ubuntu: Triaged Status in nplan package in Ubuntu: Invalid Status in systemd package in Ubuntu: Won't Fix Bug description: On my pi3 I have an image with the ubuntu-core snap rev 354 and I get the following netplan configuration file after the first boot: ubuntu@localhost:~$ cat /etc/netplan/00-initial-config.yaml network: version: 2 ethernets: all: match: name: "*" dhcp4: true This generates the following .networkd file ubuntu@localhost:~$ cat /run/systemd/network/10-netplan-all.network [Match] Name=* [Network] DHCP=ipv4 If I look now at the output of networkctl I see it also tries to manage my mlan0 device which is a WiFi one and should be managed according to the netplan rule: ubuntu@localhost:~$ networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier configured 5 eth1 ether no-carrier configuring 6 eth0 ether routableconfigured 7 mlan0wlan no-carrier configuring In summary, the networkd generator inside netplan currently does not limit the generated .network file to tell networkd to only look at ethernet devices but rather tell it to control every device available on the system. Expectation: Specifying a wildcard rule in a netplan configuration file for ethernet devices should tell the configured networking system to only consider ethernet devices and nothing else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1618522/+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 1965112] Re: cupsd crashed with SIGSEGV in __strcmp_evex()
Can you also attach your /etc/cups/cupsd.conf file?
And please also post the output of the command
cupsctl
--
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/1965112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
Incomplete
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 16 11:00:00 2022
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2022-02-28 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: LENOVO 20Y5CTO1WW
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb
(%rsi),%ymm17,%k1{%k2}
PC (0x7fdde6d9698c) ok
source "(%rsi)" (0x) not located in a known VMA region (needed
readable region)!
destination "%ymm17" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
__strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
?? ()
?? ()
?? ()
__libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2,
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
Title: cupsd crashed with SIGSEGV in __strcmp_evex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
dmi.bios.date: 10/14/2021
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET29W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
dmi.product.family: ThinkPad X1 Extreme Gen 4i
dmi.product.name: 20Y5CTO1WW
dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
dmi.product.version: ThinkPad X1 Extreme Gen 4i
dmi.sys.vendor: LENOVO
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+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 1958019]
(In reply to Darin Miller from comment #563) > *Ubuntu version: > > 1) install kernel build tools: > (https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel): > > * sudo apt install libncurses-dev gawk flex bison openssl libssl-dev dkms > libelf-dev libudev-dev libpci-dev libiberty-dev autoconf git > > 2) clone the kernel from github and checkout to v5.17 branch (Rather large, > multiple GB's): > > * git clone https://github.com/torvalds/linux.git > * cd linux > * git checkout v5.17-rc4 > > 3) get the patch and install it: > > get the patch form this site and save to "linux" directory: (top right > corner "series" button) and use the following "git am ..." line to apply the > patch: > https://patchwork.kernel.org/project/linux-acpi/patch/20220121172431.6876-4- > sbind...@opensource.cirrus.com/ > > * git am Support-Spi-in-i2c-multi-instantiate-driver.patch > > 4) load current kernel config and change configuration then run the > following scripts/config commands: > > * make olddefconfig > * ./scripts/config --enable CONFIG_SERIAL_MULTI_INSTANTIATE > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_I2C > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_SPI > * ./scripts/config --disable CONFIG_DEBUG_INFO > * ./scripts/config --set-str CONFIG_SYSTEM_TRUSTED_KEYS "" > * ./scripts/config --set-str CONFIG_SYSTEM_REVOCATION_KEYS "" > > 6) build the kernel > > * make -j 16 > > 7) install the kernel > > * sudo make module_install > * sudo make install Hi guys, This is my first time compiling a kernel (Legion 7 16ACHg6/Ubuntu 20.04). I followed these steps (checked out the v5.17-rc8 branch on git) but at the end I am getting this error at the last step, just before running sudo make install: arch/x86/Makefile:154: CONFIG_X86_X32 enabled but no binutils support sh ./arch/x86/boot/install.sh 5.17.0-rc8+ \ arch/x86/boot/bzImage System.map "/boot" *** Missing file: arch/x86/boot/bzImage *** You need to run "make" before "make install". make: *** [arch/x86/Makefile:278: install] Error 1 Any help would be appreciated -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6
[Touch-packages] [Bug 1965121] Re: "archive.ubuntu.com" was missing in "/etc/apt/sources.list"
Thanks for your bug report. I am reassigning this to the installer, but it seems more likely that this is a result of user error, given that there have not been any relevant changes in focal's installer. For user support, please use askubuntu, discourse, the ubuntu-user mailing lists, or the #ubuntu IRC channel on Libera. If you believe this to be an installer bug, to collect additional data for the bug report, run `apport-collect 1965121` in a terminal and follow the instructions. This will provide us the installer log. Also please attach the incomplete sources.list that was supposedly generated by the installer. ** Package changed: apt (Ubuntu) => ubiquity (Ubuntu) ** Changed in: ubiquity (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/1965121 Title: "archive.ubuntu.com" was missing in "/etc/apt/sources.list" Status in ubiquity package in Ubuntu: Incomplete Bug description: Right after clean install, "archive.ubuntu.com" was missing in "/etc/apt/sources.list" as summary. So, apt checked too small amount of servers for "apt update" or "apt install", and all the fundamental and basic dev packages like libgtk-dev or gnome-builder were not available to download. Platform : Ubuntu 20.04.4 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.6 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 20:18:20 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965121/+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 1897932] Re: systemd-repart not packaged
This was enabled in Debian's systemd v250.1-2 https://salsa.debian.org/systemd-team/systemd/-/commit/4a93ec2f56969e11c73ef346a342e7e552faae75 We're shipping the more stable systemd v249 in Ubuntu Jammy LTS, and are already post feature freeze, so we cannot enable new features anymore. This will most probably land in Ubuntu 22.10 once we merge systemd v250+. ** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- 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/1897932 Title: systemd-repart not packaged Status in systemd package in Ubuntu: Triaged Status in systemd package in Debian: Fix Released Bug description: systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? I'd like to use it in our new raspberry pi images where we don't have cloud-init installed. We're already using systemd-growfs, but we are missing the nice partition resizing part (so are using cloud- initramfs-growroot). Could you please consider enabling it? In another binary package - so it can have extra deps - would be just fine by me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+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 1948882] Re: PulseEffects does not properly initialize on startup
An update: I've noticed that my PE had the button "Global Bypass" occasionally activated (somehow without my consent), and after unpressing it the entire chain now works again. But the initial bug is unfortunately there, that is PE does not get activated on sturtup properly. So in 22.04 devel, the bug is still there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1948882 Title: PulseEffects does not properly initialize on startup Status in d-conf package in Ubuntu: Confirmed Status in pulseeffects package in Ubuntu: New Bug description: In KUbuntu 21.10, PulseEffects no longer initializes its effects chain on startup. I usually use only Equalizer, so when I log into KDE, this equalizer does not get activated. To ativate it I need (i) start PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This is rarher annoying sequence that I have to repeat each time I login. Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just worked immediately after logging in, without any additional actions. I would expect the same behaviour in 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseeffects 4.8.4-1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 27 02:56:47 2021 InstallationDate: Installed on 2017-04-03 (1667 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: pulseeffects UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1948882/+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 1962093] Re: network-manager can't connect to pppoe since version 1.35.90
No,I can't. I has no account on the gitlab. -- 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/1962093 Title: network-manager can't connect to pppoe since version 1.35.90 Status in network-manager package in Ubuntu: New Bug description: System:kubuntu 22.04 I create a Dsl connection with network-manager and it works ideal before I upgrading the network-manager from 1.35.8X to the higher. Now I can't connect to the Dsl, the network-manager reports errors. I found the messages in the syslogs as this: Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3773] ppp-manager: starting PPP connection Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3788] ppp-manager: pppd started with pid 1897 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server kernel: [ 184.286354] r8169 :04:01.0 enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 'serial connection' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 'establish' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.5519] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10) Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface naming scheme 'v249'. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials from NetworkManager Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 'network' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 'running' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8762] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8767] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8773] device (enp4s1): could not take control of link 10: the device already has ifindex 2 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8774] device (enp4s1): state change: config
[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup
OK, in devel 22.04 the sound restored after an update, though PE does not actually perform any transformation from the chain... I just hope that after all it will be fixed in the final release, and will work well like it worked in 20.04... If not it seems we have to use the flatpak version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1948882 Title: PulseEffects does not properly initialize on startup Status in d-conf package in Ubuntu: Confirmed Status in pulseeffects package in Ubuntu: New Bug description: In KUbuntu 21.10, PulseEffects no longer initializes its effects chain on startup. I usually use only Equalizer, so when I log into KDE, this equalizer does not get activated. To ativate it I need (i) start PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This is rarher annoying sequence that I have to repeat each time I login. Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just worked immediately after logging in, without any additional actions. I would expect the same behaviour in 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseeffects 4.8.4-1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 27 02:56:47 2021 InstallationDate: Installed on 2017-04-03 (1667 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: pulseeffects UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1948882/+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 1937019] Re: FIDO2 tokens not supported on this build
This has been enabled in Debian's systemd v250 via https://salsa.debian.org/systemd- team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8 We're sticking with the more stable systemd v249 for Ubuntu Jammy LTS and we're already post feature freeze, so we cannot enable those new features (FIDO + TPM2 support). This change will most probably land in Ubuntu 22.10 once we merge systemd v250+. ** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- 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/1937019 Title: FIDO2 tokens not supported on this build Status in systemd package in Ubuntu: Triaged Status in systemd package in Debian: Fix Released Bug description: I'm trying to test systemd-cryptenroll with FIDO2 keys in the new systemd version 248 on impish. Running "systemd-cryptenroll --fido2-device=list" results in the message: FIDO2 tokens not supported on this build. Would it be possible to build systemd with FIDO support in time for the impish release? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937019/+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 1965121] [NEW] "archive.ubuntu.com" was missing in "/etc/apt/sources.list"
Public bug reported: Right after clean install, "archive.ubuntu.com" was missing in "/etc/apt/sources.list" as summary. So, apt checked too small amount of servers for "apt update" or "apt install", and all the fundamental and basic dev packages like libgtk-dev or gnome-builder were not available to download. Platform : Ubuntu 20.04.4 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.6 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 20:18:20 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- 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/1965121 Title: "archive.ubuntu.com" was missing in "/etc/apt/sources.list" Status in apt package in Ubuntu: New Bug description: Right after clean install, "archive.ubuntu.com" was missing in "/etc/apt/sources.list" as summary. So, apt checked too small amount of servers for "apt update" or "apt install", and all the fundamental and basic dev packages like libgtk-dev or gnome-builder were not available to download. Platform : Ubuntu 20.04.4 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.6 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 20:18:20 2022 InstallationDate: Installed on 2022-03-16 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) 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/1965121/+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 1964494] Re: Setting DuplicateAddressDetection=none doesn't disable DAD for link-local IPs
Thank you for reporting this. I've forwarded it to the upstream developers, as I think at very least this new behavior should be documented in https://systemd.network/systemd.network.html#DuplicateAddressDetection= https://github.com/systemd/systemd/issues/22763 ** Bug watch added: github.com/systemd/systemd/issues #22763 https://github.com/systemd/systemd/issues/22763 ** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium ** Also affects: systemd via https://github.com/systemd/systemd/issues/22763 Importance: Unknown Status: Unknown -- 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/1964494 Title: Setting DuplicateAddressDetection=none doesn't disable DAD for link- local IPs Status in systemd: Unknown Status in systemd package in Ubuntu: Triaged Bug description: A customer reported network disconnections on their storage servers when running 'netplan apply'. The culprit was that they have link-local addresses configured and the Duplicate Address Detection (DAD) mechanism was delaying the interfaces from coming back up. As a workaround we tried to disable DAD for the interfaces but that's not working in Ubuntu 22.04: I've noticed that setting DuplicateAddressDetection=none for an interface with a link-local address (e.g., 169.254.*) via a .network file added to /etc/systemd/network/ doesn't really disable Duplicate Address Detection. OS and package versions: - Description: Ubuntu Jammy Jellyfish (development branch). Release: 22.04 - systemd 249.5-2ubuntu4 Reproducer: --- 1- Set up Ubuntu 22.04 VM 2- Increase systemlog level: mkdir -p /etc/systemd/system/systemd-networkd.service.d/ cat > /etc/systemd/system/systemd-networkd.service.d/10-debug.conf
[Touch-packages] [Bug 1965116] [NEW] Desktop lockup with because Wayland compositor not fast enough
Public bug reported: I use Ubuntu 21.10 with Wayland and nvidia drivers. Sometimes, when working, the desktop freezes. Over ssh, I can see in the system logs many of those messages: > gnome-shell[5615]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! dmesg doesn't show any problems. Xwayland has a very high CPU usage. Killing Xwayland didn't help. When I then restart gdm, logging in either works again, or at least gdm allows a graceful reboot. ** Affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1965116 Title: Desktop lockup with because Wayland compositor not fast enough Status in wayland package in Ubuntu: New Bug description: I use Ubuntu 21.10 with Wayland and nvidia drivers. Sometimes, when working, the desktop freezes. Over ssh, I can see in the system logs many of those messages: > gnome-shell[5615]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! dmesg doesn't show any problems. Xwayland has a very high CPU usage. Killing Xwayland didn't help. When I then restart gdm, logging in either works again, or at least gdm allows a graceful reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1965116/+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 1965112] Re: cupsd crashed with SIGSEGV in __strcmp_evex()
Could you run the following commands:
driverless
driverless --std-ipp-uris
lpstat -v
and post the output here.
On which print queue are you printing?
Are you running cups-browsed?
Then switch CUPS into debug mode:
cupsctl --debug-logging
Print a job as you did when the crash happened. When it fails again,
take the /var/log/cups/error_log file and attach it to this bug report.
DO NOT compress or package it.
Could you also tell me how you printed the job? Which application? GTK
print dialog? Any other print dialog?
** Changed in: cups (Ubuntu)
Status: New => Incomplete
--
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/1965112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
Incomplete
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 16 11:00:00 2022
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2022-02-28 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: LENOVO 20Y5CTO1WW
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb
(%rsi),%ymm17,%k1{%k2}
PC (0x7fdde6d9698c) ok
source "(%rsi)" (0x) not located in a known VMA region (needed
readable region)!
destination "%ymm17" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
__strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
?? ()
?? ()
?? ()
__libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2,
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
Title: cupsd crashed with SIGSEGV in __strcmp_evex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
dmi.bios.date: 10/14/2021
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET29W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
dmi.product.family: ThinkPad X1 Extreme Gen 4i
dmi.product.name: 20Y5CTO1WW
dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
dmi.product.version: ThinkPad X1 Extreme Gen 4i
dmi.sys.vendor: LENOVO
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+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 1965112] Re: cupsd crashed with SIGSEGV in __strcmp_evex()
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1965112
Title:
cupsd crashed with SIGSEGV in __strcmp_evex()
Status in cups package in Ubuntu:
New
Bug description:
trying to print with jammy 20220316, to a network printer
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 16 11:00:00 2022
ExecutablePath: /usr/sbin/cupsd
InstallationDate: Installed on 2022-02-28 (15 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No
destinations added.
MachineType: LENOVO 20Y5CTO1WW
Papersize: a4
ProcAttrCurrent: /usr/sbin/cupsd (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic
root=UUID=229d75cc-2aa3-4f8f-b5bd-d310f6218a3f ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
Segfault happened at: 0x7fdde6d9698c <__strcmp_evex+44>: vpcmpeqb
(%rsi),%ymm17,%k1{%k2}
PC (0x7fdde6d9698c) ok
source "(%rsi)" (0x) not located in a known VMA region (needed
readable region)!
destination "%ymm17" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cups
StacktraceTop:
__strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:139
?? ()
?? ()
?? ()
__libc_start_call_main (main=main@entry=0x55ea813993a0, argc=argc@entry=2,
argv=argv@entry=0x7fffb71a6eb8) at ../sysdeps/nptl/libc_start_call_main.h:58
Title: cupsd crashed with SIGSEGV in __strcmp_evex()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
dmi.bios.date: 10/14/2021
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET29W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.11
dmi.modalias:
dmi:bvnLENOVO:bvrN40ET29W(1.11):bd10/14/2021:br1.11:efr1.11:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i:
dmi.product.family: ThinkPad X1 Extreme Gen 4i
dmi.product.name: 20Y5CTO1WW
dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i
dmi.product.version: ThinkPad X1 Extreme Gen 4i
dmi.sys.vendor: LENOVO
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1965112/+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 1929345] Re: Pressing calculator key generates infinitely many key-press key-release events
A fix for this has been landed upstream (v250) for HP Omen 15 and another fix for Omen 17: https://github.com/systemd/systemd/commit/6f2353a2ce731afc8622a3d44679abc38105cded https://github.com/systemd/systemd/commit/70920214b6a1c1825a2724793497e6be2ba3c0fc It might be worth backporting those into Ubuntu. ** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- 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/1929345 Title: Pressing calculator key generates infinitely many key-press key- release events Status in systemd package in Ubuntu: Triaged Bug description: Full description is posted in this AskUbuntu question: https://askubuntu.com/q/1336575/625814 I've got a new notebook HP Omen 15, manufactured in 2020. I has Calculator key, this key is actual normal media key. Pressing on it launches calculator only once, after the OS is booted. No reaction for other presses. If I run xev and press Calculator I see infinitely many messages about pressing and releasing XF86Calculator key: ... KeyRelease event, serial 42, synthetic NO, window 0x3e1, root 0x29e, subw 0x0, time 52918, (151,-96), root:(151,806), state 0x14, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 42, synthetic NO, window 0x3e1, root 0x29e, subw 0x0, time 52918, (151,-96), root:(151,806), state 0x14, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 42, synthetic NO, window 0x3e1, root 0x29e, subw 0x0, time 52958, (151,-96), root:(151,806), state 0x14, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 42, synthetic NO, window 0x3e1, root 0x29e, subw 0x0, time 52958, (151,-96), root:(151,806), state 0x14, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 42, synthetic NO, window 0x3e1, root 0x29e, subw 0x0, time 52999, (151,-96), root:(151,806), state 0x14, keycode 148 (keysym 0x1008ff1d, XF86Calculator), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ... Then I press Ctrl-C to stop this stream. This happens only once after the system is booted, next runs of xev don't show any events after pressing this key. If I run showkey, it always shows scan codes and key codes for that key: $ sudo showkey -s kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... 0x9c 0xe0 0x21 0x1d ^Ccaught signal 2, cleaning up... 0xe0 0x21 $ sudo showkey -k kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 28 release keycode 140 press keycode 29 press ^Ccaught signal 2, cleaning up... Debugging with evtest shows that this key doesn't generate any events, while some other keys do: sudo evtest No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: Power Button /dev/input/event1: Lid Switch /dev/input/event2: Power Button /dev/input/event3: AT Translated Set 2 keyboard /dev/input/event4: Video Bus /dev/input/event5: HP WMI hotkeys /dev/input/event6: HDA NVidia HDMI/DP,pcm=3 /dev/input/event7: SONiX USB Keyboard /dev/input/event8: SONiX USB Keyboard Consumer Control /dev/input/event9: SONiX USB Keyboard System Control /dev/input/event10: PixArt Dell MS116 USB Optical Mouse /dev/input/event11: HDA NVidia HDMI/DP,pcm=7 /dev/input/event12: HDA NVidia HDMI/DP,pcm=8 /dev/input/event13: HDA NVidia HDMI/DP,pcm=9 /dev/input/event14: HDA NVidia HDMI/DP,pcm=10 /dev/input/event15: HDA NVidia HDMI/DP,pcm=11 /dev/input/event16: SYNA32A5:00 06CB:CE17 Mouse /dev/input/event17: SYNA32A5:00 06CB:CE17 Touchpad /dev/input/event18: HD-Audio Generic Mic /dev/input/event19: HD-Audio Generic Headphone /dev/input/event20: HP Wide Vision HD Camera: HP Wi /dev/input/event21: WI-XB400 (AVRCP) Select the device event number [0-21]: 5 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0 Input device name: "HP WMI hotkeys" Supported events: Event type 0
[Touch-packages] [Bug 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.
** Attachment added: "syslog(success)" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+attachment/5569560/+files/syslog.7z -- 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/1961859 Title: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI. Status in modemmanager package in Ubuntu: Incomplete Bug description: 1. We use sourcecode to install ModemManger1.16.6 2. Ubuntu can not enter UI. 3. We capture log and picture and add these on the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+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 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.
** Attachment added: "syslog(Failed)" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+attachment/5569534/+files/syslog -- 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/1961859 Title: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI. Status in modemmanager package in Ubuntu: Incomplete Bug description: 1. We use sourcecode to install ModemManger1.16.6 2. Ubuntu can not enter UI. 3. We capture log and picture and add these on the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+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 1958284] Re: shutdown hangs at "Waiting for process: ..." for 90s, ignoring DefaultTimeoutStopSec
It has recently been picked up by Foundations, and we should have the capacity to start working on this next week. -- 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/1958284 Title: shutdown hangs at "Waiting for process: ..." for 90s, ignoring DefaultTimeoutStopSec Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Focal: Confirmed Bug description: With systemd v245 as shipped with 20.04, the shutdown sequence does not use the value of `DefaultTimeoutStopSec` to wait for remaining processes, it instead uses the compiled in default of 90s. This is most visible with services that use `KillMode=process` (docker, k8s, k3s, etc...), especially if the remaining processes do not handle `SIGTERM` or choose to ignore it. For example: ``` [ OK ] Finished Reboot. [ OK ] Reached target Reboot. [ 243.652848 ] systemd-shutdown[1]: Waiting for process: containerd-shim, containerd-shim, containerd-shim, fluent-bit --- hangs here for 90s even if DefaultTimeoutStopSec is set to a lower value --- ``` The bug has been fixed upstream here: https://github.com/systemd/systemd/commit/7d9eea2bd3d4f83668c7a78754d201b22 Marc was kind enough to package the patch for 20.04 so I could test it (https://launchpad.net/~mdeslaur/+archive/ubuntu/testing/+sourcepub/13210617/+listing- archive-extra) and with that package, I can confirm that it indeed fixes the issue. Here's a few github issues I stumbled upon while trying to debug this, along with a short writeup of the workaround I ended up using: - https://github.com/moby/moby/issues/41831 - https://github.com/k3s-io/k3s/issues/2400 - https://github.com/systemd/systemd/issues/16991 - https://raby.sh/debugging-90s-hangs-during-shutdown-on-ubuntu-2004.html Of course, it would be much better if all the processes would properly handle `SIGTERM`, but having a way to enforce a maximum wait time at shutdown is a decent workaround. Given that the patch is relatively simple, would it be possible to add it the package for 20.04? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1958284/+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 1964930] Re: Failed to start flatpak document portal service.
I found the culprit, being a 0 byte "documents" file in the flatpak database. I filed an issue in the flatpak github. https://github.com/flatpak/xdg-desktop- portal/issues/369#issuecomment-1068915444 I still don't know if this relates to libxml2, and if it is worth being investigated how that 0 byte file was created. Thanks for reading. ** Bug watch added: github.com/flatpak/xdg-desktop-portal/issues #369 https://github.com/flatpak/xdg-desktop-portal/issues/369 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1964930 Title: Failed to start flatpak document portal service. Status in libxml2: Fix Released Status in libxml2 package in Ubuntu: New Bug description: Bug desciption: when launching the Calendar app (flatpak version) my system freezes for 2/3 sec, then re-become responsive, then the calendar app launcher like 10 sec after. All my flatpak apps boot a lot slower than usual. This bug happened with the recent update to libxml2 (one or two days ago ?). This is not the first time it happened. See: https://github.com/flatpak/xdg-desktop-portal-gtk/issues/107#issuecomment-454653039 I don't know where to report this, if this is relates to ubuntu or to the flatpak project. Thanks for looking into this ! Description: Ubuntu 21.10 Release: 21.10 libxml2: Installed: 2.9.12+dfsg-4ubuntu0.1 Candidate: 2.9.12+dfsg-4ubuntu0.1 Version table: *** 2.9.12+dfsg-4ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-security/main amd64 Packages 100 /var/lib/dpkg/status 2.9.12+dfsg-4 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages flatpak: Installed: 1.10.2-3ubuntu0.1 Candidate: 1.10.2-3ubuntu0.1 Version table: *** 1.10.2-3ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu impish-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-security/universe amd64 Packages 100 /var/lib/dpkg/status 1.10.2-3 500 500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages systemd: Installed: 248.3-1ubuntu8.2 Candidate: 248.3-1ubuntu8.2 Version table: *** 248.3-1ubuntu8.2 500 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-security/main amd64 Packages 100 /var/lib/dpkg/status 248.3-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages journalctl -e: mars 15 11:25:09 mathieu-ThinkPad systemd[3226]: app-gnome-gufw-20889.scope: Deactivated successfully. mars 15 11:25:13 mathieu-ThinkPad systemd[1]: systemd-timedated.service: Deactivated successfully. mars 15 11:25:13 mathieu-ThinkPad dbus-daemon[6461]: [session uid=1000 pid=6461] Activating via systemd: service name='org.freedesktop.port> mars 15 11:25:13 mathieu-ThinkPad systemd[3226]: Starting flatpak document portal service... mars 15 11:25:14 mathieu-ThinkPad xdg-document-portal[21187]: error: Failed to load db from '/home/mathieu/.local/share/flatpak/db/document> mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: xdg-document-portal.service: Main process exited, code=exited, status=2/INVALIDARGUMENT mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: xdg-document-portal.service: Failed with result 'exit-code'. mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: Failed to start flatpak document portal service. sudo dmesg: [ 2380.432314] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2380.445853] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2380.449934] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2513.367108] gnome-calendar[9096]: segfault at 40016 ip 7f8e926037a0 sp 7ffe96506ca8 error 4 in libgobject-2.0.so.0.7000.4[7f8e925db000+31000] [ 2513.367127] Code: ff fc 03 00 00 77 33 48 c1 ef 02 48 8d 05 b8 4b 02 00 48 8b 3c f8 48 81 fe fc 03 00 00 76 28 48 83 e6 fc 31 c0 48 85 ff 74 33 47 16 04 74 05 48 85 f6 75 2d 31 c0 c3 66 90 48 83 e7 fc 48 81 [ 2739.248107] [UFW BLOCK] IN=wlp3s0 OUT= MAC=a8:6d:aa:ef:af:b5:be:0d:fd:89:d3:3b:08:00 SRC=142.250.200.129 DST=192.168.43.18 LEN=40 TOS=0x00 PREC=0x00 TTL=116 ID=0 DF PROTO=TCP SPT=443 DPT=56418 WINDOW=0 RES=0x00 RST URGP=0 [ 4484.828195] gnome-calendar[20663]: segfault at 40016 ip 7f4c418207a0 sp 7ffc815aff58 error 4 in libgobject-2.0.so.0.7000.4[7f4c417f8000+31000] [ 4484.828209] Code: ff fc 03 00 00 77 33 48 c1 ef 02 48 8d 05 b8 4b 02 00 48 8b 3c f8 48 81 fe fc 03 00 00 76 28 48 83 e6 fc 31 c0 48 85 ff 74 33 47 16 04 74 05 48 85 f6 75 2d 31 c0 c3 66 90 48 83 e7 fc 48 81
[Touch-packages] [Bug 1964642] Re: Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4 but can connect to Ubuntu 20.4
sergiojd: The problem I have reported happens using Packer to create
VirtualBox .ova images of Ubuntu Server guests. As I have said,
everything works OK using the Ubuntu Server 20.04 iso (released in
2020.04), but fails with the 20.04.1, 20.04.2, 20.04.3 or 20.04.4 isos.
I would say that something has changed in Ubuntu after 20.04.
seth: During the creation of the VM, Packer uses a NAT network, so I would say
I can not ping the machine.
The VM is created OK, I can login into the machine, but as Packer can not
connect with SSH, the VM is destroyed some minutes later when Packer cancels
the build. Virtualbox defines port forwarding (127.0.0.1:) and I have tried
to connect the guest using WinSCP or Putty, but both can't connect neither.
I send attached the log file created by VirtualBox.
** Attachment added: "packer-1-2-ubuntu-20-04-4-server-2022-03-16-10-16-50.log"
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1964642/+attachment/5569531/+files/packer-1-2-ubuntu-20-04-4-server-2022-03-16-10-16-50.log
--
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/1964642
Title:
Packer virtualbox ssh can't connect to unattended Ubuntu 20.04.1/2/3/4
but can connect to Ubuntu 20.4
Status in openssh package in Ubuntu:
New
Bug description:
Two years ago I was able to create a Virtualbox Ubuntu 20.04 guest in a
Windows 10 host with Packer 1.5.6, using an unattended installation.
The Packer command was:
"boot_command": [
" ",
"autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/",
""
],
The user-data file was:
#cloud-config
autoinstall:
version: 1
identity:
realname: mclibre
hostname: ubuntu
password:
'$6$mclibre$YiuRPSZM3ZXVe4UyIqv1dvy9rUjf5/LsGCkDyaex.WN45wzVTuRmW5QLuctuicGAFZIO2M3QR8NLdtQYatKTn1'
username: mclibre
locale: es_ES.UTF-8
keyboard:
layout: es
network:
network:
version: 2
ethernets:
ens33: {dhcp4: true, dhcp-identifier: mac}
ssh:
install-server: true
late-commands:
- sed -i 's/^#*\(send dhcp-client-identifier\).*$/\1 = hardware;/'
/target/etc/dhcp/dhclient.conf
- 'sed -i "s/dhcp4: true/&\n dhcp-identifier: mac/"
/target/etc/netplan/00-installer-config.yaml'
Now, I have tried to create a Virtualbox Ubuntu 20.04.4/.3/.2/.1 guest using
packer 1.5.6 but Packer can't create the image because once the installation is
done, after rebooting the SSH server does not answer (the packer log error
says: SSH handshake err: Timeout during SSH handshake).
I have tried with the last version of Packer, Packer 1.8.0, and the result is
the same. I can create a Ubuntu Server 20.4 image but not a Ubuntu Server
20.4.1, .2, .3 or .4 image.
I can provide as much aditional information as you want.
Thanking you in advance,
Bartolome Sintes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1964642/+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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
I installed wpasupplicant_2.10-2_amd64.deb and libssl1.1_1.1.1m-1_amd64.deb from debian sid. It works. I attached the log from journalctl -b 0 with ubuntu's wpasupplicant package. ** Attachment added: "wpa_supplicant.log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1962541/+attachment/5569503/+files/wpa_supplicant.log -- 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/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working Status in network-manager package in Ubuntu: Incomplete Bug description: WPA2 enterprise can't connect PEAP ubuntu 22.04 live/installer is not working too ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.6 Uname: Linux 5.16.0-kali1-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 09:18:42 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2022-02-27T21:07:16.553410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1962541/+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 1960403] Re: Kubuntu constantly freezing on ThinkPad T510
We can do both -- close it now and keep discussing and reopen it later as required. ** Changed in: mesa (Ubuntu) Status: New => Fix Released ** No longer affects: kwin (Ubuntu) ** No longer affects: meta-kde (Ubuntu) -- 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/1960403 Title: Kubuntu constantly freezing on ThinkPad T510 Status in mesa package in Ubuntu: Fix Released Bug description: This happens either during SDDM, or on the desktop, but Kubuntu's constantly freezing up. I tried disabling the compositor, but it doesn't seem to help. Also, I removed the external monitor, but that doesn't seem to help. I've installed Lubuntu, and so far it's been fine. However, when I tried to change the SDDM theme via KDE's System Settings, the laptop locked up. I'll keep Kubuntu on it for now, but I'm gonna have to switch this to Lubuntu in the meantime. Specs: * Core i7-640M * 8GB RAM ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: kubuntu-desktop 1.416 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 05:58:18 2022 InstallationDate: Installed on 2021-08-07 (186 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: kubuntu-meta UpgradeStatus: Upgraded to jammy on 2022-02-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1960403/+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 1960403] Re: Kubuntu constantly freezing on ThinkPad T510
Reverting back to the official repo fixed it. I guess that it was fixed since I first reported this. Please keep it open just in case the issue crops up again. -- 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/1960403 Title: Kubuntu constantly freezing on ThinkPad T510 Status in kwin package in Ubuntu: New Status in mesa package in Ubuntu: New Status in meta-kde package in Ubuntu: New Bug description: This happens either during SDDM, or on the desktop, but Kubuntu's constantly freezing up. I tried disabling the compositor, but it doesn't seem to help. Also, I removed the external monitor, but that doesn't seem to help. I've installed Lubuntu, and so far it's been fine. However, when I tried to change the SDDM theme via KDE's System Settings, the laptop locked up. I'll keep Kubuntu on it for now, but I'm gonna have to switch this to Lubuntu in the meantime. Specs: * Core i7-640M * 8GB RAM ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: kubuntu-desktop 1.416 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 05:58:18 2022 InstallationDate: Installed on 2021-08-07 (186 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: kubuntu-meta UpgradeStatus: Upgraded to jammy on 2022-02-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1960403/+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 1958148] Re: mkinitramfs is too slow
This bug was fixed in the package initramfs-tools - 0.140ubuntu13 --- initramfs-tools (0.140ubuntu13) jammy; urgency=medium * Lower the compression levels for zstd and lz4 (LP: #1958148) Following the discussion on the mailing list, we have reached a conclusion to lower the default compression levels: - For lz4, the compression level is lowered to 2 from 9 - For zstd, the compression level is lowered to 1 from 19 -- Julian Andres Klode Tue, 15 Mar 2022 16:00:55 +0100 ** Changed in: initramfs-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1958148 Title: mkinitramfs is too slow Status in initramfs-tools package in Ubuntu: Fix Released Bug description: On the Nezha board creating an initrd takes more than 1 hour. The compression level -19 for zstd is unwisely chosen. Here are durations and compression results for an SiFive Unmatched board with four cores using zstd: -T0 -1 => 13.92s, 136298155 bytes -T0 -2 => 15.73s, 131717830 bytes -T0 -3 => 26.11s, 127434653 bytes -T0 -4 => 29.31s, 126924540 bytes -T0 -5 => 36.44s, 125296557 bytes -T0 -6 => 39.36s, 124781669 bytes -T0 -7 => 46.56s, 116200665 bytes -T0 -8 => 51.95s, 113172941 bytes -T0 -9 => 55.89s, 112835937 bytes -T0 -10 => 61.32s, 108326876 bytes -T0 -11 => 64.32s, 108115060 bytes -T0 -12 => 76.37s, 108016478 bytes -T0 -13 => 148.99s, 109121308 bytes -T0 -14 => 156.58s, 108908574 bytes -T0 -15 => 228.64s, 109213554 bytes -T0 -16 => 380.26s, 107260643 bytes -T0 -17 => 453.36s, 103679714 bytes -T0 -18 => 714.79s, 100402249 bytes -T0 -19 => 1046.58s, 100188713 bytes Compression level between -2 to -10 offer a good compromise between CPU time and compression results. Ideally there would be a parameter that we could pass to mkinitfs. But for as fast solution we should simply replace -19 by -9 in mkinitramfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+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 1962346] Re: Ubuntu reboots instead of powering off if a software updates exists
** Changed in: gnome-shell (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1962346 Title: Ubuntu reboots instead of powering off if a software updates exists Status in gnome-shell package in Ubuntu: New Status in packagekit package in Ubuntu: Invalid Bug description: When I want to turn off a computer, I got a checkbox "Install deferred updates" (see screenshot, I'm not sure if my back-translation is correct). If the checkbox is checked, Ubuntu box reboots instead of powering off. It is not "rebopot to install updates". It just reboots to desktop again. If I uncheck the box, it powers off normally. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 26 00:05:44 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-01-11 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962346/+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 1960403] Re: Kubuntu constantly freezing on ThinkPad T510
We would be able to at least tell if the problem is Mesa or KDE if you could test regular Ubuntu (with GNOME). -- 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/1960403 Title: Kubuntu constantly freezing on ThinkPad T510 Status in kwin package in Ubuntu: New Status in mesa package in Ubuntu: New Status in meta-kde package in Ubuntu: New Bug description: This happens either during SDDM, or on the desktop, but Kubuntu's constantly freezing up. I tried disabling the compositor, but it doesn't seem to help. Also, I removed the external monitor, but that doesn't seem to help. I've installed Lubuntu, and so far it's been fine. However, when I tried to change the SDDM theme via KDE's System Settings, the laptop locked up. I'll keep Kubuntu on it for now, but I'm gonna have to switch this to Lubuntu in the meantime. Specs: * Core i7-640M * 8GB RAM ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: kubuntu-desktop 1.416 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 05:58:18 2022 InstallationDate: Installed on 2021-08-07 (186 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: kubuntu-meta UpgradeStatus: Upgraded to jammy on 2022-02-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1960403/+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 1960403] Re: Kubuntu constantly freezing on ThinkPad T510
If llvmpipe is working, that's just because it avoids using the GPU. It's a slow workaround. If going back to Mesa version 21.3.5-1ubuntu1 from Ubuntu reintroduces freezes then I suggest that needs to be debugged by KDE/Plasma developers. ** Also affects: kwin (Ubuntu) Importance: Undecided Status: New ** Also affects: meta-kde (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: Incomplete => 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/1960403 Title: Kubuntu constantly freezing on ThinkPad T510 Status in kwin package in Ubuntu: New Status in mesa package in Ubuntu: New Status in meta-kde package in Ubuntu: New Bug description: This happens either during SDDM, or on the desktop, but Kubuntu's constantly freezing up. I tried disabling the compositor, but it doesn't seem to help. Also, I removed the external monitor, but that doesn't seem to help. I've installed Lubuntu, and so far it's been fine. However, when I tried to change the SDDM theme via KDE's System Settings, the laptop locked up. I'll keep Kubuntu on it for now, but I'm gonna have to switch this to Lubuntu in the meantime. Specs: * Core i7-640M * 8GB RAM ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: kubuntu-desktop 1.416 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 05:58:18 2022 InstallationDate: Installed on 2021-08-07 (186 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: kubuntu-meta UpgradeStatus: Upgraded to jammy on 2022-02-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1960403/+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 1960403] Re: Kubuntu constantly freezing on ThinkPad T510
It sounds like the main problem is still Mesa. The i7-640M is a "Gen5" Intel GPU apparently: https://en.wikipedia.org/wiki/List_of_Intel_graphics_processing_units#Gen5 That means Mesa should select the "i965" Mesa driver for it: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Make sure your build of Mesa provides that file. -- 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/1960403 Title: Kubuntu constantly freezing on ThinkPad T510 Status in kwin package in Ubuntu: New Status in mesa package in Ubuntu: New Status in meta-kde package in Ubuntu: New Bug description: This happens either during SDDM, or on the desktop, but Kubuntu's constantly freezing up. I tried disabling the compositor, but it doesn't seem to help. Also, I removed the external monitor, but that doesn't seem to help. I've installed Lubuntu, and so far it's been fine. However, when I tried to change the SDDM theme via KDE's System Settings, the laptop locked up. I'll keep Kubuntu on it for now, but I'm gonna have to switch this to Lubuntu in the meantime. Specs: * Core i7-640M * 8GB RAM ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: kubuntu-desktop 1.416 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 05:58:18 2022 InstallationDate: Installed on 2021-08-07 (186 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: kubuntu-meta UpgradeStatus: Upgraded to jammy on 2022-02-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1960403/+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
