> 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
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
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 Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1730460
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
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1763892
Title:
144Hz/120Hz
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 Ubuntu
Desktop Bugs, which is subscribed to
> 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 Ubuntu
Desktop Bugs, 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
Public bug reported:
Right.
Well this bug is something I stumbled into today. It turns out that:
Whenever I have invalid /etc/fstab entries, the system fails to start
with systemd.
This can be seen in the debian bug tracker as bug #765586:
Karmic should be set as the 'release'.
--
Gnome session fails on login
https://bugs.launchpad.net/bugs/424370
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in ubuntu.
--
desktop-bugs mailing list
** Also affects: gnome-desktop (Ubuntu)
Importance: Undecided
Status: New
--
Gnome session fails on login
https://bugs.launchpad.net/bugs/424370
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in ubuntu.
--
14 matches
Mail list logo
