The crash, if you'd like to call it a crash, was about gpu hardware
acceleration. I tried to append --disable-gpu from console and this made
it go away plus the browser itself is much faster now in rendering. I
then disabled it permamently in the options.
The device is a nvidia tegra, the binary
Can you please post
$ glxinfo | grep OpenGL
and
$ dmesg | grep -i drm
Chromium creates multiple processes when working, and above is the crash
of the GPU sub-process. Maybe it tries to use GPU acceleration, but
fails to do ot, and the GPU is not blacklisted or you set it to ignore
the
I managed to add enough swap space but unfortunatley it doesn't make any
difference, the trace is the same as printed without --debug in #8
My guess is that it is very similar problem to
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184
, but I don't get the segfault or any
@herrtimson: try launching without --debug. Is the stacktrace printed on
stderr any more complete?
--
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/1664147
Title:
Chromium on
Awesome! Thank you so much Oliver! @osomon
--
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/1664147
Title:
Chromium on trusty too outdated; not supported by gmail
Status in
Well, I just installed the additonal dbgsym package for chromium and
started it with
chromium-browser --debug 2>&1 | tee gdb-chromium.txt
Apparently running out of memory, the device has only 433mb ram and an
additional 266mb as a swap on a SD card. However, I attached the small logfile
which
Thanks for the feedback @herrtimson. Can you please install debug
symbols and see if that results in a more verbose stack trace printed on
the console?
You will need to follow instructions at
https://wiki.ubuntu.com/DebuggingProgramCrash#Non-built-
in_debug_symbol_packages_.28.2A-dbgsym.29 to
thank you for your effort of the upgrade to recent stable chromium-58
I am using it with the arm port of Ubuntu-14.04 on a ac 100 chromebook,
where I get something which seems to be a segmention fault while
starting the browser. This is the output from the console
Received signal 11 SEGV_MAPERR
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Released
--
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/1664147
Title:
Chromium on trusty too
Thank you. I've been testing the ppa version, and it works fine. The two
noticeable issues are that chromecast doesn't work anymore (known
upstream issue I guess), and flash's behaviour isn't the same as chrome.
--
You received this bug notification because you are a member of Desktop
Packages,
I’ve packaged chromium-browser 58.0.3029.81 for trusty, it is being
validated by the security team and will hopefully hit -updates soon.
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: chromium-browser (Ubuntu)
Status:
It looks like chromium 57 has been pushed to the ppa. I tried it on
trusty, and it works. I noticed one difference compared to chrome 57.
Flash has been deprecated in chrome 57, and set to on-demand only.
Ironically, chromium runs flash by default. The on-demand setting
doesn't exist on chromium
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-5215
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-5217
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-5218
** CVE added: http://www.cve.mitre.org/cgi-
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-5211
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-5214
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-5213
** CVE added: http://www.cve.mitre.org/cgi-
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-5181
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-5182
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-5183
** CVE added: http://www.cve.mitre.org/cgi-
It looks like this is the same problem as fixed here:
https://github.com/RussianFedora/chromium/commit/044d0710f2fefdbe3c58508806b8cb30700cb5b0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
news ?
chromium-browser - 56.0.2924.76-0ubuntu0.14.04.1159 wont build... Can someone
fix it ?
https://launchpad.net/~canonical-chromium-
builds/+archive/ubuntu/stage/+packages
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Considering the latest news about the vulnerability of SHA-1 (see
https://shattered.it/ ), any Chromium version < 56 is potentially
vulnerable.
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Desktop
Packages, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
** Tags added: trusty
--
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/1664147
Title:
Chromium on trusty too outdated; not supported by gmail
Status in chromium-browser
20 matches
Mail list logo
