Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Virtualbox Ext Pack 7.0.10 #3

Merged
merged 0 commits into from
Aug 30, 2023
Merged

Virtualbox Ext Pack 7.0.10 #3

merged 0 commits into from
Aug 30, 2023

Conversation

mmstick
Copy link
Member

@mmstick mmstick commented Aug 21, 2023

No description provided.

@mmstick mmstick requested review from a team August 21, 2023 15:08
Copy link
Member

@jacobgkau jacobgkau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've inconsistently seen a weird issue where this package needs to be installed twice to start working (after the first installation on a fresh machine, the extension pack isn't detected by VBoxManage or the VirtualBox GUI.)

  • Attempting to replicate the issue, resetting the debconf key for the EULA and removing ~/.config/VirtualBox/ do not cause it to occur again. So far, I've only seen it happen once on each computer. However, I don't see it happen in a VM (where it would be easiest to replicate with snapshots.)
  • Upgrading/downgrading the package or doing an apt reinstall makes it start working after the issue has occurred. From what I've seen, computers where 7.0.8 was already installed (with the extension pack) do not have the issue upon upgrading to 7.0.10.

Given the difficulty of replicating the issue, I can't be sure it's a regression, and it wouldn't make sense for it to be given that the installation mechanism isn't changing in this PR, so I don't think it's grounds to withhold approval (also considering this package isn't included by default and is a manual addition in the first place.)

Tested with pop-os/virtualbox#10.

@mmstick mmstick merged commit 8815bd4 into master_jammy Aug 30, 2023
@mmstick mmstick deleted the vb_jammy branch August 30, 2023 22:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants