I just installed KDE Neon, and when I opened Firefox, a pop-up arrived on my taskbar telling me to go install the Firefox extension “Plasma Integration” but this one does not work and displays a error: “check that you have installed plasma-browser-integration”, and I checked, it is installed!
I don’t understand why it doesn’t work…
I believe there version of Firefox has a extension to work with Plasma-Integration. I would go into extensions in Firefox and remove it. I’ve never been a fan of integrating the desktop with the internet in any OS.
Do you mean this?
Here with openSUSE Leap 15.5.
Yes it’s the Plasma Integration firefox extension
You could try de-installing the Firefox Extension – exiting Mozilla Firefox – opening Mozilla Firefox again – and then, from the Mozilla Store, reinstalling the KDE Plasma Integration.
- I suggest that, you search for “KDE Plasma Integration” in the Mozilla Store – only 2 items appear for me – the Plasma Integration plug-in (about 58 thousand users) and, something else for Ubuntu with only a few hundred users.
Just uninstall the extension and then go into System Settings and make sure it’s unchecked there.
I know that it’s a old post… If your issue are the same that I come across, I could solve this issue following this answers from Reddit post Plasma browser extension - failed to connect to the native host.
Your Firefox must be what comes with KDE Neon. The issue is because the apparmor. Run the commands in your terminal:
sudo ln -s /etc/apparmor.d/usr.bin.firefox /etc/apparmor.d/disable/
sudo apparmor_parser -R /etc/apparmor.d/usr.bin.firefox
Disclaimer: I didn’t understand what it really did, but now the extension works.
Strange, here on openSUSE Leap 15.5 I’m not experiencing the issue being reported here –
And, AppArmor doesn’t have anything configured which is related to Firefox –
apparmor module is loaded.
67 profiles are loaded.
66 profiles are in enforce mode.
1 profiles are in complain mode.
0 profiles are in kill mode.
0 profiles are in unconfined mode.
3 processes have profiles defined.
3 processes are in enforce mode.
/usr/sbin/avahi-daemon (978) avahi-daemon
/usr/sbin/nscd (1013) nscd
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
0 processes are in mixed mode.
0 processes are in kill mode.
And, in the directory tree ‘/etc/apparmor.d/’ I can’t find any mention of a filename related to Firefox.
You may have to raise a KDE Bug Report against the KDE Neon release you’re using.
FWIW, I would be very, very hesitant about solving a browser extension issue by disabling the primary kernel security module from monitoring the primary source of vulnerabilities for a desktop system.
Thank you for the warning. I will test if other Firefox software format can work without “modifications”.
Given the reply by Mat, I suggest that, a Bug Report against your Distribution is definitely needed.
Did you do anything unique that you know of to get that Firefox version? It looks to me like 120.0 isn’t scheduled to release to stable until the 21st. Perhaps something that brought in a beta version also impacted the extension?
@johnandmegh is correct. If you go to the Mozilla site and download Firefox, the current version is firefox-119.0.1
Is this the Firefox deb package or the snap? Because if it is the snap, then that could be an issue. Ubuntu 22.04 LTS uses a Firefox snap by default and this might be carried over into Neon. This describes how to replace the snap with a deb package if this is the case. The Firefox snaps has had a few challenges integrating with the system, so this certainly sounds plausible.
johnandmegh, I only updated the applications in Discover. Answering depmann too, this Firefox comes with KDE Neon. Sorry, I don’t know if it’s snap or deb package.
snap list and the Firefox didn’t seem.
The Firefox in KDE neon is the .deb version.
KDE neon uses the Mozilla Team PPA for Firefox.
Sometimes the Firefox and Thunderbird versions from the Mozilla Team PPA are not yet officially released (kind of “release candidate” versions). Mostly these versions are officially released only a few hours or days later.
I am not a Neon guy, so I don’t know how to tell you to check this, but it sure sounds like a repository issue here.
Thank you for answer. So… Should I uninstall this PPA that bring Firefox “no yet officially release” and install the stable PPA Firefox?
No, I would not do that - if you use KDE neon (“not the KDE distribution” ) this Firefox is what they intend you to use.
So far nobody has reported any problems with it AFAIK (at least not in the Kubuntu Forums and their KDE neon section…).
But if you do want to use another Firefox (.deb) I would recommend you to install it like Debian suggests (meaning: from Mozilla.org).
Don’t forget to disable the Mozilla Team PPA and uninstall the Firefox and Thunderbird versions that came from there first!
Here is a script that could install it for you:
It is called “Kubuntu …”, but I have also used it in Debian, KDE neon (some time ago I have to admit…) and Lubuntu already.
Otherwise see: https://wiki.debian.org/Firefox#From_Mozilla_binaries