Skip to content
This repository has been archived by the owner on Oct 31, 2024. It is now read-only.

Conflict with KDE Autostart #84

Closed
backd00rbenny opened this issue Feb 25, 2024 · 0 comments
Closed

Conflict with KDE Autostart #84

backd00rbenny opened this issue Feb 25, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@backd00rbenny
Copy link

I've setup a rule in KDE preferences to Autostart Obsidian on boot. When I use the Clipper for the first time, it's not reconising the open session, and opening a new session like it was the first time the vault has ever been accessed. Obsidian is then popping this error:
Screenshot_20240225_150527

This leaves me with 2 concurrent sessions of Obsidian running.

If I don't autostart and open Obsidian manually, Clipper works perfectly. If I don't open Obsidian at all and use Clipper, it starts Obsidian and works perfectly. The problem seems to only exist with Autostart at boot.

I want to autostart Obsidian so I don't have to remember to open it, which then encourages me to use it. I don't need 2 sessions running ever. Having to restart Obsidian just to use Clipper is a bit annoying, but when it's working it's awesome! Thanks for sharing your work.

  • EndeavourOS, KDE 5.27.10, Kernel 6.7.6, Wayland
  • Firefox 123.0
  • Clipper Version 0.3.6
@backd00rbenny backd00rbenny added the bug Something isn't working label Feb 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants