July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1193838] New: LXC /etc/systemd/system.conf is marked executable??
by bugzilla_noreply＠suse.com 21 Nov '22

21 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193838 Bug ID: 1193838 Summary: LXC /etc/systemd/system.conf is marked executable?? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dev.dorrejo(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, i am practicing LXC, and have the next issue: zypper in --no-recommends lxc Configuration file /etc/systemd/system.conf is marked executable. Please remove executable permission bits. Proceeding anyway. ll /etc/systemd/system.conf -rw-r--r-- 1 root root 1993 Nov 24 19:14 /etc/systemd/system.conf getfacl /etc/systemd/system.conf # file: etc/systemd/system.conf # owner: root # group: root user::rw- group::r-- other::r-- Environment: - VMs using tumbleweed up-to-date - Disabled AppArmor - cgroup systemd.unified_cgroup_hierarchy=0 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1196335] New: [Build C.520.1] kdump failed to start: device or resource busy
by bugzilla_noreply＠suse.com 21 Nov '22

21 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196335 Bug ID: 1196335 Summary: [Build C.520.1] kdump failed to start: device or resource busy Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://openqa.opensuse.org/tests/2204439/modules/jour nal_check/steps/22 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario microos-Staging:C-Staging-DVD-x86_64-container-host-microos@64bit-2G-HD40G fails in [journal_check](https://openqa.opensuse.org/tests/2204439/modules/journal_ch… This error appears sporadic, rerunning the test might or might not show the same error: Feb 23 09:28:47.073824 localhost.localdomain systemd[1]: Failed to start Load kdump kernel and initrd. Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: kexec_load failed: Device or resource busy Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: entry = 0x7f554760 flags = 0x3e0001 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: nr_segments = 6 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[0].buf = 0x7f8e0c0ae010 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[0].bufsz = 0x13fbbb4 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[0].mem = 0x7a804000 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[0].memsz = 0x13fc000 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[1].buf = 0x7f8e0d4ade10 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[1].bufsz = 0xb0bdb0 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[1].mem = 0x7bc00000 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[1].memsz = 0x37b4000 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[2].buf = 0x5649202ba900 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[2].bufsz = 0x3fc7 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[2].mem = 0x7f550000 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[2].memsz = 0x4000 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[3].buf = 0x5649202b36c0 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[3].bufsz = 0x70e0 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[3].mem = 0x7f554000 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[3].memsz = 0x9000 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[4].buf = 0x5649202b1860 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[4].bufsz = 0x400 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[4].mem = 0x7f55d000 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[4].memsz = 0x4000 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[5].buf = 0x7f8e0c00f010 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[5].bufsz = 0x9ec00 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[5].mem = 0x7f561000 Feb 23 09:28:47.066939 localhost.localdomain load.sh[562]: segment[5].memsz = 0x9f000 Feb 23 09:28:47.071528 localhost.localdomain kdump[991]: FAILED to load kdump kernel: /sbin/kexec -p /boot/vmlinuz-5.16.10-5-default --append=" rd.timeout=60 rd.retry=45 console=ttyS0 console=tty kernel.softlockup_panic=1 swapaccount=1 quiet security=selinux selinux=1 enforcing=1 mitigations=auto elevator=deadline sysrq=yes reset_devices acpi_no_memhotplug cgroup_disable=memory nokaslr numa=off irqpoll nr_cpus=1 root=kdump rootflags=bind rd.udev.children-max=8 disable_cpu_apicid=0 panic=1" --initrd=/boot/initrd-kdump , Result: kexec_load failed: Device or resource busy entry = 0x7f554760 flags = 0x3e0001 nr_segments = 6 segment[0].buf = 0x7f8e0c0ae010 segment[0].bufsz = 0x13fbbb4 segment[0].mem = 0x7a804000 segment[0].memsz = 0x13fc000 segment[1].buf = 0x7f8e0d4ade10 segment[1].bufsz = 0xb0bdb0 segment[1].mem = 0x7bc00000 segment[1].memsz = 0x37b4000 segment[2].buf = 0x5649202ba900 segment[2].bufsz = 0x3fc7 segment[2].mem = 0x7f550000 segment[2].memsz = 0x4000 segment[3].buf = 0x5649202b36c0 segment[3].bufsz = 0x70e0 segment[3].mem = 0x7f554 Feb 23 09:28:47.073246 localhost.localdomain systemd[1]: kdump.service: Main process exited, code=exited, status=255/EXCEPTION Feb 23 09:28:47.073509 localhost.localdomain systemd[1]: kdump.service: Failed with result 'exit-code'. ## Test suite description ## Reproducible Fails since (at least) Build [C.520.1](https://openqa.opensuse.org/tests/2204217) ## Expected result Last good: [C.519.7](https://openqa.opensuse.org/tests/2203451) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=microos… -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1082318] New: Packages must not mark license files as %doc
by bugzilla_noreply＠novell.com 21 Nov '22

21 Nov '22

http://bugzilla.suse.com/show_bug.cgi?id=1082318 Bug ID: 1082318 Summary: Packages must not mark license files as %doc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Certain licenses require that license files must be shipped together with the binaries in all cases. By using the %doc marker, this is no longer guaranteed (e.g. by enabling excludedocs). Thus it is important that for such cases, %license is used instead of %doc. The effect is that the file is always installed, stored in a different directory (/usr/share/licenses/<pkg>/) and can be queried using rpm (e.g. "rpm -qL kernel-firmware"). -- You are receiving this mail because: You are on the CC list for the bug.

2 249

[Bug 1196829] New: Failed to start auditd rules generation
by bugzilla_noreply＠suse.com 20 Nov '22

20 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196829 Bug ID: 1196829 Summary: Failed to start auditd rules generation Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: armv7 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor Assignee: suse-beta(a)cboltz.de Reporter: matwey.kornilov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, I am trying openSUSE-Leap-15.4-ARM-JeOS-beaglebone.armv7l-2021.12.06-Build2.30.raw.xz image on BeagleBone Black board. I see that augenrules.service is failed at start with default configuration. � augenrules.service - auditd rules generation Loaded: loaded (/usr/lib/systemd/system/augenrules.service; static) Active: failed (Result: exit-code) since Thu 2022-02-24 12:00:56 UTC; 1 week 4 days ago Docs: man:augenrules(8) Process: 1070 ExecStart=/sbin/augenrules --load (code=exited, status=1/FAILURE) Main PID: 1070 (code=exited, status=1/FAILURE) Feb 24 12:00:51 localhost systemd[1]: Starting auditd rules generation... Feb 24 12:00:56 localhost augenrules[1070]: /sbin/augenrules: No change Feb 24 12:00:56 localhost augenrules[1150]: Error sending add rule data request (Invalid argument) Feb 24 12:00:56 localhost augenrules[1150]: There was an error in line 5 of /etc/audit/audit.rules Feb 24 12:00:56 localhost augenrules[1150]: No rules Feb 24 12:00:56 localhost systemd[1]: augenrules.service: Main process exited, code=exited, status=1/FAILURE Feb 24 12:00:56 localhost systemd[1]: augenrules.service: Failed with result 'exit-code'. Feb 24 12:00:56 localhost systemd[1]: Failed to start auditd rules generation. /etc/audit/audit.rules consists of the following lines: ## This file is automatically generated from /etc/audit/rules.d -D -a task,never I am not sure if this issue is related specifically to armv7l architecture or not. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1125418] New: GCC 9: xtrabackup build fails
by bugzilla_noreply＠novell.com 20 Nov '22

20 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1125418 Bug ID: 1125418 Summary: GCC 9: xtrabackup 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/build/openSUSE:Factory:Staging:Gcc7/standard/x86… with: [ 471s] inlined from 'virtual String* Item_func_format::val_str_ascii(String*)' at /home/abuild/rpmbuild/BUILD/percona-xtrabackup-2.4.12/sql/item_strfunc.cc:3214:13: [ 471s] /usr/include/bits/string_fortified.h:34:33: warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)' writing 1 or more bytes into a region of size 0 overflows the destination [-Wstringop-overflow=] [ 471s] 34 | return __builtin___memcpy_chk (__dest, __src, __len, __bos0 (__dest)); [ 471s] | ~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [ 471s] [ 80%] Building CXX object sql/CMakeFiles/sql.dir/item_sum.cc.o -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1200355] New: Access to the current location was denied by GeoClue! (openSUSE-15.4, REGRESSION)
by bugzilla_noreply＠suse.com 20 Nov '22

