January 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 989284] New: KIWI images broken due to e2fsprogs update for U-Boot based boot, uses "64bit" feature
by bugzilla_noreply＠novell.com 12 Oct '21

12 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=989284 Bug ID: 989284 Summary: KIWI images broken due to e2fsprogs update for U-Boot based boot, uses "64bit" feature Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: stefan.bruens(a)rwth-aachen.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- e2fsprogs-1.43 adds the "64bit" feature for ext4 filesystems. KIWI uses the default features from /etc/mke2fs.conf U-Boot does not support ext4 with enabled 64bit feature. Thus this affects any system using U-Boot which stores kernel and initrd on the root filesystem. (e.g. rpi3 uses a seperate ext3 /boot partition, Pine64 uses the ext4 / root filesystem) The issue can be worked around by e.g.: "tune2fs -O ^64bit /dev/sdc2; e2fsck -y /dev/sdc2; resize2fs -s /dev/sdc2" assuming sdc2 is the root filesystem partition on the SD card. Affected image: e.g. http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Pin… -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1086757] New: Images for Raspberry Pi 1/2/3 does not boot - only Splash Screen Rainbow
by bugzilla_noreply＠novell.com 12 Oct '21

12 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1086757 Bug ID: 1086757 Summary: Images for Raspberry Pi 1/2/3 does not boot - only Splash Screen Rainbow Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: kasimir_(a)outlook.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have tried the current images [1] of the Raspberry Pi 1/2/3 and get only the Splash Screen Rainbow. No messages are output through the serial console. [1] RPi1: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2018.03.25-Build1.1.raw.xz RPi2: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-2018.03.25-Build1.1.raw.xz RPi3: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.aarch64-2018.03.25-Build1.1.raw.xz -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1073820] New: meson fails to build projects when run under the fish shell
by bugzilla_noreply＠novell.com 11 Oct '21

11 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1073820 Bug ID: 1073820 Summary: meson fails to build projects when run under the fish shell Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: sor.alexei(a)meowr.ru Reporter: simonf.lees(a)suse.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: pth(a)suse.com, sbrabec(a)suse.com Found By: --- Blocker: --- I have my shell set to /usr/bin/fish and meson fails to detect gcc properly, if I switch to bash then the project builds fine, i've seen this on multiple projects when building under tumbleweed. simon@tek-top ~/src/build/wireless ➤ meson build The Meson build system Version: 0.43.0 Source dir: /home/simon/src/build/wireless Build dir: /home/simon/src/build/wireless/build Build type: native build Project name: wireless Meson encountered an error in file meson.build, line 1, column 0: Unable to detect GNU compiler type: cc: error trying to exec 'cc1': execvp: No such file or directory A full log can be found at /home/simon/src/build/wireless/build/meson-logs/meson-log.txt -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 930505] New: every package available in standard or optional repos is not discoverable via https://software.opensuse.org/search
by bugzilla_noreply＠novell.com 06 Oct '21

06 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=930505 Bug ID: 930505 Summary: every package available in standard or optional repos is not discoverable via https://software.opensuse.org/search Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Infrastructure Assignee: mrueckert(a)suse.com Reporter: mrmazda(a)earthlink.net QA Contact: lrupp(a)suse.com Found By: --- Blocker: --- mc is the package name and binary executable for the best available file manager in openSUSE repos. Latest Midnight Commander (mc) not discoverable via https://software.opensuse.org/search . Until recently, current mc for 13.1 could be found on http://download.opensuse.org/repositories/Base:/System/openSUSE_13.2/ but this repo has been retired. Searching https://software.opensuse.org/search for search term commander produces no hits for Midnight Commander or mc. Search term mc is not acceptable to https://software.opensuse.org/search, as it rejects two character search strings, first by announcement, then when proceeding anyway, searching for mc only as a substring, listing many packages containing string mc but not mc itself. I tried searching for latest mc on https://build.opensuse.org/search but as I am not a builder I found it too difficult to use to locate latest (mc-4.8.14) even with help from irc://freenode/opensuse-factory. Something needs to be done so that every package that exists in standard or BS repos can be discovered via https://software.opensuse.org/search without the degree of difficulty searching for Midnight Commander presents. -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 1102840] New: trackerbug: build fails at some time
by bugzilla_noreply＠novell.com 05 Oct '21

05 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1102840 Bug ID: 1102840 Summary: trackerbug: build fails at some time Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Development Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Depends on: 1081871, 1031548, 1031549, 1068372 Found By: Development Blocker: --- Some packages make assumptions about the date+time they are built e.g. assuming that cookies or SSL-certs in their unittests are not yet expired but that breaks building in the future. This can cause trouble for maintenance-updates later and it makes my reproducible builds efforts harder. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1105510] New: iPXE build failure: Unrecognised relocation type 4
by bugzilla_noreply＠novell.com 04 Oct '21

