Shouldn't start on stable releases

[James Westby]

Binary package hint: kerneloops

Hi,

We disable apport on stable releases, but currently kerneloops still runs, which
causes apport to pop up with reports of kernel issues. We should therefore prevent
kerneloops from running as well.

Impact: prompts for kernel issues that will take a while to fix, or may not be fixed due to it being a stable release. Made worse by kerneloops not being particularly good about avoiding prompting multiple times for the same issue.

Fix for Lucid: shouldn't be changed there as it is the development branch. Will ship the defaults file though, just
with the default changed.

Patch is http://bazaar.launchpad.net/~james-w/ubuntu/karmic/kerneloops/disable-stable/revision/14

TEST CASE:

1. Boot a karmic system, note that there is a kerneloops process running.
2. Install the updated package.
3. Note that there is no longer a kerneloops process running.
4. Reboot, there should still be no kerneloops process running.

Regression potential: Should be very low in terms of the actual changes. Anyone that wants it running for whatever reason is going to have to edit the defaults file.

Thanks,

James

ProblemType: Bug
Architecture: i386
Date: Mon Nov 2 15:15:12 2009
DistroRelease: Ubuntu 9.10
Package: kerneloops (not installed)
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/zsh
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: kerneloops
Uname: Linux 2.6.31-14-generic i686

[Martin Pitt (pitti)]

Accepted kerneloops into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Brian Murray (brian-murray)]

I installed kerneloops package version 0.12+git20090217-1ubuntu4.1 from karmic-proposed and found that the kerneloops daemon was no longer running.

[Steve Beattie (sbeattie)]

I also verified that installing kerneloops-daemon 0.12+git20090217-1ubuntu4.1 from karmic-proposed no longer starts up the kerneloops monitoring daemon. I also created a simple kernel module that would do WARN_ON(), reproduced that the with the kerneloops-daemon from karmic release, a crash report prompt is generated, and that with the version from karmic-proposed it is not. I also confirmed that enabling it via /etc/default/kerneloops and restarting the kerneloops initscript caused it to properly detect and notify about kernel warnings and oops. No sign of a regression here.

(I suspect that Brian is interested in having the seven day waiting period for SRUs waived, as kerneloops is generating a large number of of launchpad bugreports. I think this is reasonable here.)

[Martin Pitt (pitti)]

Steve Beattie [2009-11-03 6:15 -0000]:
> (I suspect that Brian is interested in having the seven day waiting
> period for SRUs waived, as kerneloops is generating a large number of of
> launchpad bugreports. I think this is reasonable here.)

Full ack. I also confirm that it's quiet now, and the two ends of the
regression potential are just "it continues to spam" (nothing lost
then), or "it stops working entirely" (not the end of the world
either, we aren't so interested on getting reports from stable
releases).

[Launchpad Janitor (janitor)]

This bug was fixed in the package kerneloops - 0.12+git20090217-1ubuntu4.1

---------------
kerneloops (0.12+git20090217-1ubuntu4.1) karmic-proposed; urgency=low

  * Don't start kerneloops on boot in stable releases, for the same reasons that
    we disable appport. (LP: #471137)

 -- James Westby <email address hidden> Mon, 02 Nov 2009 15:13:28 +0000

[Martin Pitt (pitti)]

copied to lucid.

[Martin Pitt (pitti)]

If you are actually interested in getting kerneloops reports for lucid that early on, please do a followup upload with enabling it by default. (We keep apport disabled until alpha-2 or so, since fixes happen faster than people can report/we can review them).

[James Westby (james-w)]

On Tue Nov 03 11:46:19 UTC 2009 Martin Pitt wrote:
> If you are actually interested in getting kerneloops reports for lucid
> that early on, please do a followup upload with enabling it by default.
> (We keep apport disabled until alpha-2 or so, since fixes happen faster
> than people can report/we can review them).

I will discuss this with the kernel team, I imagine they would like the
time laspse as well.

Thanks,

James

[Piscium (piscium)]

Thanks, this "fixed" my suspend issue.

http://ubuntuforums.org/showthread.php?p=8234221#post8234221