Launchpad itself

Duplicate Bug of Bug that no longer exists

Asked by jamonit

I continue to have almost daily crashes in Ubuntu 12.10 caused by package 'colord 0.1.16-2'. It tells me this bug is a duplicate of #984685. When I click on https://bugs.launchpad.net/bugs/984685, I'm told the page does not exist. I'm assuming the page does not exist because the bug was fixed? Is this true? If so, and if I keep getting the bug while keeping my 12.10 version updated, how can I reopen a *new* bug for the issue I'm experiencing? Thanks for any and ALL help!

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Eliah Kagan (degeneracypressure) said : 		#1

The message you're probably seeing is:

"This page does not exist, or you may not have permission to see it."

This is happening because you don't have permission to view the bug of which your bug is a duplicate. This, in turn, is happening because that bug is marked private, to protect the personal data of the person who reported it. (When you report a crash bug, it's private by default until you change it or a bug triager or bot removes/examines attachments that might contain sensitive data like passwords and encryption/network keys.)

Revision history for this message
jamonit (jcmaynard) said : 		#2

So, I'm basically S.O.L. until that original submitter removes the private attachment or it somehow gets fixed...some day?

Revision history for this message
Eliah Kagan (degeneracypressure) said : 		#3

The submitted can mark the bug private without removing anything, and bug triagers can remove the attachment--so can bots. Since you're having the bug in Quantal, it might see quite a bit of activity in a short time and become public soon. (But it might not.) Also, please note that while it is not usually preferred, it is considered acceptable for a bug to be private for its entire lifetime. So even when the bug is fixed, you might not be able to access it. That's not very likely though, because when multiple users are experiencing a bug that has to stay private, the private bug will usually eventually be marked as a duplicate of one of the public bugs. (Unless the other bugs are private too, of course.)

That your bug has been marked a duplicate of a private bug does not mean it is being ignored or that you have not effectively contributed to the bug fixing process. The triagers and developers who can see the private bug can almost always see your bug too (even if your bug is private also) and can look at the information it contains.

See these resources for more information about private bugs:

https://help.launchpad.net/Bugs/PrivateBugs
https://wiki.ubuntu.com/Bugs/HowToTriage
https://wiki.ubuntu.com/Apport

The confusing and somewhat annoying situation you're experiencing has been noticed by others, too, and there is a discussion of it and related issues at https://bugs.launchpad.net/launchpad/+bug/434733. You can subscribe to that bug and use the green "This bug affects me" link near the top of the page. Both these actions will show increased community interest in and concern about this matter.

Revision history for this message
Eliah Kagan (degeneracypressure) said : 		#4

Correction: The submittER can mark the bug PUBLIC without removing anything...

Revision history for this message
jamonit (jcmaynard) said : 		#5

Okay. I'll just wait and see...thanks!

Can you help with this problem?

Provide an answer of your own, or ask jamonit for more information if necessary.

To post a message you must log in.