February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1188980] New: Multiple pool entries in chrony configuration at install
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1188980 Bug ID: 1188980 Summary: Multiple pool entries in chrony configuration at install Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: andrew.elwell(a)pawsey.org.au QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- A fresh installation of a openSUSE leap (15.3) as a server resulted in chrony tracking 18 time sources localhost:~ # chronyc sources | head -n 1 210 Number of sources = 18 These are coming from two places - The first (expected) is via the chrony-pool-openSUSE localhost:~ # cat /etc/chrony.d/pool.conf pool 2.opensuse.pool.ntp.org iburst localhost:~ # rpm -qf /etc/chrony.d/pool.conf chrony-pool-openSUSE-3.2-9.24.2.noarch localhost:~ # however it looks like something at install time alters the standard chrony.conf localhost:~ # rpm -V chrony S.5....T. c /etc/chrony.conf and adds multiple "pool" entries in a manner which looks like something that originally used "server" entries localhost:~ # grep ^pool /etc/chrony.conf pool 0.suse.pool.ntp.org iburst pool 1.suse.pool.ntp.org iburst pool 2.suse.pool.ntp.org iburst pool 3.suse.pool.ntp.org iburst localhost:~ # I think this could be related to #1180689 and #1172517 - but I can't work out what takes the server list generated by https://github.com/yast/yast-network/blob/master/src/lib/y2network/ntp_serv… and adds them to the config. IMHO, the solution is not to add any pool entries into chrony.conf if already using the include /etc/chrony.d/*.conf method. If they _do_ need to be added, one pool entry should be enough. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1208621] New: xfreerdp unable to connect due openssl upgrade
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208621 Bug ID: 1208621 Summary: xfreerdp unable to connect due openssl upgrade Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: miguel(a)rozsas.eng.br QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After openssl update from v1 to v3, xfreerdp is unable to connect where it was able before the update. 27840:27888] [ERROR][com.freerdp.core] - transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED [0x00020008] On a computer NOT updated yet, with openssl v1 in place, xfreerdp can connect to the remote host using the same parameters (xfreerdp /w:1900 /h:1000 /u:'obfuscated' /p:'obfuscated' /v:remotehost +clipboard +drives) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208589] VUL-0: chromium: multiple security issues fixed in 110.0.5481.177
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208589 http://bugzilla.opensuse.org/show_bug.cgi?id=1208589#c3 --- Comment #3 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1208589) was mentioned in https://build.opensuse.org/request/show/1067445 Backports:SLE-15-SP5 / chromium -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207562] U-Boot: Raspberry Pi 4 booting from USB stopped booting
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207562 https://bugzilla.suse.com/show_bug.cgi?id=1207562#c49 --- Comment #49 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Darren Davis from comment #48) > (In reply to Guillaume GARDET from comment #47) > > This should be fixed with Tumbleweed snapshot 20220221. > > > > Please re-open, if not. > > 2022? > > I assume you meant 20230221 Yes, indeed! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207944] intel_iommu=on Is not work on Alderlake
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207944 https://bugzilla.suse.com/show_bug.cgi?id=1207944#c6 Michiya Hagimoto <kokeko(a)mac.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Michiya Hagimoto <kokeko(a)mac.com> --- (In reply to Dario Faggioli from comment #5) > Ok... Which means we can close the bug? Or is there anything we need to > further test and/or try to fix? Yes, my problem is solved, thanks for support. in futuer, not require force_probe option? i915.force_probe=46a6 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207562] U-Boot: Raspberry Pi 4 booting from USB stopped booting
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207562 https://bugzilla.suse.com/show_bug.cgi?id=1207562#c48 --- Comment #48 from Darren Davis <ddavis(a)suse.com> --- (In reply to Guillaume GARDET from comment #47) > This should be fixed with Tumbleweed snapshot 20220221. > > Please re-open, if not. 2022? I assume you meant 20230221 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208616] Unable to boot on encrypted RAID 1 Btrfs install
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208616 https://bugzilla.suse.com/show_bug.cgi?id=1208616#c4 --- Comment #4 from Kelvin Hu <hukelvin99(a)gmail.com> --- Another thing to note, I didn't change any of the default Btrfs settings during the installation so I'm actually not sure if it's RAID 1, I'll double check within the next 24 hours and post an update (and corresponding logs) then. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208616] New: Unable to boot on encrypted RAID 1 Btrfs install
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208616 Bug ID: 1208616 Summary: Unable to boot on encrypted RAID 1 Btrfs install Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: hukelvin99(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 865089 --> http://bugzilla.opensuse.org/attachment.cgi?id=865089&action=edit The looping errors outputted Hi all, as in the title, I've successfully installed but failed to boot on an encrypted Btrfs RAID 1 setup. I've also tested this on the KDE variant which yields the same outcome. Current hardware: - Gigabyte Aorus 5 KE4 laptop with two deviations - Two NVMe SSDs, a WD_BLACK SN770 1TB and a Samsung MZVL21T0HCLR-00B00 (OEM PM9A1) - 64GiB (2x 32GiB) DDR4. Steps I performed during setup: - On partitioning, went through the guided proposal with disk encryption enabled. - After that, performed an expert partitioning with the current proposal. - Created a new partition on second drive with max size, role set to raw volume, and drive encrypted. - Under the Btrfs tab in the sidebar, I added the aforementioned encrypted second drive to the one created as part of the guided setup via the used devices tab. - Under Security, enabled firewall and disabled SSH service Steps performed during boot: - Entered the password when prompted for both drives - Selected default boot under Grub. - Error loops for a period of time. Afterwards the system reboots. Additional note: - The following attached images were from a Qemu/KVM (Proxmox specifically) VM, but the same behaviour was observed on a bare metal install. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1202820] kexec --load on UEFI with secure boot
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1202820 https://bugzilla.suse.com/show_bug.cgi?id=1202820#c2 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #2 from Michal Suchanek <msuchanek(a)suse.com> --- Sounds reasonable. kexec-bootloader is shipped together with kexec so no need to deal with kexec versions not supporting -a. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208616] Unable to boot on encrypted RAID 1 Btrfs install
by bugzilla_noreply＠suse.com 23 Feb '23

23 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208616 https://bugzilla.suse.com/show_bug.cgi?id=1208616#c2 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor(a)suse.com --- Comment #2 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- Although the steps are well described, it would be even better to have installation logs. They describe the storage (partitioning, encryption, etc.) in better detail. https://en.opensuse.org/openSUSE:Report_a_YaST_bug -- You are receiving this mail because: You are on the CC list for the bug.

1 0