June 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1222595] New: find-debuginfo.sh crash when build with kanidm
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222595 Bug ID: 1222595 Summary: find-debuginfo.sh crash when build with kanidm Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- find-debuginfo.sh crash when building with kanidm, the full build log openSUSE:Backports:SLE-15-SP6 staging[1] [ 1201s] + /usr/lib/rpm/find-debuginfo.sh -j4 --build-id-seed 1.1.0~rc16~git4.d407844-bp156.2.1 --unique-debug-suffix -1.1.0~rc16~git4.d407844-bp156.2.1.x86_64 --unique-debug-src-base kanidm-1.1.0~rc16~git4.d407844-bp156.2.1.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 50000000 -S debugsourcefiles.list /home/abuild/rpmbuild/BUILD/kanidm-1.1.0~rc16~git4.d407844 [ 1201s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/kanidm-1.1.0~rc16~git4.d407844-bp156.2.1.x86_64/usr/bin/kanidm [ 1201s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/kanidm-1.1.0~rc16~git4.d407844-bp156.2.1.x86_64/lib64/security/pam_kanidm.so [ 1201s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/kanidm-1.1.0~rc16~git4.d407844-bp156.2.1.x86_64/usr/lib64/libnss_kanidm.so.2 [ 1201s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/kanidm-1.1.0~rc16~git4.d407844-bp156.2.1.x86_64/usr/sbin/kanidm-ipa-sync [ 1201s] Cannot handle 8-byte build ID [ 1201s] Cannot handle 8-byte build ID [ 1203s] Cannot handle 8-byte build ID [ 1203s] Cannot handle 8-byte build ID [ 1203s] /usr/lib/rpm/find-debuginfo.sh: line 521: /tmp/find-debuginfo.avVGqk/res.*: No such file or directory [1] https://build.opensuse.org/package/live_build_log/openSUSE:Backports:SLE-15… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215622] New: iscsiuio - Couldn't mmap registers: Invalid argument
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1215622 Bug ID: 1215622 Summary: iscsiuio - Couldn't mmap registers: Invalid argument Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: per(a)computer.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When trying to set up an iscsi initiator (in yast) using a bnx2 offload engine, I wasn't getting very far, see bug#1215621. I kept getting this error: iscsiadm: Could not set host net params (err 29) I ran iscsiuio with debug level 4 and noticed the following error msg: Couldn't mmap registers: Invalid argument After some research, I rebooted the machine with "iomem=relaxed" - now it works: anton:~ # iscsiadm -m discovery -P 1 -t st -I eth4-bnx2i -p 10.42.8.10:3260 iscsiadm: Could not set host net params (err 29) iscsiadm: Connection to discovery portal 10.42.8.10 failed: operation failed but retry may succeed Target: iqn.2023-09.local.rz2:opensuse-mirror Portal: 10.42.8.10:3260,1 Iface Name: eth4-bnx2i Target: iqn.2023-09.local.rz2:webspace Portal: 10.42.8.10:3260,1 Iface Name: eth4-bnx2i -- You are receiving this mail because: You are on the CC list for the bug.

1 5

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

16 Jun '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 7

[Bug 1222269] New: LLVM run OOM while building typst for armv6/7 with 24G of RAM
by bugzilla_noreply＠suse.com 16 Jun '24

16 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222269 Bug ID: 1222269 Summary: LLVM run OOM while building typst for armv6/7 with 24G of RAM Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- LLVM run OOM while building typst for armv6/7 with 24G of RAM while aarch64 requires 11.8G of RAM ********** [ 173s] Compiling typst-ide v0.11.0 (/home/abuild/rpmbuild/BUILD/typst-0.11.0/crates/typst-ide) [ 429s] Compiling typst-fuzz v0.11.0 (/home/abuild/rpmbuild/BUILD/typst-0.11.0/tests/fuzz) [ 658s] LLVM ERROR: out of memory [ 658s] Allocation failed [ 658s] thread 'main' panicked at cargo-auditable/src/rustc_wrapper.rs:101:39: [ 658s] called `Option::unwrap()` on a `None` value [ 658s] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [ 658s] error: could not compile `typst-docs` (bin "typst-docs") [ 658s] warning: build failed, waiting for other jobs to finish... [ 663s] LLVM ERROR: out of memory [ 663s] Allocation failed [ 664s] thread 'main' panicked at cargo-auditable/src/rustc_wrapper.rs:101:39: [ 664s] called `Option::unwrap()` on a `None` value [ 664s] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [ 664s] error: could not compile `typst-fuzz` (bin "compile") [ 694s] LLVM ERROR: out of memory [ 694s] Allocation failed [ 694s] thread 'main' panicked at cargo-auditable/src/rustc_wrapper.rs:101:39: [ 694s] called `Option::unwrap()` on a `None` value [ 694s] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [ 694s] error: could not compile `typst-cli` (bin "typst") [ 694s] error: Bad exit status from /var/tmp/rpm-tmp.R2PFPX (%build) ********** See: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:ARM/typs… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1226269] AppStream metadata allow user uninstallation of PackageKit
by bugzilla_noreply＠suse.com 16 Jun '24

16 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226269 https://bugzilla.suse.com/show_bug.cgi?id=1226269#c1 --- Comment #1 from Daniel Rusek <mail(a)asciiwolf.com> --- FYI it is not GNOME (GNOME Software) related bug and the same behavior will (most likely) happen in KDE Discover and other AppStream-based package management interfaces. It needs to be fixed in the AppStream metadata file of PackageKit. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226408] New: Building opensuse microOS images with kiwi-ng without OBS fails (patterns-microos-base dependencies problems)
by bugzilla_noreply＠suse.com 16 Jun '24

16 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226408 Bug ID: 1226408 Summary: Building opensuse microOS images with kiwi-ng without OBS fails (patterns-microos-base dependencies problems) Classification: openSUSE Product: openSUSE Leap Micro Version: 6.0 Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: lubos.kocman(a)suse.com Reporter: gmachado.tl1(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I found 2 issues when I tried to build opensuse microOS images with kiwi-ng without OBS. I'm adapting this OBS project to my needs : https://build.opensuse.org/package/show/openSUSE:Factory/openSUSE-MicroOS First issue occured because obs resolver and zypper handle busybox preference differently : https://groups.google.com/g/kiwi-images/c/FptmmheOT7g Second issue occured because systemd-presets-branding-MicroOS was not installed during the bootstrap phase and the zypper resolver failed : https://groups.google.com/g/kiwi-images/c/r3L_fwXp3Xc Can you fix these issues please ? And generally test the packages/patterns dependencies also without OBS ? Thanks in advance and thanks again Marcus Schäfer for his help. Regards, Gabriel. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226269] New: AppStream metadata allow user uninstallation of PackageKit
by bugzilla_noreply＠suse.com 16 Jun '24

16 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226269 Bug ID: 1226269 Summary: AppStream metadata allow user uninstallation of PackageKit Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: mail(a)asciiwolf.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Because of a missing tags in the AppStream metainfo file (that was added in PK 1.2.8), PackageKit is shown as user uninstallable in GNOME Software and other GUI/TUI package managers based on AppStream metadata. This is incorrect and potentially dangerous. The issue was already fixed in upstream. Please, consider backporting this fix into OpenSUSE as a downstream patch until a new PackageKit version gets released. Upstream ticket: https://github.com/PackageKit/PackageKit/issues/759 Upstream fix: https://github.com/PackageKit/PackageKit/commit/d8f84f7e0a017e0b4df1e08a2a6… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1226404] 15.6: file conflicts in ruby2.5-rubygem-bcrypt_pbkdf
by bugzilla_noreply＠suse.com 16 Jun '24

16 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226404 https://bugzilla.suse.com/show_bug.cgi?id=1226404#c1 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Assignee|packagehub-bugs(a)suse.com |dcermak(a)suse.com CC| |Andreas.Stieger(a)gmx.de --- Comment #1 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- $ zypper in --dry-run --download-only ruby2.5-rubygem-bcrypt_pbkdf ruby2.5-rubygem-bcrypt_pbkdf-1.1 Loading repository data... Reading installed packages... Resolving package dependencies... The following 2 NEW packages are going to be installed: ruby2.5-rubygem-bcrypt_pbkdf ruby2.5-rubygem-bcrypt_pbkdf-1.1 2 new packages to install. Overall download size: 0 B. Already cached: 128.7 KiB. Download only. Backend: classic_rpmtrans --dry-run --download-only Continue? [y/n/v/...? shows all options] (y): y In cache ruby2.5-rubygem-bcrypt_pbkdf-1.1-1.1.0-bp156.3.3.x86_64.rpm (1/2), 64.3 KiB In cache ruby2.5-rubygem-bcrypt_pbkdf-1.1.0-bp156.3.3.x86_64.rpm (2/2), 64.3 KiB Checking for file conflicts: ....................................................................................[error] Detected 1 file conflict: File /usr/lib64/ruby/gems/2.5.0/extensions/x86_64-linux/2.5.0/bcrypt_pbkdf-1.1.0/bcrypt_pbkdf_ext.so from install of ruby2.5-rubygem-bcrypt_pbkdf-1.1-1.1.0-bp156.3.3.x86_64 (Main Repository) conflicts with file from install of ruby2.5-rubygem-bcrypt_pbkdf-1.1.0-bp156.3.3.x86_64 (Main Repository) 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): openSUSE:Backports:SLE-15-SP5:Update/rubygem-bcrypt_pbkdf openSUSE:Backports:SLE-15-SP6:Update/rubygem-bcrypt_pbkdf [...] openSUSE:Backports:SLE-15-SP5:Update/rubygem-bcrypt_pbkdf-1.1 openSUSE:Backports:SLE-15-SP6:Update/rubygem-bcrypt_pbkdf-1.1 In general our packaging policies ask for an rpm conflict between packages with overlapping files. But there may be a duplication of packages here? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226405] New: Nautilus crash when opening multiple mp3 files
by bugzilla_noreply＠suse.com 16 Jun '24

16 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226405 Bug ID: 1226405 Summary: Nautilus crash when opening multiple mp3 files Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Desktop Environment Assignee: rbrown(a)suse.com Reporter: thiagomagalhaes07(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875506 --> https://bugzilla.suse.com/attachment.cgi?id=875506&action=edit Crash example Nautilus 46.2 crash when one tries to open multiple musics in some apps. The crash happens when one tries to open 29 musics in "Clapper", "Celluloid", "Music" and "Amberol", but works using "Rhythmbox" and "VLC". (all mentioned apps in current flathub versions) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226383] Firefox 127 fails to play H.264 using libavcodec61
by bugzilla_noreply＠suse.com 16 Jun '24

16 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1226383 https://bugzilla.suse.com/show_bug.cgi?id=1226383#c6 Adam Reichold <adam.reichold(a)t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Flags|needinfo? | Status|NEW |RESOLVED --- Comment #6 from Adam Reichold <adam.reichold(a)t-online.de> --- And now I cannot reproduce it either. I think there were updated packages shipped by Packman after I wrote this, so I suspect it was an issue with libavcodec61 rather than Firefox and I just noticed it with Firefox because it is the only application which regularly encounters H.264 on my system. This would also fit with the Mozilla binaries not working either. Sorry for the noise.s would also fit with the Mozilla binaries not working either. Sorry for the noise. -- You are receiving this mail because: You are on the CC list for the bug.

1 0