linux-f10-flashplugin11 not works for 9-stable (Linuxulator?)

Andrey Chernov ache at
Tue Feb 21 00:57:21 UTC 2012

Just in case it may help somebody: the cause (but not the root) of the 
problem is found and workaround too.

The cause of the problem is
::1                     localhost
line from our _standard_ /usr/src/etc/hosts which comes first before               localhost

Linux takes the first match on localhost, i.e. ::1, then tries
        8605 npviewer.bin STRU  struct sockaddr { AF_INET6, [::1]:6010 }
it was last command from npviewer.bin, then it immeditelly terminates:
        8605 npviewer.bin RET   linux_socketcall -1 errno 4 Interrupted system call
        8605 npviewer.bin PSIG  SIGTERM SIG_DFL code=0x10001

The workaround is to switch lines order in /etc/hosts, i.e. localhost
        ::1 localhost
to make IPv4 one comes first. Flash works afterwards.

The bug affects IPv6-enabled machines with IPv4 over IPv6 preferred or 
maybe IPv4 too I don't know, but since we don't have such reports in mass, 
I think IPv4-only setup is fine.

On Wed, Feb 15, 2012 at 08:47:22PM +0400, Andrey Chernov wrote:
> Having 9-stable and ports from Feb 14, all builded from sources, I get 
> this commonly looking error attempting to view flash in FF 10.0.1:
> *** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC 
> client connection 
> NOTE: child process received `Goodbye', closing down
> Looking into ktrace I found error reason:
> 82037 plugin-container CALL  connect(0x16,0x2c04f9d4,0x42)
>  82037 plugin-container STRU  struct sockaddr { AF_LOCAL, invalid }
>  82037 plugin-container NAMI
> "/tmp/_org_wrapper_NSPlugins_libflashplayer.so_82037-2_1804289383"
>  82037 plugin-container RET   connect -1 errno 2 No such file or directory
> (repeated several times).
> This "invalid" in sockaddr looks familiar as for some time ago added 
> sockaddr length checks our kernel, but as bz@ says this should be 
> already fixed.
> Does anybody runs flash successfly on 9-stable? If yes, where else the 
> problem can be?


More information about the freebsd-ports mailing list