October 2022 - openSUSE Bugs - openSUSE Mailing Lists

[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

[Bug 1177152] New: Installer fails to reboot
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1177152 Bug ID: 1177152 Summary: Installer fails to reboot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: msuchanek(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- ┌──────────────────────────────────────────────────────────────────────────────┐ │ No device(s) for installation found │ ├──────────────────────────────────────────────────────────────────────────────┤ │ < OK > │ └──────────────────────────────────────────────────────────────────────────────┘ [ OK ] Finished Dracut Run Interactive. [ 31.617660] [ 31.643346] reboot: Restarting system dracut-pre-mount[ 32.648330] Reboot failed -- System halted -- You are receiving this mail because: You are on the CC list for the bug.

1 32

[Bug 1177264] New: ports not net-installable
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1177264 Bug ID: 1177264 Summary: ports not net-installable Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: msuchanek(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- http://download.opensuse.org/ports/armv7hl/tumbleweed/repo/oss/boot/ has nothing in it. According to https://en.opensuse.org/SDB:Network_installation this should have the installer files to install from network. -- You are receiving this mail because: You are on the CC list for the bug.

1 22

[Bug 1044803] New: Default online repositories not used even if installing with network connection by default
by bugzilla_noreply＠novell.com 07 Mar '23

07 Mar '23

http://bugzilla.suse.com/show_bug.cgi?id=1044803 Bug ID: 1044803 Summary: Default online repositories not used even if installing with network connection by default Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: opensuse.lietuviu.kalba(a)gmail.com QA Contact: jsrain(a)suse.com Depends on: 1044741 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1044741 +++ I did installation from openSUSE-Leap-42.3-DVD-x86_64-Build0279-Media.iso image and during installation there was internet connection and computer was ONLINE. But I found that it tried to use only DVD as repository... Though default online repositories (oss, non-oss, oss-updates, non-oss-updates) will be added only if I intentionally pressed to configure online repositories at dialog for computer role. If I remember good, in previous versions these four _default_ repos where enabled by default, and we had option to include _additional_ repositories. See yast2logs and screenshots in bug#1044741 -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1172465] New: transactional-update.timer fires immediately at first boot
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1172465 Bug ID: 1172465 Summary: transactional-update.timer fires immediately at first boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE-MicroOS.armv7l-16.0.0-RaspberryPi2-Snapshot20200528.raw Booted and wondered why systemd-analyze wouldn't show me results. Turns out transactional-update.timer was started immediately at first boot. Maybe related to missing rtc on rpi? So the time warp caused by chrony catching up triggered it? # systemctl status transactional-update.timer * transactional-update.timer - Daily update of the system Loaded: loaded (/usr/lib/systemd/system/transactional-update.timer; enabled; vendor preset: enabled) Active: active (waiting) since Thu 2020-04-23 14:15:38 UTC; 1 months 10 days ago Trigger: Thu 2020-06-04 01:38:53 UTC; 11h left Triggers: * transactional-update.service Docs: man:transactional-update(8) If so why April 23rd rather than end of May when the image was created? # l /var/lib/chrony total 0 drwxr-x--- 1 chrony chrony 0 May 2 22:23 ./ drwxr-xr-x 1 root root 268 Jun 3 13:56 ../ Can and do we want to do something about this behavior or a matter of documentation again? -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1195850] New: installation hooks are not working
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1195850 Bug ID: 1195850 Summary: installation hooks are not working Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: comes(a)naic.edu QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I'm trying to use hooks as described here: https://github.com/yast/yast-yast2/blob/master/library/general/doc/Hooks.md What I did is to create the file "before_copy_logs_finish_00_test_hook.sh" and put it in var/lib/YaST2/hooks/installation in the 'root' image that is used at installation time (to be clear like the one that is available in: download.opensuse.org/tumbleweed/repo/oss/boot/x86_64/root At the the end of the installation process, the script before_copy_logs_finish_00_test_hook.sh is supposed to be executed, but that doesn't happen. The log /var/log/YaST2/y2log-1.gz explains why: [Ruby] modules/Hooks.rb(find_hook_files):193 Found 1 hook files: before_copy_logs_finish_00_comes_hook.sh [Ruby] modules/Hooks.rb(execute):165 Executing hook 'before_copy_logs_finish' [Ruby] modules/Hooks.rb(execute):210 Executing hook file '/var/lib/YaST2/hooks/installation/before_copy_logs_finish_00_comes_hook.sh' [bash] ShellCommand.cc(shellcommand):78 sh: /var/lib/YaST2/hooks/installation/before_copy_logs_finish_00_comes_hook.sh: No such file or directory [Ruby] modules/Hooks.rb(execute):212 Hook file 'before_copy_logs_finish_00_comes_hook.sh' failed with stderr: sh: /var/lib/YaST/hooks/installation/before_copy_logs_finish_00_comes_hook.sh: No such file or directory The installer finds the script, but when it is executed it is not there. I suspected a chroot issue and to confirm my suspicion I did the following: After the installation process started, I moved to tty2 where a shell is available. The command 'ls /var/lib/YaST2/hooks/installation' shows that the hook script is there. then I did: mkdir -p /mnt/var/lib/YaST2/hooks/installation cp /var/lib/YaST2/hooks/installation/* /mnt/var/lib/YaST2/hooks/installation and let the installation process complete. This time the hook script got executed. The solution to the problem seemd to be: 1) do not execute the hook scripts in the chroot environment or 2) make the hook scripts visible in the chroot environment I guess the correct solution is number 2. For the record, the issue exists both in Leap 15.3 and tumbleweed. Using hooks was a possible solution to fix boo#1195118 bur I guess that's not an option right now. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1179849] New: plymouth rpm output: bad invocation of systemd-sysv-convert: too few arguments
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1179849 Bug ID: 1179849 Summary: plymouth rpm output: bad invocation of systemd-sysv-convert: too few arguments 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: mail(a)bernhard-voelker.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just saw this in the RPM output when doing 'zypper dup' today (openSUSE Tumbleweed 20201205-0 -> 20201207-0): (41/51) Installing: plymouth-0.9.5+git20200921+20778f2-4.1.x86_64 .......[done] Additional rpm output: usage: systemd-sysv-convert --apply <service> [<service> ...] Too few arguments. Please check to avoid this kind of worrying messages. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1170344] New: Btrfsprogs 5.6 bug: kernel booting stop at "BTRFS info" output
by bugzilla_noreply＠novell.com 07 Mar '23

07 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1170344 Bug ID: 1170344 Summary: Btrfsprogs 5.6 bug: kernel booting stop at "BTRFS info" output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: hillwoodroc(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I Updated My PC and laptop to Tumbleweed 20200417, then these two systems could not boot, and there is not any error on screen. I tried to chroot to get the dmesg log, I got many BTRFS notices at the end. I find Btrfsprogs was updated before 10 days ago in Factory. I guess this is a bug for Btrfsprogs. -- You are receiving this mail because: You are on the CC list for the bug.

2 18