June 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1226795] Remove VLC and Codecs from base system
by bugzilla_noreply＠suse.com 26 Jun '24

26 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226795 https://bugzilla.suse.com/show_bug.cgi?id=1226795#c3 Shawn Dunn <sfalken(a)cloverleaf-linux.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |WONTFIX --- Comment #3 from Shawn Dunn <sfalken(a)cloverleaf-linux.org> --- VLC is required for the Phonon backend, and will not be removed from the patterns. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227074] New: kscreenlocker_greet wants to auth with smartcard and fingerprint no matter what
by bugzilla_noreply＠suse.com 26 Jun '24

26 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1227074 Bug ID: 1227074 Summary: kscreenlocker_greet wants to auth with smartcard and fingerprint no matter what Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: cmi.brun+susebugzilla(a)protonmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I'm on a fresh install done a few days ago. I don't have and never had a smartcard or a fingerprint reader, yet kscreenlocker_greet keeps trying to use them to auth at every login. It'll output the following upon locking the screen: Jun 25 13:58:30 localhost.localdomain kscreenlocker_greet[3052]: PAM unable to dlopen(/usr/lib64/security/pam_fprintd.so): /usr/lib64/security/pam_fprintd.so: cannot open shared object file: No such file or directory Jun 25 13:58:30 localhost.localdomain kscreenlocker_greet[3052]: PAM adding faulty module: /usr/lib64/security/pam_fprintd.so Jun 25 13:58:30 localhost.localdomain kscreenlocker_greet[3052]: PAM unable to dlopen(/usr/lib64/security/pam_pkcs11.so): /usr/lib64/security/pam_pkcs11.so: cannot open shared object file: No such file or directory Jun 25 13:58:30 localhost.localdomain kscreenlocker_greet[3052]: PAM adding faulty module: /usr/lib64/security/pam_pkcs11.so Then this when unlocking it: Jun 25 13:59:25 localhost.localdomain unix_chkpwd[3514]: password check failed for user (USERNAME) Jun 25 13:59:25 localhost.localdomain kscreenlocker_greet[3052]: pam_unix(kde-fingerprint:auth): authentication failure; logname=USERNAME uid=1000 euid=1000 tty= ruser= rhost= user=USERNAME Jun 25 13:59:25 localhost.localdomain unix_chkpwd[3515]: password check failed for user (USERNAME) Jun 25 13:59:25 localhost.localdomain kscreenlocker_greet[3052]: pam_unix(kde-smartcard:auth): authentication failure; logname=USERNAME uid=1000 euid=1000 tty= ruser= rhost= user=USERNAME I can login and logout, unlock and lock the screen just fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1227068] New: [Wayland] Internal display (eDP) stopped working, only external (HDMI) works
by bugzilla_noreply＠suse.com 26 Jun '24

