npviewer.bin crashed with SIGSEGV

Bug #478892 reported by james
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nspluginwrapper (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: nspluginwrapper

was browsing with firefox with less than 5 tabs open, and this crash came up.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sun Nov 8 20:59:16 2009
Disassembly: 0x3130613d: Cannot access memory at address 0x3130613d
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin
NonfreeKernelModules: nvidia
Package: nspluginwrapper 1.2.2-0ubuntu6
ProcCmdline: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin --plugin /usr/lib/flashplugin-installer/libflashplayer.so --connection /org/wrapper/NSPlugins/libflashplayer.so/2301-6
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x3130613d: Cannot access memory at address 0x3130613d
 PC (0x3130613d) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: nspluginwrapper
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
 ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
 ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
 ?? () from /usr/lib/flashplugin-installer/libflashplayer.so
Title: npviewer.bin crashed with SIGSEGV
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare src video

Revision history for this message
james (jamesm51) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in nspluginwrapper (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libavahi-common3: installed version 0.6.25-1ubuntu5, latest version: 0.6.25-1ubuntu5.1
libgtk2.0-common: installed version 2.18.3-1, latest version: 2.18.3-1ubuntu1
libgtk2.0-0: installed version 2.18.3-1, latest version: 2.18.3-1ubuntu1
libavahi-client3: installed version 0.6.25-1ubuntu5, latest version: 0.6.25-1ubuntu5.1
python2.6: installed version 2.6.4-0ubuntu1, latest version: 2.6.4-0ubuntu2
tzdata: installed version 2009o+repack-0ubuntu0.9.04.2, latest version: 2009o-1ubuntu2
python2.6-minimal: installed version 2.6.4-0ubuntu1, latest version: 2.6.4-0ubuntu2
x11-common: installed version 1:7.4+3ubuntu7, latest version: 1:7.4+3ubuntu9
libpython2.6: installed version 2.6.4-0ubuntu1, latest version: 2.6.4-0ubuntu2
libavahi-common-data: installed version 0.6.25-1ubuntu5, latest version: 0.6.25-1ubuntu5.1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
Revision history for this message
james (jamesm51) wrote :

All those packages are the latest versions. Why should I bother submitting reports if they are going to be marked invalid within 10 hours?

Changed in nspluginwrapper (Ubuntu):
status: Invalid → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

visibility: private → public
Changed in nspluginwrapper (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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

Changed in nspluginwrapper (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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