Ah.. I see now, what you mean.. somehow I've missed your "sometimes" and
looked not carefully enough at the logs.
E.g. from apport.log.1:
apport (pid 16956) Thu Apr 10 00:37:47 2008: executable:
/usr/bin/epiphany-gecko (command line "epiphany-browser")
modinfo: could not open cdrom: No such device
apport (pid 16956) Thu Apr 10 00:39:04 2008: wrote report
/var/crash/_usr_bin_epiphany-gecko.1000.crash
apport (pid 18265) Thu Apr 10 00:58:21 2008: called for pid 17390, signal 11
apport (pid 18265) Thu Apr 10 00:58:21 2008: executable:
/usr/bin/epiphany-gecko (command line "epiphany-browser")
apport (pid 18726) Thu Apr 10 01:08:20 2008: called for pid 18268, signal 11
apport (pid 18726) Thu Apr 10 01:08:20 2008: executable:
/usr/bin/epiphany-gecko (command line "epiphany-browser")
apport (pid 18769) Thu Apr 10 01:08:40 2008: called for pid 18733, signal 11
apport (pid 18769) Thu Apr 10 01:08:40 2008: executable:
/usr/bin/epiphany-gecko (command line "epiphany-browser")
apport (pid 19178) Thu Apr 10 01:17:45 2008: called for pid 18776, signal 11
apport (pid 19178) Thu Apr 10 01:17:45 2008: executable:
/usr/bin/epiphany-gecko (command line "epiphany-browser")
apport (pid 19333) Thu Apr 10 01:20:51 2008: called for pid 19185, signal 11
apport (pid 19333) Thu Apr 10 01:20:51 2008: executable:
/usr/bin/epiphany-gecko (command line "epiphany-browser")
apport (pid 19758) Thu Apr 10 01:30:24 2008: called for pid 19340, signal 11
apport (pid 19758) Thu Apr 10 01:30:24 2008: executable:
/usr/bin/epiphany-gecko (command line "epiphany-browser")
apport (pid 19867) Thu Apr 10 01:32:15 2008: called for pid 19769, signal 11
apport (pid 19867) Thu Apr 10 01:32:15 2008: executable:
/usr/bin/epiphany-gecko (command line "epiphany-browser")
apport (pid 20190) Thu Apr 10 01:39:40 2008: called for pid 19870, signal 11
apport (pid 20190) Thu Apr 10 01:39:40 2008: executable:
/usr/bin/epiphany-gecko (command line "epiphany-browser")
apport (pid 20233) Thu Apr 10 01:40:03 2008: called for pid 20193, signal 11
apport (pid 20233) Thu Apr 10 01:40:03 2008: executable:
/usr/bin/epiphany-gecko (command line "epiphany-browser")
apport (pid 20596) Thu Apr 10 01:48:03 2008: called for pid 20236, signal 11
apport (pid 20596) Thu Apr 10 01:48:03 2008: executable:
/usr/bin/epiphany-gecko (command line "epiphany-browser")
apport (pid 20951) Thu Apr 10 01:50:34 2008: called for pid 20599, signal 11
apport (pid 20951) Thu Apr 10 01:50:34 2008: executable:
/usr/bin/epiphany-gecko (command line "epiphany-browser")
apport (pid 21928) Thu Apr 10 02:11:06 2008: called for pid 20956, signal 11
apport (pid 21928) Thu Apr 10 02:11:06 2008: executable:
/usr/bin/epiphany-gecko (command line "epiphany-browser")
..it does not create new crash files for the latter crashes.
But does so again later:
apport (pid 18143) Thu Apr 10 23:04:54 2008: called for pid 6669, signal 11
apport (pid 18143) Thu Apr 10 23:04:54 2008: executable:
/usr/bin/epiphany-gecko (command line "epiphany-browser")
modinfo: could not open cdrom: No such device
apport (pid 18143) Thu Apr 10 23:06:35 2008: wrote report
/var/crash/_usr_bin_epiphany-gecko.1000.crash
I don't know enough about apport (yet), but there should be all info in this
report now for a developer to look at it.
I could imagine, that this is by design (e.g. the same crash and apport knows
it has been submitted), but then there should be something in the log about it.
** Changed in: apport (Ubuntu)
Importance: Undecided => Medium
Assignee: Daniel Hahler (blueyed) => (unassigned)
Status: Incomplete => Triaged
** Summary changed:
- apport does not catch crashes
+ apport does not catch crashes sometimes
--
apport does not catch crashes sometimes
https://bugs.launchpad.net/bugs/215381
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
