When start the browser, the message "Failed to connect to the native host. Make sure the 'plasma-browser-integration' package is installed." appears. The application is of course installed. Lack of any functionality.
What distribution is this? Can you check the file /etc/opt/chrome/native-messaging-hosts/org.kde.plasma.browser_integration.json and see whether the application under "path" is actually present.
Which files did the plasma-browser-integration package install? Where is your browser (please provide exact vendor and version) installed?
Distribution is KaOS. Chrome 69.0.3486.0 Browser is installed in /opt/google/chrome-unstable/ The path in file is /usr/bin/plasma-browser-integration-host
(In reply to majoballs from comment #3) > Distribution is KaOS. > Chrome 69.0.3486.0 > Browser is installed in /opt/google/chrome-unstable/ > > The path in file is /usr/bin/plasma-browser-integration-host Copy /etc/opt/chrome/native-messaging-hosts/org.kde.plasma.browser_integration.json to /etc/opt/chrome-unstable/native-messaging-hosts/org.kde.plasma.browser_integration.json and try again. Does it work?
(In reply to Fabian Vogt from comment #4) > (In reply to majoballs from comment #3) > > Distribution is KaOS. > > Chrome 69.0.3486.0 > > Browser is installed in /opt/google/chrome-unstable/ > > > > The path in file is /usr/bin/plasma-browser-integration-host > > Copy > /etc/opt/chrome/native-messaging-hosts/org.kde.plasma.browser_integration. > json to > /etc/opt/chrome-unstable/native-messaging-hosts/org.kde.plasma. > browser_integration.json and try again. Does it work? Clarifying the location of paths. I do not have the paths you have given me. There is only one: /opt/google/chrome-unstable/native-messaging-hosts/org.kde.plasma.browser_integration.json And that's it. There is nothing to copy.
Thanks for the update; changing status.
I'm having the same issue but with chromium-dev version 69.0.3497.12 as well as chromium version 68.0.3440.106 and plasma-browser-integration version 5.13.4 It does work correctly with firefox 61.0.2 and I think it also worked correctly with chrome.
(In reply to Ignus G. from comment #7) > I'm having the same issue but with chromium-dev version 69.0.3497.12 as well > as chromium version 68.0.3440.106 and plasma-browser-integration version > 5.13.4 > > It does work correctly with firefox 61.0.2 and I think it also worked > correctly with chrome. The plasma-browser-integration creates a file /etc/chromium/native-messaging-hosts/org.kde.plasma.browser_integration.json Tried copying it to where my chromium lives in /usr/lib/chromium-dev/native-messaging-hosts/ but it didn't work
Plasma browser integration works ok with the build of Chrome provided by Google, with plasma-browser-integration allowed to install as intended to: /etc/opt/chrome/native-messaging-hosts/org.kde.plasma.browser_integration.json In Kaos it appears that they provide a Chrome package which is basically a repack of the official google-chrome-unstable amd64 .deb package with some extra things added, hence not installed/using the standard stable Chrome paths p-b-i expects. In addition pkgbuild of their p-b-i package does: mkdir -p ${pkgdir}/opt/google/chrome-unstable/native-messaging-hosts mv ${pkgdir}/etc/opt/chrome/native-messaging-hosts/org.kde.plasma.browser_integration.json ${pkgdir}/opt/google/chrome-unstable/native-messaging-hosts/org.kde.plasma.browser_integration.json rm -r ${pkgdir}/etc/opt so obviously trying to make p-b-i work with their distro provided Chrome. So at least for Kaos, I would suspect this is a downstream distro issue in their implementation, and not a KDE bug.
I have a similar issue with Firefox 64 installed to "/opt/firefox/". "Plasma integration" addon refuses to start because of lacking "plasma-browser-integration" package. System default browser with the same version (executable "/usr/bin/firefox", the same user profile) works properly with the addon, so it's likely that the reason of the bug relates to non-standard browser installation path.
Closing this now. If it works with official packaging I am not responsible for and do not care about any needless downstream fuzzing with paths.
*** Bug 442443 has been marked as a duplicate of this bug. ***
Created attachment 150077 [details] Plasma integration with Chromium does not work. Plasma integration with Chromium does not work.
Plasma integration with Chromium does not work.
Please open a downstream bug report.