May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1225729] New: Updating from tumbleweed 20240418 makes overall graphics performance worse on amdgpu
by bugzilla_noreply＠suse.com 15 Jul '24

15 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225729 Bug ID: 1225729 Summary: Updating from tumbleweed 20240418 makes overall graphics performance worse on amdgpu Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: piotrus3g(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Current system info (with bad performance): Operating System: openSUSE Tumbleweed 20240524 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.9.1-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5625U with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82SG System Version: IdeaPad 5 15ABA7 Current graphics drivers: Mesa version: 24.0.7-1699.378.pm.1 (Packman) Amdgpu packages: xf86-video-amdgpu 23.0.0-2.2 (openSUSE-Tumbleweed-Oss) kernel-firmware-amdgpu 20240519-1.1 (openSUSE-Tumbleweed-Oss) libdrm_amdgpu1 2.4.120-1.3 (openSUSE-Tumbleweed-Oss) System info from 20240418 snapshot (with proper performance): Operating System: openSUSE Tumbleweed 20240418 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.6-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5625U with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82SG System Version: IdeaPad 5 15ABA7 Graphics drivers from 20240418 snapshot: Mesa version: 24.0.3-1699.375.pm.3 (System Packages) Amdgpu packages: xf86-video-amdgpu 23.0.0-2.2 (openSUSE-Tumbleweed-Oss) kernel-firmware-amdgpu 20240322-2.1 (System Packages) libdrm_amdgpu1 2.4.120-1.3 (openSUSE-Tumbleweed-Oss) Issue description: After updating from the 20240418 snapshot, my system got performance issues. For example, when cycling through tabs in firefox by holding ctrl+tab, it doesn't go through all tabs smoothly. There wasn't such a problem in the 20240418 snapshot. Other performance issue occurs when trying to play videos in a virtual terminal with mpv using the tct output driver (it uses colored Unicode block characters) and sw-fast profile while Plasma is running or a user has logged out of it. mpv drops frames, which doesn't happen on the old snapshot. Bash completion with Plasma running has a delay with completing mpv options, that also didn't happen on the old snapshot. Without Plasma launched the Bash completion seems faster. I've also tested it with IceWM to check if it is directly related to Plasma and here are the combinations and results: 1. Boot, sddm loads, I don’t start any desktop session and switch to virtual console. No frame drops here. 2. Boot, sddm loads, start IceWM desktop session, switch to virtual console. No frame drops here. 3. Boot, sddm loads, start IceWM desktop session and log out of it, switch to virtual console. No frame drops here. 4. Boot, sddm loads, start X11 or Wayland Plasma desktop session, switch to virtual console. Frame drops happen. 5. Boot, sddm loads, start Wayland or X11 Plasma desktop session and log out of it, switch to virtual console. Frame drops happen the same as with Plasma running. It could be an issue with mpv itself, but running it the same way in Konsole (with the tct output driver) doesn't show such performance issues. Bash completion is still slow in Konsole, though. Other issue is a weather forecast website windy.com that has an animated wind map. It worked well on the old snapshot but now it performs very poorly. Tested on firefox. 3D graphics performance in glmark2 seems to be normal and similar to the old snapshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1219562] New: zypper dup killed zypper: can't open librpm.so.9
by bugzilla_noreply＠suse.com 15 Jul '24

15 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1219562 Bug ID: 1219562 Summary: zypper dup killed zypper: can't open librpm.so.9 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: shundhammer(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After not updating my TW VM for two weeks (last zypper dup: 2024-01-17), today's 'zypper dup' destroyed the package management stack: (all commands entered as root) # zypper dup -y --download-only (worked without any problem, downloaded 3181 packages) # zypper dup -y ( 330/3181) Installing: openssl-3-3.1.4-3.2.x86_64 ...........................................................................................[error] Installation of openssl-3-3.1.4-3.2.x86_64 failed: Error: Subprocess failed. Error: RPM failed: Command exited with status 1. Abort, retry, ignore? [a/r/i] (a): a Warning: %posttrans and %transfiletrigger scripts are not executed when aborting! Problem occurred during or after installation or removal of packages: Installation has been aborted as directed. Please see the above error message for a hint. # zypper dup -y zypper: error while loading shared libraries: librpm.so.9: cannot open shared object file: No such file or directory # ldconfig # zypper dup -y zypper: error while loading shared libraries: librpm.so.9: cannot open shared object file: No such file or directory -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1221322] New: cannot open yast software management app, caller yast.rb:186:in `import_pure'
by bugzilla_noreply＠suse.com 14 Jul '24

