- This topic has 2 replies, 2 voices, and was last updated Apr 18-10:01 am by Robin.
-
Posts
-
Robin
There is a nasty bug in Network-Assistant:
When clicking its help button, the Network Assistant window is corrupted after moving around the huge help screen.
This bug keeps the user from following the steps described in the help text in Network Assistant while reading on.
This is not a question of graphics card or graphics card drivers, and also not of antiX version used, nor kernel version.
The first shot above was taken from an antiX 21, upgraded to antiX 22, 32bit, on nvidia graphics card, while the shot below is taken from antiX 23, 64 bit, on asus/ati graphics.
Windows is like a submarine. Open a window and serious problems will start.
sybok
Hi, did/could you try the following:
A) Minimise the corrupted window and expand it again. Is it drawn correctly now?
B) Are other desktop environments (e.g. minimal alternative of the one you used when making screenshots) affected?
C) Can it be reproduced in a Live medium booted on the same HW?I have no idea what the cause could be but the above mentioned tests could help. In case of A), it could be a sensible work-around.
What is the installed version?I have tried it on my system (antiX-19.2_x64-full, upgraded to bullseye 5.10.142-antix.2-amd64-smp), DE: fluxbox, network-assistant version 2023.04.12, the main window gets messed up – overlaying/underlying windows “overwrite” the window content.
No need to move the help window (‘links’ in my system, not ‘dillo’), it suffices if it pops up on top of the main window.
A) Does not work, I must close the help window.
B) Fluxbox affected as well.
C) Did not try.Suggesting workarounds:
1) One could make a screenshot of the help, close the help window and use the screenshot
2) Open the local file in another browser, not the child window (probably means copying/rewriting the long name with path into the address bar)The problem is the presence of a child window.
This could mean that other programs using the same graphic libraries/tools and spawning child window(s) could be affected.Sorry, I really should have added these pieces of information you ask for already…
A) Minimise the corrupted window and expand it again. Is it drawn correctly now?
No, the window changes its content, keeping whatever is accidentally present in the position it is displayed.
B) Are other desktop environments (e.g. minimal alternative of the one you used when making screenshots) affected?
I should have mentioned: This happens on Rox-IceWM and zzzFM-IceWM, and also on pure IceWM and Minimal-IceWM. Same on JWM and Fluxbox in all variants.
C) Can it be reproduced in a Live medium booted on the same HW?
You are true. I actually should have mentioned. These are antiX USB live media, 1.) antiX 21 updated to 22, 2.) antiX 23 alpha, and 3.) anitX 23 beta. Issue shows up on three completely different type of hardware (Intel-Notebook 32bit dedicated Nvidia graphics card, AMD-CPU 64bit desktop Nvidia onboard GPU, Intel i3 Desktop 64bit dedicated Asus-ATI Graphics card )
This could mean that other programs using the same graphic libraries/tools and spawning child window(s) could be affected.
Definitely yes. Please see https://www.antixforum.com/forums/topic/window-of-app-select/ and my answer to verdy https://www.antixforum.com/forums/topic/window-of-app-select/#post-104722
The fix is pretty easy, you’ll just have to coproc the programs running in the child windows, then everything is perfectly fine. I have seen this issue in some of the scripts I worked on (aCSTV, antiXscreenshot2) already, and after some hours of try and error I had ready exactly this coproc workaround to be added within script code already to avoid this. So possibly this could work here also, just as it did in app-select’s config file.
Windows is like a submarine. Open a window and serious problems will start.
- You must be logged in to reply to this topic.
