Apport

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

Bug #944756 reported by Matthew Paul Thomas
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Apport
Confirmed
Low
Unassigned
apport (Ubuntu)
Invalid
Medium
Unassigned

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." <https://wiki.ubuntu.com/ErrorTracker#details>

See also bug 349077 for apport-cli.

See original description
Revision history for this message
Matthew Paul Thomas (mpt) wrote :
Matthew Paul Thomas (mpt)
description: updated
Rick Spencer (rick-rickspencer3)
Changed in apport (Ubuntu):
importance: Undecided → Medium
assignee: nobody → Evan Dandrea (ev)
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in apport (Ubuntu):
status: New → Confirmed
Revision history for this message
Haggai Eran (haggai-eran) wrote :

Hi,

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

Revision history for this message
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.

Revision history for this message
Evan (ev) wrote :

"When apport." Thanks iOS autocorrect.

Evan (ev)
tags: added: whoopsie-daisy
Revision history for this message
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
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

Why would we be showing it again?

Revision history for this message
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.

Revision history for this message
Evan (ev) wrote :

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

Evan (ev)
Changed in apport (Ubuntu):
assignee: Evan Dandrea (ev) → nobody
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in apport (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you.

Changed in apport (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.