Ubuntu
nspluginwrapper package

npviewer.bin crashed with SIGSEGV

Bug #148461 reported by Juksu
This bug report is a duplicate of:  Bug #141613: npviewer.bin crashed with SIGSEGV. Edit Remove
6
Affects Status Importance Assigned to Milestone
nspluginwrapper (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: nspluginwrapper

Gutsy on a HP nc8430 laptop, Mobility X1600

ProblemType: Crash
Architecture: amd64
Date: Wed Oct 3 02:55:34 2007
Disassembly: 0xf7894550:
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin
NonfreeKernelModules: fglrx
Package: nspluginwrapper 0.9.91.4-3ubuntu2
PackageArchitecture: amd64
ProcCmdline: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin --plugin /usr/lib/flashplugin-nonfree/libflashplayer.so --connection /org/wrapper/NSPlugins/libflashplayer.so/6576-1
ProcCwd: /home/jpl
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nspluginwrapper
Stacktrace: #0 0xf7894550 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: npviewer.bin crashed with SIGSEGV
Uname: Linux Possulap 2.6.22-12-generic #1 SMP Sun Sep 23 20:03:18 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Juksu (jluostar) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Juksu (jluostar) wrote :

Well, I can not verify if this bug is a duplicate or not since the other bug is marked private and therefore I HAVE NO ACCESS TO IT!
THIS IS A PUBLIC BUG!
Either change the duplicate to the other bug or make it PUBLIC!!!

Revision history for this message
laga (laga) wrote : Re: [Bug 148461] Re: npviewer.bin crashed with SIGSEGV

Juksu schrieb:
> *** This bug is a duplicate of bug 141613 ***
> https://bugs.launchpad.net/bugs/141613
>
> Well, I can not verify if this bug is a duplicate or not since the other bug is marked private and therefore I HAVE NO ACCESS TO IT!
> THIS IS A PUBLIC BUG!
> Either change the duplicate to the other bug or make it PUBLIC!!!
>

Crash reports are marked private for a reason: sensitive information
might be contained in the backtrace.

Please stop yelling, we're capable of understanding you even if you
don't abuse your caps lock key.

Revision history for this message
Juksu (jluostar) wrote :

Well, then?

Revision history for this message
Juksu (jluostar) wrote :

Is anything perhaps happening to bug where i could be of assistance?
It would be better to use a public bug as the common point so that if the devs need additional info, we could try to provide it.
Also, it would be nice to know that something is happening (or, as likely probably not).

Since this bug is marked as a duplicate of a private bug, i do not get any updates regarding this, even though i went through the trouble of reporting this bug and trying out gutsy in advance.

Nothing has been done, despite you said you understood. Apparently not, after all.
It is no use asking for bug reports if the response is like this. No-one will bother after a while.

All the best for bug-solving,
Jukka

Revision history for this message
laga (laga) wrote :

Juksu schrieb:
> *** This bug is a duplicate of bug 141613 ***
> https://bugs.launchpad.net/bugs/141613
>
> Is anything perhaps happening to bug where i could be of assistance?
> It would be better to use a public bug as the common point so that if the devs need additional info, we could try to provide it.

As the reporter of bug 141613, I have just turned it into a public report.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.