Question: How can I make a simple app with libadwaita?

Reply: Fork GNOME.

How many windows do you usually have open in a workspace? Wouldn’t the usual Meta+Direction shortcuts be quick enough for 2-4 windows?

Yeah you can mitigate it. Doesn’t change the fact that if you have no CPU time available, the audio is not getting played.

Audio from low priority processes is expected to stutter under high CPU load. I experience this a lot when playing music while compiling programs.

Probably something like “sudo this_gui_app”. This is not possible under Wayland. But who knows? This guy is being as vague as possible with details.

Sway or Hyprland for compositor, Waybar for status bar, fuzzel for app launcher, swaync for notifications, wleave for logout menu.

Everything should work across Hyprland and Sway except for Waybar worskpaces, you need a different configuration for them.

Desktop users (except for business) don’t make Microsoft any money, so they probably don’t care.

Do you specifically need ffmpeg? If it’s just screen recording from the terminal, wl-screenrec has the best performance (meaning low CPU usage) for Wayland screen capture. It does require the new screen capture extensions so it will depend on your compositor.

You can use your own server.

I’d say wl-screenrec (https://github.com/russelltg/wl-screenrec) shows the best screen capture performance on Linux. I guess it could be even better since Wayland has released newer protocols and newer versions of the protocols used in wl-screenrec.

I sincerely hope your reply in the mailing list was satire .

Is there another example of this happening in Facebook aside for the openKylin post? I looked around and every article is only talking about this specific DistroWatch issue.

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2356

wlroots doesn’t support HDR.

TRULY modern OS

What does this even mean? So iOS, MacOS, Windows11, Linux aren’t modern?

a way better compositor than wayland (in fact, android has the best compositor in the world, compared to ANY OS)

Wayland is not a compositor, it’s a protocol. SurfaceFlinger can totally be made in Wayland. Saying SurfaceFlinger is better than Wayland is like saying words are better than English.

A properly modified desktop OS based on it (better than Samsung’s DeX for example), that is also able to run normal Linux apps, would be a huge winner.

Nobody will ever use this on Linux, unless it is implemented in Wayland. It is infinitely more likely for Android to rewrite its compositor for Wayland than SurfaceFlinger being adopted as Linux’s main compositor.

Do you really talk to your friends through email?

Did you submit a bug report?

I’m pretty sure that screenshot is Wayfire, not Weston.

What about the certificate installation on windows?

That’s simply bad software practice, which was fixed once pointed out. Fact is that if they had done this on purpose, they wouldn’t have changed it and instead, would’ve came up with an excuse to keep it the same way.

I never claimed it’s malware

I don’t keep track of who says what on this app. Many people in this thread have the idea that RustDesk is some sort of Chinese spyware that is secretly transmitting their files to the CCP. If that’s not your opinion, then I guess we are not in disagreement.

There’s no way for the user to know that clicking this button will edit their GDM config and disable Wayland

Yes, that’s the wrong way to do it, which is why they changed it. I’m not saying this is perfect software developed by experts, but the idea that RustDesk should be avoided at all cost is insane, specially when they have fixed every issue that was raised.

The only thing they are missing is a security audit done by a third party, which costs money and I doubt they care enough to pay for that just to stop all the finger pointing.

Bad coding practices is not malware, that just means the devs are not experts. Also, these were fixed when pointed out by the users, which is the whole point of being open source. The only reasonable issue is the direct modification of the GDM config, which required the user to click a button.