> @Björn: that crash on zesty, did it have a similar backtrace?
Ups, I miswrote: I saw that issue on xenial and on _yakkety_, not on
zesty. Forgot that I punted that. So NO report from zesty yet (but there
might as well be). Stacktrace looked similar from memory, and esp.
revitalizing with
@Lonnie: as soon as technically possible (this might be early next
week). Have you tested the packages in the PPA? Could you confirm
whether they solve the issue for you? The more confirmations we get from
individual testers, the more confidence we can have in the validity of
the patch, which
When will this patch be available via Ubuntu's normal update program?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to 59.0.3071.109 on xenial
To
@Björn: that crash on zesty, did it have a similar backtrace?
Regarding that debian bug, the media router component extension is
indeed disabled by default on chromium, but we have a patch to re-enable
it, and it seems to work well: http://bazaar.launchpad.net/~chromium-
@Gareth: did you try installing the dbgsym ddeb packages, as instructed
there: https://wiki.ubuntu.com/Debug%20Symbol%20Packages#Getting_-
dbgsym.ddeb_packages ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: chromium-browser (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to 59.0.3071.109 on xenial
Re comment #23:
- This happened to me on both xenial and also on zesty (though it took a while
to trigger on the later)
=> disabling media router (or clearing the profile) fixed it.
Also linking https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833477 as it
says:
* Disable builtin media
Tested chromium-fix-1702407 ppa with
-ubuntu 16.0.4
-setting the Media Router option to default again.
-copied over original chromium config file.
Everything's working so far no crashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
PPA updates fix the problem for me on 16.04.2
I'm curious as to why I couldn't install the debug symbols though - can
anyone advise?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702407
> To everyone affected by the crash, could you please try the packages
in that PPA, and see if the crash goes away?
Done. On xenial it works fine.
Thanks Olivier! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the quick feedback Trent!
To everyone affected by the crash, could you please try the packages in that
PPA, and see if the crash goes away?
sudo add-apt-repository -y ppa:osomon/chromium-fix-1702407
sudo apt update
sudo apt dist-upgrade
Note that packages for trusty
Test builds seem to work here! Casting didn't even break :)
Thanks Olivier!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to 59.0.3071.109 on xenial
I only use chromium to run signal and since the last update, on
59.0.3071.109-0u, if I start it without extensions and then with the
app-id:
chromium-browser --disable-extensions && \
/usr/bin/chromium-browser --profile-directory=Default
--app-id=bikioccmkafdpakkkcpdbppfkghcmihk
it does run for
Packages with a tentative fix are currently building in
https://launchpad.net/~osomon/+archive/ubuntu/chromium-
fix-1702407/+packages. Once built (in a few hours), that should allow
people affected by the crash to test the fix.
--
You received this bug notification because you are a member of
Ouch! I have been known to boast about my proofreading skills ...
confirmed that #19 does in fact work, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after
Andrew,
Try the workaround in #19.
Note: --disable-extensions with an S, not --disable-extension.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to 59.0.3071.109 on
Linux Mint 17.2 Rafaela "Ubuntu" VERSION="14.04.2 LTS, Trusty Tahr"
The upgrade to 59.0.3071.109 stopped chrome from starting;
Purging, etc. had no effect; likewise turning off wi-fi; also:
andrew@andrew-desktop ~/.config $ chromium-browser --disable-extension
Using PPAPI flash.
If I understand correctly
https://bugs.chromium.org/p/chromium/issues/detail?id=409318 and if that
information is still current, packages built with clang are not affected. Which
would explain why all the reports affect xenial and trusty (haven't been
getting reports for yakkety, but assuming
Rohan,
Confirmed. I did have to interact with the cast extension after
enabling wifi to get it to crash though. It may have just been
coincidence though (wireless network list was probably cached).
I also tried plugging and unplugging the ethernet cable with wifi off,
which did not seem to
I was able to wget the diff from
https://bugs.chromium.org/p/chromium/issues/attachment?aid=116063. I
believe adapting it to the current code base should resolve the crash.
However I do not have a 16.04 build env to test on my system with wifi
nor a wifi adapter to test on my 14.04 system.
Just an FYI, this can be worked around by disabling the media router
extension.
1) Start chromium on the command line with: chromium-browser
--disable-extensions
2) Navigate to chrome://flags
3) Search for "media router" and set it to "Disabled"
I have tested 59.0.3071.109-0ubuntu0.16.04.1289
@osomon: The issue seems to be unrelated to whether you are online or
offline via wifi.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to 59.0.3071.109
To clarify:
togs@nb03:~$ iwconfig
vmnet8no wireless extensions.
eth0 no wireless extensions.
lono wireless extensions.
virbr0no wireless extensions.
wlan0 IEEE 802.11abgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=22 dBm
The crash happens on the following line:
NetworkMap::iterator existing_access_point_iter =
network_map->find(ssid);
in extensions::NetworkingPrivateLinux::AddOrUpdateAccessPoint(…)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@togs: it would be useful if you could verify whether turning off wifi
makes the issue go away. If not, that might be a different issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Have the same issue here on Ubuntu 14.04.5 LTS with the following
packets installed:
dpkg -l | grep chromium
ii chromium-browser
59.0.3071.109-0ubuntu0.14.04.1186amd64Chromium
web browser, open-source version of Chrome
So, I have been using the browser normally all morning without disabling
the extensions. As soon I turned on TV, which has a Chromecast dongle
attached, the browser crashed. Turned off TV, but the browser continued
crashing. So I ran `sudo network-manager stop` and I could open the
browser again,
Upstream bug report:
https://bugs.chromium.org/p/chromium/issues/detail?id=734325
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702407
Title:
Startup crash after upgrading to 59.0.3071.109 on
To everyone affected by the crash (I haven't managed to reproduce it
locally yet): can you please disable networking on your computer (turn
off wifi) and check whether that makes chromium start normally?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks Giuseppe, that's very useful. I extracted a full backtrace from
the crash, attaching it here.
** Summary changed:
- Update breaks chromium-browser on Ubuntu Mate 16.04.2
+ Startup crash after upgrading to 59.0.3071.109 on xenial
** Changed in: chromium-browser (Ubuntu)
Assignee:
31 matches
Mail list logo
