Ttgjyuk

How do ultrasonic sensors differentiate between transmitted and received signals?

Should my PhD thesis be submitted under my legal name?

What is the term when two people sing in harmony, but they aren't singing the same notes?

Is there any significance to the Valyrian Stone vault door of Qarth?

Did US corporations pay demonstrators in the German demonstrations against article 13?

What does the "3am" section means in manpages?

Greatest common substring

How can I successfully establish a nationwide combat training program for a large country?

How do I repair my stair bannister?

Calculating the number of days between 2 dates in Excel

Hostile work environment after whistle-blowing on coworker and our boss. What do I do?

How to prevent YouTube from showing already watched videos?

In Star Trek IV, why did the Bounty go back to a time when whales were already rare?

What if somebody invests in my application?

Java - What do constructor type arguments mean when placed *before* the type?

Identify a stage play about a VR experience in which participants are encouraged to simulate performing horrific activities

Have I saved too much for retirement so far?

Can the harmonic series explain the origin of the major scale?

Pronouncing Homer as in modern Greek

What to do when my ideas aren't chosen, when I strongly disagree with the chosen solution?

My boss asked me to take a one-day class, then signs it up as a day off

How to check participants in at events?

Indicating multiple different modes of speech (fantasy language or telepathy)

Lifted its hind leg on or lifted its hind leg towards?

System Program Problem Dectected - Never Solved

Getting “System program problem detected” pops up regularly after upgradeDetails regarding System program Problem Detected?Constant System Program Problem popups in Ubuntu 18.04 LTS with no Show Details buttonHow to read dbus-monitor output?How can I re-enable “never show” notifications in Xubuntu 12.04?Internal error in Ubuntu 13.10 / ProblemType: KernelOops / Package: linux-image-3.11.0-19-generic 3.11.0-19.33How to renable “never show” notifications in Xubuntu 14.04?How to fix: error report “Permission Error(13,'Access denied')” on Chrome GPU process crash?How do I recover from a broken Xubuntu 12.04.4 Install?Graphical freezes and live CD boot failuresDéja Dup backup error messageASUS Xonar Essence STX II on Xubuntu 15.04?Why isn't apport being fixed and is there a better solution than disabling it?

0

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:

1. Display and describe the actual problem,


2. Show what is being reported,


3. Explain why it continually pops up,


4. 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

share|improve this question

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
  1 hour ago
  
  

  
  
  
  

add a comment | 

0

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:

1. Display and describe the actual problem,


2. Show what is being reported,


3. Explain why it continually pops up,


4. 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

share|improve this question

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
  1 hour 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:

1. Display and describe the actual problem,


2. Show what is being reported,


3. Explain why it continually pops up,


4. 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

share|improve this question

asked 2 hours ago

SearcherSearcher

16

share|improve this question

asked 2 hours ago

SearcherSearcher

16

share|improve this question

asked 2 hours ago

SearcherSearcher

16

asked 2 hours ago

SearcherSearcher

16

asked 2 hours ago

SearcherSearcher

16