July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1201088] New: GCC 13: ceph package fails
by bugzilla_noreply＠suse.com 10 Mar '23

10 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1201088 Bug ID: 1201088 Summary: GCC 13: ceph package fails 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: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package fails due to: [ 183s] /home/abuild/rpmbuild/BUILD/ceph-16.2.9-158-gd93952c7eea/src/rocksdb/db/compaction/compaction_iteration_stats.h:23:3: error: 'uint64_t' does not name a type [ 183s] 23 | uint64_t total_filter_time = 0; [ 183s] | ^~~~~~~~ [ 183s] /home/abuild/rpmbuild/BUILD/ceph-16.2.9-158-gd93952c7eea/src/rocksdb/db/compaction/compaction_iteration_stats.h:9:1: note: 'uint64_t' is defined in header '<cstdint>'; did you forget to '#include <cstdint>'? [ 183s] 8 | #include "rocksdb/rocksdb_namespace.h" [ 183s] +++ |+#include <cstdint> as documented here: https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes please report it to upstream. One can build with gcc13 with: osc build --alternative-project devel:gcc:next -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1027519] New: Xen: Missing upstream bug fixes
by bugzilla_noreply＠novell.com 09 Mar '23

09 Mar '23

http://bugzilla.suse.com/show_bug.cgi?id=1027519 Bug ID: 1027519 Summary: Xen: Missing upstream bug fixes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xen Assignee: xen-bugs(a)suse.de Reporter: carnold(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There are upstream patches fixing bugs needed for this version of Xen. -- You are receiving this mail because: You are on the CC list for the bug.

2 293

[Bug 1192409] New: /usr/lib/systemd/system/lircd.service may not have ProtectClock=true
by bugzilla_noreply＠suse.com 08 Mar '23

08 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1192409 Bug ID: 1192409 Summary: /usr/lib/systemd/system/lircd.service may not have ProtectClock=true 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: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With one of the last Tumbleweed snapshots some (all?) systemd service files got new options according to https://en.opensuse.org/openSUSE:Security_Features#Systemd_hardening_effort. But /usr/lib/systemd/system/lircd.service may not have set ProtectClock=true, because otherwise the daemon is not able to open the remote device: lircd-0.10.1[852]: Info: initializing '/dev/input/imon_remote' lircd-0.10.1[852]: Info: Using device: /dev/input/imon_remote lircd-0.10.1[852]: Error: unable to open '/dev/input/imon_remote' lircd-0.10.1[852]: Warning: Failed to initialize hardware lircd[852]: lircd-0.10.1[852]: Error: unable to open '/dev/input/imon_remote' lircd-0.10.1[852]: Error: unable to open '/dev/input/imon_remote' Without ProtectClock=true lircd works as expected. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1200684] New: Cannot find 'org.kde.KSplash.setStage' in object /KSplash at org.kde.KSplash
by bugzilla_noreply＠suse.com 08 Mar '23

08 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1200684 Bug ID: 1200684 Summary: Cannot find 'org.kde.KSplash.setStage' in object /KSplash at org.kde.KSplash Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting with the latest Tumbleweed snapshot 20220617 I get the following messages in my journal: Cannot find 'org.kde.KSplash.setStage' in object /KSplash at org.kde.KSplash Activated service 'org.kde.KSplash' failed: Process org.kde.KSplash exited with status 1 I am not sure, if this has any impact on my system, but if not, what sense do they make? -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1048337] New: yast2-slide-show need to adjust the install path for new product builder
by bugzilla_noreply＠novell.com 08 Mar '23

08 Mar '23

http://bugzilla.suse.com/show_bug.cgi?id=1048337 Bug ID: 1048337 Summary: yast2-slide-show need to adjust the install path for new product builder Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: mlin(a)suse.com QA Contact: jsrain(a)suse.com CC: adrian(a)suse.com Found By: --- Blocker: --- I've tested this in the staging project, I hot-patched yast2-slide-show then all files are located at /usr/lib/skelcd/CD1 for new product builder, since DATADIR is obsoleted already then new product builder doesn't have process those files. you can find testdvd build log at https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… so the main question: is product builder still support slideshow? if so where is the right path it should be? -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 980292] New: Yast shouldn't allow running two instances of module at once
by bugzilla_noreply＠novell.com 08 Mar '23

08 Mar '23

http://bugzilla.suse.com/show_bug.cgi?id=980292 Bug ID: 980292 Summary: Yast shouldn't allow running two instances of module at once Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: hguo(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- It's very easy to mistakenly double click on a module icon in Yast2, causing two instances of the module to be started, and there's absolutely no point in using more than one instance of any yast module. Please disallow double click on yast2, and prevent more than one instance of module to be started. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[opensuse-bugs] [Bug 1179248] New: Bluetooth speaker: KDE widget and bluetoothcl it paired and connected, but PulseAudio does not see it at all
by bugzilla_noreply＠suse.com 08 Mar '23

08 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1179248 Bug ID: 1179248 Summary: Bluetooth speaker: KDE widget and bluetoothcl it paired and connected, but PulseAudio does not see it at all Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ncutler(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In Leap 15.1 with KDE and PulseAudio, I had no problem playing sound through speakers connected via bluetooth. It "just worked". After upgrading to Leap 15.2, it does not work. I go through the normal drill of pairing with and connecting to the device. I can see the device in both KDE's bluetooth widget and in bluetoothctl. It is connected. In Leap 15.1, after connection the device would appear in pavucontrol and I could direct an audio stream to it, and it would play. Now the device does not appear in pavucontrol. After a lot of googling I did figure out how to get log messages out of pulseaudio, but the procedure for doing so is bizarre and might actually deserve a separate bug report. Pulseaudio is run by systemd, but AFAICT the log messages just go to /dev/null (journalctl shows nothing). In order to see the log messages, I have to prevent systemd from starting pulseaudio, and then start it myself in an interactive session, while capturing its output to a file. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1190681] New: Zig fails to build because of "Could NOT find lld (missing: LLD_LIBRARIES LLD_INCLUDE_DIRS) "
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1190681 Bug ID: 1190681 Summary: Zig fails to build because of "Could NOT find lld (missing: LLD_LIBRARIES LLD_INCLUDE_DIRS) " 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: socvirnyl.estela(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Greetings! I have a few problems building zig in openSUSE Tumbleweed. **What I want to do** I want to successfully build zig in openSUSE Tumbleweed with llvm, clang, and lld provided by the distro's repositories. **Expected Outcome** Builds successfully **Actual Outcome** Failed to build **What I did** In `~/local/zig-0.8.1`, I use the following commands based on how others build zig: ```sh cmake -G Ninja -B build \ -DCMAKE_BUILD_TYPE=None \ -DCMAKE_INSTALL_PREFIX=$(llvm-config --prefix) \ -DZIG_PREFER_CLANG_CPP_DYLIB=ON . ``` ```sh ninja -C build ninja: Entering directory `build' [19/164] Building CXX object CMakeFiles/zigcpp.dir/src/zig_llvm.cpp.o FAILED: CMakeFiles/zigcpp.dir/src/zig_llvm.cpp.o /usr/bin/c++ -I/home/uncomfy/local/zig-0.8.1/deps/SoftFloat-3e/source/include -I/home/uncomfy/local/zig-0.8.1 -I/home/uncomfy/local/zig-0.8.1/build -I/home/uncomfy/local/zig-0.8.1/src -I/home/uncomfy/local/zig-0.8.1/src/stage1 -std=c++14 -DZIG_LINK_MODE=Dynamic -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -D_GNU_SOURCE -fvisibility-inlines-hidden -fno-exceptions -fno-rtti -Werror=type-limits -Wno-missing-braces -Wno-comment -MD -MT CMakeFiles/zigcpp.dir/src/zig_llvm.cpp.o -MF CMakeFiles/zigcpp.dir/src/zig_llvm.cpp.o.d -o CMakeFiles/zigcpp.dir/src/zig_llvm.cpp.o -c /home/uncomfy/local/zig-0.8.1/src/zig_llvm.cpp /home/uncomfy/local/zig-0.8.1/src/zig_llvm.cpp:67:10: fatal error: lld/Common/Driver.h: No such file or directory 67 | #include <lld/Common/Driver.h> | ^~~~~~~~~~~~~~~~~~~~~ compilation terminated. [28/164] Building CXX object CMakeFiles/zigcpp.dir/src/zig_clang_cc1_main.cpp.o ninja: build stopped: subcommand failed. ``` **What I found out** Someone in Discord assisted me and gave me the link of the build logs. We found out that the reason it fails might be because of this line: ``` # These are only available as static libraries, which we don't ship. rm -rf %{buildroot}%{_includedir}/{clang-tidy,lld} ``` It means `/usr/include/lld` does not exist in llvm-devel. Thus, zig won't be able to build. **Why do I want to include those static libraries** Because some distributions already ship zig in their respective repositories, I want to also build zig succesfully and propose that it should be added in openSUSE's repos in the future. **What could be changed to remove the problem** Including the static libraries in the llvm-devel packages and the respective headers so that applications can build against these. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1114673] New: New UI for firewalld: interface not assigned to the right zone when changed to public in first run
by bugzilla_noreply＠novell.com 07 Mar '23

07 Mar '23

http://bugzilla.suse.com/show_bug.cgi?id=1114673 Bug ID: 1114673 Summary: New UI for firewalld: interface not assigned to the right zone when changed to public in first run Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jeriveramoya(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Interface is not assigned to the right zone after following steps: - Open new UI for firewalld: yast2 firewall - Assign interface to different zone (for example public) - In Zones, set different zone (for example trusted) as default. - Accept - Check with firewall-cmd interface assignation: firewall-cmd --list-interfaces --zone=public | grep ens4 (is not there) but firewall-cmd --list-interfaces --zone=trusted | grep ens4 (it succeeds and it is pointing to the default zone not the one that was assigned) (same result also after trying a firewall-cmd --reload) Assignation works in general, but in this combination and just when the user enters first to this screen and set previous steps, does not work (perhaps some wrong initialization). Expected result: Point to the interface that is assigned in the UI (in the example, to public) -- You are receiving this mail because: You are on the CC list for the bug.

2 33

[Bug 1127481] New: Upgrade to 15.1 tries to install grub-efi even though my bootloader is Legacy BIOS and fails to install packages
by bugzilla_noreply＠novell.com 07 Mar '23

07 Mar '23

http://bugzilla.suse.com/show_bug.cgi?id=1127481 Bug ID: 1127481 Summary: Upgrade to 15.1 tries to install grub-efi even though my bootloader is Legacy BIOS and fails to install packages Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: ktsamis(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 798527 --> http://bugzilla.suse.com/attachment.cgi?id=798527&action=edit logs Using the DVD I chose Upgrade and I saw the error in the Overview section at the end that it can't detect the efi partition so it might make my system unbootable and I should open a bug. The problem is after the upgrade was finished I didn't have a y2log but only y2log-1 and y2log-2. And I couldn't find the error in those. After reboot I do a zypper up and there are like 800 packages to be updated, all of them cached already. So that means it cached all the packages instead of installing and I had to do it again. After installing all of them I see the similar error here: Executing %posttrans script 'kernel-firmware-20190118-lp151.1.3.noarch.rpm' <3%>================================================================================================================================[\] Output of kernel-firmware-20190118-lp151.1.3.noarch.rpm %posttrans script: Creating initrd: /boot/initrd-4.12.14-lp150.12.48-default dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-4.12.14-lp150.12.48-default 4.12.14-lp150.12.48-default dracut: *** Including module: bash *** dracut: *** Including module: systemd *** dracut: *** Including module: warpclock *** dracut: *** Including module: systemd-initrd *** dracut: *** Including module: i18n *** dracut: *** Including module: drm *** dracut: *** Including module: plymouth *** dracut: *** Including module: crypt *** dracut: *** Including module: dm *** dracut: Skipping udev rule: 64-device-mapper.rules dracut: Skipping udev rule: 60-persistent-storage-dm.rules dracut: Skipping udev rule: 55-dm.rules dracut: *** Including module: kernel-modules *** dracut: *** Including module: lvm *** dracut: Skipping udev rule: 64-device-mapper.rules dracut: Skipping udev rule: 56-lvm.rules dracut: Skipping udev rule: 60-persistent-storage-lvm.rules dracut: *** Including module: resume *** dracut: *** Including module: rootfs-block *** dracut: *** Including module: suse-btrfs *** dracut-install: ERROR: installing '/usr/share/doc/btrfsprogs/dracut-fsck-help.txt' to '/usr/share/fsck/fsck_help_btrfs.txt' dracut: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.GR4CZA/initramfs /usr/share/doc/btrfsprogs/dracut-fsck-help.txt /usr/share/fsck/fsck_help_btrfs.txt dracut: *** Including module: suse-xfs *** dracut: *** Including module: terminfo *** dracut: *** Including module: udev-rules *** dracut: Skipping udev rule: 40-redhat.rules dracut: Skipping udev rule: 50-firmware.rules dracut: Skipping udev rule: 50-udev.rules dracut: Skipping udev rule: 91-permissions.rules dracut: Skipping udev rule: 80-drivers-modprobe.rules dracut: *** Including module: dracut-systemd *** dracut: *** Including module: haveged *** dracut: *** Including module: usrmount *** dracut: *** Including module: base *** dracut: *** Including module: fs-lib *** dracut: *** Including module: shutdown *** dracut: *** Including module: suse *** dracut: *** Including modules done *** dracut: *** Installing kernel module dependencies and firmware *** dracut: *** Installing kernel module dependencies and firmware done *** dracut: *** Resolving executable dependencies *** dracut: *** Resolving executable dependencies done*** dracut: *** Hardlinking files *** dracut: *** Hardlinking files done *** dracut: *** Stripping files *** dracut: *** Stripping files done *** dracut: *** Generating early-microcode cpio image *** dracut: *** Constructing GenuineIntel.bin **** dracut: *** Store current command line parameters *** dracut: Stored kernel commandline: dracut: rd.luks.uuid=luks-3ca9e321-7a76-4dc6-9a46-8c11ac70b25e dracut: rd.lvm.lv=LVM_group/root dracut: resume=UUID=874f7a4f-4f84-4c92-a971-280b933bfea6 dracut: root=/dev/mapper/LVM_group-root rootfstype=xfs rootflags=rw,relatime,attr2,inode64,noquota dracut: *** Creating image file '/boot/initrd-4.12.14-lp151.21-default' *** dracut: *** Creating initramfs image file '/boot/initrd-4.12.14-lp151.21-default' done *** Executing %posttrans script 'grub2-i386-pc-2.02-lp151.19.2.noarch.rpm' .........................................................................<57%>===========================================================[|] Output of grub2-i386-pc-2.02-lp151.19.2.noarch.rpm %posttrans script: update-bootloader: 2019-02-27 13:20:09 <3> update-bootloader-2225 run_command.294: '/usr/lib/bootloader/grub2-efi/install' failed with exit code 1, output: <<<<<<<<<<<<<<<< target = x86_64-efi ls: cannot access '/sys/firmware/efi/efivars': No such file or directory + /usr/sbin/shim-install --config-file=/boot/grub2/grub.cfg --no-nvram --removable No valid EFI partition >>>>>>>>>>>>>>>> Executing %posttrans scripts ................................................................................................................................................................................[done] There are some running programs that might use files deleted by recent upgrade. You may wish to check and restart some of them. Run 'zypper ps -s' to list these programs. Core libraries or services have been updated. Reboot is required to ensure that your system benefits from these updates. The logs are a bit of a mess for some reason after the installation, I also unpacked some tarballs trying to find the error but no luck. Maybe someone else can have better luck. -- You are receiving this mail because: You are on the CC list for the bug.

2 14