Sorry I didn't tell the whole story... close chromium $ sudo apt-get purge chromium rename ~/.config/chromium (which remained after purge, not sure if it should?) reboot $ sudo apt-get install chromium copy old Bookmarks to new ~/.config/chromium/Default/
Before this, I tried upgrading a VM with 16.04.1 to the latest version of chromium, which worked perfectly, and still worked after dist-upgrade to 16.04.2 - but the VM (and certainly its version of chromium) was pretty much otherwise unused, so I wondered aloud about potential causes. I don't see why a reboot should make a difference but I hope that works for you - mine is now working normally again. I should have explained more fully before. Gareth On Wed, 5 Jul 2017, at 14:05, Giuseppe_M wrote: > @Gareth Evans > > Your suggestion, and without copying back the old Bookmarks, works only > the first time, when you close and reopen the browser it crashes again, > with: > > Received signal 11 SEGV_MAPERR 000000000008 > #0 0x0000b762af0a base::debug::StackTrace::StackTrace() > #1 0x0000b762a83a base::debug::StackTrace::StackTrace() > #2 0x0000b762b388 <unknown> > #3 0x0000b77bec20 ([vdso]+0xc1f) > #4 0x00008055948a <unknown> > #5 0x00008055c01b <unknown> > #6 0x00008055c7d4 <unknown> > #7 0x00008055cb1b <unknown> > #8 0x000080555586 <unknown> > #9 0x0000b76afe2e <unknown> > #10 0x0000b76afdb3 <unknown> > #11 0x0000b762c80b base::debug::TaskAnnotator::RunTask() > #12 0x0000b7658f3b base::MessageLoop::RunTask() > #13 0x0000b765a292 base::MessageLoop::DeferOrRunPendingTask() > #14 0x0000b765b399 base::MessageLoop::DoWork() > #15 0x0000b765bfbd base::MessagePumpLibevent::Run() > #16 0x0000b7658304 base::MessageLoop::RunHandler() > #17 0x0000b76855dd base::RunLoop::Run() > #18 0x0000b76b5c61 base::Thread::ThreadMain() > #19 0x0000b76afcdf <unknown> > #20 0x0000b7786295 start_thread > #21 0x0000afd6705e clone > gs: 00000033 fs: 00000000 es: 0000007b ds: 0000007b > edi: 00000000 esi: a824bd60 ebp: 8f1507f8 esp: 8f150780 > ebx: 835cb528 edx: 8f150714 ecx: a824bcb0 eax: 00000000 > trp: 0000000e err: 00000004 ip: 8055948a cs: 00000073 > efl: 00210282 usp: 8f150780 ss: 0000007b > [end of stack trace] > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1702407 > > Title: > Update breaks chromium-browser on Ubuntu Mate 16.04.2 > > Status in chromium-browser package in Ubuntu: > Confirmed > > 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 -- 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: Update breaks chromium-browser on Ubuntu Mate 16.04.2 Status in chromium-browser package in Ubuntu: Confirmed 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 : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
