[Touch-packages] [Bug 1913045] Re: Xorg freeze
Thanks for the bug report. 1. Please check that you haven't enabled any additional GNOME extensions in the 'Extensions' app. There should only be the three built-in ones. If you have more than that then try uninstalling or disabling them. 2. Next time you have to "hard reboot", please then run this command in a Terminal window: journalctl -b-1 > prevboot.txt and attach the resulting text file here. 3. Please also check for any recent crashes using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Xorg freeze + System freezes when in lockscreen ** Package changed: ubuntu => gnome-shell (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/1913045 Title: System freezes when in lockscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: My system freezes when I'm in lockscreen. This happens every few ours after I leave the computer running some low to mediocre computation tasks, no memory problems. It does not happen when I run heavy tasks. I can only hard reboot, nothing else is working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 25 11:26:10 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:2245] InstallationDate: Installed on 2020-06-02 (236 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20HD0001MZ ProcEnviron: LANGUAGE=de_CH:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=df6eb87b-cd89-4867-9c7c-de8b08bbdbcf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2020 dmi.bios.release: 1.63 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET88W (1.63 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HD0001MZ 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.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET88W(1.63):bd04/22/2020:br1.63:efr1.35:svnLENOVO:pn20HD0001MZ:pvrThinkPadT470:rvnLENOVO:rn20HD0001MZ:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HD0001MZ dmi.product.sku: LENOVO_MT_20HD_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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/gnome-shell/+bug/1913045/+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 1913217] Re: Screen going black and not responding to input
Thanks for the bug report. 1. Please check that you haven't enabled any additional GNOME extensions in the 'Extensions' app. There should only be the three built-in ones. If you have more than that then try uninstalling or disabling them. 2. Next time the freeze happens, please then run this command in a Terminal window: journalctl -b-1 > prevboot.txt and attach the resulting text file here. 3. Please also check for any recent crashes using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Summary changed: - Xorg freeze + Screen going black and not responding to input ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Package changed: ubuntu => gnome-shell (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/1913217 Title: Screen going black and not responding to input Status in gnome-shell package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expecting: (usually after opening a new application): window to open Happened instead: Screen going black. System not responding to inputs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 25 21:49:05 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-42-generic, x86_64: installed nvidia-340, 340.108, 5.8.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GT216M [GeForce GT 330M] [106b:00c7] InstallationDate: Installed on 2021-01-24 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Apple Inc. MacBookPro6,2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=22238608-1c5f-40aa-a8f4-1fded14f6b84 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 99.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvr99.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-v
[Touch-packages] [Bug 1912940] Re: Bluetooth disabled every time on startup
** Summary changed: - disabled everytime startup + Bluetooth disabled every time on startup ** Changed in: bluez (Ubuntu) Status: Incomplete => New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1912940 Title: Bluetooth disabled every time on startup Status in bluez package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: [Policy] AutoEnable=true not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Jan 24 19:49:49 2021 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: LENOVO 81CG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-051000-generic root=UUID=0281b4fb-589a-46ed-b8ee-896d3505e7bd ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: 6NCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 520-12IKB dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvr6NCN39WW:bd10/10/2019:br1.39:efr1.39:svnLENOVO:pn81CG:pvrMIIX520-12IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct32:cvrMIIX520-12IKB: dmi.product.family: MIIX 520-12IKB dmi.product.name: 81CG dmi.product.sku: LENOVO_MT_81CG_BU_idea_FM_MIIX 520-12IKB dmi.product.version: MIIX 520-12IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 3C:6A:A7:BB:B7:63 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:213889 acl:13940 sco:0 events:310 errors:0 TX bytes:40352 acl:45 sco:0 commands:249 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1912940/+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 1913366] [NEW] Persiste problema con ubuntu 18.04 no reconoce monitor ni resolución óptima
Public bug reported: Tuve que reinstalar ubuntu 18.04 ya que no pude ingresar más al sistema operativo, ya que se quedaba congelado en el inicio, no me permitía ingresar la contraseña. Al hacerlo seguía presentando el mismo problema de baja resolución, volví a tratar de solucionarlo con sudo apt install xserver-xorg-video-openchrome y nuevamente se congeló el sistema. Me vi forzado a realizar una segunda reinstalación de Ubuntu y no he vuelto a intentar porque obviamente se corre el riesgo de que se quede colgada otra vez. Así que estoy tratando de trabajar con la baja resolución 640x480 especificada en el informe. La instale un escritorio cinamon y me informa al inicio que està trabajando sin aceleración de software lo cual puede afectar el rendimiento del equipo. Esta es la situación. Gracias por el interés demostrado en mi caso. Saludos. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-64-generic i686 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: i386 CompositorRunning: None Date: Tue Jan 26 23:47:50 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] [1106:3371] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp CN896/VN896/P4M900 [Chrome 9 HC] [1565:1207] InstallationDate: Installed on 2021-01-26 (0 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: BIOSTAR Group P4M900-M7 FE ProcEnviron: LANGUAGE=es_VE:es TERM=xterm-256color PATH=(custom, no user) LANG=es_VE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=c6c9ee95-4dbf-4f30-b579-32cfe165d16e ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: P4M900-M7 FE dmi.board.vendor: BIOSTAR Group dmi.board.version: Ver:1.0 dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.chassis.version: P4M900-M7 FE dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/25/2008:svnBIOSTARGroup:pnP4M900-M7FE:pvrVer1.0:rvnBIOSTARGroup:rnP4M900-M7FE:rvrVer1.0:cvnBIOSTARGroup:ct3:cvrP4M900-M7FE: dmi.product.name: P4M900-M7 FE dmi.product.version: Ver:1.0 dmi.sys.vendor: BIOSTAR Group version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 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/1913366 Title: Persiste problema con ubuntu 18.04 no reconoce monitor ni resolución óptima Status in xorg package in Ubuntu: New Bug description: Tuve que reinstalar ubuntu 18.04 ya que no pude ingresar más al sistema operativo, ya que se quedaba congelado en el inicio, no me permitía ingresar la contraseña. Al hacerlo seguía presentando el mismo problema de baja resolución, volví a tratar de solucionarlo con sudo apt install xserver-xorg-video-openchrome y nuevamente se congeló el sistema. Me vi forzado a realizar una segunda reinstalación de Ubuntu y no he vuelto a intentar porque obviamente se corre el riesgo de que se quede colgada otra vez. Así que estoy tratando de trabajar con la baja resolución 640x480 especificada en el informe. La instale un escritorio cinamon y me informa al inicio que està trabajando sin aceleración de software lo cual puede afectar el rendimiento del equipo. Esta es la situación. Gracias por el interés demostrado en mi caso. Saludos. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-64-generic i686 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: i386 CompositorRunning: None Date: Tue Jan 26 23:47:50 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] [1106:3371] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp CN896/VN896/P4M900 [Chrome 9 HC] [1565:1207] InstallationDate: Installed on 2021-01-26 (0 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Relea
[Touch-packages] [Bug 1913229] Re: Arrow keys do not select the folder on Desktop
*** This bug is a duplicate of bug 1855711 *** https://bugs.launchpad.net/bugs/1855711 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1855711, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => gnome-shell-extension-desktop-icons (Ubuntu) ** This bug has been marked a duplicate of bug 1855711 Add keyboard navigation to desktop icons -- 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/1913229 Title: Arrow keys do not select the folder on Desktop Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: 1. Go to Desktop (Super + D). Not in the file explorer. 2. Press arrow keys to select files or folders. Expected this to happen - Arrows keys should have selected the files or folders. What actually happened - Arrow keys do not select a folder or file. I was only able to select by clicking it using mouse or touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 25 15:47:00 2021 DistUpgraded: 2020-11-11 01:14:21,825 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06c2] Subsystem: Dell Meso XT [Radeon R5 M315] [1028:06c2] InstallationDate: Installed on 2020-11-10 (76 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6710 Microdia Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3559 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=02fe3eed-961f-47d5-b146-b532ab73eb19 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-11-11 (75 days ago) dmi.bios.date: 05/13/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.9 dmi.board.name: 0PW9RW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.9:bd05/13/2016:svnDellInc.:pnVostro3559:pvr:rvnDellInc.:rn0PW9RW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 3559 dmi.product.sku: 06C2 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 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/gnome-shell-extension-desktop-icons/+bug/1913229/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Try also: load-module module-bluetooth-policy auto_switch=2 in /etc/pulse/default.pa as suggested in bug 508522. -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+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 1913339] Re: wrong path install location for groovy package
*** This bug is a duplicate of bug 1908818 ***
https://bugs.launchpad.net/bugs/1908818
** This bug has been marked a duplicate of bug 1908818
pure packaging of libnss3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1913339
Title:
wrong path install location for groovy package
Status in nss package in Ubuntu:
New
Bug description:
Description:Ubuntu 20.10
Release:20.10
libnss3:
Installé : 2:3.55-1ubuntu3
Candidat : 2:3.55-1ubuntu3
Table de version :
*** 2:3.55-1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
100 /var/lib/dpkg/status
On groovy, the `apt-file list libnss3` shows:
libnss3: /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
libnss3: /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
libnss3: /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
libnss3: /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so
libnss3: /usr/lib/x86_64-linux-gnu/libnss3.so
libnss3: /usr/lib/x86_64-linux-gnu/libnssutil3.so
libnss3: /usr/lib/x86_64-linux-gnu/libsmime3.so
libnss3: /usr/lib/x86_64-linux-gnu/libssl3.so
libnss3: /usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
libnss3: /usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
libnss3: /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
libnss3: /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
libnss3: /usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
libnss3: /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
libnss3: /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
libnss3: /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
libnss3: /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
libnss3: /usr/share/doc/libnss3/changelog.Debian.gz
libnss3: /usr/share/doc/libnss3/copyright
libnss3: /usr/share/lintian/overrides/libnss3
You can also see this at link:
https://packages.ubuntu.com/groovy/amd64/libnss3/filelist
Apparently, ${DEB_HOST_MULTIARCH} should be replaced by x86_64-linux-gnu. I
believe this is a bug in packing .deb files.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1913339/+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 1913356] [NEW] Windows flicker when resizing after update to 20.10
Public bug reported: Yesterday I updated to Ubuntu 20.10 (from 20.04 LTS) and immediately noticed an issue with windows flickering when I resize them. Here is a video demonstrating the issue: https://youtu.be/nNOoJWdDEes This did not happen in 20.04. Windows this has been noticed on include: - Software & Updates (as shown in video) - Tilix - KeePassXC Here is some information about my system: - OS: Ubuntu 20.10 x86_64 - Host: XPS 13 9370 - Kernel: 5.8.0-40-generic - Shell: bash 5.0.17 - Resolution: 1920x1080 - DE: GNOME 3.38.2 - WM: Mutter - WM Theme: Adwaita - Theme: Yaru-dark [GTK2/3] - Icons: Yaru [GTK2/3] - CPU: Intel i7-8550U (8) @ 4.000GHz - GPU: Intel UHD Graphics 620 - Memory: 6139MiB / 15725MiB Please let me know if there's any further details or diagnostics that would be useful. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Wed Jan 27 00:23:33 2021 DistUpgraded: 2021-01-25 15:06:27,142 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2018-02-01 (1090 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 7: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 7: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=04d2ce0b-b5d2-4184-93fc-428c29d5e2fd ro SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2021-01-25 (1 days ago) dmi.bios.date: 05/25/2018 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd05/25/2018:br1.4:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun Dec 16 15:22:33 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5252 vendor SHP xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages 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/1913356 Title: Windows flicker when resizing after update to 20.10 Status in xorg package in Ubuntu: New Bug description: Yesterday I updated to Ubuntu 20.10 (from 20.04 LTS) and immediately noticed an issue with windows flickering when I resize them. Here is a video demonstrating the issue: https://youtu.be/nNOoJWdDEes This did not happen in 20.04. Windows this has been noticed on include: - Software
[Touch-packages] [Bug 1304074] Re: [X550CC, Realtek ALC270, Black Headphone Out, Left] No sound at all
Hey guys. After 1 year with problems to make works headphone together with mic, I got a solution for my ASUS S46CA, I think this can works for you too. First, I try a lot of options snd-hda-intel, but only works this: options snd-hda-intel model=alc255-asus for my ALC270. But it is not enough. I needed use hdajackretask And force pin ID 0x1a to be "Headphone" pin ID 0x18 to be "Microphone" if alc255-asus don't works for you, you can try another options, like: alc269-dmic, alc271-dmic, headset-mic, alc283-headset. Don't forget to restart the machine after hdajackretask. -- 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/1304074 Title: [X550CC, Realtek ALC270, Black Headphone Out, Left] No sound at all Status in alsa-driver package in Ubuntu: Expired Bug description: I have sound from the laptop, but no sound when i use the jack. It works when running windows. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1734 F pulseaudio /dev/snd/pcmC0D0p: daniel 1734 F...m pulseaudio Date: Mon Apr 7 23:17:24 2014 InstallationDate: Installed on 2014-02-26 (40 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1734 F pulseaudio /dev/snd/pcmC0D0p: daniel 1734 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [X550CC, Realtek ALC270, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CC.217:bd10/16/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1304074/+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 1304074] Re: [X550CC, Realtek ALC270, Black Headphone Out, Left] No sound at all
Hey guys. After 1 year with problems to make works headphone together with mic, I got a solution for my ASUS S46CA, I think this can works for you too. First, I try a lot of options snd-hda-intel, but only works this: options snd-hda-intel model=alc255-asus for my ALC270. But it is not enough. I needed use hdajackretask And force pin ID 0x1a to be "Headphone" -- 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/1304074 Title: [X550CC, Realtek ALC270, Black Headphone Out, Left] No sound at all Status in alsa-driver package in Ubuntu: Expired Bug description: I have sound from the laptop, but no sound when i use the jack. It works when running windows. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1734 F pulseaudio /dev/snd/pcmC0D0p: daniel 1734 F...m pulseaudio Date: Mon Apr 7 23:17:24 2014 InstallationDate: Installed on 2014-02-26 (40 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1734 F pulseaudio /dev/snd/pcmC0D0p: daniel 1734 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [X550CC, Realtek ALC270, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CC.217:bd10/16/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1304074/+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 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
The version in the groovy debdiff will not work as 0.99.4 existed in
hirsute for some period of time, you'll want to use 0.99.3.1.
--
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/1829401
Title:
gi.repository.GLib.GError: pk-client-error-quark: could not do
untrusted question as no klass support
Status in packagekit package in Ubuntu:
Triaged
Status in packagekit source package in Eoan:
Won't Fix
Status in packagekit source package in Focal:
Confirmed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+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 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
Attached is a patch to SRU groovy.
** Patch added: "lp1829401_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+attachment/5457149/+files/lp1829401_groovy.debdiff
--
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/1829401
Title:
gi.repository.GLib.GError: pk-client-error-quark: could not do
untrusted question as no klass support
Status in packagekit package in Ubuntu:
Triaged
Status in packagekit source package in Eoan:
Won't Fix
Status in packagekit source package in Focal:
Confirmed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+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 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
Attached is a patch to SRU focal.
** Patch added: "lp1829401_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+attachment/5457147/+files/lp1829401_focal.debdiff
--
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/1829401
Title:
gi.repository.GLib.GError: pk-client-error-quark: could not do
untrusted question as no klass support
Status in packagekit package in Ubuntu:
Triaged
Status in packagekit source package in Eoan:
Won't Fix
Status in packagekit source package in Focal:
Confirmed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+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 1891798] Re: Backport fix from sudo 1.8.22 to fix "stair-stepped output" bug
** Summary changed: - Update sudo to 1.8.22 to fix "stair-stepped output" bug + Backport fix from sudo 1.8.22 to fix "stair-stepped output" bug ** Description changed: - sudo 1.8.20 introduced a bug in commit 44dc15d02dc0b34bf03bc971ba08d3a761c3a031 - that is fixed by sudo 1.8.22 in commit 3b88cdfcd8d1a39eabbb5b7d0c8fe8f035d7a264 + sudo 1.8.20 introduced a bug in commit + 44dc15d02dc0b34bf03bc971ba08d3a761c3a031 + that is fixed by sudo 1.8.22 in commit + 3b88cdfcd8d1a39eabbb5b7d0c8fe8f035d7a264 When the "use_pty" option is enabled, "stair-stepped output" occurs if sudo is piped to another command. Example output attached in a text file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sudo 1.8.21p2-3ubuntu1.2 Uname: Linux 5.4.50+ x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 16 12:29:23 2020 InstallationDate: Installed on 2014-05-10 (2290 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: sudo UpgradeStatus: Upgraded to bionic on 2018-11-24 (630 days ago) modified.conffile..etc.pam.d.sudo: [inaccessible: [Errno 13] Permission denied: '/etc/pam.d/sudo'] modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers'] modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README'] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1891798 Title: Backport fix from sudo 1.8.22 to fix "stair-stepped output" bug Status in sudo package in Ubuntu: New Bug description: sudo 1.8.20 introduced a bug in commit 44dc15d02dc0b34bf03bc971ba08d3a761c3a031 that is fixed by sudo 1.8.22 in commit 3b88cdfcd8d1a39eabbb5b7d0c8fe8f035d7a264 When the "use_pty" option is enabled, "stair-stepped output" occurs if sudo is piped to another command. Example output attached in a text file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sudo 1.8.21p2-3ubuntu1.2 Uname: Linux 5.4.50+ x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 16 12:29:23 2020 InstallationDate: Installed on 2014-05-10 (2290 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: sudo UpgradeStatus: Upgraded to bionic on 2018-11-24 (630 days ago) modified.conffile..etc.pam.d.sudo: [inaccessible: [Errno 13] Permission denied: '/etc/pam.d/sudo'] modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers'] modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1891798/+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 1908473] Update Released
The verification of the Stable Release Update for librelp has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1908473
Title:
rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which
leads to file descriptor leak
Status in librelp package in Ubuntu:
Fix Released
Status in rsyslog package in Ubuntu:
Fix Released
Status in librelp source package in Focal:
Fix Committed
Status in rsyslog source package in Focal:
Won't Fix
Status in librelp source package in Groovy:
Fix Released
Status in rsyslog source package in Groovy:
Fix Released
Status in librelp source package in Hirsute:
Fix Released
Status in rsyslog source package in Hirsute:
Fix Released
Bug description:
[Impact]
In recent versions of rsyslog and librelp, the imrelp module leaks
file descriptors due to a bug where it does not correctly close
sockets, and instead, leaves them in the CLOSE_WAIT state.
This causes rsyslogd on busy servers to eventually hit the limit of
maximum open files allowed, which locks rsyslogd up until it is
restarted.
A workaround is to restart rsyslogd every month or so to manually
close all of the open sockets.
Only users of the imrelp module are affected, and not rsyslog users in
general.
[Testcase]
Install the rsyslog-relp module like so:
$ sudo apt install rsyslog rsyslog-relp
Next, generate a working directory, and make a config file that loads
the relp module.
$ sudo mkdir /workdir
$ cat << EOF >> ./spool.conf
\$LocalHostName spool
\$AbortOnUncleanConfig on
\$PreserveFQDN on
global(
workDirectory="/workdir"
maxMessageSize="256k"
)
main_queue(queue.type="Direct")
module(load="imrelp")
input(
type="imrelp"
name="imrelp"
port="601"
ruleset="spool"
MaxDataSize="256k"
)
ruleset(name="spool" queue.type="direct") {
}
# Just so rsyslog doesn't whine that we do not have outputs
ruleset(name="noop" queue.type="direct") {
action(
type="omfile"
name="omfile"
file="/workdir/spool.log"
)
}
EOF
Verify that the config is valid, then start a rsyslog server.
$ sudo rsyslogd -f ./spool.conf -N9
$ sudo rsyslogd -f ./spool.conf -i /workdir/rsyslogd.pid
Fetch the rsyslogd PID and check for open files.
$ RLOGPID=$(cat /workdir/rsyslogd.pid)
$ sudo ls -l /proc/$RLOGPID/fd
total 0
lr-x-- 1 root root 64 Dec 17 01:22 0 -> /dev/urandom
lrwx-- 1 root root 64 Dec 17 01:22 1 -> 'socket:[41228]'
lrwx-- 1 root root 64 Dec 17 01:22 3 -> 'socket:[41222]'
lrwx-- 1 root root 64 Dec 17 01:22 4 -> 'socket:[41223]'
lrwx-- 1 root root 64 Dec 17 01:22 7 -> 'anon_inode:[eventpoll]'
We have 3 sockets open by default. Next, use netcat to open 100
connections:
$ for i in {1..100} ; do nc -z 127.0.0.1 601 ; done
Now check for open file descriptors, and there will be an extra 100 sockets
in the list:
$ sudo ls -l /proc/$RLOGPID/fd
https://paste.ubuntu.com/p/f6NQVNbZcR/
We can check the state of these sockets with:
$ ss -t
https://paste.ubuntu.com/p/7Ts2FbxJrg/
The listening sockets will be in CLOSE-WAIT, and the netcat sockets
will be in FIN-WAIT-2.
$ ss -t | grep CLOSE-WAIT | wc -l
100
If you install the test package available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/sf299578-test
When you open connections with netcat, these will be closed properly,
and the file descriptor leak will be fixed.
[Where problems could occur]
If a regression were to occur, it would be limited to users of the
imrelp module, which is a part of the rsyslogd-relp package, and
depends on librelp.
rsyslog-relp is not part of a default installation of rsyslog, and is
opt in by changing a configuration file to enable imrelp.
The changes to rsyslog implement a testcase which exercises the problematic
code to ensure things are working as expected; this
can be enabled manually on build, and has been verified to pass (#7).
[Other]
Upstream bug list:
https://github.com/rsyslog/rsyslog/issues/4350
https://github.com/rsyslog/rsyslog/issues/4005
https://github.com/rsyslog/librelp/issues/188
https://github.com/rsyslog/librelp/pull/193
The following commits fix the problem:
rsyslogd
commit baee0bd5420649329793746f0daf87c4f59fe6a6
Author: Andre lorbach
Date: Thu Apr 9 13:00:35 2020 +0200
Subject: testbench: Add
[Touch-packages] [Bug 1908473] Re: rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which leads to file descriptor leak
This bug was fixed in the package librelp - 1.5.0-1ubuntu2.20.10.1
---
librelp (1.5.0-1ubuntu2.20.10.1) groovy; urgency=medium
* Fix file descriptor leak as sockets are stuck in CLOSE_WAIT
due to not being closed properly due to memory leak. (LP: #1908473)
- d/p/lp1908473-01-replsess-fix-double-free-of-sendbuf-in-some-cases.patch
- d/p/lp1908473-02-fix-memory-leak-on-session-break.patch
- d/p/lp1908473-03-Fix-FD-leak-when-socket-shutdown-is-one-sided.patch
-- Matthew Ruffell Sun, 03 Jan 2021
19:50:00 +1300
** Changed in: librelp (Ubuntu Groovy)
Status: Fix Committed => Fix Released
--
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/1908473
Title:
rsyslog-relp: imrelp module leaves sockets in CLOSE_WAIT state which
leads to file descriptor leak
Status in librelp package in Ubuntu:
Fix Released
Status in rsyslog package in Ubuntu:
Fix Released
Status in librelp source package in Focal:
Fix Committed
Status in rsyslog source package in Focal:
Won't Fix
Status in librelp source package in Groovy:
Fix Released
Status in rsyslog source package in Groovy:
Fix Released
Status in librelp source package in Hirsute:
Fix Released
Status in rsyslog source package in Hirsute:
Fix Released
Bug description:
[Impact]
In recent versions of rsyslog and librelp, the imrelp module leaks
file descriptors due to a bug where it does not correctly close
sockets, and instead, leaves them in the CLOSE_WAIT state.
This causes rsyslogd on busy servers to eventually hit the limit of
maximum open files allowed, which locks rsyslogd up until it is
restarted.
A workaround is to restart rsyslogd every month or so to manually
close all of the open sockets.
Only users of the imrelp module are affected, and not rsyslog users in
general.
[Testcase]
Install the rsyslog-relp module like so:
$ sudo apt install rsyslog rsyslog-relp
Next, generate a working directory, and make a config file that loads
the relp module.
$ sudo mkdir /workdir
$ cat << EOF >> ./spool.conf
\$LocalHostName spool
\$AbortOnUncleanConfig on
\$PreserveFQDN on
global(
workDirectory="/workdir"
maxMessageSize="256k"
)
main_queue(queue.type="Direct")
module(load="imrelp")
input(
type="imrelp"
name="imrelp"
port="601"
ruleset="spool"
MaxDataSize="256k"
)
ruleset(name="spool" queue.type="direct") {
}
# Just so rsyslog doesn't whine that we do not have outputs
ruleset(name="noop" queue.type="direct") {
action(
type="omfile"
name="omfile"
file="/workdir/spool.log"
)
}
EOF
Verify that the config is valid, then start a rsyslog server.
$ sudo rsyslogd -f ./spool.conf -N9
$ sudo rsyslogd -f ./spool.conf -i /workdir/rsyslogd.pid
Fetch the rsyslogd PID and check for open files.
$ RLOGPID=$(cat /workdir/rsyslogd.pid)
$ sudo ls -l /proc/$RLOGPID/fd
total 0
lr-x-- 1 root root 64 Dec 17 01:22 0 -> /dev/urandom
lrwx-- 1 root root 64 Dec 17 01:22 1 -> 'socket:[41228]'
lrwx-- 1 root root 64 Dec 17 01:22 3 -> 'socket:[41222]'
lrwx-- 1 root root 64 Dec 17 01:22 4 -> 'socket:[41223]'
lrwx-- 1 root root 64 Dec 17 01:22 7 -> 'anon_inode:[eventpoll]'
We have 3 sockets open by default. Next, use netcat to open 100
connections:
$ for i in {1..100} ; do nc -z 127.0.0.1 601 ; done
Now check for open file descriptors, and there will be an extra 100 sockets
in the list:
$ sudo ls -l /proc/$RLOGPID/fd
https://paste.ubuntu.com/p/f6NQVNbZcR/
We can check the state of these sockets with:
$ ss -t
https://paste.ubuntu.com/p/7Ts2FbxJrg/
The listening sockets will be in CLOSE-WAIT, and the netcat sockets
will be in FIN-WAIT-2.
$ ss -t | grep CLOSE-WAIT | wc -l
100
If you install the test package available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/sf299578-test
When you open connections with netcat, these will be closed properly,
and the file descriptor leak will be fixed.
[Where problems could occur]
If a regression were to occur, it would be limited to users of the
imrelp module, which is a part of the rsyslogd-relp package, and
depends on librelp.
rsyslog-relp is not part of a default installation of rsyslog, and is
opt in by changing a configuration file to enable imrelp.
The changes to rsyslog implement a testcase which exercises the problematic
code to ensure things are working as expected; this
can be enabled manually on build, and has been verified to pass (#7).
[Other]
Upstream bug list:
https://github.com/rsyslog/rsyslog/issues/4350
https://github.com/rsyslog/rsyslog/issues/4005
https://github.com/rsyslog/librelp/issues/188
https://github.com/rsyslog/librelp/pull/193
The following commits fix the prob
[Touch-packages] [Bug 873101] Re: Totem will only plays an .m4v file when it isn't online
** Description changed: - I'm using totem 3.0.1-0ubuntu7 (same version is listed for all totem - related packages), on ubuntu 11.10 64bit. - - The issue is - if i try to watch an m4v video file in firefox, from my - university's server - (http://learn.lboro.ac.uk/file.php/997/Videos/Safety_Talk/Safety_Talk_- - _iPhone.m4v), then totem searches for a suitable plugin and an error - occurs: The playback of this movie requires a text/html decoder plugin - which is not installed. - - However, if i 'save as' on the link to the video and put in on my - computer, i can double click the video to run in totem and it runs - perfectly? - - video/x-m4v MPEG-4 videom4vis listed in - about:plugins - - Something's a bit inconsistent here - why can i only play the m4v video - file on my computer and not directly from the internet? + - ** Changed in: gstreamer0.10 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/873101 Title: Totem will only plays an .m4v file when it isn't online Status in gstreamer0.10 package in Ubuntu: Invalid Bug description: - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/873101/+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 1835660] Re: initramfs unpacking failed
This bug was fixed in the package linux - 5.8.0-41.46 --- linux (5.8.0-41.46) groovy; urgency=medium * groovy/linux: 5.8.0-41.46 -proposed tracker (LP: #1912219) * Groovy update: upstream stable patchset 2020-12-17 (LP: #1908555) // nvme drive fails after some time (LP: #1910866) - Revert "nvme-pci: remove last_sq_tail" * initramfs unpacking failed (LP: #1835660) - SAUCE: lib/decompress_unlz4.c: correctly handle zero-padding around initrds. * overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 (LP: #1900141) - ovl: do not fail because of O_NOATIME -- Kleber Sacilotto de Souza Mon, 18 Jan 2021 17:01:08 +0100 -- 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/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Released Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Released Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1835660] Re: initramfs unpacking failed
This bug was fixed in the package linux - 5.4.0-65.73 --- linux (5.4.0-65.73) focal; urgency=medium * focal/linux: 5.4.0-65.73 -proposed tracker (LP: #1912220) * initramfs unpacking failed (LP: #1835660) - SAUCE: lib/decompress_unlz4.c: correctly handle zero-padding around initrds. * overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120 (LP: #1900141) - ovl: do not fail because of O_NOATIME * Focal update: v5.4.79 upstream stable release (LP: #1907151) - net/mlx5: Use async EQ setup cleanup helpers for multiple EQs - net/mlx5: poll cmd EQ in case of command timeout - net/mlx5: Fix a race when moving command interface to events mode - net/mlx5: Add retry mechanism to the command entry index allocation * Kernel 5.4.0-56 Wi-Fi does not connect (LP: #1906770) - mt76: fix fix ampdu locking * [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander (LP: #1899802) - scsi: mpt3sas: Define hba_port structure - scsi: mpt3sas: Allocate memory for hba_port objects - scsi: mpt3sas: Rearrange _scsih_mark_responding_sas_device() - scsi: mpt3sas: Update hba_port's sas_address & phy_mask - scsi: mpt3sas: Get device objects using sas_address & portID - scsi: mpt3sas: Rename transport_del_phy_from_an_existing_port() - scsi: mpt3sas: Get sas_device objects using device's rphy - scsi: mpt3sas: Update hba_port objects after host reset - scsi: mpt3sas: Set valid PhysicalPort in SMPPassThrough - scsi: mpt3sas: Handling HBA vSES device - scsi: mpt3sas: Add bypass_dirty_port_flag parameter - scsi: mpt3sas: Handle vSES vphy object during HBA reset - scsi: mpt3sas: Add module parameter multipath_on_hba - scsi: mpt3sas: Bump driver version to 35.101.00.00 -- Kleber Sacilotto de Souza Mon, 18 Jan 2021 17:31:23 +0100 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-16120 ** Changed in: linux (Ubuntu Groovy) 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/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Released Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Released Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This c
[Touch-packages] [Bug 1913339] [NEW] wrong path install location for groovy package
Public bug reported:
Description:Ubuntu 20.10
Release:20.10
libnss3:
Installé : 2:3.55-1ubuntu3
Candidat : 2:3.55-1ubuntu3
Table de version :
*** 2:3.55-1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
100 /var/lib/dpkg/status
On groovy, the `apt-file list libnss3` shows:
libnss3: /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
libnss3: /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
libnss3: /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
libnss3: /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so
libnss3: /usr/lib/x86_64-linux-gnu/libnss3.so
libnss3: /usr/lib/x86_64-linux-gnu/libnssutil3.so
libnss3: /usr/lib/x86_64-linux-gnu/libsmime3.so
libnss3: /usr/lib/x86_64-linux-gnu/libssl3.so
libnss3: /usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
libnss3: /usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
libnss3: /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
libnss3: /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
libnss3: /usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
libnss3: /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
libnss3: /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
libnss3: /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
libnss3: /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
libnss3: /usr/share/doc/libnss3/changelog.Debian.gz
libnss3: /usr/share/doc/libnss3/copyright
libnss3: /usr/share/lintian/overrides/libnss3
You can also see this at link:
https://packages.ubuntu.com/groovy/amd64/libnss3/filelist
Apparently, ${DEB_HOST_MULTIARCH} should be replaced by x86_64-linux-gnu. I
believe this is a bug in packing .deb files.
** Affects: nss (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1913339
Title:
wrong path install location for groovy package
Status in nss package in Ubuntu:
New
Bug description:
Description:Ubuntu 20.10
Release:20.10
libnss3:
Installé : 2:3.55-1ubuntu3
Candidat : 2:3.55-1ubuntu3
Table de version :
*** 2:3.55-1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
100 /var/lib/dpkg/status
On groovy, the `apt-file list libnss3` shows:
libnss3: /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
libnss3: /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
libnss3: /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
libnss3: /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so
libnss3: /usr/lib/x86_64-linux-gnu/libnss3.so
libnss3: /usr/lib/x86_64-linux-gnu/libnssutil3.so
libnss3: /usr/lib/x86_64-linux-gnu/libsmime3.so
libnss3: /usr/lib/x86_64-linux-gnu/libssl3.so
libnss3: /usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
libnss3: /usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
libnss3: /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
libnss3: /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
libnss3: /usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
libnss3: /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
libnss3: /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
libnss3: /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
libnss3: /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
libnss3: /usr/share/doc/libnss3/changelog.Debian.gz
libnss3: /usr/share/doc/libnss3/copyright
libnss3: /usr/share/lintian/overrides/libnss3
You can also see this at link:
https://packages.ubuntu.com/groovy/amd64/libnss3/filelist
Apparently, ${DEB_HOST_MULTIARCH} should be replaced by x86_64-linux-gnu. I
believe this is a bug in packing .deb files.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1913339/+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 1904213] Re: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257]
Hi, got exactly the same issue with two identical laptops (Lenovo ThinkBook 13s-IML). One has the current latest kernel from Ubuntu 20.04 (5.8.0-40), for the other one I installed a more recent kernel (5.9.16-050916) using mainline. Microphone does not work for both. Also, I tried some steps from https://help.ubuntu.com/community/SoundTroubleshootingProcedure, and when running : wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x ./alsa-info.sh && ./alsa-info.sh I get the following error : cat: '/sys/module/snd_soc_skl_hda_dsp/parameters/*': No such file or directory Finally, I attached the output from alsa-info.sh. ** Attachment added: "alsa-info.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1904213/+attachment/5457089/+files/alsa-info.txt -- 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/1904213 Title: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257] Status in alsa-driver package in Ubuntu: Confirmed Bug description: After installing current 20.04 release on ThinkBook 13s IML with Intel audio card built-in microphone is not working - I'm unable to record anything. I could confirm that it was working in Windows 10 (previously installed on that laptop), and when I'm using headphones their microphone is working fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anlar 1496 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 13 19:07:34 2020 InstallationDate: Installed on 2020-10-29 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: Only some of inputs are working Title: [20RR, Realtek ALC257, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CQCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 13s-IML dmi.modalias: dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML: dmi.product.family: ThinkBook 13s-IML dmi.product.name: 20RR dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML dmi.product.version: Lenovo ThinkBook 13s-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1904213/+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 1904213] Re: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1904213 Title: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257] Status in alsa-driver package in Ubuntu: Confirmed Bug description: After installing current 20.04 release on ThinkBook 13s IML with Intel audio card built-in microphone is not working - I'm unable to record anything. I could confirm that it was working in Windows 10 (previously installed on that laptop), and when I'm using headphones their microphone is working fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anlar 1496 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 13 19:07:34 2020 InstallationDate: Installed on 2020-10-29 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: Only some of inputs are working Title: [20RR, Realtek ALC257, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CQCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 13s-IML dmi.modalias: dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML: dmi.product.family: ThinkBook 13s-IML dmi.product.name: 20RR dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML dmi.product.version: Lenovo ThinkBook 13s-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1904213/+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 1913187] Re: iproute2 segfaults when filtering sockets
$ git-ubuntu tag --upload
$ git describe
upload/4.15.0-2ubuntu1.3
$ git push pkg upload/4.15.0-2ubuntu1.3
Counting objects: 11, done.
Delta compression using up to 24 threads.
Compressing objects: 100% (11/11), done.
Writing objects: 100% (11/11), 2.07 KiB | 176.00 KiB/s, done.
Total 11 (delta 7), reused 0 (delta 0)
To ssh://git.launchpad.net/ubuntu/+source/iproute2
* [new tag] upload/4.15.0-2ubuntu1.3 -> upload/4.15.0-2ubuntu1.3
$ debdiff *.dsc | diffstat
changelog | 7 +++
patches/lp1913187-ss-fix-NULL-dereference-when-rendering.patch | 40
patches/series | 1 +
3 files changed, 48 insertions(+)
[rafaeldtinoco@iproute2issue ubuntu]$ dput ubuntu
./iproute2_4.15.0-2ubuntu1.3_source.changes
Checking signature on .changes
gpg: ./iproute2_4.15.0-2ubuntu1.3_source.changes: Valid signature from
A93E0E0AD83C0D0F
Checking signature on .dsc
gpg: ./iproute2_4.15.0-2ubuntu1.3.dsc: Valid signature from A93E0E0AD83C0D0F
Uploading to ubuntu (via ftp to upload.ubuntu.com):
Uploading iproute2_4.15.0-2ubuntu1.3.dsc: done.
Uploading iproute2_4.15.0-2ubuntu1.3.debian.tar.xz: done.
Uploading iproute2_4.15.0-2ubuntu1.3_source.buildinfo: done.
Uploading iproute2_4.15.0-2ubuntu1.3_source.changes: done.
Successfully uploaded packages.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1913187
Title:
iproute2 segfaults when filtering sockets
Status in iproute2 package in Ubuntu:
Fix Released
Status in iproute2 source package in Bionic:
Confirmed
Bug description:
[Impact]
* The ss tool crashes when a query returns no results (seg fault)
[Test Case]
* $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst
127.0.0.1
Segmentation fault
* PPA with the fix:
https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187
[Where problems could occur]
* The ss tool is impacted and it has its code changed for the fix.
* The fix is a clean cherry-pick and straightforward (moving
declaration after a NULL check).
[Other Info]
When in Ubuntu Bionic, if one calls:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58910 127.0.0.1:22
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)
it works. Just like when in Groovy:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58908 127.0.0.1:22
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)
but.. if there is nothing to show, in Bionic we get a segfault:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
Segmentation fault
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+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 1889742] Re: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)
[Impact] * Vector alignment hints were enabled for z14 processors, but not z13 * Since the z13 processors support vector alignment hints, binutils should have them enabled for z13 [Test Case] * Run the test suite to make sure all tests pass * Pull in the change, and re-run the test suite to make sure all tests still pass. This backport includes tests for the vector alignment hints. [Where problems could occur] * If vector alignment hints were not enabled correctly we could still compile code with incorrectly ordered opcodes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1889742 Title: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils) Status in Ubuntu on IBM z Systems: In Progress Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Focal: In Progress Status in binutils source package in Groovy: Fix Released Bug description: == Comment: #0 - Heinz-Werner Seeck - 2020-07-31 03:28:30 == On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Already included within 20.10 via LP: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654 This should also be SRUed for 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889742/+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 1913320] [NEW] software and updates do not open.
Public bug reported: i cannot open my additional drivers setting also the software & updates center. ** 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/1913320 Title: software and updates do not open. Status in software-properties package in Ubuntu: New Bug description: i cannot open my additional drivers setting also the software & updates center. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1913320/+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 1677881] Re: Missing dep8 tests
FWIW, this test correctly caught a regression, fixed in openldap 2.4.56 +dfsg-1ubuntu2. Good job :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1677881 Title: Missing dep8 tests Status in krb5 package in Ubuntu: Fix Released Bug description: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As of March 29, 2017, this source package did not contain dep8 tests in the current development release of Ubuntu, named Zesty. This was determined by running `pull-lp-source krb5 zesty` and then checking for the existence of 'debian/tests/' and 'debian/tests/control'. Test automation is essential to higher levels of quality and confidence in updates to packages. dep8 tests [1] specify how automatic testing can be integrated into packages and then run by package maintainers before new uploads. This defect is to report the absence of these tests and to report the opportunity as a potential item for development by both new and experienced contributors. [1] http://packaging.ubuntu.com/html/auto-pkg-test.html affects ubuntu/krb5 status new importance wishlist tag needs-dep8 - --- Joshua Powers Ubuntu Server Canonical Ltd -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJY3YGVAAoJEIP8BxPaZgwlCIEP/36uotG3iLNIh5/fPc2FDzwV hqK5CLKbCLqlX7RmzkSzO303hJ051Q6uWIb1ZcnvZShO4h2mrQfyXXmWBXO3So/2 imYe6Pg3j9v1aNYCxpvWKL6VIpN5beADCoWlAS9P89qSIdyEYTiaL6HFHzbA5hck 7rtMhHnzw16mkT+ttZ39f4kqZ9jqqV1je0lPyCI3L+UicswkdeymHeZAZSkG13lW uSi5SVLFDpDeWq/23Ohj0tacLZbpBKG4vScRQ7+Me3ieGnC0gii8C1luXGPWpS9v CvW1JLPbuo3yHooBzJw6YAYI2TiWyNjtO2/9ESPxcmn+tPn7iXoeTBIstlQC2iY0 fvoUrmxUjSJafgCyZE1NNy8gTlFLObpMP/qZPtw7YLKaD9t64+JZUK4vzSNr1tY5 ltCXFf0mneUrUjTOS1Io+vigiBbMEIFuUjEXT3DxGEybf8rrl6fJdCD++1L0NTXR ImfhCBgSEYBrluRLHu1tGftin7wKgarl7uWLzZxGeJ/MiXkX0eWIgOVoXaQq6gnR HR7XF1x9x1VJYi2CGMrDDWSHWDHgXC5UOcBz/KLMSPMcyQakXyRrw1Hqplj3G3PM OkqR8uLWUYfTZvrVvnSj4jJPNRSiBOz95FFbfMZ43yxoE5F6QBhztwgcJC8/g+bn zu94s0Hiyv+yxmptMwgX =ibX0 -END PGP SIGNATURE- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1677881/+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 1908502] Re: [MIR] libdeflate
** Changed in: libdeflate (Ubuntu Hirsute) Assignee: (unassigned) => Sebastien Bacher (seb128) ** Changed in: tiff (Ubuntu Hirsute) Assignee: (unassigned) => Sebastien Bacher (seb128) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1908502 Title: [MIR] libdeflate Status in libdeflate package in Ubuntu: New Status in tiff package in Ubuntu: Triaged Status in libdeflate source package in Hirsute: New Status in tiff source package in Hirsute: Triaged Bug description: * Availability In sync with Debian, built on all architectures https://launchpad.net/ubuntu/+source/libdeflate/1.7-1 * Rationale It's a new depends of libtiff * Security There is no known security issues https://security-tracker.debian.org/tracker/source-package/libdeflate https://people.canonical.com/~ubuntu-security/cve/pkg/libdeflate.html https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libdeflate * Quality assurance The desktop team is going to subscribe to the package https://launchpad.net/ubuntu/+source/libdeflate/+bugs https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libdeflate No open reports The package enables upstream tests during the build and ships basic autopkgtests * Dependencies No universe binary dependencies * Standards compliance current 4.5.1 standards-version, debhelper compat 13, dh style simple rules * Maintenance Upstream is active, the package is maintained in Debian and in sync for Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdeflate/+bug/1908502/+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 1912609] Re: mac80211_hwsim: hostapd fails to start with S1G band
** Changed in: wpa (Ubuntu Hirsute) Assignee: (unassigned) => Sebastien Bacher (seb128) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1912609 Title: mac80211_hwsim: hostapd fails to start with S1G band Status in wpa package in Ubuntu: New Status in wpa source package in Hirsute: New Bug description: Hostapd fails to start on a recent 5.10+ kernel: $ cat repro.sh #!/bin/sh sudo modprobe mac80211_hwsim sudo ip a flush dev wlan0 sudo ip a add 192.168.5.1/24 dev wlan0 cat << EOF > hostapd.conf interface=wlan0 driver=nl80211 hw_mode=b channel=1 ssid=fake net EOF sudo hostapd hostapd.conf ubuntu@hirsute-amd64:~$ ./repro.sh Configuration file: hostapd.conf nl80211: kernel reports: expected nested data Using interface wlan0 with hwaddr 02:00:00:00:00:00 and ssid "fake net" wlan0: interface state UNINITIALIZED->ENABLED wlan0: AP-ENABLED ^C wlan0: interface state ENABLED->DISABLED wlan0: AP-DISABLED wlan0: CTRL-EVENT-TERMINATING nl80211: deinit ifname=wlan0 disabled_11b_rates=0 this due to the mismanagement of the newly added S1G band, the attached patch fixes it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1912609/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
** Changed in: libx11 (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: libx11 (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: New Status in libx11 source package in Focal: New Status in libx11 source package in Groovy: New Bug description: STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710 To further assert this, note that there is a SpaceFM file manager that is available in GTK2 and GTK3. The GTK2 version displays the behavior. The GTK3 version does not. Same with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/+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 1825186] Re: gpgv-win32 autopkgtest always fails
** Changed in: gnupg2 (Ubuntu Bionic) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) ** Changed in: gnupg2 (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1825186 Title: gpgv-win32 autopkgtest always fails Status in gnupg package in Ubuntu: Invalid Status in gnupg2 package in Ubuntu: Opinion Status in gnupg source package in Xenial: Won't Fix Status in gnupg2 source package in Bionic: In Progress Status in gnupg2 source package in Cosmic: Won't Fix Status in gnupg2 source package in Disco: Fix Released Bug description: [impact] gpgv-win32 autopkgtest always fails [test case] check http://autopkgtest.ubuntu.com/packages/g/gnupg2 or run autopkgtest manually note the gpgv-win32 test is skipped on ppc64el and s390x for b/c, and has been removed from d/t/control entirely in d [regression potential] little to none; this affects the test case only [other info] as mentioned, in disco, the gpgv-win32 test has been removed from the tests/control completely. not sure if that is a better approach than fixing the test case. For now, I marked this Fix Released for disco since it doesn't fail there (since the testcase was removed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1825186/+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 1913187] Re: iproute2 segfaults when filtering sockets
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/iproute2/+git/iproute2/+merge/396921
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1913187
Title:
iproute2 segfaults when filtering sockets
Status in iproute2 package in Ubuntu:
Fix Released
Status in iproute2 source package in Bionic:
Confirmed
Bug description:
[Impact]
* The ss tool crashes when a query returns no results (seg fault)
[Test Case]
* $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst
127.0.0.1
Segmentation fault
* PPA with the fix:
https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187
[Where problems could occur]
* The ss tool is impacted and it has its code changed for the fix.
* The fix is a clean cherry-pick and straightforward (moving
declaration after a NULL check).
[Other Info]
When in Ubuntu Bionic, if one calls:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58910 127.0.0.1:22
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)
it works. Just like when in Groovy:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58908 127.0.0.1:22
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)
but.. if there is nothing to show, in Bionic we get a segfault:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
Segmentation fault
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+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 1913306] Re: slapd Apparmor profile allows /tmp widely
Any advice/comment from the security team on this please? ** Description changed: Currently debian/apparmor-profile defines: /var/tmp/** rw, This is quite wide. Can we narrow it down? There are a couple of alternative opportunities here: 1) Remove that line, and define instead more specific path rules, such as "/var/tmp/krb5_*.rcache2 rwk" that we recently added. A risk here is that it's difficult for us to determine and track the necessary paths, since some may be related to functionality that we don't have dep8 test coverage for. 2) Retain that line, add a "k", move slapd to a native systemd service and use PrivateTmp=yes. A third opportunity, independent of the above, is to move the rules to an abstraction that any sasl+gssapi+krb5 -using service could include. + + This discussion came up in + https://code.launchpad.net/~racb/ubuntu/+source/openldap/+git/openldap/+merge/396853, + but we focused on fixing only the immediate issue there, leaving this + bug open for another time. ** Merge proposal linked: https://code.launchpad.net/~racb/ubuntu/+source/openldap/+git/openldap/+merge/396853 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1913306 Title: slapd Apparmor profile allows /tmp widely Status in openldap package in Ubuntu: Triaged Bug description: Currently debian/apparmor-profile defines: /var/tmp/** rw, This is quite wide. Can we narrow it down? There are a couple of alternative opportunities here: 1) Remove that line, and define instead more specific path rules, such as "/var/tmp/krb5_*.rcache2 rwk" that we recently added. A risk here is that it's difficult for us to determine and track the necessary paths, since some may be related to functionality that we don't have dep8 test coverage for. 2) Retain that line, add a "k", move slapd to a native systemd service and use PrivateTmp=yes. A third opportunity, independent of the above, is to move the rules to an abstraction that any sasl+gssapi+krb5 -using service could include. This discussion came up in https://code.launchpad.net/~racb/ubuntu/+source/openldap/+git/openldap/+merge/396853, but we focused on fixing only the immediate issue there, leaving this bug open for another time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1913306/+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 1913306] [NEW] slapd Apparmor profile allows /tmp widely
Public bug reported: Currently debian/apparmor-profile defines: /var/tmp/** rw, This is quite wide. Can we narrow it down? There are a couple of alternative opportunities here: 1) Remove that line, and define instead more specific path rules, such as "/var/tmp/krb5_*.rcache2 rwk" that we recently added. A risk here is that it's difficult for us to determine and track the necessary paths, since some may be related to functionality that we don't have dep8 test coverage for. 2) Retain that line, add a "k", move slapd to a native systemd service and use PrivateTmp=yes. A third opportunity, independent of the above, is to move the rules to an abstraction that any sasl+gssapi+krb5 -using service could include. This discussion came up in https://code.launchpad.net/~racb/ubuntu/+source/openldap/+git/openldap/+merge/396853, but we focused on fixing only the immediate issue there, leaving this bug open for another time. ** Affects: openldap (Ubuntu) Importance: Medium Status: Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1913306 Title: slapd Apparmor profile allows /tmp widely Status in openldap package in Ubuntu: Triaged Bug description: Currently debian/apparmor-profile defines: /var/tmp/** rw, This is quite wide. Can we narrow it down? There are a couple of alternative opportunities here: 1) Remove that line, and define instead more specific path rules, such as "/var/tmp/krb5_*.rcache2 rwk" that we recently added. A risk here is that it's difficult for us to determine and track the necessary paths, since some may be related to functionality that we don't have dep8 test coverage for. 2) Retain that line, add a "k", move slapd to a native systemd service and use PrivateTmp=yes. A third opportunity, independent of the above, is to move the rules to an abstraction that any sasl+gssapi+krb5 -using service could include. This discussion came up in https://code.launchpad.net/~racb/ubuntu/+source/openldap/+git/openldap/+merge/396853, but we focused on fixing only the immediate issue there, leaving this bug open for another time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1913306/+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 1913187] Re: iproute2 segfaults when filtering sockets
MP:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/iproute2/+git/iproute2/+merge/396921
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187
** Description changed:
+ [Impact]
+
+ * The ss tool crashes when a query returns no results (seg fault)
+
+ [Test Case]
+
+ * $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst
127.0.0.1
+ Segmentation fault
+
+ [Where problems could occur]
+
+ * The ss tool is impacted and it has its code changed for the fix.
+
+ * The fix is a clean cherry-pick and straightforward (moving
+ declaration after a NULL check).
+
+ [Other Info]
+
When in Ubuntu Bionic, if one calls:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58910 127.0.0.1:22
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)
it works. Just like when in Groovy:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58908 127.0.0.1:22
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)
but.. if there is nothing to show, in Bionic we get a segfault:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
Segmentation fault
** Description changed:
[Impact]
- * The ss tool crashes when a query returns no results (seg fault)
+ * The ss tool crashes when a query returns no results (seg fault)
[Test Case]
- * $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst
127.0.0.1
- Segmentation fault
+ * $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst
127.0.0.1
+ Segmentation fault
+
+ * PPA with the fix:
+ https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187
[Where problems could occur]
- * The ss tool is impacted and it has its code changed for the fix.
+ * The ss tool is impacted and it has its code changed for the fix.
- * The fix is a clean cherry-pick and straightforward (moving
+ * The fix is a clean cherry-pick and straightforward (moving
declaration after a NULL check).
[Other Info]
-
+
When in Ubuntu Bionic, if one calls:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58910 127.0.0.1:22
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)
it works. Just like when in Groovy:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58908 127.0.0.1:22
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)
but.. if there is nothing to show, in Bionic we get a segfault:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
Segmentation fault
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1913187
Title:
iproute2 segfaults when filtering sockets
Status in iproute2 package in Ubuntu:
Fix Released
Status in iproute2 source package in Bionic:
Confirmed
Bug description:
[Impact]
* The ss tool crashes when a query returns no results (seg fault)
[Test Case]
* $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst
127.0.0.1
Segmentation fault
* PPA with the fix:
https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187
[Where problems could occur]
* The ss tool is impacted and it has its code changed for the fix.
* The fix is a clean cherry-pick and straightforward (moving
declaration after a NULL check).
[Other Info]
When in Ubuntu Bionic, if one calls:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58910 127.0.0.1:22
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)
it works. Just like when in Groovy:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58908 127.0.0.1:22
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)
but.. if there is nothing to show, in Bionic we get a segfault:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
Segmentation fault
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+subscriptions
--
[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed
$ sudo qemu-system-x86_64 -kernel ./vmlinuz-5.8.0-41-generic -initrd ./initrd-pad4-5.8.0-41-generic -append 'break=top quiet console=ttyS0' -m 2G -nographic -no-reboot Spawning shell within the initramfs BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) cat /test-file hello (initramfs) uname -a Linux (none) 5.8.0-41-generic #46-Ubuntu SMP Mon Jan 18 16:48:44 UTC 2021 x86_64 GNU/Linux (initramfs) Groovy verified too now. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- 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/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Committed Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Committed Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1913187] Re: iproute2 segfaults when filtering sockets
It only affects Bionic:
[rafaeldtinoco@iproute2issue iproute2]$ git describe
eb8559eff124221bfbafe934c4dbfe30f20604c0
v4.15.0-103-geb8559ef
[rafaeldtinoco@iproute2issue ~]$ rmadison iproute2
iproute2 | 3.12.0-2 | trusty | source
iproute2 | 3.12.0-2ubuntu1.2 | trusty-updates | source
iproute2 | 4.3.0-1ubuntu3| xenial | source
iproute2 | 4.3.0-1ubuntu3.16.04.5| xenial-updates | source
iproute2 | 4.15.0-2ubuntu1 | bionic | source
iproute2 | 4.15.0-2ubuntu1.1 | bionic-security | source
iproute2 | 4.15.0-2ubuntu1.2 | bionic-updates | source
iproute2 | 4.18.0-1ubuntu2~ubuntu18.04.1 | bionic-backports | source
iproute2 | 5.5.0-1ubuntu1| focal| source
iproute2 | 5.7.0-1ubuntu1| groovy | source
iproute2 | 5.9.0-1ubuntu1| hirsute | source
iproute2 | 5.10.0-2ubuntu1 | hirsute-proposed | source
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1913187
Title:
iproute2 segfaults when filtering sockets
Status in iproute2 package in Ubuntu:
Fix Released
Status in iproute2 source package in Bionic:
Confirmed
Bug description:
When in Ubuntu Bionic, if one calls:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58910 127.0.0.1:22
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)
it works. Just like when in Groovy:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58908 127.0.0.1:22
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)
but.. if there is nothing to show, in Bionic we get a segfault:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
Segmentation fault
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+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 1913187] Re: iproute2 segfaults when filtering sockets
[rafaeldtinoco@iproute2issue iproute2]$ git unfixed
eb8559eff124221bfbafe934c4dbfe30f20604c0 is the first bad commit
commit eb8559eff124221bfbafe934c4dbfe30f20604c0
Author: Jean-Philippe Brucker
Date: Sat Mar 3 16:59:44 2018 +
ss: fix NULL dereference when rendering without header
When ss is invoked with the no-header flag, if the query doesn't return
any result, render() is called with 'buffer' uninitialized. This
currently leads to a segfault. Ensure that buffer is initialized before
rendering.
The bug can be triggered with: ss -H sport = 10
Signed-off-by: Jean-Philippe Brucker
Acked-by: Stefano Brivio
Signed-off-by: Stephen Hemminger
:04 04 bf8f626f1c0b85bd690dab60d4f74db292ac8e65
6174ebf0728edab46c62b713f6aee495eef81cb5 M misc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1913187
Title:
iproute2 segfaults when filtering sockets
Status in iproute2 package in Ubuntu:
Fix Released
Status in iproute2 source package in Bionic:
Confirmed
Bug description:
When in Ubuntu Bionic, if one calls:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58910 127.0.0.1:22
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)
it works. Just like when in Groovy:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58908 127.0.0.1:22
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)
but.. if there is nothing to show, in Bionic we get a segfault:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
Segmentation fault
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+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 1835660] Re: initramfs unpacking failed
Verifying v5.8 build $ sudo qemu-system-x86_64 -kernel ./vmlinuz-5.8.0-41-generic -initrd ./initrd-pad4-5.8.0-41-generic -append 'break=top quiet console=ttyS0' -m 2G -nograt Spawning shell within the initramfs BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) uname -a Linux (none) 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 GNU/Linux (initramfs) cat /test-file second (initramfs) ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Committed Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Committed Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1835660] Re: initramfs unpacking failed
1) checking that reproducer still fails sudo qemu-system-x86_64 -kernel ./vmlinuz-5.4.0-64-generic -initrd ./initrd-pad4-5.4.0-64-generic -append 'break=top quiet console=ttyS0' -m 2G -nograt [3.581106] Initramfs unpacking failed: Decoding failed Spawning shell within the initramfs BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) cat /test-file cat: can't open '/test-file': No such file or directory (initramfs) uname -a Linux (none) 5.4.0-64-generic #72-Ubuntu SMP Fri Jan 15 10:27:54 UTC 2021 x86_64 GNU/Linux (initramfs) As expected, error message shown and file from second initrd is not accessible 2) checking that #65 ABI build of v5.4 is good Verifying v5.4 using a custom test case: sudo qemu-system-x86_64 -kernel ./vmlinuz-5.4.0-65-generic -initrd ./initrd-pad4-5.4.0-65-generic -append 'break=top quiet console=ttyS0' -m 2G -nograt Spawning shell within the initramfs BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) cat /test-file second (initramfs) uname -a Linux (none) 5.4.0-65-generic #73-Ubuntu SMP Mon Jan 18 17:25:17 UTC 2021 x86_64 GNU/Linux (initramfs) QEMU 5.0.0 monitor - type 'help' for more information (qemu) quit All is good. -- 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/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Committed Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Committed Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1912940] Re: disabled everytime startup
Hi Daniel, Sorry for the late reply I need to let bluetooth enabled by default during the restart but it seems not work to me..here's the rfkill attachment as per request. Thank you. On Mon, Jan 25, 2021 at 3:15 PM Daniel van Vugt <1912...@bugs.launchpad.net> wrote: > Thanks for the bug report. > > 1. Do you mean Bluetooth is disabled in Gnome Shell on startup, or the > controllers are disabled in bluetoothctl? > > 2. Please reboot and then in a Terminal window run: > >rfkill > newrfkill.txt > >and attach the resulting text file here. > > > ** Changed in: bluez (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1912940 > > Title: > disabled everytime startup > > Status in bluez package in Ubuntu: > Incomplete > > Bug description: > [Policy] > AutoEnable=true > > > not working > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: bluez 5.53-0ubuntu3 > Uname: Linux 5.10.0-051000-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.14 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: > read kernel buffer failed: Operation not permitted > Date: Sun Jan 24 19:49:49 2021 > InstallationDate: Installed on 2021-01-24 (0 days ago) > InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) > InterestingModules: rfcomm bnep btusb bluetooth > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 002: ID 8087:0a2a Intel Corp. >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Lsusb-t: >/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M >/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M >|__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M >|__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M > MachineType: LENOVO 81CG > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-051000-generic > root=UUID=0281b4fb-589a-46ed-b8ee-896d3505e7bd ro > SourcePackage: bluez > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 10/10/2019 > dmi.bios.release: 1.39 > dmi.bios.vendor: LENOVO > dmi.bios.version: 6NCN39WW > dmi.board.asset.tag: NO Asset Tag > dmi.board.name: LNVNB161216 > dmi.board.vendor: LENOVO > dmi.board.version: SDK0J40688 WIN > dmi.chassis.asset.tag: NO Asset Tag > dmi.chassis.type: 32 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: MIIX 520-12IKB > dmi.ec.firmware.release: 1.39 > dmi.modalias: > dmi:bvnLENOVO:bvr6NCN39WW:bd10/10/2019:br1.39:efr1.39:svnLENOVO:pn81CG:pvrMIIX520-12IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct32:cvrMIIX520-12IKB: > dmi.product.family: MIIX 520-12IKB > dmi.product.name: 81CG > dmi.product.sku: LENOVO_MT_81CG_BU_idea_FM_MIIX 520-12IKB > dmi.product.version: MIIX 520-12IKB > dmi.sys.vendor: LENOVO > hciconfig: >hci0:Type: Primary Bus: USB > BD Address: 3C:6A:A7:BB:B7:63 ACL MTU: 1021:5 SCO MTU: 96:6 > UP RUNNING PSCAN ISCAN > RX bytes:213889 acl:13940 sco:0 events:310 errors:0 > TX bytes:40352 acl:45 sco:0 commands:249 errors:0 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1912940/+subscriptions > ** Attachment added: "newrfkill.txt" https://bugs.launchpad.net/bugs/1912940/+attachment/5457003/+files/newrfkill.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1912940 Title: disabled everytime startup Status in bluez package in Ubuntu: Incomplete Bug description: [Policy] AutoEnable=true not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Jan 24 19:49:49 2021 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 4: Dev 2, If 1, Class=Wireless,
[Touch-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
2 of the pulseaudio patches landed upstream now, maybe time to nag on the first one and then we should be able to get the fixes in Hirsute at least? -- 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: New Status in pulseaudio package in Ubuntu: New 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 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 1835660] Re: initramfs unpacking failed
@vmc this bugfix is not yet available on any .iso for any series yet. It can only be tested from installed systems and enabling proposed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in OEM Priority Project: New Status in grub2 package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in grub2 source package in Focal: Invalid Status in initramfs-tools source package in Focal: Invalid Status in linux source package in Focal: Fix Committed Status in grub2 source package in Groovy: Invalid Status in initramfs-tools source package in Groovy: Invalid Status in linux source package in Groovy: Fix Committed Status in grub2 source package in Hirsute: Invalid Status in initramfs-tools source package in Hirsute: Invalid Status in linux source package in Hirsute: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. [Impact] * Decoding failure messages in dmsg with a single lz4 initrd * Multiple lz4 compressed initrds cannot be decompressed by kernel, when loaded by grub * Multiple lz4 compressed initrds cannot be decompressed by kernel, when there is padding between them [Test Case] * Create empty padding with $ dd if=/dev/zero of=pad4 bs=1 count=4 * Create an lz4 compressed initrd with a single test-file in it with some content. I.e. echo "second-initrd" > test-file, and then pack that with cpio hewc owned by root & lz4 -l. * Create a combined padded initrd of stock initrd, pad4, and the test-marker initrd created above. * Boot above with "break=top" kernel command line. * With broken kernels, there should be dmesg error message that decoding failed, and one will observe that /test-file does not exist in the shell. * With fixed kernel, /test-file in the initrd shell should exist, and should have the expected content "second-initrd". * The alignment and padding in the above test case depends on the size of the first initrd => if a given padded initrd does not reproduce the problem, try varying the size of the first initrd or that of the padding between 0..4. [Where problems could occur] * This changes compatible lz4 decompressor in the kernel, which can also be used by other kernel modules such as cryptography, squashfs, zram, f2fs, comprssed kernel image, pstore. For example, previously rejected files with "bogus" length and extra padding may now be accepted, whereas they were previously getting rejected by the decompressor. * Ideally kernel should switch to the stable lz4 format which has better specification of end of stream. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1835660/+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 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
Thanks for all the valuable info about this problem. I'm not sure I understand if the observed behaviour is the one expected ? On of my client had his Ryzen 2200g workstation broken ( initramfs prompt ) after a 5.8 update , going back to 5.4 worked - Virtualbox module still does not build on 5.8 - Broadcom Wifi module neither Then I don't think 5.8 was ready to be deployed ? Should we force remove linux-hwe package from workstations for now ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Beginning about January 8th Focal users that installed Focal using either the Ubuntu 20.04 or 20.04.1 installation media began getting updated to the 5.8 series linux kernel. Those who had installed using the Ubuntu Focal Beta were not effected. This is because Focal Beta was properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images were built with ‘linux-generic-hwe-20.04‘. This can be easily verified by looking at the iso manifest: https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop- amd64.manifest Note: old-release manifests (where 20.04 Beta and 20.04 reside) must be downloaded here: https://old-releases.ubuntu.com/releases/20.04/ The expected behavior is for Ubuntu Focal users to remain on the 5.4 series kernel unless they install with 20.04.2 or later images as indicated here: https://wiki.ubuntu.com/Kernel/LTSEnablementStack While not entirely updated it says “if one wants to remain on the original GA (General Availability) stacks, the options [include]; Install from a previous 12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point release and update”. Jump just below that to the Focal specific notes and it says “The 20.04.2 and newer point releases will ship with an updated kernel and X stack by default for the desktop”. Since 20.04.2 is not even due for release until next month it makes no sense for updates to the 5.8 series kernel to be occurring unless the focal-proposed repos are enabled even if HWE protocols had been changed. It’s also worth noting that thankfully no accompanying HWE X stack is yet available in the repos. I say thankfully because my efforts at downgrading the X stack in 16.04 and 18.04 were never successful! But the lack of a matching X stack may explain the many complaints on the forums about broken graphics??? It’s also worth noting that even the release notes say that “Ubuntu 20.04 LTS is based on the long-term supported Linux release series 5.4“. https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1 are supposed to be supported with the 5.4 series kernel for the entire 5 year life span: https://ubuntu.com/kernel/lifecycle The other flavors’ 20.04 and 20.04.1 images were all built correctly with ‘linux-generic’ with the possible exception of Ubuntu Studio which uses a kernel stack I’m not familiar with. I’m also uncertain about Ubuntu server because I’m simply not familiar with it. Original bug description below: ## Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-m
[Touch-packages] [Bug 1913207] Re: unable to connect dell E6400 to wifi
** Package changed: network-manager (Ubuntu) => linux (Ubuntu) -- 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/1913207 Title: unable to connect dell E6400 to wifi Status in linux package in Ubuntu: New Bug description: Software updates stated "Broadcom Inc. and subsidiaries: BCM4312 802.11b/g LP-PHY (Wireless 1397 WLAN Mini-Card) Using Broadcom 802.11 Linux STA wireless driver source from bcmwl-kernel-source (proprietary) do not use this device.. After placing a bullet next to" Using Broadcom 802.11 Linux STA...then restarting computer it reverts to: "Do not use this device" I next did a hardware probe and i found at the end it stated that System wireless is Rfkill(strikethrough) Can someone pls assist Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913207/+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
