September 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1219405] New: older clang package depends on latest libLLVM
by bugzilla_noreply＠suse.com 19 Nov '24

19 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1219405 Bug ID: 1219405 Summary: older clang package depends on latest libLLVM Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: shung-hsi.yu(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Trying to install older clang will pull in the latest llvm package (libclang13 and libLLVM17): > $ zypper install clang16 # (latest is clang17 at the moment) > > The following 11 NEW packages are going to be installed: > clang16 libLLVM16 libLLVM17 libclang-cpp16 libclang-cpp17 libclang13 > libedit0 libmpdec3 libpython3_11-1_0 python311-base update-alternatives The problem is likely that c-index-test-16 is incorrectly linked to /lib64/libclang.so.13 that is created from the latest llvm package (llvm17 at the moment), and that ends up making it linked to both the latest llvm shared library (libLLVM.so.17 from llvm17) as well as one in the corresponding package (libLLVM.so.16 from llvm16). > $ ldd /usr/bin/c-index-test-16.0.6 > linux-vdso.so.1 (0x00007ffce2336000) > libclang.so.13 => /lib64/libclang.so.13 (0x00007fb21ca18000) > libclang-cpp.so.16 => /lib64/libclang-cpp.so.16 (0x00007fb218800000) > libxml2.so.2 => /lib64/libxml2.so.2 (0x00007fb218690000) > libLLVM.so.16 => /lib64/libLLVM.so.16 (0x00007fb211200000) > libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007fb210e00000) > libc.so.6 => /lib64/libc.so.6 (0x00007fb210a00000) > libclang-cpp.so.17 => /lib64/libclang-cpp.so.17 (0x00007fb20c800000) > libLLVM.so.17 => /lib64/libLLVM.so.17 (0x00007fb205200000) > libm.so.6 => /lib64/libm.so.6 (0x00007fb21c92f000) > /lib64/ld-linux-x86-64.so.2 (0x00007fb21cb11000) > libz.so.1 => /lib64/glibc-hwcaps/x86-64-v3/libz.so.1.3 (0x00007fb218676000) > liblzma.so.5 => /lib64/glibc-hwcaps/x86-64-v3/liblzma.so.5.4.5 (0x00007fb21863d000) > libedit.so.0 => /lib64/libedit.so.0 (0x00007fb218601000) > libtinfo.so.6 => /lib64/libtinfo.so.6 (0x00007fb2111c5000) > libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fb2111a0000) c-index-test-16.0.6 thus will segfault when ran > #0 0x00007fccc253d319 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) (/lib64/libLLVM.so.17+0x3b3d319) > #1 0x00007fccc253aed2 llvm::sys::RunSignalHandlers() (/lib64/libLLVM.so.17+0x3b3aed2) > #2 0x00007fccc253db9b (/lib64/libLLVM.so.17+0x3b3db9b) > #3 0x00007fccca23f190 __restore_rt (/lib64/libc.so.6+0x3f190) > #4 0x00007fccc724587a (/lib64/libclang-cpp.so.17+0x124587a) > #5 0x00007fccca2414e1 __cxa_finalize (/lib64/libc.so.6+0x414e1) > #6 0x00007fccc719c0f7 (/lib64/libclang-cpp.so.17+0x119c0f7) > Segmentation fault (core dumped) -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1230189] New: All the packages installed on the system are not available from the Leap Micro 6.0 repositories
by bugzilla_noreply＠suse.com 19 Nov '24

19 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1230189 Bug ID: 1230189 Summary: All the packages installed on the system are not available from the Leap Micro 6.0 repositories Classification: openSUSE Product: openSUSE Leap Micro Version: 6.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: lubos.kocman(a)suse.com Reporter: xavier.coulon(a)suse.com QA Contact: jalausuch(a)suse.com Target Milestone: --- Found By: --- Blocker: --- All the packages installed on the system are not available from the Leap Micro 6.0 repositories. On a fresh install of Leap Micro 6.0: The main repo is available and enabled: # zypper lr Repository priorities are without effect. All enabled repositories share the same priority. # | Alias | Name | Enabled | GPG Check | Refresh --+----------------------+-------------------+---------+-----------+-------- 1 | openSUSE:repo-debug | repo-debug (6.0) | No | ---- | ---- 2 | openSUSE:repo-main | repo-main (6.0) | Yes | (r ) Yes | Yes 3 | openSUSE:repo-source | repo-source (6.0) | No | ---- | ---- If I search a package like NetworkManager: # zypper search -s NetworkManager Refreshing service 'openSUSE'. Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+----------------------------------+---------+-------------+--------+------------------ i | cockpit-networkmanager | package | 309-5.3 | noarch | (System Packages) i+ | NetworkManager | package | 1.42.6-5.14 | x86_64 | (System Packages) i+ | NetworkManager-branding-openSUSE | package | 42.1-1.1 | noarch | (System Packages) i+ | NetworkManager-tui | package | 1.42.6-5.14 | x86_64 | (System Packages) Repository is (System Packages). The package can't be found in the repositories. but for another package like kernel-default: # zypper search -s kernel-default Refreshing service 'openSUSE'. Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+----------------------+---------+-----------------+--------+---------------- v | kernel-default | package | 6.4.0-18.1 | x86_64 | repo-main (6.0) i+ | kernel-default | package | 6.4.0-17.1 | x86_64 | repo-main (6.0) | kernel-default-base | package | 6.4.0-17.1.1.51 | x86_64 | repo-main (6.0) | kernel-default-extra | package | 6.4.0-18.1 | x86_64 | repo-main (6.0) | kernel-default-extra | package | 6.4.0-17.1 | x86_64 | repo-main (6.0) Repository is repo-main (6.0). The package is available in repositories. I checked in the repositories and all the packages are available. But all the packages are not listed in repositories metadata. The impact for me is that I can't build Leap Micro image with Kiwi because a part of packages are not available from the repositories. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1230851] New: [Build 20240918] System Keyboard Layout setting doesn't work for tty
by bugzilla_noreply＠suse.com 19 Nov '24

19 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1230851 Bug ID: 1230851 Summary: [Build 20240918] System Keyboard Layout setting doesn't work for tty Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4493319/modules/keyb oard_layout_gdm/steps/24 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: grace.wang(a)suse.com QA Contact: qa-bugs(a)suse.de CC: yfjiang(a)suse.com Target Milestone: --- Found By: openQA Blocker: --- ## Observation System Keyboard Layout setting doesn't work for tty Simple ways to reproduce this issue: Login to desktop -> Launch YaST2 Keyboard -> Change the keyboard layout to German -> Apply the changes -> Switch to another tty -> Input string "qwertz" and observe the characters displayed on the tty Actual Result: It shows "qwertz". Expected Result: It should show "qwerty" because we are using the German keyboard layout. openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_gnome@64bit fails in [keyboard_layout_gdm](https://openqa.opensuse.org/tests/4493319/modules/keyb… ## Test suite description Maintainer: QE Core, asmorodskyi. Extra tests which were designed to run on gnome ## Reproducible Fails since (at least) Build [20240528](https://openqa.opensuse.org/tests/4231828) ## Expected result Last good: [20240527](https://openqa.opensuse.org/tests/4227928) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1229339] New: Leap 15.5 sle-update repo key expires soon
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1229339 Bug ID: 1229339 Summary: Leap 15.5 sle-update repo key expires soon Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Repository: Update repository with updates from SUSE Linux Enterprise 15 Key Fingerprint: FEAB 5025 39D8 46DB 2C09 61CA 70AF 9E81 39DB 7C82 Key Name: SuSE Package Signing Key <build(a)suse.de> Key Algorithm: RSA 2048 Key Created: Mon Sep 21 10:21:47 2020 Key Expires: Fri Sep 20 10:21:47 2024 (expires in 31 days) Rpm Name: gpg-pubkey-39db7c82-5f68629b Leap 15.5 will receive until December, so this needs to be dealt with. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1219879] New: [TRACKERBUG] Remove EOL OpenSSL 1.1.1 and OpenSSL 1.0.0
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1219879 Bug ID: 1219879 Summary: [TRACKERBUG] Remove EOL OpenSSL 1.1.1 and OpenSSL 1.0.0 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: otto.hollmann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This bug collects the challenges and packages that need to be adapted before removing OpenSSL 1.1.1 and OpenSSL 1.0.0 OpenSSL 1.1.1 (package openssl1_1) is EOL since 11th September 2023. OpenSSL 1.0.0 (package openssl1_0_0) is EOL since 31th December 2019. Therefore, it makes sense to get rid of them and we are going to remove them from Factory in the near future. Unfortunately some packages still rely/depend on these old OpenSSL versions. If we would like to keep these packages, they must be adapted to use OpenSSL 3. Currently these packages are usually hardcoded to use specific openssl package, e.g.: > BuildRequires: libopenssl-1_1-devel The preferred way is to use our meta package > BuildRequires: libopenssl or > BuildRequires: libopenssl-devel that will always pull respective packages with the default OpenSSL version (at the moment libopenssl3 or libopenssl-3-devel). Migration guide can be found here: https://www.openssl.org/docs/man3.0/man7/migration_guide.html List of packages that are using old OpenSSL: dd_rescue EternalTerminal fdo-client libredfish libzrtpcpp python -- You are receiving this mail because: You are on the CC list for the bug.

1 22

[Bug 1230082] New: VUL-0: CVE-2024-45305: jujutsu: gix-path: gix-path uses local config across repos when it is the highest scope
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1230082 Bug ID: 1230082 Summary: VUL-0: CVE-2024-45305: jujutsu: gix-path: gix-path uses local config across repos when it is the highest scope Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other URL: https://smash.suse.de/issue/419537/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: opensuse_buildservice(a)ojkastl.de Reporter: thomas.leroy(a)suse.com QA Contact: security-team(a)suse.de Blocks: 1230079 Target Milestone: --- Found By: Security Response Team Blocker: --- +++ This bug was initially created as a clone of Bug #1230079 +++ gix-path is a crate of the gitoxide project dealing with git paths and their conversions. `gix-path` executes `git` to find the path of a configuration file that belongs to the `git` installation itself, but mistakenly treats the local repository's configuration as system-wide if no higher scoped configuration is found. In rare cases, this causes a less trusted repository to be treated as more trusted, or leaks sensitive information from one repository to another, such as sending credentials to another repository's remote. In `gix_path::env`, the underlying implementation of the `installation_config` and `installation_config_prefix` functions calls `git config -l --show-origin` and parses the first line of the output to extract the path to the configuration file holding the configuration variable of highest scope. It is believed to be very difficult to exploit this vulnerability deliberately, due to the need either to anticipate a situation in which higher-scoped configuration variables would be absent, or to arrange for this to happen. Although any operating system may be affected, users running Apple Git on macOS are much less likely to be affected. This issue has been addressed in release version 0.10.10. All users are advised to upgrade. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-45305 https://www.cve.org/CVERecord?id=CVE-2024-45305 https://git-scm.com/docs/git-config#SCOPES https://github.com/Byron/gitoxide/blob/12251eb052df30105538fa831e641eea557f… https://github.com/Byron/gitoxide/blob/12251eb052df30105538fa831e641eea557f… https://github.com/Byron/gitoxide/security/advisories/GHSA-v26r-4c9c-h3j6 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1228610] New: Mail Makefile error finding alias directory
by bugzilla_noreply＠suse.com 18 Nov '24

18 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1228610 Bug ID: 1228610 Summary: Mail Makefile error finding alias directory Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: marc(a)marcchamberlin.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The macro shell script for ALIAS_FILE is searching for a file. Instead it should be searching for a directory. Change the ALIAS_FILE environment variable in /etc/mail/Makefile from ALIAS_FILE = $(shell find $(ETC)aliases.d/ -type f) to ALIAS_FILE = $(shell find $(ETC)aliases.d/ -type d) Recommend changing the name of this environment variable to ALIAS_DIR to avoid confusion. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1221183] New: Upgrade problems with clang-cpp
by bugzilla_noreply＠suse.com 17 Nov '24

