March 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1209932] New: Connection to hotspot does not prompt for login/confirmation
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209932 Bug ID: 1209932 Summary: Connection to hotspot does not prompt for login/confirmation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello GNOME team, my setup is a thinkpad t495s with MicroOS Desktop with GNOME with a default browser set to chrome from flatpak. I'm using network manager and standard steps to connect to wifi (click over the pannel on the network icon). When I try to connect to any hotspot the web-dialog to agree with terms and conditions or a login typically in case of a hotel never opens automatically. I typically have to open web browser and manually figure out and access the domain triggering the dialog with terms and conditions or login to the hostpos (e.g. cd.cz in a train). When I try it with phone either Android or iOS I always get the webdialog as part of the connection process. This seems to be a long term issue as I did experience it months ago in Vienna, Devconf conference as well as on Tuesday when I travelled to prague office. So I'd say every time when I try to connect to hotspot. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1208869] New: MicroOS - Urdu Lanuage (Pakistan) Keyboard,Formats and Region Support, Arabic Keyboarb (Pakistan) layout support
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208869 Bug ID: 1208869 Summary: MicroOS - Urdu Lanuage (Pakistan) Keyboard,Formats and Region Support, Arabic Keyboarb (Pakistan) layout support Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: abuturaaab+opensuse(a)proton.me QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 865218 --> http://bugzilla.opensuse.org/attachment.cgi?id=865218&action=edit Screenshots of the said issues and improvements Hi, I have installed MicoOS today, on first boot, it showed by the keyboard layout choice dialogue where Urdu(Pakistan) Keyboard was listed. But on click it does nothing, so I though, I can easily enable it after initial startup from the settings. But when I checked the keyboard settings afterwards, it doesn't show Urdu (Pakistan) layout as an option (Screenshot attached). Secondly, when I go to language or formats settings, and search for Urdu or Pakistan, It just shows small boxes, which does show Pakistan's format or language is there but fonts are not installed. (Screenshots attached) Third, I would like to have Arabic Keyboard with Pakistan's layout, which already available in the other mainstreams distros like Fedora and Ubuntu. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1088738] New: xhost setting fails to have affect in /etc/gdm/Xsession --- "no protocol specified"
by bugzilla_noreply＠novell.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1088738 Bug ID: 1088738 Summary: xhost setting fails to have affect in /etc/gdm/Xsession --- "no protocol specified" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: noah(a)chromakey.io QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- line 154 xhost+ si:localuser ... needs to be in /etc/X11/xinit/xinitrc.d/what-ever.sh ... ... or maybe somewhere else all I know is that in Xsession it fails to have any affect ... effectively breaking the X11 gnome access for remote logins/ssh/etc. I'd expect a lot of bug reports of people angry, confused .. and complaining about "no protocol specified" errors. Thanks! -noah -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1209980] New: Lenovo L14 Gen3, wifi card not recognized.
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209980 Bug ID: 1209980 Summary: Lenovo L14 Gen3, wifi card not recognized. 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: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, on new Lenovo L14 Gen3 laptop, AMD CPU, the wifi hardware is not recognized. This is an enterprise class laptop. It is recognized with kernel from "Kernel:stable:Backports" "https://download.opensuse.org/repositories/Kernel:/stable:/Backport/standar…" Laicolasse:~ # uname -a Linux Laicolasse 6.2.8-lp154.3.gc9a94ac-default #1 SMP PREEMPT_DYNAMIC Tue Mar 28 07:54:15 UTC 2023 (c9a94ac) x86_64 x86_64 x86_64 GNU/Linux Laicolasse:~ # Perhaps the driver can be backported? *Information before updating kernel* Laicolasse:~ # inxi --bluetooth -n -N Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: eth0 state: up speed: 100 Mbps duplex: full mac: f4:a8:0d:7a:49:01 Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: N/A Bluetooth: Device-1: Foxconn / Hon Hai Wireless_Device type: USB driver: btusb Report: bt-adapter ID: hci0 state: up address: 60:E9:AA:A0:1A:4A Laicolasse:~ # Command "ip addr" displays info on just eth0 and lo. Journal: <https://paste.opensuse.org/pastes/ccc804e35e3c> (if you want it attached to bugzilla, just ask, but it is already there because I asked on mail list) Laicolasse:~ # lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge 00:02.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge 00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge 00:02.6 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 7 01:00.0 Non-Volatile memory controller: KIOXIA Corporation Device 000c 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0e) 04:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01) 06:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter <======== 07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo (rev d1) 07:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller 07:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor 07:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 07:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 07:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor (rev 01) 07:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller Laicolasse:~ # Laicolasse:~ # hwinfo --netcard 07: PCI 300.0: 0200 Ethernet controller [Created at pci.386] Unique ID: rBUF.Osz2B5WC6KD Parent ID: aYFK.nSObxEWmqk3 SysFS ID: /devices/pci0000:00/0000:00:02.3/0000:03:00.0 SysFS BusID: 0000:03:00.0 Hardware Class: network Model: "Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd." Device: pci 0x8168 "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x50ae Revision: 0x0e Driver: "r8169" Driver Modules: "r8169" Device File: eth0 I/O Ports: 0x2000-0x2fff (rw) Memory Range: 0xfd604000-0xfd604fff (rw,non-prefetchable) Memory Range: 0xfd600000-0xfd603fff (rw,non-prefetchable) IRQ: 41 (no events) HW Address: f4:a8:0d:7a:49:01 Permanent HW Address: f4:a8:0d:7a:49:01 Link detected: yes Module Alias: "pci:v000010ECd00008168sv000017AAsd000050AEbc02sc00i00" Driver Info #0: Driver Status: r8169 is active Driver Activation Cmd: "modprobe r8169" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #14 (PCI bridge) 27: PCI 600.0: 0280 Network controller [Created at pci.386] Unique ID: vTuk.elCpZcgOa6E Parent ID: AXjq.nSObxEWmqk3 SysFS ID: /devices/pci0000:00/0000:00:02.6/0000:06:00.0 SysFS BusID: 0000:06:00.0 Hardware Class: network Model: "MEDIATEK Network controller" Vendor: pci 0x14c3 "MEDIATEK Corp." Device: pci 0x0616 SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0xe0c6 Memory Range: 0xe0200000-0xe02fffff (ro,non-prefetchable,disabled) Memory Range: 0xfd400000-0xfd407fff (rw,non-prefetchable,disabled) IRQ: 255 (no events) Module Alias: "pci:v000014C3d00000616sv000017AAsd0000E0C6bc02sc80i00" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #28 (PCI bridge) Laicolasse:~ # *After kernel upgrade*, the list of kernel packages is: Laicolasse:~ # rpm -qa | grep kernel kernel-firmware-radeon-20230320-lp154.2.1.noarch kernel-firmware-brcm-20230320-lp154.2.1.noarch kernel-firmware-nfp-20230320-lp154.2.1.noarch kernel-default-6.2.8-lp154.3.1.gc9a94ac.x86_64 kernel-firmware-amdgpu-20230320-lp154.2.1.noarch kernel-firmware-bnx2-20230320-lp154.2.1.noarch kernel-default-optional-5.14.21-150400.24.46.1.x86_64 kernel-firmware-network-20230320-lp154.2.1.noarch kernel-firmware-usb-network-20230320-lp154.2.1.noarch kernel-firmware-all-20230320-lp154.2.1.noarch kernel-firmware-liquidio-20230320-lp154.2.1.noarch kernel-firmware-mwifiex-20230320-lp154.2.1.noarch kernel-firmware-ath10k-20230320-lp154.2.1.noarch kernel-default-5.14.21-150400.24.46.1.x86_64 kernel-firmware-media-20230320-lp154.2.1.noarch kernel-firmware-ueagle-20230320-lp154.2.1.noarch kernel-firmware-serial-20230320-lp154.2.1.noarch kernel-firmware-iwlwifi-20230320-lp154.2.1.noarch kernel-default-extra-5.14.21-150400.24.46.1.x86_64 kernel-firmware-qlogic-20230320-lp154.2.1.noarch kernel-firmware-dpaa2-20230320-lp154.2.1.noarch kernel-firmware-marvell-20230320-lp154.2.1.noarch kernel-firmware-ti-20230320-lp154.2.1.noarch kernel-firmware-realtek-20230320-lp154.2.1.noarch kernel-firmware-intel-20230320-lp154.2.1.noarch kernel-firmware-qcom-20230320-lp154.2.1.noarch kernel-firmware-chelsio-20230320-lp154.2.1.noarch kernel-firmware-nvidia-20230320-lp154.2.1.noarch kernel-firmware-bluetooth-20230320-lp154.2.1.noarch kernel-firmware-i915-20230320-lp154.2.1.noarch kernel-firmware-prestera-20230320-lp154.2.1.noarch purge-kernels-service-0-150200.8.6.1.noarch kernel-firmware-atheros-20230320-lp154.2.1.noarch kernel-firmware-mellanox-20230320-lp154.2.1.noarch kernel-firmware-platform-20230320-lp154.2.1.noarch kernel-firmware-ath11k-20230320-lp154.2.1.noarch kernel-firmware-mediatek-20230320-lp154.2.1.noarch kernel-firmware-sound-20230320-lp154.2.1.noarch Laicolasse:~ # Laicolasse:~ # ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether f4:a8:0d:7a:49:01 brd ff:ff:ff:ff:ff:ff altname enp3s0f0 inet 192.168.2.17/16 brd 192.168.255.255 scope global dynamic noprefixroute eth0 valid_lft 43148sec preferred_lft 43148sec inet6 fe80::f6a8:dff:fe7a:4901/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether ee:19:17:ef:15:3d brd ff:ff:ff:ff:ff:ff permaddr 60:e9:aa:a0:1a:49 altname wlp6s0 Laicolasse:~ # Network manager now recognizes wlan, and it works instantly. Although an ssh terminal seems to give slow response to typing, with an AP just 2 meters away. I can provide any other information you need, on request. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1208941] New: VirtualBox: 'USB Rules and Permissions' popup on every start
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208941 Bug ID: 1208941 Summary: VirtualBox: 'USB Rules and Permissions' popup on every start Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: jayjayjazz(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: Community User Blocker: --- Every time I start VirtualBox 7.0.6 the popup 'USB Rules and Permissions' is shown. I choose 'Disable' and enter the root password in the next step. The popup is shown again on the next start of VirtualBox. In my previous Tumbleweed installation, the popup did only occur once. Additional information: - The file 'disable' is created in the folder /home/<user>/.config/VirtualBox/ - The script 'vbox-fix-usb-rules.sh' is located in /usr/sbin/ - my user is added to the group 'vboxusers' - I already tried removing virtualbox and reinstalling again. I also deleted the folder /home/<user>/.config/VirtualBox/. No change in the behavior. System: - OS Release: 6.2.1-1-default - VirtualBox XPCOM Server 7.0.6_SUSE r155176 linux.amd64 (no date no time) release -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1208117] New: Teach kernel-scriptlets/rpm-script about systemd-boot
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208117 Bug ID: 1208117 Summary: Teach kernel-scriptlets/rpm-script about systemd-boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- rpm-script shell script has: run_bootloader () { if [ -f /etc/sysconfig/bootloader ] && [ -f /boot/grub/menu.lst -o \ -f /etc/lilo.conf -o \ -f /etc/elilo.conf -o \ -f /etc/zipl.conf -o \ -f /etc/default/grub ] then return 0 else return 1 fi } If we want to support systemd-boot as bootloader, the hard-coded list of bootloader config files needs to be updated. However at a first glance it would have been better if `run_bootloader()` didn't make any assumption on the supported bootloaders and let /usr/lib/bootloader/bootloader_entry figure out itself what to do with the current installation. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1193135] Key stuck after resume from S3
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1193135 https://bugzilla.suse.com/show_bug.cgi?id=1193135#c15 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(opensuse@trummer. | |xyz) | --- Comment #15 from Stefan Dirsch <sndirsch(a)suse.com> --- Ok. Thanks for verifying again! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193135] Key stuck after resume from S3
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1193135 https://bugzilla.suse.com/show_bug.cgi?id=1193135#c14 --- Comment #14 from Maximilian Trummer <opensuse(a)trummer.xyz> --- (In reply to Stefan Dirsch from comment #12) > I guess this issue is still active with current TW, right? Yes I still experience this bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1209457] NFSv4 broken after kernel update (5.14.21-150400.24.46-default to 5.14.21-150400.24.49)
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209457 https://bugzilla.suse.com/show_bug.cgi?id=1209457#c30 --- Comment #30 from Marcus Meissner <meissner(a)suse.com> --- should be quite quick, an hour or two after release. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1209725] New: autoinst.xml gen by "yast2 clone_system" mess thin pool LVM patitions?
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209725 Bug ID: 1209725 Summary: autoinst.xml gen by "yast2 clone_system" mess thin pool LVM patitions? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST Assignee: yast2-maintainers(a)suse.de Reporter: Joel.Soete(a)skynet.be QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 865832 --> http://bugzilla.opensuse.org/attachment.cgi?id=865832&action=edit yast y2log file Hello, I would like to be able to easily clone my OpenSUSE Virtualbox VMs (possibly create my customized Vagrant box) thanks to autoyast. But as I always prefer to install my filesystems in this kind of LVM structure as follow: unixadmin@uts-ansible:~> sudo vgs VG #PV #LV #SN Attr VSize VFree ansiblevg00 1 9 0 wz--n- 39.00g 0 unixadmin@uts-ansible:~> sudo lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert boot ansiblevg00 -wi-ao---- 2.00g extra ansiblevg00 Vwi-aotz-- 2.00g thinpool00 3.15 home ansiblevg00 Vwi-aotz-- 2.00g thinpool00 3.18 opt ansiblevg00 Vwi-aotz-- 4.00g thinpool00 1.58 root ansiblevg00 Vwi-aotz-- 16.00g thinpool00 16.59 swap ansiblevg00 -wi-ao---- 4.00g syslogs ansiblevg00 Vwi-aotz-- 4.00g thinpool00 2.28 thinpool00 ansiblevg00 twi-aotz-- 32.93g 9.63 13.53 var ansiblevg00 Vwi-aotz-- 4.00g thinpool00 5.91 i.e. boot & swap as normal LV and all remaining FS as part of a thin_pool. All systems I build like this are working fine but when I create the autoinst.xlm file, if contains well the setup of the thin_pool LV but any ��sub�� volumes? According to opensuse doc (e.g. https://doc.opensuse.org/projects/autoyast/) it should works. So I check in the code source and easily find the sample xml file to test this figure also be able to manually update this autoinst.xml file to clone my VM :) I am attaching manip as a TIPS patch as well as y2log and original autoinst.xml -- You are receiving this mail because: You are on the CC list for the bug.

1 6