February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[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 1208371] New: Strange assigned DNS
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208371 Bug ID: 1208371 Summary: Strange assigned DNS Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: epistemepromeneur(a)free.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 864926 --> http://bugzilla.opensuse.org/attachment.cgi?id=864926&action=edit details of the bridge connection Yesterday 2023/02/15 there was a tumbleweed update, in particular an update of "NetworkManager". The DNS are assigned by DHCP. European Community supplies them. DNS1=193.110.81.0#dns0.eu DNS1=2a0f:fc80::#dns0.eu DNS2=185.253.5.0#dns0.eu DNS2=2a0f:fc81::#dns0.eu After the update, for the bridge : �� there is no more an IPV4 secondary DNS �� the IPV4 primary DNS is no more 193.110.81.0 but 184.6.216.251 The DNS of my provider are : 212.27.40.240 / 212.27.40.241 Where does this 184.6.216.251 DNS come from ? -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[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 1208381] New: Drop gumbo-parser from the distribution
by bugzilla_noreply＠suse.com 12 Mar '23

12 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208381 Bug ID: 1208381 Summary: Drop gumbo-parser from the distribution Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: jengelh(a)inai.de Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dmueller(a)suse.com, llyyr.public(a)gmail.com, mimi.vx(a)gmail.com, socvirnyl.estela(a)gmail.com Found By: --- Blocker: --- In https://github.com/sparklemotion/nokogiri/issues/2318 I asked why it was possible to build against the system copy of gumbo-parser. The reply was "the upstream copy is insecure and should not be used with user generated content" I asked google for clarification about the status and last night I got the reply that the project is now declared dead. https://twitter.com/arw/status/1626016312467271682 osc whatdependson openSUSE:Factory/gumbo-parser standard x86_64 gumbo-parser : claws-mail gromox mupdf python-PyMuPDF sioyek zathura-plugin-pdf-mupdf -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[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 1207837] New: amdgpu: externals displays don't work when booting with plugged in docking station
by bugzilla_noreply＠suse.com 11 Mar '23

