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.

  • fakeman_pretendname@feddit.uk
    5·
    3 months ago

    For trying to get back into your computer, as squid_slime mentioned, check the CTRL+ALT+F1, CTRL+ALT +F234567 etc first, and see if you’ve still got any control over the computer.

    If you get a terminal, you may be able to run “top” to show you the top processes currently running, then CTRL+C to close top, look at the ID of Cyberpunk (if it’s still running) i.e. 12345, then run “kill 12345”.

    After that you may be able to get back to your desktop - may be CTRL+ALT+F7, but could be any of the F keys really. You may have to go back and kill some other wine/steam processes. If the system is fully frozen, this won’t work.

    The other thing to look at is to see what the logs say - I can’t remember if Ubuntu includes a log viewer by default these days, but you can easily get one from your Software Centre (or you can rummage around in var/log if you’re into that kind of thing).

    Anyway, in a GUI log viewer, you should be able to see some system logs from when the program was shut down (a drop down menu at the top normally lets you select a time period) - these may help for searching i.e. “why has my Nvidia driver fallen off a bus?” rather than “Cyberpunk crashes my computer when it closes” - because the same error will have probably happened with other programs you’re not familiar with.

    Also, when I’ve had these crash-on-close in the past, it was quite often an NVidia thing, and it sorted itself out a few updates later.

    • perishthethoughtOPEnglish
      3·
      3 months ago

      Super helpful - thanks! I did not know about that Ctrl-Alt-F* thing so I will try that out ASAP. You also gave me the idea of running ‘top’ in a terminal before I start the game, so it will be there running when I exit too. Hopefully this will help get this resolved, so much appreciated.

  • Wes_Dev@lemmy.ml
    4·
    3 months ago

    Glad it’s working! Thanks for the follow-up, for anyone who runs into the same issue in the future.

  • azvasKvklenko@sh.itjust.worksEnglish
    3·
    3 months ago

    Make sure Steam is not a Snap package - it’s known from having many issues. When locked, try to switch to tty with ctrl+alt+f3 (or 4, 5,…), login, list processes using ps -aux, find if there are any processes remaining from the game or RED Launcher, try to kill it and go back to desktop (ctrl+alt+f1 or 2) to check if it’s unlocked.

  • Wes_Dev@lemmy.ml
    3·
    3 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.

  • fakeman_pretendname@feddit.uk
    2·
    3 months ago

    In response to your update, the individual setting with the program is a sort of “override” to the defaults.

    If you go into:

    Steam menu at top > settings > compatibility

    You should see options for:

    • enable steam play for supported titles
    • enable steam play for all other titles
    • run other titles with [proton 8.0-5]

    To the best of my knowledge, any title which is pre-checked by Steam (and has a green tick or whatever) is covered by the first option - this will automatically install and run using the version of Proton it was first confirmed to run with. If it ran fine with Proton 3.0-0 or whatever when it was first tested, it possibly still uses that version. Some certainly get rechecked with newer versions. It’s worth noting this is confirmed to work on Steam Deck (with its AMD graphics) - sometimes the default checked version will not work so well when you play on the desktop.

    The second option allows you to set a default Proton version for all other titles - if you’ve not adjusted this, it’s possibly set on an older version.

    You can override this on a game by game basis (as you have been doing already) - for example, on some games, steering wheel controllers work on 6.3-8, but not the newer version 7/8 etc. So my default is everything runs on the newest Proton, except I override some driving games to run on an older version.

    [Edit]The point of this being, Cyberpunk, as a confirmed working game, will have defaulted to the version which works with the Steam Deck, without you doing anything (Leaving the “run with steam play” unticked) - that version may not be best suited to a desktop/laptop running Nvidia graphics. Changing the version manually overrides the default version… and I hope it’s all working well for you :) [End edit]

    There’s a brilliant and in depth guide on the gamingonlinux website, which is definitely worth a read if you’ve got time: Gamingonlinux Steamplay guide