July 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1212877] New: [RPi4] cannot wake up after suspend triggered
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1212877 Bug ID: 1212877 Summary: [RPi4] cannot wake up after suspend triggered Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: zluo(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867900 --> https://bugzilla.suse.com/attachment.cgi?id=867900&action=edit yast2 logs ssh to my RPi 4 Model B, later I see following -- p200300ea3707b36b055205817bcf9853:~ # Broadcast message from root@localhost (Fri 2023-06-30 06:03:37 UTC): The system will suspend now! -- then I try to wake it up by hitting keyboard and click on mouse, nothing happened on screen. attache yast2logs. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1212947] New: Disable fbdev userspace interfaces and programs
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1212947 Bug ID: 1212947 Summary: Disable fbdev userspace interfaces and programs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: tzimmermann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- We want to remove fbdev from kernel and userspace as far as possible. Linux 6.6 will allow us to disable fbdev's userspace interfaces, most noteably /dev/fb*. Enable this feature in the TW kernel. Framebuffer support has been an endless source of bugs. Not giving userspace access to it's internals and framebuffer memory will close a possible entry point for all sorts of malware. Please note that the framebuffer console is implemented entirely within the kernel and will not be affected by this change. -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1213380] New: Black Screen Issue on openSUSE Tumbleweed ISO after BIOS with DP-HDMI Video Output
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1213380 Bug ID: 1213380 Summary: Black Screen Issue on openSUSE Tumbleweed ISO after BIOS with DP-HDMI Video Output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: samcon(a)protonmail.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- I encountered a black screen issue while attempting to boot the openSUSE Tumbleweed ISO after the BIOS on my system. This issue specifically occurs when using a DP-HDMI video output. This problem does not arise when using the same video output with other operating systems like Leap, Fedora, and Ubuntu LTS. In those cases, I am able to get video output without any black screen problems. Steps to Reproduce: 1. Start the computer and access the BIOS. 2. Configure the boot order to prioritize booting from the openSUSE Tumbleweed ISO. 3. Save the changes and exit the BIOS. 4. The system attempts to boot from the ISO. 5. First I see the kernal or bootloader messages, then it jumps to a black screen - with waiting for source message on projector. Expected Behavior: Upon booting from the openSUSE Tumbleweed ISO, the system should display zypper installer instead of a black screen, just like other operating systems do when using the DP-HDMI video output. Additional Information: - Operating System: openSUSE Tumbleweed - Video Output: DP-HDMI - Other operating systems (Leap, Fedora, Ubuntu LTS) do not exhibit the black screen issue with the same video output. - When I connect the same system to the monitor using DP-to-DP instead of DP-to-HDMI, the video output is successfully displayed. - Have used tried with iso from few weeks back and latest Snapshot20230714-Media.iso Kind regards, Sam -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1213370] New: tesseract-ocr should not be built with experimantal opencl support
by bugzilla_noreply＠suse.com 25 Nov '24

