April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1214915] New: Please build Qt5 with configure option -xcb-native-painting
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1214915 Bug ID: 1214915 Summary: Please build Qt5 with configure option -xcb-native-painting Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: Woebbeking(a)web.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, this is an experimental feature to let Qt5 paint as Qt4 did. This improves performance of Qt5 applications under X2Go a lot. First this option was enabled by default but some years later it was disabled to reduce the size of the platform plugin libqxcb.so a little bit. You don't have to worry that you brake something if you enable this option as the user also have to set the environment variable QT_XCB_NATIVE_PAINTING to make it work. Thanks in advance! Cheers, André -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1223134] New: Disable N_GSM
by bugzilla_noreply＠suse.com 16 Oct '24

16 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1223134 Bug ID: 1223134 Summary: Disable N_GSM 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: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- N_GSM is almost unmaintained and full of bugs: https://lore.kernel.org/all/DB9PR10MB5881D2170678C169FB42A423E0082@DB9PR10M… Esp. the 0day reported recently (bug 1222619). It is supposed to be used on special embedded devices only. So let's disable the line discipline. There is jsc#PED-8240 about the same for SLE. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215851] New: code generated by swig < 4.0.0 is incompatible with Python 3.12
by bugzilla_noreply＠suse.com 15 Oct '24

15 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1215851 Bug ID: 1215851 Summary: code generated by swig < 4.0.0 is incompatible with Python 3.12 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869858 --> https://bugzilla.suse.com/attachment.cgi?id=869858&action=edit _log.txt Code generated by swig < 4.0.0 (all Leap and SLE) generates code importing `imp` module, which has been deprecated in 3.4 (i.e., in all our supported Pythons 3) and removed in 3.12. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1221108] New: bmap-tools: FTBFS-2024-06-12
by bugzilla_noreply＠suse.com 15 Oct '24

15 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1221108 Bug ID: 1221108 Summary: bmap-tools: FTBFS-2024-06-12 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: adam(a)mizerski.pl, code(a)bnavigator.de Blocks: 1102840 Target Milestone: --- Found By: --- Blocker: --- I had previously filed this at https://github.com/intel/bmap-tools/issues/116 but then I noticed that * we have a custom patch in that region * we are only at 3.6 while there is already a 3.7 upstream release Please work with the new upstream at Yoctoproject as appropriate. This bug was found while working on reproducible builds for openSUSE. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1221557] New: flatpak runtime org.kde.Platform 6.6 does not reliably verify SSL certs
by bugzilla_noreply＠suse.com 14 Oct '24

14 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1221557 Bug ID: 1221557 Summary: flatpak runtime org.kde.Platform 6.6 does not reliably verify SSL certs Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Flatpak Assignee: rbrown(a)suse.com Reporter: vortex(a)z-ray.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:123.0) Gecko/20100101 Firefox/123.0 Build Identifier: Hello there this came to my attention as OBS Studio updated their flatpak from 30.0.2 to 30.1.0 where they also changed the used runtime form KDE Platform 6.5 to 6.6. Since that update browser sources and browser docks do no longer work if they are pointing at an HTTPS protected site. While with runtime 6.5 it still works fine (more details below). Browser docks are only available in a X11 session due to bugs under Wayland but also the only one to actually show an error message while browser sources are completely silent and simply keep empty. Beside the steps to reproduce other findings made in the meantime before reporting here. This happens on openSUSE Leap 15.6, openSUSE Tumbleweed, openSUSE Aeon and openSUSE Kalpa. Running the OBS Studio flatpak on virtually any other Linux distribution (Tested Ubuntu 22.04, Fedora 39, Arch Linux) does work just fine. Nevertheless I report the bug for Aeon as Aeon and Kalpa heavily rely on flatpaks and this issue is more imminent for them than for regular Tumbleweed and Leap. Other things I tried was running the OBS Studio 30.1.0 *.dep package from inside a Ubuntu 22.04 distrobox container running on my openSUSE Aeon host. Browser sources and docks worked just fine. Also I ran a Ubuntu 22.04 VM on my openSUSE Aeon host using Gnome Boxes and the flatpak version of OBS Studio, browser sources and docks worked just fine too. Furthermore I build the OBS Studio flatpak locally using fkatpab-builder from inside a openSUSE Tumbleweed distrobox using runtime 6.5 instead of 6.6. That OBS Studio flatpak did worked just fine on my openSUSE Aeon and inside the openSUSE Tumlbeweed distrobox container. Whilst building it with 6.6 was broken again. To build OBS Studio with a different runtime do the following: 1) git clone --recursive https://github.com/obsproject/obs-studio.git 2) Change the content of obs-studio/build-aux/com.obsproject.Studio to ruse runtime 6.5 instead of 6.6 (line 4) 3) flatpak-builder --force-clean --install-deps-from=flathub --user --install --ccache --mirror-screenshots-url=https://dl.flathub.org/media/ build-dir build-aux/com.obsproject.Studio.json --user --install Reproducible: Always Steps to Reproduce: 1. Install OBS Studio flatpak 30.1.0 2. Add a browser dock or a browser source pointing to an https site 3. See nothing or in case of a dock the error: ERR_CERT_AUTHORITY_INVALID URL: https://obsproject.com/browser-source Actual Results: Empty browser source or a browser dock showing ERR_CERT_AUTHORITY_INVALID URL: https://obsproject.com/browser-source Expected Results: Browser sources and docks to work Thsi bug was firstly reported to OBS Studio where we found out it's actually the runtime causeing the issue: https://github.com/obsproject/obs-studio/issues/10385 And reported to KDE where they asked me to better open up the issue directly for openSUSE as other distributions are not affected over here: https://bugs.kde.org/show_bug.cgi?id=483746 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1220571] New: [META] Packages failing because GCC 14+ treats some warnings as errors
by bugzilla_noreply＠suse.com 14 Oct '24

