npviewer.bin crashed with SIGSEGV in pthread_mutex_lock()

Bug #218348 reported by mabovo
6
Affects Status Importance Assigned to Milestone
nspluginwrapper (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: nspluginwrapper

Browsing with FF3b5 on Hardy 8.04 amd64

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Wed Apr 16 13:47:09 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin
NonfreeKernelModules: ath_hal
Package: nspluginwrapper 0.9.91.5-2ubuntu2
PackageArchitecture: amd64
ProcCmdline: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin --plugin /usr/lib/flashplugin-nonfree/libflashplayer.so --connection /org/wrapper/NSPlugins/libflashplayer.so/17221-5
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nspluginwrapper
StacktraceTop:
 pthread_mutex_lock () from /lib32/libpthread.so.0
 ?? () from /usr/lib/flashplugin-nonfree/libflashplayer.so
 ?? ()
 ?? () from /usr/lib/flashplugin-nonfree/libflashplayer.so
 ?? ()
Title: npviewer.bin crashed with SIGSEGV in pthread_mutex_lock()
Uname: Linux 2.6.24-16-generic x86_64
UserGroups: adm admin audio cdrom crontab dialout dip floppy fuse gdm lastfm lpadmin netdev ntp plugdev powerdev pulse pulse-access pulse-rt sambashare scanner users video

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

StacktraceTop:pthread_mutex_lock () from /lib32/libpthread.so.0
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
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.

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.