October 2019 - openSUSE Bugs - openSUSE Mailing Lists

[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 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

[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 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 1116889] New: windows:mingw:win32/mingw32-cross-gcc: Bug / Installation size is huge (unstripped exes?)
by bugzilla_noreply＠novell.com 02 Mar '23

02 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1116889 Bug ID: 1116889 Summary: windows:mingw:win32/mingw32-cross-gcc: Bug / Installation size is huge (unstripped exes?) Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: sergei.ivn+bugzilla(a)gmail.com QA Contact: bnc-team-screening(a)forge.provo.novell.com CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, idonmez(a)suse.com, mkbosmans(a)gmail.com, tlillqvist(a)suse.com Found By: --- Blocker: --- (second attempt) Hi. I'm using opensuse tumbleweed on a remote CI server for building some of my windows project. And since the container size is huge I did some investigations and it turns out that execs size for mingw32-cross-{gcc,cpp,gcc-c++} is very big, for instance the size of the cc1 executable is over 200 megabytes. I'm myself is on windows so my possibilities are limited, but the msys2 file utility said that the exec files contain some debug info. (bugzilla prefilled cc:alan@xamarin.com breaks the report attempt) -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1135212] New: LTO: libqt5-qtwebkit build fails
by bugzilla_noreply＠novell.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1135212 Bug ID: 1135212 Summary: LTO: libqt5-qtwebkit build fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… with: [ 2250s] /home/abuild/rpmbuild/BUILD/qtwebkit-5.212.0-alpha2/Source/JavaScriptCore/interpreter/CallFrame.cpp:200: undefined reference to `vmEntryRecord' [ 2250s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: /home/abuild/rpmbuild/BUILD/qtwebkit-5.212.0-alpha2/Source/JavaScriptCore/interpreter/CallFrame.cpp:200: undefined reference to `vmEntryRecord' [ 2250s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: /tmp/testair.Ki1BSG.ltrans38.ltrans.o: in function `JSC::construct(JSC::ExecState*, JSC::JSValue, JSC::ConstructType, JSC::ConstructData const&, JSC::ArgList const&, JSC::JSValue)': [ 2250s] /home/abuild/rpmbuild/BUILD/qtwebkit-5.212.0-alpha2/Source/JavaScriptCore/interpreter/Interpreter.cpp:1106: undefined reference to `vmEntryToNative' [ 2250s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: /tmp/testair.Ki1BSG.ltrans38.ltrans.o: in function `JSC::call(JSC::ExecState*, JSC::JSValue, JSC::CallType, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&)': [ 2250s] /home/abuild/rpmbuild/BUILD/qtwebkit-5.212.0-alpha2/Source/JavaScriptCore/interpreter/Interpreter.cpp:1036: undefined reference to `vmEntryToNative' [ 2250s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: /tmp/testair.Ki1BSG.ltrans54.ltrans.o: in function `JSC::Debugger::stepOutOfFunction()': [ 2250s] /home/abuild/rpmbuild/BUILD/qtwebkit-5.212.0-alpha2/Source/JavaScriptCore/interpreter/CallFrame.cpp:200: undefined reference to `vmEntryRecord' [ 2250s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: /tmp/testair.Ki1BSG.ltrans54.ltrans.o: in function `JSC::Debugger::didExecuteProgram(JSC::ExecState*)': [ 2250s] /home/abuild/rpmbuild/BUILD/qtwebkit-5.212.0-alpha2/Source/JavaScriptCore/interpreter/CallFrame.cpp:200: undefined reference to `vmEntryRecord' ... -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1133242] New: LTO: libqt5-qtbase build fails
by bugzilla_noreply＠novell.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1133242 Bug ID: 1133242 Summary: LTO: libqt5-qtbase build fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fails due to: [ 958s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: /tmp/libQt5Network.so.5.12.2.I6MFgc.ltrans0.ltrans.o:(.qtversion[qt_version_tag]+0x0): undefined reference to `qt_version_tag' [ 958s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: /tmp/libQt5Network.so.5.12.2.I6MFgc.ltrans0.ltrans.o:(.qtversion[qt_version_tag]+0x10): undefined reference to `qt_version_tag' [ 958s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: /tmp/libQt5Network.so.5.12.2.I6MFgc.ltrans0.ltrans.o:(.qtversion[qt_version_tag]+0x20): undefined reference to `qt_version_tag' [ 958s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: /tmp/libQt5Network.so.5.12.2.I6MFgc.ltrans0.ltrans.o:(.qtversion[qt_version_tag]+0x30): undefined reference to `qt_version_tag' [ 958s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: /tmp/libQt5Network.so.5.12.2.I6MFgc.ltrans0.ltrans.o:(.qtversion[qt_version_tag]+0x40): undefined reference to `qt_version_tag' [ 958s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: /tmp/libQt5Network.so.5.12.2.I6MFgc.ltrans0.ltrans.o:(.qtversion[qt_version_tag]+0x50): more undefined references to `qt_version_tag' follow -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1133241] New: LTO: libqt5-qtscript build fails
by bugzilla_noreply＠novell.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1133241 Bug ID: 1133241 Summary: LTO: libqt5-qtscript build fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fails with LTO due to a usage of top level assembler. -- You are receiving this mail because: You are on the CC list for the bug.

2 2