-
-
Notifications
You must be signed in to change notification settings - Fork 326
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
[Bug] opening attribute table in empty mapset freezes GUI #3078
Comments
I would expect an error in the GUI console, could you check for it? |
I confirm this reported behavior: Error message is:
|
I get the same error |
This is partially addressed by #3086 in the sense that the db is initialized when the mapset is created in GUI, so this problem is unlikely to happen. |
Thanks. That should solve most cases. |
landam
pushed a commit
to landam/grass
that referenced
this issue
Oct 25, 2023
neteler
pushed a commit
to nilason/grass
that referenced
this issue
Nov 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
This is a weird bug but it could be a confusing problem for many. If you try to open the attribute table manager from an empty mapset, it freezes the GUI with a 'loading attribute table' message.
To Reproduce
Expected behavior
Instead of the table manager window, there is a 'loading attribute table' message displayed that never goes away.
System description (please complete the following information):
**Work Around
Copy a vector map to the empty mapset. Then everything works fine and the table manager opens. For some reason, not having the support folders/files for vectors in the current mapset is probably what is causing the freezing. But it shouldn't freeze like that.
If you then delete the vector you've copied into the empty mapset and try to open the attribute table from another mapset, it works fine. So it definitely has something to do with setting up the support for vectors. Either this needs to happen when mapsets are created or the table manager needs to ignore the lack of vector support when opening a table of a vector in a different mapset.
The text was updated successfully, but these errors were encountered: