September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1170344] New: Btrfsprogs 5.6 bug: kernel booting stop at "BTRFS info" output
by bugzilla_noreply＠novell.com 07 Mar '23

07 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1170344 Bug ID: 1170344 Summary: Btrfsprogs 5.6 bug: kernel booting stop at "BTRFS info" output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: hillwoodroc(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I Updated My PC and laptop to Tumbleweed 20200417, then these two systems could not boot, and there is not any error on screen. I tried to chroot to get the dmesg log, I got many BTRFS notices at the end. I find Btrfsprogs was updated before 10 days ago in Factory. I guess this is a bug for Btrfsprogs. -- You are receiving this mail because: You are on the CC list for the bug.

2 18

[Bug 1194784] New: Yast should use RSpec verifying doubles everywhere
by bugzilla_noreply＠suse.com 06 Mar '23

06 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1194784 Bug ID: 1194784 Summary: Yast should use RSpec verifying doubles everywhere Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: lslezak(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- This should avoid bugs in the unit tests. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1201815] New: Inconsistent Bluetooth status display
by bugzilla_noreply＠suse.com 06 Mar '23

06 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1201815 Bug ID: 1201815 Summary: Inconsistent Bluetooth status display Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 860354 --> http://bugzilla.opensuse.org/attachment.cgi?id=860354&action=edit Bluetooth status in GNOME Sometimes when the Bluetooth status is "disabled", the suggested action in the GNOME menu is "Turn Off" (instead of "Turn On"). So yo have to "Turn Off" even if it's off, just to be able to see (if at all) a "Turn On" again. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1203092] New: GNU grep 3.8 egrep / grep warnings and migration to grep -E / grep -F
by bugzilla_noreply＠suse.com 06 Mar '23

06 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1203092 Bug ID: 1203092 Summary: GNU grep 3.8 egrep / grep warnings and migration to grep -E / grep -F Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: schwab(a)suse.de Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- GNU grep from 3.8 emitting warnings when invoking egrep/fgrep https://build.opensuse.org/request/show/1001097 > egrep and fgrep commands, deprecated since 2007, now warn that they are obsolescent and should be replaced by grep -E / -F We should look to eliminate egrep/fgrep from the distribution and replace all usages of egrep/fgrep with grep -E and grep -F, respectively. At the moment dropping these items breaks the grep build itself, it's all over the place. -- You are receiving this mail because: You are on the CC list for the bug.

1 33

[Bug 1197477] New: network port on monitor integrated usb hub never detects a link
by bugzilla_noreply＠suse.com 06 Mar '23

06 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1197477 Bug ID: 1197477 Summary: network port on monitor integrated usb hub never detects a link Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: josua.m(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Greetings everybody! I recently got a new Monitor on my desk with an integrated USB-3.0 Hub and an integrated RJ45 network interface. But with openSUSE Leap (both 15.3 and 15.4-Beta), the system never detects a link - as shown by the ethtool output below: sudo ethtool usb0 [sudo] Passwort f�r root: Settings for usb0: Current message level: 0x00000007 (7) drv probe link Link detected: no I have tested this with two laptops: - An ASUS UX331UN (i7-8250U) running Leap 15.3 - An ROG G14 (Ryzen 5800) running Leap 15.4 Beta I have also tested 2 other operating systems - On Windows the interface works - On Ubuntu Focal the interface works Very rarely, a link is detected for a very short time, leading to networkmanager applet indicating connection attempt for a second or two. I caputres such a case in the dmesg below: [11867.152288] usb 1-3: new high-speed USB device number 15 using xhci_hcd [11867.302285] usb 1-3: New USB device found, idVendor=0424, idProduct=2806, bcdDevice= 2.10 [11867.302292] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [11867.302295] usb 1-3: Product: USB2806 Smart Hub [11867.302298] usb 1-3: Manufacturer: Microchip [11867.304310] hub 1-3:1.0: USB hub found [11867.304698] hub 1-3:1.0: 6 ports detected [11867.432196] usb 2-4: new SuperSpeed Gen 1 USB device number 9 using xhci_hcd [11867.456449] usb 2-4: New USB device found, idVendor=0424, idProduct=5806, bcdDevice= 2.10 [11867.456457] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [11867.456462] usb 2-4: Product: USB5806 Smart Hub [11867.456465] usb 2-4: Manufacturer: Microchip [11867.457681] hub 2-4:1.0: USB hub found [11867.457710] hub 2-4:1.0: 5 ports detected [11867.600165] usb 1-3.6: new high-speed USB device number 16 using xhci_hcd [11867.704259] usb 1-3.6: New USB device found, idVendor=0424, idProduct=284c, bcdDevice= 2.00 [11867.704266] usb 1-3.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [11867.704269] usb 1-3.6: Product: Hub Feature Controller [11867.704272] usb 1-3.6: Manufacturer: Microchip [11867.708519] hid-generic 0003:0424:284C.0005: hiddev96,hidraw1: USB HID v1.10 Device [Microchip Hub Feature Controller] on usb-0000:00:14.0-3.6/input1 [11867.780407] usb 2-4.3: new SuperSpeed Gen 1 USB device number 10 using xhci_hcd [11867.800927] usb 2-4.3: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=33.00 [11867.800933] usb 2-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [11867.800936] usb 2-4.3: Product: USB 10/100/1000 LAN [11867.800939] usb 2-4.3: Manufacturer: Realtek [11867.800941] usb 2-4.3: SerialNumber: 0033000001 [11867.825408] cdc_ncm 2-4.3:2.0: MAC-Address: b0:4f:13:d7:59:ae [11867.825414] cdc_ncm 2-4.3:2.0: setting rx_max = 16384 [11867.825522] cdc_ncm 2-4.3:2.0: setting tx_max = 16384 [11867.826100] cdc_ncm 2-4.3:2.0 usb0: register 'cdc_ncm' at usb-0000:00:14.0-4.3, CDC NCM, b0:4f:13:d7:59:ae [11867.972746] usb 1-3.6: USB disconnect, device number 16 [11868.208085] usb 1-3.6: new high-speed USB device number 17 using xhci_hcd [11868.312781] usb 1-3.6: New USB device found, idVendor=0424, idProduct=2840, bcdDevice= 2.10 [11868.312788] usb 1-3.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [11868.312792] usb 1-3.6: Product: Hub Feature Controller [11868.312796] usb 1-3.6: Manufacturer: Microchip [11870.916715] cdc_ncm 2-4.3:2.0 usb0: 1000 mbit/s downlink 1000 mbit/s uplink [11871.172732] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready [11888.115889] usb 1-3.6: reset high-speed USB device number 17 using xhci_hcd [11888.221821] usb 1-3.6: device firmware changed [11888.221922] usb 1-3.6: USB disconnect, device number 17 [11888.303624] usb 1-3.6: new high-speed USB device number 18 using xhci_hcd [11888.407663] usb 1-3.6: New USB device found, idVendor=0424, idProduct=284c, bcdDevice= 2.00 [11888.407670] usb 1-3.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [11888.407674] usb 1-3.6: Product: Hub Feature Controller [11888.407677] usb 1-3.6: Manufacturer: Microchip [11888.411497] hid-generic 0003:0424:284C.0006: hiddev96,hidraw1: USB HID v1.10 Device [Microchip Hub Feature Controller] on usb-0000:00:14.0-3.6/input1 Also adding an lsusb: Bus 002 Device 010: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 009: ID 0424:5806 Microchip Technology, Inc. (formerly SMSC) USB5806 Smart Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 13d3:5a09 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 018: ID 0424:284c Microchip Technology, Inc. (formerly SMSC) Hub Feature Controller Bus 001 Device 015: ID 0424:2806 Microchip Technology, Inc. (formerly SMSC) USB2806 Smart Hub Bus 001 Device 006: ID 0781:55a1 SanDisk Corp. Cruzer Spark Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I'd be happy to do experiments if somebody can point me in a meaningful direction on how to approach this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1166296] New: Return of Yast2-fonts
by bugzilla_noreply＠novell.com 04 Mar '23

04 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1166296 Bug ID: 1166296 Summary: Return of Yast2-fonts Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: cornelis(a)solcon.nl QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- As yast2-fonts is back in TW again after a brief hiatus, would it be possible to add it again to Leap 15.2? -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1200235] New: Multiple X sessions not possible with Plasma (Wayland)
by bugzilla_noreply＠suse.com 04 Mar '23

04 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1200235 Bug ID: 1200235 Summary: Multiple X sessions not possible with Plasma (Wayland) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: simplyschinne(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- *steps to reproduce* (1) log in user1 with 'Desktop Session: Plasma (Wayland)' (2) lock screen (3) on lock screen, chose 'switch user' (4) log in user2 with 'Desktop Session: Plasma (Wayland)' (5) press ctrl-alt-f7 *expected behaviour* lock screen is displayed with prompt for user1's password, user1's session can be continued after keying in password *observed behaviour* lock screen is displayed but no key stroke, no mouse click is accepted. PC has to be rebooted. *notes* (1) Bug reproducible 100% with Desktop Session Plasma (Wayland) (2) Bug NOT reproducible with Desktop Session Plasma (X11) *environment* qqq@linux ~$ uname -a Linux linux.fritz.box 5.18.1-1-default #1 SMP PREEMPT_DYNAMIC Mon May 30 07:49:01 UTC 2022 (d00e88d) x86_64 x86_64 x86_64 GNU/Linux qqq@linux ~$ cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20220603" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20220603" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20220603" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1193407] New: autostart tuned daemon not working
by bugzilla_noreply＠suse.com 03 Mar '23

03 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1193407 Bug ID: 1193407 Summary: autostart tuned daemon not working 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: dead_mozay(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- tuned.service no longer starts with the system, manual launch of the unit without errors. No errors were found in any of the possible logs, journalctl - no error /var/log/tuned/tuned.log - no error the unit simply does not start with the system the error is reproducible on all PCs -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1173313] New: [aarch64] jeos qcow2 image: Root device not found during virt-install boot
by bugzilla_noreply＠suse.com 03 Mar '23

03 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1173313 Bug ID: 1173313 Summary: [aarch64] jeos qcow2 image: Root device not found during virt-install boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: aarch64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Cloud:Images Assignee: public-cloud-maintainers(a)suse.de Reporter: rrichter(a)marvell.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0 Build Identifier: Booting today's openSUSE Leap 15.2 qcow2 image with virt-inst fails: # virsh net-start default # virt-install --transient --name opensuse --import --memory 16384 --disk /srv/vm/opensuse/openSUSE-Leap-15.2-ARM-JeOS-efi.aarch64-2020.06.16-Build1.8.qcow2 ... Loading Linux 5.3.18-lp152.18-default ... ... Welcome to openSUSE Leap 15.2 dracut-049.1+suse.144.ge0eaf296-lp152.1.1 (Initramfs)! ... [ OK ] Reached target Basic System. [ *] A start job is running for dev-disk…75ec6bc9c9.device (46s / no limit) This runs forever. Image from: https://download.opensuse.org/ports/aarch64/distribution/leap/15.2/applianc… Using a customized kernel and initrd made the image boot: + virt-install --transient --name 5.7.0-virt-01309-g9046fbbe2919 --boot 'uefi,kernel=/boot/Image-5.7.0-virt-01309-g9046fbbe2919,initrd=/boot/initrd-5.7.0-virt-01309-g9046fbbe2919,kernel_args=root=/dev/sda3 ro console=ttyS0,115200n8 no_timer_check net.ifnames=0 crashkernel=auto rd.shell rd.debug log_buf_len=1M' --memory 16384 --disk /srv/vm/opensuse/openSUSE-Leap-15.2-ARM-JeOS-efi.aarch64-2020.06.16-Build1.8.qcow2 After applying dracut in the guest the original image could be booted too (with the above command line): # dracut -f /boot/initrd-5.3.18-lp152.18-default 5.3.18-lp152.18-default Though, during boot there is a long timeout of about 15 mins (which are not seen with the custom kernel, time varies): [ 915.761207] cloud-init[533]: Cloud-init v. 19.4 running 'init-local' at Wed, 24 Jun 2020 13:12:32 +0000. Up 900.51 seconds. Reproducible: Always Steps to Reproduce: See above. Actual Results: Root device is not found, no root fs. Systemd start job hangs forever: [ *] A start job is running for dev-disk…75ec6bc9c9.device (46s / no limit) Expected Results: System is booted to the prompt: Welcome to openSUSE Leap 15.2 - Kernel 5.3.18-lp152.18-default (ttyAMA0). sbr2s-27 login: Details on the host (Marvell CN99xx): sbr2s-27:~ # cat /etc/os-release NAME="SLES" VERSION="15-SP1" VERSION_ID="15.1" PRETTY_NAME="SUSE Linux Enterprise Server 15 SP1" ID="sles" ID_LIKE="suse" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:suse:sles:15:sp1" sbr2s-27:~ # uname -a Linux sbr2s-27 5.3.18-50.g39d1ea9-default #1 SMP Sun Apr 5 19:41:26 UTC 2020 (39d1ea9) aarch64 aarch64 aarch64 GNU/Linux sbr2s-27:~ # dmidecode -t 0 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 3.1.1 present. Handle 0x0000, DMI type 0, 26 bytes BIOS Information Vendor: EDK II Version: 0ACKL029 Release Date: 02/21/2020 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 64 MB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed ACPI is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 7.4 sbr2s-27:~ # dmidecode -t 1 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 3.1.1 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: To be filled by O.E.M. Product Name: Saber Version: 1.0 Serial Number: To be filled by O.E.M. UUID: 6b7bd980-bfde-1000-03f5-e0d55e60f6d4 Wake-up Type: Power Switch SKU Number: SABER SKU Family: CN99XX Systemd log showing boot timing: Jun 24 12:57:39 sbr2s-27 systemd[1]: Started Apply settings from /etc/sysconfig/keyboard. Jun 24 13:07:32 sbr2s-27 systemd[1]: Started Daily Cleanup of Snapper Snapshots. Jun 24 13:07:32 sbr2s-27 dbus-daemon[527]: [system] Activating service name='org.opensuse.Snapper' requested by ':1.2' (uid=0 pid=589 comm="/usr/lib/snapper/systemd-helper --cleanup ") (using servicehelper) Jun 24 13:07:32 sbr2s-27 dbus-daemon[527]: [system] Successfully activated service 'org.opensuse.Snapper' Jun 24 13:07:32 sbr2s-27 systemd-helper[589]: running number cleanup for 'root'. Jun 24 13:07:32 sbr2s-27 systemd-helper[589]: running timeline cleanup for 'root'. Jun 24 13:07:32 sbr2s-27 systemd-helper[589]: running empty-pre-post cleanup for 'root'. Jun 24 13:12:32 sbr2s-27 kernel: random: crng init done Jun 24 13:12:32 sbr2s-27 kernel: random: 7 urandom warning(s) missed due to ratelimiting Jun 24 13:12:32 sbr2s-27 dhclient[600]: Internet Systems Consortium DHCP Client 4.3.6-P1 Jun 24 13:12:32 sbr2s-27 dhclient[600]: Copyright 2004-2018 Internet Systems Consortium. Jun 24 13:12:32 sbr2s-27 dhclient[600]: All rights reserved. Jun 24 13:12:32 sbr2s-27 dhclient[600]: For info, please visit https://www.isc.org/software/dhcp/ Jun 24 13:12:32 sbr2s-27 dhclient[600]: Jun 24 13:12:32 sbr2s-27 dhclient[600]: Listening on LPF/eth0/52:54:00:d7:71:f6 Jun 24 13:12:32 sbr2s-27 dhclient[600]: Sending on LPF/eth0/52:54:00:d7:71:f6 Jun 24 13:12:32 sbr2s-27 dhclient[600]: Sending on Socket/fallback Jun 24 13:12:32 sbr2s-27 dhclient[600]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0x371dbcf6) Jun 24 13:12:32 sbr2s-27 dhclient[600]: DHCPOFFER from 192.168.122.1 Jun 24 13:12:32 sbr2s-27 kernel: NET: Registered protocol family 17 Jun 24 13:12:37 sbr2s-27 dhclient[600]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0x371dbcf6) Jun 24 13:12:37 sbr2s-27 dhclient[600]: DHCPACK from 192.168.122.1 (xid=0x371dbcf6) Jun 24 13:12:37 sbr2s-27 dhclient[600]: bound to 192.168.122.196 -- renewal in 1631 seconds. Jun 24 13:12:47 sbr2s-27 cloud-init[533]: Cloud-init v. 19.4 running 'init-local' at Wed, 24 Jun 2020 13:12:32 +0000. Up 900.51 seconds. Jun 24 13:12:47 sbr2s-27 cloud-init[533]: 2020-06-24 13:12:47,783 - util.py[WARNING]: No active metadata service found Jun 24 13:12:47 sbr2s-27 systemd[1]: Started Initial cloud-init job (pre-networking). Jun 24 13:12:47 sbr2s-27 systemd[1]: Reached target Network (Pre). Jun 24 13:12:47 sbr2s-27 systemd[1]: Starting wicked AutoIPv4 supplicant service... Jun 24 13:12:47 sbr2s-27 systemd[1]: Starting wicked DHCPv4 supplicant service... Jun 24 13:12:47 sbr2s-27 systemd[1]: Starting wicked DHCPv6 supplicant service... Jun 24 13:12:48 sbr2s-27 systemd[1]: Started wicked DHCPv6 supplicant service. Jun 24 13:12:48 sbr2s-27 systemd[1]: Started wicked AutoIPv4 supplicant service. Jun 24 13:12:48 sbr2s-27 systemd[1]: Started wicked DHCPv4 supplicant service. Jun 24 13:12:48 sbr2s-27 systemd[1]: Starting wicked network management service daemon... Jun 24 13:12:48 sbr2s-27 systemd[1]: Started wicked network management service daemon. Jun 24 13:12:48 sbr2s-27 systemd[1]: Starting wicked network nanny service... Jun 24 13:12:48 sbr2s-27 systemd[1]: Started wicked network nanny service. Jun 24 13:12:48 sbr2s-27 systemd[1]: Starting wicked managed network interfaces... Jun 24 13:12:48 sbr2s-27 wickedd-dhcp4[622]: eth0: Request to acquire DHCPv4 lease with UUID 5051f35e-40a5-0300-7002-000004000000 Jun 24 13:12:48 sbr2s-27 wickedd-dhcp4[622]: eth0: Committed DHCPv4 lease with address 192.168.122.34 (lease time 3600 sec, renew in 1800 sec, rebind in 3150 sec) Jun 24 13:12:53 sbr2s-27 wicked[628]: lo up Jun 24 13:12:53 sbr2s-27 wicked[628]: eth0 up Jun 24 13:12:53 sbr2s-27 systemd[1]: Started wicked managed network interfaces. Jun 24 13:12:53 sbr2s-27 systemd[1]: Starting Initial cloud-init job (metadata service crawler)... Jun 24 13:12:53 sbr2s-27 systemd[1]: Reached target Network. Jun 24 13:12:53 sbr2s-27 systemd[1]: Starting NTP client/server... Jun 24 13:12:53 sbr2s-27 chronyd[1045]: chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SECHASH -SIGND +ASYNCDNS +IPV6 -DEBUG) Jun 24 13:12:53 sbr2s-27 chronyd[1045]: Frequency -104.991 +/- 2.220 ppm read from /var/lib/chrony/drift Jun 24 13:12:53 sbr2s-27 systemd[1]: Started NTP client/server. Jun 24 13:12:53 sbr2s-27 systemd[1]: Reached target System Time Synchronized. Jun 24 13:12:53 sbr2s-27 systemd[1]: Started Discard unused blocks once a week. Jun 24 13:12:53 sbr2s-27 systemd[1]: Started Backup of /etc/sysconfig. Jun 24 13:12:53 sbr2s-27 systemd[1]: Started Check if mainboard battery is Ok. Jun 24 13:12:53 sbr2s-27 systemd[1]: Started Backup of RPM database. Jun 24 13:12:53 sbr2s-27 systemd[1]: Starting Cleanup of Temporary Directories... Jun 24 13:12:53 sbr2s-27 systemd[1]: Started Daily rotation of log files. Jun 24 13:12:53 sbr2s-27 systemd[1]: Started Timeline of Snapper Snapshots. Jun 24 13:12:53 sbr2s-27 systemd[1]: Reached target Timers. Jun 24 13:12:53 sbr2s-27 systemd-tmpfiles[1071]: [/usr/lib/tmpfiles.d/tmp.conf:13] Duplicate line for path "/var/tmp", ignoring. Jun 24 13:12:53 sbr2s-27 systemd-tmpfiles[1071]: [/usr/lib/tmpfiles.d/var.conf:21] Duplicate line for path "/var/lib", ignoring. Jun 24 13:12:53 sbr2s-27 systemd-tmpfiles[1071]: [/usr/lib/tmpfiles.d/var.conf:23] Duplicate line for path "/var/spool", ignoring. Jun 24 13:12:54 sbr2s-27 systemd[1]: Started Cleanup of Temporary Directories. Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: Cloud-init v. 19.4 running 'init' at Wed, 24 Jun 2020 13:12:54 +0000. Up 922.48 seconds. Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: ++++++++++++++++++++++++++++++++++++++Net device info++++++++++++++++++++++++++++++++++++++ Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: +--------+------+----------------------------+---------------+--------+-------------------+ Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: | Device | Up | Address | Mask | Scope | Hw-Address | Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: +--------+------+----------------------------+---------------+--------+-------------------+ Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: | eth0 | True | 192.168.122.34 | 255.255.255.0 | global | 52:54:00:d7:71:f6 | Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: | eth0 | True | fe80::5054:ff:fed7:71f6/64 | . | link | 52:54:00:d7:71:f6 | Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | host | . | Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: | lo | True | ::1/128 | . | host | . | Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: +--------+------+----------------------------+---------------+--------+-------------------+ Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: +++++++++++++++++++++++++++++++Route IPv4 info+++++++++++++++++++++++++++++++ Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: +-------+---------------+---------------+---------------+-----------+-------+ Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags | Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: +-------+---------------+---------------+---------------+-----------+-------+ Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: | 0 | 0.0.0.0 | 192.168.122.1 | 0.0.0.0 | eth0 | UG | Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: | 1 | 192.168.122.0 | 0.0.0.0 | 255.255.255.0 | eth0 | U | Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: +-------+---------------+---------------+---------------+-----------+-------+ Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: +++++++++++++++++++Route IPv6 info+++++++++++++++++++ Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: +-------+-------------+---------+-----------+-------+ Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: | Route | Destination | Gateway | Interface | Flags | Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: +-------+-------------+---------+-----------+-------+ Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: | 1 | fe80::/64 | :: | eth0 | U | Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: | 3 | local | :: | eth0 | U | Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: | 4 | ff00::/8 | :: | eth0 | U | Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: ci-info: +-------+-------------+---------+-----------+-------+ Jun 24 13:13:04 sbr2s-27 cloud-init[1042]: 2020-06-24 13:13:04,683 - util.py[WARNING]: No active metadata service found Jun 24 13:13:05 sbr2s-27 kernel: BTRFS info (device sda3): new size for /dev/sda3 is 1289728000 Jun 24 13:13:05 sbr2s-27 systemd[1]: Started Initial cloud-init job (metadata service crawler). Jun 24 13:13:05 sbr2s-27 systemd[1]: Starting Permit User Sessions... Jun 24 13:13:05 sbr2s-27 systemd[1]: Reached target Network is Online. Jun 24 13:13:05 sbr2s-27 systemd[1]: Starting OpenSSH Daemon... Jun 24 13:13:05 sbr2s-27 systemd[1]: Reached target Cloud-config availability. Jun 24 13:13:05 sbr2s-27 sshd-gen-keys-start[1118]: Checking for missing server keys in /etc/ssh Jun 24 13:13:05 sbr2s-27 systemd[1]: Starting Apply the settings specified in cloud-config... Jun 24 13:13:05 sbr2s-27 systemd[1]: Started Permit User Sessions. Jun 24 13:13:05 sbr2s-27 sshd[1122]: Server listening on 0.0.0.0 port 22. Jun 24 13:13:05 sbr2s-27 sshd[1122]: Server listening on :: port 22. Jun 24 13:13:05 sbr2s-27 systemd[1]: Started OpenSSH Daemon. Jun 24 13:13:05 sbr2s-27 systemd[1]: Started Getty on tty1. Jun 24 13:13:05 sbr2s-27 systemd[1]: Started Serial Getty on ttyAMA0. Jun 24 13:13:05 sbr2s-27 systemd[1]: Reached target Login Prompts. Jun 24 13:13:05 sbr2s-27 systemd[1]: Reached target Multi-User System. Jun 24 13:13:05 sbr2s-27 systemd[1]: Reached target Graphical Interface. Jun 24 13:13:05 sbr2s-27 systemd[1]: Starting Update UTMP about System Runlevel Changes... Jun 24 13:13:05 sbr2s-27 systemd[1]: Started Update UTMP about System Runlevel Changes. Jun 24 13:13:06 sbr2s-27 cloud-init[1120]: Cloud-init v. 19.4 running 'modules:config' at Wed, 24 Jun 2020 13:13:06 +0000. Up 933.97 seconds. Jun 24 13:13:06 sbr2s-27 systemd[1]: Started Apply the settings specified in cloud-config. Jun 24 13:13:06 sbr2s-27 systemd[1]: Starting Execute cloud user/final scripts... Jun 24 13:13:06 sbr2s-27 cloud-init[1133]: Cloud-init v. 19.4 running 'modules:final' at Wed, 24 Jun 2020 13:13:06 +0000. Up 934.77 seconds. Jun 24 13:13:06 sbr2s-27 cloud-init[1133]: Cloud-init v. 19.4 finished at Wed, 24 Jun 2020 13:13:06 +0000. Datasource DataSourceNone. Up 934.87 seconds Jun 24 13:13:06 sbr2s-27 cloud-init[1133]: 2020-06-24 13:13:06,909 - cc_final_message.py[WARNING]: Used fallback datasource Jun 24 13:13:06 sbr2s-27 systemd[1]: Started Execute cloud user/final scripts. Jun 24 13:13:06 sbr2s-27 systemd[1]: Reached target Cloud-init target. Jun 24 13:13:06 sbr2s-27 systemd[1]: Startup finished in 1.505s (kernel) + 4.647s (initrd) + 15min 28.807s (userspace) = 15min 34.961s. Jun 24 13:13:41 sbr2s-27 sshd[1142]: Accepted keyboard-interactive/pam for root from 192.168.122.1 port 42104 ssh2 Jun 24 13:13:41 sbr2s-27 systemd-logind[531]: New session 1 of user root. Jun 24 13:13:41 sbr2s-27 systemd[1]: Created slice User Slice of UID 0. Jun 24 13:13:41 sbr2s-27 systemd[1]: Starting User Manager for UID 0... Jun 24 13:13:41 sbr2s-27 systemd[1]: Started Session 1 of user root. Jun 24 13:13:41 sbr2s-27 systemd[1145]: pam_unix(systemd-user:session): session opened for user root by (uid=0) Jun 24 13:13:41 sbr2s-27 systemd[1145]: Reached target Paths. Jun 24 13:13:41 sbr2s-27 systemd[1145]: Reached target Timers. Jun 24 13:13:41 sbr2s-27 systemd[1145]: Starting D-Bus User Message Bus Socket. Jun 24 13:13:41 sbr2s-27 systemd[1145]: Listening on D-Bus User Message Bus Socket. Jun 24 13:13:41 sbr2s-27 systemd[1145]: Reached target Sockets. Jun 24 13:13:41 sbr2s-27 systemd[1145]: Reached target Basic System. Jun 24 13:13:41 sbr2s-27 systemd[1]: Started User Manager for UID 0. Jun 24 13:13:41 sbr2s-27 sshd[1142]: pam_unix(sshd:session): session opened for user root by (uid=0) Jun 24 13:13:41 sbr2s-27 systemd[1145]: Reached target Default. Jun 24 13:13:41 sbr2s-27 systemd[1145]: Startup finished in 52ms. Additional issue seen: [FAILED] Failed to start Load Kernel Modules. See 'systemctl status systemd-modules-load.service' for details. This is due to multipath-tools package: sbr2s-27:~ # systemctl status systemd-modules-load ● systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2020-06-24 12:57:39 UTC; 24min ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 480 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) Main PID: 480 (code=exited, status=1/FAILURE) Jun 24 12:57:39 sbr2s-27 systemd[1]: Starting Load Kernel Modules... Jun 24 12:57:39 sbr2s-27 systemd-modules-load[480]: Failed to find module 'scsi_dh_alua' Jun 24 12:57:39 sbr2s-27 systemd-modules-load[480]: Failed to find module 'scsi_dh_emc' Jun 24 12:57:39 sbr2s-27 systemd-modules-load[480]: Failed to find module 'scsi_dh_rdac' Jun 24 12:57:39 sbr2s-27 systemd-modules-load[480]: Failed to find module 'dm-multipath' Jun 24 12:57:39 sbr2s-27 systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE Jun 24 12:57:39 sbr2s-27 systemd[1]: Failed to start Load Kernel Modules. Jun 24 12:57:39 sbr2s-27 systemd[1]: systemd-modules-load.service: Unit entered failed state. Jun 24 12:57:39 sbr2s-27 systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. sbr2s-27:~ # cat /usr/lib/modules-load.d/multipath.conf # Load device-handler and multipath module at boot scsi_dh_alua scsi_dh_emc scsi_dh_rdac dm-multipath sbr2s-27:~ # rpm -qf /usr/lib/modules-load.d/multipath.conf multipath-tools-0.8.2+18.9ff73e7-lp152.2.1.aarch64 sbr2s-27:~ # find /lib/modules/ -name '*dm-multipath*' It does not have impact to the boot issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1203842] New: KDE Network Manager and openconnect
by bugzilla_noreply＠suse.com 03 Mar '23

03 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1203842 Bug ID: 1203842 Summary: KDE Network Manager and openconnect Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal 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: --- Can not connect using the PAN Global Protect (openconnect) with KDE Network Manager. I get an error saying: The IP config of the VPN connection ****, was invalid. In the logs I get operation not permitted. I've tried to manually connect from the cli as a normal user and I get the same. Connecting as root works. So I guess for some reason we do not allow bringing up the tunnel as normal users? Is this to be consider a bug, or it will stay like this? -------------------- ESP session established with server ESP tunnel connected; exiting HTTPS mainloop. Configured as 192.168.222.12, with SSL disconnected and ESP established Session authentication will expire at Wed Sep 28 23:14:32 2022 Failed to bind local tun device (TUNSETIFF): Operation not permitted To configure local networking, openconnect must be running as root See https://www.infradead.org/openconnect/nonroot.html for more information Set up tun device failed POST https://domain.com/ssl-vpn/logout.esp SSL negotiation with domain.com Connected to HTTPS on domain.com with ciphersuite (TLS1.2)-(ECDHE-SECP256R1)-(RSA-SHA256)-(AES-256-GCM) Logout successful. Unrecoverable I/O error; exiting. -- You are receiving this mail because: You are on the CC list for the bug.

1 5