Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Plasma Browser Extention Stopped working with this new update #953

Open
tr1xem opened this issue Feb 18, 2025 · 6 comments
Open

[BUG] Plasma Browser Extention Stopped working with this new update #953

tr1xem opened this issue Feb 18, 2025 · 6 comments

Comments

@tr1xem
Copy link

tr1xem commented Feb 18, 2025

System Details

  • OS: Cachyos Linux Kernel 6.13
  • Thorium Version : thorium-browser-bin 130.0.6723.174-1

Problem

The Plasma Browser Extention used to work fine with older version now its completely broken, Yes i tried with other browsers too and its working fine there

Did you read the FAQ?
https://thorium.rocks/faq

Additional Notes
Add any other context about the problem here.
Flags I use

--gpu-testing-vendor-id=0x8086
--gpu-testing-device-id=0xa78b
--enable-features=Thorium2024
--enable-features=VaapiVideoDecoder,VaapiIgnoreDriverChecks,Vulkan,DefaultANGLEVulkan,VulkanFromANGLE
--password-store=gnome-libsecret
--enable-features=TouchpadOverscrollHistoryNavigation
@SomeDudeNamedAnthony
Copy link

I'm having the same issue as well. Hopefully this gets fixed soon.

@SomeDudeNamedAnthony
Copy link

For the latest version, this issue can be fixed by either aliasing (using ln -s) /etc/thorium/native-messaging-hosts to /etc/(chromium|chrome)/native-messaging-hosts or simply by following the instructions shown at the bottom of the release log.

Notes:

  • The directory might be different on .AppImage, I haven't tested.
  • The directory might not exist yet, simply create it.

Note 2: If you have any extensions that use /etc/chromium/native-messaging-hosts or similar, you will need to copy them over to /etc/thorium/native-messaging-hosts. Technically, Thorium should have been using this the whole time, just like how Chrome uses /etc/opt/chrome/native-messaging-hosts and Brave uses /etc/brave/native-messaging-hosts. This was a bugfix, but means people who have gotten their extensions to work by just putting them in the Chromium native-messaging-hosts folder will now have to do it for Thorium too. But this is better overall, keeps things separate, and prevents issues.

@tr1xem
Copy link
Author

tr1xem commented Mar 1, 2025

The /etc/thorium/native-messaging-hosts Dont exists for me

@tr1xem
Copy link
Author

tr1xem commented Mar 1, 2025

Its the other wayaround
sudo ln -s /etc/chromium/native-messaging-hosts /etc/thorium/native-messaging-hosts

@SomeDudeNamedAnthony
Copy link

Interesting...
For me native messaging with Plasma Integration did work but 1Password did not.

@tr1xem
Copy link
Author

tr1xem commented Mar 1, 2025

for me buttercup worked as usual but only plasma broke

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants