Shows unpleasant "Cannot connect to crash database" instead of queuing for later

Bug #944756 reported by Matthew Paul Thomas on 2012-03-02
This bug affects 3 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)

Bug Description

apport 1.93-0ubuntu2, Ubuntu 12.04 alpha

1. Cause a crash.
2. Disconnect from the Internet.
3. With "Send an error report" checked, click "Continue".

What happens: An unpleasant error alert appears. It begins with a run-on sentence: "Cannot connect to crash database, please check your Internet connection." This is followed by jargon: "<urlopen error [Errno -2] Name or service not known>".

What should happen: "If you are not connected to the Internet at the time, reports should be queued. Any queued reports should be sent when you next agree to send an error report while online." <>

See also bug 349077 for apport-cli.

Matthew Paul Thomas (mpt) wrote :
description: updated
Changed in apport (Ubuntu):
importance: Undecided → Medium
assignee: nobody → Evan Dandrea (ev)
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apport (Ubuntu):
status: New → Confirmed
Haggai Eran (haggai-eran) wrote :


This happens to me even while connected to the internet. I checked and was accessible. I'm using apport 1.94.1-0ubuntu2 on precise.

Evan (ev) wrote :

To be clear, this is not a message for the crash database that is being constructed for Ubuntu. Instead, this message is displayed when apportion cannot connect to Launchpad or whatever bug database is specified in /etc/apport/crashdb.conf.

Evan (ev) wrote :

"When apport." Thanks iOS autocorrect.

Evan (ev) on 2012-11-01
tags: added: whoopsie-daisy
Evan (ev) wrote :

I'm not sure how we show in the UI that this report has been successfully sent to the crash database, but we're showing it again because we couldn't send it to Launchpad. Any ideas, Matthew?

Changed in apport:
importance: Undecided → Low
status: New → Confirmed
Matthew Paul Thomas (mpt) wrote :

Why would we be showing it again?

Matthew Paul Thomas (mpt) wrote :

From in-person discussion: Despite the wording, this is not to do with a "crash database". This is in a pre-release where you have asked Apport to help you manually report a bug from a crash, but it can't connect to the bug tracker to search for duplicates. So the message should say that the bug report isn't going to happen.

I suggest: "This bug can’t be reported because Ubuntu couldn’t connect to {name of tracker}."

For bonus points, change the "OK" button to a pair of "Cancel" and "Retry" buttons.

Evan (ev) wrote :

Where {name of tracker} is the backend implementation in Apport, often "Launchpad."

Evan (ev) on 2013-05-30
Changed in apport (Ubuntu):
assignee: Evan Dandrea (ev) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments