Ubuntu
chromium-browser package

chromium does not open downloaded files

Bug #1710789 reported by RCV
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Fix Released
High
Olivier Tilloy

Bug Description

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.

See original description
RCV (reichcv)
description: updated
description: updated
Revision history for this message
Olivier Tilloy (osomon) wrote :

I can reliably reproduce in a zesty VM. Investigating.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Olivier Tilloy (osomon)
Revision history for this message
Olivier Tilloy (osomon) wrote :

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

Revision history for this message
Olivier Tilloy (osomon) wrote :

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

summary: - chromium doesnot open downloaded files
+ chromium does not open downloaded files
Revision history for this message
Olivier Tilloy (osomon) wrote :

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

Revision history for this message
Olivier Tilloy (osomon) wrote :

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

Changed in chromium-browser (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Olivier Tilloy (osomon) wrote :

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.

Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

$ 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.

Revision history for this message
Olivier Tilloy (osomon) wrote :

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

Revision history for this message
Olivier Tilloy (osomon) wrote :

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.

Revision history for this message
Olivier Tilloy (osomon) wrote :

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).

Revision history for this message
RCV (reichcv) wrote :

>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?

Revision history for this message
Olivier Tilloy (osomon) wrote :

> May i test this package now?

Packages available at:

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

Revision history for this message
RCV (reichcv) wrote :

Yes, chromium is working correctly. Thank you

Revision history for this message
Walter (wdoekes) wrote :

Yeap, that fixes things. Thanks!

Olivier Tilloy (osomon)
Changed in chromium-browser (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.