August 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1212954] New: amdgpu: Monitor displaying wrong resolution
by bugzilla_noreply＠suse.com 03 Mar '25

03 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1212954 Bug ID: 1212954 Summary: amdgpu: Monitor displaying wrong resolution Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: holgi(a)suse.com QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867944 --> https://bugzilla.suse.com/attachment.cgi?id=867944&action=edit IMG_20230703_164538751_HDR.jpg Having a 4K monitor (SAMSUNG LU28R55) attached to the docking station of my ThinkPad via HDMI I can easily 1:1 mirror the screen output of the laptop and the monitor with openSUSE Leap 15.4. Doing the same with openSUSE Leap 15.5 will result in monitor displaying a resolution 1980x2160 instead of the set 1980x1080. Using a 4x different screen (Philips) is working fine. Photo of monitor attached. -- You are receiving this mail because: You are on the CC list for the bug.

1 30

[Bug 1214189] New: vdpauinfo segfaults and coredumps
by bugzilla_noreply＠suse.com 03 Mar '25

03 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1214189 Bug ID: 1214189 Summary: vdpauinfo segfaults and coredumps Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: carlos.e.r(a)opensuse.org QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868762 --> https://bugzilla.suse.com/attachment.cgi?id=868762&action=edit tar file with the strace files Derives from Bug 1210427 Machine is a Lenovo Laptop, Lenovo L14 Gen3 that I bought this year. Laicolasse:~/tmp/2 # strace --output=vdpauinfo.strace --follow-forks --output-separately vdpauinfo display: :0.0 screen: 0 API version: 1 Information string: G3DVL VDPAU Driver Shared Library version 1.0 Video surface: name width height types ------------------------------------------- 420 16384 16384 NV12 YV12 422 16384 16384 UYVY YUYV 444 16384 16384 Y8U8V8A8 V8U8Y8A8 Decoder capabilities: name level macbs width height ---------------------------------------------------- MPEG1 --- not supported --- MPEG2_SIMPLE 3 65536 4096 4096 MPEG2_MAIN 3 65536 4096 4096 H264_BASELINE --- not supported --- H264_MAIN --- not supported --- H264_HIGH --- not supported --- VC1_SIMPLE --- not supported --- VC1_MAIN --- not supported --- VC1_ADVANCED --- not supported --- MPEG4_PART2_SP 3 65536 4096 4096 MPEG4_PART2_ASP 5 65536 4096 4096 DIVX4_QMOBILE --- not supported --- DIVX4_MOBILE --- not supported --- DIVX4_HOME_THEATER --- not supported --- DIVX4_HD_1080P --- not supported --- DIVX5_QMOBILE --- not supported --- DIVX5_MOBILE --- not supported --- DIVX5_HOME_THEATER --- not supported --- DIVX5_HD_1080P --- not supported --- H264_CONSTRAINED_BASELINE --- not supported --- H264_EXTENDED --- not supported --- H264_PROGRESSIVE_HIGH --- not supported --- H264_CONSTRAINED_HIGH --- not supported --- H264_HIGH_444_PREDICTIVE --- not supported --- HEVC_MAIN --- not supported --- HEVC_MAIN_10 --- not supported --- HEVC_MAIN_STILL --- not supported --- HEVC_MAIN_12 --- not supported --- HEVC_MAIN_444 --- not supported --- Output surface: name width height nat types ---------------------------------------------------- B8G8R8A8 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 I8A8 R8G8B8A8 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 I8A8 R10G10B10A2 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 I8A8 B10G10R10A2 16384 16384 y NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 I8A8 Bitmap surface: name width height ------------------------------ B8G8R8A8 16384 16384 R8G8B8A8 16384 16384 R10G10B10A2 16384 16384 B10G10R10A2 16384 16384 A8 16384 16384 Video mixer: feature name sup ------------------------------------ DEINTERLACE_TEMPORAL y DEINTERLACE_TEMPORAL_SPATIAL - INVERSE_TELECINE - NOISE_REDUCTION y SHARPNESS y LUMA_KEY y HIGH QUALITY SCALING - L1 y HIGH QUALITY SCALING - L2 - HIGH QUALITY SCALING - L3 - HIGH QUALITY SCALING - L4 - HIGH QUALITY SCALING - L5 - HIGH QUALITY SCALING - L6 - HIGH QUALITY SCALING - L7 - HIGH QUALITY SCALING - L8 - HIGH QUALITY SCALING - L9 - parameter name sup min max ----------------------------------------------------- VIDEO_SURFACE_WIDTH y 48 4096 VIDEO_SURFACE_HEIGHT y 48 4096 CHROMA_TYPE y LAYERS y 0 4 attribute name sup min max ----------------------------------------------------- BACKGROUND_COLOR y CSC_MATRIX y NOISE_REDUCTION_LEVEL y 0.00 1.00 SHARPNESS_LEVEL y -1.00 1.00 LUMA_KEY_MIN_LUMA y LUMA_KEY_MAX_LUMA y Segmentation fault (core dumped) Laicolasse:~/tmp/2 # ls vdpauinfo.strace.6031 vdpauinfo.strace.6035 vdpauinfo.strace.6039 vdpauinfo.strace.6043 vdpauinfo.strace.6032 vdpauinfo.strace.6036 vdpauinfo.strace.6040 vdpauinfo.strace.6044 vdpauinfo.strace.6033 vdpauinfo.strace.6037 vdpauinfo.strace.6041 vdpauinfo.strace.6045 vdpauinfo.strace.6034 vdpauinfo.strace.6038 vdpauinfo.strace.6042 Laicolasse:~/tmp/2 # I will attach the trace files in a tar. Laicolasse:~ # coredumpctl TIME PID UID GID SIG COREFILE EXE SIZE Fri 2023-08-11 12:48:59 CEST 6031 0 0 SIGSEGV present /usr/bin/vdpauinfo 2.0M Fri 2023-08-11 12:48:59 CEST 6028 0 0 SIGSEGV none /usr/bin/strace n/a Laicolasse:~ # So relevant file should be vdpauinfo.strace.6031 Laicolasse:~ # inxi -SGaz System: Kernel: 5.14.21-150500.55.12-default arch: x86_64 bits: 64 compiler: gcc v: 7.5.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.12-default root=UUID=858cc569-e2ae-4d12-adf6-3a06ade8281c security=apparmor no_console_suspend splash=silent resume=/dev/disk/by-label/Swap preempt=full quiet mitigations=auto Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.34 info: xfce4-panel wm: xfwm v: 4.18.0 dm: 1: GDM v: 41.3 2: SDDM note: stopped Distro: openSUSE Leap 15.5 Graphics: Device-1: AMD Barcelo vendor: Lenovo driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s ports: active: eDP-1 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 07:00.0 chip-ID: 1002:15e7 class-ID: 0300 temp: 46.0 C Device-2: Luxvisions Innotech Integrated RGB Camera type: USB driver: uvcvideo bus-ID: 3-3.2:4 chip-ID: 30c9:0050 class-ID: fe01 serial: <filter> Display: server: X.Org v: 1.21.1.4 with: Xwayland v: 22.1.5 compositor: xfwm v: 4.18.0 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93") Monitor-1: eDP-1 mapped: eDP model: AU Optronics 0x639c built: 2021 res: 1920x1080 hz: 60 dpi: 158 gamma: 1.2 size: 309x174mm (12.17x6.85") diag: 355mm (14") ratio: 16:9 modes: max: 1920x1080 min: 640x480 API: OpenGL v: 4.6 Mesa 22.3.5 renderer: AMD Radeon Graphics (renoir LLVM 15.0.7 DRM 3.49 5.14.21-150500.55.12-default) direct render: Yes Laicolasse:~ # -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1212956] New: Linphone 5.0.16 fails to launch. Symbol lookup error
by bugzilla_noreply＠suse.com 17 Feb '25

