November 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1233535] New: After login to KDE, external monitor brightness is decreased to 38%
by bugzilla_noreply＠suse.com 23 Dec '24

23 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233535 Bug ID: 1233535 Summary: After login to KDE, external monitor brightness is decreased to 38% Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: opensuse(a)wolli.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- OS: OpenSUSE Tumbleweed Kernel 6.11.8-1-default KDE plasma 6.2.3 Wayland Hardware: Laptop Acer Aspire A515-56 Mesa Intel® Xe Graphics Monitor: Lenovo t34w-20, resolution: 3440x1440 Issue: After login to KDE, external monitor brightness is decreased to 38% -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1231548] New: rusty_v8: packages .o files
by bugzilla_noreply＠suse.com 23 Dec '24

23 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1231548 Bug ID: 1231548 Summary: rusty_v8: packages .o files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: aavindraa(a)gmail.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: amajer(a)suse.com Blocks: 1062303 Target Milestone: --- Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that our rusty_v8 package contains files that it probably should not. These have varying names (probably from LTO) such as /usr/lib64/crates/rusty_v8/false/build_script_build-0knbljou9qk3j/s-h0nd8jyxiz-07i8ehl-b7257ohw54kiru274s258lfjp/019rsrysgg6rpjdf91ex4lbvj.o The 'false' in the path makes me think that someone tried to disable it, but failed. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1233803] New: kernel: ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed
by bugzilla_noreply＠suse.com 22 Dec '24

22 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233803 Bug ID: 1233803 Summary: kernel: ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed 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: suse.junky(a)t-online.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In the journal of my system I found this error reported: Nov 27 07:14:17 kernel: ucsi_acpi USBC000:00: error -ETIMEDOUT: PPM init failed My system is a Clevo NS70AU laptop with Operating System: openSUSE Tumbleweed 20241125 KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Kernel Version: 6.11.8-1-default (64-bit) Graphics Platform: X11 Processors: 16 × 13th Gen Intel® Core™ i7-1360P Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Iris® Xe Graphics 1 x USB-A 2.0 1 x USB-A 3.2 Gen2 1 x USB-C 3.2 Gen2 1 x Thunderbolt 4 (USB-C) I could not detect any malfunction so far. If more information is needed please let me know. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1229744] New: [Build 20240825] Upgreade from 15.0 to TW: dbus-broker not operational
by bugzilla_noreply＠suse.com 21 Dec '24