17 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1221183 Bug ID: 1221183 Summary: Upgrade problems with clang-cpp Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: franz.sirl-obs(a)lauterbach.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Hi, during a "zypper --releasever=15.6 dup" upgrade from a fully up-to-date 15.5 installation I got the following messages: Checking for file conflicts: ...................................................................................................................................................................[error] Detected 4 file conflicts: File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from install of clang13-13.0.1-bp156.7.42.x86_64 (Main Repository) File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from package clang11-11.0.1-150300.3.6.1.x86_64 (@System) File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from package clang15-15.0.7-150500.4.4.1.x86_64 (@System) File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from package clang7-7.0.1-150100.3.22.2.x86_64 (@System) File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content. Continue? [yes/no] (no): yes Even though this is mostly harmless, it disturbs the upgrade experience and probably can be easily fixed by backporting the clang-cpp/update-alternatives change from clang17 to the other clang versions that are part of Leap. regards, Franz -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1228824] New: libbotan 2 > 3 switch breaks dependencies?
by bugzilla_noreply＠suse.com 17 Nov '24

17 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1228824 Bug ID: 1228824 Summary: libbotan 2 > 3 switch breaks dependencies? Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: t.rother(a)netzwissen.de QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- After the latest tumbleweed update I had problems with starting keepassxc LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20240801 Codename: n/a - current keepassxc 2.7.9 requires libbotan-2-19.x and crashes without it on startup. - only botan 3.x is available in the tumbleweed repos - this affects both the classic rpm and the flathub package Current workaround: install libbotan 2.x manually from leap 15 and have both packages in parallel: S | Name | Summary | Type ---+----------------+-----------------------------+-------- i+ | libbotan-2-19 | A C++ Crypto Library | package i+ | libbotan-3-5 | A C++ Crypto Library | package With this setup at least the flathub package works normal: KeePassXC org.keepassxc.KeePassXC 2.7.9 stable system Note: severity "major" as the password manager is a critical application for most users -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1229061] New: Laptop that will only run Plasma/Wayland, not Plasma X11
by bugzilla_noreply＠suse.com 16 Nov '24

16 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1229061 Bug ID: 1229061 Summary: Laptop that will only run Plasma/Wayland, not Plasma X11 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: 64bit OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: marc(a)marcchamberlin.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876623 --> https://bugzilla.suse.com/attachment.cgi?id=876623&action=edit xsession-errors file When I try to use the Plasma/X11 desktop, after a reboot I reach the KDE login screen OK. If I choose to log in with the Plasma/X11 desktop, after entering my login name and password, the screen just goes blank for a moment, then cycles back and re-brings up the login/password screen again. Apparently the Plasma/X11 version of the desktop is not accepting my login credentials for some reason. However, if I choose to brings up the Plasma/Wayland desktop, my login credentials work just fine and the desktop comes up OK. I have attached a copy of my .xsession-errors file hoping that might offer a clue. (Guess I can only add one attachment at a time) will add results of doing a hw-probe -all in a follow on post. -- You are receiving this mail because: You are on the CC list for the bug.

1 12