June 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1178332] zypper: symbol lookup error: /usr/lib64/libzypp.so.1722: undefined symbol: _ZN4YAML6detail9node_data12empty_scalarB5cxx11E
by bugzilla_noreply＠suse.com 29 Jun '24

29 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1178332 https://bugzilla.suse.com/show_bug.cgi?id=1178332#c31 Anton Smorodskyi <anton.smorodskyi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anton.smorodskyi(a)suse.com --- Comment #31 from Anton Smorodskyi <anton.smorodskyi(a)suse.com> --- I see this error again in Leap 15.5 https://bugzilla.opensuse.org/show_bug.cgi?id=1227202 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227193] KCalc is terrible broken
by bugzilla_noreply＠suse.com 29 Jun '24

29 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1227193 https://bugzilla.suse.com/show_bug.cgi?id=1227193#c3 Heitor da Silva <heitormoreira(a)yahoo.com.br> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|UPSTREAM |--- --- Comment #3 from Heitor da Silva <heitormoreira(a)yahoo.com.br> --- (In reply to Christophe Marin from comment #1) > kcalc isn't particularly better or worse than before. > > But you can install and use kalk instead. Based on your comment anyone can only assume that you have never used KCalc. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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 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 1225278] New: Firefox's Search Provider doesn't work on GNOME (and possibly other DEs)
by bugzilla_noreply＠suse.com 29 Jun '24

29 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225278 Bug ID: 1225278 Summary: Firefox's Search Provider doesn't work on GNOME (and possibly other DEs) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: ant.romano(a)pm.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I'm using openSUSE Tumbleweed w/ snapshot 20240523, Firefox 126.0 (.rpm) and GNOME 46.1. On Firefox, the `browser.gnome-search-provider.enabled` parameter is set to true, while "Firefox" is listed as an enabled search provider on GNOME (Settings -> Search). The "GNOME shell integration" extension is also enabled, although I'm not sure it is required. Despite my premises, Firefox simply does not appear as a search provider when trying to search through GNOME. I've tried searching for solutions or at least for people with the same issue and found out this article from a Fedora: https://mastransky.wordpress.com/2023/10/13/q3-firefox-linux-update/ although I have no idea how to correctly follow the steps he described. I can only state that the Mozilla Firefox Search Provider service indeed is _not_ "Activatable". -- You are receiving this mail because: You are on the CC list for the bug.

1 3