17 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1212956 Bug ID: 1212956 Summary: Linphone 5.0.16 fails to launch. Symbol lookup error 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: lair.retention968(a)4wrd.cc QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When launching Linphone, the following symbol lookup error message is shown: linphone: symbol lookup error: /lib64/liblinphone.so.10: undefined symbol: _ZN4lime11LimeManager6updateERKSt8functionIFvNS_14CallbackReturnENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEEE linphone - 5.0.16-1.3 liblime - 5.2.73-1.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1212912] New: hamradio/direwolf: Bug - Doesn't install on TW because it wants libgps29 instead of libgps30
by bugzilla_noreply＠suse.com 12 Feb '25

12 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1212912 Bug ID: 1212912 Summary: hamradio/direwolf: Bug - Doesn't install on TW because it wants libgps29 instead of libgps30 Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: jansimon.moeller(a)opensuse.org Reporter: ruimail24(a)gmail.com QA Contact: screening-team-bugs(a)suse.de CC: mardnh(a)gmx.de Target Milestone: --- Found By: --- Blocker: --- As per the title, hamradio/direwolf doesn't install on OpenSUSE TW because it depends on libgps29, and TW offers only libgps30. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1214053] New: Wrong Permissions for Package xmrig-6.18.1-bp155.1.8.x86_64.rpm (Download Error)
by bugzilla_noreply＠suse.com 29 Jan '25

