August 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1191727] New: Broadcom wi-fi card did not work after installing fresh tumbleweed
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1191727 Bug ID: 1191727 Summary: Broadcom wi-fi card did not work after installing fresh tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: virex(a)mail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- My Broadcom wi-fi-card on laptop did not work after installing fresh tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1179894] New: warnings in OBS builds from kernel+initrd about "Warning: running kernel does not support fscaps"
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1179894 Bug ID: 1179894 Summary: warnings in OBS builds from kernel+initrd about "Warning: running kernel does not support fscaps" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de CC: fvogt(a)suse.com, jslaby(a)suse.com, msuchanek(a)suse.com, okurz(a)suse.com, thomas.blume(a)suse.com, tiwai(a)suse.com Depends on: 1178401 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1178401 +++ ## Observation https://build.opensuse.org/build/openSUSE:Factory/images/local/000product:o… shows repeated warnings about: ``` [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps [ 14s] Warning: running kernel does not support fscaps ``` ## Steps to reproduce Seemingly reproducible in any build of packages, e.g. https://build.opensuse.org/public/build/openSUSE:Factory/standard/x86_64/00… shows the same ## Expected result Only errors and warnings in the log that I as package/project maintainer can fix -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1178463] New: Flood of "usb usb{2,6}-port1: Cannot enable." messages
by bugzilla_noreply＠suse.com 27 Jan '23

27 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1178463 Bug ID: 1178463 Summary: Flood of "usb usb{2,6}-port1: Cannot enable." messages Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lmb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 843325 --> https://bugzilla.suse.com/attachment.cgi?id=843325&action=edit lsusb -vv With the 5.10.0rc2 kernel from Kernel:HEAD, I'm experiencing a flood of: ... [ 372.567942] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 374.686509] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 377.026495] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 378.986503] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 381.446415] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 383.290504] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 385.918496] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 387.586478] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? [ 390.386475] usb usb2-port1: Cannot enable. Maybe the USB cable is bad? [ 391.894454] usb usb6-port1: Cannot enable. Maybe the USB cable is bad? ... The XPS 13 is connected to a Belkin Thunberbird dock. As far as I can tell, except for these messages, all USB connected peripherals (keyboard, mouse, webcam) are working. Attaching lsusb -vv and dmesg output. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1188487] New: BUG: workqueue lockup
by bugzilla_noreply＠suse.com 26 Jan '23

