-
Notifications
You must be signed in to change notification settings - Fork 104
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
Release 2.16.4 #3299
Release 2.16.4 #3299
Conversation
graphics/MultiplexingDisplay: Add HW cursor support.
eda00ca
to
a96f43c
Compare
@RAOF : I implemented a test in WLCS that works in |
You'll need this as well: You can see the build status in: |
Oh and don't worry about the conflict, the way to deal with this is to merge locally and push to |
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.
There are 14 commits, but only 5 fixes mentioned in the changelog, that seems wrong! Obviously the changelog and build related changes (like #3257) do not need mention, but omitting 10 of 14 commits seems wrong.
On closer examination there fixes included than are mentioned in the changelog, e.g.: #3261, #3238, #3240 & #3278.
I need to be convinced that #3237 and #3220 justify inclusion in a bugfix release: they are extensive and change (admittedly deprecated) APIs. Ideally, bugfix releases should only include things that can be tested in isolation and with confidence the rest of the system is stable.
I can part with #3237, but #3220 is dear to my heart as it fixes all of the problems that I'm having on Nvidia for miracle-wm. Without it, miracle-wm doesn't function out of the box on all of my systems. I understand the change is extensive, but it felt like a good time to test if that's working across different systems. |
Ignore zero length gamma curves
fixes #3236 Am I right to think this @RAOF ? It looks like `CPUCopyOutputSurface` is trying to have a `GL` layout. I could be wrong, but this makes my screenshots work. ## Before ![2024-02-21T17:01:19,606591722-05:00](https://github.com/canonical/mir/assets/25062299/1835506f-6725-47d4-920a-f2fdcec4ce91) ## After ![2024-02-21T17:06:29,424484886-05:00](https://github.com/canonical/mir/assets/25062299/6dfbc1e2-8fcf-40e2-8913-7a610b9a5743)
567be30
to
14c0550
Compare
WTF? |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3299 +/- ##
==========================================
- Coverage 77.51% 77.40% -0.11%
==========================================
Files 1066 1064 -2
Lines 75358 68072 -7286
==========================================
- Hits 58410 52694 -5716
+ Misses 16948 15378 -1570 ☔ View full report in Codecov by Sentry. |
I'm running Miriway [edit] The above happened when editing the [edit 1] This also happens with |
Testing ~rc13Note: DO NOT use the
|
…hat the final image is correct (#3292) fixes #3259 # Screenshots ## Left ![20240318_15h54m23s_grim](https://github.com/canonical/mir/assets/25062299/7815dfb9-ed03-491f-8422-e417d5d39d3b) ## Right ![20240318_15h54m44s_grim](https://github.com/canonical/mir/assets/25062299/412bd5a8-4935-4c4f-8c9a-6c710bf232b4) ## Inverted (Scaled) ![20240318_15h55m27s_grim](https://github.com/canonical/mir/assets/25062299/4bd4a102-c666-431f-86f8-ec005d3c457a) ## Normal ![20240318_15h56m07s_grim](https://github.com/canonical/mir/assets/25062299/f50be354-d664-4589-a75a-63e818d8597f)
…ot_respect_other_exclusive_zones WLCS test
We're *mostly* insulated from this, but our tests need to intercept calls to `open`, which means that we're exposed to some glibc internals that change under `_TIME_BITS=64`. Fortunately umockdev in the archive has already hit this, so adapt that fix to our use. Fixes: #3285
…ther_exclusive_zones WLCS tests needed to be excluded entirely as they spuriously fail
31782c0
to
994e25e
Compare
Testing ~rc13 (mark II)Note: Because I force-pushed after dropping a commit and editing the changelog we're still at
|
I've had to force a rebuild of Miriway/beta with ppa:mir-team/rc, but that's now up to date with this PR. (It works as expected) |
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.
@AlanGriffiths @mattkae #3300 is biting me on Pis, but I don't see any real problems, I'm +1 to tag v2.16.4
Screenshot items have been confirmed 🎉 |
Release Notes
mir (2.16.4) UNRELEASED; urgency=medium
grimshot save output
is using the exact opposite clip area on my machine #3236)(Fixes: Screenshots wrong when display rotated #3259)
(Fixes: Not respecting snap-name ubuntu-frame#172)