Minimize/Maximize/Close buttons suddenly non-interactable (Bazzite)
No known changes made, was working fine until it wasn't.
Solution:Jump to solution
I don't bother with this kind of thing because god knows how far up the chain these are - it could be in Tauri, or Wry, or Tao, or Winit, or Rust bindings to Gtk, or Gtk, or KDE
23 Replies
Flatpak, KDE Plasma 6
For me on arch with kde plasma the buttons were never interact able in windowed mode.
In full screen they work.
@fightforlife @Goodums X11 or Wayland?
I use wayland
I just retested this with the new version.
On first start the app starts in windowed mode. Here the buttons to not work.
When I maximize the window by double clicking, the buttons start working.
When I return to window mode the buttons still work.
So to fix it I have to maximaze once after start.
wayland
a few things i've tried: deleted profile, it had corrected it the first time. restoring the profile disabled the buttons again. I tried to replicate this and since then deleting the profile doesn't help anything.
I've also tried removing the flatpak and all associated folders then reinstall which still left me with non-interactable top buttons.
Ok so ironically the double clicking to maximize works for me, after restoring the window it continues to work. However closing and re-opening it returns to non-interactable unless I do the maximize trick again.
Yeah I actually have this bug too
It only happens when the title bar is thicker than the normal thinner one
Solution
I don't bother with this kind of thing because god knows how far up the chain these are - it could be in Tauri, or Wry, or Tao, or Winit, or Rust bindings to Gtk, or Gtk, or KDE
Anyway no matter where it is I'm powerless to fix it
(This is why (plus memory usage) I want to rid OpenDeck of Tauri and find a nice native toolkit, but Elgato made the awful decision to need webviews)
Gotcha, it's really a non-issue but wasn't sure if it meant I had broken something. Glad it's just "normal" lol thanks!
Same on Debian KDE Plasma
Going to mark this as solved, neke knows. Some kind of scaling issue, workarounds listed above.
sweet thanks
@everyone I pushed a small fix so that the window can be hidden one time before the bug starts - but, starting OpenDeck hidden on launch still counts as hiding the window, so don't expect any real change.
If you start OpenDeck not hidden / visible, then now you can close (hide) it one time, but the second time the bug will happen again
@Cryptic as well
if someone really wants you can file a bug with tauri and they might point you to kde instead but i don't have the time or energy
@RazorFox I think this is the issue: https://github.com/tauri-apps/tauri/issues/11856
GitHub
[bug][linux] Decorations are unresponsive if WebviewWindow is built...
Describe the bug Reproduced on Gnome on both Fedora and Ubuntu (fresh installs). I don't know about other DEs. Windows/macOS work well. When manually building a WebviewWindow via its Builder, a...
Thanks. Seems like a lot of downstream issues are coming in, but I'm not sure if there is already a plan for a fix...
not that I am aware of.
Yeah, that's kind of unfortunate. I don't want to be the guy posting "any news on this", but is there something maybe you can do to push this in the right direction?
I am not aware of a way with more leverage then "any news on this" I/we would have.
You can give a thumbs up and subscribe to the issue tho
You are the devs of a project using their library, and this bug currently prevents users from interacting with the window buttons. I'd say this is a pretty serious bug and they should try to fix it. But when I read that they "currently have very limited time for Linux-specific stuff" (https://github.com/tauri-apps/tao/issues/1046#issuecomment-3209788993) this makes me not very confident this will get fixed anytime soon. (I don't even know if the issue I just linked is the reason for the non-responsive window buttons.)
Apart from I am currently not beeing a dev of OpenDeck I don't think OpenDeck is big enough to really make a difference if you look at the issue. Also Nekename already posted to this.
Yeah I know, you are probably right. I'm used to projects treating Linux as if nobody uses it, so we'll have to live with it I guess.
Unfortunatly yes.