how to report problems with a new kernel from intrepid-proposed?

Asked by Uwe Geuder

Where/how do I report regression in the 2.6.27-14 kernel from intrepid-proposed?

Do I just create a new bug report or is there s central palce wehre regression for proposed kernels is collected?

I've searched for "2.6.27-14" in launchpad bugs, but I got many unrelated hits and couldn't find anything suitable.

(The reason I'm using a kernel from proposed is that my networking broke with 2.6.27-11 and this was fixed with 2.6.27-13 from intrepid-proposed. However, 2.6.27-13 causes regression in framebuffer and that problem is still there in 2.6.27-14 so I thought I better report it.)

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu linux Edit question
Assignee:
No assignee Edit question
Solved by:
Uwe Geuder
Solved:
Last query:
Last reply:
Revision history for this message
ANDREA (andrea54) said :
#1

Hi Uwe
I think you should file a bug report against it. I am not aware of any other place.
Hope this helps!

ANDREA

Revision history for this message
Huygens (huygens-25) said :
#2

Hello Uwe,

The best way to report a bug from a particular package is to use Apport (the bug/crash reporter integrated in Ubuntu). To do so, I am not aware of any graphical user interface that does it when the package is the Kernel. So you will have to use the command line. So open a Terminal (main Ubuntu menu 'Applications' -> 'Accessories' -> 'Terminal').
First type the following command to verify the version of the package:
dpkg -l linux-image-generic
If the version of the Linux Kernel is correctly reported, then you can simply do:
ubuntu-bug linux-image-generic
And A bug report with all necessary information will be created and you can modify/edit it.

If the version of the Linux Kernel is not correct, try this:
dpkg -l linux-image-2.6.27-14-generic
If it is working, then you can report the bug by doing this:
ubuntu-bug linux-image-2.6.27-14-generic

I hope this help you.

Revision history for this message
Uwe Geuder (ubuntulp-ugeuder) said :
#3

Thanks for your answers. However, my feeling that I have seen special reports just for that case was correct.

I have found the places I was looking for:

https://bugs.launchpad.net/ubuntu/intrepid/+source/linux/+bugs?field.tag=verification-needed

The reports have the headline "[Intrepid] Update kernel..." and the tag "verification-needed"

I didn't even know that tags exist in launchpad.

This way you get the reports with feedback requests for kernels 2.6.27-14, -15, -16/17, and -18

However 2.6.27-13 is hidden deep in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/326891 and it's not tagged.

Is the tagging documented anywhere???

(My concrete problem has been solved, but I still leave the question open for a while in case somebody can explain the general principle)

Revision history for this message
Uwe Geuder (ubuntulp-ugeuder) said :
#4

@Huygens:

Thanks, for the hint with ubuntu-bug. Hadn't used that before. According to the man page it should be used with option -p, but it looks like the option does not really make a difference.

However the package name linux-image-generic should probably not be used. The bug report will to directed to source package linux-meta, but I believe kernel bugs belong to source package linux.

ubuntu-bug saves really a lot of work, because it attaches 9 files with logs and system information additionally to the "normal" version information in the text.

So I decided to create a new bug report and just add links from the "verification-needed" reports (because my report seems to apply to more than one "verification-needed" anyway)

Still leaving this question open, if anybody can explain the tag usage. (Or comment whether any of my guesses were wrong here)

Revision history for this message
Uwe Geuder (ubuntulp-ugeuder) said :
#5

I found some answers to my questions:

Tag usage is explained here: https://wiki.ubuntu.com/Bugs/Tags

Some information about kernel specific bug practices is found here https://wiki.ubuntu.com/KernelTeamBugPolicies

Unfortunately the page does not mention anything about those reports titled "[Intrepid] Update kernel...".

According to this page a kernel bug can be reported using "ubuntu-bug -p linux"

(Not sure whether this is 100% equivalent to the longer version specific form "ubuntu-bug -p linux-image-2.6.27-14-generic" I have used)

Revision history for this message
Huygens (huygens-25) said :
#6

I am not sure either if it is the correct method to report bugs for the kernel, but this is also the method recommended by an Ubuntu member:
http://mdzlog.wordpress.com/2009/03/31/please-dont-report-ubuntu-bugs-directly-to-launchpad/