14 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1220571 Bug ID: 1220571 Summary: [META] Packages failing because GCC 14+ treats some warnings as errors Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: mjambor(a)suse.com Reporter: mjambor(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- GCC 14 treats the following situations, which were only warnings before, as errors: -Werror=implicit-int -Werror=implicit-function-declaration -Werror=declaration-missing-parameter-type -Werror=return-mismatch -Werror=int-conversion -Werror=incompatible-pointer-types More details about all of these cases together with the most common ways of addressing them and some associated pitfalls is available at https://gcc.gnu.org/gcc-14/porting_to.html For the record, clang has taken a similar step since clang 16, see for example https://www.redhat.com/en/blog/new-warnings-and-errors-clang-16 The preferred method of dealing with these issues is of course fixing the code. Other distributions have shared patches from their porting efforts on relevant upstream mailing lists and bug trackers, Gentoo and RedHat are perhaps most active in this regard, so you can have a look at what they did for their packages at: - https://bugs.gentoo.org/showdependencytree.cgi?id=870412&hide_resolved=0 - https://gitlab.com/fweimer-rh/fedora-modernc/ In case there is for some reason not possible to fix the code, or at least to fix it in time for adoption of GCC 14, it is possible to turn these back to warnings by adding to the compiler options one of the following: -std=gnu89, -std=c89, or -fpermissive. (Especially if you use -fpermissive as a temporary workaround with intention to fix the underlying issues later, I'd suggest leaving the particular bug opened until it is done so.) -- You are receiving this mail because: You are on the CC list for the bug.

1 112

[Bug 1221714] New: GCC 14: fipscheck package fails
by bugzilla_noreply＠suse.com 14 Oct '24

14 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1221714 Bug ID: 1221714 Summary: GCC 14: fipscheck package fails 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: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: meissner(a)suse.com Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Building fipscheck with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to (exhaustive list of errors): filehmac.c: In function ‘compute_file_hmac’: filehmac.c:219:24: error: implicit declaration of function ‘OSSL_PROVIDER_load’ [-Wimplicit-function-declaration] 219 | fips = OSSL_PROVIDER_load(NULL, "fips"); | ^~~~~~~~~~~~~~~~~~ filehmac.c:219:22: error: assignment to ‘OSSL_PROVIDER *’ {aka ‘struct ossl_provider_st *’} from ‘int’ makes pointer from integer without a cast [-Wint-conversion] 219 | fips = OSSL_PROVIDER_load(NULL, "fips"); | ^ filehmac.c:265:32: error: passing argument 3 of ‘EVP_MAC_final’ from incompatible pointer type [-Wincompatible-pointer-types] 265 | EVP_MAC_final(c, rbuf, &hlen, sizeof(rbuf)); | ^~~~~ | | | unsigned int * /usr/include/openssl/evp.h:1228:47: note: expected ‘size_t *’ {aka ‘long unsigned int *’} but argument is of type ‘unsigned int *’ 1228 | unsigned char *out, size_t *outl, size_t outsize); | ~~~~~~~~^~~~ See the meta bug#1220571 for more info. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1223466] New: Mnemosyne failed to start on the latest Tumbleweed snapshot
by bugzilla_noreply＠suse.com 11 Oct '24

