Indeed it is expired, I haven't been able to run chromium on my rpi3 due
to its memory requirements in years.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1673636
Title:
Ch
> data that they have stored locally will continue to be available
locally.
Doesn't forcing deletion of the profile violate this claim?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
I have a Raspberry Pi 3 running Ubuntu Mate 16.04.2 LTS armhf, and the
latest chromium-browser release (56.0.2924.76-0ubuntu0.16.04.1268)
displays only the "Aw, snap!" error instead of opening the page.
Here's what it outputs:
chromium-browser --type=renderer --enable-pinch
@cmiller If you need any impersonal information about the crash on my
system, I would be happy to porvide it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1563184
Title:
Ch
I was aware that the InitializeSandbox error was not related to the issue
because I get that from like half of my applications. XD
The chromium-browser script that starts chromium-browser supports the
flag --no-touch-pinch, which I find a little odd because it essentially turns
it into --disable
*** This bug is a duplicate of bug 1563184 ***
https://bugs.launchpad.net/bugs/1563184
Since you get the exact same error, this is almost definitely a duplicate of
this bug:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184
The issue affects the entire armhf build of chr
Did you get something like this when run in the terminal:
$ chromium-browser
Segmentation fault (Core dumped)
$
Where it has a segfault or like this:
$ chromium-browser
$
Where it exits normally?
--
You received this bug notification because you are a member of Desktop
Packages, which is subs
This bug affects me as well, but I have found a tutorial explaining how to get
it.
https://ubuntu-mate.community/t/tutorial-flash-player-for-chromium-and-firefox/3598
https://ubuntu-mate.community/t/tutorial-extract-pepper-flash-plugin-v-20-0-0-228-r1-and-above-from-samsung-chromebook-2-13/3614/1
This could be a duplicate of #1563184, if it's just an issue with the
armhf build of chromium-browser instead of the Raspberry Pi's kernel.
Would you please post the error message you get when it crashes?
Possible duplicate of:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563
I have had several other bugs have this error:
``
I think that the name should be changed to be more descriptive:
`Chromium-browser armhf crashes with "InitializeSandbox() called with
multiple threads in process gpu-process"`
** Summary changed:
- InitializeSandbox() called with multiple thread
I upgraded my Raspberry Pi 2 to Ubuntu Mate 16.10 LTS and Chromium
continues to segfault when launched from the menu, but when I launched
it from the terminal it opened a completely transparent window that
proceeded to do absolutely nothing. When I finally got impatient and
^Ced it, then it had a s
I have had almost the exact same problem on a Raspberry Pi 2 running Ubuntu
Mate 15.10.
uname -a:
Linux RaspberryPi 3.18.0-20-rpi2 #21-Ubuntu SMP PREEMPT Sun Apr 5 01:56:02 UTC
2015 armv7l armv7l armv7l GNU/Linux
$ chromium-browser
[2815:2815:0403/092234:ERROR:sandbox_linux.cc(334)] InitializeSa
12 matches
Mail list logo
