I don’t know which package you use. For linux we only support the packages we make under KDE or GNOME. Sorry.
The recent package (that we make) uses electron 39 which now defaults to wayland native as opposed to xwayland. I don’t know if that’s the source of change you are seeing.
I have a similar issue with focus and no content being inserted.
Arch Linux - KDE Plasma 6.5.5
Obsidian 1.11.4
Firefox 147.0.1 w/ obsidian web clipper from the firefox addons page
Clipping to an existing note no longer works. The Obsidian application is brought to the foreground but nothing is inserted. Inserting to a new note works.
I had to change this setting to make the focus work : from low to none. It fixed the app being brought to the foreground but didn’t help with the content issue.
Hey, just following up on this with some more info.
A couple of people over on the Arch GitLab helped me test this, and we’ve narrowed it down:
It’s a Wayland native issue: If I force Obsidian to run via XWayland by adding --ozone-platform=x11 to my config, the clipper starts working perfectly again—the window focuses correctly and the full page content is sent.
KDE Plasma specific? Another user was able to reproduce the bug on Plasma, but interestingly, they mentioned it seemed to work fine on GNOME.
The Regression: Since Obsidian 1.11.4+ (Electron 39) now defaults to Wayland native, this is why it suddenly broke for us.
It looks like there’s a specific bug in how the app handles the obsidian:// URI payload and window activation when running natively on Wayland under Plasma.
Is there any specific log or debug info I can provide from a Wayland session to help you guys look into the focus/URI handling for Linux?
We do not have code that is X11 or Wayland specific (nor KDE or Gnome Specific for that matter).
I have the feeling that you are running into this:
I don’t know if there is some special config in KDE to make it work for wayland (like it there is for Sway). This should be asked in some KDE-centric forum.