I did a zypper dup yesterday on my tumbleweed system. Next to other updates this also brought nvidia 570.124. And after that I noticed that every time when I see the Lock Screen and try to login again, the system freezes and is not responsible anymore. The first login after system start work, but when the system locks after inactivity the problem occurs. The only thing I can do is to force a reboot.
Is this a known bug?
I’m having issues since the first 570 beta package was pushed. Lockscreen is not okay, I get black screen when sleeping, and the new 570 also broke the GL package.
Try to downgrade to the last working driver. For most people it’s 550.
the previous (and first) 570 release worked for me, at least
Then go for it while it’s still in the repos. 
P.s.: And watch out for mismatched package versions. The non-free repo pushed a 550 driver package with the 570 beta downgrade I did today. It won’t work, manually downgrade everything to the first 570 if it happens to you.
I will wait for a few days because I have no other problems. I have just disabled screen locking for now 
Ok I have to correct myself, it is not the Lock Screen but the wake-up from switched of screens. Only one of my monitors gets back, the other stays black and on the first screen I can see from the clock in the task bar, that the system freezed right at the moment of moving my mouse again
What DE are you using? (GNOME, KDE, or something else?)
I’m running GNOME here, and so far, I haven’t seen this issue here. It might be DE-specific.
I am using kde plasma with wayland
The behavior is strange. Sometimes the secondary screen is working even if the primary one is freezed.
ok it seems that this is really a bug with the new driver: Bug: 570.124.04 - freeze on monitor wakeup - "Flip event timeout" - Linux - NVIDIA Developer Forums which is kind of a relief because i was afraid my hardware is broke
is there a way to revert to the previous version?
If you’re using btrfs and have snapshots enabled on the system, you can roll back to before the update, lock the old driver package (with zypper al), and then re-run the update.
Yes but my whole system uses btrfs even home, I do not want to revert other changes I made there.
But, I noticed that the repository still contains the previous version of the nvidia driver, it is also possible to select the older version from yast/software but there are more than one relevant package and I do not know which one to downgrade. I hoped that there would be an easy zypper command which just downgrades all of the driver packages. But anyway I just disabled the display energy saving option, that keeps my monitors enabled all of the time (i enabled lock screen again though) and this helped so far.
That why you don’t snapshot home!!! Snapshot is NOT a backup process!!!
I did not explicitly enabled snapshoting for /home. Maybe it is excluded by default?
# snapper list-configs
Config │ Subvolume
───────┼──────────
root │ /
It is not standard to have /home in snapper in a BTRFS root partition You have to add it
So than I am probably fine.
Snapshots work on btrfs volumes, not on the entire partition.
You can inspect the contents of a snapshot using snapper - see man snapper for details (snapper status is what you likely want). That is a way you can confirm whether or not reverting the snapshot is going to change things that you don’t want to change.
On my system, I was not able to resolve this issue so I turned hibernation off. Below are details; I see you already mentioned that you turned sleep off. This still allows a password locked screen after a given time; just not a black screen.
Procedure for disabling hibernation/sleep
In BIOS → Power → Deep Sleep Control → disabled
And/or
As su,
cd to /etc/systemd/
and
man sleep.conf.d
check either usr/lib/systemd or /etc/systmd/ … sleep.conf
copy sleep.conf from usr/lib/systmd to /etc/systmd/
gedit sleep.conf
[Sleep]
AllowSuspend=No
AllowHibernation=No
AllowSuspendThenHibernate=No
AllowHybridSleep=No
… by default, these operations are commented out …. need to state ‘No’ directly
[Sleep]
#AllowSuspend=yes
#AllowHibernation=yes
#AllowSuspendThenHibernate=yes
#AllowHybridSleep=yes
It seems that the problem is related to monitor sleeping. The lock screen does not cause the issue. But after rebooting the screen can sleep, if you wait to long to login. This can cause the issue too.