@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- team/chromium-browser/xenial-stable/view/head:/debian/patches/enable- chromecast-by-default.patch
-- 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/1702407 Title: Startup crash after upgrading to 59.0.3071.109 on xenial Status in chromium-browser package in Ubuntu: In Progress Status in chromium-browser package in Debian: Fix Released Bug description: $ apt-cache policy chromium-browser chromium-browser: Installed: 59.0.3071.109-0ubuntu0.16.04.1289 Candidate: 59.0.3071.109-0ubuntu0.16.04.1289 Version table: *** 59.0.3071.109-0ubuntu0.16.04.1289 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 100 /var/lib/dpkg/status 49.0.2623.108-0ubuntu1.1233 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages $ chromium-browser Using PPAPI flash. --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version= Received signal 11 SEGV_MAPERR 000000000010 #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace() #1 0x7f8cc1af580b <unknown> #2 0x7f8cc1e20390 <unknown> #3 0x5619ce286dc8 <unknown> #4 0x5619ce289656 <unknown> #5 0x5619ce289df9 <unknown> #6 0x5619ce28a143 <unknown> #7 0x7f8cc1b70821 <unknown> #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask() #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask() #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask() #11 0x7f8cc1b2283d <unknown> #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run() #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler() #14 0x7f8cc1b49628 base::RunLoop::Run() #15 0x7f8cc1b75e36 base::Thread::ThreadMain() #16 0x7f8cc1b70726 <unknown> #17 0x7f8cc1e166ba start_thread #18 0x7f8cab4c53dd clone r8: 000000000000002e r9: 00005619cfcdd6ec r10: 0000000000000000 r11: 00007f8cab552f50 r12: 00007f8c1b0d1ff0 r13: 0000000000000008 r14: 0000000000000008 r15: 00007f8c1b0d1eb0 di: 0000000000000000 si: 00007f8c1b0d1eb0 bp: 00007f8c1b0d1f00 bx: 00007f8c1b0d1eb0 dx: 0000000000000061 ax: 0000000000000000 cx: 00007f8bf0047070 sp: 00007f8c1b0d1e60 ip: 00005619ce286dc8 efl: 0000000000010206 cgf: 0000000000000033 erf: 0000000000000004 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000010 [end of stack trace] Quits <1s after starting on desktop. Output from terminal-based launch is above. Worked earlier today before updating. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