20 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200355 Bug ID: 1200355 Summary: Access to the current location was denied by GeoClue! (openSUSE-15.4, REGRESSION) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: duge(a)pre-sense.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- redshift and redshift-gtk don't work on openSUSE-LEAP-15.4. This was working on openSUSE-LEAP-15.3, so it's an regression. Error: Unable to start GeoClue client: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: 'redshift' disallowed, no agent for UID 1000. Access to the current location was denied by GeoClue! Related Tumbleweed bug (contains a workaround and more information): Bug 1093592 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1115455] New: rkhunter: migrate from cron to systemd timers
by bugzilla_noreply＠novell.com 20 Nov '22

20 Nov '22

http://bugzilla.suse.com/show_bug.cgi?id=1115455 Bug ID: 1115455 Summary: rkhunter: migrate from cron to systemd timers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: kstreitova(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kstreitova(a)suse.com Found By: --- Blocker: --- This bug is part of TRACKERBUG bug#1115430. Based on fate#323635 (Reduce usage of cron package in favor of systemd timers) we would like to minimize the number of packages that use cron in favour of systemd timers. It seems that your package uses cron. Please take a look at it and evaluate if it's possible to migrate your package to use systemd timers without impacting behaviour. If it's not possible, please write down the reason. Please note that by default, services are not enabled when the package is installed. You probably want your service to be enabled by default so you should create a submit request on systemd-presets-branding-openSUSE package, modifying default-openSUSE.preset file by adding "enable your_service_name.service". -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1115430] New: [TRACKERBUG-OPENSUSE] FATE#323635: Reduce usage of cron in favour of systemd timers
by bugzilla_noreply＠novell.com 20 Nov '22

20 Nov '22

http://bugzilla.suse.com/show_bug.cgi?id=1115430 Bug ID: 1115430 Summary: [TRACKERBUG-OPENSUSE] FATE#323635: Reduce usage of cron in favour of systemd timers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: kstreitova(a)suse.com Reporter: kstreitova(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a tracker bug for fate#323635 (Reduce usage of cron package in favor of systemd timers). It tracks openSUSE packages only (for SLE packages see bug#1115399). The goal is to minimize the number of openSUSE:Factory packages that use cron in favour of systemd timers. See dependent bugs for more information about particular packages that should be migrated. -- You are receiving this mail because: You are on the CC list for the bug.

2 19

[Bug 1200861] New: susefirewall2-to-firewalld fails
by bugzilla_noreply＠suse.com 18 Nov '22

18 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200861 Bug ID: 1200861 Summary: susefirewall2-to-firewalld fails Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: Friedrich.Hotz(a)ef-hotz.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 859801 --> http://bugzilla.opensuse.org/attachment.cgi?id=859801&action=edit crash log susefirewall2-to-firewalld fails - see attachment -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1191170] New: No RDP possible from any KDE app
by bugzilla_noreply＠suse.com 18 Nov '22

18 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191170 Bug ID: 1191170 Summary: No RDP possible from any KDE app Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: cosmin.tanczel(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After an update, I found that I am not able to connect to local network machines through RDP. I have 3 machines, all of them are accesible from a Windows OS without any issues. Using remmina or KRDC I instantly get Cannot connect to the "192.168.1.248" RDP Server. I've tried disabling NLA on the RDP servers, even though it worked before the update without any issues. Connecting to port 3389 using nc works: nc -zv 192.168.1.248 3389 Connection to 192.168.1.248 3389 port [tcp/ms-wbt-server] succeeded! Starting remmina from konsole, I get: Load modules from /usr/lib64/remmina/plugins Remmina plugin glibsecret (type=Secret) has been registered, but is not yet initialized/activated. The initialization order is 2000. The glibsecret secret plugin has been initialized and it will be your default secret plugin (org.remmina.Remmina:4333): Gtk-WARNING **: 11:23:25.205: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem (org.remmina.Remmina:4333): Gtk-CRITICAL **: 11:23:31.454: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed (org.remmina.Remmina:4333): Gtk-CRITICAL **: 11:23:31.455: gtk_toggle_tool_button_set_active: assertion 'GTK_IS_TOGGLE_TOOL_BUTTON (button)' failed (org.remmina.Remmina:4333): Gtk-CRITICAL **: 11:23:31.455: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed [11:23:31:056] [4333:4347] [INFO][com.freerdp.core] - freerdp_connect:freerdp_set_last_error_ex resetting error state [11:23:31:056] [4333:4347] [ERROR][com.freerdp.common.settings] - [freerdp_settings_set_bool] Invalid key index 2816 [11:23:31:056] [4333:4347] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr [11:23:31:056] [4333:4347] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd [11:23:31:056] [4333:4347] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr [11:23:31:056] [4333:4347] [INFO][com.freerdp.client.common.cmdline] - loading channelEx drdynvc [11:23:31:365] [4333:4347] [INFO][com.freerdp.primitives] - primitives autodetect, using optimized [11:23:31:365] [4333:4347] [ERROR][com.freerdp.codec] - Failed to find libav H.264 codec [11:23:31:365] [4333:4347] [ERROR][com.freerdp.core.codecs] - Failed to create h264 codec context libfreerdp returned code is 00000000 So, it seems an update broke something related to libav H.264 codec library. I added the Packman essential repository and switched to this repo so the avcodecs are installed. After this operation everything is working fine. So it means some update broke something that was working before. I only added the Packman repo after I've noticed this issue. Please let me know if there is the need to send you the zypper logs. The issue happened few days ago and I still have the logs. -- You are receiving this mail because: You are on the CC list for the bug.

1 9