[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
#7 would suggest it's a kernel bug, so maybe test drm-tip to see if it helps -- 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/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+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 1925411] [NEW] apparmor adt test failure blocking tcpdump migration
Public bug reported: tcpdump has a sync from debian 4.99.0-2 that is currently blocked in hirsute-proposed due to a regression in the apparmor adt tests. The reason for this failure is that 'compile-policy' testcase is failing; this test ensures that various apparmor policies included in packages are accepted by the apparmor policy parser. In the new version of tcpdump 4.99.0-2, the tcpdump binary is installed into /usr/bin/tcpdump, and the tcpdump apparmor policy has been renamed from usr.sbin.tcpdump to usr.bin.tcpdump to match. The apparmor adt test however was not also changed to match, and so fails with: Addition succeeded for "/usr/sbin/ntpd". Testing usr.sbin.tcpdump File /etc/apparmor.d/usr.sbin.tcpdump not found, skipping... autopkgtest [15:35:53]: test compile-policy: ---] autopkgtest [15:35:54]: test compile-policy: - - - - - - - - - - results - - - - - - - - - - compile-policy FAIL non-zero exit status 2 causing the entire adt test to fail. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1925411 Title: apparmor adt test failure blocking tcpdump migration Status in apparmor package in Ubuntu: New Bug description: tcpdump has a sync from debian 4.99.0-2 that is currently blocked in hirsute-proposed due to a regression in the apparmor adt tests. The reason for this failure is that 'compile-policy' testcase is failing; this test ensures that various apparmor policies included in packages are accepted by the apparmor policy parser. In the new version of tcpdump 4.99.0-2, the tcpdump binary is installed into /usr/bin/tcpdump, and the tcpdump apparmor policy has been renamed from usr.sbin.tcpdump to usr.bin.tcpdump to match. The apparmor adt test however was not also changed to match, and so fails with: Addition succeeded for "/usr/sbin/ntpd". Testing usr.sbin.tcpdump File /etc/apparmor.d/usr.sbin.tcpdump not found, skipping... autopkgtest [15:35:53]: test compile-policy: ---] autopkgtest [15:35:54]: test compile-policy: - - - - - - - - - - results - - - - - - - - - - compile-policy FAIL non-zero exit status 2 causing the entire adt test to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1925411/+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 1918855] Re: Xorg xserver got signal 6 to abort
** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) ** Changed in: oem-priority Status: New => In Progress -- 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/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+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 1918855] Re: Xorg xserver got signal 6 to abort
Version of mesa on oibaf ppa 21.2~git2104200600.4a384f~oibaf~h (note) -- 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/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: New Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+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 1925401] [NEW] stack-overflow on binutils/__interceptor_strlen
Public bug reported: ==36966==ERROR: AddressSanitizer: stack-overflow on address 0x7ffc5b883fe8 (pc 0x7f07be5f21a4 bp 0x7ffc5b884860 sp 0x7ffc5b883ff0 T0) #0 0x7f07be5f21a3 in __interceptor_strlen (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x701a3) #1 0x6a3f4a in demangle_type rust-demangle.c:869 #2 0x6a40d5 in demangle_type rust-demangle.c:903 #3 0x6a44d7 in demangle_type rust-demangle.c:972 #4 0x6a399d in demangle_path rust-demangle.c:747 #5 0x6a4929 in demangle_type rust-demangle.c:1031 #6 0x6a4897 in demangle_type rust-demangle.c:1024 #7 0x6a44d7 in demangle_type rust-demangle.c:972 #8 0x6a399d in demangle_path rust-demangle.c:747 #9 0x6a4929 in demangle_type rust-demangle.c:1031 #10 0x6a4897 in demangle_type rust-demangle.c:1024 #11 0x6a44d7 in demangle_type rust-demangle.c:972 #12 0x6a399d in demangle_path rust-demangle.c:747 #13 0x6a4929 in demangle_type rust-demangle.c:1031 #14 0x6a4897 in demangle_type rust-demangle.c:1024 #15 0x6a44d7 in demangle_type rust-demangle.c:972 #16 0x6a399d in demangle_path rust-demangle.c:747 #17 0x6a4929 in demangle_type rust-demangle.c:1031 #18 0x6a4897 in demangle_type rust-demangle.c:1024 #19 0x6a44d7 in demangle_type rust-demangle.c:972 #20 0x6a399d in demangle_path rust-demangle.c:747 #21 0x6a4929 in demangle_type rust-demangle.c:1031 #22 0x6a4897 in demangle_type rust-demangle.c:1024 #23 0x6a44d7 in demangle_type rust-demangle.c:972 #24 0x6a399d in demangle_path rust-demangle.c:747 #25 0x6a4929 in demangle_type rust-demangle.c:1031 #26 0x6a4897 in demangle_type rust-demangle.c:1024 #27 0x6a44d7 in demangle_type rust-demangle.c:972 #28 0x6a399d in demangle_path rust-demangle.c:747 #29 0x6a4929 in demangle_type rust-demangle.c:1031 #30 0x6a4897 in demangle_type rust-demangle.c:1024 #31 0x6a44d7 in demangle_type rust-demangle.c:972 #32 0x6a399d in demangle_path rust-demangle.c:747 #33 0x6a4929 in demangle_type rust-demangle.c:1031 #34 0x6a4897 in demangle_type rust-demangle.c:1024 #35 0x6a44d7 in demangle_type rust-demangle.c:972 #36 0x6a399d in demangle_path rust-demangle.c:747 #37 0x6a4929 in demangle_type rust-demangle.c:1031 #38 0x6a4897 in demangle_type rust-demangle.c:1024 #39 0x6a44d7 in demangle_type rust-demangle.c:972 #40 0x6a399d in demangle_path rust-demangle.c:747 #41 0x6a4929 in demangle_type rust-demangle.c:1031 #42 0x6a4897 in demangle_type rust-demangle.c:1024 #43 0x6a44d7 in demangle_type rust-demangle.c:972 #44 0x6a399d in demangle_path rust-demangle.c:747 #45 0x6a4929 in demangle_type rust-demangle.c:1031 #46 0x6a4897 in demangle_type rust-demangle.c:1024 #47 0x6a44d7 in demangle_type rust-demangle.c:972 #48 0x6a399d in demangle_path rust-demangle.c:747 #49 0x6a4929 in demangle_type rust-demangle.c:1031 #50 0x6a4897 in demangle_type rust-demangle.c:1024 #51 0x6a44d7 in demangle_type rust-demangle.c:972 #52 0x6a399d in demangle_path rust-demangle.c:747 #53 0x6a4929 in demangle_type rust-demangle.c:1031 #54 0x6a4897 in demangle_type rust-demangle.c:1024 #55 0x6a44d7 in demangle_type rust-demangle.c:972 #56 0x6a399d in demangle_path rust-demangle.c:747 #57 0x6a4929 in demangle_type rust-demangle.c:1031 #58 0x6a4897 in demangle_type rust-demangle.c:1024 #59 0x6a44d7 in demangle_type rust-demangle.c:972 #60 0x6a399d in demangle_path rust-demangle.c:747 #61 0x6a4929 in demangle_type rust-demangle.c:1031 #62 0x6a4897 in demangle_type rust-demangle.c:1024 #63 0x6a44d7 in demangle_type rust-demangle.c:972 #64 0x6a399d in demangle_path rust-demangle.c:747 #65 0x6a4929 in demangle_type rust-demangle.c:1031 #66 0x6a4897 in demangle_type rust-demangle.c:1024 #67 0x6a44d7 in demangle_type rust-demangle.c:972 #68 0x6a399d in demangle_path rust-demangle.c:747 #69 0x6a4929 in demangle_type rust-demangle.c:1031 #70 0x6a4897 in demangle_type rust-demangle.c:1024 #71 0x6a44d7 in demangle_type rust-demangle.c:972 #72 0x6a399d in demangle_path rust-demangle.c:747 #73 0x6a4929 in demangle_type rust-demangle.c:1031 #74 0x6a4897 in demangle_type rust-demangle.c:1024 #75 0x6a44d7 in demangle_type rust-demangle.c:972 #76 0x6a399d in demangle_path rust-demangle.c:747 #77 0x6a4929 in demangle_type rust-demangle.c:1031 #78 0x6a4897 in demangle_type rust-demangle.c:1024 #79 0x6a44d7 in demangle_type rust-demangle.c:972 #80 0x6a399d in demangle_path rust-demangle.c:747 #81 0x6a4929 in demangle_type rust-demangle.c:1031 #82 0x6a4897 in demangle_type rust-demangle.c:1024 #83 0x6a44d7 in demangle_type rust-demangle.c:972 #84 0x6a399d in demangle_path rust-demangle.c:747 #85 0x6a4929 in demangle_type rust-demangle.c:1031 #86 0x6a4897 in demangle_type rust-demangle.c:1024 #87 0x6a44d7 in demangle_type rust-demangle.c:972 #88
[Touch-packages] [Bug 1925400] [NEW] stack-overflow on binutils/in __asan_memcpy
Public bug reported: ==32900==ERROR: AddressSanitizer: stack-overflow on address 0x7ffe20ebff88 (pc 0x7faa529f75cf bp 0x7ffe20ec0800 sp 0x7ffe20ebff90 T0) #0 0x7faa529f75ce in __asan_memcpy (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x8c5ce) #1 0x6a660a in str_buf_append rust-demangle.c:1490 #2 0x6a6651 in str_buf_demangle_callback rust-demangle.c:1497 #3 0x6a131f in print_str rust-demangle.c:273 #4 0x6a398e in demangle_path rust-demangle.c:746 #5 0x6a4929 in demangle_type rust-demangle.c:1031 #6 0x6a4897 in demangle_type rust-demangle.c:1024 #7 0x6a399d in demangle_path rust-demangle.c:747 #8 0x6a4929 in demangle_type rust-demangle.c:1031 #9 0x6a4897 in demangle_type rust-demangle.c:1024 #10 0x6a399d in demangle_path rust-demangle.c:747 #11 0x6a4929 in demangle_type rust-demangle.c:1031 #12 0x6a4897 in demangle_type rust-demangle.c:1024 #13 0x6a399d in demangle_path rust-demangle.c:747 #14 0x6a4929 in demangle_type rust-demangle.c:1031 #15 0x6a4897 in demangle_type rust-demangle.c:1024 #16 0x6a399d in demangle_path rust-demangle.c:747 #17 0x6a4929 in demangle_type rust-demangle.c:1031 #18 0x6a4897 in demangle_type rust-demangle.c:1024 #19 0x6a399d in demangle_path rust-demangle.c:747 #20 0x6a4929 in demangle_type rust-demangle.c:1031 #21 0x6a4897 in demangle_type rust-demangle.c:1024 #22 0x6a399d in demangle_path rust-demangle.c:747 #23 0x6a4929 in demangle_type rust-demangle.c:1031 #24 0x6a4897 in demangle_type rust-demangle.c:1024 #25 0x6a399d in demangle_path rust-demangle.c:747 #26 0x6a4929 in demangle_type rust-demangle.c:1031 #27 0x6a4897 in demangle_type rust-demangle.c:1024 #28 0x6a399d in demangle_path rust-demangle.c:747 #29 0x6a4929 in demangle_type rust-demangle.c:1031 #30 0x6a4897 in demangle_type rust-demangle.c:1024 #31 0x6a399d in demangle_path rust-demangle.c:747 #32 0x6a4929 in demangle_type rust-demangle.c:1031 #33 0x6a4897 in demangle_type rust-demangle.c:1024 #34 0x6a399d in demangle_path rust-demangle.c:747 #35 0x6a4929 in demangle_type rust-demangle.c:1031 #36 0x6a4897 in demangle_type rust-demangle.c:1024 #37 0x6a399d in demangle_path rust-demangle.c:747 #38 0x6a4929 in demangle_type rust-demangle.c:1031 #39 0x6a4897 in demangle_type rust-demangle.c:1024 #40 0x6a399d in demangle_path rust-demangle.c:747 #41 0x6a4929 in demangle_type rust-demangle.c:1031 #42 0x6a4897 in demangle_type rust-demangle.c:1024 #43 0x6a399d in demangle_path rust-demangle.c:747 #44 0x6a4929 in demangle_type rust-demangle.c:1031 #45 0x6a4897 in demangle_type rust-demangle.c:1024 #46 0x6a399d in demangle_path rust-demangle.c:747 #47 0x6a4929 in demangle_type rust-demangle.c:1031 #48 0x6a4897 in demangle_type rust-demangle.c:1024 #49 0x6a399d in demangle_path rust-demangle.c:747 #50 0x6a4929 in demangle_type rust-demangle.c:1031 #51 0x6a4897 in demangle_type rust-demangle.c:1024 #52 0x6a399d in demangle_path rust-demangle.c:747 #53 0x6a4929 in demangle_type rust-demangle.c:1031 #54 0x6a4897 in demangle_type rust-demangle.c:1024 #55 0x6a399d in demangle_path rust-demangle.c:747 #56 0x6a4929 in demangle_type rust-demangle.c:1031 #57 0x6a4897 in demangle_type rust-demangle.c:1024 #58 0x6a399d in demangle_path rust-demangle.c:747 #59 0x6a4929 in demangle_type rust-demangle.c:1031 #60 0x6a4897 in demangle_type rust-demangle.c:1024 #61 0x6a399d in demangle_path rust-demangle.c:747 #62 0x6a4929 in demangle_type rust-demangle.c:1031 #63 0x6a4897 in demangle_type rust-demangle.c:1024 #64 0x6a399d in demangle_path rust-demangle.c:747 #65 0x6a4929 in demangle_type rust-demangle.c:1031 #66 0x6a4897 in demangle_type rust-demangle.c:1024 #67 0x6a399d in demangle_path rust-demangle.c:747 #68 0x6a4929 in demangle_type rust-demangle.c:1031 #69 0x6a4897 in demangle_type rust-demangle.c:1024 #70 0x6a399d in demangle_path rust-demangle.c:747 #71 0x6a4929 in demangle_type rust-demangle.c:1031 #72 0x6a4897 in demangle_type rust-demangle.c:1024 #73 0x6a399d in demangle_path rust-demangle.c:747 #74 0x6a4929 in demangle_type rust-demangle.c:1031 #75 0x6a4897 in demangle_type rust-demangle.c:1024 #76 0x6a399d in demangle_path rust-demangle.c:747 #77 0x6a4929 in demangle_type rust-demangle.c:1031 #78 0x6a4897 in demangle_type rust-demangle.c:1024 #79 0x6a399d in demangle_path rust-demangle.c:747 #80 0x6a4929 in demangle_type rust-demangle.c:1031 #81 0x6a4897 in demangle_type rust-demangle.c:1024 #82 0x6a399d in demangle_path rust-demangle.c:747 #83 0x6a4929 in demangle_type rust-demangle.c:1031 #84 0x6a4897 in demangle_type rust-demangle.c:1024 #85 0x6a399d in demangle_path rust-demangle.c:747 #86 0x6a4929 in demangle_type rust-demangle.c:1031 #87 0x6a4897 in demangle_type
[Touch-packages] [Bug 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound
OK, thanks, let me ask for help from realtek side to explain the #9. thx. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1925057 Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Hello, I'm using Ubuntu together with Windows on my laptop. If I boot in Ubuntu after Windows sound doesn't work well (instead of system sounds I can hear only shot noise). To fix the issue I need to completely shut down the system (call Power Off via Ubuntu GUI) and then boot again in Ubuntu. Please note, that reboot (called via Ubuntu GUI) doesn't help to fix the issue. Expected result: sound works well regardless of boot history. Actual result: every time I boot in Ubuntu after Windows sound doesn't work. Issue occurrence: 100%. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Thank you in advance! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1640 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 19:37:56 2021 InstallationDate: Installed on 2021-03-06 (43 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 'module-null-sink' was still loaded! кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925057/+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 1878300] Re: Impossible to report bugs in snap packages with ubuntu-bug
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- 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/1878300 Title: Impossible to report bugs in snap packages with ubuntu-bug Status in apport package in Ubuntu: Confirmed Bug description: I'm trying to report a bug in the Software Center. I ran `ubuntu-bug -w`. It crapped out with a horribly long message in a dialog box spanning the height of a dual monitor setup (see screenshot). I don't see any buttons to continue from that point. Pressed Enter (I don't know on what), which resulted in "This problem cannot be reported: This package does not seem to be installed correctly" This is ridiculous. Ubuntu Software is *the* package used to install all others. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1878300/+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 1925055] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490780/+files/PulseList.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490778/+files/ProcInterrupts.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490783/+files/WifiSyslog.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490777/+files/ProcEnviron.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490781/+files/RfKill.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490773/+files/Lsusb-v.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490772/+files/Lsusb-t.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490784/+files/acpidump.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490782/+files/UdevDb.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490779/+files/ProcModules.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490776/+files/ProcCpuinfoMinimal.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490775/+files/ProcCpuinfo.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490774/+files/PaInfo.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490767/+files/CurrentDmesg.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490771/+files/Lsusb.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490770/+files/Lspci-vt.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490769/+files/Lspci.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490768/+files/IwConfig.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490766/+files/CRDA.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1925055/+attachment/5490765/+files/AlsaInfo.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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925055] Re: Boot stuck in UEFI after enrolling keys for drivers
Hello Dan, Thank you very much for your comments! I played with graphics card settings and found out that when I use only Intel graphics everything works well and I can boot without stuck. I performed the following steps. 1. Originally I used NVidia graphics via NVidia driver. 2. First I switched on Nouveau driver and it didn't help. 3. Then I switched again on NVidia recommended driver (nvidia-driver-460) and it didn't help. 4. Eventually I switched on Intel graphics via nvidia-settings (prime selection) and it helped. Thanks! ** Tags added: apport-collected wayland-session ** Description changed: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu65 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: gluttton 1602 F pulseaudio + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 21.04 + InstallationDate: Installed on 2021-03-06 (46 days ago) + InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + MachineType: LENOVO 82A1 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 + RelatedPackageVersions: + linux-restricted-modules-5.11.0-16-generic N/A + linux-backports-modules-5.11.0-16-generic N/A + linux-firmware 1.197 + Tags: hirsute wayland-session + Uname: Linux 5.11.0-16-generic x86_64 + UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) + UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 01/14/2021 + dmi.bios.release: 1.31 + dmi.bios.vendor: LENOVO + dmi.bios.version: DHCN31WW + dmi.board.asset.tag: ��� + dmi.board.name: LNVNB161216 + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40688 WIN + dmi.chassis.asset.tag: ��� + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Yoga Slim 7 14IIL05 + dmi.ec.firmware.release: 1.29 + dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: + dmi.product.family: Yoga Slim 7 14IIL05 + dmi.product.name: 82A1 + dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 + dmi.product.version: Yoga Slim 7 14IIL05 + dmi.sys.vendor: LENOVO -- 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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot
[Touch-packages] [Bug 1925215] Re: System completely freezes and requires reboot
I am testing 21.04. I stated the system randomly crashed but am unsure how to diagnose it and was asking for guidance so that I can share the relevant logs and you can fix it. -- 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/1925215 Title: System completely freezes and requires reboot Status in systemd package in Ubuntu: Incomplete Bug description: The OS spontaneously froze whilst doing some work (firefox, VMs). I can't find anything suspect in the logs at this stage. I will keep an eye out for this issue but would like advise on what to check for, any tools I should install and commands to run when it crashes again. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Apr 20 14:28:46 2021 ExecutablePath: /usr/lib/systemd/systemd InstallationDate: Installed on 2021-04-16 (3 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=739968f7-1aa4-47f1-8d68-55af0ffb428d ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: Z77 OC Formula dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd07/11/2013:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77OCFormula:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925215/+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 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)
I attach the screencast with Ubuntu 20.04 LTS VM about CapsLock issue for illustration. ** Attachment added: "Screecast with Ubuntu 20.04 LTS VM about CapsLock issue" https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1925141/+attachment/5490764/+files/capslock-focal-vm.gif -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1925141 Title: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1) Status in kbd-chooser: New Status in console-setup package in Ubuntu: New Status in kbd package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have minimal Ubuntu 20.04 LTS installed with all default settings and minimal set of packages on the laptop or desktop with physical CapsLock / Caps Lock LED indicator on the case or keyboard. 2. Boot the system using default settings 3. Login to the system 4. Press `` key, enter some letters in CAPITALS (while CapsLock LED is on) 5. Press `` key again, enter some letters in lowercase (while CapsLock LED is off) Expected results: * CapsLock key toggles CapsLock LED, the LED state indicates current CapsLock key function Actual results: * CapsLock LED is always off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-sysv 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 20 11:31:53 2021 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+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 1925057] Re: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound
> So if only run below commands, does the audio become good or not? Yes, I confirm that the following lines are enough to make audio good: sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x08 sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x4ab7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1925057 Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Hello, I'm using Ubuntu together with Windows on my laptop. If I boot in Ubuntu after Windows sound doesn't work well (instead of system sounds I can hear only shot noise). To fix the issue I need to completely shut down the system (call Power Off via Ubuntu GUI) and then boot again in Ubuntu. Please note, that reboot (called via Ubuntu GUI) doesn't help to fix the issue. Expected result: sound works well regardless of boot history. Actual result: every time I boot in Ubuntu after Windows sound doesn't work. Issue occurrence: 100%. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Thank you in advance! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1640 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 19:37:56 2021 InstallationDate: Installed on 2021-03-06 (43 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: кві 19 19:37:21 tiptop pulseaudio[958]: After module unload, module 'module-null-sink' was still loaded! кві 19 19:37:21 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:40 tiptop systemd[944]: pulseaudio.service: Succeeded. кві 19 19:37:50 tiptop systemd[944]: pulseaudio.socket: Succeeded. Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [82A1, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to hirsute on 2021-03-06 (43 days ago) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925057/+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 1925381] Re: rsync conceals file deletions from reporting when --dry-run --remove-source-files are used together
** Description changed: Rsync has an astonishing and dangerous bug: The dry run feature (-n / --dry-run) fails to report file deletions when --remove-source-files is used. This is quite serious. People use --dry- run to see if an outcome will work as expected before a live run. When the simulated run shows *less* destruction than the live run, the consequences can be serious because rsync may unexpectedly destroy the - only copy of a file. + only copy(*) of a file. Users rely on --dry-run. Although users probably expect --dry-run to have limitations, we don't expect destructive operations to be under reported. If it were reversed, such that the live run were less destructive than the dry run, this wouldn't be as serious. Reproducer: $ mkdir -p /tmp/src /tmp/dest $ printf '%s\n' 'yada yada' > /tmp/src/foo.txt $ printf '%s\n' 'yada yada' > /tmp/src/bar.txt $ cp /tmp/src/foo.txt /tmp/dest $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt foo.txt $ rsync -na --info=remove1 --remove-source-files --existing src/* dest/ (no output) $ rsync -a --info=remove1 --remove-source-files --existing src/* dest/ sender removed foo.txt $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt + (*) note when I say it can destroy the only copy of a file, another + circumstance is needed: that is, rsync does not do a checksum by + default. It checks for identical files based on parameters like name + and date. So it's possible that two files match in the default + comparison but differ in the actual content. Losing a unique file in + this scenario is perhaps a rare corner case, but this bug should be + fixed nonetheless. + Note this bug is similar but differs in a few ways: https://bugzilla.samba.org/show_bug.cgi?id=3844 I've marked this as a security vulnerability because it causes unexpected data loss due to --dry-run creating a false expectation. ** Description changed: Rsync has an astonishing and dangerous bug: The dry run feature (-n / --dry-run) fails to report file deletions when --remove-source-files is used. This is quite serious. People use --dry- run to see if an outcome will work as expected before a live run. When the simulated run shows *less* destruction than the live run, the consequences can be serious because rsync may unexpectedly destroy the only copy(*) of a file. Users rely on --dry-run. Although users probably expect --dry-run to have limitations, we don't expect destructive operations to be under reported. If it were reversed, such that the live run were less destructive than the dry run, this wouldn't be as serious. Reproducer: $ mkdir -p /tmp/src /tmp/dest $ printf '%s\n' 'yada yada' > /tmp/src/foo.txt $ printf '%s\n' 'yada yada' > /tmp/src/bar.txt $ cp /tmp/src/foo.txt /tmp/dest $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt foo.txt $ rsync -na --info=remove1 --remove-source-files --existing src/* dest/ (no output) $ rsync -a --info=remove1 --remove-source-files --existing src/* dest/ sender removed foo.txt $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt (*) note when I say it can destroy the only copy of a file, another circumstance is needed: that is, rsync does not do a checksum by - default. It checks for identical files based on parameters like name - and date. So it's possible that two files match in the default - comparison but differ in the actual content. Losing a unique file in - this scenario is perhaps a rare corner case, but this bug should be - fixed nonetheless. + default. It checks for identical files based on superficial parameters + like name and date. So it's possible that two files match in the + default superficial comparison but differ in the actual content. Losing + a unique file in this scenario is perhaps a rare corner case, but this + bug should be fixed nonetheless. Note this bug is similar but differs in a few ways: https://bugzilla.samba.org/show_bug.cgi?id=3844 I've marked this as a security vulnerability because it causes unexpected data loss due to --dry-run creating a false expectation. ** Description changed: Rsync has an astonishing and dangerous bug: - The dry run feature (-n / --dry-run) fails to report file deletions when - --remove-source-files is used. This is quite serious. People use --dry- - run to see if an outcome will work as expected before a live run. When - the simulated run shows *less* destruction than the live run, the - consequences can be serious because rsync may unexpectedly destroy the - only copy(*) of a file. + The dry run feature (-n / --dry-run) inhibits reporting of file + deletions when --remove-source-files is used. This is quite serious. + People use --dry-run to see if an outcome will work as expected before a + live run. When the simulated run shows
[Touch-packages] [Bug 1925381] [NEW] rsync conceals file deletions from reporting when --dry-run --remove-source-files are used together
Public bug reported: Rsync has an astonishing and dangerous bug: The dry run feature (-n / --dry-run) fails to report file deletions when --remove-source-files is used. This is quite serious. People use --dry- run to see if an outcome will work as expected before a live run. When the simulated run shows *less* destruction than the live run, the consequences can be serious because rsync may unexpectedly destroy the only copy of a file. Users rely on --dry-run. Although users probably expect --dry-run to have limitations, we don't expect destructive operations to be under reported. If it were reversed, such that the live run were less destructive than the dry run, this wouldn't be as serious. Reproducer: $ mkdir -p /tmp/src /tmp/dest $ printf '%s\n' 'yada yada' > /tmp/src/foo.txt $ printf '%s\n' 'yada yada' > /tmp/src/bar.txt $ cp /tmp/src/foo.txt /tmp/dest $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt foo.txt $ rsync -na --info=remove1 --remove-source-files --existing src/* dest/ (no output) $ rsync -a --info=remove1 --remove-source-files --existing src/* dest/ sender removed foo.txt $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt Note this bug is similar but differs in a few ways: https://bugzilla.samba.org/show_bug.cgi?id=3844 I've marked this as a security vulnerability because it causes unexpected data loss due to --dry-run creating a false expectation. ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1925381 Title: rsync conceals file deletions from reporting when --dry-run --remove- source-files are used together Status in rsync package in Ubuntu: New Bug description: Rsync has an astonishing and dangerous bug: The dry run feature (-n / --dry-run) fails to report file deletions when --remove-source-files is used. This is quite serious. People use --dry-run to see if an outcome will work as expected before a live run. When the simulated run shows *less* destruction than the live run, the consequences can be serious because rsync may unexpectedly destroy the only copy of a file. Users rely on --dry-run. Although users probably expect --dry-run to have limitations, we don't expect destructive operations to be under reported. If it were reversed, such that the live run were less destructive than the dry run, this wouldn't be as serious. Reproducer: $ mkdir -p /tmp/src /tmp/dest $ printf '%s\n' 'yada yada' > /tmp/src/foo.txt $ printf '%s\n' 'yada yada' > /tmp/src/bar.txt $ cp /tmp/src/foo.txt /tmp/dest $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt foo.txt $ rsync -na --info=remove1 --remove-source-files --existing src/* dest/ (no output) $ rsync -a --info=remove1 --remove-source-files --existing src/* dest/ sender removed foo.txt $ ls /tmp/src/ /tmp/dest/ /tmp/dest/: foo.txt /tmp/src/: bar.txt Note this bug is similar but differs in a few ways: https://bugzilla.samba.org/show_bug.cgi?id=3844 I've marked this as a security vulnerability because it causes unexpected data loss due to --dry-run creating a false expectation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1925381/+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 1925055] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1925055 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1916485] Re: test -x fails inside shell scripts in containers
Thanks for the investigation, Dan. I tested the Linux package from your PPA on a s390x machine and can confirm that it does solve the issue. -- 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/1916485 Title: test -x fails inside shell scripts in containers Status in Ubuntu on IBM z Systems: New Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1
[Touch-packages] [Bug 1923267] Re: indicator-multiload app broken after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1
The errors seems to be coming from gnome-shell-extension-appindicator there, do you still get the issue using https://launchpad.net/ubuntu/+source/gnome-shell-extension- appindicator/35-1 ? ** Package changed: glib2.0 (Ubuntu) => gnome-shell-extension- appindicator (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1923267 Title: indicator-multiload app broken after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: Problem tested in two different environments: - Ubuntu 21.04 Beta amd64 - Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB) After upgrading these packages: libglib2.0-02.67.5-2 to 2.68.0-1 libglib2.0-bin 2.67.5-2 to 2.68.0-1 libglib2.0-data 2.67.5-2 to 2.68.0-1 The app indicator-multiload (0.4-0ubuntu5) doesn't work showing only three dots (...) instead of the graphic expected. It's throwing error messages to the system journal every second or so (depends of the refresh interval selected in the app settings): abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]: multiload, Impossible to read image from path '/run/user/1026 /multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png': TypeError: method Gio.File.read_async: At least 3 arguments required, but only 2 passed Don't know if this is a documented change of that method and the bug should be open for the indicator-multiload app. Please, if that's the case just let me know to do it. Thanks and best reagrds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1923267/+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 1923845] Re: Please compress packages with zstd by default
@juliank Yes, python-apt works with just touched /usr/bin/zstd :
>>> apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
True
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
New
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
In Progress
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz=1=1
https://codesearch.debian.net/search?q=control.tar.xz=1=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip, profdata.tar.xz
galculator - skip, just changelog
grads - skip, ...orig-data.tar.xz
gvmd- skip, just creates xz compressed .deb
insighttoolkit4 - skip, ...orig-data.tar.xz
jdeb- skip, just creates compressed .deb
[Touch-packages] [Bug 1925055] Re: Boot stuck in UEFI after enrolling keys for drivers
> But after I install some drivers (NVidia you appear to have 2 separate graphics cards: [4.893710] nvidia :30:00.0: enabling device (0006 -> 0007) [6.034799] i915 :00:02.0: [drm] fb0: i915drmfb frame buffer device my guess would be you're having problems with the kernel choosing the correct graphics device to use, and/or some problem with the driver not correctly updating the screen. I also noticed this: [5.535665] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 however you said disabling secure boot doesn't help, so that's probably not related. Have you tried uninstalling the nvidia driver package to see if that is what's causing the problem? > Return to the original console by Alt+Fn+F1 Just a note, since you're booting with vt.handoff=7 the active VT should be 7, i.e. Ctrl+Alt+F7 You might also want to try booting with all the possibly relevant params removed, i.e. remove 'quiet splash vt.handoff=7' You could also try adding 'nomodeset' to the kernel boot params to see if that helps. In any case, this certainly looks like a kernel issue, not systemd. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1925141] Re: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1)
** Also affects: console-setup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1925141 Title: There is no CapsLock indication of CapsLock key using Caps Lock LED on the keyboard while using plain TTY (such as Ctrl+Alt+F1) Status in kbd-chooser: New Status in console-setup package in Ubuntu: New Status in kbd package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have minimal Ubuntu 20.04 LTS installed with all default settings and minimal set of packages on the laptop or desktop with physical CapsLock / Caps Lock LED indicator on the case or keyboard. 2. Boot the system using default settings 3. Login to the system 4. Press `` key, enter some letters in CAPITALS (while CapsLock LED is on) 5. Press `` key again, enter some letters in lowercase (while CapsLock LED is off) Expected results: * CapsLock key toggles CapsLock LED, the LED state indicates current CapsLock key function Actual results: * CapsLock LED is always off ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd-sysv 245.4-4ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 20 11:31:53 2021 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2021-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/kbd-chooser/+bug/1925141/+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 1923618] Re: upgrading systemd on groovy terminates sessions
It looks like something happened to dbus, but it's hard to tell what, if anything. Was this upgrading from 246.6-1ubuntu1.2 to 246.6-1ubuntu1.3, or some other versions? -- 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/1923618 Title: upgrading systemd on groovy terminates sessions Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Groovy: Incomplete Bug description: Whenever I upgrade systemd on my groovy system, my gnome session is terminated. This is very annoying, as everything that was running on that session is terminated. NetworkManager also stops running. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923618/+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 1923845] Re: Please compress packages with zstd by default
I have not tested hirsute in a clean container; but touch /usr/bin/zstd
makes it work, so the compressor lookup is broken.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
New
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
In Progress
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz=1=1
https://codesearch.debian.net/search?q=control.tar.xz=1=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip, profdata.tar.xz
galculator - skip, just changelog
grads - skip, ...orig-data.tar.xz
gvmd- skip, just creates xz compressed .deb
insighttoolkit4 - skip, ...orig-data.tar.xz
jdeb- skip, just creates compressed .deb packages
jmol- skip, just
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
There seems to be a bug in bionic's apt.
root@bb:/home/jak/Projects# python3 -c 'import apt_inst, apt_pkg;
apt_pkg.init();
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2_zstd1_all.deb").control.extractdata("control")'
Traceback (most recent call last):
File "", line 1, in
LookupError: There is no member named 'control'
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 72, in
apport_excepthook
from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in
from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in
import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 25, in
from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in
import apt
File "/usr/lib/python3/dist-packages/apt/__init__.py", line 35, in
apt_pkg.init_system()
apt_pkg.Error: E:Cannot find a configured compressor for 'false'
** No longer affects: python-apt (Ubuntu)
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
New
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
In Progress
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz=1=1
https://codesearch.debian.net/search?q=control.tar.xz=1=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro-
[Touch-packages] [Bug 1925348] [NEW] stack-overflow on GNU libiberty/rust-demangle.c:664 demangle_path
Public bug reported: ==34504==ERROR: AddressSanitizer: stack-overflow on address 0x7ffee6038f48 (pc 0x006a3331 bp 0x7ffee6039060 sp 0x7ffee6038f20 T0) #0 0x6a3330 in demangle_path rust-demangle.c:664 #1 0x6a3bd1 in demangle_path rust-demangle.c:774 #2 0x6a3bd1 in demangle_path rust-demangle.c:774 #3 0x6a3bd1 in demangle_path rust-demangle.c:774 #4 0x6a3bd1 in demangle_path rust-demangle.c:774 #5 0x6a3bd1 in demangle_path rust-demangle.c:774 #6 0x6a3bd1 in demangle_path rust-demangle.c:774 #7 0x6a3bd1 in demangle_path rust-demangle.c:774 #8 0x6a3bd1 in demangle_path rust-demangle.c:774 #9 0x6a3bd1 in demangle_path rust-demangle.c:774 #10 0x6a3bd1 in demangle_path rust-demangle.c:774 #11 0x6a3bd1 in demangle_path rust-demangle.c:774 #12 0x6a3bd1 in demangle_path rust-demangle.c:774 #13 0x6a3bd1 in demangle_path rust-demangle.c:774 #14 0x6a3bd1 in demangle_path rust-demangle.c:774 #15 0x6a3bd1 in demangle_path rust-demangle.c:774 #16 0x6a3bd1 in demangle_path rust-demangle.c:774 #17 0x6a3bd1 in demangle_path rust-demangle.c:774 #18 0x6a3bd1 in demangle_path rust-demangle.c:774 #19 0x6a3bd1 in demangle_path rust-demangle.c:774 #20 0x6a3bd1 in demangle_path rust-demangle.c:774 #21 0x6a3bd1 in demangle_path rust-demangle.c:774 #22 0x6a3bd1 in demangle_path rust-demangle.c:774 #23 0x6a3bd1 in demangle_path rust-demangle.c:774 #24 0x6a3bd1 in demangle_path rust-demangle.c:774 #25 0x6a3bd1 in demangle_path rust-demangle.c:774 #26 0x6a3bd1 in demangle_path rust-demangle.c:774 #27 0x6a3bd1 in demangle_path rust-demangle.c:774 #28 0x6a3bd1 in demangle_path rust-demangle.c:774 #29 0x6a3bd1 in demangle_path rust-demangle.c:774 #30 0x6a3bd1 in demangle_path rust-demangle.c:774 #31 0x6a3bd1 in demangle_path rust-demangle.c:774 #32 0x6a3bd1 in demangle_path rust-demangle.c:774 #33 0x6a3bd1 in demangle_path rust-demangle.c:774 #34 0x6a3bd1 in demangle_path rust-demangle.c:774 #35 0x6a3bd1 in demangle_path rust-demangle.c:774 #36 0x6a3bd1 in demangle_path rust-demangle.c:774 #37 0x6a3bd1 in demangle_path rust-demangle.c:774 #38 0x6a3bd1 in demangle_path rust-demangle.c:774 #39 0x6a3bd1 in demangle_path rust-demangle.c:774 #40 0x6a3bd1 in demangle_path rust-demangle.c:774 #41 0x6a3bd1 in demangle_path rust-demangle.c:774 #42 0x6a3bd1 in demangle_path rust-demangle.c:774 #43 0x6a3bd1 in demangle_path rust-demangle.c:774 #44 0x6a3bd1 in demangle_path rust-demangle.c:774 #45 0x6a3bd1 in demangle_path rust-demangle.c:774 #46 0x6a3bd1 in demangle_path rust-demangle.c:774 #47 0x6a3bd1 in demangle_path rust-demangle.c:774 #48 0x6a3bd1 in demangle_path rust-demangle.c:774 #49 0x6a3bd1 in demangle_path rust-demangle.c:774 #50 0x6a3bd1 in demangle_path rust-demangle.c:774 #51 0x6a3bd1 in demangle_path rust-demangle.c:774 #52 0x6a3bd1 in demangle_path rust-demangle.c:774 #53 0x6a3bd1 in demangle_path rust-demangle.c:774 #54 0x6a3bd1 in demangle_path rust-demangle.c:774 #55 0x6a3bd1 in demangle_path rust-demangle.c:774 #56 0x6a3bd1 in demangle_path rust-demangle.c:774 #57 0x6a3bd1 in demangle_path rust-demangle.c:774 #58 0x6a3bd1 in demangle_path rust-demangle.c:774 #59 0x6a3bd1 in demangle_path rust-demangle.c:774 #60 0x6a3bd1 in demangle_path rust-demangle.c:774 #61 0x6a3bd1 in demangle_path rust-demangle.c:774 #62 0x6a3bd1 in demangle_path rust-demangle.c:774 #63 0x6a3bd1 in demangle_path rust-demangle.c:774 #64 0x6a3bd1 in demangle_path rust-demangle.c:774 #65 0x6a3bd1 in demangle_path rust-demangle.c:774 #66 0x6a3bd1 in demangle_path rust-demangle.c:774 #67 0x6a3bd1 in demangle_path rust-demangle.c:774 #68 0x6a3bd1 in demangle_path rust-demangle.c:774 #69 0x6a3bd1 in demangle_path rust-demangle.c:774 #70 0x6a3bd1 in demangle_path rust-demangle.c:774 #71 0x6a3bd1 in demangle_path rust-demangle.c:774 #72 0x6a3bd1 in demangle_path rust-demangle.c:774 #73 0x6a3bd1 in demangle_path rust-demangle.c:774 #74 0x6a3bd1 in demangle_path rust-demangle.c:774 #75 0x6a3bd1 in demangle_path rust-demangle.c:774 #76 0x6a3bd1 in demangle_path rust-demangle.c:774 #77 0x6a3bd1 in demangle_path rust-demangle.c:774 #78 0x6a3bd1 in demangle_path rust-demangle.c:774 #79 0x6a3bd1 in demangle_path rust-demangle.c:774 #80 0x6a3bd1 in demangle_path rust-demangle.c:774 #81 0x6a3bd1 in demangle_path rust-demangle.c:774 #82 0x6a3bd1 in demangle_path rust-demangle.c:774 #83 0x6a3bd1 in demangle_path rust-demangle.c:774 #84 0x6a3bd1 in demangle_path rust-demangle.c:774 #85 0x6a3bd1 in demangle_path rust-demangle.c:774 #86 0x6a3bd1 in demangle_path rust-demangle.c:774 #87 0x6a3bd1 in demangle_path rust-demangle.c:774 #88 0x6a3bd1 in demangle_path rust-demangle.c:774 #89 0x6a3bd1 in demangle_path
[Touch-packages] [Bug 1923845] Re: Please compress packages with zstd by default
I don't understand what python-apt does here, it inherits zstd support
from apt.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
New
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
In Progress
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz=1=1
https://codesearch.debian.net/search?q=control.tar.xz=1=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip, profdata.tar.xz
galculator - skip, just changelog
grads - skip, ...orig-data.tar.xz
gvmd- skip, just creates xz compressed .deb
insighttoolkit4 - skip, ...orig-data.tar.xz
jdeb- skip, just creates compressed .deb packages
jmol- skip, just local data archive
jq -
[Touch-packages] [Bug 1925344] Re: Session not started after reboot (black screen) - requires switching tty back and forth
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1925344 ** Tags added: iso-testing -- 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/1925344 Title: Session not started after reboot (black screen) - requires switching tty back and forth Status in nvidia-graphics-drivers-460 package in Ubuntu: New Status in nvidia-prime package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: After installation, the first boot works as expected - the system boots into a graphical shell login screen. However all subsequent reboots end up with a black screen with a blinking cursor in the top- left corner of the screen. To get to the login screen, one has to switch to a different tty (like tty2 with ctrl+alt+f2) and then to tty1. Running `prime-select query` shows `nvidia`. Interesting enough, when I change the nvidia-prime settings at least once, like to on-demand via `prime-select on-demand` - then everything starts working as expected. Even when I switch back to `nvidia`. Not sure which package I should fill this under. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xserver-xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.67 Thu Mar 11 00:11:45 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 21 15:20:15 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:09e1] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU116M [GeForce GTX 1660 Ti Mobile] [1028:09e1] InstallationDate: Installed on 2021-04-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. G3 3500 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=5b38428b-60e8-4741-8b7f-0e60094a80f7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 06ND9G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd12/04/2020:br1.7:svnDellInc.:pnG33500:pvr:rvnDellInc.:rn06ND9G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3500 dmi.product.sku: 09E1 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1925344/+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 1923845] Re: Please compress packages with zstd by default
Debootstrap fix is merged in Debian: https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54 ** Also affects: appstream-glib (Ubuntu) Importance: Undecided Status: New ** Also affects: aptly (Ubuntu) Importance: Undecided Status: New ** Also affects: boinc (Ubuntu) Importance: Undecided Status: New ** Also affects: busybox (Ubuntu) Importance: Undecided Status: New ** Also affects: cdebootstrap (Ubuntu) Importance: Undecided Status: New ** Also affects: cdist (Ubuntu) Importance: Undecided Status: New ** Also affects: debdelta (Ubuntu) Importance: Undecided Status: New ** Also affects: debian-el (Ubuntu) Importance: Undecided Status: New ** Also affects: debootstrap (Ubuntu) Importance: Undecided Status: New ** Also affects: debsigs (Ubuntu) Importance: Undecided Status: New ** Also affects: debsig-verify (Ubuntu) Importance: Undecided Status: New ** Also affects: diffoscope (Ubuntu) Importance: Undecided Status: New ** Also affects: dpkg-sig (Ubuntu) Importance: Undecided Status: New ** Also affects: file (Ubuntu) Importance: Undecided Status: New ** Also affects: libsolv (Ubuntu) Importance: Undecided Status: New ** Also affects: lintian (Ubuntu) Importance: Undecided Status: New ** Also affects: lutris (Ubuntu) Importance: Undecided Status: New ** Also affects: obs-build (Ubuntu) Importance: Undecided Status: New ** Also affects: osc (Ubuntu) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Also affects: radare2 (Ubuntu) Importance: Undecided Status: New ** Also affects: reprepro (Ubuntu) Importance: Undecided Status: New ** Also affects: vim-scripts (Ubuntu) Importance: Undecided Status: New ** Also affects: zeroinstall-injector (Ubuntu) Importance: Undecided Status: New ** Changed in: python-apt (Ubuntu) Importance: Undecided => High ** Changed in: debootstrap (Ubuntu) Importance: Undecided => High ** Changed in: debootstrap (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1923845 Title: Please compress packages with zstd by default Status in appstream-glib package in Ubuntu: New Status in aptly package in Ubuntu: New Status in boinc package in Ubuntu: New Status in busybox package in Ubuntu: New Status in cdebootstrap package in Ubuntu: New Status in cdist package in Ubuntu: New Status in debdelta package in Ubuntu: New Status in debian-el package in Ubuntu: New Status in debootstrap package in Ubuntu: In Progress Status in debsig-verify package in Ubuntu: New Status in debsigs package in Ubuntu: New Status in diffoscope package in Ubuntu: New Status in dpkg package in Ubuntu: New Status in dpkg-sig package in Ubuntu: New Status in file package in Ubuntu: New Status in libsolv package in Ubuntu: New Status in lintian package in Ubuntu: New Status in lutris package in Ubuntu: New Status in obs-build package in Ubuntu: New Status in osc package in Ubuntu: New Status in python-apt package in Ubuntu: New Status in radare2 package in Ubuntu: New Status in reprepro package in Ubuntu: New Status in vim-scripts package in Ubuntu: New Status in zeroinstall-injector package in Ubuntu: New Bug description: https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built on Hirsute having both data and control members of the .deb being compressed with zstd. It can be handy for testing various tools. [dpkg] Decompression support in dpkg landed first in Bionic and is being SRUd to Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the zstd-compressed binary packages. From dpkg's perspective the upgrade path is cleared. The original plan was compressing only the internal data.tar .deb member, but dpkg uses uniform compression by default since dpkg 1.19.0 thus I'm collecting all the changes to support control.tar.zst, too, in this bug. Reviewed packages from: https://codesearch.debian.net/search?q=data.tar.xz=1=1 https://codesearch.debian.net/search?q=control.tar.xz=1=1 appstream-glib - needs fix: libappstream-builder/asb-package-deb.c aptly - needs fix: deb/deb.go boinc - needs fix: debian/fetch_example_applications.sh busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c cdebootstrap- needs fix: src/package.c cdist - may need fix, can use dpkg-deb: cdist/preos/debootstrap/files/devuan-debootstrap/functions debdelta- needs fix: debdelta debpatch.sh debian-el - needs fix: deb-view.el debian-handbook - needs fix, maybe later,
[Touch-packages] [Bug 387957] Re: Improve Save As Dialog Box (focus issues)
This is a very irritating thing, and should be easy to solve. The fix is just changing initial focus! Hard to understand this has been open for 12 years now. There's even a risk of data loss by unintentionally overwriting a file when one types, *as it works just fine on all other OS*, the filename to save the file as and hits return... overwriting some other file that just happened to "match" the "filter". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/387957 Title: Improve Save As Dialog Box (focus issues) Status in One Hundred Papercuts: Invalid Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: The save dialog box has the irritating habit of not focusing on the file name area once I have browsed to the location where I would like to save my document. This is done better in Windows. There are two main scenarios when saving a document where this behaviour annoys: Scanario 1 - Browsing to save location by double-clicking: 1. File -> Save As (to bring up the "Save" dialog box). 2. Double click on the folder in which you would like to save the document. 3. Notice that the focus is now in the folder list area, not on the file name area. 4. I now have to click in the file name area to be able to name my document. In Windows, the focus is returned immediately to the file name box once a folder is double clicked, so the name can be typed and the document saved in one step. Scenario 2 - Browsing save location using the keyboard (find as you type): 1. File -> Save As (to bring up the "Save" dialog box). 2. Click on the folder area so that folder names can be typed to find them. Hit enter to enter desired folder. 3. Within the folder, step 2 can be repeated for subfolders indefinitely. 4. Once the desired location has been reached, the user must use the mouse click in the file name area to name the file before saving. In Windows, when using find as you type, although focus is retained by the folder area when entering a lower folder level (so that you can browse to another level using the keyboard if desired), jumping to the file name box is simply a matter of pressing tab ONCE. In Ubuntu, I have to reverse tab (shift-tab) around 10 times to get back to the file name box at the top of the screen, or use the mouse - most annoying. Solutions (copy the Windows behaviour): 1. If a folder is double clicked with the mouse, the focus should jump back to the file name box. 2. If a folder is entered into by pressing enter (on the keyboard), focus should remain in the folder area, but the file name box should only be a single tab away. I understand that solution 2 is problematic in that tabbing would ordinarily jump to the next element (usually the "file type" dropdown), not back to the top of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/387957/+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 1916485] Re: test -x fails inside shell scripts in containers
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1916485 in case anyone wants to test with the patched kernel -- 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/1916485 Title: test -x fails inside shell scripts in containers Status in Ubuntu on IBM z Systems: New Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not seem to be installed,
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
It seems the s390x failure on bionic is fixed by the patch(es) for bug 1895132. I'm not 100% sure why it is returning the normal ENOSYS for invalid syscalls except while running under systemd-nspawn, but it might be due to the different syscall entry path taken when _TIF_TRACE is set, and that does get set if _TIF_SECCOMP is set. In any case, I'll send the kernel patches to the ML. -- 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/1916485 Title: test -x fails inside shell scripts in containers Status in Ubuntu on IBM z Systems: New Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU
[Touch-packages] [Bug 1925344] [NEW] Session not started after reboot (black screen) - requires switching tty back and forth
Public bug reported: After installation, the first boot works as expected - the system boots into a graphical shell login screen. However all subsequent reboots end up with a black screen with a blinking cursor in the top-left corner of the screen. To get to the login screen, one has to switch to a different tty (like tty2 with ctrl+alt+f2) and then to tty1. Running `prime-select query` shows `nvidia`. Interesting enough, when I change the nvidia-prime settings at least once, like to on-demand via `prime-select on-demand` - then everything starts working as expected. Even when I switch back to `nvidia`. Not sure which package I should fill this under. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xserver-xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.67 Thu Mar 11 00:11:45 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 21 15:20:15 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:09e1] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU116M [GeForce GTX 1660 Ti Mobile] [1028:09e1] InstallationDate: Installed on 2021-04-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. G3 3500 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=5b38428b-60e8-4741-8b7f-0e60094a80f7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 06ND9G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd12/04/2020:br1.7:svnDellInc.:pnG33500:pvr:rvnDellInc.:rn06ND9G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3500 dmi.product.sku: 09E1 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu ** Also affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New -- 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/1925344 Title: Session not started after reboot (black screen) - requires switching tty back and forth Status in nvidia-graphics-drivers-460 package in Ubuntu: New Status in nvidia-prime package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: After installation, the first boot works as expected - the system boots into a graphical shell login screen. However all subsequent reboots end up with a black screen with a blinking cursor in the top- left corner of the screen. To get to the login screen, one has to switch to a different tty (like tty2 with ctrl+alt+f2) and then to tty1.
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
** Description changed: + SRU Justification + + [Impact] + + Hot removal of disks under kvm on s390 does not result in the kernel + removing the block device, which can lead to hung tasks and other + issues. + + [Test Plan] + + See steps to reproduce the bug in the original description below. To + test, execute these steps and confirm that the block device gets removed + as expected. + + [Where problems could occur] + + The fix is a revert of the changes which introduced this regression. The + original commit was a removal of supposedly unused code, but it seems a + mistake was made in the logic around unregistering of disks. Reverting + the changes could have potential to introduce bugs related to other virt + devices, especially if it interacts badly with subsequent driver + changes. However, the patch reverted cleanly, and reverting restores the + code to the state which has been working well in previous kernels and + seems like the lowest risk option until a proper fix is available + upstream. + + --- + Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc - From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! - --- + --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: - + Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: - + ProcFB: - + ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: - linux-restricted-modules-5.11.0-14-generic N/A - linux-backports-modules-5.11.0-14-generic N/A - linux-firmware N/A + linux-restricted-modules-5.11.0-14-generic N/A + linux-backports-modules-5.11.0-14-generic N/A + linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x Status in Ubuntu on IBM z Systems: Triaged Status in linux package in
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
The condition for css_sch_device_unregister(sch) also caught my eye, calling it unconditionally is probably closer to right because it was called in the !cdev case before, and in the attached patch it would no longer be called in this case. However I think in the short term the revert is the safest option, since the code will match what we already know was working in the groovy kernel. Once a fix is committed upstream, we can trade out the revert for that patch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: Invalid Status in linux source package in Hirsute: Triaged Status in systemd source package in Hirsute: Invalid Status in udev source package in Hirsute: Invalid Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1925211/+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 1925318] Re: bluetooth just turning off and on and also disconnecting
** Package changed: ubuntu => bluez (Ubuntu) -- 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/1925318 Title: bluetooth just turning off and on and also disconnecting Status in bluez package in Ubuntu: New Bug description: bluetooth just turning off and on and also disconnecting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 21 14:53:05 2021 InstallationDate: Installed on 2020-12-22 (119 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 3521 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=e7fbb5e3-519a-41d2-94fd-6b2a0305a65d ro text SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0JYTX5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd10/25/2013:efr1.1:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rn0JYTX5:rvrA00:cvnDellInc.:ct8:cvrA12: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 3521 dmi.product.sku: Inspiron 3521 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. hciconfig: rfkill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1925318/+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 1925318] [NEW] bluetooth just turning off and on and also disconnecting
You have been subscribed to a public bug: bluetooth just turning off and on and also disconnecting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 21 14:53:05 2021 InstallationDate: Installed on 2020-12-22 (119 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 3521 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=e7fbb5e3-519a-41d2-94fd-6b2a0305a65d ro text SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0JYTX5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd10/25/2013:efr1.1:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rn0JYTX5:rvrA00:cvnDellInc.:ct8:cvrA12: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 3521 dmi.product.sku: Inspiron 3521 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. hciconfig: rfkill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- bluetooth just turning off and on and also disconnecting https://bugs.launchpad.net/bugs/1925318 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez 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 1806961] Re: Lock can be circumvented by switching tty when using lightdm
I'm commenting to let other people know and be aware that this issue persists on Ubuntu 20.04 with lightdm 1.30.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1806961 Title: Lock can be circumvented by switching tty when using lightdm Status in lightdm package in Ubuntu: Confirmed Bug description: Steps to reproduce (only works on X11, not on wayland): 1) install lightdm a) run "sudo apt install lightdm" on a fresh 18.04 install of ubuntu b) switch to lightdm with "sudo dpkg-reconfigure gdm3" c) reboot to make the login manager switch take effect 2) log in to your account 3) click switch user (clicking lock should also work) in the dropdown in the top right corner 4) switch to a different tty (ctrl+alt+f2 for example) 5) switch back to your original tty (with lightdm usally tty 7) You are now logged back in your account without having to type your password. I have marked lightdm as the vulnerable package because all I had to do to reproduce the issue was install lightdm with "sudo apt install lightdm" and then switch to lightdm with "sudo dpkg-reconfigure gdm3" So I think something should either be changed in lightdm or in dpkg- reconfigure. I have been told that I should be using light-locker instead of dm-tool, but I have no idea what those things are, or how to switch between them, i'm just clicking switch user. The user does not know, and is never informed of the existence of these tools. Since neither apt, nor dpkg-reconfigure warns me that i should use lightlocker instead of dm-tool, I think this is still a security vulnerability, because a user that wants to use lightdm and installs it by quickly searching online for "how to switch login managers" will not be informed of this vulnerability. Extra info: ubuntu 18.04 (fully up to date) lightdm version 1.26.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1806961/+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 1924597] Re: package openssh-server 1:8.3p1-1ubuntu0.1 failed to install/upgrade: podproces zainstalowany pakiet openssh-server skrypt post-installation zwrócił kod błędu 1
Thank you for help and answer. Regards J -- 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/1924597 Title: package openssh-server 1:8.3p1-1ubuntu0.1 failed to install/upgrade: podproces zainstalowany pakiet openssh-server skrypt post-installation zwrócił kod błędu 1 Status in openssh package in Ubuntu: Invalid Bug description: that happen when i try to install ssh ProblemType: Package DistroRelease: Ubuntu 20.10 Package: openssh-server 1:8.3p1-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 AptOrdering: ncurses-term:amd64: Install openssh-sftp-server:amd64: Install openssh-server:amd64: Install ssh-import-id:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Apr 15 19:12:21 2021 ErrorMessage: podproces zainstalowany pakiet openssh-server skrypt post-installation zwrócił kod błędu 1 InstallationDate: Installed on 2021-04-15 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: gnome-shell RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: /etc/ssh/sshd_config: No such file or directory SourcePackage: openssh Title: package openssh-server 1:8.3p1-1ubuntu0.1 failed to install/upgrade: podproces zainstalowany pakiet openssh-server skrypt post-installation zwrócił kod błędu 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.ssh.moduli: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1924597/+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 1925329] [NEW] package linux-firmware 1.187.11 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: looks like the boot partition is full ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.11 ProcVersionSignature: Ubuntu 5.6.0-1054.58-oem 5.6.19 Uname: Linux 5.6.0-1054-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: celian 1807 F pulseaudio CasperMD5CheckResult: skip Date: Wed Apr 21 12:04:27 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-04-12 (8 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0-1054-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.9 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.11 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0PV91W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd05/20/2020:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. ** 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/1925329 Title: package linux-firmware 1.187.11 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: looks like the boot partition is full ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.11 ProcVersionSignature: Ubuntu 5.6.0-1054.58-oem 5.6.19 Uname: Linux 5.6.0-1054-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: celian 1807 F pulseaudio CasperMD5CheckResult: skip Date: Wed Apr 21 12:04:27 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-04-12 (8 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 17 9700 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0-1054-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.9 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.11 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 0PV91W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd05/20/2020:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0PV91W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1925329/+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 1916485] Re: test -x fails inside shell scripts in containers
Interestingly, faccessat2() does correctly return ENOSYS when using a simple chroot instead of systemd-nspawn: ubuntu@test-s390x:~/h$ sudo systemd-nspawn Spawning container h on /home/ubuntu/h. Press ^] three times within 1s to kill container. root@h:~# test -x /bin/bash || echo "fail" fail root@h:~# exit logout Container h exited successfully. ubuntu@test-s390x:~/h$ sudo chroot . root@test-s390x:/# test -x /bin/bash || echo "fail" root@test-s390x:/# and to verify, stracing bash: faccessat2(AT_FDCWD, "/bin/bash", X_OK, AT_EACCESS) = -1 ENOSYS (Function not implemented) faccessat(AT_FDCWD, "/bin/bash", X_OK) = 0 -- 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/1916485 Title: test -x fails inside shell scripts in containers Status in Ubuntu on IBM z Systems: New Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: New Status in runc source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in docker.io source package in Groovy: New Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: Fix Released Status in systemd source package in Hirsute: Fix Released Status in systemd package in Debian: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version
[Touch-packages] [Bug 1925320] [NEW] Backport packages for 20.04.3 HWE stack
Public bug reported: PLACEHOLDER migrate to building libclc from llvm? ** Affects: directx-headers (Ubuntu) Importance: Undecided Status: Invalid ** Affects: libdrm (Ubuntu) Importance: Undecided Status: Invalid ** Affects: llvm-toolchain-12 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: mesa (Ubuntu) Importance: Undecided Status: Invalid ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: Invalid ** Affects: directx-headers (Ubuntu Focal) Importance: Undecided Status: New ** Affects: libdrm (Ubuntu Focal) Importance: Undecided Status: New ** Affects: llvm-toolchain-12 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: mesa (Ubuntu Focal) Importance: Undecided Status: New ** Affects: xorg-server (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Also affects: llvm-toolchain-12 (Ubuntu) Importance: Undecided Status: New ** Changed in: libdrm (Ubuntu) Status: New => Invalid ** Changed in: llvm-toolchain-12 (Ubuntu) Status: New => Invalid ** Changed in: mesa (Ubuntu) Status: New => Invalid ** Changed in: xorg-server (Ubuntu) Status: New => Invalid ** Description changed: PLACEHOLDER + + migrate to building libclc from llvm? ** Also affects: directx-headers (Ubuntu) Importance: Undecided Status: New ** Changed in: directx-headers (Ubuntu) Status: New => Invalid -- 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/1925320 Title: Backport packages for 20.04.3 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-12 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in directx-headers source package in Focal: New Status in libdrm source package in Focal: New Status in llvm-toolchain-12 source package in Focal: New Status in mesa source package in Focal: New Status in xorg-server source package in Focal: New Bug description: PLACEHOLDER migrate to building libclc from llvm? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+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 1923880] Re: FFE: libdrm 2.4.105
** Also affects: libdrm (Ubuntu Hirsute) Importance: Wishlist Status: New -- 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/1923880 Title: FFE: libdrm 2.4.105 Status in libdrm package in Ubuntu: New Status in libdrm source package in Hirsute: New Bug description: There is a new minor release available, which adds support for i915 Jasper Lake (JSL) and Alder Lake S (ADL-S), among other things. With this added, JSL can boot hirsute with the native driver. git shortlog since 2.4.104: 6b4e956d299c6ff Bump version to 2.4.105 1d13cc1032bf66f amdgpu: add function of INFO ioctl for querying video caps 50c98335c7b4013 amdgpu: sync up amdgpu_drm.h with latest from kernel b362850689d1b00 xf86drmMode: set FB_MODIFIERS flag when modifiers are supplied a5a400c9581c3b9 tests/amdgpu: fix bo eviction test issue af871ec1a6f017b drm/tests/amdgpu: fix Metadata test failed issue 6d821612d9a4bc4 xf86drmMode: introduce drmModeGetPropertyType f5abbc303361980 test/amdgpu: remove static varible in Syncobj test cd3681976c3bbef intel: Keep libdrm working without pread/pwrite ioctls 52f05d3d896480e meson: use library() instead of shared_library(). 7d6a1759900ffde xf86drm: fix null pointer deref in drmGetBufInfo 2e67fef5f6c5870 intel: Add support for JSL a9bb32cfe1ee87f xf86drm: cap number of reported devices by drmGetDevice(2) 06844b6eaefb03c Revert "xf86drm: cap number of reported devices by drmGetDevice(2)" 632f59fcbfc790a xf86drm: warn about GEM handle reference counting 523b3658aa8efa7 xf86drmMode: add drmIsKMS 1225171bd55f65d amdgpu_drm: sync up with the latest amdgpu_drm.h based on drm-next (https://cgit.freedesktop.org/drm/drm) 3b6cfb20fb3b7dd intel: add INTEL_ADLS_IDS to the pciids list 9086ff9dafa87f9 intel: sync i915_pciids.h with kernel 869ef0e4b22b8ba amdgpu: update marketing names a43cac24db2876b Avoid some compiler errors for tests/util/pattern.c62b9a3eee9bdaaf 8cb12a2528d795c xf86drm: cap number of reported devices by drmGetDevice(2) 19f0a9cb878da5b tests/amdgpu/vcn: clean abundant codes 2315bcddd643b4b tests/amdgpu: add vcn test support for dimgrey_cavefish 10377d661a31c7a tests/amdgpu: add vcn test support for navy_flounder 5f85a6d98baba1d tests/util: Add mxsfb-drm driver 62b9a3eee9bdaaf meson: Also search for rst2man.py 10dd3eb6d5ab6c1 Use dep_rt in amdgpu/meson.build diffstat: amdgpu/amdgpu-symbols.txt|1 amdgpu/amdgpu.h | 17 +++ amdgpu/amdgpu_gpu_info.c | 15 ++ amdgpu/meson.build |4 - core-symbols.txt |1 data/amdgpu.ids |6 ++ etnaviv/meson.build |2 exynos/meson.build |2 freedreno/meson.build|2 include/drm/amdgpu_drm.h | 51 +++--- intel/i915_pciids.h | 177 +++-- intel/intel_bufmgr_gem.c | 96 - intel/intel_chipset.c|2 intel/meson.build|2 libkms/meson.build |2 meson.build |6 +- nouveau/meson.build |2 omap/meson.build |2 radeon/meson.build |2 tegra/meson.build|2 tests/amdgpu/amdgpu_test.c |6 -- tests/amdgpu/basic_tests.c | 13 +++-- tests/amdgpu/bo_tests.c |4 - tests/amdgpu/syncobj_tests.c |2 tests/amdgpu/vcn_tests.c |6 +- tests/util/kms.c |1 tests/util/pattern.c |5 -- xf86drm.c| 11 xf86drm.h| 18 +++ xf86drmMode.c| 14 +- xf86drmMode.h| 12 + 31 files changed, 365 insertions(+), 121 deletions(-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1923880/+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 1925055] Re: Boot stuck in UEFI after enrolling keys for drivers
Thanks, it seems the issue is happening without plymouth then so it's probably the wrong component. I'm unsure what's the right place but I'm going to reassign to systemd which is probably closer from being right ** Package changed: plymouth (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Status: Incomplete => 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/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in systemd package in Ubuntu: New Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1925055/+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 1925055] [NEW] Boot stuck in UEFI after enrolling keys for drivers
You have been subscribed to a public bug: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Boot stuck in UEFI after enrolling keys for drivers https://bugs.launchpad.net/bugs/1925055 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd 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 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: Invalid Status in linux source package in Hirsute: Triaged Status in systemd source package in Hirsute: Invalid Status in udev source package in Hirsute: Invalid Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
** Tags added: architecture-s39064 bugnameltc-192463 severity-high targetmilestone-inin2104 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: Invalid Status in linux source package in Hirsute: Triaged Status in systemd source package in Hirsute: Invalid Status in udev source package in Hirsute: Invalid Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1925211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
I was wondering if I could trigger the same issue on an lpar as it would raise the severity IMHO. I have no claim on completeness of these tests in regard to all that could happen. I tried what I considered low hanging fruits in regard to this cross check. Pre-condition each time - a dasd attached to the system - not used e.g. as a FS - no aliases enabled => this (more or less) matches our former KVM based test case $ lscss | grep 1523; lsdasd 0.0.1523; ll /dev/dasdc 0.0.1523 0.0.0183 3390/0c 3990/e9 yes f0 f0 ff 10111213 Bus-IDStatusName Device Type BlkSz Size Blocks 0.0.1523 activedasdc 94:8ECKD 4096 7043MB1803060 brw-rw 1 root disk 94, 8 Apr 21 06:21 /dev/dasdc I was tracking the same state after the removing action and ran udevadm monitor to see is a unbind happened. --- #1 cio purge $ sudo cio_ignore -a 0.0.1523; sudo cio_ignore --purge => can't take away online devices, and I'm not interested in initial blocking .. --- #2 chzdev $ sudo chzdev --disable 0.0.1523 => properly removed --- #3 remove the dasds on the storage server "LSS 08 SRV_SS0_0823" is mapped to s1lp5 0.0.1523 - removing that on the storage server By default that fails: Error - delete of volume SRV_SS0_0823 failed. 8:28 AM Error: CMUN02948E IBM.2107-75DXP71/0823 The Delete logical volume task cannot be initiated because the Allow Host Pre-check Control Switch is set to true and the volume that you have specified is online to a host. In the old UI the force option is available as checkbox - trying via that. Done. The system does not realize that the disk is gone, I/O on it (e.g. dasdfmt) goes into a deadlock. After a while in that hang the system realizes it is in trouble: dmesg: Apr 21 06:42:32 s1lp5 kernel: dasd(eckd): I/O status report for device 0.0.1523: dasd(eckd): in req: e903a5ac CC:00 FC:00 AC:00 SC:00 DS:00 CS:00 RC:-11 dasd(eckd): device 0.0.1523: Failing CCW: dasd(eckd): SORRY - NO VALID SENSE AVAILABLE Apr 21 06:42:32 s1lp5 kernel: dasd(eckd): Related CP in req: e903a5ac dasd(eckd): CCW c3e100c4: 276C 014C5FF0 DAT: 1800 08231c00 dasd(eckd): CCW 335dd238: 3E20401A 00A4 DAT: Apr 21 06:42:32 s1lp5 kernel: dasd(eckd):.. Apr 21 06:42:32 s1lp5 kernel: dasd-eckd.adb621: 0.0.1523: ERP failed for the DASD udevadm: KERNEL[1313.022835] remove /devices/css0/0.0.0183/0.0.1523/block/dasdc/dasdc1 (block) UDEV [1313.024648] remove /devices/css0/0.0.0183/0.0.1523/block/dasdc/dasdc1 (block) Even after the above - the disk is still "present": $ lscss | grep 1523; lsdasd 0.0.1523; ll /dev/dasdc 0.0.1523 0.0.0183 3390/0c 3990/e9 yes f0 f0 0f 10111213 Bus-IDStatusName Device Type BlkSz Size Blocks 0.0.1523 activedasdc 94:8ECKD 4096 7043MB1803060 brw-rw 1 root disk 94, 8 Apr 21 06:26 /dev/dasdc Only when I detach it from the system via chzdev the hanging processes get un-stuck and the device removed. So maybe case #3 is a good one ... ? Trying the same with a Focal kernel that didn't have the issue we've seen in KVM-disk-detach. => 5.4.0-72-generic The behavior is rather similar to the new 5.11 kernel for this. Thereby, while not complete, we still can make an assumption that this case really might only affect the detach of KVM disks. Is that good: no; But is it so bad that we need to interrupt the kernel cycle, no IMHO it is not. So IMHO this can go on into the next normal Kernel SRU cycle and also gives us a chance for the IBM Developers to chime in which of the proposed solutions they want. ** Changed in: udev (Ubuntu Hirsute) Status: New => Invalid ** Changed in: systemd (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux (Ubuntu Hirsute) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: udev (Ubuntu Hirsute) Importance: Critical => Undecided ** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: ubuntu-z-systems Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Status in udev package in
[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
I can reproduce this issue on hirsute. Information below is the mesa version. libegl-mesa0:amd64 21.0.1-2 libgbm1:amd64 21.0.1-2 libgl1-mesa-dri:amd64 21.0.1-2 libglapi-mesa:amd64 21.0.1-2 libglx-mesa0:amd64 21.0.1-2 libxatracker2:amd64 21.0.1-2 mesa-vulkan-drivers:amd64 21.0.1-2 ** Attachment added: "sosreport-u-Inspiron-3891-2021-04-21-jcddohr.tar.xz" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1918855/+attachment/5490468/+files/sosreport-u-Inspiron-3891-2021-04-21-jcddohr.tar.xz -- 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/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: New Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925211] Re: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x
Yes, !resuming always evaluates to true because obviously the hot-unplug test was not done in any system PM operations. I am also unsure whether cdev can be NULL in that context so I left it there. Other functions have similar cdev check too. I think IBM devs will have more insights on this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute on s390x Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udev package in Ubuntu: New Status in linux source package in Hirsute: Confirmed Status in systemd source package in Hirsute: New Status in udev source package in Hirsute: New Bug description: Repro: #1 Get a guest $ uvt-kvm create --disk 5 --password=ubuntu h release=hirsute arch=s390x label=daily $ uvt-kvm wait h release=hirsute arch=s390x label=daily #2 Attach and Detach disk $ sudo qemu-img create -f qcow2 /var/lib/libvirt/images/test.qcow2 10M $ virsh attach-disk h /var/lib/libvirt/images/test.qcow2 vdc $ virsh detach-disk h vdc From libvirts POV it is gone at this point $ virsh domblklist h Target Source -- vda /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs.qcow vdb /var/lib/uvtool/libvirt/images/hirsute-2nd-zfs-ds.qcow But the guest thinks still it is present $ uvt-kvm ssh --insecure hirsute-2nd-zfs lsblk ... vdc252:32 0 20M 0 disk This even remains a while after (not a race). Any access to it in the guest will hang (as you'd expect of a non-existing blockdev) 4 017581739 20 0 12140 4800 - S+ pts/0 0:00 | \_ sudo mkfs.ext4 /dev/vdc 4 017591758 20 0 6924 1044 - D+ pts/0 0:00 | \_ mkfs.ext4 /dev/vdc The result above was originally found with hirsute-guest@hirsute-host on s390x I do NOT see the same with groovy-guest@hirsute-host on s390x I DO see the same with hirsute-guest@groovy-host on s390x => Guest version dependent not Host/Hipervisor dependent I DO see the same with ZFS disks AND LVM disks being added => not type dependent I do NOT see the same on x86. => Arch dependent ?? ... the evidence slowly points towards an issue in the guest, damn we are so close to release - but non-fully detaching disks are critical in my POV :-/ Filing this as-is for awareness, but certainly this will need more debugging. Unsure where this is going to eventually I'll now file it for kernel/udev/systemd. If there are any known issues/components that are related let me know please! --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu65 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 21.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: Package: udev PackageArchitecture: s390x PciMultimedia: ProcFB: ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ProcVersionSignature: User Name 5.11.0-14.15-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: hirsute uec-images Uname: Linux 5.11.0-14-generic s390x UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1925211/+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
