npviewer.bin crashed with SIGSEGV

Bug #634232 reported by Linards Ticmanis
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nspluginwrapper (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: nspluginwrapper

Happened without any obvious action triggering it. Browser was open during Update Manager run, maybe that's the reason?

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nspluginwrapper 1.2.2-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Sep 9 18:50:27 2010
ExecutablePath: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin
ProcCmdline: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin --plugin /usr/lib/flashplugin-installer/libflashplayer.so --connection /org/wrapper/NSPlugins/libflashplayer.so/4669-7
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xf601bdd6: movl $0x0,0x418(%eax)
 PC (0xf601bdd6) 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 audio cdrom dialout dip fax floppy fuse lp lpadmin netdev plugdev pulse pulse-access sambashare scanner tape video

Revision history for this message
Linards Ticmanis (ticmanis) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

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

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
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:

libgcc1: installed version 1:4.5.1-5ubuntu1, latest version: 1:4.5.1-7ubuntu1
libc6-i386: installed version 2.12.1-0ubuntu4, latest version: 2.12.1-0ubuntu6
libavahi-common3: installed version 0.6.27-2ubuntu1, latest version: 0.6.27-2ubuntu3
python: installed version 2.6.5-13ubuntu1, latest version: 2.6.6-1ubuntu1
gcc-4.5-base: installed version 4.5.1-5ubuntu1, latest version: 4.5.1-7ubuntu1
lib32stdc++6: installed version 4.5.1-5ubuntu1, latest version: 4.5.1-7ubuntu1
libavahi-client3: installed version 0.6.27-2ubuntu1, latest version: 0.6.27-2ubuntu3
libgdk-pixbuf2.0-0: installed version 2.21.6-2ubuntu5, latest version: 2.21.7-1ubuntu3
python-minimal: installed version 2.6.5-13ubuntu1, latest version: 2.6.6-1ubuntu1
libcups2: installed version 1.4.4-3ubuntu1, latest version: 1.4.4-4
libc-bin: installed version 2.12.1-0ubuntu4, latest version: 2.12.1-0ubuntu6
libcairo2: installed version 1.9.14-1ubuntu1, latest version: 1.10.0-1ubuntu1
lib32gcc1: installed version 1:4.5.1-5ubuntu1, latest version: 1:4.5.1-7ubuntu1
python-central: installed version 0.6.15ubuntu1, latest version: 0.6.15ubuntu2
libpython2.6: installed version 2.6.6-1ubuntu1, latest version: 2.6.6-4ubuntu1
libavahi-common-data: installed version 0.6.27-2ubuntu1, latest version: 0.6.27-2ubuntu3
libc6: installed version 2.12.1-0ubuntu4, latest version: 2.12.1-0ubuntu6

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