Core version lockscreen is 60hz

General Help
,
1

When i first boot up my pc lockscreen is 60hz but after i unlock it returns to 240hz

2

Hi and welcome! Zorin is a fork of Ubuntu 22.04 and uses a modified version of the Gnome Desktop Environment:

Ubuntu 22.04 240Hz Issue

Based on the provided search results, it appears that the issue of a 240Hz screen dropping to 60Hz on lock screen in Ubuntu 22.04 is related to the compositor and the way Ubuntu handles multiple monitors with different refresh rates.

One suggestion is to use Wayland instead of X11, as Wayland is designed to handle multiple monitors with different refresh rates more efficiently. However, the user in the search results mentioned that they encountered issues with Wayland, such as crashes when trying to open settings.

Another suggestion is to use a hack for KDE to enable a “fake” 240Hz refresh rate with X11, but this would require switching to the KDE desktop environment.

In terms of a more straightforward solution, it’s possible that the issue is related to the NVIDIA drivers or the DisplayPort cable used. One user in the search results reported that updating the NVIDIA drivers resolved the issue for them.

It’s also worth noting that the 240Hz refresh rate may only be available at lower resolutions, and not at the native 5120x1440 resolution used by the user. The xrandr output shows that the monitor can handle 60Hz at the native resolution, but not at 240Hz.

To troubleshoot this issue further, you may want to try the following:

  1. Check the NVIDIA driver version and update if necessary.
  2. Verify the DisplayPort cable version and try switching to a different cable if possible.
  3. Experiment with different resolutions and refresh rates using xrandr to see if the 240Hz refresh rate is available at a lower resolution.
  4. Consider switching to Wayland if you’re experiencing issues with X11.

Here is a summary of the key points:

  • The issue is related to the compositor and handling multiple monitors with different refresh rates.
  • Wayland may be a better option, but it’s not a straightforward solution.
  • NVIDIA driver updates and DisplayPort cable versions may also be relevant.
  • Experimenting with different resolutions and refresh rates using xrandr may help identify the issue.

Please note that these suggestions are based on the provided search results and may not be exhaustive or definitive solutions. Further investigation and testing may be necessary to resolve the issue.

Just to add, Zorin uses Wayland compositor by default.

1 Like
3

Thanks for replying i experienced some bugs on wayland so i wont use wayland
i think i will just ignore it.