June 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1227199] New: xdg-desktop-portal-wlr no longer captures desktop
by bugzilla_noreply＠suse.com 29 Jun '24

29 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1227199 Bug ID: 1227199 Summary: xdg-desktop-portal-wlr no longer captures desktop Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: jsmithfpv(a)gmail.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- This was reported to me on Matrix and I had reproduced the issue. Both on snapshot 20240627. Since updating, desktop capture no longer works across multiple compositors. I had tested multiple compositors, sway and river. Relevant logs systemctl status --user xdg-desktop-portal ``` Jun 29 06:18:24 Tylwyth systemd[2539]: Starting Portal service... Jun 29 06:18:24 Tylwyth systemd[2539]: Started Portal service. ``` systemctl status --user xdg-desktop-portal-wlr ``` Jun 29 06:18:24 Tylwyth systemd[2539]: Starting Portal service (wlroots implementation)... Jun 29 06:18:24 Tylwyth systemd[2539]: Started Portal service (wlroots implementation). ``` systemctl status --user wireplumber ``` Jun 29 06:21:40 Tylwyth systemd[2539]: Started Multimedia Service Session Manager. Jun 29 06:21:40 Tylwyth wireplumber[36783]: default: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner Jun 29 06:21:40 Tylwyth wireplumber[36783]: wp-event-dispatcher: <WpAsyncEventHook:0x555a5bfd7f70> failed: <WpSiStandardLink:0x555a5c00bc00> link failed: some node was destroyed before the link was created Jun 29 06:21:40 Tylwyth wireplumber[36783]: wp-event-dispatcher: <WpAsyncEventHook:0x555a5bfd7f70> failed: failed to configure si-standard-link <WpSiStandardLink:0x555a5c1c6b60> Jun 29 06:21:41 Tylwyth wireplumber[36783]: [0:35:20.234047080] [36783] WARN IPAManager ipa_manager.cpp:154 No IPA found in '/usr/lib64/libcamera' Jun 29 06:21:41 Tylwyth wireplumber[36783]: [0:35:20.234095802] [36783] INFO Camera camera_manager.cpp:284 libcamera v0.2.0 ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1227153] Leap 15.6 Linux 6.4.0.150600.23.7 boot hanger; former Linux ~.21 works
by bugzilla_noreply＠suse.com 29 Jun '24

29 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1227153 https://bugzilla.suse.com/show_bug.cgi?id=1227153#c3 --- Comment #3 from Peter Thoms <p.thoms(a)t-online.de> --- Created attachment 875779 --> https://bugzilla.suse.com/attachment.cgi?id=875779&action=edit sudo inxi -Fxz sudo inxi -Fxz -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227194] New: ‘mount -t cifs’ then ‘ls /mnt’ causes “soft lockup - CPU#0 stuck”. Can’t kill -9 nor init s, etc
by bugzilla_noreply＠suse.com 29 Jun '24

29 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1227194 Bug ID: 1227194 Summary: ‘mount -t cifs’ then ‘ls /mnt’ causes “soft lockup - CPU#0 stuck”. Can’t kill -9 nor init s, etc Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: hattons(a)speakeasy.net 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: Every time I do: USS-Liberty:~ # mount -t cifs //192.168.99.78/elements -o username=hattons /mnt/elements Password for hattons(a)//192.168.99.78/elements: followed by ‘ls /mnt’, I get 2024-06-27T03:48:38.093101-04:00 USS-Liberty kernel: [ 2664.161932][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 1643s! [ls:5764] etc. I can’t ‘kill -9 5764’, ‘reboot’, ‘halt’, ‘init s’, etc. Other CPUs start to get stuck on other processes. I haven’t been using Linux for several years, but in the good old days, this wasn’t supposed to happen. Reproducible: Always Steps to Reproduce: 1. # mount -t cifs //192.168.99.78/<share> -o username=<user> /mnt/<mount point> 2. ‘ls /mnt’ 3. Actual Results: I get repeated messages of the form 2024-06-27T03:48:38.093101-04:00 USS-Liberty kernel: [ 2664.161932][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 1643s! [ls:5764] I can’t ‘kill -9 5764’, ‘reboot’, ‘halt’, ‘init s’, etc. Other CPUs start to get stuck on other processes. Expected Results: Expected the remote share to either be mounted an ls to show me the contents of /mnt, or receive an error indicating a failure of the mount and/or ls commands. This is very deterministic. I have nothing to compare it to because it is my first Linux install in years, and I don't have a second machine to test with. There is, however, this: https://forums.opensuse.org/t/mount-t-cifs-then-ls-mnt-causes-soft-lockup-c… Unfortunately, I did a reinstall since I last crashed the machine, so I don't have logs. If you can't reproduce the result, I will try again. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1227201] New: 1
by bugzilla_noreply＠suse.com 29 Jun '24

29 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1227201 Bug ID: 1227201 Summary: 1 Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: BlackBerry 10.x Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: screening-team-bugs(a)suse.de Reporter: gautreauxa4(a)gmail.com QA Contact: adrian.schroeter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- 1\ -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1227200] New: kdeconnect crashes after upgrading to Leap:15.6
by bugzilla_noreply＠suse.com 29 Jun '24

29 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1227200 Bug ID: 1227200 Summary: kdeconnect crashes after upgrading to Leap:15.6 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: davejplater(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875777 --> https://bugzilla.suse.com/attachment.cgi?id=875777&action=edit KDE crash trace back I already had kdeconnect running when my system was Leap:15.5 but after doing a zypper dup --allow-vendor change with only Main repository and dvd enabled, whenever my phone with kdeconnect installed tries to connect kdeconnect on my pc apparently crashes. I've installed updates and removed any packages that have lp155 then restored the unrestricted packages I had before it's still the same. I've tried gdb on kdeconnectd but when the unhappy face appears on the taskbar about eight times it simply says process exited normally. I'll attach the kde crash trace but I can't fathom anything from it. Surprisingly nobody else has filed a bug. to get the crash I open kdeconnect on my phone (same version as before) and it crashes continually. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1227196] New: mygnuhealth fails on startup with "ModuleNotFoundError: No module named 'bleak'" in Tumbleweed container
by bugzilla_noreply＠suse.com 29 Jun '24

29 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1227196 Bug ID: 1227196 Summary: mygnuhealth fails on startup with "ModuleNotFoundError: No module named 'bleak'" in Tumbleweed container Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: axel.braun(a)gmx.de Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- ## Observation In a clean openSUSE Tumbleweed container I installed just mygnuhealth just to check if all necessary dependencies are provided and I found mygnuhealth eventually fails with "ModuleNotFoundError: No module named 'bleak'": ``` # mygnuhealth [WARNING] [Config ] Older configuration version detected (0 instead of 27) [WARNING] [Config ] Upgrading configuration in progress. [DEBUG ] [Config ] Upgrading from 0 to 1 [INFO ] [Logger ] Record log in /root/.kivy/logs/kivy_24-06-29_0.txt [INFO ] [Kivy ] v2.3.0 [INFO ] [Kivy ] Installed at "/usr/lib64/python3.11/site-packages/kivy/__init__.py" [INFO ] [Python ] v3.11.9 (main, Apr 08 2024, 06:18:15) [GCC] [INFO ] [Python ] Interpreter at "/usr/bin/python3.11" [INFO ] [Logger ] Purge log fired. Processing... [INFO ] [Logger ] Purge finished! [INFO ] [Factory ] 195 symbols loaded [INFO ] [Image ] Providers: img_tex, img_dds, img_sdl2, img_pil (img_ffpyplayer ignored) [INFO ] [Text ] Provider: sdl2(['text_pango'] ignored) Initializing MyGNUHealth version 2.2.0 MyGNUHealth local config and db files wil go into dir: /root/.config/mygnuhealth Initializing MyGNUHealth directory Configuration file not found. Writing defaults Verifying MyGNUHealth Database..... DB file not found. [INFO ] [Window ] Provider: sdl2 error: XDG_RUNTIME_DIR is invalid or not set in the environment. [INFO ] [GL ] Using the "OpenGL" graphics system [INFO ] [GL ] Backend used <sdl2> [INFO ] [GL ] OpenGL version <b'4.5 (Compatibility Profile) Mesa 24.1.2'> [INFO ] [GL ] OpenGL vendor <b'Mesa'> [INFO ] [GL ] OpenGL renderer <b'llvmpipe (LLVM 18.1.6, 256 bits)'> [INFO ] [GL ] OpenGL parsed version: 4, 5 [INFO ] [GL ] Shading version <b'4.50'> [INFO ] [GL ] Texture max size <16384> [INFO ] [GL ] Texture max units <32> [INFO ] [Window ] auto add sdl2 input provider [INFO ] [Window ] virtual keyboard not allowed, single mode, not docked Traceback (most recent call last): File "/usr/bin/mygnuhealth", line 5, in <module> from mygnuhealth import main File "/usr/lib/python3.11/site-packages/mygnuhealth/main.py", line 76, in <module> from mygnuhealth.bluetooth_settings import BluetoothSettings as bluetooth File "/usr/lib/python3.11/site-packages/mygnuhealth/bluetooth_settings.py", line 30, in <module> from bleak import BleakScanner ModuleNotFoundError: No module named 'bleak' ``` ## Steps to reproduce * Run `podman run --pull=newer --rm -it registry.opensuse.org/opensuse/tumbleweed sh -c 'zypper -n in mygnuhealth && mygnuhealth'` ## Expected result mygnuhealth should fail with clear error messages (which might already show up) but should not fail with a not found module ## Suggestions * Obviously there is no good realistic use case behind running mygnuhealth in a headless container but maybe this just needs simple fixing of package runtime dependencies -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1227182] Builtin microphone doesn't work on OMEN by HP Gaming Laptop 16-n0xxx
by bugzilla_noreply＠suse.com 29 Jun '24

