https://bugs.kde.org/show_bug.cgi?id=396525
Rik Mills <rikmi...@kubuntu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rikmi...@kubuntu.org
--- Comment #9 from Rik Mills <rikmi...@kubuntu.org> ---
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.
--
You are receiving this mail because:
You are watching all bug changes.
