How can I report a bug when ubuntu-bug crashes?
ongun@ongun-ubuntu:~$ ubuntu-bug python ERROR: /etc/apport/crashdb.conf is damaged: No default database
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It only takes a minute to sign up.Sign up to join this community
I don't know if the specific error described here is due to a bug or misconfiguration or some other problem. Users who see that exact message should try the workaround Rinzwind described. Somewhat more generally, though not applicable to the error message shown here, the
apport-cli command will sometimes work when
But the answer to "How can I report a bug when ubuntu-bug crashes?" (or otherwise cannot be used) is that bugs can be reported directly via Launchpad's web interface, and that such a bug report may be useful so long as the reporter describes the problem carefully and meticulously includes all information reasonably related to it.
There are two major cases.
If you're reporting a non-crash bug by running
ubuntu-bug package, then Apport wouldn't attach a stack trace and core dump to the bug report anyway. So it's reasonable to report the bug directly on Launchpad. As its_me's answer to How do I report a bug? says:
It's as easy as visiting Launchpad and filling the 2 or 3 fields that are there. Command line is not the only way.
Alternatively, you can use this (replace
PACKAGENAMEin the URL with the package name. For example: unity, gnome-shell, etc):
It's mentioned in the Ubuntu documentation.
That applies directly to the situation described in this question. Just make sure to include enough information to fully describe the bug, the system on which the bug occurs, and the packages relevant to the bug, including their exact versions. As always, users reporting bugs this way should first read ReportingBugs.
Reporting a bug that causes a crash without Apport is more laborious, but it can be done in the traditional manner. This consists of installing debug symbols for the program that crashed and the libraries it uses, opening the program in a debugger (for Ubuntu packages,
gdb should typically be used), then attempting to reproduce the crash. The resulting stack trace, produced by running
gdb after the crash, should be usable so long as all the relevant debug symbols were available.
This isn't the situation described in the question here, and I don't intend to cover it thoroughly. I mainly mention it so readers who are trying to report crashes don't use the approach mentioned above without also including a stack trace. But basically, some packages have corresponding debug symbols in similarly named packages whose names end in
-dbg, and most others have debug symbol packages available from separate repositories that can be enabled and used as described in Debug Symbol Packages.
If you follow this method, and then decide to add files in the same way as you would by
ubuntu-bugmethod, you can simply type
apport-collect REPORTNUMBER, where REPORTNUMBER is the number of the bug, that will be in the URL of your submitted [bug].
This is most useful for crash bugs where there are stack trace and core dump files in
/var/crash to attach.
As mentioned in the bug report in comments this seems to be a a "locale" issue.
LC_ALL=C ubuntu-bug python