29 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1227182 https://bugzilla.suse.com/show_bug.cgi?id=1227182#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- The upstream and Leap 15.6 kernel had the quirk entry for HP OMEN 16-n0xxx (8A42) in the commit ee4281de4d60288b9c802bb0906061ec355ecef2, and it's .matches = { DMI_MATCH(DMI_BOARD_VENDOR, "HP"), DMI_MATCH(DMI_BOARD_NAME, "8A42"), } I suppose yours doesn't match, even though it's the same name HP OMEN 16-n0xxx? Could you give the output grep -Hr . /sys/class/dmi/id ?? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225965] New: Improve KDE Discover bug reporting button
by bugzilla_noreply＠suse.com 29 Jun '24

29 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225965 Bug ID: 1225965 Summary: Improve KDE Discover bug reporting button Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de CC: shundhammer(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Whenever we have a generic package issues that affects multiple users like (bug 1225174), we get a whole to of bug reports and duplicates. All that users seem to be doing is copy the text "<html>Dependency resolution failed:<br/><br/>[...] </html>", report a bug in a random component. Bonus: If the component is YaST, Huha gets angry like in bug 1225949. We do not see the bugs that were not reported due to bugzilla pointing out the possible duplicate, but in the example above we got 14 reports. These users may or may not have read through the duplicated bug, or read the recommendation there. https://github.com/KDE/discover/blob/d644b2a1000c04f084d39a4ef8a3402abf6417… Let's improve user experience here. Some ideas: 0. Direct the user to zypper/YaST for self-service resolution of the conflict. 1. Direct the user to a landing page with instructions for #0. 2. Direct the user to bugzilla search first 3. Take the message - extract package names only, strip arch/installed version, sort, and make a hash from it. Use that as the bug alias for automatic reduplication. 4. or even a fuzzy hash 5. Use a bugzilla whiteboard field with self-service fix instructions -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1227192] New: Can't run system upgrade
by bugzilla_noreply＠suse.com 29 Jun '24

29 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1227192 Bug ID: 1227192 Summary: Can't run system upgrade 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: dlpville(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Dependency resolution failed the to be installed phonon-vlc-qt5-0.12.0-2.3.x86_64 requires vlc = 3.0.21;, but this requirement cannot be provided the to be installed phonon-vlc-qt6-0.12.0-2.3.x86_64 requires vlc-noX = 3.0.21, but this requirement cannot be provided -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1226065] New: Trackpad does not work after suspend/resume
by bugzilla_noreply＠suse.com 29 Jun '24

29 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226065 Bug ID: 1226065 Summary: Trackpad does not work after suspend/resume 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: David(a)WalkerStreet.info QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The trackpad on my Framework Gen 11 laptop stopped working after a suspend/resume cycle. The problem turned out to be that I had accidentally enabled secure boot: Jun 06 19:18:01 homelap8.WalkerStreet.info kernel: mousedev: PS/2 mouse device common for all mice Jun 06 19:18:05 homelap8.WalkerStreet.info kernel: Lockdown: vmmouse_detect: raw io port access is restricted; see man kernel_lockdown.7 Disabling secure boot fixes the trackpad problem and eliminates the lockdown log message. It looks like there's some issue in mousedev when secure boot is enabled. -- You are receiving this mail because: You are on the CC list for the bug.

1 14