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

未关闭
#995 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 6 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
c, cpp

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.
主要语言
C
星标
1.4k
派生
219
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

VirtualBox/virtualbox 的其他 Issue

查看 VirtualBox/virtualbox 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。