-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
Fix mutter 3.3x crashes #635
Conversation
…ng to get non-existing workspaces
…instead of keeping at least the last workspace
…t algorithm to remove destroyed workspaces
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By creating an unowned List
you're creating a leak here
For each one of the suggestions, we fill the list using Just to be sure there is no mistake. Edit:Ok I just tested it, it seems to work without I just noticed I should have accepted the changes directly from github instead of pushing a new commit however. |
@Tireg a new commit is fine too, no worries :) |
I'm looking forward to testing this on fedora :) Just one question / nit-pick: The name for the gsettings override file seems rather odd:
Can we rename it to something like |
@decathorpe Yeah, would make sense too :) |
Hm. I'm still getting a reproducible crash on startup on fedora 31 :( I'll try to file a new bug report for it, once I'm able to provide a useful traceback :( |
This PR fixes issues against running upstream gala with mutter 3.3x.
This should fix #634
Every single patch is detailed in this post: #634 (comment)
I reported every step as a commit comment in order to understand it more easily.