Suggestion: Add plasma-browser-integration package in Aurora

KDE 6.4 now supports Plasma browser integration for Flatpak versions of Firefox and Chromium.
Hereโ€™s the link to KDE 6.4 Complete Changelog you can find it in Plasma Browser Integration section.

I think that plasma-browser-integration package could be pre-installed on Aurora in order to get this feature work :slight_smile:

It is included, but it doesnโ€™t work by default!

~> which plasma-browser-integration-host 
โ•ญโ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ
โ”‚ # โ”‚             command             โ”‚                   path                   โ”‚   type   โ”‚
โ”œโ”€โ”€โ”€โ”ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ค
โ”‚ 0 โ”‚ plasma-browser-integration-host โ”‚ /usr/bin/plasma-browser-integration-host โ”‚ external โ”‚
โ•ฐโ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ
~> rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: inactive
Deployments:
โ— ostree-unverified-registry:ghcr.io/santiagocezar/aurora-dx-nixed
                   Digest: sha256:4d6dfa537ade564b13447665454de267a861200cd3b7255b87da1abfc1e626ac
                  Version: latest-42.20250623 (2025-06-23T03:37:06Z)

  ostree-unverified-registry:ghcr.io/santiagocezar/aurora-dx-nixed
                   Digest: sha256:47fe4902d2a0e0613a9e8dbdb19edae0badccca420e0895b33543365da6cf26d
                  Version: latest-42.20250619 (2025-06-19T02:14:38Z)
~>                                                                                                                                                                                                                         26/06/25 17:24:09

I looked into it and asked around, and hereโ€™s what I found:

  1. The flatpak-integrator service used by plasma-browser-integrator โ€œdoesnโ€™t likeโ€ symlinks. By default, $HOME points to the symlinked homedir at /home/user, which breaks the function that creates the files required for the integration to work. Details here, though Iโ€™m not sure if it should/will get fixed sinceโ€ฆ
  2. $HOME shouldnโ€™t really be pointing to the symlink. According to Chris (from the ublue discord), this is an upstream Kinoite bug, already reported here.

Ultimately, what I just did is redefine the userโ€™s homedir with usermod, which seems to have fixed it. This wonโ€™t work unless youโ€™re logged out, so log from a tty with the root account (if you have one) or make another user that is allowed to sudo:

sudo usermod youruser --home /var/home/youruser
3 Likes

Thank you so much for the helpโ€”it works for me on Flatpak Firefox and Chromium.
Iโ€™m wondering how to make it work for Zen Browser too. :thinking:

1 Like

Itโ€™s not supported yet, but it seems trivial to add support for it:

// List of Flatpak browsers we support.
const QList<BrowserInfo> supportedBrowsers = {
    {BrowserBase::Firefox, u"org.mozilla.firefox"_s, u"/.mozilla/native-messaging-hosts"_s},
    {BrowserBase::Firefox, u"io.gitlab.librewolf-community"_s, u"/.librewolf/native-messaging-hosts"_s},
    {BrowserBase::Chrome, u"com.google.Chrome"_s, u"/config/google-chrome/NativeMessagingHosts"_s},
    {BrowserBase::Chrome, u"com.google.ChromeDev"_s, u"/config/google-chrome-unstable/NativeMessagingHosts"_s},
    {BrowserBase::Chromium, u"org.chromium.Chromium"_s, u"/config/chromium/NativeMessagingHosts"_s},
    {BrowserBase::Chromium, u"io.github.ungoogled_software.ungoogled_chromium"_s, u"/config/chromium/NativeMessagingHosts"_s},
};

flatpak-integrator/plugin.cpp ยท master ยท Plasma / Plasma Browser Integration ยท GitLab

You can probably copy the files manually as a workaround

1 Like

Thank you so much
I copy the plasma-browser-integration-host file from librewolf folder to /var/home/rain/.var/app/app.zen_browser.zen folder and copy native-messaging-hosts folder to /var/home/rain/.var/app/app.zen_browser.zen/.zen.

Then I edit the org.kde.plasma.browser_integration.json file โ€œpathโ€ to where zen browser is "/var/home/rain/.var/app/app.zen_browser.zen/plasma-browser-integration-host",.

But no luck, extension in zen still canโ€™t connect to the host, is there any steps I missed?

Ah, there was this too:

It seems to do it automatically for all the supported browsers, but of course for Zen it does not.

Try running flatpak override --user --talk-name=org.kde.plasma.browser.integration app.zen_browser.zen