Pop!_OS (Linux)

5145 readers

2 users here now

Pop!_OS is an operating system developed by System76 for STEM and creative professionals who use their computer as a tool to discover and create. Unleash your potential on secure, reliable open source software. Based on your exceptional curiosity, we sense you have a lot of it.

Unleash your potential

Whether this is your first experience with Linux, or your latest adventure, all are welcome to discuss and ask questions about Pop!_OS and COSMIC. Keep the discussions friendly though, and remember to assume good intentions whenever you reply. We're all here because we have a shared love for Linux and open source software.

Support us by buying System76 hardware for you or your company! Or by donating on the Pop!_OS website through the "Support Pop" button. Pop!_OS and COSMIC are fully funded by System76 hardware sales. All systems are assembled in the USA. With your support, we'll work to push the Linux desktop forward with COSMIC.

Links

Guides

Hardware

Recommended

Community Rules

Follow the Code of Conduct

All posts on pop_os must adhere to the Pop!_OS community Code of Conduct. https://github.com/pop-os/code-of-conduct

Be helpful

Posts to pop_os must be helpful. When responding to a user asking for help, do not provide tongue-in-cheek responses like "RTM" or links to LMGTFY. Linking to direct sources that answer the asker's question is fine, but it's advised to provide some explanation as to how you got to that source.

Critique should be constructive

We within the Pop!_OS community welcome helpful criticism or ideas on ways to improve. However, basic "It's bad" or other simple negative comments don't help anyone fix anything. When voicing a complaint about something, try to point out ways the complaint could be improved or worked around, so that we can make a better product for it.

This rule applies to both Pop!_OS and its projects as well as other products available from third-parties.

Don't post malicious "advice"

It can be funny to joke about malicious commands, however this is not the venue for it. Do not advise users to run commands which will lock up their systems, steal their data, or erase their drive. Examples of this include (but are not limited to) fork bombs, rm, etc.

Posts violating this rule will be removed, even if the post is clearly in jest. Repeated offences may lead to a ban. You may understand that the command isn't serious, but a new user might not.

No personal attacks

Posts making a personal attack on any user will not be tolerated.

No hate speech

Hate speech of any kind will not be tolerated. Any violations will be removed, and are grounds for a ban.

founded 1 year ago

MODERATORS

mmstick

ahoneybun

soller

I've had to force reset my desktop running Pop after waking from sleep a couple times recently (kbin.social)

submitted 1 year ago by [email protected] to c/pop_os

9 comments fedilink hide all child comments

How's everyone weekend going? I've been dealing with this issue for a little while so I thought I would finally look into it and make a post about it.

Sometimes when I wake my PC from sleep, it fails to resume correctly. I'm able to log in from the lock screen just fine, but when I get to my desktop there's usually some graphical glitches like medium-sized black boxes spanning across different application windows. The next thing I'll notice is that if I try to close windows or interact with the desktop, it will lock up to the point I can't use my mouse or keyboard. Trying to switch to another TTY terminal doesn't even work at that point. If I switch to a TTY quickly before it locks up then I can use the reboot command normally as a fix.

If it does lock up however, I'm still able to REISUB in order to reset. I've found all the times that I've done that recently in my syslog and linked it to this pastebin; I tried to keep anything that seemed relevant from when the PC goes to sleep until when I had to reset it manually.

Looking through my syslogs, I notice lines that seem to indicate the GPU isn't waking correctly. (ie codium.desktop[19525]: [19525:0616/173717.963456:ERROR:gpu_process_host.cc(991)] GPU process exited unexpectedly: exit_code=512, and GpuWatchdog[84807]: segfault at 0 ip 00007fa297f929a6 sp 00007fa28c3fd370 error 6 in libcef.so[7fa293aef000+7770000] likely on CPU 3 (core 3, socket 0) ) I'm not sure if that means its a mesa driver issue, a CPU sleep state issue, or maybe just the current kernel update. I was hoping someone with more experience could look through the pastebin link and see if you notice anything I didn't. I separated the different crashes with white space.

My desktop is an Asus ROG Crosshair VIII Formula with a Ryzen 9 5950X CPU, and a XFX Radeon 6700x GPU

Thank you for you time and help, let me know if I left anything important out.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

I added that line into codium's config file using the instructions mmstick wrote out. What are you having issues with?

Edit: and if you're not noticing any issues you probably aren't affected then.

[–] [email protected] 1 points 1 year ago

I think that fixed it

Damn I read it 'I fixed it' instead of 'that fixed it'. My bad.