Ubuntu
nspluginwrapper package

npviewer.bin crashed with SIGSEGV

Bug #632242 reported by Dom on 2010-09-07

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	nspluginwrapper (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: nspluginwrapper

was just using google chrome on ubuntu 10.10 beta, and it keeps on crashing.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nspluginwrapper 1.2.2-0ubuntu6
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 7 09:15:27 2010
ExecutablePath: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
ProcCmdline: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin --plugin /usr/lib/flashplugin-installer/libflashplayer.so --connection /org/wrapper/NSPlugins/libflashplayer.so/5874-3
ProcEnviron:
PATH=(custom, no user)
LANG=en_GB.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xf607edd6: movl $0x0,0x418(%eax)
PC (0xf607edd6) ok
source "$0x0" ok
destination "0x418(%eax)" (0x00000418) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL 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
?? () from /usr/lib/flashplugin-installer/libflashplayer.so
Title: npviewer.bin crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Dom (dom-becher) wrote on 2010-09-07:

#1

Dependencies.txt Edit (3.3 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (538 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (34.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (801 bytes, text/plain; charset="utf-8")
Registers.txt Edit (447 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.5 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (1.4 KiB, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2010-09-09:

#2

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

Revision history for this message

Apport retracing service (apport) wrote on 2010-09-09: Stacktrace.txt

#3

Stacktrace.txt Edit (839 bytes, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2010-09-09: ThreadStacktrace.txt

#4

ThreadStacktrace.txt Edit (866 bytes, text/plain)

Changed in nspluginwrapper (Ubuntu):
status:	New → Invalid

Revision history for this message

Apport retracing service (apport) wrote on 2010-09-09: Crash report cannot be processed

#5

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:

libc6-i386: installed version 2.12.1-0ubuntu3, latest version: 2.12.1-0ubuntu4
ia32-libs: installed version 20090808ubuntu3, latest version: 20090808ubuntu4
libfreetype6: installed version 2.4.2-1, latest version: 2.4.2-2
libc-bin: installed version 2.12.1-0ubuntu3, latest version: 2.12.1-0ubuntu4
nspluginwrapper: installed version 1.2.2-0ubuntu6, latest version: 1.2.2-0ubuntu7
dpkg: installed version 1.15.8.4ubuntu2, latest version: 1.15.8.4ubuntu3
libpixman-1-0: installed version 0.18.2-1ubuntu1, latest version: 0.18.4-1
libc6: installed version 2.12.1-0ubuntu3, latest version: 2.12.1-0ubuntu4

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

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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