11 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1223466 Bug ID: 1223466 Summary: Mnemosyne failed to start on the latest Tumbleweed snapshot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: ecsos(a)schirra.net Reporter: wire.a3n6s(a)simplelogin.com QA Contact: qa-bugs(a)suse.de CC: lars.vogdt(a)suse.com Target Milestone: --- Found By: --- Blocker: --- mnemosyne was installed from the Education repository. It used to work fine but now failed to start since the OS was rolled to the latest snapshot. Environment: * openSUSE Tumbleweed snapshot version 20240426 * mnemosyne version 2.11 from the Education repository (mnemosyne-2.11-3.6.noarch) Reproduce Steps: Start mnemosyne from the commandline: # mnemosyne /usr/lib/python3.11/site-packages/mnemosyne/libmnemosyne/__init__.py:377: UserWarning: google_trans_new package is not installed. Google translate feature will not be available. warnings.warn("google_trans_new package is not installed. Google translate feature will not be available.") QGuiApplication::setDesktopFileName: the specified desktop file name ends with .desktop. For compatibility reasons, the .desktop suffix will be removed. Please specify a desktop file name without .desktop suffix Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/bin/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/libexec/qt6/qtwebengine_dictionaries' Path override failed for key base::DIR_APP_DICTIONARIES and path '/usr/libexec/qt6/qtwebengine_dictionaries' The application won't start. Ctrl-C to stop it, then got following debug information: An unexpected error has occurred. Please forward the following info to the developers: Traceback (innermost last): File "/usr/lib/python3.11/site-packages/mnemosyne/pyqt_ui/review_wdgt.py", line 449, in restore_focus def restore_focus(self): Since it worked fine in March before some OS upgradings (rollings), it may has something to do with the dependencies (maybe some Qt6 libraries). -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1212995] New: KDE Plasma System Settings's printer module cannot add new printers
by bugzilla_noreply＠suse.com 10 Oct '24

10 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1212995 Bug ID: 1212995 Summary: KDE Plasma System Settings's printer module cannot add new printers Classification: openSUSE Product: openSUSE Kalpa Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Desktop Environment Assignee: sfalken(a)cloverleaf-linux.org Reporter: ars2swim(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Overview: Upon attempting to add a new printer in KDE Plasma System Settings, the user is denied permission to do so. Steps to Reproduce: 1) Open System Settings 2) Select Printers 3) Click 'Click here to add a new printer) Actual Results: The window that appears returns no printers and says at the top: "Failed to get a list of devices: 'Forbidden'" Expected Results: The window returns a list of printers and allows you to add them Build date: openSUSE Kalpa 20230619 Additional Information: * This does occur on openSUSE Aeon; the built in printer settings work as expected. * Currently this can be worked around by navigating to https://localhost:631 and adding a printer through the CUPS interface, logging in as the root user when prompted. This implies that it is a permissions issue. * This bug also occurs in openSUSE Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1219866] New: install guix complains about non-existent group and fails
by bugzilla_noreply＠suse.com 10 Oct '24

10 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1219866 Bug ID: 1219866 Summary: install guix complains about non-existent group and fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: ilgaz(a)ilgaz.gen.tr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When I attempt to install guix via 'zypper in guix' on opensuse tw 20240211-2738.1 Problem: nothing provides 'group(guixbuild)' needed by the to be installed guix-1.4.0-1.6.x86_64 Solution 1: do not install guix-1.4.0-1.6.x86_64 Solution 2: break guix-1.4.0-1.6.x86_64 by ignoring some of its dependencies -- You are receiving this mail because: You are on the CC list for the bug.

1 4