[Touch-packages] [Bug 1966849] [NEW] gzip exec format error under WSL
Public bug reported: gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows 19044.1620, making WSL pretty much unusable. bash: /usr/bin/gzip: cannot execute binary file: Exec format error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gzip 1.10-4ubuntu3 ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35 Uname: Linux 4.4.0-19041-Microsoft x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 29 06:40:33 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/usr/bin/fish SourcePackage: gzip UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gzip (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wsl -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1966849 Title: gzip exec format error under WSL Status in gzip package in Ubuntu: New Bug description: gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows 19044.1620, making WSL pretty much unusable. bash: /usr/bin/gzip: cannot execute binary file: Exec format error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gzip 1.10-4ubuntu3 ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35 Uname: Linux 4.4.0-19041-Microsoft x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 29 06:40:33 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/usr/bin/fish SourcePackage: gzip UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1966849/+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 1959525] Re: Occasional no display output on 6900XT or if been idle for too long
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1959525 Title: Occasional no display output on 6900XT or if been idle for too long Status in libdrm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: ## No output at boot The dmesg I attached is from when nothing showed at boot. Journal output: $ journalctl -r --grep amdgpu -- Journal begins at Thu 2022-01-27 05:36:17 EST, ends at Sun 2022-01-30 15:58:40 EST. -- Jan 30 15:50:24 Y4M1-II kernel: amdgpu: probe of :0c:00.0 failed with error -110 Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: ttm finalized Jan 30 15:50:24 Y4M1-II kernel: amdgpu_init+0x77/0x1000 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_pci_probe+0x12a/0x1b0 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_driver_load_kms.cold+0x46/0x83 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_driver_unload_kms+0x43/0x70 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_device_fini+0xc5/0x1e5 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_device_ip_fini.isra.0+0x206/0x2cd [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: gmc_v10_0_sw_fini+0x33/0x40 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_bo_fini+0x12/0x50 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_ttm_fini+0xab/0x100 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_vram_mgr_fini+0xe8/0x160 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: Modules linked in: hid_generic usbhid hid amdgpu(+) iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul sysfillrect ghash_clmulni_intel sysimgblt fb_sys_fops cec aesni_intel rc_core crypto_simd cryptd drm nvme ahci xhci_pci i2c_piix4 nvme_core igc libahci xhci_pci_renesas wmi Jan 30 15:50:24 Y4M1-II kernel: [drm:psp_v11_0_ring_destroy [amdgpu]] *ERROR* Fail to stop psp ring Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: amdgpu: finishing device. Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Fatal error during GPU init Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: amdgpu_device_ip_init failed Jan 30 15:50:24 Y4M1-II kernel: [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* hw_init of IP block failed -110 Jan 30 15:50:24 Y4M1-II kernel: [drm:amdgpu_gfx_enable_kcq.cold [amdgpu]] *ERROR* KCQ enable failed Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SMU is initialized successfully! Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: use vbios provided pptable Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SMU driver if version not matched Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: smu driver if version = 0x003d, smu fw if version = 0x0040, smu fw version = 0x003a4700 (58.71.0) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Will use PSP to load VCN firmware Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: 16368M of GTT memory ready. Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: 16368M of VRAM memory ready Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: AGP: 267894784M 0x0084 - 0x Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: GART: 512M 0x - 0x1FFF Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: VRAM: 16368M 0x0080 - 0x0083FEFF (16368M used) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SRAM ECC is not presented. Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: MEM ECC is not presented. Jan 30 15:50:24 Y4M1-II kernel: amdgpu: ATOM BIOS: 113-EXT800216-L05 Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Fetched VBIOS from VFCT Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: enabling device (0006 -> 0007) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: vgaarb: deactivate vga console Jan 30 15:50:24 Y4M1-II kernel: fb0: switching to amdgpudrmfb from EFI VGA Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Topology: Add CPU node Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Virtual CRAT table created for CPU Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Ignoring ACPI CRAT on non-APU system Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu kernel
[Touch-packages] [Bug 1959525] Re: Occasional no display output on 6900XT or if been idle for too long
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libdrm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1959525 Title: Occasional no display output on 6900XT or if been idle for too long Status in libdrm package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: ## No output at boot The dmesg I attached is from when nothing showed at boot. Journal output: $ journalctl -r --grep amdgpu -- Journal begins at Thu 2022-01-27 05:36:17 EST, ends at Sun 2022-01-30 15:58:40 EST. -- Jan 30 15:50:24 Y4M1-II kernel: amdgpu: probe of :0c:00.0 failed with error -110 Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: ttm finalized Jan 30 15:50:24 Y4M1-II kernel: amdgpu_init+0x77/0x1000 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_pci_probe+0x12a/0x1b0 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_driver_load_kms.cold+0x46/0x83 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_driver_unload_kms+0x43/0x70 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_device_fini+0xc5/0x1e5 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_device_ip_fini.isra.0+0x206/0x2cd [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: gmc_v10_0_sw_fini+0x33/0x40 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_bo_fini+0x12/0x50 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_ttm_fini+0xab/0x100 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: amdgpu_vram_mgr_fini+0xe8/0x160 [amdgpu] Jan 30 15:50:24 Y4M1-II kernel: Modules linked in: hid_generic usbhid hid amdgpu(+) iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul sysfillrect ghash_clmulni_intel sysimgblt fb_sys_fops cec aesni_intel rc_core crypto_simd cryptd drm nvme ahci xhci_pci i2c_piix4 nvme_core igc libahci xhci_pci_renesas wmi Jan 30 15:50:24 Y4M1-II kernel: [drm:psp_v11_0_ring_destroy [amdgpu]] *ERROR* Fail to stop psp ring Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: amdgpu: finishing device. Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Fatal error during GPU init Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: amdgpu_device_ip_init failed Jan 30 15:50:24 Y4M1-II kernel: [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* hw_init of IP block failed -110 Jan 30 15:50:24 Y4M1-II kernel: [drm:amdgpu_gfx_enable_kcq.cold [amdgpu]] *ERROR* KCQ enable failed Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SMU is initialized successfully! Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: use vbios provided pptable Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SMU driver if version not matched Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: smu driver if version = 0x003d, smu fw if version = 0x0040, smu fw version = 0x003a4700 (58.71.0) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Will use PSP to load VCN firmware Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: 16368M of GTT memory ready. Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu: 16368M of VRAM memory ready Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: AGP: 267894784M 0x0084 - 0x Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: GART: 512M 0x - 0x1FFF Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: VRAM: 16368M 0x0080 - 0x0083FEFF (16368M used) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: SRAM ECC is not presented. Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: MEM ECC is not presented. Jan 30 15:50:24 Y4M1-II kernel: amdgpu: ATOM BIOS: 113-EXT800216-L05 Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Fetched VBIOS from VFCT Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: enabling device (0006 -> 0007) Jan 30 15:50:24 Y4M1-II kernel: amdgpu :0c:00.0: vgaarb: deactivate vga console Jan 30 15:50:24 Y4M1-II kernel: fb0: switching to amdgpudrmfb from EFI VGA Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Topology: Add CPU node Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Virtual CRAT table created for CPU Jan 30 15:50:24 Y4M1-II kernel: amdgpu: Ignoring ACPI CRAT on non-APU system Jan 30 15:50:24 Y4M1-II kernel: [drm] amdgpu kernel modesetting enabled. Jan
[Touch-packages] [Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
Seems like killing your Xwayland process is an easy way to reproduce this crash. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing in GTK since the introduction of GNOME 40. https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad . ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+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 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing in GTK since the introduction of GNOME 40. https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad . ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+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 1966836] [NEW] package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Public bug reported: Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) This has been happening over the last month. Error prints after apt upgrade. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Mar 28 23:10:08 2022 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-02-12 (44 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: lvm2 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1966836 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: New Bug description: Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) This has been happening over the last month. Error prints after apt upgrade. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Mar 28 23:10:08 2022 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-02-12 (44 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: lvm2 Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1966836/+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 1966436] Re: Bluetooth fails to connect "br-connection-profile-unavailable"
Oh this is KDE too, so I wonder if that chooses PipeWire instead of PulseAudio. If so then please try a regular Ubuntu 22.04 live session (GNOME). -- 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/1966436 Title: Bluetooth fails to connect "br-connection-profile-unavailable" Status in bluez package in Ubuntu: New Status in pipewire package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: How to reproduce: > bluetoothctl scan on Discovery started ... > bluetoothctl connect 94:DB:56:8E:0B:96 Attempting to connect to 94:DB:56:8E:0B:96 Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable > systemctl status bluetooth bluetooth.service - Bluetooth service Loaded: loaded ... mars 25 12:39:08 ncelrnd2375 bluetoothd[1282]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 94:DB:56:8E:0B:96: Protocol not available Notes: kernel-5.15, bluez-5.64 Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth Dell Precision 3560 Unfortunately I did not test before upgrade to 22.04. Tried installing pipewire-pulse, blueman, but this is lower-level. There are reports of similar errors popping up in Arch and Manjaro recently: https://bbs.archlinux.org/viewtopic.php?id=270465 https://forum.manjaro.org/t/bluetooth-ko-with-kernel-5-16/99913 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Mar 25 12:56:34 2022 InstallationDate: Installed on 2022-03-04 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision 3560 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/AmadeUbuntu20-root ro audit=1 acpi_rev_override load_nvme=YES nouveau.modeset=0 dis_ucode_ldr quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-03-22 (3 days ago) dmi.bios.date: 09/13/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.2 dmi.board.name: 095HH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.2:bd09/13/2021:br1.12:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn095HH7:rvrA00:cvnDellInc.:ct10:cvr:sku0A22: dmi.product.family: Precision dmi.product.name: Precision 3560 dmi.product.sku: 0A22 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 44:E5:17:BC:00:DD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:24189 acl:41 sco:0 events:519 errors:0 TX bytes:8252 acl:33 sco:0 commands:239 errors:0 modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1966436/+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 1966436] Re: Bluetooth fails to connect "br-connection-profile-unavailable"
What is the model of the Bluetooth device/headphones/speaker? -- 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/1966436 Title: Bluetooth fails to connect "br-connection-profile-unavailable" Status in bluez package in Ubuntu: New Status in pipewire package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: How to reproduce: > bluetoothctl scan on Discovery started ... > bluetoothctl connect 94:DB:56:8E:0B:96 Attempting to connect to 94:DB:56:8E:0B:96 Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable > systemctl status bluetooth bluetooth.service - Bluetooth service Loaded: loaded ... mars 25 12:39:08 ncelrnd2375 bluetoothd[1282]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 94:DB:56:8E:0B:96: Protocol not available Notes: kernel-5.15, bluez-5.64 Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth Dell Precision 3560 Unfortunately I did not test before upgrade to 22.04. Tried installing pipewire-pulse, blueman, but this is lower-level. There are reports of similar errors popping up in Arch and Manjaro recently: https://bbs.archlinux.org/viewtopic.php?id=270465 https://forum.manjaro.org/t/bluetooth-ko-with-kernel-5-16/99913 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Mar 25 12:56:34 2022 InstallationDate: Installed on 2022-03-04 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision 3560 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/AmadeUbuntu20-root ro audit=1 acpi_rev_override load_nvme=YES nouveau.modeset=0 dis_ucode_ldr quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-03-22 (3 days ago) dmi.bios.date: 09/13/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.2 dmi.board.name: 095HH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.2:bd09/13/2021:br1.12:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn095HH7:rvrA00:cvnDellInc.:ct10:cvr:sku0A22: dmi.product.family: Precision dmi.product.name: Precision 3560 dmi.product.sku: 0A22 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 44:E5:17:BC:00:DD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:24189 acl:41 sco:0 events:519 errors:0 TX bytes:8252 acl:33 sco:0 commands:239 errors:0 modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1966436/+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 1965563] Re: gnome-extensions-app fails to start (Protocol error)
Timo, was it bug 1966221 that you meant to assign to mesa? Regardless, I think we should keep a gnome-shell task here just to make the bug easier to find, and avoid duplicates. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1965563 Title: gnome-extensions-app fails to start (Protocol error) Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: $ dpkg-query -W gnome-shell-extension-prefs gnome-shell-extension-prefs 42~beta-1ubuntu3 $ gnome-extensions-app Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error Caveat: I currently have a mix of packages from jammy-release and jammy-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+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 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
Yes the yelp->gtk->opengl backend has probably changed over the past year. ** Tags removed: hirsute ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop Status in gtk+3.0 package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Status in yelp package in Ubuntu: Confirmed Bug description: On the hirsute Pi desktop, under a wayland session with the "full" KMS overlay enabled, and "kms-modifiers" present in the org.gnome.mutter/experimental-features, the body of a window containing an HTML renderer (e.g. help text or a login page) displays corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+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 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"
** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Confirmed ** Changed in: mesa (Ubuntu) Importance: Undecided => High ** Tags added: crocus -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966221 Title: gnome-extensions-app crashes with "Segmentation fault (core dumped)" Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: when I use the command "gnome-extensions-app" in command line ,it will crash and report "Segmentation fault (core dumped)" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 22:32:21 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-09 (42 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966221/+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 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
This still seems to be an issue on the current Ubuntu Pi Jammy images although it presents in a different manner: instead of an incorrect- stride corruption, the embedded browser (in the same places: help windows, or the login entries for online accounts) simply appears blank white. However, if the mouse cursor is moved across the blank white content of the window, the cursor shape changes to indicate text entry fields or clickable links indicating that the browser is likely operating correctly but failing to render correctly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop Status in gtk+3.0 package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Status in yelp package in Ubuntu: Confirmed Bug description: On the hirsute Pi desktop, under a wayland session with the "full" KMS overlay enabled, and "kms-modifiers" present in the org.gnome.mutter/experimental-features, the body of a window containing an HTML renderer (e.g. help text or a login page) displays corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+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 1965646] Re: pulseaudio missing even though says installed in software center. Have no audio
The laptop jack hardware is the problem. ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => ptosis (ccrandal-7) -- 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/1965646 Title: pulseaudio missing even though says installed in software center. Have no audio Status in pulseaudio package in Ubuntu: Invalid Bug description: Previously: had SoundHissheadphones https://answers.launchpad.net/ubuntu/+question/700984 Messed with pulseaudio until it's totally gone even though on the software center it still says it is installed but unable to remove it because it says: "PulseAudio System Tray": no packages to remove Sudo apt remove pulseaudio Removing pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Setting up pipewire-pulse (0.3.48-1ubuntu1) ... Created symlink /etc/systemd/user/default.target.wants/pipewire-pulse.service → /usr/lib/systemd/user/pipewire-pulse.service. Created symlink /etc/systemd/user/sockets.target.wants/pipewire-pulse.socket → / usr/lib/systemd/user/pipewire-pulse.socket. Processing triggers for man-db (2.10.1-1) ... Processing triggers for libglib2.0-0:amd64 (2.71.3-1) ... sudo apt purge Purging configuration files for pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Processing triggers for dbus (1.12.20-2ubuntu3) . ___ No audio symbol, it's gone Software center still says it is installed. Unable to remove "PulseAudio" in software center Unable to remove"PulseAudio Volume Control": no packages to remove Version 0.17.0 ___ mate-volume-control No device to configure under Hardware Input: unchecked Monitor of Dummy Output Output: unchecked Dummy Output Stereo __ sudo apt-get update -y sudo apt-get install -y pulseaudio Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libsbc1 libssl1.1 linux-headers-5.13.0-19 Use 'sudo apt autoremove' to remove them. Suggested packages: pavumeter paprefs ubuntu-sounds The following NEW packages will be installed: pulseaudio 0 upgraded, 1 newly installed, 0 to remove and 7 not upgraded. Need to get 0 B/913 kB of archives. After this operation, 4,674 kB of additional disk space will be used. Selecting previously unselected package pulseaudio. (Reading database ... 321785 files and directories currently installed.) Preparing to unpack .../pulseaudio_1%3a15.99.1+dfsg1-1ubuntu1_amd64.deb ... Unpacking pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Setting up pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Adding user pulse to group audio Created symlink /etc/systemd/user/default.target.wants/pulseaudio.service → /usr/lib/systemd/user/pulseaudio.service. Created symlink /etc/systemd/user/sockets.target.wants/pulseaudio.socket → /usr/lib/systemd/user/pulseaudio.socket. Processing triggers for man-db (2.10.1-1) ... Processing triggers for dbus (1.12.20-2ubuntu3) ...y sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: libsbc1 libssl1.1 linux-headers-5.13.0-19 0 upgraded, 0 newly installed, 3 to remove and 7 not upgraded. After this operation, 80.1 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 321976 files and directories currently installed.) Removing libsbc1:amd64 (1.5-3build1) ... Removing libssl1.1:amd64 (1.1.1l-1ubuntu1) ... Removing linux-headers-5.13.0-19 (5.13.0-19.19) ... Processing triggers for libc-bin (2.35-0ubuntu3) ... pulseaudio W: [pulseaudio] pid.c: Stale PID file, overwriting. E: [pulseaudio] socket-server.c: bind(): Address already in use E: [pulseaudio] module.c: Failed to load module "module-native-protocol-unix" (argument: ""): initialization failed. E: [pulseaudio] main.c: D-Bus name org.pulseaudio.Server already taken. pulseaudio -k E: [pulseaudio] main.c: Failed to kill daemon: No such process __ ubuntu-bug -s audio Package pulseaudio 1:15:99.1+dgsg1-1ubuntu1 2.20.11-Outbuntu79 __ killall pulseaudio; pulseaudio -k ; rm -r ~/.config/pulse/* ; rm -r ~/.pulse* rm -r ~/.pulse* pulseaudio: no process found E: [pulseaudio] main.c: Failed to kill daemon: No such process rm: cannot remove '/home/ptosis/.pulse*': No such file or directory pulseaudio --start waited 10 seconds, then reboot wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x ./alsa-info.sh && ./alsa-info.sh bash alsa-info.sh --stdout AFTER
[Touch-packages] [Bug 1965646] Re: pulseaudio missing even though says installed in software center. Have no audio
Solved:Marko Stanković solved no audio with https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1963934 The laptop's jack is jacked. Bought another 5755 and put 20.04 on it and works perfectly with zero intervention. -- 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/1965646 Title: pulseaudio missing even though says installed in software center. Have no audio Status in pulseaudio package in Ubuntu: Invalid Bug description: Previously: had SoundHissheadphones https://answers.launchpad.net/ubuntu/+question/700984 Messed with pulseaudio until it's totally gone even though on the software center it still says it is installed but unable to remove it because it says: "PulseAudio System Tray": no packages to remove Sudo apt remove pulseaudio Removing pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Setting up pipewire-pulse (0.3.48-1ubuntu1) ... Created symlink /etc/systemd/user/default.target.wants/pipewire-pulse.service → /usr/lib/systemd/user/pipewire-pulse.service. Created symlink /etc/systemd/user/sockets.target.wants/pipewire-pulse.socket → / usr/lib/systemd/user/pipewire-pulse.socket. Processing triggers for man-db (2.10.1-1) ... Processing triggers for libglib2.0-0:amd64 (2.71.3-1) ... sudo apt purge Purging configuration files for pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Processing triggers for dbus (1.12.20-2ubuntu3) . ___ No audio symbol, it's gone Software center still says it is installed. Unable to remove "PulseAudio" in software center Unable to remove"PulseAudio Volume Control": no packages to remove Version 0.17.0 ___ mate-volume-control No device to configure under Hardware Input: unchecked Monitor of Dummy Output Output: unchecked Dummy Output Stereo __ sudo apt-get update -y sudo apt-get install -y pulseaudio Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libsbc1 libssl1.1 linux-headers-5.13.0-19 Use 'sudo apt autoremove' to remove them. Suggested packages: pavumeter paprefs ubuntu-sounds The following NEW packages will be installed: pulseaudio 0 upgraded, 1 newly installed, 0 to remove and 7 not upgraded. Need to get 0 B/913 kB of archives. After this operation, 4,674 kB of additional disk space will be used. Selecting previously unselected package pulseaudio. (Reading database ... 321785 files and directories currently installed.) Preparing to unpack .../pulseaudio_1%3a15.99.1+dfsg1-1ubuntu1_amd64.deb ... Unpacking pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Setting up pulseaudio (1:15.99.1+dfsg1-1ubuntu1) ... Adding user pulse to group audio Created symlink /etc/systemd/user/default.target.wants/pulseaudio.service → /usr/lib/systemd/user/pulseaudio.service. Created symlink /etc/systemd/user/sockets.target.wants/pulseaudio.socket → /usr/lib/systemd/user/pulseaudio.socket. Processing triggers for man-db (2.10.1-1) ... Processing triggers for dbus (1.12.20-2ubuntu3) ...y sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: libsbc1 libssl1.1 linux-headers-5.13.0-19 0 upgraded, 0 newly installed, 3 to remove and 7 not upgraded. After this operation, 80.1 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 321976 files and directories currently installed.) Removing libsbc1:amd64 (1.5-3build1) ... Removing libssl1.1:amd64 (1.1.1l-1ubuntu1) ... Removing linux-headers-5.13.0-19 (5.13.0-19.19) ... Processing triggers for libc-bin (2.35-0ubuntu3) ... pulseaudio W: [pulseaudio] pid.c: Stale PID file, overwriting. E: [pulseaudio] socket-server.c: bind(): Address already in use E: [pulseaudio] module.c: Failed to load module "module-native-protocol-unix" (argument: ""): initialization failed. E: [pulseaudio] main.c: D-Bus name org.pulseaudio.Server already taken. pulseaudio -k E: [pulseaudio] main.c: Failed to kill daemon: No such process __ ubuntu-bug -s audio Package pulseaudio 1:15:99.1+dgsg1-1ubuntu1 2.20.11-Outbuntu79 __ killall pulseaudio; pulseaudio -k ; rm -r ~/.config/pulse/* ; rm -r ~/.pulse* rm -r ~/.pulse* pulseaudio: no process found E: [pulseaudio] main.c: Failed to kill daemon: No such process rm: cannot remove '/home/ptosis/.pulse*': No such file or directory pulseaudio --start waited 10 seconds, then reboot wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x ./alsa-info.sh && ./alsa-info.sh bash
[Touch-packages] [Bug 1966813] [NEW] package cron 3.0pl1-128ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: cron could not be installed while updating 16.04 to 18.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cron 3.0pl1-128ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic i686 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: i386 Date: Mon Mar 28 21:16:55 2022 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-10-01 (3100 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) RelatedPackageVersions: dpkg 1.18.4ubuntu1.7 apt 1.2.35 SourcePackage: cron Title: package cron 3.0pl1-128ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2022-03-28 (0 days ago) ** Affects: cron (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1966813 Title: package cron 3.0pl1-128ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in cron package in Ubuntu: New Bug description: cron could not be installed while updating 16.04 to 18.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cron 3.0pl1-128ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-210.242-generic 4.4.262 Uname: Linux 4.4.0-210-generic i686 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: i386 Date: Mon Mar 28 21:16:55 2022 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-10-01 (3100 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) RelatedPackageVersions: dpkg 1.18.4ubuntu1.7 apt 1.2.35 SourcePackage: cron Title: package cron 3.0pl1-128ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2022-03-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1966813/+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 1965830] Re: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float'
** Branch linked: lp:~ubuntu-core-dev/ubuntu/jammy/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1965830 Title: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' Status in apport package in Ubuntu: In Progress Status in apport source package in Jammy: In Progress Bug description: this crash did happen after i successfully submitted my last report. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: apport-kde 2.20.11-0ubuntu79 ProcVersionSignature: Ubuntu 5.15.0-23.23-lowlatency 5.15.27 Uname: Linux 5.15.0-23-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Mar 21 18:22:47 2022 ExecutablePath: /usr/share/apport/apport-kde InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-kde ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= SHELL=/bin/bash LANG=de_DE.UTF-8 Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/share/apport/apport-kde'] PythonDetails: N/A SourcePackage: apport Title: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm games lpadmin plugdev sudo users vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1965830/+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 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi
** Tags added: fr-2147 -- 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/1947311 Title: Unexpected partition growth on first boot on impish for raspberry pi Status in cloud-init package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Invalid Status in ubuntu-image package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Hi, On Raspberry Pi since Impish, the partition always grows even if I set the following in user-data of cloud-init. growpart: mode: off devices: ['/'] I have tested this on 21.04, and it works, but is broken on 21.10. (partition always grows) I've also tested this in KVM on amd64, and it works (partition does NOT grow). This is a problem for me because I am using runcmd in cloud init to migrate my drive to LVM/LUKS, and the partitioning step fails because the drive is already full. Cheers, Noah To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+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 1965830] Re: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float'
** Changed in: apport (Ubuntu Jammy) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport (Ubuntu Jammy) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1965830 Title: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' Status in apport package in Ubuntu: In Progress Status in apport source package in Jammy: In Progress Bug description: this crash did happen after i successfully submitted my last report. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: apport-kde 2.20.11-0ubuntu79 ProcVersionSignature: Ubuntu 5.15.0-23.23-lowlatency 5.15.27 Uname: Linux 5.15.0-23-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Mar 21 18:22:47 2022 ExecutablePath: /usr/share/apport/apport-kde InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-kde ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= SHELL=/bin/bash LANG=de_DE.UTF-8 Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/share/apport/apport-kde'] PythonDetails: N/A SourcePackage: apport Title: apport-kde crashed with setGeometry(self, int, int, int, int) in ui_start_info_collection_progress(): argument 1 has unexpected type 'float' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm games lpadmin plugdev sudo users vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1965830/+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 1966416] Re: pam_faillock does not actually deny login after given number of failures
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1966416
Title:
pam_faillock does not actually deny login after given number of
failures
Status in pam package in Ubuntu:
New
Bug description:
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libpam-modules 1.4.0-11ubuntu1
I just noticed that Ubuntu 22.04 changed from the old pam_tally2
module to the more widespread pam_faillock one. \o/
However, locking (denying logins) does not actually seem to work.
According to pam_faillock(8) I changed the config like this:
# diff -u /etc/pam.d/common-auth{.orig,}
--- /etc/pam.d/common-auth.orig 2022-03-25 10:41:29.08800 +
+++ /etc/pam.d/common-auth2022-03-25 10:48:48.913419254 +
@@ -17,11 +17,11 @@
auth [success=2 default=ignore] pam_unix.so nullok
auth [success=1 default=ignore] pam_sss.so use_first_pass
# here's the fallback if no module succeeds
-auth requisite pam_deny.so
+auth [default=die] pam_faillock.so authfail
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
-auth requiredpam_permit.so
+auth sufficient pam_faillock.so authsucc
# and here are more per-package modules (the "Additional" block)
auth optionalpam_cap.so
# end of pam-auth-update config
This config works fine on both Debian 11 and Debian testing, and it agrees
with the example in the manpage -- so I don't think it's that broken.
Start from a blank slate:
# faillock --user admin --reset
# faillock --user admin
admin:
WhenType Source
Valid
Now I log in as user "admin" with a wrong password four times (one
more than the default "deny=3", just to make sure):
sshd[3841]: pam_unix(sshd:auth): authentication failure; logname= uid=0
euid=0 tty=ssh ruser= rhost=172.27.0.2 user=admin
sshd[3841]: Failed password for admin from 172.27.0.2 port 39446 ssh2
After the third time, I even see this in the journal:
sshd[3841]: Failed password for admin from 172.27.0.2 port 39446 ssh2
pam_faillock(sshd:auth): Consecutive login failures for user admin account
temporarily locked
Failed password for admin from 172.27.0.2 port 39446 ssh2
But if I then log in with the correct password, it succeeds:
sshd[4492]: Accepted password for admin from 172.27.0.2 port 39450 ssh2
sshd[4492]: pam_unix(sshd:session): session opened for user admin(uid=1000)
by (uid=0)
That's buggy -- "admin" should be denied access for ten minutes
("unlock_time = 600" in /etc/security/faillock.conf).
It did record the failed logins alright:
# faillock --user admin
admin:
WhenType Source
Valid
2022-03-25 10:54:02 RHOST 172.27.0.2
V
2022-03-25 10:54:27 RHOST 172.27.0.2
V
2022-03-25 10:54:30 RHOST 172.27.0.2
V
But the actual denial doesn't seem to work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1966416/+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 1946388] Re: Journalctl -f --file some.journal causes coredump
Hello Marko, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.16 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1946388 Title: Journalctl -f --file some.journal causes coredump Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: Fix Committed Bug description: [impact] journalctl -f --file FILE results in segfault [test case] $ journalctl -f --file $FILENAME [regression potential] journalctl segfault or failure to properly operate [scope] needed in focal fixed upstream in 2b6df46d21a at v246, so fixed already in h and later [original description] Focal latest systemd 245. Journalctl -f --file path/to/file.journal. Will allways causes journalctl crash... The same doesnt happen on centos8 systemd 239... I couldnt test on any more systems atm. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1946388/+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 1955997] Re: The airplane hotkey has no function on a HP platform
Hello jeremyszu, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.16 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: systemd (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1955997
Title:
The airplane hotkey has no function on a HP platform
Status in OEM Priority Project:
Triaged
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Fix Committed
Status in systemd source package in Impish:
Fix Committed
Status in systemd source package in Jammy:
Fix Released
Bug description:
[Impact]
The airplane hokey doesn't work on HP new generation machines.
[Test Plan]
Press airplane hokey.
Before the patch, nothing happens.
After the patch, the rfkill works as expected.
In some old HP platforms (contains Intel-HID and HPQ6001 in same
machine), the user will aware the airplane mode toggled very quickly
e.g. turn-on and turn-off immediately (or works good without problem,
depends on how DM handles multiple rfkill events).
In this case, you could check:
1. sudo evtest
# You probably could see
# ...
# /dev/input/event8: Intel HID events
# ...
# /dev/input/event11: Wireless hotkeys
# or "HP Wireless hotkeys" depends on your kernel version
2. try to listen these events when pressing airplane key, you will
probably see these two events will send the keycode out.
3. check the components own this event
$ sudo udevadm info -a /dev/input/event11
# ...
# ATTRS{phys}=="hpq6001/input0"
$ sudo udevadm info -a /dev/input/event8
# ...
#DRIVERS=="intel-hid"
4. check your hwdb is affect.
$ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
# If you didn't see anything then it means your intel-hid is unmask.
5. You could report a bug to your DM for dealing with two rfkill events (same
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as
workaround (but it will be overwritten in next upgrade) by adding:
```
evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
```
to /lib/udev/hwdb.d/60-keyboard.hwdb
then
$ systemd-hwdb update
$ udevadm trigger
[Where problems could occur]
In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will
not work but HP confirmed the new HP generation won't contain the HPQ6001 and
also each DM still need to deal with multi-rfkill events because upstream
changes[2].
---
In the last year, HP mentions HP machines need to use hp-wireless
(HPQ6001) as the rfkill source[1].
However, HP confirms the HPQ6001 has been retired in the platforms
since 2022.
In the platforms after 2022, there are two sources of rkfill events
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
Therefore, the upstream already accept the patch[2] to unmask intel-hid and
mention this big change in the NEWS.
This change makes the pre-2022 HP platforms meet the regression since they
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing
function key.
Thus, there is a patch[3] to make sure the GNOME could deal with this case
smoothly.
However, the systemd change will still cause other DEs meet the regression
(xfce, KDE, lxde, etc..).
Backport systemd change to make HP 2022 platforms work is not the best choice
on stable version (focal in this case).
We still need a solution to make airplane key works on 2022 HP platforms
(intel-hid and atkbd only).
The potential solution from my mind that is to maintain a whitelist to unmask
intel-hid in ubuntu-patch in focal, something like:
```
evdev:name:Intel HID
[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Hello Christian, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.16 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Committed Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice.
[Touch-packages] [Bug 1958284] Re: shutdown hangs at "Waiting for process: ..." for 90s, ignoring DefaultTimeoutStopSec
Hello Jean, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.16 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: systemd (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1958284
Title:
shutdown hangs at "Waiting for process: ..." for 90s, ignoring
DefaultTimeoutStopSec
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Fix Committed
Bug description:
[Impact]
The systemd shutdown sequence does not honor systemd-system.conf
settings when waiting for remaining processes. This means that, for
example, if a systemd service specifies KillMode=process and a process
remaining from that service does not properly handle SIGTERM, then the
remaining process will not be killed until after the compiled-in
default value of DefaultTimeoutStopSec (90s), even if the user has
changed the setting of DefaultTimeoutStopSec. In such cases, this
impacts users by significantly increasing the time required for
shutdown/reboot.
[Test Plan]
* Create a new script, /usr/local/bin/loop-ignore-sigterm:
```
#!/bin/bash
loop_forever() {
while true; do sleep 1; done
}
(
trap 'echo Ignoring SIGTERM...' SIGTERM
loop_forever
)
loop_forever
```
This script will spawn a subshell which will loop forever and ignore
SIGTERM. This will force systemd to wait for the subprocess at
reboot/shutdown, and eventually send SIGKILL after TimeoutStopSec
(DefaultTimeoutStopSec in this case).
* Make the script executable:
$ chmod +x /usr/local/bin/loop-ignore-sigterm
* Create a systemd service for this script. Add the following to
/etc/systemd/system/loop-ignore-sigterm.service:
```
[Service]
KillMode=process
ExecStart=/usr/local/bin/loop-ignore-sigterm
```
* Start the service:
$ systemctl start loop-ignore-sigterm.service
* Edit /etc/systemd/system.conf, and uncomment the
'DefaultTimeoutStopSec=90s' line. Modify 90s to something much shorter,
e.g. 20s.
* Re-exec the daemon so this new default takes effect:
$ systemctl daemon-reexec
* Reboot, and monitor the logs. Observe that systemd-shutdown will wait
for the loop-ignore-sigterm process for 90s, instead of the 20s
configured earlier.
[Where problems could occur]
The patch moves the reset_arguments() call to the end of main, which
means reset_arguments() is no longer called before daemon re-execution
(if that branch is taken). If anything in that code path relied on
reset_arguments() being called before re-executing, those assumptions
could be broken. Any such problems would potentially be seen during
daemon re-execution, e.g. when calling systemctl daemon-reexec.
[ Original Description ]
With systemd v245 as shipped with 20.04, the shutdown sequence does
not use the value of `DefaultTimeoutStopSec` to wait for remaining
processes, it instead uses the compiled in default of 90s.
This is most visible with services that use `KillMode=process`
(docker, k8s, k3s, etc...), especially if the remaining processes do
not handle `SIGTERM` or choose to ignore it.
For example:
```
[ OK ] Finished Reboot.
[ OK ] Reached target Reboot.
[ 243.652848 ] systemd-shutdown[1]: Waiting for process: containerd-shim,
containerd-shim, containerd-shim, fluent-bit
--- hangs here for 90s even if DefaultTimeoutStopSec is set to a lower
value ---
```
The bug has been fixed upstream here:
https://github.com/systemd/systemd/commit/7d9eea2bd3d4f83668c7a78754d201b22
Marc was kind
[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform
Hello jeremyszu, or anyone else affected,
Accepted systemd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: systemd (Ubuntu Impish)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-impish
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1955997
Title:
The airplane hotkey has no function on a HP platform
Status in OEM Priority Project:
Triaged
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Fix Committed
Status in systemd source package in Impish:
Fix Committed
Status in systemd source package in Jammy:
Fix Released
Bug description:
[Impact]
The airplane hokey doesn't work on HP new generation machines.
[Test Plan]
Press airplane hokey.
Before the patch, nothing happens.
After the patch, the rfkill works as expected.
In some old HP platforms (contains Intel-HID and HPQ6001 in same
machine), the user will aware the airplane mode toggled very quickly
e.g. turn-on and turn-off immediately (or works good without problem,
depends on how DM handles multiple rfkill events).
In this case, you could check:
1. sudo evtest
# You probably could see
# ...
# /dev/input/event8: Intel HID events
# ...
# /dev/input/event11: Wireless hotkeys
# or "HP Wireless hotkeys" depends on your kernel version
2. try to listen these events when pressing airplane key, you will
probably see these two events will send the keycode out.
3. check the components own this event
$ sudo udevadm info -a /dev/input/event11
# ...
# ATTRS{phys}=="hpq6001/input0"
$ sudo udevadm info -a /dev/input/event8
# ...
#DRIVERS=="intel-hid"
4. check your hwdb is affect.
$ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
# If you didn't see anything then it means your intel-hid is unmask.
5. You could report a bug to your DM for dealing with two rfkill events (same
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as
workaround (but it will be overwritten in next upgrade) by adding:
```
evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
```
to /lib/udev/hwdb.d/60-keyboard.hwdb
then
$ systemd-hwdb update
$ udevadm trigger
[Where problems could occur]
In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will
not work but HP confirmed the new HP generation won't contain the HPQ6001 and
also each DM still need to deal with multi-rfkill events because upstream
changes[2].
---
In the last year, HP mentions HP machines need to use hp-wireless
(HPQ6001) as the rfkill source[1].
However, HP confirms the HPQ6001 has been retired in the platforms
since 2022.
In the platforms after 2022, there are two sources of rkfill events
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
Therefore, the upstream already accept the patch[2] to unmask intel-hid and
mention this big change in the NEWS.
This change makes the pre-2022 HP platforms meet the regression since they
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing
function key.
Thus, there is a patch[3] to make sure the GNOME could deal with this case
smoothly.
However, the systemd change will still cause other DEs meet the regression
(xfce, KDE, lxde, etc..).
Backport systemd change to make HP 2022 platforms work is not the best choice
on stable version (focal in this case).
We still need a solution to make airplane key works on 2022 HP platforms
(intel-hid and atkbd only).
The potential solution from my mind that is to maintain a whitelist to unmask
intel-hid in ubuntu-patch in focal, something like:
```
[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Hello Christian, or anyone else affected, Accepted systemd into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Impish) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Committed Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Committed Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update
[Touch-packages] [Bug 1962038] Re: wrong sysrq value in /usr/lib/sysctl.d/50-default.conf
Hello Steve, or anyone else affected, Accepted systemd into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Impish) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962038 Title: wrong sysrq value in /usr/lib/sysctl.d/50-default.conf Status in procps package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in procps source package in Impish: Won't Fix Status in systemd source package in Impish: Fix Committed Status in procps source package in Jammy: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] I've just learned that systemd is setting kernel.sysrq to 16 in /usr/lib/sysctl.d/50-default.conf. This is inconsistent with /etc/sysctl.d/10-magic-sysrq.conf which intentionally sets it to 176 by default. systemd should drop its setting to defer to the file that we have been carrying in procps for a very long time. Therefore, users can only sync their storage but not do any other actions using the magic sysrq key. [Test Plan] $ sysctl kernel.sysrq => This should show "kernel.sysrq = 176" as set by /etc/sysctl.d/10-magic-sysrq.conf $ sysctl net.ipv4.conf.all.rp_filter => This should show "net.ipv4.conf.all.rp_filter=2" as set by /etc/sysctl.d/10-network-security.conf [Where problems could occur] * This patch changes systemd's sysctl configuration in /lib/sysctl.d/*.conf * If something is broken it could fail to apply any of systemd's sysctl configuration, but Ubuntu's defaults from /etc/sysctl.d/*.conf would still be in place. [Other Info] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1962038/+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 1966519] Re: hard shutdown after close laptop lid
Hello, do you think that update to ubuntu 22.04 fix the problem, if it is the kernel issue? I could revert back changes that i made in systemd' s logind.conf and run the log command again, or it is not necessary? Thanks Matej Valasek Dne 28. 03. 22 v 10:36 Daniel van Vugt napsal(a): > ** Also affects: systemd (Ubuntu) > Importance: Undecided > Status: New > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1966519 Title: hard shutdown after close laptop lid Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: shutdown on close screen lid and when i reopen the lid it is completely shutdown and i must press the power button and start boot sequence, i have set in gnome-tweaks action,the after close the lid memory suspend, but evidently it is not working. Sorry for my english. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 20:59:38 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.32, 5.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d3) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Cezanne [103c:8895] InstallationDate: Installed on 2022-03-23 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210502) MachineType: HP HP EliteBook 845 G8 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-37-generic root=UUID=e3adb113-cca4-4316-9c3b-edc124da9ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2022 dmi.bios.release: 8.3 dmi.bios.vendor: HP dmi.bios.version: T82 Ver. 01.08.03 dmi.board.name: 8895 dmi.board.vendor: HP dmi.board.version: KBC Version 43.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 67.42 dmi.modalias: dmi:bvnHP:bvrT82Ver.01.08.03:bd02/11/2022:br8.3:efr67.42:svnHP:pnHPEliteBook845G8NotebookPC:pvr:rvnHP:rn8895:rvrKBCVersion43.2A.00:cvnHP:ct10:cvr:sku48R69EA#BCM: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 845 G8 Notebook PC dmi.product.sku: 48R69EA#BCM dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.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-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966519/+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 1966800] Re: systemd locks up due to incorrect handling of time zone changes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1966800 Title: systemd locks up due to incorrect handling of time zone changes Status in systemd package in Ubuntu: Confirmed Status in systemd package in Fedora: Unknown Bug description: Recently on systems in Ireland, systemd became unresponsive due the change from GMT to Irish Standard Time. This is due to Ireland being unique in having their standard time during the summer, unlike most regions. Related to: https://bugzilla.redhat.com/show_bug.cgi?id=1941335 Fixed by: https://github.com/systemd/systemd-stable/commit/a8b66ca9af811148b67ee952ab32748f88b8bba3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966800/+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 1966800] Re: systemd locks up due to incorrect handling of time zone changes
** Bug watch added: Red Hat Bugzilla #1941335 https://bugzilla.redhat.com/show_bug.cgi?id=1941335 ** Also affects: systemd (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1941335 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1966800 Title: systemd locks up due to incorrect handling of time zone changes Status in systemd package in Ubuntu: Confirmed Status in systemd package in Fedora: Unknown Bug description: Recently on systems in Ireland, systemd became unresponsive due the change from GMT to Irish Standard Time. This is due to Ireland being unique in having their standard time during the summer, unlike most regions. Related to: https://bugzilla.redhat.com/show_bug.cgi?id=1941335 Fixed by: https://github.com/systemd/systemd-stable/commit/a8b66ca9af811148b67ee952ab32748f88b8bba3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966800/+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 1966800] [NEW] systemd locks up due to incorrect handling of time zone changes
Public bug reported: Recently on systems in Ireland, systemd became unresponsive due the change from GMT to Irish Standard Time. This is due to Ireland being unique in having their standard time during the summer, unlike most regions. Related to: https://bugzilla.redhat.com/show_bug.cgi?id=1941335 Fixed by: https://github.com/systemd/systemd-stable/commit/a8b66ca9af811148b67ee952ab32748f88b8bba3 ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: systemd (Fedora) Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1966800 Title: systemd locks up due to incorrect handling of time zone changes Status in systemd package in Ubuntu: Confirmed Status in systemd package in Fedora: Unknown Bug description: Recently on systems in Ireland, systemd became unresponsive due the change from GMT to Irish Standard Time. This is due to Ireland being unique in having their standard time during the summer, unlike most regions. Related to: https://bugzilla.redhat.com/show_bug.cgi?id=1941335 Fixed by: https://github.com/systemd/systemd-stable/commit/a8b66ca9af811148b67ee952ab32748f88b8bba3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966800/+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 1966791] [NEW] package initramfs-tools-core 0.136ubuntu6.7 failed to install/upgrade: problèmes de dépendances - laissé non configuré
Public bug reported: the error message is already when i start my computer ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools-core 0.136ubuntu6.7 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: thunderbird-locale-en:amd64: Install thunderbird-locale-fr:amd64: Install thunderbird:amd64: Install thunderbird-gnome-support:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Mar 27 18:58:28 2022 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2021-12-05 (112 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools-core 0.136ubuntu6.7 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1966791 Title: package initramfs-tools-core 0.136ubuntu6.7 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in initramfs-tools package in Ubuntu: New Bug description: the error message is already when i start my computer ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools-core 0.136ubuntu6.7 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: thunderbird-locale-en:amd64: Install thunderbird-locale-fr:amd64: Install thunderbird:amd64: Install thunderbird-gnome-support:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Mar 27 18:58:28 2022 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2021-12-05 (112 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools-core 0.136ubuntu6.7 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1966791/+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 1931024] Re: BOOT fails on UEFI with 100MB initrd.img [Dell XPS 9550]
Same problem today: LUKS FS and stuck at boot on initramfs due to a kernel upgrade, I've no knoledge to solve this easily and going to re- format everything. Fortunately, a live usb allows me to recover my data. -- 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/1931024 Title: BOOT fails on UEFI with 100MB initrd.img [Dell XPS 9550] Status in initramfs-tools package in Ubuntu: Confirmed Bug description: I've been working with a user for the last 2 days on a failure to even start the kernel when installing 20.04 or 21.04 (possibly other releases) with a UEFI boot. System is Dell XPS 9550 amd64 with Ubuntu Budgie. The symptom is that after GRUB successfully loads the kernel into RAM, it fails to return from loading the initrd into RAM. This was proved by adding guard 'echo' and 'sleep' around each stage n grub.cfg. After much investigation since this seemed initially related to a LUKS install I noticed the initrd.img files generated with MODULES=most are 105MB. Most of that is unneeded firmware and other files so I changed to MODULES=dep. Resulting initrd.img's are around 55MB. System then boots correctly. This looks like a possible issue with the UEFI on these XPS models but as initrd.img sizes get ridiculously large this is likely to hit more systems and users. For several years I carry optimisation patches to initramfs-tools that don't add most firmwares except those specifically required (certainly not adding AMD GPU firmware when system has only Intel or Nvidia GPUs - and visa versa) My initrd.img's are a hybrid of MODULES=dep and result in less than 20MB. My recommendation is to add optimisations to initramfs-tools or adopt MODULES=dep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1931024/+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 1966775] [NEW] systemd-resolved fails resolution via TCP
Public bug reported:
It happened in one of our production instances.
Suddenly fails to resolve the hostname.
Later I found it has happened if the DNS response message is bigger than 512
bytes.
But never reproduced from other instances which have the same instance template.
with nslookup
```bash
$ nslookup pod51041.outlook.com
;; Truncated, retrying in TCP mode.
;; Connection to 127.0.0.53#53(127.0.0.53) for pod51041.outlook.com failed:
timed out.
```
and dig with another address.
```bash
$ time dig +noanswer +noedns toomany.ddstreet.org
;; Truncated, retrying in TCP mode.
;; Connection to 127.0.0.53#53(127.0.0.53) for toomany.ddstreet.org failed:
timed out.
real0m7.070s
user0m0.004s
sys 0m0.004s
```
system versions
```bash
$ systemctl --version
systemd 245 (245.4-4ubuntu3.15)
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2
default-hierarchy=hybrid
$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.2 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.2 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
$ uname -r
5.8.0-1041-aws
```
status
```bash
$ resolvectl status
Global
LLMNR setting: no
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test
Link 2 (ens5)
Current Scopes: DNS
DefaultRoute setting: yes
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 172.29.0.2
DNS Servers: 172.29.0.2
DNS Domain: ap-south-1.compute.internal
```
strace to resolved process
```bash
$ strace -fp $(which systemd-resolved)
epoll_pwait(4, [{EPOLLIN, {u32=3491475680, u64=187650612637920}}], 14, -1,
NULL, 8) = 1
recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 38
recvmsg(12, {msg_name={sa_family=AF_INET, sin_port=htons(52259),
sin_addr=inet_addr("127.0.0.1")}, msg_namelen=128->16,
msg_iov=[{iov_base="\344g\1
\0\1\0\0\0\0\0\0\10pod51041\7outlook\3com\0\0\1\0\1", iov_len=3928}],
msg_iovlen=1, msg_control=[{cmsg_len=28, cmsg_level=SOL_IP,
cmsg_type=IP_PKTINFO, cmsg_data={ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}},
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, cmsg_data=[64]}],
msg_controllen=56, msg_flags=0}, 0) = 38
newfstatat(AT_FDCWD, "/etc/hosts", {st_mode=S_IFREG|0644, st_size=262, ...}, 0)
= 0
newfstatat(AT_FDCWD, "/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=752,
...}, 0) = 0
newfstatat(AT_FDCWD, "/run/systemd/resolve/resolv.conf", {st_mode=S_IFREG|0644,
st_size=622, ...}, 0) = 0
newfstatat(AT_FDCWD, "/run/systemd/resolve/stub-resolv.conf",
{st_mode=S_IFREG|0644, st_size=752, ...}, 0) = 0
getrandom("\x62\xe8", 2, GRND_NONBLOCK) = 2
newfstatat(AT_FDCWD, "/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=752,
...}, 0) = 0
newfstatat(AT_FDCWD, "/run/systemd/resolve/resolv.conf", {st_mode=S_IFREG|0644,
st_size=622, ...}, 0) = 0
newfstatat(AT_FDCWD, "/run/systemd/resolve/stub-resolv.conf",
{st_mode=S_IFREG|0644, st_size=752, ...}, 0) = 0
sendmsg(12, {msg_name={sa_family=AF_INET, sin_port=htons(52259),
sin_addr=inet_addr("127.0.0.1")}, msg_namelen=16,
[Touch-packages] [Bug 1966436] Re: Bluetooth fails to connect "br-connection-profile-unavailable"
Indeed audio is also broken since the update (no audio device is found), I didn't think bluetooth audio was related to the wired one, but if so this bug is misrouted. lspci -nnk | grep -A2 Audio :00:1f.3 Audio device [0403]: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller [8086:a0c8] (rev 20) Subsystem: Dell Tiger Lake-LP Smart Sound Technology Audio Controller [1028:0a22] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl aplay --list-devices List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3204 Analog [ALC3204 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] ... up to HDMI 11 sudo dmesg | grep snd [ 293.314241] snd_hda_intel :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 [ 293.314682] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [ 293.314933] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 293.480757] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [ 293.480761] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 293.480762] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 293.480764] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 293.480769] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 293.480770] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 [ 293.480772] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [ 293.480773] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 -- 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/1966436 Title: Bluetooth fails to connect "br-connection-profile-unavailable" Status in bluez package in Ubuntu: New Status in pipewire package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: How to reproduce: > bluetoothctl scan on Discovery started ... > bluetoothctl connect 94:DB:56:8E:0B:96 Attempting to connect to 94:DB:56:8E:0B:96 Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable > systemctl status bluetooth bluetooth.service - Bluetooth service Loaded: loaded ... mars 25 12:39:08 ncelrnd2375 bluetoothd[1282]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 94:DB:56:8E:0B:96: Protocol not available Notes: kernel-5.15, bluez-5.64 Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth Dell Precision 3560 Unfortunately I did not test before upgrade to 22.04. Tried installing pipewire-pulse, blueman, but this is lower-level. There are reports of similar errors popping up in Arch and Manjaro recently: https://bbs.archlinux.org/viewtopic.php?id=270465 https://forum.manjaro.org/t/bluetooth-ko-with-kernel-5-16/99913 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Mar 25 12:56:34 2022 InstallationDate: Installed on 2022-03-04 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision 3560 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/AmadeUbuntu20-root ro audit=1 acpi_rev_override load_nvme=YES nouveau.modeset=0 dis_ucode_ldr quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-03-22 (3 days ago) dmi.bios.date: 09/13/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.2 dmi.board.name: 095HH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.2:bd09/13/2021:br1.12:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn095HH7:rvrA00:cvnDellInc.:ct10:cvr:sku0A22: dmi.product.family: Precision dmi.product.name: Precision 3560 dmi.product.sku: 0A22 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 44:E5:17:BC:00:DD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:24189 acl:41 sco:0 events:519 errors:0 TX bytes:8252 acl:33 sco:0 commands:239 errors:0 modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1966436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1966591] Re: ssh-keygen -R changes known_hosts file permissions (mode)
Thank you for taking the time to report this bug while providing a good reproducer. I was able to reproduce in Focal and Bionic # ssh-keyscan github.com >test_known_hosts # ls -la test_known_hosts -rw-r--r-- 1 root root 656 Mar 28 14:24 test_known_hosts # ssh-keygen -R github.com -f test_known_hosts test_known_hosts updated. Original contents retained as test_known_hosts.old # ls -la test_known_hosts -rw--- 1 root root 0 Mar 28 14:25 test_known_hosts However in Jammy and Impish this is fixed: # ssh-keyscan github.com >test_known_hosts # ls -la test_known_hosts -rw-r--r-- 1 root root 656 Mar 28 14:30 test_known_hosts # ssh-keygen -R github.com -f test_known_hosts test_known_hosts updated. Original contents retained as test_known_hosts.old # ls -la test_known_hosts -rw-r--r-- 1 root root 0 Mar 28 14:31 test_known_hosts With this already being fixed in the newer releases it should just be a matter of finding the relevant commit and adding it to focal and bionic. Thanks ** Also affects: openssh (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: openssh (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: openssh (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: openssh (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: openssh (Ubuntu Impish) Status: New => Fix Released ** Changed in: openssh (Ubuntu Jammy) Status: New => Fix Released ** Changed in: openssh (Ubuntu Bionic) Status: New => Confirmed ** Changed in: openssh (Ubuntu Focal) Status: New => Confirmed ** Tags added: server-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1966591 Title: ssh-keygen -R changes known_hosts file permissions (mode) Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Bionic: Confirmed Status in openssh source package in Focal: Confirmed Status in openssh source package in Impish: Fix Released Status in openssh source package in Jammy: Fix Released Bug description: When I use ssh-keygen -R to remove a host from known_hosts it changes permissions on the file. This causes problems particularly when used on the global known hosts file (/etc/ssh/ssh_known_hosts), because then only root can read it. Programs running non-interactively as non- root users suddenly fail to SSH and it's not immediately obvious why. To reproduce: $ ssh-keyscan github.com >test_known_hosts $ chmod 741 test_known_hosts $ ssh-keygen -R github.com -f test_known_hosts $ stat test_known_hosts ... Access: (0600/-rw---) ... Expected behavior: file permissions remain unchanged (mode 0741 in this example). $ lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 $ apt-cache policy openssh-client openssh-client: Installed: 1:7.6p1-4ubuntu0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1966591/+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 1965563] Re: gnome-extensions-app fails to start (Protocol error)
** Package changed: gnome-shell (Ubuntu) => mesa (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1965563 Title: gnome-extensions-app fails to start (Protocol error) Status in mesa package in Ubuntu: Confirmed Bug description: $ dpkg-query -W gnome-shell-extension-prefs gnome-shell-extension-prefs 42~beta-1ubuntu3 $ gnome-extensions-app Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error Caveat: I currently have a mix of packages from jammy-release and jammy-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1965563/+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 1965563] [NEW] gnome-extensions-app fails to start (Protocol error)
You have been subscribed to a public bug: $ dpkg-query -W gnome-shell-extension-prefs gnome-shell-extension-prefs 42~beta-1ubuntu3 $ gnome-extensions-app Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error Caveat: I currently have a mix of packages from jammy-release and jammy- proposed. ** Affects: mesa (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: jammy wayland wayland-session -- gnome-extensions-app fails to start (Protocol error) https://bugs.launchpad.net/bugs/1965563 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
The only current interactivity detection code in pam is part of a pam.conf -> pam.d conversion tool that won't be useful here. The pam_motd code emits content via things like try_to_display_fd. A message is created and then printed via pam_info. Which is actually pam_prompt which wraps pam_vprompt This gets the conversation function via retval = pam_get_item (pamh, PAM_CONV, ); and on that it then emits the message retval = conv->conv (1, , _resp, conv->appdata_ptr); Either via this PAM_CONV and then attributes of that channel (as it is what we'd print on) OR via something like pam_get_item(pamh, PAM_TTY, ); we might get access from pam_motd to something that we can work out if it is interactive. I'm busy with other things now (for the rest of today), but I want ton continue tomorrow. I want this at least to get into a clear state that is sure if: a) this is as important as I think b) the steps needed from here are clear ** Also affects: pam (Ubuntu) Importance: Undecided Status: New ** Changed in: pam (Ubuntu) Status: New => Confirmed ** Changed in: update-motd (Ubuntu) Status: Triaged => Confirmed ** Changed in: pam (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1893716 Title: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions Status in pam package in Ubuntu: Confirmed Status in update-motd package in Ubuntu: Confirmed Bug description: My client has 200+ devices automatically uploading information via sftp and scp to a server every few minutes. After a recent update, I noticed the load on their server spiking through the roof. Upon investigation, I discovered a horde of landscape-sysinfo and /usr/bin/lsb_release processes running that correlated with login session notifications in /var/log/syslog and the load spikes. It appears that even in non-interactive sessions where this information will never be seen, the configuration options below in /etc/pam.d/sshd cause these items to be launched (in fact, probably everything in /etc/update-motd.d). This only started on the system in question after a recent set of system updates were installed. The content of /etc/update-motd.d/* really, really, really shouldn't be executed if the session in question is not interactive, as it provides no value at all. Unfortunately, to disable it for these non- interactive sessions, we also have to disable it for the interactive ones as well where it has some value (though not enough to make spiking the load on this server through the roof an acceptable tradeoff). # Print the message of the day upon successful login. # This includes a dynamically generated part from /run/motd.dynamic # and a static (admin-editable) part from /etc/motd. #sessionoptional pam_motd.so motd=/run/motd.dynamic #sessionoptional pam_motd.so noupdate Also, looking at the script 00-header in /etc/update-motd.d/, /usr/bin/lsb_release is being improperly launched, as /etc/lsb_release does include the necessary information: [ -r /etc/lsb-release ] && . /etc/lsb-release if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then # Fall back to using the very slow lsb_release utility DISTRIB_DESCRIPTION=$(lsb_release -s -d) fi # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1893716/+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 1966418] Re: [jammy regression] Evolution does not display message content anymore
Launchpad has imported 13 comments from the remote bug at https://bugs.webkit.org/show_bug.cgi?id=238244. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2022-03-23T05:43:23+00:00 Adrian Vovk wrote: In a recent mass upgrade in my distro, I upgraded WebKitGTK to 2.36.0 (among other packages). I'm now finding that the webview is blank in all the apps that use it (epiphany, Yelp). The web inspector shows up fine, and when I move the cursor around the screen it changes as if it were hovering over the actual web content. Running either yelp or epiphany with WEBKIT_DISABLE_COMPOSITING_MODE=1 makes the webviews work correctly again, so I suspect this is an issue with the accelerated hardware compositing. Not sure what libraries are involved with that, so I don't know which versions to give you. I'm happy to provide whatever you need to track down the bug! Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/comments/0 On 2022-03-23T05:54:55+00:00 Adrian Vovk wrote: Not sure if this is related, but when I start epiphany w/o the environment variable, I get this warning and xdg-desktop-portal segfaults while trying to handle MakeThreadRealtimeWithPID $ epiphany (WebKitWebProcess:2): Gdk-WARNING **: 01:48:32.563: Failed to read portal settings: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable (WebKitWebProcess:2): Gdk-WARNING **: 01:48:32.563: Failed to read portal settings: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable when the environment variable is set, the crash still seems to happen, but the warning becomes hit-or-miss (either happening once or none at all) and epiphany starts rendering webpages correctly. Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/comments/1 On 2022-03-23T13:42:19+00:00 Pgriffis wrote: > I get this warning and xdg-desktop-portal segfaults while trying to handle MakeThreadRealtimeWithPID You need `xdg-desktop-portal` 1.12.2 or 1.14.0 to fix that. Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/comments/2 On 2022-03-23T13:54:11+00:00 Michael Catanzaro wrote: (In reply to Adrian Vovk from comment #0) > Running either yelp or epiphany with > WEBKIT_DISABLE_COMPOSITING_MODE=1 makes the webviews work correctly again, > so I suspect this is an issue with the accelerated hardware compositing. I agree. > Not > sure what libraries are involved with that, so I don't know which versions > to give you. I'm happy to provide whatever you need to track down the bug! Try loading webkit://gpu and paste the output here. The flaw in this plan is that it probably won't load unless you use WEBKIT_DISABLE_COMPOSITING_MODE=1, which will impact the results it shows, but we'll just have to keep that in mind. Reply at: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/comments/3 On 2022-03-23T16:27:10+00:00 Adrian Vovk wrote: > You need `xdg-desktop-portal` 1.12.2 or 1.14.0 to fix that. I'm using xdg-desktop-portal 1.14.1 > Try loading webkit://gpu and paste the output here This causes epiphany to segfault, no matter if the environment variable is set. Here's the backtrace of this crash: #0 0x7f9f4c1b534e _ZN6WebKit21WebKitProtocolHandler9handleGPUEP23_WebKitURISchemeRequest (libwebkit2gtk-4.0.so.37 + 0xba634e) #1 0x7f9f4c1b57ab _ZN6WebKit21WebKitProtocolHandler13handleRequestEP23_WebKitURISchemeRequest (libwebkit2gtk-4.0.so.37 + 0xba67ab) #2 0x7f9f4c1cf69e _ZN22WebKitURISchemeHandler17platformStartTaskERN6WebKit12WebPageProxyERNS0_16WebURLSchemeTaskE (libwebkit2gtk-4.0.so.37 + 0xbc069e) #3 0x7f9f4c119a50 _ZN6WebKit12WebPageProxy24startURLSchemeTaskSharedEON3WTF3RefINS_15WebProcessProxyENS1_12RawPtrTraitsIS3_NS1_16ObjectIdentifierIN7WebCore18PageIdentifierT> #4 0x7f9f4c119b3a _ZN6WebKit12WebPageProxy18startURLSchemeTaskEONS_23URLSchemeTaskParametersE (libwebkit2gtk-4.0.so.37 + 0xb0ab3a) #5 0x7f9f4bdac8f3 _ZN3IPC13handleMessageIN8Messages12WebPageProxy18StartURLSchemeTaskEN6WebKit12WebPageProxyEMS5_FvONS4_23URLSchemeTaskParametersvRNS_10ConnectionERNS_7Deco> #6 0x7f9f4bd9f404 _ZN6WebKit12WebPageProxy17didReceiveMessageERN3IPC10ConnectionERNS1_7DecoderE (libwebkit2gtk-4.0.so.37 + 0x790404) #7 0x7f9f4c01868b _ZN3IPC18MessageReceiverMap15dispatchMessageERNS_10ConnectionERNS_7DecoderE (libwebkit2gtk-4.0.so.37 + 0xa0968b) #8
[Touch-packages] [Bug 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: intel-media-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966571 Title: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Status in intel-media-driver package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: I noticed that it upgraded mesa to 22.x and now video acceleration is not working due to: ❯ vainfo libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_10 libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit ~/Desktop ❯ inxi -G Graphics: Device-1: Intel driver: i915 v: kernel Device-2: Generalplus GENERAL WEBCAM type: USB driver: snd-usb-audio,uvcvideo Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 3840x2160~60Hz OpenGL: renderer: Mesa Intel UHD Graphics P630 (CML GT2) v: 4.6 Mesa 22.0.0 I tried rebuilding the i965-va-driver, and it's still the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mesa-vdpau-drivers 22.0.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 27 10:37:41 2022 DistUpgraded: 2022-01-18 23:59:55,390 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl88x2bu/5.8.7.1, 5.15.0-18-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.15.0-22-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.15.0-23-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.17.0-xanmod1, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9bc6] (rev 05) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-10-05 (172 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=018d5b69-accd-451b-a6f7-2027f791ea0e ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2022-01-18 (67 days ago) dmi.bios.date: 07/08/2021 dmi.bios.release: 23.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: Default string dmi.board.name: Pro WS W480-ACE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/08/2021:br23.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSW480-ACE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1966571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1964274] Re: Xwayland crashes with wl_display@1: error 1: invalid arguments for wl_shm@6.create_pool
I guess mutter side can be closed, since we've already beta in archive. ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1964274 Title: Xwayland crashes with wl_display@1: error 1: invalid arguments for wl_shm@6.create_pool Status in X.Org X server: Unknown Status in mutter package in Ubuntu: Fix Released Status in wayland package in Ubuntu: In Progress Status in xwayland package in Ubuntu: Fix Released Bug description: System : Ubuntu 21.10 Kernel 5.13.0-35 Session : Wayland Each time I try to rip a CD with "abcde" gnome-shell crashes What I understand from the logs : Before the CD is ripped, abcde downloads a picture (from internet) as a cover of the CD. When tracker-extract discovers this picture something bad happens. Then gnome-shell crashes. After the crash (and re-login into Ubuntu) I can resume the ripping process as the picture has been cached by abcde, and tracker-extract does not interact again with it. Obviously the problem is back for each new CD. The problem appeared quite recently, probably less than 1 month ago. Logs : 00:13:06 host dbus-daemon[3541]: [session uid=1000 pid=3541] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.8' (uid=1000 pid=3573 comm="/usr/libexec/tracker-mi> 00:13:06 host systemd[3523]: Starting Tracker metadata extractor... 00:13:06 host dbus-daemon[3541]: [session uid=1000 pid=3541] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract' 00:13:06 host systemd[3523]: Started Tracker metadata extractor. 00:13:14 host tracker-extract-3[11545]: Not a JPEG file: starts with 0x89 0x50 00:13:14 host tracker-extract[11545]: Task for 'file:///home/user/Downloads/abcde.a80c7f0c/cover.jpg' finished with error: Could not get any metadata for uri:'file:///home/user/Downloads/abcde.a80c7f0c/cover.jpg' and mime:'image/jpeg' 00:13:14 host gnome-shell[3640]: WL: file descriptor expected, object (6), message create_pool(nhi) 00:13:14 host gnome-shell[3640]: WL: error in client communication (pid 3640) 00:13:14 host gnome-shell[4456]: (EE) 00:13:14 host gnome-shell[4456]: Fatal server error: 00:13:14 host gnome-shell[4456]: (EE) wl_display@1: error 1: invalid arguments for wl_shm@6.create_pool 00:13:14 host gnome-shell[4456]: (EE) 00:13:14 host gnome-shell[3640]: Connection to xwayland lost To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1964274/+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 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
** Tags added: rls-jj-incoming ** Changed in: mesa (Ubuntu) Importance: Undecided => High ** Changed in: intel-media-driver (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966571 Title: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Status in intel-media-driver package in Ubuntu: New Status in mesa package in Ubuntu: Confirmed Bug description: I noticed that it upgraded mesa to 22.x and now video acceleration is not working due to: ❯ vainfo libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_10 libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit ~/Desktop ❯ inxi -G Graphics: Device-1: Intel driver: i915 v: kernel Device-2: Generalplus GENERAL WEBCAM type: USB driver: snd-usb-audio,uvcvideo Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 3840x2160~60Hz OpenGL: renderer: Mesa Intel UHD Graphics P630 (CML GT2) v: 4.6 Mesa 22.0.0 I tried rebuilding the i965-va-driver, and it's still the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mesa-vdpau-drivers 22.0.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 27 10:37:41 2022 DistUpgraded: 2022-01-18 23:59:55,390 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl88x2bu/5.8.7.1, 5.15.0-18-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.15.0-22-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.15.0-23-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.17.0-xanmod1, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9bc6] (rev 05) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-10-05 (172 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=018d5b69-accd-451b-a6f7-2027f791ea0e ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2022-01-18 (67 days ago) dmi.bios.date: 07/08/2021 dmi.bios.release: 23.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: Default string dmi.board.name: Pro WS W480-ACE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/08/2021:br23.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSW480-ACE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1966571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1553466] Re: org.gnome.SessionManager was not provided by any .service files
Today, on my Xubuntu system Distributor ID: Ubuntu Description:Ubuntu 20.04.4 LTS Release:20.04 Codename: focal 5.13.0-37-generic x86_64 I saw the error message from the headline of this bug report in /var/log/apport.log: ERROR: apport (pid 27563) Mon Mar 28 11:45:22 2022: called for pid 1770, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 27563) Mon Mar 28 11:45:23 2022: executable: /usr/bin/xfce4-power-manager (command line "xfce4-power-manager") ERROR: apport (pid 27563) Mon Mar 28 11:45:23 2022: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ERROR: apport (pid 27563) Mon Mar 28 11:45:23 2022: debug: session gdbus call: ERROR: apport (pid 27563) Mon Mar 28 11:45:24 2022: wrote report /var/crash/_usr_bin_xfce4-power-manager.1000.crash This occurred on a special installation on my "yellow" USB3 stick (instead of the built-in SSD) that I have made for maintenance purposes. Do I need to worry about the error message? Is it possible that this is why the boot process from the stick takes so long? Trying to find the reason why the boot process takes 2:45 minutes with the screen being black for 1:30 minutes was the reason for me to look for error messages in `/var/log` and on this occasion I came across the error message. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1553466 Title: org.gnome.SessionManager was not provided by any .service files Status in dbus package in Ubuntu: Confirmed Bug description: This is logged into journalctl: org.gnome.ScreenSaver[1755]: ** (gnome-screensaver:1868): WARNING **: Couldn't get presence status: The name org.gnome.SessionManager was not provided by any .service files ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dbus 1.10.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Mar 5 08:37:25 2016 ExecutablePath: /usr/bin/dbus-daemon ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) upstart.dbus.log: Activating service name='org.gnome.Terminal' Successfully activated service 'org.gnome.Terminal' Activating service name='org.gnome.Terminal' Successfully activated service 'org.gnome.Terminal' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1553466/+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 1966418] Re: [jammy regression] Evolution does not display message content anymore
There is a similar discussion upstream on https://bugs.webkit.org/show_bug.cgi?id=238244 ** Bug watch added: bugs.webkit.org/ #238244 https://bugs.webkit.org/show_bug.cgi?id=238244 ** Also affects: webkit via https://bugs.webkit.org/show_bug.cgi?id=238244 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore Status in Webkit: Unknown Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in liferea package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/1966418/+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 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
From https://github.com/intel/media-driver/issues/1366 it looks like a regression with intel-media-va-driver 22.x ** Also affects: intel-media-driver (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/intel/media-driver/issues #1366 https://github.com/intel/media-driver/issues/1366 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966571 Title: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Status in intel-media-driver package in Ubuntu: New Status in mesa package in Ubuntu: Confirmed Bug description: I noticed that it upgraded mesa to 22.x and now video acceleration is not working due to: ❯ vainfo libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_10 libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit ~/Desktop ❯ inxi -G Graphics: Device-1: Intel driver: i915 v: kernel Device-2: Generalplus GENERAL WEBCAM type: USB driver: snd-usb-audio,uvcvideo Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 3840x2160~60Hz OpenGL: renderer: Mesa Intel UHD Graphics P630 (CML GT2) v: 4.6 Mesa 22.0.0 I tried rebuilding the i965-va-driver, and it's still the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mesa-vdpau-drivers 22.0.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 27 10:37:41 2022 DistUpgraded: 2022-01-18 23:59:55,390 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl88x2bu/5.8.7.1, 5.15.0-18-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.15.0-22-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.15.0-23-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.17.0-xanmod1, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9bc6] (rev 05) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-10-05 (172 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=018d5b69-accd-451b-a6f7-2027f791ea0e ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2022-01-18 (67 days ago) dmi.bios.date: 07/08/2021 dmi.bios.release: 23.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: Default string dmi.board.name: Pro WS W480-ACE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/08/2021:br23.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSW480-ACE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1966571/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1965993] Re: [UIFe] Remove Ubuntu Pro settings
** Changed in: software-properties (Ubuntu) Status: Triaged => Fix Committed -- 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/1965993 Title: [UIFe] Remove Ubuntu Pro settings Status in software-properties package in Ubuntu: Fix Committed Bug description: Due to backend delay, we want to remove the Ubuntu Pro settings and only show Livepatch settings as were previously shown. This feature will be re-added at a future time. This change will rename the "Ubuntu Pro" page to "Livepatch" and hide various UI elements. This adds the following new strings for translations: "This machine is not covered by an Ubuntu Advantage subscription." "Ubuntu Advantage subscription attached." "Livepatch" All existing strings for the Ubuntu Pro settings remain, so should remain translated when this change is reverted. See below for screenshots of the change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965993/+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 1966519] Re: hard shutdown after close laptop lid
I am sorry the first on prevboot.txt is bad i don´t understand the whole process of making the file,the second one is right one with these two messages maybe it starts sleeping,but not waking up after reopening. bře 28 10:43:34 matej-laptop systemd-logind[1188]: Lid closed. bře 28 10:43:34 matej-laptop systemd-logind[1188]: Suspending... from prevboot.txt Dne 28. 03. 22 v 10:36 Daniel van Vugt napsal(a): > ** Also affects: systemd (Ubuntu) > Importance: Undecided > Status: New > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1966519 Title: hard shutdown after close laptop lid Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: shutdown on close screen lid and when i reopen the lid it is completely shutdown and i must press the power button and start boot sequence, i have set in gnome-tweaks action,the after close the lid memory suspend, but evidently it is not working. Sorry for my english. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 20:59:38 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.32, 5.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d3) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Cezanne [103c:8895] InstallationDate: Installed on 2022-03-23 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210502) MachineType: HP HP EliteBook 845 G8 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-37-generic root=UUID=e3adb113-cca4-4316-9c3b-edc124da9ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2022 dmi.bios.release: 8.3 dmi.bios.vendor: HP dmi.bios.version: T82 Ver. 01.08.03 dmi.board.name: 8895 dmi.board.vendor: HP dmi.board.version: KBC Version 43.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 67.42 dmi.modalias: dmi:bvnHP:bvrT82Ver.01.08.03:bd02/11/2022:br8.3:efr67.42:svnHP:pnHPEliteBook845G8NotebookPC:pvr:rvnHP:rn8895:rvrKBCVersion43.2A.00:cvnHP:ct10:cvr:sku48R69EA#BCM: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 845 G8 Notebook PC dmi.product.sku: 48R69EA#BCM dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.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-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966519/+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 1966631] Re: Nouveau is very slow on RTX 3060 Ti
Wayland will be an option again in Ubuntu 22.04 but you can enable it manually by adding a kernel parameter: nvidia-drm.modeset=1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966631 Title: Nouveau is very slow on RTX 3060 Ti Status in linux-hwe-5.13 package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: When I login with Ubuntu on Wayland, everything goes extremely slow. For example the mouse pointer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 09:16:30 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-11 (44 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1966631/+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 1966631] Re: Nouveau is very slow on RTX 3060 Ti
Alright, now there is no option for login with Ubuntu on Wayland, but maybe this have solved my previous xorg problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966631 Title: Nouveau is very slow on RTX 3060 Ti Status in linux-hwe-5.13 package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: When I login with Ubuntu on Wayland, everything goes extremely slow. For example the mouse pointer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 09:16:30 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-11 (44 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1966631/+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 1966519] Re: hard shutdown after close laptop lid
I reproduce this issue again and there is another prevboot.txt, but it is different the the first one. Dne 28. 03. 22 v 10:08 Daniel van Vugt napsal(a): > It appears the system is sleeping but logs nothing about waking up: > > bře 28 09:40:59 matej-laptop systemd[1]: Reached target Sleep. > bře 28 09:40:59 matej-laptop systemd[1]: Starting Record successful boot for > GRUB... > bře 28 09:40:59 matej-laptop systemd[1]: Starting Suspend... > bře 28 09:40:59 matej-laptop systemd-sleep[3339]: Suspending system... > bře 28 09:40:59 matej-laptop systemd[1]: grub-common.service: Deactivated > successfully. > bře 28 09:40:59 matej-laptop systemd[1]: Finished Record successful boot for > GRUB. > bře 28 09:40:59 matej-laptop kernel: PM: suspend entry (s2idle) > > Maybe see if bug 1964711 is related? > > ** Package changed: ubuntu => linux (Ubuntu) > > ** Changed in: linux (Ubuntu) > Status: Incomplete => New > ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/bugs/1966519/+attachment/5573677/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1966519 Title: hard shutdown after close laptop lid Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: shutdown on close screen lid and when i reopen the lid it is completely shutdown and i must press the power button and start boot sequence, i have set in gnome-tweaks action,the after close the lid memory suspend, but evidently it is not working. Sorry for my english. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 20:59:38 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.32, 5.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d3) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Cezanne [103c:8895] InstallationDate: Installed on 2022-03-23 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210502) MachineType: HP HP EliteBook 845 G8 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-37-generic root=UUID=e3adb113-cca4-4316-9c3b-edc124da9ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2022 dmi.bios.release: 8.3 dmi.bios.vendor: HP dmi.bios.version: T82 Ver. 01.08.03 dmi.board.name: 8895 dmi.board.vendor: HP dmi.board.version: KBC Version 43.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 67.42 dmi.modalias: dmi:bvnHP:bvrT82Ver.01.08.03:bd02/11/2022:br8.3:efr67.42:svnHP:pnHPEliteBook845G8NotebookPC:pvr:rvnHP:rn8895:rvrKBCVersion43.2A.00:cvnHP:ct10:cvr:sku48R69EA#BCM: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 845 G8 Notebook PC dmi.product.sku: 48R69EA#BCM dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.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-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966519/+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 1966519] Re: hard shutdown after close laptop lid
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1966519 Title: hard shutdown after close laptop lid Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: shutdown on close screen lid and when i reopen the lid it is completely shutdown and i must press the power button and start boot sequence, i have set in gnome-tweaks action,the after close the lid memory suspend, but evidently it is not working. Sorry for my english. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 20:59:38 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.32, 5.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d3) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Cezanne [103c:8895] InstallationDate: Installed on 2022-03-23 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210502) MachineType: HP HP EliteBook 845 G8 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-37-generic root=UUID=e3adb113-cca4-4316-9c3b-edc124da9ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2022 dmi.bios.release: 8.3 dmi.bios.vendor: HP dmi.bios.version: T82 Ver. 01.08.03 dmi.board.name: 8895 dmi.board.vendor: HP dmi.board.version: KBC Version 43.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 67.42 dmi.modalias: dmi:bvnHP:bvrT82Ver.01.08.03:bd02/11/2022:br8.3:efr67.42:svnHP:pnHPEliteBook845G8NotebookPC:pvr:rvnHP:rn8895:rvrKBCVersion43.2A.00:cvnHP:ct10:cvr:sku48R69EA#BCM: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 845 G8 Notebook PC dmi.product.sku: 48R69EA#BCM dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.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-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966519/+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 1966631] Re: ubuntu on wayland works very slow
Thanks for the quick reply. The problem here is that kernel 5.13 and the free graphics driver it includes is too old to support your Nvidia RTX 3060 Ti chip. Please use the 'Additional Drivers' app to install the official Nvidia driver. ** Summary changed: - ubuntu on wayland works very slow + Nouveau is very slow on RTX 3060 Ti ** Package changed: gnome-shell (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** Changed in: linux-hwe-5.13 (Ubuntu) Status: Incomplete => New ** Tags added: nouveau ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966631 Title: Nouveau is very slow on RTX 3060 Ti Status in linux-hwe-5.13 package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: When I login with Ubuntu on Wayland, everything goes extremely slow. For example the mouse pointer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 09:16:30 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-11 (44 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1966631/+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 1966418] Re: [jammy regression] Evolution does not display message content anymore
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: epiphany-browser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in liferea package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1966418/+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 1966418] Re: [jammy regression] Evolution does not display message content anymore
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: liferea (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore Status in epiphany-browser package in Ubuntu: Confirmed Status in evolution package in Ubuntu: Confirmed Status in liferea package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1966418/+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 1831039] Re: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome
** Changed in: firefox (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1831039 Title: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome Status in OEM Priority Project: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: When using wayland - onscreen keyboard not open in text inputs in many applications such as firefox or chrome. Ubuntu 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2015-06-09 (1455 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcEnviron: LANG=cs_CZ.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-31 (368 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1831039/+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 1964274] Re: Xwayland crashes with wl_display@1: error 1: invalid arguments for wl_shm@6.create_pool
Also in progress in https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/203 ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New ** Changed in: wayland (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1964274 Title: Xwayland crashes with wl_display@1: error 1: invalid arguments for wl_shm@6.create_pool Status in X.Org X server: Unknown Status in mutter package in Ubuntu: Fix Committed Status in wayland package in Ubuntu: In Progress Status in xwayland package in Ubuntu: Fix Released Bug description: System : Ubuntu 21.10 Kernel 5.13.0-35 Session : Wayland Each time I try to rip a CD with "abcde" gnome-shell crashes What I understand from the logs : Before the CD is ripped, abcde downloads a picture (from internet) as a cover of the CD. When tracker-extract discovers this picture something bad happens. Then gnome-shell crashes. After the crash (and re-login into Ubuntu) I can resume the ripping process as the picture has been cached by abcde, and tracker-extract does not interact again with it. Obviously the problem is back for each new CD. The problem appeared quite recently, probably less than 1 month ago. Logs : 00:13:06 host dbus-daemon[3541]: [session uid=1000 pid=3541] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.8' (uid=1000 pid=3573 comm="/usr/libexec/tracker-mi> 00:13:06 host systemd[3523]: Starting Tracker metadata extractor... 00:13:06 host dbus-daemon[3541]: [session uid=1000 pid=3541] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract' 00:13:06 host systemd[3523]: Started Tracker metadata extractor. 00:13:14 host tracker-extract-3[11545]: Not a JPEG file: starts with 0x89 0x50 00:13:14 host tracker-extract[11545]: Task for 'file:///home/user/Downloads/abcde.a80c7f0c/cover.jpg' finished with error: Could not get any metadata for uri:'file:///home/user/Downloads/abcde.a80c7f0c/cover.jpg' and mime:'image/jpeg' 00:13:14 host gnome-shell[3640]: WL: file descriptor expected, object (6), message create_pool(nhi) 00:13:14 host gnome-shell[3640]: WL: error in client communication (pid 3640) 00:13:14 host gnome-shell[4456]: (EE) 00:13:14 host gnome-shell[4456]: Fatal server error: 00:13:14 host gnome-shell[4456]: (EE) wl_display@1: error 1: invalid arguments for wl_shm@6.create_pool 00:13:14 host gnome-shell[4456]: (EE) 00:13:14 host gnome-shell[3640]: Connection to xwayland lost To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1964274/+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 1966381] Re: applications crash that never crashed under Ubuntu-20.04
Oh well, that latest systemd-oom didn't help. Chrome just crashed again - while I wasn't even using the computer. Here are all the syslogs at the time it crashed - nothing but the OOM Mar 28 19:30:56 ubuntu systemd-oomd[1121]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-google\x2dchrome-5640.scope due to memory used (15992975360) / total (16153948160) and swap used (921436160) / total (1023406080) being more than 90.00% Mar 28 19:30:56 ubuntu systemd[5083]: app-gnome-google\x2dchrome-5640.scope: systemd-oomd killed 311 process(es) in this unit. Mar 28 19:30:56 ubuntu systemd[5083]: app-gnome-google\x2dchrome-5640.scope: Consumed 7h 10min 56.132s CPU time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1966381 Title: applications crash that never crashed under Ubuntu-20.04 Status in systemd package in Ubuntu: New Bug description: Just now I was watching some video in Firefox. I popped over to another virtual workspace for a few minutes, and when I popped back to Firefox it had gone. The same thing had been happening all week (I installed fresh Ubuntu-22.04 last week) with Chrome, Firefox and Thunderbird. This time instead of shrugging it off I looked in the logs, and found this Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-firefox-6607.scope due to memory used (15940579328) / total (16153944064) and swap used (925564928) / total (1023406080) being more than 90.00% Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: systemd-oomd killed 298 process(es) in this unit. Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-thunderbird-5418.scope due to memory used (15591993344) / total (16149745664) and swap used (927760384) / total (1023406080) being more than 90.00% Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: systemd-oomd killed 173 process(es) in this unit. I know it's saying those three entirely unrelated applications had suddenly decided to swallow all the RAM+swap on this laptop of mine - but the very same apps didn't act like that last week under Ubuntu-20.04, so I suspect something else is going on I can't say they hadn't swallowed all the RAM, but there is ZERO sign of a system on the verge of collapsing - everything has been screaming along just nicely - no sign of the "staggering" you normally get when the OS is heavily into swap. However, now that I look I see my 16G laptop only has 1G swap??? I just let the Ubuntu installer do it's defaults - but it used to auto- choose 1xRAM or 2xRAM - what's with this 1G swap? Could that be related? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-oomd 249.11-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 19:47:44 2022 InstallationDate: Installed on 2022-03-13 (11 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+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 1910938] Re: Text is missing from shell panel and menus
** No longer affects: xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910938 Title: Text is missing from shell panel and menus Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Hello [happy new year :) ! ] Text information in the Ubuntu dialogs aren't displayed, or some times just a part of it. I don't see the hours, but i see the icons like Firefox actually opened, my battery etc. and notifications are empty (just the "!" icon). Text normally displayed when mouse-hover the applications icons is not displayed, when Ubuntu ask for my password the frame display only 3 or 4 characters, when i put the computer in standby and reopen it doesn't change anything, and the bullets of my password aren't displayed when i login. The text normally displayed on the menus aren't displayed too, same for the application menu (when hitting the bottom left corner button) and icons of applications (like Discord options on the top right of the screen). The only text from xorg that is displayed (if it's from xorg…) is the window's title (like "#Room - Discord" for Discord application, or "me@computer: ~/" above the terminal). What is left works : Firefox can display text, and text is displayed in settings for example. P.S: a reboot solved the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 11 02:26:55 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39e9] InstallationDate: Installed on 2020-11-15 (56 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80V0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN20WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 510S-13IKB dmi.modalias: dmi:bvnLENOVO:bvr3PCN20WW(V2.04):bd07/03/2018:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~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/1910938/+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 1966630] Re: Text disappears and reduces system usability
*** This bug is a duplicate of bug 1910938 *** https://bugs.launchpad.net/bugs/1910938 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 1910938, 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 (Ubuntu) ** This bug has been marked a duplicate of bug 1910938 Text is missing from shell panel and menus -- 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/1966630 Title: Text disappears and reduces system usability Status in gnome-shell package in Ubuntu: New Bug description: After the most recent updates to the system, a new problem emerged where after the system is running for a long period of time, text from the system will slowly start to disappear and reduce usability of the system overtime. It affects the top bar of the system UI and any notifications or menus that pop up. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 02:53:14 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:3672] InstallationDate: Installed on 2021-03-04 (388 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard Presario CQ57 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=471589a7-bc4c-4b2a-94ce-cf23181fdd2f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2011 dmi.bios.release: 15.51 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.33 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3672 dmi.board.vendor: Hewlett-Packard dmi.board.version: 23.48 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.72 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.33:bd12/13/2011:br15.51:efr23.72:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068C11000320491620100:rvnHewlett-Packard:rn3672:rvr23.48:cvnHewlett-Packard:ct10:cvrChassisVersion:skuQE264UA#ABA: dmi.product.family: 103C_5335KV G=N L=CON B=CO S=PRE dmi.product.name: Presario CQ57 Notebook PC dmi.product.sku: QE264UA#ABA dmi.product.version: 068C11000320491620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966630/+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 1966630] [NEW] Text disappears and reduces system usability
Public bug reported: After the most recent updates to the system, a new problem emerged where after the system is running for a long period of time, text from the system will slowly start to disappear and reduce usability of the system overtime. It affects the top bar of the system UI and any notifications or menus that pop up. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 02:53:14 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:3672] InstallationDate: Installed on 2021-03-04 (388 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard Presario CQ57 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=471589a7-bc4c-4b2a-94ce-cf23181fdd2f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2011 dmi.bios.release: 15.51 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.33 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3672 dmi.board.vendor: Hewlett-Packard dmi.board.version: 23.48 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.72 dmi.modalias: dmi:bvnHewlett-Packard:bvrF.33:bd12/13/2011:br15.51:efr23.72:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068C11000320491620100:rvnHewlett-Packard:rn3672:rvr23.48:cvnHewlett-Packard:ct10:cvrChassisVersion:skuQE264UA#ABA: dmi.product.family: 103C_5335KV G=N L=CON B=CO S=PRE dmi.product.name: Presario CQ57 Notebook PC dmi.product.sku: QE264UA#ABA dmi.product.version: 068C11000320491620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu ** Attachment added: "Example of the text being missing from the system UI" https://bugs.launchpad.net/bugs/1966630/+attachment/5573586/+files/Screenshot%20from%202022-03-28%2002-58-57.png -- 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/1966630 Title: Text disappears and reduces system usability Status in xorg package in Ubuntu: New Bug description: After the most recent updates to the system, a new problem emerged where after the system is running for a long period of time, text from the system will slowly start to disappear and reduce usability of the system overtime. It affects the top bar of the system UI and any notifications or menus that pop up. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 02:53:14 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:3672] InstallationDate: Installed on 2021-03-04 (388 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard Presario CQ57 Notebook PC ProcKernelCmdLine:
[Touch-packages] [Bug 1831039] Re: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome
per test on jammy updated on 2022/03/28, wayland mode, OSK works fine with firefox snap (v98.0.2-1, r1154) ** Also affects: oem-priority Importance: Undecided Status: New ** Tags added: 2-in-1 ** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1831039 Title: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome Status in OEM Priority Project: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: When using wayland - onscreen keyboard not open in text inputs in many applications such as firefox or chrome. Ubuntu 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2015-06-09 (1455 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcEnviron: LANG=cs_CZ.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-31 (368 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1831039/+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 1966557] Re: Non especified problem.
That message comes from something crashing, so... Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1966557 Title: Non especified problem. Status in Ubuntu: Incomplete Bug description: Hi, I'm new Ubuntu Linux user but I'm studding a lot to understand and work with it. I use a 20.04 desktop Ubuntu and a few times appears a window telling that something is wrong but didn't show what is. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 26 14:41:54 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.32, 5.13.0-35-generic, x86_64: installed virtualbox, 6.1.32, 5.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:3070] InstallationDate: Installed on 2020-10-25 (517 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4518R72 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=9b812900-6c91-4990-9d09-581145c17061 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2011 dmi.bios.release: 0.43 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT43AUS dmi.board.vendor: LENOVO dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvr9HKT43AUS:bd07/11/2011:br0.43:svnLENOVO:pn4518R72:pvrThinkCentreM91P:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 4518R72 dmi.product.sku: To be filled by O.E.M. dmi.product.version: ThinkCentre M91P dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1966557/+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 1966519] Re: hard shutdown after close laptop lid
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1966519 Title: hard shutdown after close laptop lid Status in Ubuntu: Incomplete Bug description: shutdown on close screen lid and when i reopen the lid it is completely shutdown and i must press the power button and start boot sequence, i have set in gnome-tweaks action,the after close the lid memory suspend, but evidently it is not working. Sorry for my english. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 25 20:59:38 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.32, 5.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d3) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Cezanne [103c:8895] InstallationDate: Installed on 2022-03-23 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210502) MachineType: HP HP EliteBook 845 G8 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-37-generic root=UUID=e3adb113-cca4-4316-9c3b-edc124da9ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2022 dmi.bios.release: 8.3 dmi.bios.vendor: HP dmi.bios.version: T82 Ver. 01.08.03 dmi.board.name: 8895 dmi.board.vendor: HP dmi.board.version: KBC Version 43.2A.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 67.42 dmi.modalias: dmi:bvnHP:bvrT82Ver.01.08.03:bd02/11/2022:br8.3:efr67.42:svnHP:pnHPEliteBook845G8NotebookPC:pvr:rvnHP:rn8895:rvrKBCVersion43.2A.00:cvnHP:ct10:cvr:sku48R69EA#BCM: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 845 G8 Notebook PC dmi.product.sku: 48R69EA#BCM dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.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-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1966519/+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 1966436] Re: Bluetooth fails to connect "br-connection-profile-unavailable"
What is the model of the audio device? -- 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/1966436 Title: Bluetooth fails to connect "br-connection-profile-unavailable" Status in bluez package in Ubuntu: New Status in pipewire package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: How to reproduce: > bluetoothctl scan on Discovery started ... > bluetoothctl connect 94:DB:56:8E:0B:96 Attempting to connect to 94:DB:56:8E:0B:96 Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable > systemctl status bluetooth bluetooth.service - Bluetooth service Loaded: loaded ... mars 25 12:39:08 ncelrnd2375 bluetoothd[1282]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 94:DB:56:8E:0B:96: Protocol not available Notes: kernel-5.15, bluez-5.64 Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth Dell Precision 3560 Unfortunately I did not test before upgrade to 22.04. Tried installing pipewire-pulse, blueman, but this is lower-level. There are reports of similar errors popping up in Arch and Manjaro recently: https://bbs.archlinux.org/viewtopic.php?id=270465 https://forum.manjaro.org/t/bluetooth-ko-with-kernel-5-16/99913 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Mar 25 12:56:34 2022 InstallationDate: Installed on 2022-03-04 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision 3560 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/AmadeUbuntu20-root ro audit=1 acpi_rev_override load_nvme=YES nouveau.modeset=0 dis_ucode_ldr quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-03-22 (3 days ago) dmi.bios.date: 09/13/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.2 dmi.board.name: 095HH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.2:bd09/13/2021:br1.12:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn095HH7:rvrA00:cvnDellInc.:ct10:cvr:sku0A22: dmi.product.family: Precision dmi.product.name: Precision 3560 dmi.product.sku: 0A22 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 44:E5:17:BC:00:DD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:24189 acl:41 sco:0 events:519 errors:0 TX bytes:8252 acl:33 sco:0 commands:239 errors:0 modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1966436/+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 1966436] Re: Bluetooth fails to connect "br-connection-profile-unavailable"
Profile selection is probably related to the sound server in use, so this should be assigned there too (pulseaudio or pipewire). ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Also affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Tags added: a2dp -- 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/1966436 Title: Bluetooth fails to connect "br-connection-profile-unavailable" Status in bluez package in Ubuntu: New Status in pipewire package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: How to reproduce: > bluetoothctl scan on Discovery started ... > bluetoothctl connect 94:DB:56:8E:0B:96 Attempting to connect to 94:DB:56:8E:0B:96 Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable > systemctl status bluetooth bluetooth.service - Bluetooth service Loaded: loaded ... mars 25 12:39:08 ncelrnd2375 bluetoothd[1282]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 94:DB:56:8E:0B:96: Protocol not available Notes: kernel-5.15, bluez-5.64 Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth Dell Precision 3560 Unfortunately I did not test before upgrade to 22.04. Tried installing pipewire-pulse, blueman, but this is lower-level. There are reports of similar errors popping up in Arch and Manjaro recently: https://bbs.archlinux.org/viewtopic.php?id=270465 https://forum.manjaro.org/t/bluetooth-ko-with-kernel-5-16/99913 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Mar 25 12:56:34 2022 InstallationDate: Installed on 2022-03-04 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision 3560 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/AmadeUbuntu20-root ro audit=1 acpi_rev_override load_nvme=YES nouveau.modeset=0 dis_ucode_ldr quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-03-22 (3 days ago) dmi.bios.date: 09/13/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.2 dmi.board.name: 095HH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.2:bd09/13/2021:br1.12:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn095HH7:rvrA00:cvnDellInc.:ct10:cvr:sku0A22: dmi.product.family: Precision dmi.product.name: Precision 3560 dmi.product.sku: 0A22 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 44:E5:17:BC:00:DD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:24189 acl:41 sco:0 events:519 errors:0 TX bytes:8252 acl:33 sco:0 commands:239 errors:0 modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1966436/+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 1918410] Re: isc-dhcp-client denied by apparmor
Note to everyone watching this bug:
The file that John modified above is in the "extra profiles" section of
the upstream AppArmor source repository. It may be found on an Ubuntu
system at
/usr/share/apparmor/extra-profiles/sbin.dhclient
and in jammy, it has his fix.
However, the isc-dhcp-client package provides its own separate profile,
which is installed at
/etc/apparmor.d/sbin.dhclient
and is quite different.
Most people are likely going to be using this latter one, as it is
enabled by default. So they will not receive the benefit of John's fix.
I've confirmed that the original "DENIED" messages still occur on jammy.
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1918410
Title:
isc-dhcp-client denied by apparmor
Status in isc-dhcp package in Ubuntu:
Triaged
Bug description:
Hi, I get weird errors in the audit log, seeing dhclient is being
denied reading its comm or the comm of one of its tasks:
[1383307.827378] audit: type=1400 audit(1615367094.054:162):
apparmor="DENIED" operation="open" profile="/{,usr/}sbin/dhclient"
name="/proc/1095210/task/1095213/comm" pid=1095210 comm="dhclient"
requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
This might or might not be linked with the fact that I can't get an
IPv4 on this interface. Note that it happened to other, see this
comment:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1413232/comments/8
Or even an article recommending disabling apparmor for dhclient(!):
https://blog.anthony-jacob.com/perte-dip-v4-sous-ubuntu-20-04-apparmor-et-dhclient/
As I said, I'm not sure this is the root cause of the lack of IPv4 renewal,
because running it manually *does* succeed in getting an IP. And running it in
strace shows the EACCES failure:
[pid 1095210] openat(AT_FDCWD, "/proc/self/task/1095211/comm", O_RDWRstrace:
Process 1095211 attached
) = -1 EACCES (Permission non accordée)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1918410/+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
