suddenly couldn't open the Obsidian window by clicking the tray icon #48
Comments
|
Hm, unfortunately I can't replicate this with the latest version of Obsidian and the tray, it stills opens for me. I'm going to need more information to be able to fix this. What was your configuration? Does reinstalling the plugin cause the same thing to happen again? What happens if you press the hotkey to show/hide the window? |
|
Seeing the same issue - the tray plugin appears to be broken. The tray icon appears to be completely inactive - even right click options aren't showing. Running a fresh install of Fedora 40 KDE 6 and using the AppImage from the Obsidian site. |
|
Having a similar issue, Obsidian itself runs fine, the tray icon appears, and I had it set to launch on start, hide to tray etc. right-clicking the tray (for me) would show the fly-out menu, open a new vault relaunch etc, but none of them would DO anything. I'm on Arch Linux using Obsidian installed from the Extra repository. I do have plenty of other plugins, so I'm not sure if it might be some sort of conflict, but for me the problem only started within the last two-days. |
|
Same issue here on EndeavourOS (Arch based), Cinnamon Desktop, and the latest version of obsidian in arch extra repository. The tray icon appear as well as the tray menu is showing, but clicks on icon or menu items don't work. It happened just after the latest upgrade (see logs below of upgraded packages). With Tray extention disabled, Obsidian work properly. |
|
Friends, that's my question, and now I'm rolling back obsidian to version 1.5.12-1. Now the tray is back to normal use. I'm on an arch linux system and the command I use is: sudo pacman -U /var/cache/pacman/pkg/obsidian-1.5.12-1-x86_64.pkg.tar.zst Provided, of course, that there is no cleaned pacman cache. |
|
@dragonwocky I can confirm this issue. Maybe its make a different with wayland? I'm using wayland. |
|
No, I use X11 and I observe the same behavior. It is not related to the display server. |
A nice tool called yay -S downgrade
sudo downgrade obsidianAnd downgrading from Regarding the Arch packages updated, there is nothing related to DE (Cinnamon), WM (Muffin), GTK, Tray, etc that could explain the issue. |
Thanks ! |
|
Today, I updated obsidian to --> obsidian 1.6.3-2 Now tray plugin is fully functional again |
|
I can confirm it. Its resolved with 1.6.3-2 on arch and co. o.o .... weird |
|
I've had success with the AppImage, but the Flatpak version won't work for me in Fedora 40 with KDE. I'd much rather a working Flatpak. |
|
This plugin is based off Electron's Tray API, which should be handling support and specific implementations for each different distro/build of the app. The fact that this is a bug that pops up inconsistently depending on the version and build of Obsidian makes it seem like this is an issue related to changing dependencies or platform compatibilities, which are out of my control. I'll leave the issue open and take a closer look again when I've got time, but I'm not so sure this is something that can be fixed (at least not by this plugin). E.g. without digging too far into it yet, I'd guess that there'd be something related to the Flatpak's isolating techniques that is blocking the tray's registration of a global shortcut or something similar and thus breaking everything. |
|
I thought that with the Flatpak too @dragonwocky. I haven’t yet found the permission, but if I get it working I’ll post a result. Otherwise AppImage is working for now. For me anyway. |
|
@dragonwocky I've got it working with Flatpak. I enabled "Session Bus Access" in the Flatpak Permissions in KDE Settings. Needed checking even with the new v1.6.5, but so far so good, unless anything else changes, I'm set. Thanks for the work you do :) |
The Tray plugin has great features, but I don't know why today I suddenly couldn't open the Obsidian window by clicking the tray icon. Even after terminating the task in the task manager and restarting it, I still couldn't open it. I had to enter the folder and delete the plugin and its directory folder. I hope the bug can be fixed soon.
The text was updated successfully, but these errors were encountered: