System Program Problem Dectected - Never Solved
I am using Xubuntu 18 and receive the above mentioned message after every single boot up.
I have read all the links to similar questions, but it bothers me that continues to go on without being addressed directly by Ubuntu.
The only "solution" appears to be to apply sudo rm /var/crash/* in a terminal. I guess people don't get it that this only removes a possible link to the message. It does nothing to:
- Display and describe the actual problem,
- Show what is being reported,
- Explain why it continually pops up,
- or other(?) possibilities
An example of this is at the posting at No Details. Another is at Details regarding
Also, note the comments from Regular problem:
> It is disturbing that old crash reports can trigger more crash reports
> If the developers don't want people to disable error reporting, they should probably make it work right. This seems to be a long-existing and very visible bug.
> ... error message boxes that do not provide the slightest hint as to what error has happened (or how to find out more about that error) are not a desirable solution
It was disturbing to realize that the Ubuntu also has the security problems listed at Security Issues. That would indicate that the problems go much deeper.
I just wish I knew why such fundamental issues are allowed to continue to confuse the average user.
Why the inability or lack of concern to fix the problem? Why is there no feedback from developers when these reports are made? Are they ever fixed? Why did reporting get less detailed with later OS versions? That seems counter-intuitive. Why aren't associated log details clearly displayed and explained when proposing a report be sent?
Here was a good one: one commentor recommended to use Log File Viewer, but of course no such program exists on my menu. I probably wouldn't know what to look for if I had access to that program since viewers are often just a long listing of code information.
We really don't need more new OS versions. IMHO, Ubuntu must just do better with the basics.
xubuntu notification error-handling
asked 2 hours ago
SearcherSearcher
16
add a comment |
I am using Xubuntu 18 and receive the above mentioned message after every single boot up.
I have read all the links to similar questions, but it bothers me that continues to go on without being addressed directly by Ubuntu.
The only "solution" appears to be to apply sudo rm /var/crash/* in a terminal. I guess people don't get it that this only removes a possible link to the message. It does nothing to:
- Display and describe the actual problem,
- Show what is being reported,
- Explain why it continually pops up,
- or other(?) possibilities
An example of this is at the posting at No Details. Another is at Details regarding
Also, note the comments from Regular problem:
> It is disturbing that old crash reports can trigger more crash reports
> If the developers don't want people to disable error reporting, they should probably make it work right. This seems to be a long-existing and very visible bug.
> ... error message boxes that do not provide the slightest hint as to what error has happened (or how to find out more about that error) are not a desirable solution
It was disturbing to realize that the Ubuntu also has the security problems listed at Security Issues. That would indicate that the problems go much deeper.
I just wish I knew why such fundamental issues are allowed to continue to confuse the average user.
Why the inability or lack of concern to fix the problem? Why is there no feedback from developers when these reports are made? Are they ever fixed? Why did reporting get less detailed with later OS versions? That seems counter-intuitive. Why aren't associated log details clearly displayed and explained when proposing a report be sent?
Here was a good one: one commentor recommended to use Log File Viewer, but of course no such program exists on my menu. I probably wouldn't know what to look for if I had access to that program since viewers are often just a long listing of code information.
We really don't need more new OS versions. IMHO, Ubuntu must just do better with the basics.
xubuntu notification error-handling
asked 2 hours ago
SearcherSearcher
16
2
I'm voting to close this question as off-topic because it's too close to be a rant in disguise (askubuntu.com/help/dont-ask). This site is so users can help other users, and not developers anyway. Launchpad is for bug reporting & requests to developers (wish-list)
– guiverc
2 hours ago
If you want to peruse the actual errors & reports; they are located on your system in /var/crash/ - go and look and you'll see exactly what gets sent upstream. I did a search in my 'menu' for 'logs' & then got a log-viewer. You mention Xubuntu 18, but there is only Ubuntu Core 18 - yy or yearly releases are releases intended for specialized devices (like IoT), Xubuntu has only yy.mm format releases. I see no example of anything that was sent to a developer, but only user to user (askubu). Most reports are duplicate so they primarily add 'heat' to bug. Xubuntu is community supported, so
– guiverc
2 hours ago
It helps to prepare the bug report report carefully and include any missing information that was not generated automatically in the bug report. I usually get email replies including follow-up emails from subscribers to the bug after submitting a bug report.
– karel
2 hours ago
add a comment |
I am using Xubuntu 18 and receive the above mentioned message after every single boot up.
I have read all the links to similar questions, but it bothers me that continues to go on without being addressed directly by Ubuntu.
The only "solution" appears to be to apply sudo rm /var/crash/* in a terminal. I guess people don't get it that this only removes a possible link to the message. It does nothing to:
- Display and describe the actual problem,
- Show what is being reported,
- Explain why it continually pops up,
- or other(?) possibilities
An example of this is at the posting at No Details. Another is at Details regarding
Also, note the comments from Regular problem:
> It is disturbing that old crash reports can trigger more crash reports
> If the developers don't want people to disable error reporting, they should probably make it work right. This seems to be a long-existing and very visible bug.
> ... error message boxes that do not provide the slightest hint as to what error has happened (or how to find out more about that error) are not a desirable solution
It was disturbing to realize that the Ubuntu also has the security problems listed at Security Issues. That would indicate that the problems go much deeper.
I just wish I knew why such fundamental issues are allowed to continue to confuse the average user.
Why the inability or lack of concern to fix the problem? Why is there no feedback from developers when these reports are made? Are they ever fixed? Why did reporting get less detailed with later OS versions? That seems counter-intuitive. Why aren't associated log details clearly displayed and explained when proposing a report be sent?
Here was a good one: one commentor recommended to use Log File Viewer, but of course no such program exists on my menu. I probably wouldn't know what to look for if I had access to that program since viewers are often just a long listing of code information.
We really don't need more new OS versions. IMHO, Ubuntu must just do better with the basics.
xubuntu notification error-handling
asked 2 hours ago
SearcherSearcher
16
I am using Xubuntu 18 and receive the above mentioned message after every single boot up.
I have read all the links to similar questions, but it bothers me that continues to go on without being addressed directly by Ubuntu.
The only "solution" appears to be to apply sudo rm /var/crash/* in a terminal. I guess people don't get it that this only removes a possible link to the message. It does nothing to:
- Display and describe the actual problem,
- Show what is being reported,
- Explain why it continually pops up,
- or other(?) possibilities
An example of this is at the posting at No Details. Another is at Details regarding
Also, note the comments from Regular problem:
> It is disturbing that old crash reports can trigger more crash reports
> If the developers don't want people to disable error reporting, they should probably make it work right. This seems to be a long-existing and very visible bug.
> ... error message boxes that do not provide the slightest hint as to what error has happened (or how to find out more about that error) are not a desirable solution
It was disturbing to realize that the Ubuntu also has the security problems listed at Security Issues. That would indicate that the problems go much deeper.
I just wish I knew why such fundamental issues are allowed to continue to confuse the average user.
Why the inability or lack of concern to fix the problem? Why is there no feedback from developers when these reports are made? Are they ever fixed? Why did reporting get less detailed with later OS versions? That seems counter-intuitive. Why aren't associated log details clearly displayed and explained when proposing a report be sent?
Here was a good one: one commentor recommended to use Log File Viewer, but of course no such program exists on my menu. I probably wouldn't know what to look for if I had access to that program since viewers are often just a long listing of code information.
We really don't need more new OS versions. IMHO, Ubuntu must just do better with the basics.
xubuntu notification error-handling
xubuntu notification error-handling
asked 2 hours ago
SearcherSearcher
16
asked 2 hours ago
SearcherSearcher
16
asked 2 hours ago
SearcherSearcher
16
asked 2 hours ago
SearcherSearcher
16
asked 2 hours ago
SearcherSearcher
16
16
2
I'm voting to close this question as off-topic because it's too close to be a rant in disguise (askubuntu.com/help/dont-ask). This site is so users can help other users, and not developers anyway. Launchpad is for bug reporting & requests to developers (wish-list)
– guiverc
2 hours ago
If you want to peruse the actual errors & reports; they are located on your system in /var/crash/ - go and look and you'll see exactly what gets sent upstream. I did a search in my 'menu' for 'logs' & then got a log-viewer. You mention Xubuntu 18, but there is only Ubuntu Core 18 - yy or yearly releases are releases intended for specialized devices (like IoT), Xubuntu has only yy.mm format releases. I see no example of anything that was sent to a developer, but only user to user (askubu). Most reports are duplicate so they primarily add 'heat' to bug. Xubuntu is community supported, so
– guiverc
2 hours ago
It helps to prepare the bug report report carefully and include any missing information that was not generated automatically in the bug report. I usually get email replies including follow-up emails from subscribers to the bug after submitting a bug report.
– karel
2 hours ago
add a comment |
2
I'm voting to close this question as off-topic because it's too close to be a rant in disguise (askubuntu.com/help/dont-ask). This site is so users can help other users, and not developers anyway. Launchpad is for bug reporting & requests to developers (wish-list)
– guiverc
2 hours ago
If you want to peruse the actual errors & reports; they are located on your system in /var/crash/ - go and look and you'll see exactly what gets sent upstream. I did a search in my 'menu' for 'logs' & then got a log-viewer. You mention Xubuntu 18, but there is only Ubuntu Core 18 - yy or yearly releases are releases intended for specialized devices (like IoT), Xubuntu has only yy.mm format releases. I see no example of anything that was sent to a developer, but only user to user (askubu). Most reports are duplicate so they primarily add 'heat' to bug. Xubuntu is community supported, so
– guiverc
2 hours ago
It helps to prepare the bug report report carefully and include any missing information that was not generated automatically in the bug report. I usually get email replies including follow-up emails from subscribers to the bug after submitting a bug report.
– karel
2 hours ago
2
2
I'm voting to close this question as off-topic because it's too close to be a rant in disguise (askubuntu.com/help/dont-ask). This site is so users can help other users, and not developers anyway. Launchpad is for bug reporting & requests to developers (wish-list)
– guiverc
2 hours ago
I'm voting to close this question as off-topic because it's too close to be a rant in disguise (askubuntu.com/help/dont-ask). This site is so users can help other users, and not developers anyway. Launchpad is for bug reporting & requests to developers (wish-list)
– guiverc
2 hours ago
If you want to peruse the actual errors & reports; they are located on your system in /var/crash/ - go and look and you'll see exactly what gets sent upstream. I did a search in my 'menu' for 'logs' & then got a log-viewer. You mention Xubuntu 18, but there is only Ubuntu Core 18 - yy or yearly releases are releases intended for specialized devices (like IoT), Xubuntu has only yy.mm format releases. I see no example of anything that was sent to a developer, but only user to user (askubu). Most reports are duplicate so they primarily add 'heat' to bug. Xubuntu is community supported, so
– guiverc
2 hours ago
If you want to peruse the actual errors & reports; they are located on your system in /var/crash/ - go and look and you'll see exactly what gets sent upstream. I did a search in my 'menu' for 'logs' & then got a log-viewer. You mention Xubuntu 18, but there is only Ubuntu Core 18 - yy or yearly releases are releases intended for specialized devices (like IoT), Xubuntu has only yy.mm format releases. I see no example of anything that was sent to a developer, but only user to user (askubu). Most reports are duplicate so they primarily add 'heat' to bug. Xubuntu is community supported, so
– guiverc
2 hours ago
It helps to prepare the bug report report carefully and include any missing information that was not generated automatically in the bug report. I usually get email replies including follow-up emails from subscribers to the bug after submitting a bug report.
– karel
2 hours ago
It helps to prepare the bug report report carefully and include any missing information that was not generated automatically in the bug report. I usually get email replies including follow-up emails from subscribers to the bug after submitting a bug report.
– karel
2 hours ago
add a comment |
0
active
oldest
votes
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%2f1128667%2fsystem-program-problem-dectected-never-solved%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f1128667%2fsystem-program-problem-dectected-never-solved%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
2
I'm voting to close this question as off-topic because it's too close to be a rant in disguise (askubuntu.com/help/dont-ask). This site is so users can help other users, and not developers anyway. Launchpad is for bug reporting & requests to developers (wish-list)
– guiverc
2 hours ago
If you want to peruse the actual errors & reports; they are located on your system in /var/crash/ - go and look and you'll see exactly what gets sent upstream. I did a search in my 'menu' for 'logs' & then got a log-viewer. You mention Xubuntu 18, but there is only Ubuntu Core 18 - yy or yearly releases are releases intended for specialized devices (like IoT), Xubuntu has only yy.mm format releases. I see no example of anything that was sent to a developer, but only user to user (askubu). Most reports are duplicate so they primarily add 'heat' to bug. Xubuntu is community supported, so
– guiverc
2 hours ago
It helps to prepare the bug report report carefully and include any missing information that was not generated automatically in the bug report. I usually get email replies including follow-up emails from subscribers to the bug after submitting a bug report.
– karel
2 hours ago