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
gnome3.mutter: 3.36.4 -> 3.36.5 #95474
Conversation
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.
Changes look okay:
3.36.5
- Screencast fixes and improvements [Jonas; !1351, !1365]
- Fix glitches when subsurfaces extend outside the toplevel [Robert; #1316]
- Mipmap background texture rendering [Daniel; !1347]
- Fix wine copy & paste [Sebastian; !1369]
- Plugged memory leaks [Marco, Thomas; !1195]
Contributors:
Jonas Ådahl, Thomas Hindoe Paaboel Andersen, Sebastian Keller, Robert Mader,
Marco Trevisan (Treviño), Daniel van VugtTranslators:
Rafael Fontenelle [pt_BR]
@GrahamcOfBorg test gnome3 gnome3-xorg |
Test failed but it is not clear to me why. Trying again. @GrahamcOfBorg test gnome3 |
Maybe we need to update gnome-shell as well... there is a release ready for that package as well... I'll do a separate PR for that. |
The test succeeded now so merging. |
The test seems to be blocking unstable channel now, even though it passed here. https://hydra.nixos.org/build/125573530 I can also reproduce the failure locally using I tried bisecting mutter itself but it does not seem to make much sense:
|
Tried reverting it on master but it does not seem to fix it there 😕 |
I am now consistently getting the |
The test is probably just a bit flaky (IIRC that's been an issue a while). Tested on The failure on hydra indicates that the dbus session might not be up yet? We probably need a better way to wait for gnome-shell to be properly set up. Doing some digging now. |
Yep, that is entirely the problem. The only thing better would be to actually extend the testing driver. |
Tried a few things without real success:
The test have been passing on hydra now, but it's fairly annoying that it isn't consistent. We could perhaps just install an autostart file for gnome-terminal, that might be more robust? |
OK, autostart file looks promising, will make a PR. |
Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for gnome3.mutter is: "A window manager for GNOME"
meta.homepage for gnome3.mutter is: "https://gitlab.gnome.org/GNOME/mutter"
meta.changelog for gnome3.mutter is: ""
Updates performed
To inspect upstream changes
Impact
Checks done (click to expand)
built on NixOS
The tests defined in
passthru.tests
, if any, passed0 of 0 passed binary check by having a zero exit code.
0 of 0 passed binary check by having the new version present in output.
found 3.36.5 with grep in /nix/store/j7j4gaj1hll48w9np946in2x6vz8h3h8-mutter-3.36.5
directory tree listing: https://gist.github.com/a9e96576c1991121932d0dc1115eaa6b
du listing: https://gist.github.com/d051a41970ae4e382f0c222116d67fae
Rebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from Cachix:
(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the
trusted-users
list or you can usesudo
since root is effectively trusted.Or, build yourself:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of
nixpkgs-review
113 packages built:
Maintainer pings
cc @hedning @jtojnar @worldofpeace @dasj19 for testing.