chromium does not open downloaded files

[RCV]

I have up to date Ubuntu 17.04. Recently, Chromium stoped to open downloaded files.

If i download and open doc file from chromium, in command line i see the following message:

/usr/lib/libreoffice/program/soffice.bin: relocation error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: symbol mir_display_config_release, version MIR_CLIENT_0.21 not defined in file libmirclient.so.9 with link time reference

If i download pdf file i see the same message with evince instead of libreoffice.

It looks like more general problem, but I still can open files from these two applications or using xdg-open.

I tried to work with new chromium profile, but i get the same message no matter what and files cannot be opened.

[Olivier Tilloy (osomon)]

I can reliably reproduce in a zesty VM. Investigating.

[Olivier Tilloy (osomon)]

Not reproducible on xenial or trusty, but I can observe the same issue on artful.

[Olivier Tilloy (osomon)]

Symbol mir_display_config_release is missing from the mir symbol stubs in third_party/protobuf/mirclient.cc¹, that might explain the problem.

¹ https://cs.chromium.org/chromium/src/third_party/protobuf/mirclient.cc

[Olivier Tilloy (osomon)]

Test packages with added stub symbol currently building in https://launchpad.net/~osomon/+archive/ubuntu/cr-test-fix-1710789/+packages.

[Olivier Tilloy (osomon)]

I confirm that adding mir_display_config_release to the symbol stubs fixes the issue on zesty.

[Olivier Tilloy (osomon)]

Nope, that was a false hope. I’m still seeing the problem on zesty and artful (only amd64, not on i386), even after patching chromium to add the missing stub symbol.

[Alan Griffiths (alan-griffiths)]

$ objdump -T /usr/lib/chromium-browser/libmirclient.so.9 | grep mir_display_config_release
$ objdump -T /usr/lib/x86_64-linux-gnu/libmirclient.so.9 | grep mir_display_config_release
0000000000072860 g DF .text 0000000000000012 MIR_CLIENT_0.21 mir_display_config_release

What appears to be happening is that soffice.bin is loading a stub version of libmirclient.so.9 belonging to chromium-browser.

That implies that chromium-browser has reconfigured link loading and then started an external program that needs the real libmirclient.so.9.

[Olivier Tilloy (osomon)]

Upstream bug report: https://bugs.chromium.org/p/chromium/issues/detail?id=756061

[Olivier Tilloy (osomon)]

Note that google-chrome is not affected as it's built with is_component_build=false, and thus it doesn't ship any stub libmirclient.so.9.

[Olivier Tilloy (osomon)]

I have switched builds for the beta branch to is_component_build=false, so this bug should go away with the next major chromium update (61).

[RCV (reichcv)]

>I have switched builds for the beta branch to is_component_build=false, so this bug should go away with the next major chromium update (61).

May i test this package now?

[Olivier Tilloy (osomon)]

> May i test this package now?

Packages available at:

https://launchpad.net/~osomon/+archive/ubuntu/cr-test-officialbuild/+packages

[RCV (reichcv)]

Yes, chromium is working correctly. Thank you

[Walter (wdoekes)]

Yeap, that fixes things. Thanks!