January 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1206570] New: [SELinux] rebootmgr: new features needs bash execution
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1206570 Bug ID: 1206570 Summary: [SELinux] rebootmgr: new features needs bash execution 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: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- rebootmgr get's a new feature: make the reboot command configureable, so that we could use kexec, too (https://github.com/SUSE/rebootmgr/issues/13) This requires that the policy for rebootmgr allows to execute a shell: type=AVC msg=audit(1671572322.755:93): avc: denied { execute } for pid=1445 comm="rebootmgrd" name="bash" dev="vda2" ino=43372 scontext=system_u:system_r:rebootmgr_t:s0 tcontext=system_u:object_r:shell_exec_t:s0 tclass=file permissive=0 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1200955] New: ansible-lint broken: ModuleNotFoundError: No module named 'ansiblelint'
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1200955 Bug ID: 1200955 Summary: ansible-lint broken: ModuleNotFoundError: No module named 'ansiblelint' 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: felix.niederwanger(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The ansible-lint package on Tumbleweed complains about the missing ansiblelint module: > phoenix@racetrack-7290:~/Projects/geekoops> ansible-lint > Traceback (most recent call last): > File "/usr/bin/ansible-lint", line 5, in <module> > from ansiblelint.__main__ import _run_cli_entrypoint > ModuleNotFoundError: No module named 'ansiblelint' -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1200542] New: Regional preferences error with "default" locale
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1200542 Bug ID: 1200542 Summary: Regional preferences error with "default" locale 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: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: smartinds(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 859593 --> http://bugzilla.opensuse.org/attachment.cgi?id=859593&action=edit Screenshot with the solution When I configure in: Preferences > Formats > Region > es_PE (Per�) Result: Many of the details (Numbers, Date, Money) are in "Default" so if I save the config: $ locale locale: Cannot set LC_ALL to default locale: No existe el fichero o el directorio (Don't exist the file or directory) Also, some apps in python show error: locale.Error: unsupported locale setting BUT, if I config each detail with es_PE, all is OK. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1200391] New: Add country flag to the calendar in digital clock
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1200391 Bug ID: 1200391 Summary: Add country flag to the calendar in digital clock Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: smartinds(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 859507 --> http://bugzilla.opensuse.org/attachment.cgi?id=859507&action=edit screenshot When I configure two or more calendars en the clock, the holidays of different countries are confusing BUT if flags are added it would be solved. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1189826] New: Severe screen flickering with kernel 5.13.12-1-default and i915
by bugzilla_noreply＠suse.com 12 Mar '23

12 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1189826 Bug ID: 1189826 Summary: Severe screen flickering with kernel 5.13.12-1-default and i915 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: javier(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- My laptop's screen flickers so much with 5.13.12 that it renders my laptop unusable. One workaround is to close and open the lid. After resuming, it works fine - there is no flickering. Booting up from the KDE Live image works fine. I have used the same Tumbleweed version (20210820) as the one I have installed on my laptop. The only difference is that I have an encrypted /home partition on my laptop's SSD. Tested kernels: 5.10.16-1.3: OK 5.11.4-1.3: NON-OK 5.12.12-1: NON-OK 5.13.12-1: NON-OK KDE Plasma 5.22.4 KDE Frameworks 5.85.0 Qt 5.15.2 See the attachments for more details. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1206651] New: Leap 15.4 guests running VirtualBox 7.0.4 crash when run on hosts with certain Intel graphics cards
by bugzilla_noreply＠suse.com 12 Mar '23

12 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206651 Bug ID: 1206651 Summary: Leap 15.4 guests running VirtualBox 7.0.4 crash when run on hosts with certain Intel graphics cards 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: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: Larry.Finger(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Long-term tests of Leap 15.4 guests running VirtualBox 7.0.4 find crashes of the VM. If 'journalctl -f' is running on the VM, the output shows repeated instances of the following: Dec 18 07:36:28 suse15r2 kernel: [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out Dec 18 07:36:28 suse15r2 kernel: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:38:crtc-0] commit wait timed out Testing showed that VMs running the Oracle version of the code did not have the problem, which led to the solution. When the kernel module vboxvideo.ko became part of the kernel, generation of that module was disabled in the openSUSE package. Although this decision had not previously caused problems, something in the 7.0.4 code is interacting badly with that kernel module from 5.14.X when used with the i915 driver for the Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] hardware. The "bug" is causing the VM to error. There may be other types of Intel graphics devices that error - this was the only one that was available for testing. The problem happened on every machine with this graphics device, and is not an obscure hardware error. On one machine with nVidia hardware using the nouveau driver, no problems were noted. We also did not find the problem with Tumbleweed guests. It seems that whatever causes the bug, it was fixed between kernel 5.14.X used in Leap 15.4 and kernel 6.0.X used in Tumbleweed. Once the module vboxvideo.ko was generated as part of the virtualbox-kmp-default package, and the new code was installed on the VM, no further problems of this type were noted. Outside the scope of this defect, but worth noting, all Windows 11 guests run with the 7.0.4 guest extensions crashed. Furthermore, these crashes corrupted the virtual disk of the guest. Oracle knows of this problem and strongly recommends that Windows 11 guests be run with the VB 6.1.40 guest extensions. We have not found any problems with this configuration. Whether Windows 10 is also affected is not clear. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1207386] New: [Build 20230121] openQA test fails in docker_firewall
by bugzilla_noreply＠suse.com 11 Mar '23

11 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207386 Bug ID: 1207386 Summary: [Build 20230121] openQA test fails in docker_firewall Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3060138/modules/dock er_firewall/steps/68 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation The test runs iptables -L DOCKER-USER -nvx --line-numbers, which does return valid data, but 'proto' is not translated from '0' to 'all'; looks like a lookup table missing? openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-containers_host_docker@64bit fails in [docker_firewall](https://openqa.opensuse.org/tests/3060138/modules/docker_f… ## Test suite description Maintainer: dheidler. Extra tests about CLI software in container module ## Reproducible Fails since (at least) Build [20230121](https://openqa.opensuse.org/tests/3059492) ## Expected result Last good: [20230120](https://openqa.opensuse.org/tests/3057872) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1206614] New: [Build 20221221] nerdctl: fails to initialize if iptables is absent
by bugzilla_noreply＠suse.com 11 Mar '23

11 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206614 Bug ID: 1206614 Summary: [Build 20221221] nerdctl: fails to initialize if iptables is absent Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2970571/modules/cont ainerd_nerdctl/steps/58 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation [31mFATA[0m[0000] failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: time="2022-12-22T02:29:28-05:00" level=fatal msg="failed to call cni.Setup: plugin type=\"bridge\" failed (add): failed to locate iptables: exec: \"iptables\": executable file not found in $PATH" Failed to write to log, write /var/lib/nerdctl/1935db59/containers/default/c3cf5d1baef6bdb4812f94cfa6e37fecbe170d360f70df78177b114c940056f8/oci-hook.createRuntime.log: file already closed: unknown If it's so keen to have iptables present, it should require it (better yet, migrate to nftables) openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-containers_host_containerd@64bit fails in [containerd_nerdctl](https://openqa.opensuse.org/tests/2970571/modules/conta… ## Test suite description Maintainer: dheidler. Extra tests about CLI software in container module ## Reproducible Fails since (at least) Build [20221221](https://openqa.opensuse.org/tests/2969686) ## Expected result Last good: [20221220](https://openqa.opensuse.org/tests/2967582) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1204007] New: Use region-specific variant of noto sans/serif cjk fonts, not language-specific ones as source
by bugzilla_noreply＠suse.com 10 Mar '23

10 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1204007 Bug ID: 1204007 Summary: Use region-specific variant of noto sans/serif cjk fonts, not language-specific ones as source 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: i(a)marguerite.su QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, I am the initial packager of google-noto-sans/serif-CJK-fonts and the maintainer of our fonts-config. In the early version of that package, I used region-specific variants. Later Mr. hillwood replaced them with language-specific variants and accepted the submit request by himself, then guoyunhe continued to update that package with language specific ones There is a known bug back in 2016 that Japanese variant wll always take effect due to the alphabetical order so you can not see any chinese variant. Nowadays in 2022, although pango/harfbuzz/freetype support opentype locl feature and language tagging underlying, this regression still exists because: 1. All Qt applications don��t support any opentype features because QFont doesn��t implemented such things 2. GTK supports them but rare application made use of that, eg: GIMP still can��t use opentype features although GTKFontChooser allows such usage since 3.24 3. Such usage needs programming, it does not mean users can simply set up font variant in system settings and the Simplified Chinese variant will apply everywhere. Every application/web page needs to enable opentype locl features during programming. So only professional application like Adobe CS 6 may adapt to it. We will not see it work out of the box in the foreseeable future. So the only benefit of using language-specific variants is its code point coverage, but seldom people needs to display Pan CJK everyday while everyone hates to see Japanese variant in charge under non-Japanese locales And openSUSE��s fonts-config were implemented with region-specific font names eg ��Noto Sans SC�� not ��Noto Sans CJK SC��. such packaging nearly destroyed those font configurations Please fix -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1206835] New: iodine cannot find /dev/net/tun after upgrade from Leap 15.3 to 15.4
by bugzilla_noreply＠suse.com 10 Mar '23

10 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206835 Bug ID: 1206835 Summary: iodine cannot find /dev/net/tun after upgrade from Leap 15.3 to 15.4 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: wagner-thomas(a)gmx.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading from Leap 15.3 to 15.4, iodined.service won't start. Output of journalctl ``` iodined: open_tun: /dev/net/tun: No such file or directory: No such file or directory ``` However, /dev/net/tun is present. ``` #ls -alh /dev/net/tun crw-rw-rw- 1 root root 10, 200 4. Jan 12:36 /dev/net/tun ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 3