26 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1227068 Bug ID: 1227068 Summary: [Wayland] Internal display (eDP) stopped working, only external (HDMI) works Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: burnus(a)gmx.de QA Contact: sndirsch(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 875706 --> https://bugzilla.suse.com/attachment.cgi?id=875706&action=edit "wayland-info" output This is on a Lenovo ThinkPad P1 Gen6 with an Intel i7-13800H (→ "i915"/"xe" GPU driver) + Nvidia RTX A1000 6GB Laptop with nvidia-open-driver-G06 ... 550.90.07. After today's update: under Wayland, the internal laptop monitor (eDP) stopped working. Tried with "Plasma (Wayland)" and "GNOME (Wayland)". Under X11, only the internal monitor is visible. I don't know whether that's a regression or was the case before. (I had issues with the proprietary Nvidia driver in the past in this regard: it either only supported the internal one or either the internal or the external; fixed by using the open-kernels driver; cf. bug #1226116). To be precise: Last reboot was June 20 , last kdm re-login last Monday (after first Plasma 6.1 install). Today, Qt 6.7.1, some KDE and a few others (Mesa/Vulcan packages) were installed and the system rebooted. * * * As the issue shows up with KDE and GNOME under Wayland, it seems to be unrelated to the Qt and KDE/Plasma updates. Some of today's RPMs (rpm -qa --last), I hope I haven't missed some crucial package but due to Qt6.7.1 and KDE Framework/Plasma update, the list is rather long - and Qt and KDE have Wayland components. kwayland6-6.1.0-1.2.x86_64 Wed Jun 26 10:56:45 2024 xwaylandvideobridge-0.4.0+git12-3.5.x86_64 Wed Jun 26 10:54:26 2024 libOSMesa8-32bit-24.1.2-382.1.x86_64 Wed Jun 26 10:56:47 2024 libOSMesa8-24.1.2-382.1.x86_64 Wed Jun 26 10:56:47 2024 libQt6WaylandEglCompositorHwIntegration6-6.7.2-1.1.x86_64 Wed Jun 26 10:54:12 2024 Mesa-libva-24.1.2-382.1.x86_64 Wed Jun 26 10:50:33 2024 libvulkan_intel-24.1.2-382.1.x86_64 Wed Jun 26 10:50:31 2024 libvdpau_nouveau-24.1.2-382.1.x86_64 Wed Jun 26 10:50:31 2024 Mesa-vulkan-device-select-24.1.2-382.1.x86_64 Wed Jun 26 10:50:21 2024 Mesa-libglapi0-32bit-24.1.2-382.1.x86_64 Wed Jun 26 10:50:21 2024 Mesa-libglapi0-24.1.2-382.1.x86_64 Wed Jun 26 10:50:20 2024 * * * * Looks fine initially (kdm) but after login (KDE with Wayland), the internal laptop screen is black, but an external screen (HDMI) works - using ALT-CTRL-F... it is possible to change to the terminal or (F2) the used KDM login screen - all of those are shown on the the internal laptop monitor, only. $ kscreen-doctor -o Output: 1 HDMI-A-1 enabled connected priority 1 HDMI Modes: 0:1920x1080@60*! [...] i.e. the internal screen is not seen. * When choosing Plasma X11 instead of Wayland, only the internal monitor works, the external one does not even show up i.e.: $ xrandr Screen 0: minimum 320 x 200, current 2560 x 1600, maximum 16384 x 16384 eDP-1 connected primary 2560x1600+0+0 (normal left inverted right x axis y axis) 344mm x 215mm ... $ kscreen-doctor -o Output: 66 eDP-1 enabled connected priority 1 Panel Modes: 68:2560x1600@165*! [...] While HWINFO sees both: # hwinfo --monitor 31: None 00.0: 10002 LCD Monitor Model: "22FHD_LCD_TV" Vendor: VES Device: eisa 0x3700 "22FHD_LCD_TV" ... Resolution: 1920x1080@60Hz ... Detailed Timings #0: Resolution: 1920x1080 Horizontal: 1920 2448 2492 2640 (+528 +572 +720) +hsync Vertical: 1080 1084 1089 1125 (+4 +9 +45) +vsync Frequencies: 148.50 MHz, 56.25 kHz, 50.00 Hz ... Detailed Timings #1: Resolution: 1920x1080 Horizontal: 1920 2008 2052 2200 (+88 +132 +280) +hsync Vertical: 1080 1084 1089 1125 (+4 +9 +45) +vsync Frequencies: 148.50 MHz, 67.50 kHz, 60.00 Hz Driver Info #0: Max. Resolution: 1920x1080 Vert. Sync Range: 48-62 Hz Hor. Sync Range: 15-70 kHz Bandwidth: 148 MHz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #11 (VGA compatible controller) 32: None 00.0: 10002 LCD Monitor ... Model: "BOE CQ LCD Monitor" Vendor: BOE "BOE CQ" Device: eisa 0x0ae0 Serial ID: "0" Resolution: 2560x1600@60Hz Size: 344x215 mm ... Detailed Timings #0: Resolution: 2560x1600 Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync Vertical: 1600 1603 1609 1732 (+3 +9 +132) +vsync Frequencies: 282.67 MHz, 103.92 kHz, 60.00 Hz Driver Info #0: Max. Resolution: 2560x1600 Vert. Sync Range: 60-165 Hz Hor. Sync Range: 31-31 kHz Bandwidth: 282 MHz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #25 (VGA compatible controller) -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1227092] New: network/boinc-client: Add WorkingDirectory= to unit file (and other possible unit file enhancements)
by bugzilla_noreply＠suse.com 26 Jun '24

26 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1227092 Bug ID: 1227092 Summary: network/boinc-client: Add WorkingDirectory= to unit file (and other possible unit file enhancements) Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: 3rd party software Assignee: chris(a)computersalat.de Reporter: timuzhti(a)gmail.com QA Contact: screening-team-bugs(a)suse.de CC: Sascha.Manns(a)outlook.de Target Milestone: --- Found By: --- Blocker: --- This is a pretty minor issue but without WorkingDirectory= set, the ExecStop= command (/usr/bin/boinccmd --quit) does not actually function because it can't find the gui_rpc_auth.cfg file. This causes the unit to report failure every time it's stopped. According to documentation, boinccmd checks three places for the password (it doesn't have a --datadir option). Changing the working directory to either /var/lib/boinc or ~ (which is the same thing by default) seems to be the easiest way to resolve this, since /etc/boinc-client/ and /var/lib/boinc-client are not used by default. I'm not really sure which of the two options would be better. Using the home directory of the boinc user would probably make it easier to reconfigure to another directory, but I'm not sure that's worth it. It might be even better to somehow pull $BOINC_BOINC_DIR into WorkingDirectory= but systemd doesn't seem to support this. Another quirk uncovered looking at the logs is that systemd apparently interprets /lockfile as part of the variable name, sample log message as follows: (rm): boinc-client.service: Invalid environment variable name evaluates to an empty string: BOINC_BOINC_DIR/lockfile This can be avoided by wrapping the variable name in braces, ExecStopPost=/bin/rm -f ${BOINC_BOINC_DIR}/lockfile though I'm not sure if this is actually a systemd issue. Finally, the upstream unit file at https://github.com/BOINC/boinc/blob/master/client/scripts/boinc-client.serv… includes a couple of systemd hardening options. Some of these are off by default because Atlas requires setuid root, but the three options limiting the read/write access of the unit to the boinc directory only might be worthwhile. ProtectSystem=full ProtectControlGroups=true ReadWritePaths=-/var/lib/boinc -/etc/boinc-client -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227083] regression: Apple keyboard fails reconnecting in 6.9.3, 6.9.5. Works 6.9.1
by bugzilla_noreply＠suse.com 26 Jun '24

26 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1227083 https://bugzilla.suse.com/show_bug.cgi?id=1227083#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pallaswept(a)proton.me, | |tiwai(a)suse.com Flags| |needinfo?(pallaswept@proton | |.me) --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Just to be sure, can you retest with 6.9.6 kernel in OBS Kernel:stable repo? http://download.opensuse.org/repositories/Kernel:/stable/standard/ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227083] New: regression: Apple keyboard fails reconnecting in 6.9.3, 6.9.5. Works 6.9.1
by bugzilla_noreply＠suse.com 26 Jun '24

26 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1227083 Bug ID: 1227083 Summary: regression: Apple keyboard fails reconnecting in 6.9.3, 6.9.5. Works 6.9.1 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: pallaswept(a)proton.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- With kernel 6.9.1, on TW build 0524, when my bluetooth keyboard (a keychron, which uses the 'apple' driver) goes to sleep, I can quickly reconnect, by pressing any key, wait one second, and I can start typing. This required me to enable the 'FastConnectable' bluez option, but has worked well. Upon the TW 0531 upgrade to 6.9.3, I found this no longer working. Connections from the keyboard to the machine take several seconds to connect, if the keyboard is untouched. If I press a key during this time, the lights flash faster, and the sequence starts over. This can be prolonged indefinitely. I have checked, and the device (intel AX200) firmware was not updated, and booting to 6.9.1 worked, so the issue does not appear to be bluez (which was also updated at the same time) or firmware, so it seems to be kernel. This probably seems inconsequential, but with my disabilities, this dictated an instant rollback to 0524, so I'm sorry that I couldn't get logs for this. I tried to boot to the live image to see if I could collect any, but saw no messages in journalctl other than the normal. I read other issues which mentioned there might be a fix in 6.9.5, so waited for that before reporting. Thanks for any help! -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1227081] New: dbus-broker-launch[2047]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
by bugzilla_noreply＠suse.com 26 Jun '24

26 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1227081 Bug ID: 1227081 Summary: dbus-broker-launch[2047]: Activation request for 'org.freedesktop.nm_dispatcher' failed. Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: simonf.lees(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- With the move from dbus to dbus-broker, we are now seeing the following error message when NetworkManager is shutdown dbus-broker-launch[2047]: Activation request for 'org.freedesktop.nm_dispatcher' failed. The question is, does this failure matter at a point when network manager is already being shutdown. Below is some more detailed snippets from openqa's Journal. Sometimes the timing is slightly different but it always happens after network manager has started shutting down. Jun 24 16:15:23.017670 localhost.localdomain systemd[1]: Stopped target Network. Jun 24 16:15:23.018332 localhost.localdomain systemd[1]: Stopped target Remote File Systems. Jun 24 16:15:23.018713 localhost.localdomain NetworkManager[806]: <info> [1719245723.0186] caught SIGTERM, shutting down normally. Jun 24 16:15:23.019259 localhost.localdomain NetworkManager[806]: <info> [1719245723.0192] dhcp4 (ens4): canceled DHCP transaction Jun 24 16:15:23.019270 localhost.localdomain NetworkManager[806]: <info> [1719245723.0192] dhcp4 (ens4): activation: beginning transaction (timeout in 45 seconds) Jun 24 16:15:23.019279 localhost.localdomain NetworkManager[806]: <info> [1719245723.0192] dhcp4 (ens4): state changed no lease Jun 24 16:15:23.019402 localhost.localdomain NetworkManager[806]: <info> [1719245723.0193] manager: NetworkManager state is now CONNECTED_SITE Jun 24 16:15:23.020526 localhost.localdomain systemd[1]: Stopping Network Manager... Jun 24 16:15:23.028049 localhost.localdomain dbus-broker-launch[804]: Activation request for 'org.freedesktop.nm_dispatcher' failed. Jun 24 16:15:23.028622 localhost.localdomain NetworkManager[806]: <info> [1719245723.0286] exiting (success) Jun 24 16:15:23.034610 localhost.localdomain systemd[1]: run-user-0.mount: Deactivated successfully. Jun 24 16:15:23.036340 localhost.localdomain systemd[1]: Unmounted /run/user/0. Jun 24 16:15:23.037099 localhost.localdomain systemd[1]: user-runtime-dir(a)0.service: Deactivated successfully. Jun 24 16:15:23.037269 localhost.localdomain systemd[1]: Stopped User Runtime Directory /run/user/0. Jun 24 16:15:23.039021 localhost.localdomain systemd[1]: Removed slice User Slice of UID 0. Jun 24 16:15:23.039249 localhost.localdomain systemd[1]: user-0.slice: Consumed 4.552s CPU time. Jun 24 16:15:23.059794 localhost.localdomain systemd[1]: NetworkManager.service: Deactivated successfully. Jun 24 16:15:23.060274 localhost.localdomain systemd[1]: Stopped Network Manager. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1226825] New: podman erros with "configure storage: unknown option overlay.mountopt"
by bugzilla_noreply＠suse.com 26 Jun '24

26 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226825 Bug ID: 1226825 Summary: podman erros with "configure storage: unknown option overlay.mountopt" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Using distrobox/podman containers on MicroOS and with the last snapshot of Tumbleweed I get this on any podman command I run: ERRO[0000] User-selected graph driver "overlay" overwritten by graph driver "btrfs" from database - delete libpod local files ("/var/lib/containers/storage") to resolve. May prevent use of images created by other tools Error: configure storage: unknown option overlay.mountopt ("overlay.mountopt=nodev,metacopy=on") Unfortunately, it also breaks my main working container (`distrobox --root`). mitmanek:~ $ cat /etc/os-release NAME="openSUSE MicroOS" # VERSION="20240621" ID="opensuse-microos" ID_LIKE="suse opensuse opensuse-tumbleweed microos sl-micro" VERSION_ID="20240621" PRETTY_NAME="openSUSE MicroOS" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:microos:20240621" BUG_REPORT_URL="https://bugzilla.opensuse.org" SUPPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:MicroOS" LOGO="distributor-logo-MicroOS" mitmanek:~ $ -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1226830] sdlpop is installed in an inappropriate location
by bugzilla_noreply＠suse.com 26 Jun '24

26 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226830 https://bugzilla.suse.com/show_bug.cgi?id=1226830#c1 Andrea Manzini <andrea.manzini(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |andrea.manzini(a)suse.com Resolution|--- |FIXED CC| |andrea.manzini(a)suse.com Status|NEW |RESOLVED --- Comment #1 from Andrea Manzini <andrea.manzini(a)suse.com> --- changed binary and asset data location with https://build.opensuse.org/request/show/1183437 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227076] New: Tumbleweed update 20240624 breaks KDE
by bugzilla_noreply＠suse.com 26 Jun '24

26 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1227076 Bug ID: 1227076 Summary: Tumbleweed update 20240624 breaks KDE Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: alanhants(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Following an routine update to Tumbleweed 20242624, the following issues have been noted that make the KDE UI effectively unusable: 1. The graphical icons for all widgets appear to have disappeared; no icons are show for widgets when the list of icons (using "Add Widget") is shown, and existing widgets disappear apart from the label. 2. Icons on the Task Manager move to the extreme left (i.e. over the menu application) when the mouse is moved over them, although the icon areas on the Task Manager remain. Issues are reproducible on both Wayland and X11. Rolling back to the previous release did not fix the problem, from which I assume that a configuration change has been made that is not easily reversible. -- You are receiving this mail because: You are on the CC list for the bug.

1 0