kernel plugin: the modprobe output parsing is wrong
Metadata
Current evaluation
Closed without resolution. The kernel plugin modprobe output parser incorrectly captured only the last dependency line. No fix or patch was applied.
Suggested action: —
No scores available.
Issue body
For this output:
$ modprobe --show-depends -n vmwgfx
insmod /lib/modules/4.10.0-13-generic/kernel/drivers/video/fbdev/core/sysimgblt.ko
insmod /lib/modules/4.10.0-13-generic/kernel/drivers/video/fbdev/core/sysfillrect.ko
insmod /lib/modules/4.10.0-13-generic/kernel/drivers/video/fbdev/core/syscopyarea.ko
insmod /lib/modules/4.10.0-13-generic/kernel/drivers/video/fbdev/core/fb_sys_fops.ko
insmod /lib/modules/4.10.0-13-generic/kernel/drivers/gpu/drm/drm.ko
insmod /lib/modules/4.10.0-13-generic/kernel/drivers/gpu/drm/drm_kms_helper.ko
insmod /lib/modules/4.10.0-13-generic/kernel/drivers/gpu/drm/ttm/ttm.ko
insmod /lib/modules/4.10.0-13-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko enable_fbdev=1
We always capture the last item, on the last line you can see why this is a problem.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The kernel plugin modprobe output parser incorrectly captured only the last dependency line. No fix or patch was applied. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The kernel plugin incorrectly parsed modprobe output, capturing only the last dependency line instead of all modules. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1208 kernel plugin: fix modprobe output parsing. | snapcraft | merged | Merged by maintainer sergiusens to fix modprobe output parsing in the kernel plugin. The change correctly identifies the module path as the second output item. A failing test was explicitly ignored during merge. | |
| #1759592 kernel build fails for lack of modprobe | snapcraft (launchpad) | closed | Closed without resolution. Zero comments and no linked fix indicate the modprobe dependency issue was abandoned or superseded. |