npviewer.bin crashed with SIGSEGV [8.10]

Bug #272704 reported by Nanley Chery
6
Affects Status Importance Assigned to Milestone
nspluginwrapper (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: nspluginwrapper

1. Ubuntu Intrepid 8.10 Alpha 6
  Installed and updated less than 1 hour ago.

2. flashplugin-nonfree:
  Installed: 10.0.1.218+10.0.0.525ubuntu1

3. Expected to visit youtube.com in Firefox with no problems.

4. Typed in youtube.com in Firefox. Upon pressing enter, the screen quickly flashed white for less than a second, firefox grayed out for a couple seconds (w/ compiz) and came back to normal. Apport came up with a crash, but youtube works perfectly.

ProblemType: Crash
Architecture: amd64
Disassembly: 0x0:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin
Package: nspluginwrapper 1.1.0-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin --plugin /usr/lib/flashplugin-nonfree/libflashplayer.so --connection /org/wrapper/NSPlugins/libflashplayer.so/9249-2
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nspluginwrapper
Stacktrace: #0 0x00000000 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: npviewer.bin crashed with SIGSEGV
Uname: Linux 2.6.27-3-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Revision history for this message
Nanley Chery (nanoman) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()

Revision history for this message
Pedro Villavicencio (pedro) wrote : Missing Backtrace

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.

Changed in nspluginwrapper:
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:
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.