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.
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
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.
It may be related to this: https://bbs.archlinux.org/viewtopic.php?id=284076&p=2
If so, then this could be resolved by our next kernel update.
I think you could get around this by disabling hardware acceleration in VS Code. Open the command palette (Ctrl + Shift + P), search for Preferences: Configure Runtime Arguments, and add "disable-hardware-acceleration": true. You might need to do similar for other applications triggering this behavior.
I think that fixed it, haven't run into it since.
i think it's a three-way problem between asus bios, ryzen, and linux kernel. i had a similar problem that was pinning my PN51 to kernel 5.19.16 (in my case, though, i didn't get a garbage screen, i just got a hard freeze).
i am deathly afraid of bios upgrades, but i swallowed hard and took it - and then the sleep problem went away, and i went back to floating on kernel 6.
but i just got a fanless enclosure, and once i flipped off the fan monitoring, sleep stopped working again - now it hard reboots by itself without any obvious clue in the logs.
the fanless life is more valuable to me than sleep - i have an ssd and don't run persistent services, so i don't care enough to keep fighting it. but there's definitely a tussle in there.
I do get those graphical glitches once in a while but I restart immediately whenever I do and it seems to be okay