Header files of new builds of the Kernel not installed automatically while update after install and remove packages with upstream kernel from kernel-ppa

[RussianNeuroMancer]

Typical user do this:
1. Install Lucid release or Maverick Beta.
2. Update. New headers will be downloaded and installed without problems, as expected.

But Launchpad users sometimes do this, because developers and contributors ask test upstream kernel:
1. Install Lucid release or Maverick Beta.
2. Install upstream kernel from this link: https://wiki.ubuntu.com/KernelMainlineBuilds
3. Do something with upstream kernel - check some bug for example.
4. So, after that upstream kernel not no need anymore (and its' not comfortably - it' not updated automatically) - user remove it.
5. Try update after that - headers of new kernel, what available in repositories, not installed automatically. It's a big problem for all, who use additional kernel modules (VirtualBox modules, proprietary video driver modules, etc.), because after kernel update without headers update system can not run graphical mode or work incorrect (VirtualBox can not run virtual machines).

I conclude there is no problem with APT or Linux, but problem with testing of upstream kernel process (Installing/Uninstalling) for Launchpad users.
Xorg team already have PPA and ppa-purge for testing fresh X.org and FOSS drivers. Maybe need create something similar for upstream kernel testing process?

[Jeremy Foshee (jeremyfoshee)]

Hi RussianNeuroMancer,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 633449

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[RussianNeuroMancer (russianneuromancer)]

Looks like I found origin of this issue.

Typical user do this:
1. Install Lucid release or Maverick Beta.
2. Update. New headers will be download and installed without problems, as expected.

But for reproduce this issue you must do this:
1. Install Lucid release or Maverick Beta.
2. Install upstream kernel from your link: https://wiki.ubuntu.com/KernelMainlineBuilds
3. Do something with upstream kernel - check some bug for example.
4. So, after that upstream kernel not no need anymore (and its' not comfortably - it' not updated automatically) and user remove it.
5. Try update after that - headers of new kernel, what available in repositories, not installed automatically. It's a big problem for all, who user additional kernel modules (VirtualBox modules, proprietary video driver modules, etc.), because after kernel update without headers update system can not boot.

I conclude there is problem no problem with APT or Linux, but problem with testing of upstream kernel process (Installing/Uninstalling) for Launchpad users.

[RussianNeuroMancer (russianneuromancer)]

For example I get problem what described in this bug (also see original description https://bugs.launchpad.net/ubuntu/+source/linux/+bug/633449/comments/0 ) after testing upstream kernel, because you ask me about it here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/606839

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 633449

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.