March 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1210018] New: Dependency for the package samba-ad-dc not fully enumerated in ADDC package
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1210018 Bug ID: 1210018 Summary: Dependency for the package samba-ad-dc not fully enumerated in ADDC package Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Samba Assignee: samba-maintainers(a)SuSE.de Reporter: donald.vosburg(a)suse.com QA Contact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- samba-ad-dc package needs samba-winbind in order to start, yet this package is not installed as a dependency by default. In addition, after starting, errors are produced in the service immediately: /usr/sbin/samba_dnsupdate: ModuleNotFoundError: No module named 'dns' This is resolved with another missing package, python3-dnspython. So - if we add as dependencies for sanba-ad-dc these two packages, both issues will be resolved. samba-windbind python3-dnspython -- You are receiving this mail because: You are on the CC list for the bug.

1 0

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

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209725 https://bugzilla.suse.com/show_bug.cgi?id=1209725#c17 --- Comment #17 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- Preliminary fix with regression unit test: https://github.com/yast/yast-storage-ng/pull/1327 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207243] New: Update from 0800 UTC 230118 does not complete startup, kernel 6.1.4
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207243 Bug ID: 1207243 Summary: Update from 0800 UTC 230118 does not complete startup, kernel 6.1.4 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Maintenance Assignee: screening-team-bugs(a)suse.de Reporter: chris(a)twoten.is QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Both in normal and rescue mode the laptop (Dell XPS 15 7590) does not complete startup process. In normal mode there's no feedback visible, screen goes black, fan runs periodically but no apparent response from OS e.g. cannot switch tty, caps lock doesn't activate. In rescue mode the fail is similar but the screen remains visible; last message was tagged T390 and referenced nvme0 (system SSD). Failed boots appear to log possibly related lines: 2023-01-18T08:11:40.832204+00:00 linux-nyw8 kernel: [760085.543888][T12422] block nvme0n1: No UUID available providing old NGUID 2023-01-18T08:11:40.856207+00:00 linux-nyw8 kernel: [760085.568170][T12438] block nvme0n1: No UUID available providing old NGUID 2023-01-18T08:11:40.884204+00:00 linux-nyw8 kernel: [760085.594053][T12455] block nvme0n1: No UUID available providing old NGUID 2023-01-18T08:11:40.908217+00:00 linux-nyw8 kernel: [760085.617856][T12471] block nvme0n1: No UUID available providing old NGUID Booting to last used kernel (6.0.12) restores operation. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

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

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209725 https://bugzilla.suse.com/show_bug.cgi?id=1209725#c16 --- Comment #16 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- (In reply to Ancor Gonzalez Sosa from comment #15) > > If it would use "vg.all_lvm_lvs" instead of the current "vg.lvm_lvs" Yes. I can confirm that introducing that change, it produces exactly the wanted result. -- 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#c29 Brian Murrell <brian(a)interlinx.bc.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brian(a)interlinx.bc.ca --- Comment #29 from Brian Murrell <brian(a)interlinx.bc.ca> --- How long does it typically take for these updates to show up in repos on mirrors? I am not yet seeing the 5.14.21-150400.24.55.1 update present there. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

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

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209725 https://bugzilla.suse.com/show_bug.cgi?id=1209725#c15 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(igonzalezsosa@sus | |e.com) | --- Comment #15 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- (In reply to Stefan Hundhammer from comment #14) > > That much is clear. But the question was: Does the cloning part do that > extra iteration over each LVM LV because it might have sub-elements itself; > which only happens in the case of a thin pool LV? No. And that's exactly the root of the problem. Here it only iterates through the first level https://github.com/yast/yast-storage-ng/blob/master/src/lib/y2storage/autoi… If it would use "vg.all_lvm_lvs" instead of the current "vg.lvm_lvs", then it would cover the thin volumes as well and it would likely work. I can write a unit test to verify that. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1209954] New: Installation via "virt-install --graphics none ..." renders the system unbootable
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209954 Bug ID: 1209954 Summary: Installation via "virt-install --graphics none ..." renders the system unbootable Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: opensuse_buildservice(a)ojkastl.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi all, when I install openSUSE Leap 15.4 or openSUSE Leap 15.5 using virt-install, as soon as I use the "--graphics none" parameter the system does not boot after the installation. 1. The system reboots, shows the GRUB menu (both when using virt-viewer or virt-manager or when using virsh console). 2. The default entry is selected. 3. "Loading Linux 5.14.21-150400.22-default ..." is being shown (which is the echo command before loading the kernel in grub.cfg) 4. The GRUB boot menu is shown again Steps 2/3/4 can be repeated endlessly. I have tested with and without Autoyast files. I have tested with 15.4 and 15.5. I have tested both with a NET-install ISO image and with "--location=...". The change in the virt-install invocation between a working and a non-working installation is that "--graphics none" is added. The manpage for libvirt says that --graphics only influences the way the VM is being accessed, but does not change any virtual hardware. I have not yet found out, what exactly goes wrong. The full invocation: ``` virt-install \ --name=somename \ --disk path=somename.qcow2,bus=virtio,format=qcow2 \ --network=bridge:virbr0,model=e1000 \ --ram=1024 \ --os-variant=sle15sp4 \ --location="http://download.opensuse.org/pub/opensuse/distribution/leap/15.4/repo/oss" \ --accelerate ``` Host system is openSUSE Tumbleweed. Libvirt packages: libvirt-9.1.0-2.2.x86_64 libvirt-client-9.1.0-2.2.x86_64 libvirt-daemon-9.1.0-2.2.x86_64 libvirt-daemon-common-9.1.0-2.2.x86_64 libvirt-daemon-config-network-9.1.0-2.2.x86_64 libvirt-daemon-config-nwfilter-9.1.0-2.2.x86_64 libvirt-daemon-driver-interface-9.1.0-2.2.x86_64 libvirt-daemon-driver-libxl-9.1.0-2.2.x86_64 libvirt-daemon-driver-lxc-9.1.0-2.2.x86_64 libvirt-daemon-driver-network-9.1.0-2.2.x86_64 libvirt-daemon-driver-nodedev-9.1.0-2.2.x86_64 libvirt-daemon-driver-nwfilter-9.1.0-2.2.x86_64 libvirt-daemon-driver-qemu-9.1.0-2.2.x86_64 libvirt-daemon-driver-secret-9.1.0-2.2.x86_64 libvirt-daemon-driver-storage-9.1.0-2.2.x86_64 libvirt-daemon-driver-storage-core-9.1.0-2.2.x86_64 libvirt-daemon-driver-storage-disk-9.1.0-2.2.x86_64 libvirt-daemon-driver-storage-gluster-9.1.0-2.2.x86_64 libvirt-daemon-driver-storage-iscsi-9.1.0-2.2.x86_64 libvirt-daemon-driver-storage-iscsi-direct-9.1.0-2.2.x86_64 libvirt-daemon-driver-storage-logical-9.1.0-2.2.x86_64 libvirt-daemon-driver-storage-mpath-9.1.0-2.2.x86_64 libvirt-daemon-driver-storage-rbd-9.1.0-2.2.x86_64 libvirt-daemon-driver-storage-scsi-9.1.0-2.2.x86_64 libvirt-daemon-lock-9.1.0-2.2.x86_64 libvirt-daemon-log-9.1.0-2.2.x86_64 libvirt-daemon-plugin-lockd-9.1.0-2.2.x86_64 libvirt-daemon-proxy-9.1.0-2.2.x86_64 libvirt-glib-1_0-0-4.0.0-1.10.x86_64 libvirt-libs-9.1.0-2.2.x86_64 Kind Regards, Johannes -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1209741] pam session keyring creating during KDE GUI login not available to cifscreds
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209741 https://bugzilla.suse.com/show_bug.cgi?id=1209741#c18 --- Comment #18 from Franck Bui <fbui(a)suse.com> --- (In reply to Fabian Vogt from comment #17) > Not at all. cifscreds is so far the only application I've seen that actually > uses it in a DE context. ecryptfs-utils makes use of the kernel key infra. IIRC it doesn't make any use of the session keyring. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1209741] pam session keyring creating during KDE GUI login not available to cifscreds
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209741 https://bugzilla.suse.com/show_bug.cgi?id=1209741#c17 --- Comment #17 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Franck Bui from comment #16) > (In reply to Fabian Vogt from comment #14) > > The graphical session itself is split over multiple services, so unless you > > want applications started by keyboard shortcuts (kglobalaccel) have a > > different keyring than applications started by the start menu (plasmashell) > > or the command launcher (krunner), this is needed. > > I see that makes sense for a group of user services that belong to the same > component. > > BTW how does it work currently ? do these KDE applications rely on the > kernel key management infra currently ? if so do they fallback to the user > session keyring ? Not at all. cifscreds is so far the only application I've seen that actually uses it in a DE context. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1209674] New: RISC-V Linux 6.3.0-rc3-25-default crashes on boot "Store/AMO access fault"
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209674 Bug ID: 1209674 Summary: RISC-V Linux 6.3.0-rc3-25-default crashes on boot "Store/AMO access fault" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: RISC-V OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: kkaempf(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Board: VisionFive2, 8GB Image: openSUSE-Tumbleweed-RISC-V-JeOS-starfivevisionfive2.riscv64-2023.03.02-Build10.14.raw.xz (checksummed ok) Full log (after grub boot screen): Loading Linux 6.3.0-rc3-25-default ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... Unhandled exception: Store/AMO access fault EPC: 00000000fff48a98 RA: 00000000fff871ea TVAL: 0000000040000000 EPC: 0000000040201a98 RA: 00000000402401ea reloc adjusted SP: 00000000ff734a50 GP: 00000000ff736e00 TP: 0000000000000001 T0: 0000000041c3fb81 T1: 0000005643534952 T2: 0000004005435352 S0: 0000000040000000 S1: 0000000040000000 A0: 0000000040000000 A1: 00000000f8ab1000 A2: 00010d20106f5a4d A3: 0000000000200000 A4: 0000000001d42000 A5: 0000000000000000 A6: 0000000000000002 A7: 0000000000000000 S2: 0000000001d42000 S3: 00000000ff734c18 S4: 0000000001c3fc00 S5: 0000000000200000 S6: 00000000f8ab1000 S7: 0000000000000000 S8: 00000000fe45f490 S9: 0000000000000001 S10: 0000000000000000 S11: 0000000000000000 T3: 0002506400004550 T4: 0000000000000000 T5: 020600a000000000 T6: 0000000040000000 Code: b383 0385 be03 0405 be83 0485 bf03 0505 (e110) UEFI image [0x00000000fe44f000:0x00000000fe713fff] '/efi\boot\bootriscv64.efi' UEFI image [0x00000000f8ab1000:0x00000000fa7f2fff] resetting ... reset not supported yet ### ERROR ### Please RESET the board ### -- You are receiving this mail because: You are on the CC list for the bug.

1 3