linux package hook checks uname for KernelOops
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Fix Released
|
Undecided
|
Martin Pitt |
Bug Description
The linux package hook, provided by apport, contains the following code:
def add_info(report, ui):
# If running an upstream kernel, instruct reporter to file bug upstream
abi = re.search(
if abi and (abi.group(1) == '999' or re.search("^0\d", abi.group(1))):
Checking uname makes sense if some one is reporting a bug about the running kernel, but not if apport has raised a crash report dialog for a previous Oops. Here is a portion of one crash report:
ProblemType: KernelOops
...
Package: linux-image-
...
Uname: Linux 3.12.0-
It should be investigated to see if this blocks sending crash reports to the error tracker and if so the check should be modified not to use uname at least for kerneloops.
Related branches
summary: |
- linux package hook checks uname for Oops'es + linux package hook checks uname for KernelOops |
I'm afraid I don't understand this. If you do "ubuntu-bug linux" it's supposed to be filed against the currently running kernel, so the Uname: field will be determined at the time when you run ubuntu-bug. But when add_info() runs, it only looks at the report's Uname: field, not the current uname(). So what is the problem here, can you please be more concrete about when this would do the wrong thing? Thanks!