And nearly 13 years later, we are still here.
If I have a core file in the Current directory and another run of the
program encounters a fault, the old core (possibly months old) prevents
the current core file from being written. Outstanding!
--
You received this bug notification because you
Same problem here!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/160999
Title:
Apport doesn't overwrite existing core files
Status in apport package in Ubuntu:
** Changed in: apport (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/160999
Title:
Apport doesn't overwrite existing core
@k04jg02, as noted in comment #7, this bug has no effect on the Ubuntu
Error Reporting process for software that is distributed through normal
channels.
Instead, for software that comes from any other source, apport seems to
make a 'best-efforts' approach to dump a core file, roughly following
9 years later and still broken! Can confirm still exists in 16.04. Does
no one develop on Ubuntu or has every developer in the last nine years
manually removed apport?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in
5 matches
Mail list logo
