September 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1189137] [doc] Example 4.72: Example firewall section
by bugzilla_noreply＠suse.com 27 Sep '21

27 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189137 https://bugzilla.suse.com/show_bug.cgi?id=1189137#c5 Carla Schroder <cschroder(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #5 from Carla Schroder <cschroder(a)suse.com> --- Thank you! SLE15SP3 fb7b50519 SLE15SP2 f5eb51a66 SLE15SP1 368b4bfd6 SLE15SP0 36b0abb55 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187214] Leap 15.3: sle_version is not set
by bugzilla_noreply＠suse.com 27 Sep '21

27 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1187214 https://bugzilla.suse.com/show_bug.cgi?id=1187214#c22 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(maintenance@opens | |use.org) | --- Comment #22 from Marcus Meissner <meissner(a)suse.com> --- i copied over your changes to a incident for release, will go into QA in some hours -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190918] [Staging:A.270.1] openQA test fails in journal_check (audit hardening)
by bugzilla_noreply＠suse.com 27 Sep '21

27 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190918 https://bugzilla.suse.com/show_bug.cgi?id=1190918#c2 Dominique Leuenberger <dleuenberger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dleuenberger(a)suse.com Flags|needinfo?(dimstar@opensuse. | |org) | --- Comment #2 from Dominique Leuenberger <dleuenberger(a)suse.com> --- (In reply to Enzo Matsumiya from comment #1) > I can see those error messages ok, and I already have an idea on what's > failing (probably some systemd unit hardening directives from bsc#1181400, > but I would like to reproduce to confirm before taking action). > > > Always latest result in this scenario: > > [latest](https://openqa.opensuse.org/tests/ > > latest?arch=x86_64&distri=microos&flavor=Staging-DVD&machine=64bit-2G- > > HD40G&test=container-host-microos&version=Staging%3AA) > > That interface is very confusing to me, could you help me > gathering/confirming some information please? In what way confusing? i.e. https://openqa.opensuse.org/tests/1937572 It runs multiple 'test modules' - mainly taking the MicroOS medium (can be downloaded from the test under Logs&Assets) and install it (as role MicroOS container Host) using mostly defaults. > - this is trigged by "systemctl start auditd.service", yes or no? Triggered right after bootup (audit is a default-enabled service). According to the journal, boot happened (in the linked test) at Sep 25 18:42:10, the log from audit appeared at 18:42:45 (regular bootup delay with selinux relabeling and first boot) > - what's the host setup like? I don't have experience with microOS and > container technologies whatsoever, so if you could give me a step-by-step > guide how to get a similar environment I'd appreciate it Nothing special there: default install of MicroOS from DVD (online repo disabled, role MicroOS Container Host); the VM used is kvm/qemu, 40GB HDD and 2GB RAM) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187214] Leap 15.3: sle_version is not set
by bugzilla_noreply＠suse.com 27 Sep '21

27 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187214 http://bugzilla.opensuse.org/show_bug.cgi?id=1187214#c21 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maintenance(a)opensuse.org Flags| |needinfo?(maintenance@opens | |use.org) --- Comment #21 from Michal Suchanek <msuchanek(a)suse.com> --- Changes to Leap-release cannot be submitted - they are autorejected by a bot: https://build.opensuse.org/request/show/921829 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190967] Cannot mount neither Tablet nor Smartphone
by bugzilla_noreply＠suse.com 27 Sep '21

27 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190967 https://bugzilla.suse.com/show_bug.cgi?id=1190967#c1 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner(a)suse.com --- Comment #1 from Marcus Meissner <meissner(a)suse.com> --- is this happening new after the last libmtp update? or was this always the case? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188941] ppc64 optflags don't enable LTO
by bugzilla_noreply＠suse.com 27 Sep '21

27 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188941 http://bugzilla.opensuse.org/show_bug.cgi?id=1188941#c8 Dominique Leuenberger <dimstar(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrian(a)suse.net Flags| |needinfo?(adrian(a)suse.net) --- Comment #8 from Dominique Leuenberger <dimstar(a)opensuse.org> --- (In reply to Michal Suchanek from comment #7) > ppc64 looks OK > > %{optflags}=-O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong > -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection > -Werror=return-type -flto=auto -g > > but s390x still has > > %{optflags}=-O2 -g -m64 -fmessage-length=0 -D_FORTIFY_SOURCE=2 > -fstack-protector -funwind-tables -fasynchronous-unwind-tables Interesting - will have to find where that comes from then, as Optflags in openSUSE:Factory is: Optflags: * -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type %%{?_lto_cflags} @Adrian: any hints? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190976] New: [Build :21254:docker][sporadic] openQA test fails in first_boot after gnome likely crashed or failed to start service
by bugzilla_noreply＠suse.com 27 Sep '21

