[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubu
thanks. For me consider this as closed.
--
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/1696207
Title:
Chromium crash
Status in chromium-browser package in Ubuntu:
Incomple
@Joachim: do you mean that you're not seeing the crash any longer now?
What's your version of chromium now? Please, do not use the canonical-
chromium-builds/stage PPA, it's not meant for end-users (and indeed you
won't be able to install debug symbols for that PPA with the method I
suggested).
@G
Oh. I wondered what «stage» meant in the URL, and looked it up. Looks
like it's the staging (a.k.a proposed?) repo for upcoming releases, with
unstable chromium builds. Do not have any idea how that repo has been
added to my system. Anyway Removing it and re-installing chromium
did the trick.
Hi.
I'm having the same problem:
Chromium 59.0.3071.86 Built on Ubuntu , running on Ubuntu 16.04
This is the output from terminal:
Received signal 11 SEGV_MAPERR 0010
#0 0x7fb63985b425 base::debug::StackTrace::StackTrace()
#1 0x7fb63985b80b
#2 0x7fb639b86390
#3 0x5602ce752d68
#4 0x56
Well I was installed de package but it seems it was not laoded, now I see stuff
like that
[526:526:0619/220831.336873:ERROR:display_info_provider_aura.cc(31)] Not
implemented reached in virtual void
extensions::DisplayInfoProviderAura::UpdateDisplayUnitInfoForPlatform(const
display::Display&,
Hello,
yes I have installed it I will retry tonight.
--
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/1696207
Title:
Chromium crash
Status in chromium-browser package in Ubunt
Thanks Grummfy. Are you sure you installed the debug symbols as I requested in
comment #2 ?
No need to launch the app with the --debug flag, if you have the debug symbols
a complete stack trace will be printed in the console when the app crashes, and
that should be enough to identify the issue.
Hi,
so, after some change I see that when I launch the browser with
"--no-experiments" flag I got no issue. So disable it and it work again ;)
To come back to your question : when it's start crashing it crashing
every time (reboot or leaving session change nothing). When I restart
with no-exper
here is the output of "chromium-browser --debug" command that start gdb
automatically
i use run and continue (i think it's almost the only think I know how to deal
with gdb)
hope it helps.
** Attachment added: "debug.log"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/169620
Thanks for the report Grummfy. Is chromium crashing reliably/regularly
at startup, or was that a one-off?
If the former, can you please install the debug symbols and launch
chromium from a terminal, that should produce a more verbose stacktrace
that we can use as a starting point for further inves
11 matches
Mail list logo
