Hey y’all, I just got Cyberpunk for the first time and started playing it. The game plays fine – no issues at all while in the game – but whenever I close it out, then the game goes away, I can see my desktop again, but now no mouse clicks or keyboard typing does anything. I am effectively locked out of using my PC until I hold the power button for ten seconds to reboot.

This has happened all 3 times I’ve played this game but never happens with any other game. I searched online and tried verifying my game files in Steam, but the problem still happens.

My PC:
Unbuntu 22.04
AMD Ryzen 5
16 GB RAM
Nvidia RTX3060 - nvidia-driver-535
Steam with the native game, no mods, using these launch options:
–intro-skip --launcher-skip -skipStartScreen

Thanks for any ideas, let me know what else you might like to know.

UPDATE: It seems to have helped to enable the Compatibility mode for the game with Proton 8.0-5. Now when I exit, the game shuts down normally. Once I realized I was running a Windows game without forcing compatibility mode, this seemed like the right thing to do. But I don’t get how the game was playable at all without doing that. Most (all?) other games I’ve played on Ubuntu yet required me to enable the compatibility with Proton before they would even install. In any case, thanks all. I learned a few new tricks.

  • Wes_Dev@lemmy.ml
    link
    fedilink
    arrow-up
    3
    ·
    9 months ago

    This won’t help you recover during a freeze or crash, but it may help find the cause…maybe.

    Try running Steam from a terminal, and see if the game gives any output when crashing. I’d put the game in window mode so I can see the terminal and the game at the same time, in-case you lose control over the system. See if the terminal shows any errors.

    Usually, when my computer starts to freeze up, it’s because the disk IO is saturated. I moved my Steam library to a different drive than my OS, and that hasn’t happened since. The interface really shouldn’t freeze just because the drive is busy, but that’s what I did to fix it. Don’t know if it’s a GNOME 3 problem, a Fedora problem, or something else.