Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am suffering from a bug/crash in Natty, which I have logged in Launchpad:

The response I got back on my bug was a "provide us with a .crash file, or we won't look into it". Not very helpful really, but I can understand that the developers need something to work with. I have checked for this .crash file, which I can provide, but it isn't there.

So, my question is, what else can I provide/do in order to get this bug looked at and fixed?

It can't be a specific problem as it happens to both my 32bit laptop and my 64bit desktop, both being very different machines, and it is stopping me from connecting to my development & backup network machines so I can't do my work...

It turns out that I had to replicate the bug a number of times before I finally got promoted to report it by Apport. It would be nice, though, if there was a simpler way.

share|improve this question
up vote 2 down vote accepted

I find some of the Unity bug filing a bit brusque too, such as using "Incomplete" to mean "we haven't decided how to fix this yet" even though it is a real bug.

If you have a hang/crash bug, one good way to get some more data is to run strace on the process in question, with eg

strace -ff -o /tmp/unity.strace -p UNITY_PID

(after finding the right pid), then attach that file to the bug. I can't promise they'll accept it but for things I work on that's often helpful.

share|improve this answer

This can be frustrating as I've had to file a few bugs by hand using the advanced debugging procedures here:

I was having a particularly bad crasher so I had to open the web page on my laptop (or you can print it out or something), then get it to crash, then follow the procedures and then file a bug and attach the log.

share|improve this answer

You need to enable Apport - details on how to do this are found on the Ubuntu Wiki here

share|improve this answer
That is my point though, Apport is enabled but it isn't picking up on the crash. Usually I'd get a dialog telling me that the system died, but not in this case. – Valorin Mar 19 '11 at 21:49
Did you read through the how to guide at – Mark Rooney Mar 19 '11 at 22:16
That appears to be for application developers to get Apport reporting correctly, not end users who have nothing to do with the application's development. – Valorin Mar 19 '11 at 23:38

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.