View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001279 | Kali Linux | General Bug | public | 2014-05-24 09:28 | 2014-05-24 20:35 |
Reporter | muts | Assigned To | rhertzog | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | resolved | Resolution | fixed | ||
Fixed in Version | 1.0.7 | ||||
Summary | 0001279: Possible issues with virtualbox 3.4 and kernel 3.14 | ||||
Description | Upgrade to 3.14 fails with: dpkg-reconfigure linux-image-3.14-kali1-amd64 | ||||
Do you have linux-headers-amd64 installed ? If yes, it should have pulled linux-headers-3.14-amd64 and you should not have error messages about missing headers (or only temporarily during the upgrade). |
|
It happens that you get some complaints during update of linux-image-3.14-kali1-amd64 because linux-headers-3.14-kali1-amd64 is often only upgraded afterwards. But once linux-headers-3.14-kali1-amd64 is installed, it should trigger /etc/kernel/header_postinst.d/dkms which does mostly the same than /etc/kernel/postinst.d/dkms. |
|
So virtualbox-source is not really compatible with Linux 3.14, I confirmed it: Examining /etc/kernel/header_postinst.d. And then the log file says: DKMS make.log for virtualbox-4.1.18 for kernel 3.14-kali1-amd64 (x86_64) |
|
I imported virtualbox 4.3.10-dfsg-1~bpo70+1 from wheezy-backports together with gsoap 2.8.16-2~bpo70+1 to fix this issue. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2014-05-24 09:28 | muts | New Issue | |
2014-05-24 19:45 | rhertzog | Note Added: 0001907 | |
2014-05-24 19:49 | rhertzog | Note Added: 0001908 | |
2014-05-24 20:13 | rhertzog | Note Added: 0001909 | |
2014-05-24 20:35 | rhertzog | Note Added: 0001910 | |
2014-05-24 20:35 | rhertzog | Status | new => resolved |
2014-05-24 20:35 | rhertzog | Fixed in Version | => 1.0.7 |
2014-05-24 20:35 | rhertzog | Resolution | open => fixed |
2014-05-24 20:35 | rhertzog | Assigned To | => rhertzog |