14 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1221322 Bug ID: 1221322 Summary: cannot open yast software management app, caller yast.rb:186:in `import_pure' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Ruby Assignee: ruby-devel(a)suse.de Reporter: canalcheferaser(a)tutanota.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873462 --> https://bugzilla.suse.com/attachment.cgi?id=873462&action=edit y2log when trying to open yast software management app i get this error: ` Internal error. Please report a bug report with logs. Run save_y2logs to get complete logs. Caller: /usr/lib64/ruby/vendor_ruby/3.3.0/yast/yast.rb:186:in `import_pure' Details: component cannot import namespace 'Pkg' ` I attached the log. Also "sudo zypper dup" doesnt work, with error: ` sudo zypper dup [sudo] password for root: zypper: error while loading shared libraries: libabsl_log_internal_check_op.so.2308.0.0: cannot open shared object file: No such file or directory ` Restarting does not help. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1222019] New: krdc can not connect to VNC hosts in plasma 6
by bugzilla_noreply＠suse.com 13 Jul '24

13 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1222019 Bug ID: 1222019 Summary: krdc can not connect to VNC hosts in plasma 6 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: noreply.section+dev(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After upgrading to Plasma 6, krdc can not connect to VNC hosts anymore. When trying to connect, krdc goes straight to a blue screen. After that, if trying to disconnect, the program freezes and the only way out is to kill the application. The behavior is the same regardless of what string is typed in the address field: i.e. the lock must happen quite early in the program. This still happens in tw 20240325 with krdc 24.02.1. A workaround so far is to use an alternative VNC viewer, such as tigervnc. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1222875] New: ghostwriter crash on start
by bugzilla_noreply＠suse.com 13 Jul '24

13 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1222875 Bug ID: 1222875 Summary: ghostwriter crash on start Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: hol.jimis(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I can not tell from what tumbleweed update it started not working but version 24.02.1-1.3 crashes with segmentation fault (core dumped) ghostwriter The only output I have is Command "pandoc" is not available. Command "multimarkdown" is not available. Command "cmark" is not available. [1] 12170 segmentation fault (core dumped) ghostwriter I installed pandoc, it finds it ok, but the crash seems irrelevant to previous output. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1225451] New: zypper invoked as non-root no more warns about outdated repositories
by bugzilla_noreply＠suse.com 13 Jul '24

13 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225451 Bug ID: 1225451 Summary: zypper invoked as non-root no more warns about outdated repositories Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: arvidjaar(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- andrei@tumbleweed:~> rpm -q zypper zypper-1.14.73-1.2.x86_64 andrei@tumbleweed:~> zypper se no-such-package Loading repository data... Reading installed packages... No matching items found. andrei@tumbleweed:~> grep cpe /var/cache/zypp/raw/repo-oss/repodata/repomd.xml <distro cpeid="cpe:/o:opensuse:opensuse:20240520">openSUSE Tumbleweed</distro> andrei@tumbleweed:~> cat /etc/zypp/repos.d/repo-oss.repo [repo-oss] name=openSUSE-Tumbleweed-Oss enabled=1 autorefresh=1 baseurl=http://download.opensuse.org/tumbleweed/repo/oss/ andrei@tumbleweed:~> Well, as of now the available snapshot is 20240524 so I most certainly expect Repository 'openSUSE-Tumbleweed-OSS' is out-of-date. You can run 'zypper refresh' as root to update it. ... -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1222442] New: [20240404] Xorg crash running Android studio
by bugzilla_noreply＠suse.com 12 Jul '24

12 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1222442 Bug ID: 1222442 Summary: [20240404] Xorg crash running Android studio Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: pujos.michael(a)gmail.com QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since snapshot 20240404 and upgrade of xorg-x11-server (21.1.11 -> 21.1.12), starting Android Studio crashes Xorg hard everytime. Most specifically, I am using Android Studio Koala | 2024.1.1 Canary 3 that can be downloaded here: https://developer.android.com/studio/preview. I would not be surprised this crash happens with other Jetbrains IDE but I have not tried. I triggered 2 crashes, both of which killed the Xorg process. There first crash had a crash stack in journalctl why the other did not: Apr 08 10:06:11 p72 systemd-coredump[16070]: [🡕] Process 11338 (Xorg.bin) of user 1000 dumped core. Stack trace of thread 11338: #0 0x00007f63b22949ec __pthread_kill_implementation (libc.so.6 + 0x949ec) #1 0x00007f63b2241176 raise (libc.so.6 + 0x41176) #2 0x00007f63b2228917 abort (libc.so.6 + 0x28917) #3 0x0000555e1e464efc n/a (/usr/bin/Xorg.bin + 0x1dbefc) #4 0x00007ffee9bf4ba0 n/a (n/a + 0x0) ELF object binary architecture: AMD x86-64 Reverting to 21.1.11 fixes that issue and I have added a lock for package xorg-x11-server for the time being. -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1225264] New: please create group cockpit-bugs
by bugzilla_noreply＠suse.com 12 Jul '24

12 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225264 Bug ID: 1225264 Summary: please create group cockpit-bugs Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: screening-team-bugs(a)suse.de Reporter: jzerebecki(a)suse.com QA Contact: adrian.schroeter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Please create group cockpit-bugs on both OBS and IBS. Thank you. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1221085] New: encfs segfaults
by bugzilla_noreply＠suse.com 12 Jul '24

