this post was submitted on 23 Nov 2023
6 points (100.0% liked)

KDE & Plasma users

2786 readers
2 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE's software runs on GNU/Linux, BSD and other operating systems, including Windows.

founded 4 years ago
MODERATORS
 

Thank you in advance :)

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 2 points 11 months ago* (last edited 11 months ago) (1 children)

The way I have it, is that I copied org.kde.plasma.browser_integration.json from /usr/lib/mozilla/native-messaging-hosts/org.kde.plasma.browser_integration.json (for Kubuntu 22.04, might be elsewhere for you) to ~/.var/app/org.mozilla.firefox/.mozilla/native-messaging-hosts and then changed the path to a shell script that calls the original executable with flatpak-spawn --host. Of course this kind of breaks sandboxing since you are allowing the browser to access programs on your machine but it works.

So I have: org.kde.plasma.browser_integration.json :

{
  "name": "org.kde.plasma.browser_integration",
  "description": "Native connector for KDE Plasma",
  "path": "/home/username/.var/app/org.mozilla.firefox/.mozilla/native-messaging-hosts/org.kde.plasma.browser_integration.sh",
  "type": "stdio",
  "allowed_extensions": ["[email protected]"]
}

and org.kde.plasma.browser_integration.sh

#!/bin/bash
flatpak-spawn --host /usr/bin/plasma-browser-integration-host "$@"

Don't forget to chmod +x the shell script.

I have the same for the KeePassXC extension.

[โ€“] [email protected] 1 points 11 months ago

Oh, alright. I might give that a try. Thanks mate :D