unknown -The KDE Crash Handler

[nik0]

Binary package hint: dolphin

not exactly the same bug that #132238 Dolphin crash but next from it

General

Short description

The application unknown(nspluginviewer)crashed and caused the signal 11
(SIGSEGV)

What is this?

AN application mostly receives the SIGSEGV signal due to a bug in the application.THe application was asked to save its documents

Backtrace:

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

Unable to create a valid backtrace. (i can't copy or save as )

[Yuriy Kozlov (yuriy-kozlov)]

Thank you for reporting this.
What were you doing when it crashed? Can you reproduce it?
Were you using dolphin from kde 3.5 or 4.0?
What version of Kubuntu were you using?

[nik0 (nik0p0l)]

 it was Kunbuntu 7.10
when i surf on internet  with konqueror
I change of page and it crash after
it close konqueror and marked the message Kde crash handler
not sur of the kde version 3.5 or 4.0

> Message du 23/03/08 20:55
> De : "Yuriy Kozlov"
> A : <email address hidden>
> Copie à :
> Objet : [Bug 205597] Re: unknown -The KDE Crash Handler
>
> Thank you for reporting this.
> What were you doing when it crashed? Can you reproduce it?
> Were you using dolphin from kde 3.5 or 4.0?
> What version of Kubuntu were you using?
>
> ** Changed in: dolphin (Ubuntu)
> Status: New => Incomplete
>
> --
> unknown -The KDE Crash Handler
> https://bugs.launchpad.net/bugs/205597
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Source Package "dolphin" in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: dolphin
>
> not exactly the same bug that #132238 Dolphin crash but next from it
>
> General
>
> Short description
>
> The application unknown(nspluginviewer)crashed and caused the signal 11
> (SIGSEGV)
>
> What is this?
>
> AN application mostly receives the SIGSEGV signal due to a bug in the application.THe application was asked to save its documents
>
> Backtrace:
>
> This backtrace appears to be of no use.
> This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.
>
> (no debugging symbols found)
> Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
>
>
>
>
> Unable to create a valid backtrace. (i can't copy or save as )
>
>

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

[kabotage (kabotage)]

i have the experienced it too a couple of times. i dont know what it caused, i have a lot of open windows so i cant figure out which of them crashed? im on kubuntu 8.10/kde 4.1.2

The application nspluginviewer (nspluginviewer) crashed and caused the signal 11 (SIGSEGV).

Unable to create a valid backtrace.

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

[kabotage (kabotage)]

it crashed again but now with a backtrace.

[Adam (vitali)]

I get this always after leaving the wastebin by closing Dolphin or going to another folder.

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5f3d6c0 (LWP 14445)]
[New Thread 0xb3a5db90 (LWP 14447)]
[New Thread 0xb43e8b90 (LWP 14446)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols fou...

[xteejx (xteejx)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu version (10.04). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.

[xteejx (xteejx)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!