12 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1221085 Bug ID: 1221085 Summary: encfs segfaults Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: tiwai(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After upgrading from leap 15.5 to 15.6, mounting via encfs causes a segfault. Reverting back to leap 15.5 package fixed. My understanding is that this happens because we now build with openssl3 while it was openssl1 in leap 15.5. When I rebuild the package with libopenssl-1_1-devel instead of openssl-devel, it starts working. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1223336] New: openssl-3: variations in openssl-3-debugsource
by bugzilla_noreply＠suse.com 12 Jul '24

12 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1223336 Bug ID: 1223336 Summary: openssl-3: variations in openssl-3-debugsource Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: otto.hollmann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: pmonrealgonzalez(a)suse.com Blocks: 1062303 Target Milestone: --- Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that our openssl-3 package debugsource varies in /usr/src/debug/openssl-3.1.4/crypto/modes/aes-gcm-avx512.s --- old//usr/src/debug/openssl-3.1.4/crypto/modes/aes-gcm-avx512.s +++ new//usr/src/debug/openssl-3.1.4/crypto/modes/aes-gcm-avx512.s @@ -24,14 +24,14 @@ movl 240(%rdi),%eax cmpl $9,%eax - je .Laes_128_rujxAgiqdxpwrqy + je .Laes_128_ovGcEknxlsxtefb cmpl $11,%eax - je .Laes_192_rujxAgiqdxpwrqy + je .Laes_192_ovGcEknxlsxtefb cmpl $13,%eax ... This file is created by ["/usr/bin/perl", "crypto/modes/asm/../../perlasm/x86_64-xlate.pl", "elf", "crypto/modes/aes-gcm-avx512.s"] called by ["/usr/bin/perl", "crypto/modes/asm/aes-gcm-avx512.pl", "elf", "-I.", "-Iinclude", "-Iproviders/common/include", "-Iproviders/implementations/include", "-fPIC", "-pthread", "-m64", "-Wa,--noexecstack", "-Wall", "-O3", "-march=x86-64-v3", "-O2", "-Wall", "-U_FORTIFY_SOURCE", "-fstack-protector-strong", "-funwind-tables", "-fasynchronous-unwind-tables", "-fstack-clash-protection", "-Werror=return-type", "-flto=auto", "-Wa,--noexecstack", "-fno-common", "-Wall", "-DOPENSSL_USE_NODELETE", "-DL_ENDIAN", "-DOPENSSL_PIC", "-DOPENSSLDIR=\"/etc/ssl\"", "-DENGINESDIR=\"/usr/lib64/engines-3\"", "-DMODULESDIR=\"/usr/lib64/ossl-modules\"", "-DOPENSSL_BUILDING_OPENSSL", "-DZLIB", "-DNDEBUG", "-D_FORTIFY_SOURCE=3", "-DTERMIO", "-DPURIFY", "-D_GNU_SOURCE", "-DOPENSSL_NO_BUF_FREELISTS", "-DSYSTEM_CIPHERS_FILE=\"/etc/crypto-policies/back-ends/openssl.config\"", "-DAES_ASM", "-DBSAES_ASM", "-DCMLL_ASM", "-DECP_NISTZ256_ASM", "-DGHASH_ASM", "-DKECCAK1600_ASM", "-DMD5_ASM", "-DOPENSSL_BN_ASM_GF2m", "-DOPENSSL_BN_ASM_MONT", "-DOPENSSL_BN_ASM_MONT5", "-DOPENSSL_CPUID_OBJ", "-DOPENSSL_IA32_SSE2", "-DPOLY1305_ASM", "-DRC4_ASM", "-DSHA1_ASM", "-DSHA256_ASM", "-DSHA512_ASM", "-DVPAES_ASM", "-DWHIRLPOOL_ASM", "-DX25519_ASM", "crypto/modes/aes-gcm-avx512.s"] and another such call without -march=x86-64-v3 -- You are receiving this mail because: You are on the CC list for the bug.

1 1