view the rest of the comments
Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
The problem is that your desktop environment's shortcut handler intercepts Alt+V before KeePassXC ever sees it, so the internal keybinding never fires. And when pgrep finds the process running, your command simply does nothing.
The fix is to use KeePassXC's --auto-type CLI flag, which sends the auto-type signal to a running instance:
Command for your custom shortcut (Alt+V):
Not sure how keepass behaves though. Maybe you don't need the condition at all and can just run
keepassxc --auto-typefrom the shortcut and if there is no running instance it will start it.Wow, it works; you're a genius!!! Thanks so much!!! Hmm, Lemmy doesn't seem to have post flair, but it does allow title-editing, so I'll just update the post title, haha.
@HelloRoot@lemy.lol, it is actually failing after all. It only pulls up the auto-type window the first time. Then it only summons the main window from thereafter until it closes...
Yeah you probably have to play around with the flags to figure out the right approach. I can not look into it right now
I don't really understand how to figure out flags, so I just set it to start up on boot and just log in from the start and that basically fixes it.