27 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190976 Bug ID: 1190976 Summary: [Build :21254:docker][sporadic] openQA test fails in first_boot after gnome likely crashed or failed to start service Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other URL: https://openqa.suse.de/tests/7224313/modules/first_boo t/steps/2 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-15.3-Leap-DVD-Incidents-x86_64-cryptlvm@64bit fails in [first_boot](https://openqa.suse.de/tests/7224313/modules/first_boot/steps/2) showing the GDM login screen when instead an automatically logged in gnome session is expected. Likely gnome could not properly start after boot or crashed. Please find logfiles in https://openqa.suse.de/tests/7224313#downloads ## Test suite description Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Maintainers: QE Yast Conduct installation with encrypted LVM selected during installation. Generated disk image used in downstream jobs. (crypt-)LVM installations can take longer, especially on non-x86_64 architectures. YAML_SCHEDULE=schedule/yaml/cryptlvm/cryptlvm_sle.yaml ## Reproducible Fails since (at least) Build [:21254:docker](https://openqa.suse.de/tests/7224313) (current job) ## Expected result Last good: [:21234:glibc](https://openqa.suse.de/tests/7224309) (or more recent) showing the automatically logged in gnome desktop. ## Further details Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=x86_64&distri=opensuse&flavor=Leap-DVD-Incidents&machine=64bit&test=cryptlvm&version=15.3) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187214] Leap 15.3: sle_version is not set
by bugzilla_noreply＠suse.com 27 Sep '21

27 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1187214 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|mls(a)suse.com |mlin+factory(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183054] New: dbus-1-devel-32bit is missing the architecture-specific header files
by bugzilla_noreply＠suse.com 27 Sep '21

27 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183054 Bug ID: 1183054 Summary: dbus-1-devel-32bit is missing the architecture-specific header files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: fgouget(a)codeweavers.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Part of the D-Bus headers have been moved to an architecture-specific location in /usr/lib*, which works fine in 64-bit: $ pkg-config --cflags dbus-1 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include $ echo "#include <dbus/dbus.h>" >config.c $ gcc `pkg-config --cflags dbus-1` -c config.c; echo $? 0 But trying to produce a 32-bit object file fails: $ PKG_CONFIG_PATH=/usr/lib/pkgconfig pkg-config --cflags dbus-1 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include $ gcc -m32 `PKG_CONFIG_PATH=/usr/lib/pkgconfig pkg-config --cflags dbus-1` -c config.c In file included from config.c:1: /usr/include/dbus-1.0/dbus/dbus.h:29:10: fatal error: dbus/dbus-arch-deps.h: No such file or directory 29 | #include <dbus/dbus-arch-deps.h> | ^~~~~~~~~~~~~~~~~~~~~~~ And indeed, while dbus-1-devel does ship dbus-arch-deps.h, dbus-1-devel-32bit does not: $ rpm -ql dbus-1-devel | grep /usr/lib /usr/lib64/cmake /usr/lib64/cmake/DBus1 /usr/lib64/cmake/DBus1/DBus1Config.cmake /usr/lib64/cmake/DBus1/DBus1ConfigVersion.cmake /usr/lib64/dbus-1.0 /usr/lib64/dbus-1.0/include /usr/lib64/dbus-1.0/include/dbus /usr/lib64/dbus-1.0/include/dbus/dbus-arch-deps.h /usr/lib64/libdbus-1.so /usr/lib64/pkgconfig/dbus-1.pc $ rpm -ql dbus-1-devel-32bit | grep /usr/lib /usr/lib/libdbus-1.so /usr/lib/pkgconfig/dbus-1.pc This breaks D-Bus support in 32-bit Windows applications run in Wine. Additional notes: * Configuration with CMake is very likely broken in the same way. * This issue did not exist in Leap 15.2 because the D-Bus shipped there did not yet have the architecture-specific headers. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1188941] ppc64 optflags don't enable LTO
by bugzilla_noreply＠suse.com 27 Sep '21

27 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188941 http://bugzilla.opensuse.org/show_bug.cgi?id=1188941#c7 --- Comment #7 from Michal Suchanek <msuchanek(a)suse.com> --- ppc64 looks OK %{optflags}=-O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -g but s390x still has %{optflags}=-O2 -g -m64 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -- You are receiving this mail because: You are on the CC list for the bug.

1 0