Paperwhite:
[root@kindle root]#
chromium-browser --temp-profile http://google.com
Quote:
/usr/lib/chromium-browser/chromium-browser: /usr/lib/libz.so.1: no version information available (required by /usr/lib/chromium-browser/chromium-browser)
[10607:10607:24768629928:FATAL:chrome/browser/zygote_host_linux.cc(123)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /usr/lib/chromium-browser/chromium-browser-sandbox is mode 4755 and owned by root.
Aborted
|
I'll have more of a fiddle at some point. "mode 4755" might be tricky on FAT.
I couldn't find a decent port to armv6 that wasn't android related.
I did find a raft of building for arm examples but didn't dig into whether there was a Framebuffer version.
Spoiler:
EDIT: Tried it on rootfs for the heck of it.
[root@kindle root]#
ls -al /usr/lib/chromium-browser/chromium-browser-sandbox
Quote:
|
-rwxr-xr-x 1 root root 10984 Aug 7 12:44 /usr/lib/chromium-browser/chromium-browser-sandbox
|
[root@kindle root]#
stat -c "%a %n" /usr/lib/chromium-browser/chromium-browser-s
andbox
Quote:
|
755 /usr/lib/chromium-browser/chromium-browser-sandbox
|
huh? *scratches head*
I'll think more on that at some point
EDIT: DOH! Forget the setuid bit.
Let me see if I can get this thing to a screenshottable state.
GDK_PIXBUF_MODULE_FILE="/mnt/us/extensions/system/lib/armv7l/gdk-pixbuf-2.0/2.10.0/loaders.cache" chromium-browser --temp-profile http://google.com
Yeah so with a bit of love (and more skills than me) That could probably be made usable
Seems like the only error left is:
Quote:
*** glibc detected *** /usr/lib/chromium-browser/chromium-browser --type=renderer --lang=en-US --force-fieldtest=CacheSize/CacheSizeGroup_0/
ConnCountImpact/_conn_count_7/DnsImpact/_default_enabled_prefetch/GlobalSdch/_global_enable_sdch/
IdleSktToImpact/_idle_timeout_10/SpdyImpact/_npn_with_spdy/ --user-data-dir=/tmp/tmp.Z8fARr --channel=12380.0x2b9dfc78.350096601: free(): invalid next size (fast): 0x2ba0e1d8 ***
|
Which no doubt baf could fix but is a bit beyond me.
Anyways. break over.
The "fail AW SNAP!" errors seems related to the javascript stuff.
http://nodejs.org/
I pictured a javascript free site that loaded just fine.
Cheers.