March 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1221415] New: [TRACKER] RPM 4.19 generates user()/group() dependencies
by bugzilla_noreply＠suse.com 08 May '24

08 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221415 Bug ID: 1221415 Summary: [TRACKER] RPM 4.19 generates user()/group() dependencies Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other 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: --- Blocker: --- Since RPM 43.19, any file that is installed with explicit ownership e.g %attr(, username, groupname) get's an automatic dependency on user(username) and group(groupname) added, to ensure the requested ownership can be assigned. According to https://en.opensuse.org/openSUSE:Packaging_guidelines#Users_and_Groups there are two methods to generate the user * Creating the users using sysuser_tools (prefer) As described in above wiki article This method adds the user provides/capability automatically to the RPM metadata * Creating users/groups in %pre script * Any user/group generated like this needs to be advertised in the rpm metadata using Provides: user(username) and Provides: group(groupname) Only a single package should ever provide a user -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1221418] New: janus-gateway cannot be installed - missing user() dependency
by bugzilla_noreply＠suse.com 08 May '24

08 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221418 Bug ID: 1221418 Summary: janus-gateway cannot be installed - missing user() dependency 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: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since the upgrade to RPM 4.19, janus-gateway can no longer be installed: > sudo zypper in janus-gateway Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides 'group(janus)' needed by the to be installed janus-gateway-1.1.4-1.3.x86_64 Solution 1: do not install janus-gateway-1.1.4-1.3.x86_64 Solution 2: break janus-gateway-1.1.4-1.3.x86_64 by ignoring some of its dependencies Please see bug#1221415 for more details on possible solutions -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1221438] New: trash_kcm conflicts kio-core
by bugzilla_noreply＠suse.com 08 May '24

08 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221438 Bug ID: 1221438 Summary: trash_kcm conflicts kio-core Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: thomas.rahimi(a)mailbox.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, in the freshly updated OpenSUSE Tumbleweed version 20240311, the trash_kcm plugin for dolphin is missing in my installation. An attempt to install the plugin leads to the message, that this conflicts kio-core and thus would lead to the removal of the overall desktop environment. I'm by far not an expert in KDE Plasma packaging, but I suspect this dependency may be resolved without leading to this conflict. Looking forward to a resolution, if any is possible Kind regards Thomas -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1221546] New: status and notifications, no more icon to check the update of the OS
by bugzilla_noreply＠suse.com 08 May '24

08 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221546 Bug ID: 1221546 Summary: status and notifications, no more icon to check the update of the OS 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: epistemepromeneur(a)free.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After the kde mega release, in "status and notifications" window there is no more the icon for checking if the OS is update or needs to be updated. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1218424] New: go1.22 release tracking
by bugzilla_noreply＠suse.com 07 May '24

07 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1218424 Bug ID: 1218424 Summary: go1.22 release tracking Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- go1.22 (expected February 2024) is a major release of Go. Minor releases of go1.22.x will be provided through February 2025. This issue tracks go1.22.x releases packaged and submitted initially to openSUSE:Factory and can be referenced in submissions to additional repositories. Go Release Cycle https://github.com/golang/go/wiki/Go-Release-Cycle Go Release history https://golang.org/doc/devel/release.html -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1222156] New: After an upgrade the graphical interface no longer works
by bugzilla_noreply＠suse.com 07 May '24

07 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222156 Bug ID: 1222156 Summary: After an upgrade the graphical interface no longer works Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: rm.canella(a)gmail.com QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On my HP 255 G5 Notebook PC, following "zypper dup --no-allow-vendor-change" (openSUSE-20231218-0) the system no longer starts in graphics mode. - I did some checks and the problem seems to be on the "radeonsi_dri" driver; The following error message appears in the dmesg: [ 84.119680] gnome-shell[1557]: segfault at 40 ip 00007ff2ca32b98d sp 00007ffe59c27170 error 4 in radeonsi_dri.so[7ff2c9c91000+1476000] likely on CPU 1 (core 1, socket 0) - Doing an lspci the video card is: 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R3 Graphics] (rev 40) - And the following is the output of the zypper info kernel-firmware-radeon command: Information for package kernel-firmware-radeon: ------------------------------------------------- Repository : Main Repository (OSS) Name : kernel-firmware-radeon Version: 20240322-1.1 Arch : noarch Vendor: openSUSE Installed Size: 3.3 MiB Installed : Yes (automatically) Status: up-to-date Source package : kernel-firmware-20240322-1.1.src Upstream URL: https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/ Summary : Kernel firmware files for Radeon graphics driver Description: This package contains compressed kernel firmware files for Radeon graphics driver. -- You are receiving this mail because: You are on the CC list for the bug.

1 34

[Bug 1217750] New: Nonfunctional brightness keys on Lenovo Slim 7 16" AMD
by bugzilla_noreply＠suse.com 07 May '24

07 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217750 Bug ID: 1217750 Summary: Nonfunctional brightness keys on Lenovo Slim 7 16" AMD Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: variable_valuables761(a)simplelogin.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871117 --> https://bugzilla.suse.com/attachment.cgi?id=871117&action=edit Output of "brightnessctl -l" for Lenovo 16ARH7 It seems the brightness keys (Fn+F5,Fn+F6) do not work in the latest Tumbleweed KDE snapshot on the Lenovo Slim 7 16" AMD, 16ARH7, 82UX0001US (and this same model is called Yoga outside the United States). It seems the internal display's brightness values are bugged and show up as 0 and "0 (-2147483648%)" in brightnessctl rather than something within the expected range. I've attached the output of "brightnessctl -l", which shows the display and some of the keyboard/charging LEDs on the laptop. Glad to provide any other logs that could be helpful. Hope this is the right place to report this. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1221304] New: GCC 14: argyllcms package fails
by bugzilla_noreply＠suse.com 07 May '24

07 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221304 Bug ID: 1221304 Summary: GCC 14: argyllcms package fails 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: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: antonio.teixeira(a)suse.com Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Building argyllcms with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to (exhaustive list of errors): execunix.c: In function ‘execcmd’: execunix.c:238:34: error: passing argument 2 of ‘execvp’ from incompatible pointer type [-Wincompatible-pointer-types] 238 | execvp( argv[0], argv ); | ^~~~ | | | const char ** In file included from execunix.c:45: /usr/include/unistd.h:599:52: note: expected ‘char * const*’ but argument is of type ‘const char **’ 599 | extern int execvp (const char *__file, char *const __argv[]) | ~~~~~~~~~~~~^~~~~~~~ mkjambase.c:27:1: error: return type defaults to ‘int’ [-Wimplicit-int] 27 | main( int argc, char **argv, char **envp ) | ^~~~ 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 1216950] New: openssl-3 should offer ktls capability but has OPENSSL_NO_KTLS enabled
by bugzilla_noreply＠suse.com 07 May '24

07 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1216950 Bug ID: 1216950 Summary: openssl-3 should offer ktls capability but has OPENSSL_NO_KTLS enabled Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: bruno(a)ioda-net.ch QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I've been trying to benefit of ktls support offered by the kernel (6.5.9-1-default as time reporting), but none of the experimentation to implement ktls failed. This is due because OpenSSL 3.1.4 24 has OPENSSL_NO_KTLS defined. Would it be possible to review that parameter, and offer developer and user the same capability that other operating system offer (Fedora for example) ? Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 5

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

07 May '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 14