OK I have now regression tested on the latest 19.10, with the above
^^software stack. All except incrementing the kernel from 5.8.11 to
5.8.13.
I can now confirm that the old bug has also re-appeared on 19.10 too. So
it is not only exclusive to 20.04.
To myself, I really don know what to try.
It would be nice to understand what is going on here. Currently on 19.10
and have not upgraded to 20.04 yet... because of this very same bug! It
took so long to get rid of the last time around. Many months.
Should also do a regression test here back on 19.10 too? It seems I can
install both the
Did you see it work on previous ubuntu version (19.10)? Or is 20.04 the
first version you tested here?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1820832
Title:
Thanks for pointing that out because I also had
__GL_SYNC_DISPLAY_DEVICE=DP-0 in /etc/environment as completely forgot
to mention that in my previous comment to yours here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Hello there. Good news for a change:
Re-tested this bug today on latest linux 5.3.1 kernel and nvidia 435.21
binary (closed) drivers. And it seems like there might be some
improvement now.
What I noticed this time:
* Enabled 120hz overclock on my high refresh 120hz monitor, and rebooted this
well by that logic, then somebody with an amd ryzen APU (such as 3200G
or whichever with the integrated Vega graphics). Would also not be
affected by this bug.
But the other reason would be that intel's linux igp drivers are not
affected. That is a different reason as to whether the gpu is being
> As luck would have it, one user upstream found a solution for NVIDIA
> documented here:
>
> https://gitlab.gnome.org/GNOME/mutter/issues/503#note_463305
>
Hello. Tried this suggestion today (setting "__GL_MaxFramesAllowed=1" in
/etc/environment, and rebooting). It might have decreased my CPU
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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz monitor
multi-monitor FPS bug for xorg, discussion moved to --->
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820832
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1730460
Title:
Public bug reported:
multiple monitors on xorg
=
Was recently discussed over on
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892
Another user + myself have the following issue:
The slowest connected display limits the FPS. The test case we used is
over
multiple monitors on xorg
=
Was recently discussed over on
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892
Another user + myself have the following issue:
The slowest connected display limits the FPS. The test case we used is
over at the top of the
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 Desktop
Packages, which is subscribed to mutter
> 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,
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 Desktop
Packages, which is subscribed to mutter in
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.
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
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
17 matches
Mail list logo
