[Bug]: Update does not check validity of installed extension pack, causing crashes

Open
#995 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 6 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c, cpp

Research direction

The failure surfaces as VERR_PDM_DRIVER_NAME_CLASH when a stale extension pack is loaded by a newer VirtualBox, so start in the main API's extension-pack manager (src/VBox/Main/src-server/ExtPackManagerImpl.cpp) and the extpack sources under src/VBox/ExtPacks, then trace where the UI/installer path (src/VBox/Frontends) decides to load a pack at startup. Reproduce by installing an older extension pack alongside the newly installed 7.2.22 build on macOS and noting that no version check fires. Done means the update path detects the version mismatch and warns or refuses instead of loading and crashing.

Written by the indexing model from the issue text.

Description

bug
Version

trunk/main

Host OS Type

macOS

Host OS name + version

Tahoe 26.6.2

Host Architecture

x86

Guest OS Type

Linux

Guest Architecture

x86

Guest OS name + version
Component

Unspecified

What happened?

VERR_PDM_DRIVER_NAME_CLASH after updating to 7.2.22, without updating the extension pack - as there was no message and no warning.

This bug seems to exist for more than 10 years. This is insane.

How can we reproduce this?

install a new version when an old version with extension pack is installed and the new version would need an updated extension pack

Did you upload all of your necessary log files, screenshots, etc.?
  • Yes, I've uploaded all pertinent files to this issue.
Dominant language
C
Stars
1.4k
Forks
219
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from VirtualBox/virtualbox

All issues in VirtualBox/virtualbox

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.