April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1222087] Systemd generated two service file for the same encrypted partition, leads to boot failure
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222087 https://bugzilla.suse.com/show_bug.cgi?id=1222087#c2 Antonio Feijoo <antonio.feijoo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |antonio.feijoo(a)suse.com --- Comment #2 from Antonio Feijoo <antonio.feijoo(a)suse.com> --- (In reply to Nicolas FORMICHELLA from comment #0) > Steps to Reproduce: > 1. Install Tumbleweed with /home (or other) partition encrypted I think that in order to reproduce your issue, you also have to manually set the DPS Partition ID using YaST or gdisk, because the default just sets the "Linux" type, and the systemd-gpt-auto-generator does not recognize any partitions and does not do create any device unit at boot in this case. > After investigation I found that both `systemd-gpt-auto-generator` and > `systemd-cryptsetup-generator` create a service for the same partition. What is happening is documented in the systemd-gpt-auto-generator(8) man page: "The /home/, /srv/, /var/, /var/tmp/ and swap partitions may be encrypted in LUKS format. In this case, a device mapper device is set up under the names /dev/mapper/home, /dev/mapper/srv, /dev/mapper/var, /dev/mapper/tmp or /dev/mapper/swap. Note that this might create conflicts if the same partition is listed in /etc/crypttab with a different device mapper device name." If you have an encrypted partition with the DPS UUID, you need to disable the systemd-gpt-auto-generator by adding `systemd.gpt_auto=0` to the kernel command line, or remove its entry from /etc/crypttab. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222186] VirtualBox not allowed to access USB devices although user is in vboxusers group
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222186 Thomas Rother <t.rother(a)netzwissen.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |t.rother(a)netzwissen.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222152] Slowdowns in terminal emulators under GNOME X.org with binary nvidia driver
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222152 https://bugzilla.suse.com/show_bug.cgi?id=1222152#c3 --- Comment #3 from Eskild Hustvedt <user-opensuse(a)zerodogg.org> --- (In reply to Alynx Zhou from comment #2) > This sounds really like this upstream issue: > https://gitlab.gnome.org/GNOME/mutter/-/issues/3384 I agree, that has to be the same issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219766] Virtualbox USB passthrough fails
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219766 https://bugzilla.suse.com/show_bug.cgi?id=1219766#c38 --- Comment #38 from Javier de San Pedro <javispedro(a)gmail.com> --- It is not the same issue. This new issue is being discussed in bug 1222186 . -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219766] New: USB passthrough fails
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219766 Bug ID: 1219766 Summary: USB passthrough fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: pinkernell(a)ph-heidelberg.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This is on OS: openSUSE Tumbleweed 20240207 Kernel: 6.7.4-1-default (64-bit) with Virtualbox 7.0.14-Virt.1699.733.2-x.86_64 Kernel module 7.0.14_k6.7.4_1-Virt.1699.733.2 Guest Windows 10, Guest Additions 7.0.14r161095 USB-3.0 xHCI Controller activated VBox host software recognises USB device (ScanSnap Scanner) and allows setting device filter. But guest does not find device. Hovering the mouse on USB icon of host software shows "No USB Devices connected". In the list of USB devices that opens after clicking on the icon, the Scanner is blanked out. This seems new since upgrade to 6.7.2(?) kernel. Which part of the log do you need? I am new here and happy to help. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1222156] After an upgrade the graphical interface no longer works
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222156 https://bugzilla.suse.com/show_bug.cgi?id=1222156#c13 --- Comment #13 from Roberto Canella <rm.canella(a)gmail.com> --- (In reply to Stefan Dirsch from comment #10) > Togan switches with his option to the newer amdgpu Kernel driver (which > isn't default for his Radeon GPU). I doubt this changes also the Mesa > driver. But seems this prevents the segfault. > > @Robert I think you have a different Radeon GPU, so you can't easily switch > to amdgpu driver or the support for it isn't working (there is a reason that > default kernel driver is radeon and not amdgpu). So this doesn't help. > > I suggest to either do a rollback or disable radeon kernel driver completely > with > adding > > modprobe.blacklist=radeon > > to GRUB_CMDLINE_LINUX_DEFAULT (see comment#7). With that you'll get simpledrm > on top of generic framebuffer. Means no 2d/3d acceleration and no > multimonitor support, but you should have a stable desktop back. Hi Stefan, given the security problem that arose with xz, I preferred not to do the "snapper rollback" and update the system... so I did as you suggested and put the radeon on the blacklist. Now everything works correctly even if not at its best, however I prefer it this way and not have possible security problems. Thank you -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1221636] While booting system waits 2 minutes for non-existing partition with uuid
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221636 https://bugzilla.suse.com/show_bug.cgi?id=1221636#c6 --- Comment #6 from Freek de Kruijf <freek(a)opensuse.org> --- > Although the protection is -rw-r--r-- I am unable to remove that entry with > "rm" as root; Operation not permitted. Did not read further and used chattr -i on that entry and now the entry is removed. Thanks!! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1221636] While booting system waits 2 minutes for non-existing partition with uuid
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221636 https://bugzilla.suse.com/show_bug.cgi?id=1221636#c5 --- Comment #5 from Freek de Kruijf <freek(a)opensuse.org> --- (In reply to Antonio Feijoo from comment #4) > (In reply to Freek de Kruijf from comment #0) > > During boot journalctl -b reports: > > mrt 18 13:40:14 eiktum systemd-hibernate-resume-generator[167]: Reported > > hibernation image: ID=opensuse-tumbleweed VERSION_ID=20231106 > > kernel=6.5.9-1-default UUID=b66ef179-3b2f-407b-81f3-88e5c71ea8de offset=0 > > You're experiencing the following upstream issue: > https://github.com/systemd/systemd/issues/32021 > > Temporary workaround: > https://github.com/systemd/systemd/issues/30395#issuecomment-1852613917 It suggests to remove the entry /sys/firmware/efi/efivars/HibernateLocation... Although the protection is -rw-r--r-- I am unable to remove that entry with "rm" as root; Operation not permitted. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222186] VirtualBox not allowed to access USB devices although user is in vboxusers group
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222186 https://bugzilla.suse.com/show_bug.cgi?id=1222186#c11 --- Comment #11 from Claudio Marcial Peon <claudio(a)datacor.net.ar> --- (In reply to T Adams from comment #9) > I'm afraid that these steps didn't help for me. I made the changes > indicated in: > > https://bugzilla.suse.com/attachment.cgi?id=873962&action=diff > > and in: > > https://bugzilla.suse.com/attachment.cgi?id=873963&action=diff > > with the change from 660 to 650 in lines 50 and 52, and also ran > /usr/lib/virtualbox/vboxdrv.sh restart > > On reboot, I still get a locked /dev/vboxusb directory, and the user > enumeration error on firing up the Windows VM. > > I'm on snapshot 20240329. After a reboot, I have to run again /usr/lib/virtualbox/vboxdrv.sh restart After that the enumeration error is gone, at least until the next reboot -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222186] VirtualBox not allowed to access USB devices although user is in vboxusers group
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222186 https://bugzilla.suse.com/show_bug.cgi?id=1222186#c10 Javier de San Pedro <javispedro(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |javispedro(a)gmail.com --- Comment #10 from Javier de San Pedro <javispedro(a)gmail.com> --- Suffering the same problem, but as far as I can see to me it is because of these changes to the package: https://build.opensuse.org/request/show/1163382#comments , rather than any kernel changes. I left a message there, but not sure since anyone is notified about it. I don't know what the intention of the patch is but in addition to the /etc/vboxusb type (which I didn't see either :) ) , setting 0660 to /dev/vboxusb looks wrong to me. As I say on the message there, my recommendation is to just avoid doing these chmod workarounds in the virtualbox packaging. I don't know if this was introduced due to bug 1219766 or something else, but to me it doesn't sound like something that should be workarounded silently in the virtualbox package. Just reverting these vboxusb chmod workarounds from the package (as in https://build.opensuse.org/package/rdiff/home:javispedro:fixpkgs/virtualbox… ) for me makes USB passthrough work again in TW. -- You are receiving this mail because: You are on the CC list for the bug.

1 0