Windows Chrome vs Porteus Chrome: Shockwave Flash Player

[WavyLinesAreNotReal]

I'm a fan of a particular Facebook game called Avengers Alliance. It is flash based game, which means that it requires a flash player to run. It works fine with Chrome, while inside windows; but not for Porteus. Why the difference?

[brokenman]

What version of Porteus and chrome? Your profile says you are using v3.0.

[WavyLinesAreNotReal]

Porteus v3.1 | KERNEL: 3.17.4-porteus
Chrome Version 39.0.2171.71 (64-bit)

Note: The Chrome version is the one that was obtained from the repos in Porteus 3.1

[brokenman]

Does it work using firefox? Also I have put the latest version of chrome on the server if you wish to try it, but this may not help if your problem is related to a GPU incompatibility.

[WavyLinesAreNotReal]

The outcome is more or less the same with Chrome and Firefox. (I just obtained and tested the latest versions a few minutes ago)

[brokenman]

So you will need to start the browser via a terminal and then navigate to the game in question and post any relevant error output from the terminal. Also posting a system information dump (on pastebin) would be advisable.

[WavyLinesAreNotReal]

guest@porteus:~$ google-chrome-stable
[4281:4281:0125/003633:ERROR:nacl_fork_delegate_linux.cc(292)] Bad NaCl helper startup ack (0 bytes)
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[4271:4297:0125/003633:ERROR:logging.h(739)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.kwalletd was not provided by any .service files
[4271:4297:0125/003633:ERROR:native_backend_kwallet_x.cc(230)] Error contacting kwalletd (isEnabled)
[4271:4297:0125/003633:ERROR:native_backend_kwallet_x.cc(213)] Error launching kwalletd: error 'Could not find service 'kwalletd'.' (code 2)
[WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
[4271:4271:0125/003735:ERROR:browser_main_loop.cc(207)] gdkdrawable-x11.c:942 drawable is not a native X11 window (http://bugs.chromium.org/329991)

So a couple of things to note, the 1st line is myself entering the command 'google-chrome-stable'. The WARNING is immediately after I log into Facebook. After that, the last ERROR occurs anytime between then and the actual game (also during the game.)

You also requested a system dump. I'm not sure how to carry this out.

[fanthom]

Must be related to MTRR issues I recently fixed in kiosk.
Please generate 'psinfo' report so i could confirm that.

Thanks

[brokenman]

You also requested a system dump. I'm not sure how to carry this out.

Open a terminal and type: psinfo
Then paste the content of the dump on pastebin.com and link to it here.

I just tried the game under xfce and chrome (and logging in through facebook) and it started ok but then sat there on the loading screen. After 5 minutes I closed it. Same for firefox.
The link in your error refers to the oxygen theme bug so perhaps also try it under a different desktop first to discount this. It does smell of hardware acceleration, so perhaps it is related to MTRR

[WavyLinesAreNotReal]

http://pastebin.com/Tq4MDXxm

[fanthom]

hhmmm.... cant see anything MTRR related.
just to be sure - please post here an output of following commands:

Code: Select all

cat /proc/mtrr
dmesg | grep -A10 -i mtrr 

thank you

[WavyLinesAreNotReal]

guest@porteus:~$ cat /proc/mtrr
reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back
reg01: base=0x080000000 ( 2048MB), size= 1024MB, count=1: write-back
reg02: base=0x0ffe00000 ( 4094MB), size= 2MB, count=1: write-protect
reg03: base=0x0bc000000 ( 3008MB), size= 64MB, count=1: uncachable
reg04: base=0x0ba000000 ( 2976MB), size= 32MB, count=1: uncachable
reg05: base=0x100000000 ( 4096MB), size= 1024MB, count=1: write-back
reg06: base=0x0c0000000 ( 3072MB), size= 256MB, count=1: write-combining

guest@porteus:~$ dmesg | grep -A10 -i mtrr
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask F80000000 write-back
[ 0.000000] 1 base 080000000 mask FC0000000 write-back
[ 0.000000] 2 base 0FFE00000 mask FFFE00000 write-protect
[ 0.000000] 3 base 0BC000000 mask FFC000000 uncachable
[ 0.000000] 4 base 0BA000000 mask FFE000000 uncachable
[ 0.000000] 5 base 100000000 mask FC0000000 write-back
[ 0.000000] 6 disabled
[ 0.000000] e820: last_pfn = 0xba000 max_arch_pfn = 0x400000000
[ 0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]

[WavyLinesAreNotReal]

I figured it out. The windows version of flash player carries both 64 bit and 32 bit libraries. This makes the windows version extremely compatibility with flash apps. In contrast, the porteus version only contains the libraries for the architecture you select. So if a flash app requires 32 bit flash, you need 32 bit porteus to run it, because it has 32 bit flash libraries. 64 bit porteus won't work for that same reason.

My understanding right now is that HTML5 is going to eventually replace flash altogether. So in a few years none of this is going to matter, but in the mean time it's good to know that you can still run those apps within porteus. Just do a side by side installation of your favorite desktop in 64 bit and 32 bit mode. (See the guide on how to do this) Hopefully that answers related questions.