Created attachment 158354 [details] The Plasma Browser Extension reporting an error about being unable to connect to the native host running SUMMARY On a completely fresh install of the latest user edition of KDE neon, the Plasma Browser Integration cannot communicate with the native host when using Firefox. Google Chrome installed from the .deb file from https://www.google.com/chrome/ picks up the integration out of the box. STEPS TO REPRODUCE 1. Install KDE Neon User Edition 2. Make sure all your software is up to date (I did this by using Discover) 3. Notice that Firefox does not have a functional plasma browser integration OBSERVED RESULT The Extension in Firefox says "Failed to connect to native host" SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon User Edition (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.19.0 Kernel 5.19.0-40-generic Graphics Platform: X11 ADDITIONAL INFORMATION Plasma Browser Integration Version (pulled from 'apt search plasma-browser-integration') plasma-browser-integration/jammy,now 5.27.4-0xneon+22.04+jammy+release+build24 amd64 [installed,automatic] Plasma Browser Integration Version (Reported from Firefox) 1.8.1 (Last Updated April 22, 2023) Firefox version: 112.0.1 (64-bit) Attached is the error reported by the extension.
(In reply to Michael Eisemann from comment #0) > Created attachment 158354 [details] > The Plasma Browser Extension reporting an error about being unable to > connect to the native host running > > SUMMARY > > On a completely fresh install of the latest user edition of KDE neon, the > Plasma Browser Integration cannot communicate with the native host when > using Firefox. Google Chrome installed from the .deb file from > https://www.google.com/chrome/ picks up the integration out of the box. > > > STEPS TO REPRODUCE > 1. Install KDE Neon User Edition > 2. Make sure all your software is up to date (I did this by using Discover) > 3. Notice that Firefox does not have a functional plasma browser integration > > OBSERVED RESULT > The Extension in Firefox says "Failed to connect to native host" > > SOFTWARE/OS VERSIONS > Linux/KDE Plasma: KDE Neon User Edition > (available in About System) > KDE Plasma Version: 5.27.4 > KDE Frameworks Version: 5.105.0 > Qt Version: 5.19.0 > Kernel 5.19.0-40-generic > Graphics Platform: X11 > > ADDITIONAL INFORMATION > Plasma Browser Integration Version (pulled from 'apt search > plasma-browser-integration') > plasma-browser-integration/jammy,now > 5.27.4-0xneon+22.04+jammy+release+build24 amd64 [installed,automatic] > > Plasma Browser Integration Version (Reported from Firefox) > 1.8.1 (Last Updated April 22, 2023) > > Firefox version: 112.0.1 (64-bit) > > Attached is the error reported by the extension. Just updating to say I am using the native installation of Firefox, not a snap or a flatpak.
The apparmor profile shipped with the native version of Firefox that's used by neon prevents access to the browser integration, however it's usually disabled by default using a symbolic link in /etc/apparmor.d/disable/usr.bin.firefox -> ../usr.bin.firefox. Can you check to see if you've got that?
(In reply to Paul Worrall from comment #2) > The apparmor profile shipped with the native version of Firefox that's used > by neon prevents access to the browser integration, however it's usually > disabled by default using a symbolic link in > /etc/apparmor.d/disable/usr.bin.firefox -> ../usr.bin.firefox. Can you check > to see if you've got that? That symlink is missing. Here are the contents of /etc/apparmor.d/disable/ me@neon:/etc/apparmor.d/disable$ ls -l total 0 lrwxrwxrwx 1 root root 33 Apr 20 03:24 usr.sbin.rsyslogd -> /etc/apparmor.d/usr.sbin.rsyslogd However, creating it manually and rebooting my computer did seem to resolve the issue.
Confirming the bug because I've seen it myself and also seen others reporting it on Reddit .
(In reply to Michael Eisemann from comment #3) > (In reply to Paul Worrall from comment #2) > > The apparmor profile shipped with the native version of Firefox that's used > > by neon prevents access to the browser integration, however it's usually > > disabled by default using a symbolic link in > > /etc/apparmor.d/disable/usr.bin.firefox -> ../usr.bin.firefox. Can you check > > to see if you've got that? > > That symlink is missing. Here are the contents of /etc/apparmor.d/disable/ > > me@neon:/etc/apparmor.d/disable$ ls -l > total 0 > lrwxrwxrwx 1 root root 33 Apr 20 03:24 usr.sbin.rsyslogd -> > /etc/apparmor.d/usr.sbin.rsyslogd > > > However, creating it manually and rebooting my computer did seem to resolve > the issue. Creating the disable apparmor symlink also fixes «The WidevineCdm plugin has crashed» in sites such as spotify.
*** Bug 461505 has been marked as a duplicate of this bug. ***