search

pop-os / nvidia-graphics-drivers

Pop!_OS NVIDIA Graphics Drivers
134 stars 7 forks source link

Steam GUI doesn't show, and process uses 100% CPU #123

Closed 13r0ck closed 2 years ago

13r0ck commented 2 years ago

Issue Steam will update, then never launch the login GUI after a fresh install of Pop!_OS. The steam process will get stuck and use 100% CPU. I have waited 20+ minutes for the GUI to show, but it never does.

Steps to Reproduce

  1. Fresh install of pop nvidia (21.04 or 21.10 or 20.04)
  2. Run sudo apt update && sudo apt upgrade -y && sudo reboot do not touch the system until after the reboot.
  3. Install steam via pop shop.
  4. Launch steam via launcher.
  5. Wait for steam update window to finish and close. The login GUI will never show, and the steam process will be using 100% CPU.

Notes

pilotstew commented 2 years ago

Thanks for posting. Same issue here on a new oryx8.

leviport commented 2 years ago

I haven't seen this lately, so I'm going to close it. I can reopen it if I'm mistaken.

jarettmillard commented 2 years ago

@leviport I had this happen in my new Oryx Pro 3 weeks ago when I first installed Steam.

leviport commented 2 years ago

Just once, or does it still happen on 510, which was released last week?

jarettmillard commented 2 years ago

Hybrid graphics were so unstable with 470 that I switched over to only using Nvidia after a few days. I haven't tried hybrid graphics on 510 yet, but I will try to remember to report back after I do.

leviport commented 2 years ago

Related to https://github.com/pop-os/nvidia-graphics-drivers/issues/61 do you think?

jarettmillard commented 2 years ago

No, this was without an external display attached. In addition to Steam never opening on first launch, on subsequent launches I would get full-system freezes in hybrid mode within a few minutes if I opened Steam. I couldn't even switch to a tty and log in.

leviport commented 2 years ago

Gotcha, thanks for the info

jarettmillard commented 2 years ago

I tried switching back to hybrid graphics today and I haven't had any lock ups yet. It's hard to say what fixed it, but 510 is a likely suspect. Unfortunately, I'm not sure if my stability issues were related to the original problem with Steam or not, since that specific problem only happened on the initial run of Steam.

leviport commented 2 years ago

Think it's ok to close the issue now?

jarettmillard commented 2 years ago

Maybe? I guess it can always be reopened if someone experiences the original issue running 510.