Pop!_OS (Linux)

5580 readers

4 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 2 years ago

MODERATORS

[email protected]

Finally got to try wayland on Pop!_OS 22.04 (social.ggbox.fr)

submitted 4 days ago by [email protected] to c/[email protected]

2 comments fedilink hide all child comments

This is a followup of my previous post where I struggled to use wayland on 22.04 with nvidia.

After a few more reading and tinkering, I found out that I needed to actively install the more recent nvidia-driver version 570 to have better wayland support, so that's what I did. It was kind of janky as my screen just went black as I apt installed the driver, I had to reset the computer. The next boot, I was running no nvidia driver at all, so I re-did the apt install and it actually completed this time. After a second reboot, I was now running nvidia driver version 570.153.02, yay!

With that out of the way, I proceeded to test those wayland sessions again, starting with KDE Plasma, but I found it is completely broken for me. Most mouse clicks don't even register, and there is a several seconds lag on everything, it's very weird and unusable.

Now for gnome wayland. Well, to my surprise, this works about OK. The desktop is relatively smooth at 144hz. I can't help but feel some extra latency on the mouse cursor but it's still usable. So much so that I actually have been trying it out for a few days now, with mixed results I'm afraid.

While it does work for the most part, it's still not as good an experience as X11 for me, for a few reasons that I found out with daily use :

I use mumble extensively, and keyboard shortcuts don't work on wayland (https://github.com/mumble-voip/mumble/issues/5257). I had to set a global gnome shortcut that sends rcp commands to mumble to mute/unmute which was kind of a pain to figure out. I've also lost the "push-to-mute" feature in the process, which is my prefered way to operate the muting/unmuting.
I like RustDesk for remote desktop, but it doesn't work well on wayland yet either. (it says it has experimental support, but I just get no image at all so it's just broken for me)
The extra latency is not a lot but I do notice it. I've played some Rocket League, it's decent, but not as snappy as on x11.
I've had a complete freeze of the desktop yesterday out of the blue, I've had to ssh in to loginctl session-kill my gnome session. This kind of thing never happens on X11, and I can't have that happen too often during work.

For these reasons, I'm back on x11 for now, but it was fun experimenting. I'll give wayland another go later, with better application support I'm hoping.

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

[–] [email protected] 4 points 4 days ago (1 children)

It’s not surprising you ran into issues.

KDE’s Wayland session sucked 3 years ago, it only started becoming usable for me with 5.27. Before, Plasmashell would commonly crash.

Both have improved quite a bit since 2022. Though Gnome Wayland has always been pretty stable, just lacking some features.

[–] [email protected] 1 points 4 days ago

Interesting. Thanks for the insight.