"This problem was already reported..."

Bug #1451186 reported by teo1978
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
New
Low
Unassigned

Bug Description

Something crashed (as always) after installing Ubuntu updates, presumably due to https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1268257

A popup appeared (as usual) telling me that a problem was detected and whether I wanted to report, to which I said Yes.

Then, this message appeared (see screenshot), which says "The problem was already reported in the bug report DISPLAYED IN THE WEB BROWSER..."
No bug report was open in the browser. I waited more than a minute and no bug report was being opened in the browser.

Only after clicking on Close, did the browser finally open the related bug report.

So either:

1) this is by design, that is, the bug report is supposed to be opened after closing the popup. If this is the case then
 => the message should be rephrased, to read "in the bug report that WILL be displayed in the web browser", and instead of Close the button should read Continue or Ok.

or

2) the bug report is supposed to be opened at the same time the popup is displayed, but it takes long. If this is the case, then
 2.a => either the message should read "in the bug report that IS BEING LOADED in the web browser (this may take a few minutes)",
              OR much better
 2.b => a first popup should inform you that the bug report is being opened in the browser, with a loading/waiting indicator, and then, when it is loaded, the final message similar to the one currently displayed, should be displayed.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apport 2.14.1-0ubuntu3.10
ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
Uname: Linux 3.13.0-49-generic x86_64
ApportLog:

ApportVersion: 2.14.1-0ubuntu3.10
Architecture: amd64
CrashReports:
 640:0:110:33136:2015-05-03 14:52:36.419100999 +0200:2015-05-03 14:52:37.419100999 +0200:/var/crash/nvidia-331.0.crash
 600:106:110:0:2015-05-03 14:52:39.567100861 +0200:2015-04-27 16:38:24.687981219 +0200:/var/crash/nvidia-331.0.uploaded
 640:1000:110:1018542:2015-05-01 11:41:36.971999876 +0200:2015-05-01 11:42:00.869033693 +0200:/var/crash/_usr_bin_compiz.1000.crash
 644:0:110:0:2015-05-03 14:52:38.143100920 +0200:2015-05-03 14:52:38.143100920 +0200:/var/crash/nvidia-331.0.upload
CurrentDesktop: Unity
Date: Sun May 3 14:53:47 2015
InstallationDate: Installed on 2013-10-11 (568 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to trusty on 2014-05-24 (343 days ago)

Revision history for this message
teo1978 (teo8976) wrote :
description: updated
tags: added: string-fix
Changed in apport (Ubuntu):
status: New → Triaged
importance: Undecided → Low
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: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for apport (Ubuntu) because there has been no activity for 60 days.]

Changed in apport (Ubuntu):
status: Incomplete → Expired
Revision history for this message
teo1978 (teo8976) wrote :

> If this is still an issue on a maintained version of Ubuntu please let us know.

No, you let us know if this is confirmed to be fixed in more recent versions of Ubuntu, and if so, then close as fixed.

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

I'm so sorry this issue went unanswered for so long. The backlog we've accrued here is truly unfortunate. We'd really like to see the situation improve, but with hundreds of open bugs, manually testing each has become virtually impossible. The aim 2 months ago was to ping neglected bugs such as these and allow those still effected to put their bug back on the radar again.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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