[Bug]: Update does not check validity of installed extension pack, causing crashes
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
- Domain
- operating-systems
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
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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from VirtualBox/virtualbox
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 84/100
VirtualBox/virtualbox#996 ·
Maintainers usually reply within 6 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
VirtualBox/virtualbox#979 ·
Maintainers usually reply within 6 days
-
[Bug]: Guest Additions 7.2.20 vboxvideo fails to build on Linux kernel 6.12.113 (drm_fb_helper_restore_fbdev_mode_unlocked: too few arguments)Possibly taken @Berbe claimed this 18 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
VirtualBox/virtualbox#918 · 9 comments ·
Maintainers usually reply within 6 days
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
VirtualBox/virtualbox#994 ·
Maintainers usually reply within 6 days
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 30/100
VirtualBox/virtualbox#993 ·
Maintainers usually reply within 6 days
All issues in VirtualBox/virtualbox
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
ESPresense/ESPresense#2680 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ImageMagick/ImageMagick#9134 ·
Maintainers usually reply within 1 day
-
Builder: a structure opened without calculation data shows the Diffraction (fibre) view by defaultOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
FriendsofECCE/ECCE#1245 · 1 comment ·
-
Arch: ARM/AArch64 Doc
Difficulty 1/5 Under an hour Newbie friendliness 90/100
RT-Thread/rt-thread#12082 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/nuttx-apps#4108 · 4 comments ·
Maintainers usually reply within 1 day