This is default installation, im not very pro in linux 
This mean that is not in separate partition? And can i change and fix the problem with this or i will be back to the initial issue?
One note i test on pop_os and the not freeze and i can kill the game (if they are running and suspend or hibernate) what is the differences, Zorin use XFCE right, and pop_os gnome.
By the way if i use a layoute of a PRO version of zorin, this happen? (i mean ubuntu like, gnome etc...)
Thanks
If it is a default installation, then you may not be using Hibernate. It does not come with it, that is something the user must set up.
Did you set up Hibernate? If not, what function are you referring to?
Sorry for my dumb questions Aravisian, but how can i check that?
I change the /etc/systemd/logind.conf
What changes did you make?
If you had set up Hibernate - I am pretty sure you would remember it. It is a pretty involved process.
Just change to ignore
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#InhibitDelayMaxSec=5
#HandlePowerKey=poweroff
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
HandleLidSwitch=ignore
#HandleLidSwitchExternalPower=suspend
#HandleLidSwitchDocked=ignore
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#HoldoffTimeoutSec=30s
#IdleAction=ignore
#IdleActionSec=30min
#RuntimeDirectorySize=10%
#RemoveIPC=yes
#InhibitorsMax=8192
#SessionsMax=8192
Ah, got it.
Yes, this is not hibernate, though I can see you are achieving a similar effect. You are preventing log out losing your work, right?
Yes
Basically if im gaming or work and close the lid, freeze or if the computer supend for not using for long time.
I cant see swap
Filesystem Size Used Avail Use% Mounted on
udev 7,7G 0 7,7G 0% /dev
tmpfs 1,6G 1,9M 1,6G 1% /run
/dev/nvme0n1p2 234G 69G 153G 32% /
tmpfs 7,8G 0 7,8G 0% /dev/shm
tmpfs 5,0M 0 5,0M 0% /run/lock
tmpfs 7,8G 0 7,8G 0% /sys/fs/cgroup
/dev/loop0 69M 69M 0 100% /snap/bitwarden/55
/dev/loop1 100M 100M 0 100% /snap/core/11606
/dev/loop2 102M 102M 0 100% /snap/p7zip-desktop/220
/dev/loop4 165M 165M 0 100% /snap/gnome-3-28-1804/161
/dev/loop3 33M 33M 0 100% /snap/snapd/12883
/dev/loop5 66M 66M 0 100% /snap/gtk-common-themes/1515
/dev/loop6 256K 256K 0 100% /snap/gtk2-common-themes/13
/dev/loop7 56M 56M 0 100% /snap/core18/2128
/dev/nvme0n1p1 511M 5,3M 506M 2% /boot/efi
tmpfs 1,6G 96K 1,6G 1% /run/user/1000
You can check swap with
swapon -s
But I think this is Not Relevant since having Swap on a partition is only relevant to if you are using Hibernate - which you are not.
I am not sure about any updates currently... but which graphics drivers are you using?
Not relevant for hibernate or suspend?
swapon -s
Filename Type Size Used Priority
/swapfile file 2097148 0 -2
Im using nvidia
Does the 460 driver also freeze the desktop up when you suspend?
They stuck on OMEN logo, and need to shutdown
Run systemctl suspend
What is the terminal output of uname -r ?
uname -r
5.11.0-34-generic
For that to work, you must set up Hibernate and create a swap partition. But do you believe this is related to your system Freezing when you suspend?
I really dont know, i search from some foruns, and they say that about swap.
But why this only happens in ubuntu or zorin, i test in pop-os, they freeze when gamming (probably nvidia drivers) but pop_os can kill the program without need to shutdow (hardpoweroff).
I dont understand why linux doesn't came with this "default".
I can resinstall Zorin (again 
) and try to create this to test, but only need to create swap?
Let's focus on this, first. I do not believe that Swap is related to your problem. But we can explore creating a Swap Partition and setting up Hibernate if you want it, in a new thread.
For this one, please review here:
Please follow the steps outlined in that thread. There is a reasonable chance that the recent update with kernel 5.11.0-34 and your Nvidia are in conflict. This may have caused your current situation to revert, even as you had previously marked it as resolved.
Ok
I already boot into the recovery menu: Select the previous working 5.11.0-27 kernel Boot up Run software updater or run sudo apt dist-upgrade in terminal Once complete, reboot normally in the 5.11.0-34 kernel
Im lost know....do i run systemctl suspend or just close the lid? (remember that i have change the config to ignore)
Retrace your normal steps in order to try to replicate the issue.