11 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207837 Bug ID: 1207837 Summary: amdgpu: externals displays don't work when booting with plugged in docking station 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: jirib79(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 864672 --> http://bugzilla.opensuse.org/attachment.cgi?id=864672&action=edit dmesg - one with plugged in, other without 6.1.8-3.gbddbb73-default #1 openSUSE Tumbleweed (unreleased) ec01a7011546b1865e0ba429f47535b0e2fbc5e1, but also usual latest TW kernel - Lenovo T14s gen1 - FW: 0.1.42 (latest for 2023-02-01) - no idea if docking statin FW exists and can be updated When Lenonvo T14s Gen1 boots with plugged in USB-C connecting it with 'ThinkPad Hybrid USB-C with USB-A Dock (40AF)' (??) the externals monitors never work. The OS has to be booted with docking station unplugged, then when plugged again external monitors work. But..., after than when suspend is done, after resume the monitors are not active anymore - although visible in `xrandr' output. Steps to reproduce: - the docking station - external monitors (i have two SAMSUNG LF22T450F, HDMI and DP connected) - boot with usb-c cable between the docking station and Lenovo T14s gen1 plugged in Is this related? ---%>--- # tac /root/dmesg.txt | grep -m1 -A 20 -B 40 'Call Trace:' | tac Feb 01 17:47:35 t14s kernel: usb 5-1.1: SerialNumber: 301000001 Feb 01 17:47:35 t14s kernel: amdgpu: [VBLANK]:crtc:0, vupdate-vrr:0, planes:1 Feb 01 17:47:35 t14s kernel: amdgpu: [VBLANK]:crtc:0, vupdate-vrr:0, planes:1 Feb 01 17:47:35 t14s kernel: ------------[ cut here ]------------ Feb 01 17:47:35 t14s kernel: WARNING: CPU: 6 PID: 161 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link.c:3533 update_mst_stream_alloc_table+0x150/0x160 [amdgpu] Feb 01 17:47:35 t14s kernel: Modules linked in: dm_crypt essiv authenc trusted asn1_encoder tee hid_generic usbhid amdgpu crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul drm_ttm_helper ttm iommu_v2 ghash_clmulni_intel gpu_sched ehci_pci xhci_pci sha512_ssse3 rtsx_pci_sdmmc xhci_pci_renesas drm_buddy mmc_core drm_display_helper xhci_hcd ehci_hcd aesni_intel ucsi_acpi nvme crypto_simd typec_ucsi cryptd cec usbcore roles nvme_core ccp rtsx_pci sp5100_tco rc_core typec video battery wmi serio_raw btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq dm_mirror dm_region_hash dm_log sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua ledtrig_timer msr efivarfs Feb 01 17:47:35 t14s kernel: CPU: 6 PID: 161 Comm: kworker/6:1 Tainted: G W 6.1.8-3.gbddbb73-default #1 openSUSE Tumbleweed (unreleased) ec01a7011546b1865e0ba429f47535b0e2fbc5e1 Feb 01 17:47:35 t14s kernel: Hardware name: LENOVO 20UJS2B901/20UJS2B901, BIOS R1CET73W(1.42 ) 12/09/2022 Feb 01 17:47:35 t14s kernel: Workqueue: events_long drm_dp_mst_link_probe_work [drm_display_helper] Feb 01 17:47:35 t14s kernel: RIP: 0010:update_mst_stream_alloc_table+0x150/0x160 [amdgpu] Feb 01 17:47:35 t14s kernel: Code: 00 00 75 2d 48 81 c4 98 00 00 00 5b 5d 41 5c e9 16 da ad d5 41 0f b7 40 04 4d 89 19 49 89 59 08 66 41 89 41 10 e9 71 ff ff ff <0f> 0b e9 fe fe ff ff e8 c4 01 83 d5 0f 1f 40 00 0f 1f 44 00 00 55 Feb 01 17:47:35 t14s kernel: RSP: 0018:ffffb7ce0073f678 EFLAGS: 00010202 Feb 01 17:47:35 t14s kernel: RAX: 0000000000000002 RBX: 0000000000000000 RCX: 0000000000000000 Feb 01 17:47:35 t14s kernel: RDX: 0000000000000000 RSI: ffffb7ce0073f678 RDI: ffffb7ce0073f708 Feb 01 17:47:35 t14s kernel: RBP: ffff9826d5e00aa0 R08: ffffb7ce0073f738 R09: ffffb7ce0073f480 Feb 01 17:47:35 t14s kernel: R10: ffff9826c7edb000 R11: ffff9826dd3037e0 R12: 0000000000000002 Feb 01 17:47:35 t14s kernel: R13: ffff9826d8701000 R14: ffffffffc188d8e0 R15: 0000000000000000 Feb 01 17:47:35 t14s kernel: FS: 0000000000000000(0000) GS:ffff9829bf980000(0000) knlGS:0000000000000000 Feb 01 17:47:35 t14s kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 01 17:47:35 t14s kernel: CR2: 00007effc2b12440 CR3: 0000000295010000 CR4: 0000000000350ee0 Feb 01 17:47:35 t14s kernel: Call Trace: Feb 01 17:47:35 t14s kernel: <TASK> Feb 01 17:47:35 t14s kernel: dc_link_allocate_mst_payload+0x95/0x290 [amdgpu 94e1b47238533e7ef69a131fcfbdc0d3832eb584] Feb 01 17:47:35 t14s kernel: core_link_enable_stream+0x7cc/0x980 [amdgpu 94e1b47238533e7ef69a131fcfbdc0d3832eb584] Feb 01 17:47:35 t14s kernel: ? optc1_set_drr+0x136/0x1e0 [amdgpu 94e1b47238533e7ef69a131fcfbdc0d3832eb584] Feb 01 17:47:35 t14s kernel: dce110_apply_ctx_to_hw+0x652/0x700 [amdgpu 94e1b47238533e7ef69a131fcfbdc0d3832eb584] Feb 01 17:47:35 t14s kernel: dc_commit_state_no_check+0x38c/0xc90 [amdgpu 94e1b47238533e7ef69a131fcfbdc0d3832eb584] Feb 01 17:47:35 t14s kernel: dc_commit_state+0x92/0x110 [amdgpu 94e1b47238533e7ef69a131fcfbdc0d3832eb584] Feb 01 17:47:35 t14s kernel: amdgpu_dm_atomic_commit_tail+0x4a0/0x2a80 [amdgpu 94e1b47238533e7ef69a131fcfbdc0d3832eb584] Feb 01 17:47:35 t14s kernel: ? get_page_from_freelist+0x4d9/0x1590 Feb 01 17:47:35 t14s kernel: ? dcn21_fast_validate_bw+0x3be/0x490 [amdgpu 94e1b47238533e7ef69a131fcfbdc0d3832eb584] Feb 01 17:47:35 t14s kernel: ? dcn21_validate_bandwidth_fp+0x101/0x6d0 [amdgpu 94e1b47238533e7ef69a131fcfbdc0d3832eb584] Feb 01 17:47:35 t14s kernel: ? __alloc_pages+0xec/0x240 Feb 01 17:47:35 t14s kernel: ? __get_random_u32_below+0x12/0x60 Feb 01 17:47:35 t14s kernel: ? allocate_slab+0x255/0x490 Feb 01 17:47:35 t14s kernel: ? drm_atomic_helper_setup_commit+0x4c7/0x840 Feb 01 17:47:35 t14s kernel: ? dma_resv_iter_first_unlocked+0x62/0x70 Feb 01 17:47:35 t14s kernel: ? dma_resv_get_fences+0x52/0x210 Feb 01 17:47:35 t14s kernel: ? wait_for_completion_timeout+0x112/0x140 Feb 01 17:47:35 t14s kernel: commit_tail+0x94/0x130 Feb 01 17:47:35 t14s kernel: drm_atomic_helper_commit+0x112/0x140 Feb 01 17:47:35 t14s kernel: drm_atomic_commit+0x77/0xf0 Feb 01 17:47:35 t14s kernel: ? drm_plane_get_damage_clips.cold+0x1c/0x1c Feb 01 17:47:35 t14s kernel: drm_client_modeset_commit_atomic+0x1e7/0x230 Feb 01 17:47:35 t14s kernel: drm_client_modeset_commit_locked+0x56/0x160 Feb 01 17:47:35 t14s kernel: drm_client_modeset_commit+0x21/0x40 Feb 01 17:47:35 t14s kernel: drm_fb_helper_set_par+0x9e/0xe0 Feb 01 17:47:35 t14s kernel: drm_fb_helper_hotplug_event+0x9f/0xe0 Feb 01 17:47:35 t14s kernel: drm_kms_helper_hotplug_event+0x26/0x30 Feb 01 17:47:35 t14s kernel: process_one_work+0x20f/0x3d0 Feb 01 17:47:35 t14s kernel: worker_thread+0x4a/0x3b0 Feb 01 17:47:35 t14s kernel: ? process_one_work+0x3d0/0x3d0 Feb 01 17:47:35 t14s kernel: kthread+0xda/0x100 Feb 01 17:47:35 t14s kernel: ? kthread_complete_and_exit+0x20/0x20 Feb 01 17:47:35 t14s kernel: ret_from_fork+0x22/0x30 Feb 01 17:47:35 t14s kernel: </TASK> Feb 01 17:47:35 t14s kernel: ---[ end trace 0000000000000000 ]--- Feb 01 17:47:35 t14s kernel: amdgpu: [VBLANK]:crtc:0, vupdate-vrr:0, planes:1 Feb 01 17:47:35 t14s kernel: amdgpu: [VBLANK]:crtc:0, vupdate-vrr:0, planes:1 Feb 01 17:47:36 t14s kernel: [HDCP_TOP]: Feb 01 17:47:36 t14s kernel: [HDCP_TOP]:[Link 0] mod_hdcp_add_display display 4 ---%<--- -- You are receiving this mail because: You are on the CC list for the bug.

1 9