29 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1214053 Bug ID: 1214053 Summary: Wrong Permissions for Package xmrig-6.18.1-bp155.1.8.x86_64.rpm (Download Error) Classification: openSUSE Product: openSUSE Backports Version: SLE-15-SP5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Packages Assignee: packagehub-bugs(a)suse.com Reporter: stephan.kreuz(a)bwi.de QA Contact: packagehub-bugs(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Sine 07/01/23 (not sure when problem occure first Time) I get Permission denied for Package xmrig-6.18.1-bp155.1.8.x86_64.rpm from suse-packagehub-15-sp5-backports-pool-x86_64(-sap). Please verify that the correct Permisions set for that Package. kind regards Stephan -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1212947] New: Disable fbdev userspace interfaces and programs
by bugzilla_noreply＠suse.com 06 Jan '25

06 Jan '25

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 18

[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 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 1213879] New: Could not allocate memory for RTAS
by bugzilla_noreply＠suse.com 29 Nov '24

29 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213879 Bug ID: 1213879 Summary: Could not allocate memory for RTAS Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: PowerPC OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: dmitriy.markov(a)mezame.ru 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: Good afternoon. While booting from iso for further installation of the system, I encountered the error "Could not allocate memory for RTAS". The problem is only present in the openSUSE Leap 15.5 ppc64le distribution. OpenSUSE Leap 15.4 ppc64le does not have this problem. Of course, on the Internet there was a solution from the equipment manufacturer. (https://www.ibm.com/support/pages/could-not-allocate-memory-rtas-grub-or-ya…) But it does not help and the error remains. My opinion is that this is a bug in the distribution, if it is not, please let me know about it. Reproducible: Always Steps to Reproduce: 1.Booting LPAR from CD/DVD openSUSE-Leap-15.5-DVD-ppc64le-Media.iso 2.In the bootloader, select "install operating system" 3.We get an error Actual Results: We get an error Welcome to GRUB! search prep from disk `ieee1275//vdevice/v-s csi@3000000b/disk@8100000000000000' error: ../../grub-core/commands/prep_loadenv.c:179:no prep partition. earlycfg: root=memdisk prefix=(memdisk)/ bdev=ieee1275//vdevice/v-scsi@3000000b/disk@8100000000000000 bpart=,1 bpath=/boot/ppc64le/grub2-ieee1275 Reading vars from (ieee1275//vdevice/v-scsi@3000000b/disk@8100000000000000) error: ../../grub-core/commands/prep_loadenv.c:179:no prep partition. ENV_HINT= ENV_GRUB_DIR= ENV_FS_UUID= searching for /boot/ppc64le/grub2-ieee1275/grub.cfg /boot/ppc64le/grub2-ieee1275/grub.cfg is on ieee1275//vdevice/v-scsi@3000000b/disk@81000 00000000000,1 prefix=(ieee1275//vdevice/v-scsi@3000000b/disk@8100000000000000,1)/boot/ppc64le /grub2-ieee1275 root=ieee1275//vdevice/v-scsi@3000000b/disk@8100000000000000,1 Loading kernel ... Loading initial ramdisk ... OF stdout device is: /vdevice/vty@30000000 Preparing to boot Linux version 5.14.21-150500.53-default (geeko@buildhost) (gcc (SUSE Linux) 7.5.0, GNU ld (GNU Binut ils; SUSE Linux Enterprise 15) 2.39.0.20220810-150100.7.40) #1 SMP Wed May 10 07:56:26 UTC 2023 (b630043) Detected machine type: 0000000000000101 command line: BOOT_IMAGE=/boot/ppc64le/linux Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : 0000000000000000 (16 MB aligned) alloc_bottom : 000000001fef0000 alloc_top : 0000000020000000 alloc_top_hi : 0000000020000000 rmo_top : 0000000020000000 ram_top : 0000000020000000 Could not allocate memory for RTAS EXIT called ok 0 > Expected Results: The system installer is loading iso SHA-256 checksum - pass My HW - IBM Power E880 SLES 12SP5 - also not affected by this error. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[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