kernel oops results in apport-gtk launching for every .crash file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-notifier (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
I've been testing multiple different kernels for bug 1218004, as a part of this process my system frequently experiences a kernel oops. Only occasionally, is a kernel oops crash file created for these crashes. This particular time the following happened:
Sep 24 09:47:42 localhost kernel: [ 330.255893] ubuntuone-
Sep 24 09:47:54 localhost kernel: [ 341.887110] BUG: unable to handle kernel NULL pointer dereference at 0000000000000070
Sep 24 09:47:54 localhost kernel: [ 341.887197] IP: [<ffffffff811fb
Sep 24 09:47:54 localhost kernel: [ 341.887242] PGD 72b78067 PUD 6d306067 PMD 0
Sep 24 09:47:54 localhost kernel: [ 341.887276] Oops: 0000 [#1] SMP
It looks like ubuntuone-syncd crashed and shortly after that I experienced a kernel oops. Looking in /var/crash we can see the following:
$ ls -lctr /var/crash/
total 39532
-rw-r----- 1 root whoopsie 7141 Sep 18 10:10 linux-image-
-rw-r--r-- 1 bdmurray whoopsie 0 Sep 18 12:00 _usr_bin_
-rw-r--r-- 1 bdmurray whoopsie 0 Sep 18 12:02 _usr_bin_
-rw------- 1 whoopsie whoopsie 0 Sep 18 13:47 _usr_bin_
-rw------- 1 whoopsie whoopsie 0 Sep 18 13:47 _usr_bin_
-rw-r----- 1 bdmurray whoopsie 33668113 Sep 24 09:53 _usr_lib_
-rw-r----- 1 bdmurray whoopsie 105043 Sep 24 09:53 _usr_lib_
-rw-r----- 1 bdmurray whoopsie 1770585 Sep 24 09:53 _usr_bin_
---------- 1 bdmurray whoopsie 50209 Sep 24 09:53 _usr_bin_
---------- 1 bdmurray whoopsie 952256 Sep 24 09:53 _usr_bin_
-rw-r----- 1 bdmurray whoopsie 3851246 Sep 24 09:53 _usr_bin_
Something caused every crash file's modification time to change. The end result of this being that on the next reboot I received an apport-gtk notification for every crash, even ones that I experienced some time ago and that have already been uploaded. While this is an unlikely, it is rather annoying.
Changed in update-notifier (Ubuntu): | |
importance: | Undecided → Medium |
Looking at the upstart user job log files we see:
$ cat ~/.cache/ upstart/ update- notifier- crash-_ var_crash_ _usr_lib_ firefox_ firefox. 1000.crash. log _usr_lib_ firefox_ firefox. 1000.crash detected syncdaemon
Tue Sep 24 09:52:46 PDT 2013 crash report /var/crash/
ubuntuone-
$ cat update- notifier- crash-_ var_crash_ _usr_bin_ xeyes.1000. crash.log _usr_bin_ xeyes.1000. crash detected syncdaemon
Tue Sep 24 09:52:46 PDT 2013 crash report /var/crash/
ubuntuone-
Most of the other crash.log files look the same except for ubuntuone- syncdaemon.
$ zcat update- notifier- crash-_ var_crash_ _usr_lib_ ubuntuone- client_ ubuntuone- syncdaemon. 1000.crash. log.1.gz _usr_lib_ ubuntuone- client_ ubuntuone- syncdaemon. 1000.crash detected syncdaemon
Tue Sep 24 09:48:04 PDT 2013 crash report /var/crash/
ubuntuone-
(apport-gtk:2718): Gtk-WARNING **: Theme parsing error: gtk-widgets. css:1605: 38: '' is not a valid color name _usr_lib_ ubuntuone- client_ ubuntuone- syncdaemon. 1000.crash detected syncdaemon
Tue Sep 24 09:52:46 PDT 2013 crash report /var/crash/
ubuntuone-
One is from before the reboot after the kernel oops and the other is after it.
The contents of the linux crash log file are also interesting:
$ cat update- notifier- crash-_ var_crash_ linux-image- 3.9.0-030900- generic. 229283. crash.log linux-image- 3.9.0-030900- generic. 229283. crash detected syncdaemon
Tue Sep 24 09:52:46 PDT 2013 crash report /var/crash/
ubuntuone-
so the linux*.crash file was detected but it remains unmodified for some reason.