April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[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

[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#c9 --- Comment #9 from T Adams <timothyadams(a)ymail.com> --- 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. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222184] New: SDDM fails after upgrade to Plasma 6
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222184 Bug ID: 1222184 Summary: SDDM fails after upgrade to Plasma 6 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: o.g.m.belleux(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873946 --> https://bugzilla.suse.com/attachment.cgi?id=873946&action=edit History of sudo zypper -v dup --allow-vendor-change Hello, After unsuccessful attempts to upgrade to Plasma 6 (see bug 1221515), I've finally been able to give it a go. The upgrade went well until the reboot. First of all, SDDM didn't display the theme and an error message in red indicating that it couldn't find a file. I logged into TTY and searched for and installed the missing RPMs, which are not installed by default: - libQt6QuickLayouts6 - libQt6Xml6 - libQt6Svg6 From there SDDM displays the theme. By entering login + password, there is a connection attempt then back to Greeter with Wayland as X11. In TTY , I found that libQt6Core5Compat6 was missing for wayland. I was able to launch a plasma 6 session under wayland with an ugly display that didn't respect the theme colours, among other oddities. However, with X11 I get a black screen for SDDM. So I can't connect. So reboot + snapper rollback to plasma 5 for now. I attach the upgrade history for information. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1221515] New: unsatisfied dependency problems for Plasma 6 / Gear 24.02
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221515 Bug ID: 1221515 Summary: unsatisfied dependency problems for Plasma 6 / Gear 24.02 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: o.g.m.belleux(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873571 --> https://bugzilla.suse.com/attachment.cgi?id=873571&action=edit result of ```sudo zypper -v dup -D --allow-vendor-change|tee zypper_dup.txt``` I added kde repositories as described in https://en.opensuse.org/SDB:KDE_repositories and try ```sudo zypper -v dup -D --allow-vendor-change``` which give me 2 Problems: – Problem: the to be installed libKPim6Mime6-24.02.0-kf.276.1.x86_64 requires 'kmime >= 24.02.0', but this requirement cannot be provided – Problem: the to be installed kdepim-runtime-24.02.0-kf.347.1.x86_64 requires 'akonadi', but this requirement cannot be provided I checked with zypper se and at the openbuildservice; kmime and akonadi are availables. I've tried to solve these problems, but it just keeps producing more and more of them. I did ```sudo zypper -v dup -D --allow-vendor-change|tee zypper_dup.txt``` choosing the uninstall solution with the smallest number for info. I attach the file zypper_dup.txt. I think these are simple problems of dependencies and "conflict" or "obsolete" in specs due to changes between "KDE 5" and "KDE 6". In doubt, I'd rather wait for them to be resolved than break everything before upgrading to Plasma 6. Thanks to all the KDE Team for the great work you do voluntarily. -- You are receiving this mail because: You are on the CC list for the bug.

1 13