Activity for Ruggiero A
-
Ruggiero A posted a comment on ticket #233
From the shell script, no application seems to be stealing focus ./focus_logger2.sh 2024-08-12 14:55:15.015 - ./focus_logger2.sh 2024-08-12 14:55:20.013 - gnome-shell 2024-08-12 14:55:21.056 - Scid - <clipbase> (game 0 / 0) 2024-08-12 14:55:35.397 - ./focus_logger2.sh (I came back manually to the terminal about the last log line This could also explain why changing the NVIDIA driver resolves the issue; it's not necessarily the driver itself but the updated system libraries that accompany it. This...
-
There is a start like this [...] (1723412291061) <FocusIn> .fdockmain (1723412291062) <FocusOut> from .fdockmain to .main.board (1723412291062) <FocusOut> from . to .main.board (1723412291062) <FocusIn> .main (1723412291064) <FocusIn> .main.board) Then I start making some moves (1723412291430) <ButtonRelease> .main.board.bd (focus: .main) (1723412291430) <FocusOut> from .main.board to .main (1723412292454) <FocusOut> from .main to (1723412293582) <FocusIn> . (1723412293582) <FocusIn> .fdockmain (1723412293583)...
-
There is a start like this [...] (1723412291061) <FocusIn> .fdockmain (1723412291062) <FocusOut> from .fdockmain to .main.board (1723412291062) <FocusOut> from . to .main.board (1723412291062) <FocusIn> .main (1723412291064) <FocusIn> .main.board) Then I start making some moves (1723412291430) <ButtonRelease> .main.board.bd (focus: .main) (1723412291430) <FocusOut> from .main.board to .main (1723412292454) <FocusOut> from .main to (1723412293582) <FocusIn> . (1723412293582) <FocusIn> .fdockmain (1723412293583)...
-
There is a start like this [...] (1723412291061) <FocusIn> .fdockmain (1723412291062) <FocusOut> from .fdockmain to .main.board (1723412291062) <FocusOut> from . to .main.board (1723412291062) <FocusIn> .main (1723412291064) <FocusIn> .main.board) Then I start making some moves (1723412291430) <ButtonRelease> .main.board.bd (focus: .main) (1723412291430) <FocusOut> from .main.board to .main (1723412292454) <FocusOut> from .main to (1723412293582) <FocusIn> . (1723412293582) <FocusIn> .fdockmain (1723412293583)...
-
There is a start like this [...] (1723412291061) <FocusIn> .fdockmain (1723412291062) <FocusOut> from .fdockmain to .main.board (1723412291062) <FocusOut> from . to .main.board (1723412291062) <FocusIn> .main (1723412291064) <FocusIn> .main.board) Then I start making some moves (1723412291430) <ButtonRelease> .main.board.bd (focus: .main) (1723412291430) <FocusOut> from .main.board to .main (1723412292454) <FocusOut> from .main to (1723412293582) <FocusIn> . (1723412293582) <FocusIn> .fdockmain (1723412293583)...
-
In theory, the video driver should not affect the keyboard/mouse focus, so maybe it is related to multiple displays? So far the bug has happened both with only one display, on the laptop with Debian 12, and on my other PC with OSes different than Ubuntu. It does not seem related to multiple displays. Also I don't think it's just a focus problem. There are probably at least some errors happening in the background, since the application also is sensibly slower when the bug happens (still usable in...
-
In theory, the video driver should not affect the keyboard/mouse focus, so maybe it is related to multiple displays? So far the bug has happened both with only one display, on the laptop with Debian 12, and on my other PC with OSes different than Ubuntu. It does not seem related to multiple displays. Also I don't think it's just a focus problem. There are probably a lot of errors happening in the background, since the application also is sensibly slower when the bug happens (still usable in regards...
-
I may have made some advancements in reproducibility. I used this virtual machine image (Ubuntu 22.04 LTS) on my Fedora 40, with VirtualBox 7.0.20, and I manually installed VirtualBox Tools beforehand and restarted (I guess that the image straight for VBox can also work for the purpose, but to clarify what I did exactly use), and the problem still appears. I attach a screenshot where tcl/main.tcl was modified adding the lines in the post, just for log purposes, but the problem appears even in the...
-
I may have made some advancements in reproducibility. I used this virtual machine image (Ubuntu 22.04 LTS) on my Fedora 40, with VirtualBox 7.0.20, and I manually installed VirtualBox Tools beforehand and restarted (I guess that the image straight for VBox can also work for the purpose, but to clarify what I did exactly use), and the problem still appears. I attach a screenshot where tcl/main.tcl was modified adding the lines in the post, just for log purposes, but the problem appears even in the...
-
I may have made some advancements in reproducibility. I used this virtual machine image (Ubuntu 22.04 LTS) on my Fedora 40, with VirtualBox 7.0.20, and I manually installed VirtualBox Tools beforehand and restarted (I guess that the image straight for VBox can also work for the purpose, but to clarify what I did exactly use), and the problem still appears. I attach a screenshot where tcl/main.tcl was modified adding the lines in the post, just for log purposes, but the problem appears even in the...
-
I forgot to add that when the bug happens, the application will lose focus (FocusOut event on .main) basically as soon as a piece is pressed with the mouse. Also clicking on tabs applies. The events may not trigger at the very beginning of the launch of the application, but eventually they will start arising and they will happen basically after every click in the app. When .main is unfocused, no input from the keyboard will work untill focus is again forced, such as switching applications. The issue...
-
SCID focus bug on Linux | update + details
-
**Update: ** From the PC which I have a GTX 1060 (as opposed to the laptop with a RTX 4060 Laptop) and where SCID works on Ubuntu, SCID is almost completely unusable (keyboard input does not work to move in a file, you can't search games due to focus issues and here not even the alt-tab workaround helps) from another distro; I installed latest Kali Linux; nor nvidia driver versions 525.147.05 or 535.161.08 do work well with SCID. It is not easy to install another version, because the 535.161.08 is...
-
I suspected it was related to NVIDIA driver version after I installed SCID from flatpak, where I saw that it downloaded as dependency something related to my specific NVIDIA driver version at that time installed. Then I proceeded to install my previous (first and only) exact driver version where SCID used to work properly, and it again proceeded to work properly. I don't think I would have easily guessed it if not for flatpak, since I had nonetheless a working Nvidia driver even before the last ...
-
Ok, maybe the focus problem has definitively to do with Nvidia drivers. Still have to confirm it though. TL;DR: When SCID is buggy as I described it such as being often incapable to focus on text/other widgets or input from the keyboard, other subtle anomalies happen like menu flickering when hovered with cursor. When SCID isn't buggy, none of these anomalies happen, although the ones related to scaling may still happen. The problem seems to be indeed related to Nvidia drivers x86_64-545.29.06 is...
-
For clarity on the font size problem, I will also add a screenshot of the application full screen when scale is 200%
-
SCID 5.0.2 on Debian 12, focus on textfields not working as expected (again) plus font problems
-
The problem apparently disappeared after properly installing Nvidia drivers (which was not easy to do due to Secure Boot). I am not sure that's strictly the cause but it's the only thing I did. I also blacklisted Nouveau driver doing so.
-
SCID on Debian 12, focus on textfields not working as expected
1