-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI freezes while palette cycling continues #261
Comments
Thanks for reporting! Is the issue present with the latest sources (4.3.3 at the moment) too? |
Yes, this issue is present with 4.3.3 built from source. It is also present with 4.3.0 built from source just now. I would like to update one observation— if this happens when I run XaoS from a terminal window, I can Ctrl-C in that terminal window to exit XaoS as expected. If I run Xaos from the desktop menu system, then I have to open a terminal to find the process and kill it manually. |
Sorry, I cannot reproduce this. Please, can you create a video recording to show what you exactly experience? |
Hi, sorry for the late reply. I reinstalled the latest version and made a video. I demonstrate the following actions:
All of these work as expected. When I go to File -> Open, nothing happens, and the window itself becomes unresponsive, including the menu bar and the Close (X) button. The application still cycles colors. There are no errors in the terminal window from which I ran XaoS, and Ctrl-C from the terminal closes XaoS. I am using Linux Mint 22.1 which is mostly the Ubuntu 24 system libraries. I have a more current version of libpoco, if that matters. If I understand correctly (as I'm still somewhat new to Linux) the desktop is Cinnamon, which I believe is GTK+3. Linux Mint also has editions with Xfce and MATE. I would be glad to try those and be more prompt with the results if you still aren't able to reproduce this. Since the palette cycling continues, I'm wondering if the problem is ultimately not with XaoS but elsewhere. However, I use a few Qt6 applications and have never encountered this before. On an older, slower machine with the same OS, the pointer briefly displays as the "busy" pinwheel after choosing File -> Open, then becoming unresponsive. I hope this helps. Thanks! video5573388863.mp4 |
Thanks for your very detailed and helpful explanation. I tried to reproduce it on Ubuntu 24.04, for the first time I had some issues when trying to open the file, but after I updated my system (to have the newest version of each package), I cannot reproduce it any longer. |
Correct, I cannot reproduce this issue with the WebAssembly version. It turns out I do have several pending system updates, but in the meantime here's the info on the current Qt package:
|
Updating my system packages didn't resolve the behavior with version 4.3. The WebAssembly app at xaos.app and the previous version 4.2.1 still work as before. I tried building XaoS on several different Debian Live Builds with different desktop environments to see what happens. Even though that might not represent the most current software updates, the results might be useful. When using File -> Open: Debian/Cinnamon
Devian/GNOME
Debian/KDE
Debian/Mate
Debian/Xfce
If I knew anything about Qt I might be able to devise some other tests. However, if this indicates a missing Qt package in the desktop environment, let me know and I'll be glad to try installing it. |
Thank you, this is extremely useful. I will try to find time to have the problematic systems installed (currently I use Ubuntu/KDE which just works). |
Hi. I have trouble with the UI freezing when some commands would presumably open a dialogue window. While the UI is frozen, fractal rendering actions such as color cycling and autopilot will continue.
I see no indication that a window has opened in the background. The only recourse is to
ps && kill
the XaoS process from a terminal.I have observed this with:
I am on an AMD desktop using Linux Mint 22 / Ubuntu 24. This happens from both the packaged edition and when I build from source.
This did not happen with version 4.2 when I was using the system package. This doesn't happen when I build from the 4.2.1 source right now.
Let me know if there is a way to generate a logfile that might help. Thanks!
The text was updated successfully, but these errors were encountered: