April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[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#c17 --- Comment #17 from T Adams <timothyadams(a)ymail.com> --- >After a reboot, I have to run again > /usr/lib/virtualbox/vboxdrv.sh restart Thanks, Claudio. I did try this, but without effect on the enumeration error. I fear I'm not competent enough to do extensive editing of these configuration files, will wait until you more knowledgeable openSUSErs find a fix. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222183] pcr-oracle fails to parse LOADER_CONF_EVENT_TAG_ID
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222183 https://bugzilla.suse.com/show_bug.cgi?id=1222183#c2 --- Comment #2 from Alberto Planas Dominguez <aplanas(a)suse.com> --- (In reply to Andrei Borzenkov from comment #0) > Apart from the obvious bug in pcr-oracle, this invalidates any claim of > "immutability" of MicroOS - failed update makes it impossible to boot > MicroOS without human intervention. Also comment here that the ESP, /etc and /var are outside of the transaction. This bug is a very interesting case where a side effect (the update of the boot loader) affect all the transactions at the same time: the new boot loader is visible for all the snapshots. We are thinking how to fix this. One option can be that when doing a rollback, recover the old boot loader from the snapshot. This is the correct approach in general, but if the user select an old snapshot from the boot loader, it is still using the most updated one. -- 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#c16 --- Comment #16 from robert spitzenpfeil <rs.opensuse(a)spitzenpfeil.org> --- Correction to comment #13: The perms for the device nodes are 0660 (OK) The perms for the (previously created) folders just get g+x (just in case) and are _not_ overwritten with 0660 (no g+x) -- 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#c15 --- Comment #15 from Javier de San Pedro <javispedro(a)gmail.com> --- (In reply to Larry Rainey from comment #12) > The issue is wrong major minor numbers Sorry, I don't understand, can you elaborate how to reproduce that problem with wrong minor for vboxdrv? Sounds like a udev issue. It would also entirely prevent vbox from working, not just USB passthrough. I am now very confused, as I see the package installs a /usr/lib/udev/rules.d/60-vboxdrv.rules , _but at the same time_ running vboxdrv.sh setup will create /etc/udev/rules.d/60-vboxdrv.rules I never had to run "vboxdrv.sh setup", it has always worked without that (since we had kmp package in TW). In fact I didn't have the /etc/udev/rules.d/60-vboxdrv.rules at all in my system. > I have a good fix - need others to validate it. > > sudo /usr/lib/virtualbox/vboxdrv.sh start will fix it without a reboot with > this file > > too big to paste here so here is a link put it in /usr/lib/virtualbox/ > > https://paste.opensuse.org/pastes/9641ebe078e6 In any case, the attached vboxdrv.sh does not fix the issue. Just running "start" will chmod /dev/vboxusb back to 0660 and as I mentioned above for me this is wrong. -- 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 robert spitzenpfeil <rs.opensuse(a)spitzenpfeil.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #873962|0 |1 is obsolete| | -- 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 robert spitzenpfeil <rs.opensuse(a)spitzenpfeil.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #873962|fix path: 'etc' --> 'dev' |fix path: 'etc' --> 'dev' description| |(see newer diff!) -- 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#c14 --- Comment #14 from robert spitzenpfeil <rs.opensuse(a)spitzenpfeil.org> --- Created attachment 873974 --> https://bugzilla.suse.com/attachment.cgi?id=873974&action=edit fix device node / folder perms -- 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#c13 --- Comment #13 from robert spitzenpfeil <rs.opensuse(a)spitzenpfeil.org> --- See my comment #3 --- I now think this is wrong, as it also set the perms for the directories to 0660 * /usr/lib/virtualbox/vboxdrv.sh lines 63-65 should (IMO) read (it was /etc/vboxusb on my box): chmod "${DEVICE_MODE}" /dev/vboxusb/ chmod "${DEVICE_MODE}" /dev/vboxusb/* chmod "${DEVICE_MODE}" /dev/vboxusb/*/* --- If I replace all the chmod lines with: find /dev/vboxusb -type f -exec chmod "${DEVICE_MODE}" {} \; find /dev/vboxusb -type d -exec chmod g+x {} \; The perms for the device nodes are 0600 (OK) The perms for the (previously created) folders just get g+x (just in case) and are _not_ overwritten with 0660 (no g+x) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222183] pcr-oracle fails to parse LOADER_CONF_EVENT_TAG_ID
by bugzilla_noreply＠suse.com 01 Apr '24

01 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222183 https://bugzilla.suse.com/show_bug.cgi?id=1222183#c1 --- Comment #1 from Alberto Planas Dominguez <aplanas(a)suse.com> --- (In reply to Andrei Borzenkov from comment #0) Hi Andrei, thanks a lot for the detailed bug report > Error: Unable to parse EVENT_EVENT_TAG event from TPM log > ::: 04f9c: event type=EVENT_EVENT_TAG pcr=5 digests=4 data=32 bytes > ::: sha1 01d4e1ca16f118f6fcd954e175c0116c4a4f746b > ::: sha256 > bdbea6dbc6791de89a483abc3a61af8e910249e7565682ff2011c910a490520a > ::: sha384 > 12ebd339e16a134b0aeeb3114bd5b233f9f862037b7550c922a7c73686fa616995273aa751446 > 40d4fb911945d7b5f55 > ::: sha512 > 7c4a18a73955640cde19777b87735f1ca928fe6ef6b54aa3a6d8117c8eaadbd6c00778165a9a3 > 20303644489c242c88a5b2ca6b20be1ffe75f70d5b930f647f6 > ::: Data: > ::: 0000 2a 58 bc f5 18 00 00 00 6c 00 6f 00 61 00 64 00 65 00 72 > 00 2e 00 63 00 6f 00 6e 00 66 00 00 00 *X......l.o.a.d.e.r...c.o.n.f... > Fatal: Aborting. > Error: Failed to install TPM predictions for If I am not wrong this was fixed here: https://github.com/okirch/pcr-oracle/pull/50 Can you check that the version of pcr-oracle running in the snapshot that you are updating from contains this change? """ Tue Feb 20 18:16:53 UTC 2024 - Alberto Planas Dominguez <aplanas(a)suse.com> - Add fix_loader_conf.patch to measure the systemd-boot loader.conf file """ > Apart from the obvious bug in pcr-oracle, this invalidates any claim of > "immutability" of MicroOS - failed update makes it impossible to boot > MicroOS without human intervention. Yes, there is an issue here: systemd-boot started to measure loader.conf in v255. We updated the pcr-oracle version 20th of February, and the systemd v255 was populated in Factory two weeks ago, at the end of March. That should give 1 month of time for the update. I do not understand how is possible that you have a new systemd, but an old pcr-oracle. I will try to replicate the issue locally, downgrading my current installation. -- 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#c39 Thomas Rother <t.rother(a)netzwissen.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|REOPENED |RESOLVED --- Comment #39 from Thomas Rother <t.rother(a)netzwissen.de> --- Note: new issues with USB passthrough are discussed at https://bugzilla.suse.com/show_bug.cgi?id=1219766 -- You are receiving this mail because: You are on the CC list for the bug.

1 0