October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1229061] New: Laptop that will only run Plasma/Wayland, not Plasma X11
by bugzilla_noreply＠suse.com 16 Nov '24

16 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1229061 Bug ID: 1229061 Summary: Laptop that will only run Plasma/Wayland, not Plasma X11 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: 64bit OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: marc(a)marcchamberlin.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876623 --> https://bugzilla.suse.com/attachment.cgi?id=876623&action=edit xsession-errors file When I try to use the Plasma/X11 desktop, after a reboot I reach the KDE login screen OK. If I choose to log in with the Plasma/X11 desktop, after entering my login name and password, the screen just goes blank for a moment, then cycles back and re-brings up the login/password screen again. Apparently the Plasma/X11 version of the desktop is not accepting my login credentials for some reason. However, if I choose to brings up the Plasma/Wayland desktop, my login credentials work just fine and the desktop comes up OK. I have attached a copy of my .xsession-errors file hoping that might offer a clue. (Guess I can only add one attachment at a time) will add results of doing a hw-probe -all in a follow on post. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1215403] New: SDDM default display-manager cannot login to X11 desktop
by bugzilla_noreply＠suse.com 16 Nov '24

16 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215403 Bug ID: 1215403 Summary: SDDM default display-manager cannot login to X11 desktop 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: ajbudge(a)errichel.co.uk QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- With TW as OS and KDE desktop, when running SDDM as default-displaymanager after boot login will only work with Plasma (Wayland) desktop. Selecting X11 and logging in goes dark and then after a few seconds returns to login screen. journal gives me:- Sep 16 09:22:04 HP-Z640-1 sddm-helper[2134]: Starting X11 session: "" "/usr/etc/X11/xdm/Xsession \"/usr/bin/startplasma-x11\"" Sep 16 09:22:04 HP-Z640-1 sddm[1851]: Session started false Sep 16 09:22:04 HP-Z640-1 sddm-helper[2134]: [PAM] Closing session Sep 16 09:22:04 HP-Z640-1 sddm-helper[2134]: [PAM] Ended. Sep 16 09:22:04 HP-Z640-1 sddm[1851]: Auth: sddm-helper exited with 2 and there is nothing in /etc/sddm.conf.d> or /.local/share/sddm> cat xorg-session.log (nothing here) -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1232702] New: Docker does not start properly after upgrade from TW 20241023 to 20241028
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232702 Bug ID: 1232702 Summary: Docker does not start properly after upgrade from TW 20241023 to 20241028 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: David(a)WalkerStreet.info QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After upgrading from Tumbleweed 20241023 to 20241028 this morning, docker failed to start its container engine: Oct 31 12:38:51 rpi4b (dockerd)[3994]: docker.service: Referenced but unset environment variable evaluates to an empty string: DOCKER_NETWORK_OPTIONS Editing /etc/sysconfig/docker to add DOCKER_NETWORK_OPTIONS="" corrects the problem, but I'm not sure that's the right way to fix the root problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1230010] New: /.snapshots not mountable during boot
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1230010 Bug ID: 1230010 Summary: /.snapshots not mountable during boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: forgotten_u0-bnvADNc(a)user.net Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877086 --> https://bugzilla.suse.com/attachment.cgi?id=877086&action=edit journalctl -b output I had this now the second time in a few days, every time a different MicroOS machine: after reboot machine is stuck in sulogin, because /.snapshots could not be mounted. Reading the logs I noticed that wtmpdb got again started before dbus-broker, but I don't know if the wrong ordering is a followup error or the root cause (see bsc#1229813). This machine is using systemd-boot with FDE+TPM. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1232541] New: rabbitmq-c: tools can't connect to opensuse instance
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232541 Bug ID: 1232541 Summary: rabbitmq-c: tools can't connect to opensuse instance Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: pgajdos(a)suse.com Reporter: amajer(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I cannot connect to our instance of rabbitmq with the sample tools provided, > amqp-consume -u 'amqps://opensuse:opensuse@rabbit.opensuse.org' -e pubsub -x -r '#' /usr/bin/cat opening socket to rabbit.opensuse.org:5671: SSL peer cert verification failed openssl indicates valid certificate, > cat /dev/null | openssl s_client -status -connect rabbit.opensuse.org:5671 -verify 10 | openssl x509 -dates -noout verify depth is 10 depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1 verify return:1 depth=1 C = US, O = Let's Encrypt, CN = R10 verify return:1 depth=0 CN = obs-login.opensuse.org verify return:1 DONE notBefore=Aug 12 00:25:20 2024 GMT notAfter=Nov 10 00:25:19 2024 GMT -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1213139] New: [Build 20230706] openQA test fails in consoletest_setup: vmalloc error in kernel
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213139 Bug ID: 1213139 Summary: [Build 20230706] openQA test fails in consoletest_setup: vmalloc error in kernel Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3412937/modules/cons oletest_setup/steps/52 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes Randomly (currently every ~4th run), the test fails because systemd-vconsole-setup fails to complete. The kernel spits out an allocation failure: [ 519.853569] systemd-vconsol: vmalloc error: size 0, page order 9, failed to allocate pages, mode:0xcc2(GFP_KERNEL|__GFP_HIGHMEM), nodemask=(null),cpuset=/,mems_allowed=0 [ 519.854619] CPU: 0 PID: 11361 Comm: systemd-vconsol Not tainted 6.3.9-1-default #1 openSUSE Tumbleweed 4b767630dbc263131e96e89ef291fd4fd2951892 [ 519.855385] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 [ 519.855860] Call Trace: [ 519.856047] <TASK> [ 519.856208] dump_stack_lvl+0x47/0x60 [ 519.856455] warn_alloc+0x13a/0x1b0 [ 519.856693] ? __alloc_pages+0x32d/0x350 [ 519.857009] __vmalloc_node_range+0x631/0x8b0 [ 519.857343] ? con_font_op+0x193/0x430 [ 519.857593] kvmalloc_node+0xa6/0xd0 [ 519.857857] ? con_font_op+0x193/0x430 [ 519.858105] con_font_op+0x193/0x430 [ 519.858346] ? __pfx_bpf_lsm_capable+0x10/0x10 [ 519.858631] ? security_capable+0x44/0x70 [ 519.858891] vt_ioctl+0x834/0x1380 [ 519.859126] tty_ioctl+0x4b1/0x870 [ 519.859355] __x64_sys_ioctl+0x94/0xd0 [ 519.859601] do_syscall_64+0x60/0x90 [ 519.859871] ? exc_page_fault+0x6e/0x150 [ 519.860129] entry_SYSCALL_64_after_hwframe+0x72/0xdc [ 519.860447] RIP: 0033:0x7f1144d0c2cf [ 519.860710] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [ 519.861757] RSP: 002b:00007ffe520b5af0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 519.862201] RAX: ffffffffffffffda RBX: 00007ffe520b5c10 RCX: 00007f1144d0c2cf [ 519.862843] RDX: 00007ffe520b5bf0 RSI: 0000000000004b72 RDI: 0000000000000003 [ 519.863463] RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000001 [ 519.864093] R10: 0000000000000004 R11: 0000000000000246 R12: 0000000000000008 [ 519.864705] R13: 0000000000000003 R14: 0000000000000000 R15: 0000000000000000 [ 519.865317] </TASK> [ 519.865681] Mem-Info: [ 519.866038] active_anon:34752 inactive_anon:94983 isolated_anon:0 active_file:120769 inactive_file:114642 isolated_file:0 unevictable:3088 dirty:1160 writeback:0 slab_reclaimable:23978 slab_unreclaimable:21653 mapped:30383 shmem:4200 pagetables:3497 sec_pagetables:0 bounce:0 kernel_misc_reclaimable:0 free:66953 free_pcp:198 free_cma:0 [ 519.881932] Node 0 active_anon:139008kB inactive_anon:379932kB active_file:483076kB inactive_file:458568kB unevictable:12352kB isolated(anon):0kB isolated(file):0kB mapped:121532kB dirty:4640kB writeback:0kB shmem:16800kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 61440kB writeback_tmp:0kB kernel_stack:8040kB pagetables:13988kB sec_pagetables:0kB all_unreclaimable? no [ 519.893364] Node 0 DMA free:8220kB boost:0kB min:328kB low:408kB high:488kB reserved_highatomic:0KB active_anon:32kB inactive_anon:1908kB active_file:1564kB inactive_file:2136kB unevictable:0kB writepending:0kB present:15000kB managed:14364kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB [ 519.903019] lowmem_reserve[]: 0 1889 1889 1889 1889 [ 519.905153] Node 0 DMA32 free:259592kB boost:0kB min:44724kB low:55904kB high:67084kB reserved_highatomic:16384KB active_anon:138976kB inactive_anon:378024kB active_file:481512kB inactive_file:456432kB unevictable:12352kB writepending:4640kB present:2076960kB managed:1966804kB mlocked:16kB bounce:0kB free_pcp:792kB local_pcp:792kB free_cma:0kB [ 519.915738] lowmem_reserve[]: 0 0 0 0 0 [ 519.917815] Node 0 DMA: 31*4kB (UME) 13*8kB (UME) 10*16kB (UM) 21*32kB (UME) 20*64kB (UM) 10*128kB (UME) 2*256kB (UE) 2*512kB (UE) 1*1024kB (E) 1*2048kB (E) 0*4096kB = 8228kB [ 519.920264] Node 0 DMA32: 20402*4kB (UMEH) 7366*8kB (UMEH) 2957*16kB (UMEH) 1109*32kB (UMEH) 359*64kB (UMEH) 66*128kB (UMEH) 11*256kB (MH) 4*512kB (MH) 0*1024kB 0*2048kB 0*4096kB = 259624kB [ 519.922145] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB [ 519.923229] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB [ 519.924415] 262294 total pagecache pages [ 519.925139] 22685 pages in swap cache [ 519.925777] Free swap = 1663652kB [ 519.926439] Total swap = 2097148kB [ 519.927082] 522990 pages RAM [ 519.927676] 0 pages HighMem/MovableOnly [ 519.928332] 27698 pages reserved [ 519.929181] 0 pages cma reserved [ 519.929828] 0 pages hwpoisoned If the system was actually out of RAM, I'd expect it to fail earlier in random places already. ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-upgrade_Leap_15.2_cryptlvm@uefi fails in [consoletest_setup](https://openqa.opensuse.org/tests/3412937/modules/consol… ## Test suite description Upgrade scenario with cryptlvm for Leap 15.2 Set QEMUVGA=virtio due to bsc#1210555 ## Reproducible Fails since (at least) Build [20230401](https://openqa.opensuse.org/tests/3205451) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1212937] New: Kernel panic when booting up tumbleweed 20230629
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1212937 Bug ID: 1212937 Summary: Kernel panic when booting up tumbleweed 20230629 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867932 --> https://bugzilla.suse.com/attachment.cgi?id=867932&action=edit screenshot When I booted my tw system today, I ran into a kernel panic. Kernel: Linux 6.3.9-1-default Architecture: x86-64 Hardware Vendor: Lenovo Hardware Model: ThinkPad T14s Gen 2a The issue happened once and after a reboot I was able to boot up fine. The standby issue with the laptop hanging up on resume and eventually rebooting automatically is back again and sadly reproducible always. Not sure if that could be related. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1230425] New: Using shorter name of build root folder can build out a smaller ovmf image
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1230425 Bug ID: 1230425 Summary: Using shorter name of build root folder can build out a smaller ovmf image Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: jlee(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This situation be found when I am porting edk2-stable202405 ovmf to Tumbleweed. The built out FV image size is too big for FD_SIZE_2MB config. It shows the following build error on OBS: Generating PEIFV FV ### Generating DXEFV FV ############ ['GenFv', '-a', '/home/joeyli/tmp/tmp/edk2-edk2-stable202405/Build/OvmfX64/DEBUG_GCC5/FV/Ffs/FVMAIN_COMPACT.inf', '-o', '/home/joeyli/tmp/tmp/edk2-edk2-stable202405/Build/OvmfX64/DEBUG_GCC5/FV/FVMAI Return Value = 2 GenFv: ERROR 3000: Invalid the required fv image size 0x1ac300 exceeds the set fv image size 0x1ac000 This error can also be reproduced by local build. Then I start to checking the binary of *.ffs files which are the source of FV image. e.g. Build/OvmfX64/DEBUG_GCC5/FV/Ffs/D6A2CB7F-6A18-4e2f-B43B-9920A733700ADxeCore/D6A2CB7F-6A18-4e2f-B43B-9920A733700ASEC1.1.pe32 In pe32 binary, it has many strings which are copied from the name of build root folder. e.g. ^@!(((INTN)(RETURN_STATUS)(Status)) < 0)^@/home/joeyli/tmp/tmp/edk2/MdeModulePkg/Core/Dxe/Misc/MemoryProtection.c^@DisableNullDetectionAtTheEndOfDxe(): end^M ^@/home/joeyli/tmp/tmp/edk2/MdeModulePkg/Library/ImagePropertiesRecordLib/ImagePropertiesRecordLib.c^@!!!!!!!! ImageRecord not found !!!!!!!! So, if I used a build root folder with short name. I can reduce the size of the final FV image for FD_SIZE_2MB config. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1231346] New: Virtualbox guest won't start but crashes with NS_ERROR_FAILURE (0X80004005)
by bugzilla_noreply＠suse.com 14 Nov '24

14 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1231346 Bug ID: 1231346 Summary: Virtualbox guest won't start but crashes with NS_ERROR_FAILURE (0X80004005) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: dutchkind(a)txoriaskea.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After some update the Virtualbox guests wouldn't start anymore. After some trial and error I found in the Virtualbox log: 00:00:00.011066 main rtldrNativeLoad: dlopen('/usr/lib/virtualbox/libpthread.so', RTLD_NOW | RTLD_LOCAL) failed: /usr/lib/virtualbox/libpthread.so: cannot open shared object file: No such file or directory 00:00:00.011130 main rtldrNativeLoad: dlopen('/usr/lib/virtualbox/libdl.so', RTLD_NOW | RTLD_LOCAL) failed: /usr/lib/virtualbox/libdl.so: cannot open shared object file: No such file or directory So I created a symbolic link in /usr/lib/virtualbox/ pointing to the current version of those missing libs giving the link the expected name, after which I was able to start a guest OS. This is obviously a hack and there is probably a better way, so maybe someone can fix it -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1231465] New: Kernel 6.11.2-1 causes OOM errors with Plasma 6.2
by bugzilla_noreply＠suse.com 14 Nov '24

