Unable to reproduce this issue on Ubuntu 14.04 using chromium build #60.0.3112.101. Able to open the .doc file in Libreoffice by deafault from the downloads.

Oliver@ Could you please let us know is this issue seen on incognito mode as well and Are you seeing this issue on chrome latest stable #60.0.3112.101?

Thanks!

The issue doesn't seem to happen on Ubuntu 14.04. Only on 17.04 and 17.10.
Note that strangely enough it isn't 100% reproducible. Sometimes the document opens correctly in libreoffice. Most of the time it doesn't though, and the error message is printed in the terminal.

Incognito mode is also affected.

The latest stable chrome doesn't appear to be affected. That is to be expected, given that it is built with is_component_build=false, and thus there is no stub libmirclient.so.9. I guess only component builds are affected, which is currently the way chromium is built on ubuntu (I'm working on changing this, but that's orthogonal).

Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tested in chrome Stable #60.0.3112.101,Beta #61.0.3163.49 & Canary #62.0.3191.0 on Ubuntu 14.04 & 17.04 and not able to reproduce the issue.Please find the screen shots for your reference.

As per comment #3 issue reproduce inconsistently.Some one from UI>Browser>Downloads team please look in to this issue.

Thanks in Advance.

Deleted: 756061.png 173 KB

	756061.png 173 KB View Download

Another way to trigger the same issue, is attempt to use xdg-open to handle url schemes.

Steps to reproduce:
1) create file ~/.local/share/applications/some-protocol.desktop with following contents:

[Desktop Entry]
Name=whatever
Exec=zenity --info
Type=Application
MimeType=x-scheme-handler/someprotocol;

2) create html file with following contents:
<a href="someprotocol:someurl">Click here</a>

3) click the link

Expected behaviour:
zenity opens

Actual behaviour:
nothing happens, when chrome running on console, I see following output:

$ chromium-browser 
Using PPAPI flash.
 --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version=

(chromium-browser:4878): Gtk-WARNING **: Theme parsing error: gtk.css:68:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version

(chromium-browser:4878): Gtk-WARNING **: Theme parsing error: gtk.css:69:35: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version

(chromium-browser:4878): Gtk-WARNING **: Theme parsing error: gtk.css:73:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version
kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "someprotocol"
kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "someprotocol"
kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "someprotocol"
kf5.kio.core: "preferred service for x-scheme-handler/someprotocol" "some-protocol"
kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "someprotocol"
kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "someprotocol"
kf5.kio.core: "preferred service for x-scheme-handler/someprotocol" "some-protocol"
/usr/bin/zenity: 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


Running xdg-open by hand works (like this: xdg-open someprotocol:someurl)

OS: Kubuntu 17.04

Contents of about:version

Chromium	60.0.3112.78 (Entwickler-Build) Built on Ubuntu , running on Ubuntu 17.04 (64-Bit)
Überarbeitung	a06489456eeba3939f2f058a4e5bd6178e7b3bb9-
Betriebssystem	Linux
JavaScript	V8 6.0.286.44
Flash	26.0.0.151 /usr/lib/adobe-flashplugin/libpepflashplayer.so
User-Agent	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/60.0.3112.78 Chrome/60.0.3112.78 Safari/537.36
Befehlszeile	/usr/lib/chromium-browser/chromium-browser --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version=26.0.0.151 --enable-pinch --flag-switches-begin --flag-switches-end
Ausführbarer Pfad	/usr/lib/chromium-browser/chromium-browser
Profilpfad	/home/miko/.config/chromium/Default

Tested in chrome Stable & Beta # 61.0.3163.79 on & Canary #63.0.3207.0 on Ubuntu 14.04 & 17.04 and not able to reproduce the issue.

@ olivier: If possible,Please create new profile without extensions and apps.Re-check once in latest Stable/Beta/Canary build and let us know the observations of the issue which would help us to triage the issue further.

Thanks in Advance.

If it's just showing up in component builds, does that mean it won't affect any shipped versions of Chrome?  Dropping priority if that is the case, but I'll try to find someone who can help us track this down.

Yes, as stated in comment #3, the issue affects only component builds, so chrome itself is not affected, only custom chromium builds using is_component_build=true.

Note that with the next stable update in Ubuntu (due this week), this will cease to be a problem as chromium will be built with is_component_build=false on all supported releases.

The issue remains valid for component builds, so might be worth looking into (with reduced priority of course).

Thank you for providing more feedback. Adding requester "rbasuvula@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

@dtrainor-- Could you please check comment #10 and update the thread accordingly.

Thanks!

Since it's not a problem for any version we ship, I agree it's relatively low priority, but it would still be nice to not fail.  Reassigning to thomasanderson@ for his work on https://codereview.chromium.org/2885223002.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6f81d270e70f54c1c98afc394a7b0da5f8e20aa1

commit 6f81d270e70f54c1c98afc394a7b0da5f8e20aa1
Author: Tom Anderson <thomasanderson@chromium.org>
Date: Fri Oct 20 18:23:31 2017

Add more mir symbols to our stub library

BUG= 756061 
TBR=pkasting@chromium.org

Change-Id: I931ae4af5a31f09b373fc2b04556cc527db37be3
Reviewed-on: https://chromium-review.googlesource.com/729225
Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#510499}
[modify] https://crrev.com/6f81d270e70f54c1c98afc394a7b0da5f8e20aa1/third_party/protobuf/mirclient.cc
[modify] https://crrev.com/6f81d270e70f54c1c98afc394a7b0da5f8e20aa1/third_party/protobuf/mirclient.map

OP, is the issue fixed after the cl in c#16?

All builds of chromium on ubuntu are now done with is_component_build=false, so there's no stub libmirclient anymore, and thus the issue is not affecting us any longer. There's not much point in reverting our builds to is_component_build=true just for the sake of testing, perhaps people that do component builds locally for testing can confirm the issue is fixed?