Launchpad.net : “Lost something?”
up vote
1
down vote
favorite
I used Apport to report a severe Ubuntu. When sending it, I got told something like:
The bug you are trying to report has already been reported, please click here to see it and add details to help developers.
I click, and here is what I am told:
It is very frustrating. What is happening and why?
- I have further information about this crash that I think is valuable.
- If the crash has been solved, I want to see how.
- Let's say the same crash can be caused in two ways, one benign and one devastating. If the benign way was discovered first, the crash is in limbo somewhere with low priority, this reduces the chances for a fix in the next Ubuntu release.
The problem has happened to me several times:
- https://bugs.launchpad.net/bugs/1671487
- https://bugs.launchpad.net/bugs/1720694
- https://bugs.launchpad.net/bugs/1763728
- https://bugs.launchpad.net/bugs/1765961
launchpad apport
add a comment |
up vote
1
down vote
favorite
I used Apport to report a severe Ubuntu. When sending it, I got told something like:
The bug you are trying to report has already been reported, please click here to see it and add details to help developers.
I click, and here is what I am told:
It is very frustrating. What is happening and why?
- I have further information about this crash that I think is valuable.
- If the crash has been solved, I want to see how.
- Let's say the same crash can be caused in two ways, one benign and one devastating. If the benign way was discovered first, the crash is in limbo somewhere with low priority, this reduces the chances for a fix in the next Ubuntu release.
The problem has happened to me several times:
- https://bugs.launchpad.net/bugs/1671487
- https://bugs.launchpad.net/bugs/1720694
- https://bugs.launchpad.net/bugs/1763728
- https://bugs.launchpad.net/bugs/1765961
launchpad apport
I get the same error for the number shown in your picture. I'd suggest trying to find it using keywords, package or whatever information you do have.
– guiverc
May 24 at 8:47
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I used Apport to report a severe Ubuntu. When sending it, I got told something like:
The bug you are trying to report has already been reported, please click here to see it and add details to help developers.
I click, and here is what I am told:
It is very frustrating. What is happening and why?
- I have further information about this crash that I think is valuable.
- If the crash has been solved, I want to see how.
- Let's say the same crash can be caused in two ways, one benign and one devastating. If the benign way was discovered first, the crash is in limbo somewhere with low priority, this reduces the chances for a fix in the next Ubuntu release.
The problem has happened to me several times:
- https://bugs.launchpad.net/bugs/1671487
- https://bugs.launchpad.net/bugs/1720694
- https://bugs.launchpad.net/bugs/1763728
- https://bugs.launchpad.net/bugs/1765961
launchpad apport
I used Apport to report a severe Ubuntu. When sending it, I got told something like:
The bug you are trying to report has already been reported, please click here to see it and add details to help developers.
I click, and here is what I am told:
It is very frustrating. What is happening and why?
- I have further information about this crash that I think is valuable.
- If the crash has been solved, I want to see how.
- Let's say the same crash can be caused in two ways, one benign and one devastating. If the benign way was discovered first, the crash is in limbo somewhere with low priority, this reduces the chances for a fix in the next Ubuntu release.
The problem has happened to me several times:
- https://bugs.launchpad.net/bugs/1671487
- https://bugs.launchpad.net/bugs/1720694
- https://bugs.launchpad.net/bugs/1763728
- https://bugs.launchpad.net/bugs/1765961
launchpad apport
launchpad apport
edited Dec 3 at 3:08
asked May 24 at 8:42
Nicolas Raoul
4,8001862113
4,8001862113
I get the same error for the number shown in your picture. I'd suggest trying to find it using keywords, package or whatever information you do have.
– guiverc
May 24 at 8:47
add a comment |
I get the same error for the number shown in your picture. I'd suggest trying to find it using keywords, package or whatever information you do have.
– guiverc
May 24 at 8:47
I get the same error for the number shown in your picture. I'd suggest trying to find it using keywords, package or whatever information you do have.
– guiverc
May 24 at 8:47
I get the same error for the number shown in your picture. I'd suggest trying to find it using keywords, package or whatever information you do have.
– guiverc
May 24 at 8:47
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
This happens when the bug report that apport thinks is the "primary" one for that crash is private, probably because it hasn't been reviewed for sensitive user data. It's probably best to contact the bug squad and ask them if they can make that bug public.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
This happens when the bug report that apport thinks is the "primary" one for that crash is private, probably because it hasn't been reviewed for sensitive user data. It's probably best to contact the bug squad and ask them if they can make that bug public.
add a comment |
up vote
1
down vote
This happens when the bug report that apport thinks is the "primary" one for that crash is private, probably because it hasn't been reviewed for sensitive user data. It's probably best to contact the bug squad and ask them if they can make that bug public.
add a comment |
up vote
1
down vote
up vote
1
down vote
This happens when the bug report that apport thinks is the "primary" one for that crash is private, probably because it hasn't been reviewed for sensitive user data. It's probably best to contact the bug squad and ask them if they can make that bug public.
This happens when the bug report that apport thinks is the "primary" one for that crash is private, probably because it hasn't been reviewed for sensitive user data. It's probably best to contact the bug squad and ask them if they can make that bug public.
answered Jun 25 at 13:27
Colin Watson
5,26411223
5,26411223
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1039724%2flaunchpad-net-lost-something%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I get the same error for the number shown in your picture. I'd suggest trying to find it using keywords, package or whatever information you do have.
– guiverc
May 24 at 8:47