26 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188487 Bug ID: 1188487 Summary: BUG: workqueue lockup Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: tdevries(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I started seeing this bug on my tumbleweed system: ... 2021-07-07T16:24:41.803560+02:00 lena kernel: [1053710.804959] CPU: 3 PID: 31988 Comm: gdb Tainted: G D 5.12.10-1-default #1 openSUSE Tumbleweed Message from syslogd@lena at Jul 19 16:18:29 ... kernel:[722585.589404] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for inted: G D 5.12.10-1-default #1 openSUSE Tumbleweed 2021-07-07T16:24:41.803561+02:00 lena kernel: [1053710.804964] Hardware name: LENOVO 20F5S0KF00/20F5S0KF00, BIOS R02ET73W (1.46 ) 01/08/2020 2021-07-07T16:24:41.803563+02:00 lena kernel: [1053710.804966] Call Trace: 2021-07-07T16:24:41.803564+02:00 lena kernel: [1053710.804971] dump_stack+0x76/0x94 2021-07-07T16:24:41.803566+02:00 lena kernel: [1053710.804978] bad_page.cold+0x9b/0xa0 2021-07-07T16:24:41.803567+02:00 lena kernel: [1053710.804983] get_page_from_freelist+0x739/0x13a0 2021-07-07T16:24:41.803568+02:00 lena kernel: [1053710.804990] __alloc_pages_nodemask+0x161/0x310 2021-07-07T16:24:41.803569+02:00 lena kernel: [1053710.804993] pagecache_get_page+0x14c/0x4f0 2021-07-07T16:24:41.803570+02:00 lena kernel: [1053710.805000] grab_cache_page_write_begin+0 7-07T16:24:41.803572+02:00 lena kernel: [1053710.805009] iomap_write_actor+0x9f/0x1a0 2021-07-07T16:24:41.803573+02:00 lena kernel: [1053710.805013] iomap_apply+0x111/0x2e0 2021-07-07T16:24:41.803575+02:00 lena kernel: [1053710.805015] ? iomap_write_end+0x260/0x260 2021-07-07T16:24:41.803576+02:00 lena kernel: [1053710.805020] iomap_file_buffered_write+0x5c/0x80 2021-07-07T16:24:41.803577+02:00 lena kernel: [1053710.805023] ? iomap_write_end+0x260/0x260 2021-07-07T16:24:41.803578+02:00 lena kernel: [1053710.805026] xfs_file_buffered_write+0xbd/0x2b0 [xfs] 2021-07-07T16:24:41.803579+02:00 lena kernel: [1053710.805122] ? _flat_send_IPI_mask+0x21/0x40 2021-07-07T16:24:41.803580+02:00 lena kernel: [1053710.805128] ? generic_exec_single+0x50/0xc0 2021-07-07T16:24:41.803582+02:00 lena kernel: [1053710.805133] ? smp_call_function_single_async+0x17/0x20 2021-07-07T16:24:41.803583+02:00 lena kernel: [1053710.805138] new_sync_write+0x11c/0x1b0 2021-07-07T16:24:41.803583+02:00 lena kernel: [1053710.805143] vfs_write+0x1b8/0x270 2021-07-07T16:24:41.803585+02:00 lena kernel: [1053710.805146] ksys_write+0x5f/0xe0 2021-07-07T16:24:41.803586+02:00 lena kernel: [1053710.805150] do_syscall_64+0x33/0x80 2021-07-07T16:24:41.803587+02:00 lena kernel: [1053710.805155] entry_SYSCALL_64_after_hwframe+0x44/0xae 2021-07-07T16:24:41.803588+02:00 lena kernel: [1053710.805159] RIP: 0033:0x7fc4b3b4539f 2021-07-07T16:24:41.803589+02:00 lena kernel: [1053710.805162] Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 b9 49 f9 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 0c 4a f9 ff 48 2021-07-07T16:24:41.803590+02:00 lena kernel: [1053710.805167] RSP: 002b:00007fff61dfb5f0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 2021-07-07T16:24:41.803592+02:00 lena kernel: [1053710.805171] RAX: ffffffffffffffda RBX: 0000000000001000 RCX: 00007fc4b3b4539f 2021-07-07T16:24:41.803592+02:00 lena kernel: [1053710.805174] RDX: 0000000000001000 RSI: 0000000001f9fe90 RDI: 000000000000000e 2021-07-07T16:24:41.803593+02:00 lena kernel: [1053710.805177] RBP: 0000000001f9fe90 R08: 0000000000000000 R09: 00007fff61dfbb30 2021-07-07T16:24:41.803594+02:00 lena kernel: [1053710.805180] R10: 0000000001a44440 R11: 0000000000000293 R12: 0000000000001000 2021-07-07T16:24:41.803596+02:00 lena kernel: [1053710.805182] R13: 00000000018442a0 R14: 0000000000001000 R15: 00007fc4b3c18700 ... This is with kernel: ... $ uname -a Linux lena 5.12.13-1-default #1 SMP Mon Jun 28 06:37:23 UTC 2021 (74bd8c0) x86_64 x86_64 x86_64 GNU/Linux ... It happens during a build and test run of gdb. I've updated and rebooted to kernel version 5.13.0-1-default, but ran into the same bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1193762] New: libstorage-ng fails with 'device not found' even though the device exists
by bugzilla_noreply＠suse.com 26 Jan '23

26 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1193762 Bug ID: 1193762 Summary: libstorage-ng fails with 'device not found' even though the device exists Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: snwint(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 854604 --> https://bugzilla.suse.com/attachment.cgi?id=854604&action=edit yast logs + lvm + lsblk output Running 'yast2 storage' throws an exception [libstorage] BlkDeviceImpl.cc(find_by_any_name):393 THROW: \ device not found, name:/dev/mapper/vg_b-tpool_tdata_rimage_1 even though the device clearly exists. If I mount the corresponding device with UUID 2f3d4144-0cb4-499a-a183-dd012f4c9dd6 and run the probing again, it works. The setup is an admittedly slightly convoluted LVM test setup. YaST logs for both failing and working runs are attached. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1192623] New: ltp_nfs FCNTL_LOCKTESTS test causes stack trace in dmesg
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1192623 Bug ID: 1192623 Summary: ltp_nfs FCNTL_LOCKTESTS test causes stack trace in dmesg Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Tumbleweed Build 20211110 kernel 5.14.14-2-default (2b5383f) (but it might have been failing in 5.13 and older kernels) https://openqa.opensuse.org/tests/2029105/file/serial0.txt Prints really long stack trace, which begins: [ 5211.445898][ C0] sysrq: Show State [ 5211.446508][ C0] task:systemd state:S stack: 0 pid: 1 ppid: 0 flags:0x00000000 [ 5211.447686][ C0] Call Trace: [ 5211.448216][ C0] __schedule+0x325/0x1530 [ 5211.448874][ C0] ? kmem_cache_alloc+0x151/0x480 [ 5211.449593][ C0] schedule+0x44/0xa0 [ 5211.450202][ C0] schedule_hrtimeout_range_clock+0x10b/0x120 [ 5211.451077][ C0] ? kfree+0xba/0x3c0 [ 5211.451934][ C0] ? sock_poll+0x4f/0xe0 [ 5211.452914][ C0] ? ep_done_scan+0xa7/0xf0 [ 5211.453723][ C0] do_epoll_wait+0x542/0x700 [ 5211.454594][ C0] ? wait_woken+0x70/0x70 [ 5211.455511][ C0] __x64_sys_epoll_wait+0x60/0x100 [ 5211.456475][ C0] ? syscall_exit_to_user_mode+0x18/0x40 [ 5211.457467][ C0] do_syscall_64+0x5c/0x80 [ 5211.458342][ C0] ? syscall_exit_to_user_mode+0x18/0x40 [ 5211.459302][ C0] ? do_syscall_64+0x69/0x80 [ 5211.460048][ C0] ? ksys_read+0x5f/0xe0 [ 5211.460755][ C0] ? syscall_exit_to_user_mode+0x18/0x40 [ 5211.461615][ C0] ? do_syscall_64+0x69/0x80 [ 5211.462361][ C0] ? syscall_exit_to_user_mode+0x18/0x40 [ 5211.463276][ C0] ? do_syscall_64+0x69/0x80 [ 5211.464043][ C0] ? exc_page_fault+0x68/0x130 [ 5211.464821][ C0] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 5211.465736][ C0] RIP: 0033:0x7fe070700c1e [ 5211.466480][ C0] RSP: 002b:00007ffc484b5ed0 EFLAGS: 00000293 ORIG_RAX: 00000000000000e8 [ 5211.467713][ C0] RAX: ffffffffffffffda RBX: 0000562627698e40 RCX: 00007fe070700c1e [ 5211.468853][ C0] RDX: 00000000000000ae RSI: 000056262788a3e0 RDI: 0000000000000004 [ 5211.469999][ C0] RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000006 [ 5211.471147][ C0] R10: 00000000ffffffff R11: 0000000000000293 R12: 0000000000000352 [ 5211.472315][ C0] R13: 00000000000000ae R14: 0000000000000055 R15: 0000562627698fd0 [ 5211.473472][ C0] task:kthreadd state:S stack: 0 pid: 2 ppid: 0 flags:0x00004000 [ 5211.474773][ C0] Call Trace: [ 5211.475449][ C0] __schedule+0x325/0x1530 [ 5211.476249][ C0] ? kernel_thread+0x55/0x70 [ 5211.477068][ C0] schedule+0x44/0xa0 [ 5211.477836][ C0] kthreadd+0x2c0/0x2e0 [ 5211.478647][ C0] ? kthread_is_per_cpu+0x30/0x30 [ 5211.479670][ C0] ret_from_fork+0x22/0x30 [ 5211.480495][ C0] task:rcu_gp state:I stack: 0 pid: 3 ppid: 2 flags:0x00004000 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1192624] New: ltp_nfs nfs05 (NFS stress test with make) fails
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1192624 Bug ID: 1192624 Summary: ltp_nfs nfs05 (NFS stress test with make) fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Tumbleweed Build 20211110 kernel 5.14.14-2-default (2b5383f) [1] (but it might have been failing in 5.13 and older kernels) fails to run all nfs*_05 tests which run shell script nfs05 [2] which runs nfs05_make_tree.c [3] (NFS stress test with make). Test output: # nfs05 -v 4 -t tcp; echo "### TEST nfs4_05 COMPLETE >>> $?" nfs05 1 TINFO: timeout per run is 0h 5m 0s nfs05 1 TINFO: setup NFSv4, socket type tcp nfs05 1 TINFO: Mounting NFS: mount -v -t nfs -o proto=tcp,vers=4 10.0.0.2:/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp /tmp/LTP_nfs05.G8q7DLN0j0/4/0 nfs05 1 TINFO: start nfs05_make_tree -d 20 -f 50 -t 8 tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s Test timed out, sending SIGTERM! If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 Terminated nfs05 1 TBROK: test terminated nfs05 1 TINFO: Cleaning up testcase umount.nfs4: /tmp/LTP_nfs05.G8q7DLN0j0/4/0: device is busy Test is still running... 10 Test is still running... 9 Test is still running... 8 make[6]: *** No rule to make target '26445.6.20.c', needed by '26445.6.20'. Stop. make[5]: *** [makefile:9: dir] Error 2 make[4]: *** [makefile:9: dir] Error 2 make[3]: *** [makefile:9: dir] Error 2 make[2]: *** [makefile:9: dir] Error 2 make[1]: *** [makefile:9: dir] Error 2 make: *** [makefile:9: dir] Error 2 tst_cmd.c:109: TBROK: 'make' exited with a non-zero code 2 at tst_cmd.c:109 Test is still running... 7 ... make: *** [makefile:9: dir] Error 2 Test is still running... 1 rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26445/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26446/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26447/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26448/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26449/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26450/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26452/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26451/dir/dir/dir/dir/dir/dir': Directory not empty make[6]: *** No rule to make target '26451.6.46.c', needed by '26451.6.46'. Stop. make[5]: *** [makefile:9: dir] Error 2 make[4]: *** [makefile:9: dir] Error 2 make[3]: *** [makefile:9: dir] Error 2 make[2]: *** [makefile:9: dir] Error 2 make[1]: *** [makefile:9: dir] Error 2 make: *** [makefile:9: dir] Error 2 rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/0': Device or resource busy rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/0': Is a directory There is probably no stack trace in dmesg related to this test (in attached dmesg there is really long Call Trace related to FCNTL_LOCKTESTS reported in #1192623). [1] https://openqa.opensuse.org/tests/2029105 [2] https://github.com/linux-test-project/ltp/blob/master/testcases/network/nfs… [3] https://github.com/linux-test-project/ltp/blob/master/testcases/network/nfs… -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1197369] New: Screenlocker does not work using frameworks unstable
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1197369 Bug ID: 1197369 Summary: Screenlocker does not work using frameworks unstable Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: robby.engelmann(a)r-engelmann.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Screenlocker just do not work since approx 1-2 weeks using the KDE unstable repos. Operating System: openSUSE Tumbleweed 20220320 KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.16.15-1-default (64-bit) Graphics Platform: Wayland Processors: 8 �� Intel�� Core�� i7-10510U CPU @ 1.80GHz Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel�� UHD Graphics -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1199549] New: plasmashell unusable in frameworks master builds
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1199549 Bug ID: 1199549 Summary: plasmashell unusable in frameworks master builds Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: robby.engelmann(a)r-engelmann.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- plasmashell shows 100% CPU since last friday update of frameworks-unstable repo. This can be seen starting from yakuake after having plasmashell killed: xx@linux-6mz9:~> plasmashell& [1] 4491 xx@linux-6mz9:~> kf.plasma.quick: Applet preload policy set to 1 file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:70:5: QML Connections: Detected function "onConfigurationChanged" in Connections element. This is probably intended to be a signal handler but no signal of the target matches the name. file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:70:5: QML Connections: Detected function "onRepaintNeeded" in Connections element. This is probably intended to be a signal handler but no signal of the target matches the name. file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:67: TypeError: Cannot read property 'wallpaper' of null file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:71: TypeError: Cannot read property 'wallpaper' of null file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:152:13: QML TextArea: Binding loop detected for property "implicitWidth" org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1166005] New: 20s to unlock fully encrypted partition
by bugzilla_noreply＠novell.com 25 Jan '23

