npviewer.bin crashed with SIGSEGV in pthread_mutex_lock()

[Petri Damstén]

Binary package hint: nspluginwrapper

Browsing with konqueror

ProblemType: Crash
Architecture: amd64
Date: Sat Jul 14 23:28:14 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin
NonfreeKernelModules: nvidia
Package: nspluginwrapper 0.9.91.4-3ubuntu1
PackageArchitecture: amd64
ProcCmdline: /usr/lib/nspluginwrapper/i386/linux/npviewer.bin --plugin /usr/lib/flashplugin-nonfree/libflashplayer.so --connection /org/wrapper/NSPlugins/libflashplayer.so/8927-1
ProcCwd: /home/damu
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=~/bin:~/bin/kde4:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games:/usr/bin32
 LANG=en_US.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
 ?? () 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 wood 2.6.22-8-generic #1 SMP Thu Jul 12 16:09:47 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev scanner video

[Apport retracing service (apport)]

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

[Apport retracing service (apport)]

StacktraceTop:pthread_mutex_lock () from /lib32/libpthread.so.0
?? ()
?? ()
?? () from /lib/ld-linux.so.2
?? ()

[Sarah Kowalik (hobbsee-deactivatedaccount)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, your crash report is incomplete or corrupt, so I am closing this bug as there is not much we can do with it. Please try and obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and open a new bug report with that information and steps to reproduce the crash. Thanks again.

[Dara Adib (daradib)]

More duplicates

[Dara Adib (daradib)]

Please resubmit any additional information relevant to this bug on Bug 126040 (not on the duplicates). Do not simply repost information that is already specified. Thank you.

[nickdjones (nick-nickdjones)]

so is simply following the natural workflow of bug submission suggested by the crash report agent on the desktop not useful? i don't know much about these modules, but have been getting these errors for a while, and most times submit them, in case the information is of use. happy to stop, though I'm not always sure if the error is a repeat or not....

[Sander Jonkers (jonkers)]

Same crash here on Ubuntu Hardy Heron AMD64 running on Athlon X2 3600+.

AFAIK I have npviewer.bin updated with http://launchpadlibrarian.net/12234800/nspluginwrapper_0.9.91.5-2ubuntu1_amd64.deb (as described in https://bugs.launchpad.net/ubuntu/+source/nspluginwrapper/+bug/141613), but maybe a Heron upgrade has overwritten it with the older, buggy npviewer.bin?

sander@ubuntu804:~$ ll `locate npviewer.bin`
-rwxr-xr-x 1 root root 107088 2008-03-18 20:48 /usr/lib/nspluginwrapper/i386/linux/npviewer.bin
-rw------- 1 sander sander 691333 2008-04-06 10:48 /var/crash/_usr_lib_nspluginwrapper_i386_linux_npviewer.bin.1000.crash
sander@ubuntu804:~$

[liquidator87 (liquidator87)]

Confirmed... happened to me today :-(

[Fedor Isakov (fisakov)]

Confirming same here on Hardy x86_64, nspluginwrapper version 0.9.91.5-2ubuntu2.

[John Vivirito (gnomefreak)]

There is not one bug report or crash report we can use to find out exactly what the problem is other than its flash issue. We are unable to fix flash crashes since the source is closed please file one crash report for one bug report.
Closing this bug due to reasons above, iF you see a crash in FireFox please report it on a seperate bug report using apport

[Sander Jonkers (jonkers)]

John,

I'm the OP and here's my question:

For which reason *exactly* are you closing this bug report?

1) Because Flash is closed source?
If so, I guess no further bug reports are needed. Well, that is, as long as flash stays closed source, which it probably will.

2) Because others are 'attaching' to *my* bug-report-per-crash?
If so, I will not do any further bug reports as I can not prevent others from 'attaching'

3) Because I'm using an incorrect reporting method?
If so, please advice me how to do a correct bug report. I just follow Ubuntu's automatic bug reporting method. If that's wrong, instruct me what to do exactly.

Thanks,

Sander

Quote:
"There is not one bug report or crash report we can use to find out exactly what the problem is other than its flash issue. We are unable to fix flash crashes since the source is closed please file one crash report for one bug report.
Closing this bug due to reasons above, iF you see a crash in FireFox please report it on a seperate bug report using apport"

[Sander Jonkers (jonkers)]

Oh, wait: my bug report was before your advice for one-report-per-crash on April 11. You can ignore my previous post. Since your advice on April 11, I'm opening a bug report per crash.

Sorry for the misunderstanding.

[thecure (keith-k)]

Hardy, 64bit.

I get this crash on login. No firefox running/flash at crash.

[Michael S Costello (fraterm)]

Since flash is now rather well integrated into the 64 bit Hardy Heron release, I think this should receive some attention, however I'm confused currently about the prospect of adding any additional helpful information about the crash to this bug number rather than opening new.

Overall, flash operates properly in the new setup from a user perspective, it just seems there are lingering issues with stability. Let me know how best one can help characterize these breaks and I'll devote that time to reproductions/workarounds.

[Lean Fuglsang (lean-ubuntu-cd)]

One way to fix this bug, is to stop reporting when a crash occurs in flash. If people aren't interested in fixing this issue, then we shouldn't nag people to create a bug report whenever flash crashes.