14 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1231465 Bug ID: 1231465 Summary: Kernel 6.11.2-1 causes OOM errors with Plasma 6.2 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: felix.niederwanger(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 877874 --> https://bugzilla.suse.com/attachment.cgi?id=877874&action=edit dmesg After updating from TW 20241001 to 20241007 (current) causes many OOM errors when logging in to a Plasma desktop. The issue is only present when booting with the new 6.11.2-1 kernel, not when booting the older 6.11.0-1 kernel. I see the login manager and when I try to login as user, the Plasma Splash screen pops up, and then the laptop freezes. In the dmesg I see many OOM messages like the following: > [ 92.704048] [ T848] systemd-journal invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=-250 > [ 92.704056] [ T848] CPU: 4 UID: 0 PID: 848 Comm: systemd-journal Not tainted 6.11.2-1-default #1 openSUSE Tumbleweed e7184aff5e8c765d07bd8e233cb429101cfc70a8 > [ 92.704060] [ T848] Hardware name: Dell Inc. Latitude 7290/09386V, BIOS 1.39.0 07/04/2024 > > ... > > [ 92.704266] [ T848] Tasks state (memory values in pages): > [ 92.704267] [ T848] [ pid ] uid tgid total_vm rss rss_anon rss_file rss_shmem pgtables_bytes swapents oom_score_adj name > ... > [ 92.704386] [ T848] [ 5486] 1000 5486 67186069 2101 2081 20 0 1273856 0 200 baloo_file > [ 92.704439] [ T848] [ 5912] 1000 5912 67125561 700 608 92 0 192512 0 200 kioworkerr > [ 92.704478] [ T848] [ 6084] 1000 6084 53113 884 768 116 0 184320 0 200 kioworker > [ 92.704480] [ T848] [ 6086] 1000 6086 67125560 753 640 113 0 188416 0 200 kioworker > ... > [ 92.704510] [ T848] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=DiscoverNotifie,pid=6205,uid=1000 > [ 92.704530] [ T848] Out of memory: Killed process 6205 (DiscoverNotifie) total-vm:1148792kB, anon-rss:174748kB, file-rss:176kB, shmem-rss:0kB, UID:1000 pgtables:912kB oom_score_adj:200 See the full log as attachment. Hardware: DEll Latitude 7290, Intel i7-8650U, 32 GiB RAM As said, running the old 6.11.0-1 kernel from the same 20241007 snapshot works without issues. -- You are receiving this mail because: You are on the CC list for the bug.

1 20