25 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1166005 Bug ID: 1166005 Summary: 20s to unlock fully encrypted partition Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: axel.braun(a)gmx.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I have a new TW installation with a 940GB encrypted root partition (including /boot, excluding /boot/efi). When starting the machine, grub asks in text mode for the passphrase. After entering the passphrase, it takes about 20s until the graphical boot screen appears. X1E:/home/test # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme0n1 259:0 0 953,9G 0 disk ├─nvme0n1p1 259:1 0 500M 0 part /boot/efi ├─nvme0n1p2 259:2 0 937G 0 part │ └─cr_root 254:0 0 937G 0 crypt / └─nvme0n1p3 259:3 0 16,4G 0 part [SWAP] linux:/home/test # cryptsetup luksDump /dev/nvme0n1p2 LUKS header information for /dev/nvme0n1p2 Version: 1 Cipher name: aes Cipher mode: xts-plain64 Hash spec: sha256 Payload offset: 4096 MK bits: 512 MK digest: c3 b3 b9 a1 4b cd 08 8d 93 47 59 be f1 b8 f3 24 5f ae 81 75 MK salt: 8b 87 eb c4 bd 43 4e af 57 ef eb 9f 3c 38 a9 8a f4 c5 63 2f 1b f6 98 1a 49 62 36 e0 9e 12 8a db MK iterations: 153840 UUID: 720864c9-f8ed-405e-9a17-ccfa1d2f347b Key Slot 0: ENABLED Iterations: 1229280 Salt: 5f 9b 38 6b 29 b4 2e b0 80 35 c5 bd 88 9f 77 61 29 6c 34 00 54 3c af a5 5a d4 f6 15 7e e4 8d c4 Key material offset: 8 AF stripes: 4000 Key Slot 1: DISABLED Key Slot 2: DISABLED Key Slot 3: DISABLED Key Slot 4: DISABLED Key Slot 5: DISABLED Key Slot 6: DISABLED Key Slot 7: DISABLED It is an i7-9750H machine, so CPU power should not be an issue... -- You are receiving this mail because: You are on the CC list for the bug.

2 13