25 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213370 Bug ID: 1213370 Summary: tesseract-ocr should not be built with experimantal opencl support Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: opensuse(a)titlis.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- opencl in tesseract-ocr is considered experimental, according to this thread (https://groups.google.com/g/tesseract-ocr/c/eIQbsurfSEM/m/mVb_4GF1BgAJ) it is considered just an entry point for possible developers. Their own doucmentantion (https://tesseract-ocr.github.io/tessdoc/TesseractOpenCL.html) states: "Important note: OpenCL support in Tesseract is still considered experimental. There are some major bugs associated with it (see issue 837). Building Tesseract with OpenCL support is not recommended (for any version of Tesseract), unless you are a developer and want to improve the OpenCL code" Please remove the flag "--enable-opencl" from https://build.opensuse.org/package/view_file/openSUSE:Factory/tesseract-ocr… This would also resolve https://bugzilla.opensuse.org/show_bug.cgi?id=1207570 PS: I indeed encounter problems with the opencl code path -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[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 1213784] New: bugzilla.opensuse.org e-mails direct to bugzilla.suse,com
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213784 Bug ID: 1213784 Summary: bugzilla.opensuse.org e-mails direct to bugzilla.suse,com Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Bugzilla Assignee: screening-team-bugs(a)suse.de Reporter: rokejulianlockhart+1674683091(a)outlook.com QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Target Milestone: --- Found By: --- Blocker: --- When I file a report at opensuse.bugzilla.org and receive a message via e-mail about it, all links in the post direct me to bguzilla.suse.com instead. This is quite the hassle when dealing with frequent notifications on multiple tickets. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213156] New: systemd-xdg-autostart-generator cannot start several existing desktop files in Leap 15.5
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213156 Bug ID: 1213156 Summary: systemd-xdg-autostart-generator cannot start several existing desktop files in Leap 15.5 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: ftake(a)geeko.jp QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This report is created in order to summarize related report caused by the same issues of systemd-xdg-autostart-generator in 15.5. systemd-xdg-autostart-generator is a mechanism to start XDG autostart (e.g., /etc/xdg/autostart) instead of desktop environments. In Leap 15.5, KDE plasma started to use this mechanism. However, due to the following problems, xdg-autostart-generator cannot start desktop files derived from Leap 15.4. Some essential services including IBus does not work in 15.5 (#1211977). * systemd-xdg-autostart-generator inappropriately ignores desktop files with X-GNOME-Autostart-Phase (#1201728) [1] * systemd-xdg-autostart-generator cannot start process that forks another process [2, 3, 4] [1] https://github.com/systemd/systemd/issues/18791 (resolved) [2] https://bugs.kde.org/show_bug.cgi?id=433299 [3] https://github.com/systemd/systemd/pull/20813 (merged) [4] https://github.com/systemd/systemd/issues/27919 (unresolved) FYI: Upstream bug tracker related xdg-autostart https://github.com/systemd/systemd/labels/xdg-autostart Some other fixes also might be necessary for 15.5 -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1213339] New: Segmentation fault when setting up database with sqlite3 gda-control-center-6.0
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1213339 Bug ID: 1213339 Summary: Segmentation fault when setting up database with sqlite3 gda-control-center-6.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: vojta.kottas(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0 Build Identifier: When setting up a sqlite database using gda-control-center-6.0 as a test in a folder (/tmp/test_db in my case), the gui crashed and the command line showed that a segmentation fault had occurred. This issue does not happen on other distros. Reproducible: Always Steps to Reproduce: 1. Run gda-control-center-6.0 2. Set up database with sqlite Actual Results: Segmentation fault Expected Results: A database is set up in the specified folder. This all came from me trying to install the Pano extension, which upon install crashed the gnome-shell. I tracked the issue to this github issue: https://github.com/oae/gnome-shell-pano/issues/178 Which further tracks the issue down to a problem with the sqlite3 package on openSUSE. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1212995] New: KDE Plasma System Settings's printer module cannot add new printers
by bugzilla_noreply＠suse.com 10 Oct '24

10 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1212995 Bug ID: 1212995 Summary: KDE Plasma System Settings's printer module cannot add new printers Classification: openSUSE Product: openSUSE Kalpa Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Desktop Environment Assignee: sfalken(a)cloverleaf-linux.org Reporter: ars2swim(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Overview: Upon attempting to add a new printer in KDE Plasma System Settings, the user is denied permission to do so. Steps to Reproduce: 1) Open System Settings 2) Select Printers 3) Click 'Click here to add a new printer) Actual Results: The window that appears returns no printers and says at the top: "Failed to get a list of devices: 'Forbidden'" Expected Results: The window returns a list of printers and allows you to add them Build date: openSUSE Kalpa 20230619 Additional Information: * This does occur on openSUSE Aeon; the built in printer settings work as expected. * Currently this can be worked around by navigating to https://localhost:631 and adding a printer through the CUPS interface, logging in as the root user when prompted. This implies that it is a permissions issue. * This bug also occurs in openSUSE Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 7