Wed, 23 Sep 2009

Kerneloops enabled by default in Karmic

One of the new things that is going to be in karmic is that the kerneloops daemon will be installed and running by default. This tool, created by Arjan van de Ven, watches the kernel logs for problems. It has a companion service, which aggregates reports of these problems, and can sort by kernel version and the like. This allows kernel developers to spot the most commonly encountered problems, areas of the code which are prone to bugs etc. When the kerneloops daemon catches a problem it allows you to send the problem to

We however, are not using the applet that comes with kerneloops to do this, we are making use of the brilliant Apport. There are a couple of reasons for this. We also want to make it easy for you to report these issues as bugs to Launchpad, and we don't want to prompt you with two different interfaces to do that.

The changes mean that if your machine has a kernel issue you will get an apport prompt as usual. As well as asking if you would like to report the problem to Launchpad like it does for other crashes it will ask if you would also like to report it to Passing the information through apport means that it can also be used on servers as well without running X.

Hopefully you will never see this improvement, but it's now going to be there for when those bugs do creep in.

Posted at: 16:55 | category: /ubuntu | Comments (3)

I was a bit disappointed that kerneloops got punted late in the Jaunty release run up.  But I'm very glad you guys have stuck with it. 

Will kerneloops reporting be enabled for the daily and other ppa based kernels builds you are doing as well as the Karmic release kernels?  The daily kernel builds you are doing which track close to mainline are probably the most valuable kerneloops for upstream work.


Posted by jef spaleta at Wed Sep 23 20:29:17 2009


I haven't checked, but I believe apport will bomb out before allowing kerneloops to submit. There's a larger conversation going on about apport and external packages, and this will be used as input to that.

In the meantime I'll add instructions on using kerneloops-applet to submit oopses to to the mainline build documentation.



Posted by James Westby at Thu Sep 24 11:58:19 2009

This is excellent work, and turned out even better than I had hoped.  Thanks very much for making it happen.

Posted by Matt Zimmerman at Sat Oct 10 15:10:46 2009