-
Notifications
You must be signed in to change notification settings - Fork 159
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
GNOME 3.30 + GNOME 3.32 compatibility patch #1591
GNOME 3.30 + GNOME 3.32 compatibility patch #1591
Conversation
This drops support for the old mutter versions. It's too much work to support them all.
With the current master branch, we also need to port this work e10d621 |
@fossfreedom about the animations problem in popovers it couldn't be related to the popover code? |
I don't think so - you see the remnants of the notification window and the alt+tab window. Which make me think it is due to the bespoke animation code budgie uses. |
oh, ok, I'll see wm code, to check if I can find something |
indeed - that was an area I was fiddling with before I ran out of time on UB 18.10.
It does look promising though from a first initial look.
On Thu, 13 Dec 2018 at 11:40, Daniel Pinto <notifications@github.com<mailto:notifications@github.com>> wrote:
https://github.com/solus-project/budgie-desktop/blob/master/src/wm/wm.vala#L1039 It should be related to that function no?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#1591 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AA8zkLHB9ZnH2mVM7aE4JceVPXG8K25_ks5u4jyXgaJpZM4XMmOD>.
|
do you have any place we can talk easier? telegram, hangouts... |
IRC freenode #budgie-desktop-dev
…On Thu, 13 Dec 2018 at 11:54, Daniel Pinto ***@***.***> wrote:
do you have any place we can talk easier? telegram, hangouts...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Thanks, I'm running on this branch. Works great so far! |
Well,, @fossfreedom i can do a shot into Manjaro? |
@fossfreedom i started the building so i can testing also in our community 😉 |
--> @fossfreedom @Ste74 It runs mostly fine, but I have experienced a few more crashes compared to b2d7a8b which I was running before. These aren't annoying unless you get logged out after a few crashes. For example, Budge Panel crashes when starting Budgie Settings. This may be because of wonky or old settings though. Haven't looked into the reason for that, but at least make sure you test messing about with Budgie Settings, @Ste74! Same thing goes with dragging and dropping things to Budgie Panel, and switching workspaces when Guake is open and set to |
ok - the budgie-settings thing is a merge issue. Easy enough to fix. Will do that friday.
On Wed, 26 Dec 2018 at 23:28, Joakim Soderlund <notifications@github.com<mailto:notifications@github.com>> wrote:
…--> @fossfreedom<https://github.com/fossfreedom> @Ste74<https://github.com/Ste74>
It runs mostly fine, but I have experienced a few more crashes compared to b2d7a8b<b2d7a8b> which I was running before. These aren't annoying unless you get logged out after a few crashes.
For example, Budge Panel crashes when starting Budgie Settings. This may be because of wonky or old settings though. Haven't looked into the reason for that, but at least make sure you test messing about with Budgie Settings, @Ste74<https://github.com/Ste74>!
Same thing goes with dragging and dropping things to Budgie Panel, and switching workspaces when Guake<https://github.com/Guake/guake/> is open and set to hide on lose focus. Again though, I haven't looked into the reasons for this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#1591 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AA8zkA5ItAecwrvfJDipSmZUNZbRpN7Jks5u9AYLgaJpZM4XMmOD>.
|
Yea, I'm referring to the override file. I just wanted to know if it was a requirement or not, I didn't see anything about the suffix / vendor bit being required in the GLib changelogs is all, hence the inquiry.
The equivalent keys should be kept in sync. Most of src/daemon/settings.wm does that when we change the respective Budgie keys, like
My biggest issue with the original patch from Iain was it did away with all backwards compatibility for the prior stack (so the proposal was 3.30, with no support for 3.28). This patch satisfies backwards compatibility by supporting both 3.30 and 3.32. I would've used a mix of Structs since Vala has no form of typedef or type aliases, as well as implementing a class to handle getting the monitor and screen, with |
@fossfreedom can you merge again with my branch, so that you can get the auto-generated vapis? |
Marco,
haven't had alot of time to spend on this. I had a quick look over the weekend at trying to retrofit the new bits to retain both Mutter 3.30 and Mutter 3.32 compilation ability but rather failed miserably. I know enough about meson to be dangerous - but your new bits are a little over my head.
Solus Project would like to retain a cross version compilation ability and intend (a little later) to retrofit the ability also to compile against Mutter 3.28. For the moment I have merged your changes into a separate 3.32 only branch
- https://github.com/UbuntuBudgie/budgie-desktop/tree/mutter332
On Wed, 6 Mar 2019 at 11:07, Marco Trevisan <notifications@github.com<mailto:notifications@github.com>> wrote:
@fossfreedom<https://github.com/fossfreedom> can you merge again with my branch, so that you can get the auto-generated vapis?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#1591 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AA8zkBstaRu9y_Koj7KM-4BOF2uN1CWHks5vT6FvgaJpZM4XMmOD>.
|
@fossfreedom so... I've pushed to my branch a version that generates Vapi for both libmutter-3 and libmutter-4, it works fine and I've added a custom vapi file to avoid source changes or This is not supporting libmutter-2 at the moment, but I think you can add that with few lines more in the same way is done for 3 and 4. So please, give it a look, because right now budgie is completely wrong in using the system cogl and clutter VAPIs which have already diverged from mutter forks, while it's better if it generates the VAPIs at build time using the proper gir files with some customizations if needed, instead of shipping big vapi files. PS: what is done here should actually be applied to the other VAPIs that are inside budgie, but not something I'll touch for now. |
I use the VAPIs as a reference point sometimes in development. I'd much rather we ship them than generate at build time. |
well, a part that if you develop, I guess you're also building and in such case are in the build directory, but if you really want the built vapi can be instead wrote in the source directory, and then when something new is generated or has changed, you can commit it and push straight forward without having to care to stay in sync manually. So, this method isn't really touching this, in general though I think the vapi generation should automatized by meson, instead of having to deal with those bits at every mutter abi change. |
All - just a heads up. Keyboard shortcuts like CTRL + ALT + T and all custom keyboard shortcuts are broken with the new (almost) stable mutter/gnome-settings-daemon 3.32 No idea what is going on - will need investigation. Seems to be ok with vanilla GNOME-Shell so I'm guessing something in the budgie shim will need reworking. EDIT: Saw this in journalctl
|
The signature for the registration method has changed, so needs to be updated. |
These changes landed in 3.31.9x cycle: Mutter: https://gitlab.gnome.org/GNOME/mutter/commit/00ca387ec7f6a864a35e0baee8c69cc71d60641e Gnome-Shell: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/156/diffs And G-S-D might also have similar changes for following the Mutter 3.31.9x change... Regards. |
Thx. Solved. Just now need to tidy up the changes made. Will push when done.
On Fri, 8 Mar 2019, 08:13 Tista, <notifications@github.com<mailto:notifications@github.com>> wrote:
@fossfreedom<https://github.com/fossfreedom>,
These changes landed in 3.31.9x cycle:
Mutter: https://gitlab.gnome.org/GNOME/mutter/commit/00ca387ec7f6a864a35e0baee8c69cc71d60641e
Gnome-Shell: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/156/diffs
And G-S-D might also have similar changes for following the Mutter 3.31.9x change...
Regards.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#1591 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AA8zkF9PZ_Vd8cj7ClgVscRlxDdjbb67ks5vUhuggaJpZM4XMmOD>.
|
Runs well for me on GNOME 3.32! Thanks again! |
@@ -285,8 +285,7 @@ public class SettingsManager { | |||
} | |||
|
|||
this.xoverrides.set_value("overrides", xset); | |||
this.wm_settings.set_string("button-layout", wm_set); |
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.
Let's preserve the setting of our key as per our earlier conversation in this PR.
budgie_wm_settings = new GLib.Settings("com.solus-project.budgie-wm"); | ||
budgie_wm_settings.bind("attach-modal-dialogs", switch_dialogs, "active", SettingsBindFlags.DEFAULT); |
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.
Should maintain use of budgie_wm_settings instead of using gnome_wm_settings for attach-modal-dialogs and edge-tiling. We can just additionally change the gnome_wm_settings value in our switch_dialogs and switch_settings functions.
budgie_wm_settings.bind("button-style", combo_layouts, "active-id", SettingsBindFlags.DEFAULT); | ||
budgie_wm_settings.bind("center-windows", center_windows, "active", SettingsBindFlags.DEFAULT); | ||
budgie_wm_settings.bind("disable-night-light-on-fullscreen", disable_night_light, "active", SettingsBindFlags.DEFAULT); | ||
budgie_wm_settings.bind("edge-tiling", switch_tiling, "active", SettingsBindFlags.DEFAULT); |
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.
Should maintain use of budgie_wm_settings instead of using gnome_wm_settings for attach-modal-dialogs and edge-tiling. We can just additionally change the gnome_wm_settings value in our switch_dialogs and switch_settings functions.
@fossfreedom Thanks for your hard work! I've successfully compiled and using your branch on brand new Fedora 29. |
There's still changes here I'd like to see addressed. Any chance you could take a look at your patch / branch @fossfreedom? |
Josh, Sorry for the late reply ... for the last few weeks have been snowed
under with 19.04 release stuff. Hope that stuff will die down soon.
…On Mon, 22 Apr 2019, 15:31 Joshua Strobl, ***@***.***> wrote:
There's still changes here I'd like to see addressed. Any chance you could
take a look at your patch / branch @fossfreedom
<https://github.com/fossfreedom>?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1591 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAHTHED4PPAJ4XXVT3H5XD3PRXD5LANCNFSM4FZSMOBQ>
.
|
It's alright, completely understandable that you folks would be busy. Congratulations on the new release! I've just updated the GNOME Stack on Solus locally to GNOME 3.32 and wanting to start landing the patches and validate now that I have the stack to do so. If the patch isn't sorted by tomorrow, it's not a problem, I can land it and fix it post-merge. |
This PR describes the GNOME 3.30 patch set Ubuntu 18.10 will be using for its release on the 18th Oct and is part of Debian Buster at the moment
Yes - I am aware this is not backwards compatible with 3.28 - so feel free to ignore/cherry-pick/use as a reference point etc etc.
I'll outline the decision points I made to enable budgie-desktop to work against mutter 3.30 and underlying stuff like Vala that has been incorporated in UB and Debian Buster. Hopefully this may be useful.
The TL;DR; I believe this patch set resolves all except one issue described later.
The one remaining issue I have not been able to resolve is Window border shading being left on the screen when the menu / Alt+Tab / notification popups are hidden. For the interim I have gsettings overridden the WM animations schema key to turn off budgie animations via the budgie-desktop debian package. I suspect UB and Debian end-users will raise issues here if they subsequently turn animations on in budgie-settings ... or have previously fiddled with that setting in the past and have now upgraded. Obviously if/when someone resolves this I will immediately backport this fix to 18.10 UB and Debian Buster.