-
Notifications
You must be signed in to change notification settings - Fork 47
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
Two issues encountered testing Coot 1.1.10 (homebrew) #146
Comments
I get a hard lock on Sonoma 14.5 when opening the Ramachandran plot window. Need to kill Coot. 1.1.10. Only output is below:
|
That looks like it might be related. |
This was mentioned on the mailing list I think. I have removed much old python toolbar code. We are looking at an old config and a new executable. Hopefully just removing line 17 from your |
Hi Paul, I commented out these lines (17 plus the other ones referencing the modeling tool bar). This gets rid of the startup error pertaining specifically to the modeling toolbar, but all the Rama plot glitches persist. Cheers |
Happened using the tutorial data, sorry, should have specified. |
Eeek! Poor Coot! I don't treat Coot like that! Some of that might be GTK4 on macOS. Some is my doing. OK, I'll see if I can reproduce it. |
In my hands there is not much required to reproduce - just open coot, load tutorial data, launch rama plot, close it, then try resizing the window - everything glitches and eventually the screen goes black |
OK, I can more or less reproduce this. |
Hi Paul,
Just listing two (possibly unrelated) issues encountered using the latest homebrew build (1.1.10, brewsci-bio-coot) with the tutorial model and data:
Basically, the Rama plot loads ok, and residues are clickable (yay!). It does affect window resizing (making vertical resizing of the main window impossible), but otherwise it works. However, if I then try to close the rama plot (~0:44 in the screen recording), everything goes bananas - it initially closes, but then randomly reappears, the main window eventually becomes unresponsive and window resizing then causes a black screen. This is on a 14 inch Macbook pro, apple silicon M2-Max, Sonoma 14.5. After killing the unresponsive app, here are a selection of the messages in the log:
The text was updated successfully, but these errors were encountered: