Re: linux-f10-flashplugin11 not works for 9-stable (Linuxulator?)
Andrey Chernov wrote:
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 localhost.my.domain
line from our _standard_ /usr/src/etc/hosts which comes first before
127.0.0.1 localhost localhost.my.domain
line.
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.
127.0.0.1 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.
Can you clarify this a bit? I have at least one machine with vanilla
/etc/hosts connected to IPv4/IPv6 network (i.e. some internal hosts
resolve to IPv6) and flash works fine there.
The DEPEND list on www/nspluginwrapper lists ftp/curl as a dependence.
And this port can be built without IPv6. Can you check your ports
configuration about enabling IPv6 support?
--
Sphinx of black quartz judge my vow.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-flashplugin11 not works for 9-stable (Linuxulator?)
On Tue, Feb 21, 2012 at 12:07:46PM +0200, Volodymyr Kostyrko wrote:
Andrey Chernov wrote:
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 localhost.my.domain
line from our _standard_ /usr/src/etc/hosts which comes first before
127.0.0.1 localhost localhost.my.domain
line.
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.
127.0.0.1 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.
Can you clarify this a bit? I have at least one machine with vanilla
/etc/hosts connected to IPv4/IPv6 network (i.e. some internal hosts
resolve to IPv6) and flash works fine there.
I can't - I don't know why npviewer.bin is killed by SIGTERM immediatelly
when it socketcall to [::1]:6010 in Linuxulator and why it works
normally when it socketcall to 127.0.0.1:6010. I remember when I had
FF 7, Flash works with ::1 first, but Linuxulator not yet have any length
checks at those times as it have now (or perhaps other recent fixes).
The DEPEND list on www/nspluginwrapper lists ftp/curl as a dependence.
And this port can be built without IPv6. Can you check your ports
configuration about enabling IPv6 support?
This is not the case, all my ports which have IPv6 capability
are builded with IPv6 as the system too.
--
http://ache.vniz.net/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-flashplugin11 not works for 9-stable (Linuxulator?)
On 02/21/2012 02:43, Andrey Chernov wrote: I can't - I don't know why npviewer.bin is killed by SIGTERM immediatelly when it socketcall to [::1]:6010 in Linuxulator and why it works normally when it socketcall to 127.0.0.1:6010. I remember when I had FF 7, Flash works with ::1 first, but Linuxulator not yet have any length checks at those times as it have now (or perhaps other recent fixes). I have an IPv6 connection and listing ::1 first works for me as well. Try closing down firefox, rm -r ~/.macromedia, rebuilding www/nspluginwrapper and www/linux-f10-flashplugin11, then rm ~/.mozilla/plugins/npwrapper.libflashplayer.so and reinstall. (I just use, nspluginwrapper -i /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so personally) Then restart firefox and check out about:plugins Good luck, Doug -- It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-flashplugin11 not works for 9-stable (Linuxulator?)
On Tue, Feb 21, 2012 at 02:51:26AM -0800, Doug Barton wrote: On 02/21/2012 02:43, Andrey Chernov wrote: I can't - I don't know why npviewer.bin is killed by SIGTERM immediatelly when it socketcall to [::1]:6010 in Linuxulator and why it works normally when it socketcall to 127.0.0.1:6010. I remember when I had FF 7, Flash works with ::1 first, but Linuxulator not yet have any length checks at those times as it have now (or perhaps other recent fixes). I have an IPv6 connection and listing ::1 first works for me as well. Try closing down firefox, rm -r ~/.macromedia, rebuilding www/nspluginwrapper and www/linux-f10-flashplugin11, then rm ~/.mozilla/plugins/npwrapper.libflashplayer.so and reinstall. (I just use, nspluginwrapper -i /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so personally) Then restart firefox and check out about:plugins I already do all the above first, rebuild everything etc. Nothing helps excepting moving ::1 down (moving it down works even with FF is already running - on the next page reload). BTW, Flash is shown in about:plugins normally in either case, just not works due to misteriosly killed npviewer.bin in ::1 first case. -- http://ache.vniz.net/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: nspluginwrapper (was Re: linux-f10-flashplugin11 not works for 9-stable (Linuxulator?))
On Thursday 16 February 2012 04:26 pm, Andrey Chernov wrote:
It seems part of the bug is already noticed by maintainer (Jung-uk
Kim) but nothing is done to fix it:
http://lists.freebsd.org/pipermail/freebsd-stable/2011-September/06
4067.html BTW, the bug is in native FreeBSD code (rpc.c), not in
linux code.
Jung-uk, could you fix/hack it somehow, please?
Linuxulator does not support abstract namespace yet and it is hard
problem. However, nspluginwrapper does not use abstract namespace
when it is built for non-Linux platform, i.e., --enable-generic
configure option unsets USE_ANONYMOUS_SOCKETS for both Linux and
FreeBSD.
OTH, FreeBSD-SA-11:05.unix broke Linuxulator but it was quickly
patched by cperciva and refined by me *before* 9.0-RELEASE.
Jung-uk Kim
On Fri, Feb 17, 2012 at 12:31:08AM +0400, Andrey Chernov wrote:
On Thu, Feb 16, 2012 at 11:47:05AM +0200, Volodymyr Kostyrko
wrote:
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_180428
9383 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?
Am running flash successfully on 9-stable (daily rebuild).
Works for me under chromium/seamonkey.
Just filed a patch for the latest flash version... Works for me
also.
Do you have recently-builded nspluginwrapper from sources? It
seems the bug is there, since even that does not work:
# nspluginplayer --verbose type=application/x-shockwave-flash
src=some.swf
*** NSPlugin Player *** swf application/x-shockwave-flash
Shockwave Flash *** NSPlugin Player *** spl
application/futuresplash
FutureSplash Player *** NSPlugin Wrapper *** ERROR: failed to
initialize plugin-side RPC client connection *** NSPlugin Player
*** ERROR: could not execute: NPERR_MODULE_LOAD_FAILED_ERROR
And I see very suspicious socket_addr_len size related code
(which recent SA-fixes address) in rpc.c there:
connection-socket_addr_len =
_rpc_socket_path(connection-socket_path, ident);
memcpy(connection-socket_addr.sun_path[0],
connection-socket_path, connection-socket_addr_len);
connection-socket_addr_len += offsetof(struct sockaddr_un,
sun_path); /* though POSIX says size of the actual sockaddr
structure */ #ifdef HAVE_SOCKADDR_UN_SUN_LEN
connection-socket_addr.sun_len = connection-socket_addr_len;
#endif
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-flashplugin11 not works for 9-stable (Linuxulator?)
On Wednesday 15 February 2012 11:47 am, 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.
Yes, it should be fixed *before* 9.0-RELEASE.
Please try make configure and send me config-host.h from
work/nspluginwrapper-1.4.4 directory.
Jung-uk Kim
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-flashplugin11 not works for 9-stable (Linuxulator?)
On Friday 17 February 2012 01:32 pm, Jung-uk Kim wrote: 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. Yes, it should be fixed *before* 9.0-RELEASE. I meant 9.0 was released with the fix. Sorry if I caused confusion. Jung-uk Kim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-flashplugin11 not works for 9-stable (Linuxulator?)
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?
Am running flash successfully on 9-stable (daily rebuild). Works for me
under chromium/seamonkey.
Just filed a patch for the latest flash version... Works for me also.
--
Sphinx of black quartz judge my vow.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-flashplugin11 not works for 9-stable (Linuxulator?)
Volodymyr Kostyrko writes: Am running flash successfully on 9-stable (daily rebuild). Works for me under chromium/seamonkey. Just filed a patch for the latest flash version... Works for me also. On my system, portversion did not catch the jump from Flash 9 to Flash 11. Was this just me, or should there be an entry in UPDATING? Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-flashplugin11 not works for 9-stable (Linuxulator?)
Robert Huff wrote: Am running flash successfully on 9-stable (daily rebuild). Works for me under chromium/seamonkey. Just filed a patch for the latest flash version... Works for me also. On my system, portversion did not catch the jump from Flash 9 to Flash 11. Was this just me, or should there be an entry in UPDATING? They are different ports. You need to switch to other one. You can do so with portmaster: portmaster -o www/linux-f10-flashplugin11 www/linux-flashplugin9 -- Sphinx of black quartz judge my vow. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-flashplugin11 not works for 9-stable (Linuxulator?)
Volodymyr Kostyrko writes: On my system, portversion did not catch the jump from Flash 9 to Flash 11. Was this just me, or should there be an entry in UPDATING? They are different ports. You need to switch to other one. Given the number of people who have/had trouble getting Flash to work, telling the average user that this is not covered by a common port version checking tool would be prudent. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: linux-f10-flashplugin11 not works for 9-stable (Linuxulator?)
Robert Huff wrote: On my system, portversion did not catch the jump from Flash 9 to Flash 11. Was this just me, or should there be an entry in UPDATING? They are different ports. You need to switch to other one. Given the number of people who have/had trouble getting Flash to work, telling the average user that this is not covered by a common port version checking tool would be prudent. Traditionally FreeBSD ports contain more than one flash version. I don't know where this came from, maybe the previous version was left intact until Adobe/Macromedia fully moves to the next one resolving incompatibility issues or something... -- Sphinx of black quartz judge my vow. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
nspluginwrapper (was Re: linux-f10-flashplugin11 not works for 9-stable (Linuxulator?))
On Thu, Feb 16, 2012 at 11:47:05AM +0200, Volodymyr Kostyrko wrote:
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?
Am running flash successfully on 9-stable (daily rebuild). Works for me
under chromium/seamonkey.
Just filed a patch for the latest flash version... Works for me also.
Do you have recently-builded nspluginwrapper from sources? It seems the
bug is there, since even that does not work:
# nspluginplayer --verbose type=application/x-shockwave-flash
src=some.swf
*** NSPlugin Player *** swf application/x-shockwave-flash
Shockwave Flash
*** NSPlugin Player *** spl application/futuresplash
FutureSplash Player
*** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client
connection
*** NSPlugin Player *** ERROR: could not execute:
NPERR_MODULE_LOAD_FAILED_ERROR
And I see very suspicious socket_addr_len size related code (which recent
SA-fixes address) in rpc.c there:
connection-socket_addr_len = _rpc_socket_path(connection-socket_path,
ident);
memcpy(connection-socket_addr.sun_path[0], connection-socket_path,
connection-socket_addr_len);
connection-socket_addr_len += offsetof(struct sockaddr_un, sun_path);
/* though POSIX says size of the actual sockaddr structure */
#ifdef HAVE_SOCKADDR_UN_SUN_LEN
connection-socket_addr.sun_len = connection-socket_addr_len;
#endif
--
http://ache.vniz.net/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: nspluginwrapper (was Re: linux-f10-flashplugin11 not works for 9-stable (Linuxulator?))
It seems part of the bug is already noticed by maintainer (Jung-uk Kim) but
nothing is done to fix it:
http://lists.freebsd.org/pipermail/freebsd-stable/2011-September/064067.html
BTW, the bug is in native FreeBSD code (rpc.c), not in linux code.
Jung-uk, could you fix/hack it somehow, please?
On Fri, Feb 17, 2012 at 12:31:08AM +0400, Andrey Chernov wrote:
On Thu, Feb 16, 2012 at 11:47:05AM +0200, Volodymyr Kostyrko wrote:
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?
Am running flash successfully on 9-stable (daily rebuild). Works for me
under chromium/seamonkey.
Just filed a patch for the latest flash version... Works for me also.
Do you have recently-builded nspluginwrapper from sources? It seems the
bug is there, since even that does not work:
# nspluginplayer --verbose type=application/x-shockwave-flash
src=some.swf
*** NSPlugin Player *** swf application/x-shockwave-flash
Shockwave Flash
*** NSPlugin Player *** spl application/futuresplash
FutureSplash Player
*** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client
connection
*** NSPlugin Player *** ERROR: could not execute:
NPERR_MODULE_LOAD_FAILED_ERROR
And I see very suspicious socket_addr_len size related code (which recent
SA-fixes address) in rpc.c there:
connection-socket_addr_len = _rpc_socket_path(connection-socket_path,
ident);
memcpy(connection-socket_addr.sun_path[0], connection-socket_path,
connection-socket_addr_len);
connection-socket_addr_len += offsetof(struct sockaddr_un, sun_path);
/* though POSIX says size of the actual sockaddr structure */
#ifdef HAVE_SOCKADDR_UN_SUN_LEN
connection-socket_addr.sun_len = connection-socket_addr_len;
#endif
--
http://ache.vniz.net/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
--
http://ache.vniz.net/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
linux-f10-flashplugin11 not works for 9-stable (Linuxulator?)
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?
--
http://ache.vniz.net/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
