Why very frequently appears "Crash report detected"?

Asked by Navin Talati

I have got Ubuntu 13.04 as OS in my machine.

 It very frequently gives noticifation as "Crash report detected".

When clicking on it, a notification appears as:

"System program problen detected.
Do you want to report the problem now?
 CANCEL REPORT PROBLEM..... "

When clicking on REPORT PROBLEM..... , it asks for Authentication.

Applying the Password and ENTER, it notifies as under:

"Sorry, Ubuntu 13.04 has experienced an internal error.
If you notice further problems, try restarting the computer.
Send an error report to help fix this problem
SHOW DETAILS CONTINUE"

Clicking on SHOW DETAILS opens a window giving list of detail.
Clicking on CONTINUE, the notification disappears.

Again after some time the process continues in abofe fashion.

My questions are:
[1]. Why so frequently it happens?
[2]. How to resolve this and which commands need to be applied in Terminal?

Please help me in resolving this problem.
Thanks.
Navin Talati / 05-09-2013

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
N1ck 7h0m4d4k15
Solved:
Last query:
Last reply:

This question was reopened

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

If you log in as a new Ubuntu user is it the same?

Revision history for this message
Navin Talati (n-m-talati) said :
#2

Yes. When I log in as Guest, or through Unity or Gnome desktops GUI, it appears.

Revision history for this message
Manfred Hampl (m-hampl) said :
#3

Please provide some more information, e.g. about the package name mentioned in the crash report, and some other details.

Revision history for this message
Navin Talati (n-m-talati) said :
#4

Sir,
Crash Report problem window's content is not copiable.
Please, suggest a command line/stuff applicable in the Terminal, so that I may apply ans send you the result.
Thanks

Revision history for this message
Manfred Hampl (m-hampl) said :
#5

There is no need to copy the whole window content, just naming the failing package and some key information from the crash reporting window would be helpful.

Revision history for this message
Navin Talati (n-m-talati) said :
#6

In the crash report, after applying the password to report the problem, it shows in the "Sorry, ....." window something as below:
*ExecutablePath
     /user/lib/i386-linux-gnu/speech-dispatcher-modules/sd_espeak
*Package
     speech-dispatcher 0.7.1-6. 1ubuntu2
*ProblemType
     Crash
*Title

Revision history for this message
Navin Talati (n-m-talati) said :
#7

In the crash report, after applying the password to report the problem, it shows in the "Sorry, ....." window something as below:
*ExecutablePath
     /user/lib/i386-linux-gnu/speech-dispatcher-modules/sd_espeak
*Package
     speech-dispatcher 0.7.1-6. 1ubuntu2
*ProblemType
     Crash
*Title
     sd_espeak crashed with SIGABRT in raise()
*ApportVersion
     2.9.2-0ubuntu8.3
*Architecture
     i386
*coreDump
     (binary data)
.... and still many titles are nerrated in brief. Please specify if anything further is required.
Like this it is mentioned in the window/dialogbox and asks to continue for sending the error report to help fix this problem. Usually, I every time sends seeking help.
Stillo the problem persists.
Please guide.

Revision history for this message
Best N1ck 7h0m4d4k15 (nicktux) said :
#8

 [1]. Why so frequently it happens?

Probably this is a problem with the apport itself. Apport is the applications that help (or should help) the user to report problems. Actual problems and crashes. The Apport usually is disabled on stable releases (like Raring) and is always enabled in development releases (like Saucy).
Sometimes apport can't handle itself and crash all the time.

 [2]. How to resolve this and which commands need to be applied in Terminal?

sudo sed 's/enabled=1/enabled=0/g' -i /etc/default/apport

sudo service apport restart

Regards
 NikTh

Revision history for this message
Navin Talati (n-m-talati) said :
#9

Sir,

Thanks for the guidance and providing basic understanding about the "APPORT" as per [1].

As per [2], I applied the stuffs and the output was something like:
apport stop/waiting
apport start/running

I shell let you know what happens in future.

Navin Talati / 17-09-2013

Revision history for this message
Navin Talati (n-m-talati) said :
#10

Sir,
Since above stuffs are applied, "Crash Report Detected" warning is not appeared.
This seems that it would be an issue of "Apport" which is resolved through this operation.
Commands applied were:
(1). "sudo sed 's/enabled=1/enabled=0/g' -i /etc/default/apport"
(2). "sudo service apport restart"
Thanks to NIK and ALL
Navin Talati / 21-09-2013

Revision history for this message
Navin Talati (n-m-talati) said :
#11

Thanks Nik.Th., that solved my question.