What happens when I click “Send” after Ubuntu experienced an internal error?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I am using Ubuntu 18.10. Sometimes, when some program has just crashed, a window pops up saying the following:
"Sorry, Ubuntu 18.10 has experienced an internal error. Send problem report to the developers?"
Then there are three buttons: "Show details", "Don't send" and "Send".
If I click "Show details" then it does show details nicely, for example that "gjs-console crashed with SIGABRT" and lots of other info. It seems like a good idea to send this to the developers, so I click "Send". Then the window is closed. I do not get any confirmation that anything was actually sent. I would have liked to get some confirmation like "OK, problem report sent successfully" or something but there is no such confirmation so I am a little worried that something went wrong when I clicked the "Send" button.
My questions:
- Is anything actually sent to the developers?
- Is there any way for me to verify that something was actually sent?
- Can I even see the details of the resulting automatically generated problem report in a public bug tracking system somewhere?
EDIT: according to an answer here: How can I find my Bug-report on launchpad that I submitted from the Desktop? it should be possible to see the resulting bug report by going to https://bugs.launchpad.net/~/+reportedbugs but that does not work for me -- that page just says "There are currently no open bugs."
So I am still not sure if any problem report was really sent and if so, where did it end up.
EDIT 2: this seems related also: How can I track a bug that caused a crash and was reported via apport / whoopsie? but after reading that I still donät know how to verify if a problem report was really sent.
18.10 bug-reporting
add a comment |
I am using Ubuntu 18.10. Sometimes, when some program has just crashed, a window pops up saying the following:
"Sorry, Ubuntu 18.10 has experienced an internal error. Send problem report to the developers?"
Then there are three buttons: "Show details", "Don't send" and "Send".
If I click "Show details" then it does show details nicely, for example that "gjs-console crashed with SIGABRT" and lots of other info. It seems like a good idea to send this to the developers, so I click "Send". Then the window is closed. I do not get any confirmation that anything was actually sent. I would have liked to get some confirmation like "OK, problem report sent successfully" or something but there is no such confirmation so I am a little worried that something went wrong when I clicked the "Send" button.
My questions:
- Is anything actually sent to the developers?
- Is there any way for me to verify that something was actually sent?
- Can I even see the details of the resulting automatically generated problem report in a public bug tracking system somewhere?
EDIT: according to an answer here: How can I find my Bug-report on launchpad that I submitted from the Desktop? it should be possible to see the resulting bug report by going to https://bugs.launchpad.net/~/+reportedbugs but that does not work for me -- that page just says "There are currently no open bugs."
So I am still not sure if any problem report was really sent and if so, where did it end up.
EDIT 2: this seems related also: How can I track a bug that caused a crash and was reported via apport / whoopsie? but after reading that I still donät know how to verify if a problem report was really sent.
18.10 bug-reporting
add a comment |
I am using Ubuntu 18.10. Sometimes, when some program has just crashed, a window pops up saying the following:
"Sorry, Ubuntu 18.10 has experienced an internal error. Send problem report to the developers?"
Then there are three buttons: "Show details", "Don't send" and "Send".
If I click "Show details" then it does show details nicely, for example that "gjs-console crashed with SIGABRT" and lots of other info. It seems like a good idea to send this to the developers, so I click "Send". Then the window is closed. I do not get any confirmation that anything was actually sent. I would have liked to get some confirmation like "OK, problem report sent successfully" or something but there is no such confirmation so I am a little worried that something went wrong when I clicked the "Send" button.
My questions:
- Is anything actually sent to the developers?
- Is there any way for me to verify that something was actually sent?
- Can I even see the details of the resulting automatically generated problem report in a public bug tracking system somewhere?
EDIT: according to an answer here: How can I find my Bug-report on launchpad that I submitted from the Desktop? it should be possible to see the resulting bug report by going to https://bugs.launchpad.net/~/+reportedbugs but that does not work for me -- that page just says "There are currently no open bugs."
So I am still not sure if any problem report was really sent and if so, where did it end up.
EDIT 2: this seems related also: How can I track a bug that caused a crash and was reported via apport / whoopsie? but after reading that I still donät know how to verify if a problem report was really sent.
18.10 bug-reporting
I am using Ubuntu 18.10. Sometimes, when some program has just crashed, a window pops up saying the following:
"Sorry, Ubuntu 18.10 has experienced an internal error. Send problem report to the developers?"
Then there are three buttons: "Show details", "Don't send" and "Send".
If I click "Show details" then it does show details nicely, for example that "gjs-console crashed with SIGABRT" and lots of other info. It seems like a good idea to send this to the developers, so I click "Send". Then the window is closed. I do not get any confirmation that anything was actually sent. I would have liked to get some confirmation like "OK, problem report sent successfully" or something but there is no such confirmation so I am a little worried that something went wrong when I clicked the "Send" button.
My questions:
- Is anything actually sent to the developers?
- Is there any way for me to verify that something was actually sent?
- Can I even see the details of the resulting automatically generated problem report in a public bug tracking system somewhere?
EDIT: according to an answer here: How can I find my Bug-report on launchpad that I submitted from the Desktop? it should be possible to see the resulting bug report by going to https://bugs.launchpad.net/~/+reportedbugs but that does not work for me -- that page just says "There are currently no open bugs."
So I am still not sure if any problem report was really sent and if so, where did it end up.
EDIT 2: this seems related also: How can I track a bug that caused a crash and was reported via apport / whoopsie? but after reading that I still donät know how to verify if a problem report was really sent.
18.10 bug-reporting
18.10 bug-reporting
edited Mar 22 at 20:50
Elias
asked Mar 22 at 10:31
EliasElias
966
966
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
If I am right, the information lands here:
https://errors.ubuntu.com/
They do a lot of thinking work:
https://wiki.ubuntu.com/AutomatedProblemReports
It seems the best solution so far is Apport with whoopsie. But the Documentation says disabled by default.
https://wiki.ubuntu.com/Apport
I think this is more a concept, but looks like your Idea (tell the User an ID) is already covered:
https://wiki.ubuntu.com/ErrorTracker
All together the Error Reports are collected and one main issue to solve is to automatic group the entries. Beside the issue with sensitive data in the report, but this is less fun.
add a comment |
Usually, the system collects system logs, timestamps when an error occurred and additional information regarding which module failed.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f1127780%2fwhat-happens-when-i-click-send-after-ubuntu-experienced-an-internal-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
If I am right, the information lands here:
https://errors.ubuntu.com/
They do a lot of thinking work:
https://wiki.ubuntu.com/AutomatedProblemReports
It seems the best solution so far is Apport with whoopsie. But the Documentation says disabled by default.
https://wiki.ubuntu.com/Apport
I think this is more a concept, but looks like your Idea (tell the User an ID) is already covered:
https://wiki.ubuntu.com/ErrorTracker
All together the Error Reports are collected and one main issue to solve is to automatic group the entries. Beside the issue with sensitive data in the report, but this is less fun.
add a comment |
If I am right, the information lands here:
https://errors.ubuntu.com/
They do a lot of thinking work:
https://wiki.ubuntu.com/AutomatedProblemReports
It seems the best solution so far is Apport with whoopsie. But the Documentation says disabled by default.
https://wiki.ubuntu.com/Apport
I think this is more a concept, but looks like your Idea (tell the User an ID) is already covered:
https://wiki.ubuntu.com/ErrorTracker
All together the Error Reports are collected and one main issue to solve is to automatic group the entries. Beside the issue with sensitive data in the report, but this is less fun.
add a comment |
If I am right, the information lands here:
https://errors.ubuntu.com/
They do a lot of thinking work:
https://wiki.ubuntu.com/AutomatedProblemReports
It seems the best solution so far is Apport with whoopsie. But the Documentation says disabled by default.
https://wiki.ubuntu.com/Apport
I think this is more a concept, but looks like your Idea (tell the User an ID) is already covered:
https://wiki.ubuntu.com/ErrorTracker
All together the Error Reports are collected and one main issue to solve is to automatic group the entries. Beside the issue with sensitive data in the report, but this is less fun.
If I am right, the information lands here:
https://errors.ubuntu.com/
They do a lot of thinking work:
https://wiki.ubuntu.com/AutomatedProblemReports
It seems the best solution so far is Apport with whoopsie. But the Documentation says disabled by default.
https://wiki.ubuntu.com/Apport
I think this is more a concept, but looks like your Idea (tell the User an ID) is already covered:
https://wiki.ubuntu.com/ErrorTracker
All together the Error Reports are collected and one main issue to solve is to automatic group the entries. Beside the issue with sensitive data in the report, but this is less fun.
answered Mar 22 at 11:01
LupusELupusE
1197
1197
add a comment |
add a comment |
Usually, the system collects system logs, timestamps when an error occurred and additional information regarding which module failed.
add a comment |
Usually, the system collects system logs, timestamps when an error occurred and additional information regarding which module failed.
add a comment |
Usually, the system collects system logs, timestamps when an error occurred and additional information regarding which module failed.
Usually, the system collects system logs, timestamps when an error occurred and additional information regarding which module failed.
answered Mar 22 at 12:18
skoch13skoch13
242
242
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.
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%2f1127780%2fwhat-happens-when-i-click-send-after-ubuntu-experienced-an-internal-error%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