21 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1229744 Bug ID: 1229744 Summary: [Build 20240825] Upgreade from 15.0 to TW: dbus-broker not operational Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4434922/modules/zypp er_ref/steps/60 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation This seems only to happen on old upgrade scenarios - so I assign it 'normal' priority. After upgrading, Network is not operational, likely due to the dbus service not running (switched to dbus-broker in this snapshot) WE see similar issues in transactional and non-transactional systems (possibly install order, preset errors, ….) openQA test in scenario opensuse-Tumbleweed-NET-x86_64-upgrade_Leap_15.0_gnome@64bit fails in [zypper_ref](https://openqa.opensuse.org/tests/4434922/modules/zypper_ref/st… ## Test suite description Upgrade scenario from Leap 15.0 with gnome installed. ## Reproducible Fails since (at least) Build [20240825](https://openqa.opensuse.org/tests/4432596) ## Expected result Last good: [20240823](https://openqa.opensuse.org/tests/4430330) (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 3

[Bug 1231408] New: VUL-0: CVE-2024-25885: python-xhtml2pdf: regular expression denial of service through the getcolor function in utils.py
by bugzilla_noreply＠suse.com 21 Dec '24

21 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1231408 Bug ID: 1231408 Summary: VUL-0: CVE-2024-25885: python-xhtml2pdf: regular expression denial of service through the getcolor function in utils.py Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/423265/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: python-maintainers(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- An issue in the getcolor function in utils.py of xhtml2pdf v0.2.13 allows attackers to cause a Regular expression Denial of Service (ReDOS) via supplying a crafted string. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-25885 https://www.cve.org/CVERecord?id=CVE-2024-25885 http://dirk.com http://xhtml2pdf.com https://gist.github.com/salvatore-abello/c88dd0027496774023ef36c7b576d206 -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1230884] New: Kde connect fails to access android filesystem giving 'Error when accessing filesystem. sshfs finished with exit code 1'
by bugzilla_noreply＠suse.com 21 Dec '24

21 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1230884 Bug ID: 1230884 Summary: Kde connect fails to access android filesystem giving 'Error when accessing filesystem. sshfs finished with exit code 1' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: fijik19(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Kde connect fails to browse files from dolphin with error: 'Error when accessing filesystem. sshfs finished with exit code 1', when i pair device, unpair device and pair again Steps to reproduce: 1. Connect to the device with kdeconnect 2. Browse device files via dolphin 3. Disconnect to the device with kdeconnect 4. Connect to the device with kdeconnect again 5. Browse device files via dolphin Expected result: Files browsed successfully Result: Giving error described above -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1224452] New: installing audacious pulls in -devel packages
by bugzilla_noreply＠suse.com 21 Dec '24

21 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1224452 Bug ID: 1224452 Summary: installing audacious pulls in -devel packages Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: kocelfc(a)tutanota.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874956 --> https://bugzilla.suse.com/attachment.cgi?id=874956&action=edit zypper.log When trying to install the audacious package, zypper tries to pull in a lot of -devel packages: The following recommended package was automatically selected: audacious-plugins-extra The following 64 NEW packages are going to be installed: at-spi2-core-devel audacious audacious-plugins audacious-plugins-extra dbus-1-devel glib2-devel libaudcore5 libaudgui5 libaudqt2 libaudtag3 libblkid-devel libcddb2 libcue2 libdrm-devel libeconf-devel libffi-devel libfluidsynth3 libgirepository-2_0-0 libglvnd-devel libinstpatch-1_0-2 liblirc_client0 libmms0 libmodplug1 libmount-devel libopusfile0 libpciaccess-devel libpcre2-32-0 libpcre2-posix3 libselinux-devel libsepol-devel libsidplayfp6 libsndio7 libstdc++-devel libX11-devel libXau-devel libxcb-dbe0 libxcb-devel libxcb-screensaver0 libxcb-xf86dri0 libxcb-xtest0 libxcb-xvmc0 libXext-devel libXfixes-devel libXi-devel libxkbcommon-devel libXrandr-devel libXrender-devel libXtst-devel Mesa-KHR-devel Mesa-libEGL-devel Mesa-libGL-devel pcre2-devel qt6-core-devel qt6-dbus-devel qt6-gui-devel qt6-svg-devel qt6-widgets-devel typelib-1_0-Atspi-2_0 typelib-1_0-GIRepository-3_0 typelib-1_0-GLibUnix-2_0 vulkan-devel vulkan-headers wayland-devel xorgproto-devel -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1225296] New: Dual monitor not recognised after upgrade 15.5 to 15.6
by bugzilla_noreply＠suse.com 20 Dec '24

20 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1225296 Bug ID: 1225296 Summary: Dual monitor not recognised after upgrade 15.5 to 15.6 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: martin.schmidt(a)io-warnemuende.de QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Moin, moin, I am using openSUSE 15.5 on an old intel based x86 PC, equipped with a simple nvidia gforce and two monitors. The monitors are using a displayport connnection from the graphics card to the monitors via an Y-shaped cable. Both monitors are recognised correctly and can be configured to form a single graphical work space, when the system is up and running. After upgrading to openSUSE 15.6 this does not work any more. When booting, monitor 1 shows some firmware screen and the openSUSE boot screen, where the OS version (several subversions of 15.6 and frozen snapshots of 15.5) can be selected. Using the default option (15.6 from harddrive), the output of the boot process is moving to monitor 2, but monitor 1 is going to a "power saving sleep mode" and stays inactive frome here on. The boot process is finished correctly with monitor 2 as the only graphical device. Monitor 1 cannot be activated again. Switching off monitor 2 before booting, the system comes up without any valid output device. Monitor 1 goes to sleep after the system boot started. I did not check the system status with a remote ssh-connection yet. Switching off monitor 1 before booting, lets the system come up completely with monitor 2. Also the initial hardware screen is diplayerd there. In turn, booting from a read-only snapshot with openSUSE 15.5, both monitors are used as before. The nouveau-dri drivers are used, no propriatary nvidia driver is installed. Some upgrade history: - just to test, if the few graphic card cores could be used in a cuda environment, cuda was installed under 15.5. This failed and cuda was deinstalled. However, when upgrading later from 15.5 to 15.6 the cuda development environment was reinstalled automatically together with nvidia drivers. As a result the nvidia drivers allowed only for a single low resolution vga monitor. May be, this happened, since the nvidia repository was not deleted and there was some leftover from the cuda test. - with the ascii-yast the nvidia drivers (gforce003/004) and cuda could be removed and the nouveau-dri drivers where reinstalled - together with dependencies. This allows for a single monitor OS_15.6 system with high resolution, but the second monitor (monitor 1) is lost during the boot process as described above. Before I try to install from scratch just with the hope that the error goes away, I am reporting this strange behaviour here. May be, this helps to streamline the distribution. Any hints are very welcome - especially how to modify the bootloader options. Cheers, Martin Schmidt -- You are receiving this mail because: You are on the CC list for the bug.

1 33

[Bug 1233358] New: [SELinux] AVC denial for sdbootutil during snapper cleanup
by bugzilla_noreply＠suse.com 20 Dec '24

20 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233358 Bug ID: 1233358 Summary: [SELinux] AVC denial for sdbootutil during snapper cleanup Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On my Tumbleweed system with systemd-boot + TPM backed FDE and the SELinux targeted policy in enforcing mode, I found some AVC denials which were triggered by snapper-cleanup.service. snapper cleanup runs sdbootutil which in turn executes systemd-pcrlock: type=AVC msg=audit(14.11.2024 10:13:13.145:227) : avc: denied { execute } for pid=6038 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.145:228) : avc: denied { execute } for pid=6038 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.319:229) : avc: denied { execute } for pid=6082 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.319:230) : avc: denied { execute } for pid=6082 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.482:231) : avc: denied { execute } for pid=6126 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.482:232) : avc: denied { execute } for pid=6126 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.652:233) : avc: denied { execute } for pid=6170 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.652:234) : avc: denied { execute } for pid=6170 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.829:235) : avc: denied { execute } for pid=6214 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.829:236) : avc: denied { execute } for pid=6214 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.999:237) : avc: denied { execute } for pid=6258 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:13.999:238) : avc: denied { execute } for pid=6258 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:14.175:239) : avc: denied { execute } for pid=6302 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 type=AVC msg=audit(14.11.2024 10:13:14.175:240) : avc: denied { execute } for pid=6302 comm=sdbootutil name=systemd-pcrlock dev="dm-0" ino=659797 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:systemd_pcrlock_exec_t:s0 tclass=file permissive=0 -- You are receiving this mail because: You are on the CC list for the bug.

1 21

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

20 Dec '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 13