| 2007-02-05 11:48:10 |
Martin Pitt |
apport: statusexplanation |
|
Indeed apport only considers crashes which belong to programs in /usr/bin, /usr/lib, etc. If I crash a program in /tmp or in my home directory, apport does:
apport (pid 29130) Mon Feb 5 12:47:05 2007: executable: /tmp/test (command line "./test")
apport (pid 29130) Mon Feb 5 12:47:05 2007: executable does not belong to a package, ignoring
Where did you build/run this test program? |
|
| 2007-02-09 13:38:36 |
Martin Pitt |
apport: statusexplanation |
Indeed apport only considers crashes which belong to programs in /usr/bin, /usr/lib, etc. If I crash a program in /tmp or in my home directory, apport does:
apport (pid 29130) Mon Feb 5 12:47:05 2007: executable: /tmp/test (command line "./test")
apport (pid 29130) Mon Feb 5 12:47:05 2007: executable does not belong to a package, ignoring
Where did you build/run this test program? |
Ah, I see. When apport runs, it does not check the dpkg database for the originin of the executuable, it just applies some heuristics (checking dpkg takes ages).
And since /usr is reserved for distro packages (you should put custom stuff into /usr/local/), this usually does the right thing.
Not displaying the dialog would be confusing if you previously got a bomb icon in update-notifier. It's a bit tricky to get this right. |
|
