Launchpad itself

Bug #1223417 is inaccessible although the apport retracing service marked multiple bugs a duplicates of it.

Asked by Alexander Behringer on 2013-10-11

After filing Bug #1237416 via apport, the apport retracing service marked it as duplicate of bug #1223417, which is however not accessible.

This happened to other bugs as well (#1224913, #1234566, #1237020, #1237593) which pointed to bug #1223417 before I marked them as duplicate of the bug I filed.

Accessing https://bugs.launchpad.net/bugs/1223417 produces an error with the following error ID:

OOPS-dfb010ff1e7271d11464f5defd2f5914

And clicking on the bug number produces: "Bug 1223417 cannot be found"

Is this a technical error or is bug #1223417 being marked as 'private', 'security relevant' or something similar?

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
William Grant
Solved:
2013-10-11
Last query:
2013-10-11
Last reply:
2013-10-11
Best William Grant (wgrant) said : #1

apport leaves bugs with potentially sensitive information in them private, but will still mark public bugs as duplicates of private bugs if the private one is considered the master. Bug #1223417 is one such private master bug; it has a retraced core dump with potentially sensitive variable values.

Bug #764414 asks that apport not send users into this confusing situation, for example by preferring public bugs when determining the master.

Alexander Behringer (alexander-behringer-deactivatedaccount) said : #2

From my point of view, it is OK when apport points to privat bugs. That's not the problem.

But shouldn't launchpad at least tell the user, that this bug exists (without showing any details) instead of leading the user into an error message telling him, that there is no such bug?

Alexander Behringer (alexander-behringer-deactivatedaccount) said : #3

Thanks William Grant, that solved my question.