wayland makes multi gpu setups really nice, especially for vfio, as you don't need to bind to vfio-gpu, and you don't need to kill the server either so long as the compositor supports hotplugging
Announcement
Collapse
No announcement yet.
Ubuntu Had A Great Year In Switching To Wayland, Continued Commercial Success
Collapse
X
-
Originally posted by Danny3 View PostToo bad that they again wasting time with Snap and Flutter and we have to wait again for 10 years until they figure out that they need to drop them.
Comment
-
Originally posted by CTown View Post
Is this a lose-lose situation or am I just overthinking this? If Canonical makes Flutter popular, Google can just pull the rug from under their feet (since it will be the main framework of their new OS). Yet, at the same time it's a Google project so it has a good chance of dying soon.
- Likes 2
Comment
-
Originally posted by skeevy420 View Post
I have to imagine that this is the answer to 80% of their calls - That issue was fixed in a newer version than what Kubuntu ships with. You need to first either update from LTS to the newest .10 release or enable HWE and after doing one of those you need to install the XYZ PPA for updated KDE builds.
- Likes 1
Comment
-
Originally posted by Quackdoc View Post
flutter is here to stay, flutter might suck, but it is still one of the best frameworks for making mobile apps that don't look like a gnomes hairy ass crack. all the frameworks like that suck, but at least flutter isn't to terrible to work with.
Should the Qt Company be worried about this?
- Likes 1
Comment
-
Originally posted by lacek View PostJust out of curiosity: last time I tried Wayland, it seems Ubuntu didn't offer per monitor content scaling. I am using 175%, 100%, 100% setup in X11, I was unable to set that in Wayland (and in Plasma even under X). Is it fixed now?
Code:gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']"
- Likes 1
Comment
Comment