[Bug 1820832] Re: (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
> 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 usage, I am not certain. However what I am sure of is that it does no fix the 60hz framerate issue with multiple monitors, on NVIDIA. So have now reported the bug over on NVIDIA's forum. With links back to here: https://devtalk.nvidia.com/default/topic/1049107/linux/-linux-xorg- multiple-monitors-limits-the-framerate-of-faster-120-144hz-monitors-to- 60hz/ -- 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/1820832 Title: (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1820832/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820832] [NEW] (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
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 at the top of the other bug report ^^ This we found today happens with either amd vega graphics, or nvidia pascal graphics, the vendor doesn't seem to matter. We have both seen the same issue (xorg). This is on 18.10, and booting into the 'Gnome (xorg)' login option. With the FPS being logged by journalctl -f. With only single monitor attached. Then it initially goes as high as the primary monitor can show. (And glmark2 running in background, to maintain a continued load). Which is 120fps for my case. Then as soon as secondary monitor is plugged in, which is a 60hz TV. This is being plugged into the HDMI port of the same graphics card in real time. Then the FPS logged by 'journalctl -f' drops, and becomes capped to 60hz, in the output being printed by journalctl -f. My setup: kernel 5.0.0-05-lowlatency #201903032031 NVIDIA Driver for UNIX platforms 415.27 (the closed source one) ubuntu 18.10 mutter version: mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed] mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all [installed] To confirm where the '.4' at the very end of the ~ubuntu18.10.4 version number, it seems to be that we have updated now on our client machines the be most recent bugfix updates, kindly provided by Daniel. Which closed the other bug https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being referred to, as being solved for people's single monitor scenarios. Thanks again for the other recent bug fixes in this area, it is a nice progress. Very helpful! We hope you can also look into this latest problem / issue for the multiple monitor scenario. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: 144hz 60hz mutter xorg -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1820832 Title: (xorg) multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820832/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730460] Re: Very poor multi-monitor performance in Wayland sessions
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 Title: Very poor multi-monitor performance in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1730460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
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 monitor but mutter seems to cap rendering at 60FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730460] Re: Very poor multi-monitor performance in Wayland sessions
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 other bug report ^^ This we found today happens with either amd vega graphics, or nvidia pascal graphics, the vendor doesn't seem to matter. We have both seen the same issue (xorg). This is on 18.10, and booting into the 'Gnome (xorg)' login option. With the FPS being logged by journalctl -f. With only single monitor attached. Then it initially goes as high as the primary monitor can show. (And glmark2 running in background, to maintain a continued load). Which is 120fps for my case. Then as soon as secondary monitor is plugged in, which is a 60hz TV. This is being plugged into the HDMI port of the same graphics card in real time. Then the FPS logged by 'journalctl -f' drops, and becomes capped to 60hz, in the output being printed by journalctl -f. My setup: kernel 5.0.0-05-lowlatency #201903032031 NVIDIA Driver for UNIX platforms 415.27 (the closed source one) ubuntu 18.10 mutter version: mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed] mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all [installed] To confirm where the '.4' at the very end of the ~ubuntu18.10.4 version number, it seems to be that we have updated now on our client machines the be most recent bugfix updates, kindly provided by Daniel. Which closed the other bug https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being referred to, as being solved for people's single monitor scenarios. Thanks again for the other recent bug fixes in this area, it is a nice progress. Very helpful! We hope you can also look into this latest problem / issue for the multiple monitor scenario. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1730460 Title: Very poor multi-monitor performance in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1763892 Title: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
> 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, and linux kernel (dmesg | grep -i nvidia && uname -a). Another interesting thing (for multi-monitor users) is to see if the same thing happens with both of the monitors connected off of the intel integrated graphics (motherboard ports) instead. (Should that be an option, for these testing / debugging purposes). -- 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 monitor but mutter seems to cap rendering at 60FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
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 Ubuntu. https://bugs.launchpad.net/bugs/1763892 Title: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
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. Hopefully others can also install / confirm / deny. -- 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 monitor but mutter seems to cap rendering at 60FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
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 card with the closed 415.xx drivers). And even after switching to intel igp (and physically removing my nvidia graphics card), loading up Gnome 3 / unity desktop instead of budgie, and physically disconnecting my 2nd 60hz TV. The original 'remove patch' + CLUTTER_FPS env var still was not changing anything. My xrandr output is claiming 120hz (for acer x34p monitor). However it's still mouse trails and not feeling 120hz. However my other factor of uncertainty is having a very low powered gpu (GT 1030 pascal). However that should be enough? for just regular desktop. Without anything more taxing Basically I don't want to spend hundreds of pounds on a more powerful graphics card if it cannot properly drive at high refresh rates on linux for these other reasons. So these fixes are potentially very important to me in respect of that future hardware buying decision. So yes... am very much looking forward to trying out any new fixes being targeted for cosmic. To find out if they can help anything further. Thank you for these continued efforts towards solving this problem Daniel. -- 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 monitor but mutter seems to cap rendering at 60FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS
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 mind upgrading. Not using wayland over here just xorg. Here is my mutter version. And my Ubuntu software updater says 'no new updates'... $ sudo apt search mutter | grep -i mutter WARNING: apt does not have a stable CLI interface. Use with caution in scripts. gir1.2-mutter-2/bionic-updates,now 3.28.3-2~ubuntu18.04.2 amd64 [installed] GObject introspection data for Mutter libmutter-2-0/bionic-updates,now 3.28.3-2~ubuntu18.04.2 amd64 [installed] window manager library from the Mutter window manager libmutter-2-dev/bionic-updates,now 3.28.3-2~ubuntu18.04.2 amd64 [installed,automatic] Development files for the Mutter window manager mutter/bionic-updates,now 3.28.3-2~ubuntu18.04.2 amd64 [installed] mutter-common/bionic-updates,bionic-updates,now 3.28.3-2~ubuntu18.04.2 all [installed] shared files for the Mutter window manager -- 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 monitor but mutter seems to cap rendering at 60FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1763892/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1471430] [NEW] systemd-gpt-auto-generator[$pid]: Failed to determine partition table type of /dev/sda: Input/output error
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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765586 I stongly believe it to be the same bug. For more infos go there. It is basically that the error code is always reported back to the user incorrectly. Due to a genuine bug in the affected systemd component(s). The component is responsible for auto-finding and auto-mounting GPT partitions at boot time. In absense of a valid fstab file (because mounting fstab failed). Most times there is no real I/O error. The error message is extremely non-intuitive and alarming + confusing for users. They may un-knowningly try to take more drastic actions such as replacing their HDD etc. Which are not necessary. In my case it was that: * It was the result of removing or failed HDD physical (permanment) device. * Which had an entry in fstab. Now what should happen, and has historically happened with upstart, up to and including 14.10 is this message should appear during boot time (when the fstab fails to find the disk to mount): http://imgur.com/a2NoohQ http://www.gooditdad.com/ubuntu-press-s-to-skip-mount-or-m-for-manual- recovery/ This is a common situation that many users may find themselves in. When their fstab file is not valid in respect to the currently attached system disks. Including USB removable storage etc. 2 work-arounds: * In Grub -- Ubuntu Advanced Boot Menu -- upstart mode * Edit /etc/fstab file and try to find / comment out / disable the offending entries 2 solutions: * Look to get this but fixed upstream in debian / systemd / wherever * Don't use systemd ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: boot-failure fstab systemd -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1471430 Title: systemd-gpt-auto-generator[$pid]: Failed to determine partition table type of /dev/sda: Input/output error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1471430/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 424370] Re: Gnome session fails on login
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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 424370] Re: Gnome session fails on login
** 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. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