04 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1105510 Bug ID: 1105510 Summary: iPXE build failure: Unrecognised relocation type 4 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jjolly(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 780322 --> http://bugzilla.opensuse.org/attachment.cgi?id=780322&action=edit ipxe-efi-recognize-plt32-relocation.patch iPXE build is failing with the following error: ./util/elf2efi64 --subsystem=10 bin-x86_64-efi/ipxe.efi.tmp bin-x86_64-efi/ipxe.efi Unrecognised relocation type 4 This is due to a change in the buildtools that causes the efi build to set some relocatable symbols to R_X86_64_PLT32 instead of R_X86_64_PC32. The simple solution is to allow the elf2efi tool to recognize the PLT32 relocation symbols just as it would the PC32 symbols. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1090355] New: GCC 8: qemu build fails
by bugzilla_noreply＠novell.com 04 Oct '21

04 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1090355 Bug ID: 1090355 Summary: GCC 8: qemu 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: --- [ 1107s] In function 'process_section', [ 1107s] inlined from 'elf2pe.isra.4' at util/elf2efi.c:909:25: [ 1107s] util/elf2efi.c:494:2: error: 'strncpy' specified bound 8 equals destination size [-Werror=stringop-truncation] [ 1107s] strncpy ( ( char * ) new->hdr.Name, name, sizeof ( new->hdr.Name ) ); [ 1107s] ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Seen here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1003226] New: Slow loading/page construction
by bugzilla_noreply＠novell.com 03 Oct '21

03 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1003226 Bug ID: 1003226 Summary: Slow loading/page construction Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: matthias(a)mailaender.name QA Contact: adrian(a)suse.com Found By: --- Blocker: --- I already reported my dashboard loading extremely slow https://github.com/openSUSE/open-build-service/issues/2086 which seems to be strengthened by my activity as I have 3 pages full of open requests submitted to Factory or devel project awaiting peer review from maintainers. How since a few weeks the whole website became super slow. Viewing regular package pages or repository enable/disable sites, which I usually quickly click to avoid redundant rebuilds. See also https://github.com/openSUSE/open-build-service/issues/586 I usually only branch or create packages via the web interface and use osc with local builds and only commit stuff that works. But with the current response time it is far too tedious. Pages take several minutes to load for me. Tested on multiple V-DSL connections at various day times. It seems to be a fundamental problem that has gotten worse lately. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1105229] New: Plasmashell attempts to load Wayland-EGL and fails after X11:Xorg repository was added.
by bugzilla_noreply＠novell.com 02 Oct '21

02 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1105229 Bug ID: 1105229 Summary: Plasmashell attempts to load Wayland-EGL and fails after X11:Xorg repository was added. Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: sndirsch(a)suse.com Reporter: mail(a)marekpasnikowski.name QA Contact: bnc-team-screening(a)forge.provo.novell.com Found By: --- Blocker: --- # journalctl | grep -i plasma Aug 17 15:49:39 obikawa14 sddm-greeter[1794]: Reading from "/usr/share/xsessions/plasma5.desktop" Aug 17 15:49:39 obikawa14 sddm-greeter[1794]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop" Aug 17 15:49:47 obikawa14 sddm-greeter[1794]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop" Aug 17 15:49:47 obikawa14 sddm[1762]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop" Aug 17 15:49:47 obikawa14 sddm[1762]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop" Aug 17 15:49:47 obikawa14 sddm[1762]: Session "/usr/share/wayland-sessions/plasmawayland.desktop" selected, command: "dbus-run-session /usr/bin/startplasmacompositor" Aug 17 15:49:47 obikawa14 sddm-helper[1850]: Starting: "/usr/share/sddm/scripts/wayland-session dbus-run-session /usr/bin/startplasmacompositor" Aug 17 15:49:51 obikawa14 ksmserver[1981]: org.kde.kf5.ksmserver: Starting autostart service "/etc/xdg/autostart/org.kde.plasmashell.desktop" ("/usr/bin/plasmashell") Aug 17 15:49:53 obikawa14 plasmashell[1999]: org.kde.plasmaquick: Applet preload policy set to 1 Aug 17 15:49:53 obikawa14 plasmashell[1999]: Using Wayland-EGL Aug 17 15:49:53 obikawa14 plasmashell[1999]: The EGL implementation does not support the Wayland platform After I had added the X11:Xorg repository in order to get fixes for another bug my desktop is no longer rendered by the proper driver. When I tried looking at the logs by myself, I could not find anything indicating the source of the problem. The above fragment is the only thing that I could find that indicates that something went wrong. The X11:Xorg repository has the top priority in my system and I had used the "zypper dup --allow-vendor-change" command. -- You are receiving this mail because: You are on the CC list for the bug.

2 25

[Bug 1091603] New: iproute2: "ip route add default via <ipv6_address>" not parsed correctly
by bugzilla_noreply＠novell.com 01 Oct '21

01 Oct '21

http://bugzilla.suse.com/show_bug.cgi?id=1091603 Bug ID: 1091603 Summary: iproute2: "ip route add default via <ipv6_address>" not parsed correctly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mkubecek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With iproute2 4.16, command "ip route add default via ..." fails if an IPv6 address is supplied (unless "-6" is used): alaris:~ # ip route add default via 1::1 Error: inet address is expected rather than "1::1". This is a regression in version 4.16 fixed by commit d42c7891d26e utils: Do not reset family for default, any, all addresses -- You are receiving this mail because: You are on the CC list for the bug.

2 2