You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Sometimes when tabbing on to RNote it starts eating all inputs. When this happens, everything else still updates (its not frozen), but attempting to interact with anything fails. I can still move my cursor (via mouse or tablet), but clicks, pen down, keyboard, etc all dont work. I have tried waiting (sometimes up to 30 minutes) and it never allows interaction again. The only fix is to restart the computer entirely.
To Reproduce
I really don't know... I wanted to wait until I could find a pattern to it, but its been months and I cant find a cause. It seems to only occur after tabbing back on to RNote, and if memory serves its only happned when tabbing on with the tablet (not keyboard or clicking the window). I wish I could be more helpful...
Expected behavior
It should continue to work as normal and not make the system inoperable.
Console Output
Run the app in the terminal with flatpak --env=RUST_LOG=rnote=debug --env=RUST_BACKTRACE=1 run com.github.flxzt.rnote
and post the output.
Unfortuntely due to the nature of the bug, I cant capture any output that includes the bug (to my knowlege). Either way, the only output I get when using it (and unsuccessfully attempting to trigger the bug) is:
Desktop (please complete the following information):
OS: Fedora 40
App Version: Rnote v0.11.0
Installation Source: Flatpak
Desktop Environment: GNOME 46.5
Display Server: Wayland
Input Source: Keyboard, Mouse, Wacom Inuos S tablet
Additional Context
I will continue to add to this as I learn more, and will try and capture the big in action. (Its elusive, it seems to only happen when I am not trying to capture it ... )
The text was updated successfully, but these errors were encountered:
In GNOME 46 in Fedora 40 whenever I tried to move an app (for example file manager or rnote) with my stylus, this used to happen. I could interact again by pressing esc key. Fortunately, in GNOME 47 in Fedora 41, this is no longer a problem. But, there is another problem in GNOME 47 for some tablets. See this.
In GNOME 46 in Fedora 40 whenever I tried to move an app (for example file manager or rnote) with my stylus, this used to happen. I could interact again by pressing esc key. Fortunately, in GNOME 47 in Fedora 41, this is no longer a problem. But, there is another problem in GNOME 47 for some tablets. See this.
Oh my gosh, thank you!! I couldve sworn I pressed every key when trying to fix it but pressing ESC actually fixes it (at least the few times its happned since ive seen this comment). Im going to keep this open for now incase it happens again, but if it keeps working for the next bunch of times I think the issue may have just been GNOME being weird. Thank you!
Still have yet to find a case that pressing ESC doesnt fix, and updated GNOME so I probably wont be replicating it again is the previous commenter was correct (which they seem to be). Still feels like an issue, but idk if its worth dev time to fix.
Describe the bug
Sometimes when tabbing on to RNote it starts eating all inputs. When this happens, everything else still updates (its not frozen), but attempting to interact with anything fails. I can still move my cursor (via mouse or tablet), but clicks, pen down, keyboard, etc all dont work. I have tried waiting (sometimes up to 30 minutes) and it never allows interaction again. The only fix is to restart the computer entirely.
To Reproduce
I really don't know... I wanted to wait until I could find a pattern to it, but its been months and I cant find a cause. It seems to only occur after tabbing back on to RNote, and if memory serves its only happned when tabbing on with the tablet (not keyboard or clicking the window). I wish I could be more helpful...
Expected behavior
It should continue to work as normal and not make the system inoperable.
Console Output
Run the app in the terminal with
flatpak --env=RUST_LOG=rnote=debug --env=RUST_BACKTRACE=1 run com.github.flxzt.rnote
and post the output.
Unfortuntely due to the nature of the bug, I cant capture any output that includes the bug (to my knowlege). Either way, the only output I get when using it (and unsuccessfully attempting to trigger the bug) is:
Screenshots
Desktop (please complete the following information):
Additional Context
I will continue to add to this as I learn more, and will try and capture the big in action. (Its elusive, it seems to only happen when I am not trying to capture it ... )
The text was updated successfully, but these errors were encountered: