** Changed in: mutter (Ubuntu Bionic)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to
** Changed in: mutter (Ubuntu Bionic)
Assignee: Daniel van Vugt (vanvugt) => Tyler Alexander Driggers (exderia)
** Changed in: mutter (Ubuntu Bionic)
Assignee: Tyler Alexander Driggers (exderia) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package mutter - 3.28.4-0ubuntu18.04.1
---
mutter (3.28.4-0ubuntu18.04.1) bionic; urgency=medium
* New upstream release:
- Implement keycode remap to keysyms on virtual key devices (LP: #1827029)
*
Fix verified on bionic (both Xorg and Wayland sessions) using mutter
version 3.28.4-0ubuntu18.04.1
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
The test case passes, and gnome-shell reaches 120Hz for me. But it's not
as smooth and reliable as I would like in Xorg sessions. I think
https://gitlab.gnome.org/GNOME/mutter/merge_requests/520 will fix that
in the coming months.
But don't be confused, this bug is now definitely fixed in bionic
Hello Knut, or anyone else affected,
Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.4-0ubuntu18.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: mutter (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap rendering
** Merge proposal linked:
https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/366676
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but
Thank you Daniel. The new bug is
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820832
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems
Argh, sorry again. Bug 1730460 and one of the above links are about
Wayland sessions only. Please open a new bug for Xorg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz
Argh, sorry again. Bug 1730460 and the above links are about Wayland
sessions only. Please open a new bug for Xorg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor
Sorry, this is an issue I should have foreseen and warned people about.
This bug is not about multiple monitors, it is about the single monitor
case only.
I know multi-monitor systems have an additional problem which is best
captured upstream in:
Hello again. Well this is promising news. Because I am also using xorg
with multiple monitors. And observing the same exact issue. Taking that
discussion over to the other bug then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm using Xorg with an AMD Vega 64. Both displays are connected to the
GPU. My main 144hz display is connected via Display Port, and my second
60hz display is connected via HDMI.
I'm using Mesa 19.1.0-devel - padoka PPA
When I perform the test case in the first post, I get high framerates
when
I forgot to mention that multi-monitors still won't work properly in
Wayland sessions. You'll only get the speed of the slowest monitor. But
a fix for that is coming eventually:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/73
If you experience the problem in Xorg then that's a new
> I'm on 18.10 with dual monitors, and I'm still capped at 60hz on my
144hz display. However, if I disable my second display (it only supports
60hz), I my main gets 144hz as expected.
Is that with both dislays attached to an nvidia graphics card ? If so,
then what version of the nvidia driver,
I'm on 18.10 with dual monitors, and I'm still capped at 60hz on my
144hz display. However, if I disable my second display (it only
supports 60hz), I my main gets 144hz as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi. On 18.10 with proposed enabled the screen now renders at > 60 Hz and
feels smooth (: This fixes the issue for me. Thank you for you hard
work guys.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: mutter (Ubuntu Disco)
Importance: Medium
Assignee: Daniel van Vugt (vanvugt)
Status: Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
Still a massive upgrade for me. Ive been working in Windows for the last 10
years with FPS/Hz ranging from 100-240. Loving ubuntu, but it feels so
choppy right now.
Cheers Daniel.
ons. 13. mar. 2019 kl. 09:50 skrev Daniel van Vugt <
daniel.van.v...@canonical.com>:
> A few caveats to remember
A few caveats to remember though:
* In Wayland sessions, if the screen is idle then the mouse cursor will
slow to 60Hz (https://gitlab.gnome.org/GNOME/mutter/issues/406)
* Removing the 60Hz limit doesn't mean everything will happen at full
frame rate. There are many reasons why
Excited! Cant wait.
ons. 13. mar. 2019 kl. 09:15 skrev Daniel van Vugt <
daniel.van.v...@canonical.com>:
> Bionic fix on the way:
>
> https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/364362
>
> ** Merge proposal linked:
>
>
Bionic fix on the way:
https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/364362
** Merge proposal linked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/364362
--
You received this bug notification because you are a member of Ubuntu
** Changed in: mutter (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap rendering at
You are a living legend Daniel. Thank you for your work :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
To manage
Yes I will be backporting the same fix to bionic. At least I will try
to. I don't know what conflicts and incompatibilities might be in mutter
3.28.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Łukasz
Will you not be following/patching bionic with this fix? (@Daniel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap rendering at
I think we can assume that at least the mutter cosmic SRU does not
introduce regressions and does fix the bug for certain testers. In case
there's a follow-up fix needed, please file a separate bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package mutter - 3.30.2-1~ubuntu18.10.4
---
mutter (3.30.2-1~ubuntu18.10.4) cosmic; urgency=medium
* Add support for high frame rate displays (LP: #1763892):
- Drop clutter-Smooth-out-master-clock-to-smooth-visuals.patch
- Add
there is also this:
https://github.com/solus-project/budgie-desktop/pull/1591
however just not sure if it's something that they need to rebuild there
also with these changes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Rachel,
Please use the test case at the top of the bug.
There are also other bugs which may make mutter appear to not render at
full speed. Most notably:
https://gitlab.gnome.org/GNOME/mutter/issues/406
but also most of:
https://trello.com/c/Q6JYXPPs
You need to be careful to not confuse
mutter 3.30.2-1~ubuntu18.10.4 doesn't appear to solve this issue in
ubuntu budgie.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap rendering
Verified on cosmic that mutter version 3.30.2-1~ubuntu18.10.4 has fixed
this bug.
** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verification-done verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Confirmed fixed in Pop_OS 18.10 using the test case provided.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
To manage
Installed new mutter from proposed today and... Well it didn't crash my
system. Due to other complications (which were mentioned previously in
may last comment)/ I cannot confirm if it actually fixes the 120/144hz
issue in my specific environment. However the changes seems safe enough
to me.
Hello Knut, or anyone else affected,
Accepted mutter into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.30.2-1~ubuntu18.10.4 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: mutter (Ubuntu Bionic)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to
Correction:
https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/363599
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to
** Merge proposal linked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/363599
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor
When do you expect to get into Bionic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
To manage notifications about
Cosmic branch prepared:
https://code.launchpad.net/~vanvugt/mutter/+git/mutter/+ref/fix-lp1763892-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter
** Description changed:
[Impact]
Gnome Shell redraws at 60 FPS at most, regardless of the hardware
refresh rate, and regardless of the current display mode. This is
particularly annoying for owners of 144Hz/120Hz/240Hz displays.
[Test Case]
- TODO: Use env var to verify?
+ 0.
** Description changed:
- Monitor is set to 144hz, but on Wayland it visually fails to go above
- 60Hz. I have confirmed the monitor is running at 144Hz during the
- Wayland session, and that is also the setting in the Settings control
- panel.
+ [Impact]
- Using the additional NVidia drivers
Thanks Daniel for your recent comments. They are very helpful. As
someone who upgraded to Cosmic specifically to fix this bug. I found it
still wasn't working and simple was not sure the reason (as have other
factors at play on my system, including Budgie Desktop, multiple
monitors, and nvidia
I am aiming to get the fix(es) into cosmic before bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
To manage
Oops. I forgot about that regression which broke it on Xorg. And that
old patch needs to be removed to get Xorg up above 60Hz.
** Also affects: mutter (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu Bionic)
Status: New => Triaged
** Changed in:
Still working on getting the fix into cosmic first.
Although it's easy to forget this bug is for Wayland only. In theory
Xorg sessions don't need fixing. In practice though, I find 120Hz
displays sometimes need a lot of encouragement to go above 60Hz even on
Xorg. I think that problem is a
Hi Daniel van Vugt, would you be kind enough to let us know how to apply this
patch and compile mutter from source. Thank you,
Marius.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
Nothing about Bionic yet? Still need the "CLUTTER_DEFAULT_FPS"
workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap rendering at
** Changed in: mutter (Ubuntu Cosmic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap rendering at
I've generated a fresh patch for 3.30 based on the final upstream
commits in 3.32:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/318.patch
It's functionally identical to what's already in disco. I wouldn't
bother updating the disco patch though since it changes nothing
functional and
** Changed in: mutter
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
To manage
** Changed in: mutter (Ubuntu Cosmic)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap rendering at
** Changed in: mutter (Ubuntu Cosmic)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap rendering at
mutter (3.30.2-2) unstable; urgency=medium
[ Daniel van Vugt ]
* Add Sync-to-the-hardware-refresh-rate-not-just-60.00Hz.patch to render at
the full monitor refresh rate (LP: #1763892).
[ Jeremy Bicha ]
* debian/libmutter-3-0.symbols: Mark a Wacom symbol as linux-any
[ Patrice
Yes I certainly aim to get the fix into 18.04 eventually. This counts as
a hardware enablement bug so it shouldn't be a problem. The only delay
is that we need to ensure the fix(es) are in 19.04 and 18.10 first.
If you're only using Xorg then you only need one of the fixes, which is
to drop
Hi there. Sorry but I'm a bit confused as to which branches will be
getting this fix and which ones will not be. Specifically I as wondering
if a fix might be back-ported to 18.04. Because I need to stay on LTS
release for the canonical kernel live patching service. Otherwise I
really would not
** Changed in: mutter (Ubuntu Cosmic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
Yes, removing the change from the SRU would resolve the problem,
weirdly. Though without fixing the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter
That fix doesn't appear to be merged upstream.
Why are you not comfortable about what I proposed?
I will remove the change from the SRU, then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
** Tags removed: artful
** Tags added: bionic cosmic disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
To manage
Here's the final missing piece:
https://salsa.debian.org/gnome-team/mutter/merge_requests/20
** Changed in: mutter (Ubuntu Cosmic)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yeah this bug started out as just being about Wayland so I don't feel
comfortable making this bug just about the Xorg case now.
There is a solution though. Just add the Wayland fix in:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/171
It may require some backporting to 3.30 as of
I should say:
> We are proposing taking the version of mutter from disco for an SRU,
and it has the above patch.
For that this bug needs to be considered to be fixed in the development
release, and fixed by the SRU.
If we split it into "wayland" and "Xorg" halves, we could do that.
I know the
Can we please use a different bug for Wayland?
We are proposing taking the version of mutter from disco for an SRU, and
it has the above patch.
Could you please also write an SRU template for this bug?
** Also affects: mutter (Ubuntu Cosmic)
Importance: Undecided
Status: New
**
Hmm, that's not quite right. The Xorg fix has landed, but the Wayland
fix has not. Both require changes to mutter.
** Changed in: mutter (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug was fixed in the package mutter - 3.30.1-4
---
mutter (3.30.1-4) unstable; urgency=medium
[ Andrea Azzarone ]
* d/p/x11-close-display-in-an-idle-function.patch:
- close the x11 display in an idle function. This fixes a crash when running
'gnome-shell
Proposed fix for Xorg sessions:
https://salsa.debian.org/gnome-team/mutter/merge_requests/19
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap
Verified on a 120Hz display that Xorg sessions only need clutter-Smooth-
out-master-clock-to-smooth-visuals.patch removed to fix this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
** Description changed:
Monitor is set to 144hz, but on Wayland it visually fails to go above
- 60Hz. On XOrg it runs higher and feels much smoother. I have
- confirmed the monitor is running at 144Hz during the Wayland session,
- and that is also the setting in the Settings control panel.
+
When this bug was first reported in 17.10 it was a Wayland-only bug and the fix
for that is awaiting review:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/171
However since 18.04, a patch was introduced to Ubuntu/Debian that seems
to be affecting Xorg sessions now too. So I think that
71 matches
Mail list logo
