How does one go about measuring the battery drain of a Wayland compositor? Are there any reasonably simple tests to at least roughly check for regressions in this area?
How does one go about measuring the battery drain of a Wayland compositor? Are there any reasonably simple tests to at least roughly check for regressions in this area?
Since KiCad still does not work with Wayland, I decided to give Horizon EDA a try (https://horizon-eda.org/).
Now, that I shaved a yak by writing a little package for installing Horizon on Gentoo (https://codeberg.org/smeikx/horizon-eda-gentoo), I can first start figuring out how to design circuit boards, and then finally get back to designing my very own keyboard.
He visto el último vídeo #A1RM4X (que hace comparativas y esta a la última en #videojuegos con un pepino de #computador) donde repasa #Proton 10. Habla del controlador #Wayland. Está muy avanzado pero no está listo para Proton / Wine 10. Queda medio años o así para sustituir a XWayland.
#openSUSE #leap 16 is going to work only with #Wayland. XOrg/X11- Server will no longer supported.
Does anybody know is there still a Bug in MS #Teams with Wayland and screen sharing?
Teams from #Flathub works fine with XOrg. It always crashes with Wayland one year ago.
Unfortunately I need Teams for University and don't go away from openSUSE. I have been using this distribution for 15 years.
#Linux #github
Anyone know when #Proton (#Wine) 10 will be out?
Even #ProtonPlus does not show WINE / soda 10.
Afaik that is the version which brings native #Wayland support? One translation layer less (#XWayland), better performance, I guess?
I never gamed, now pretty deep into #GTA5 and it runs extremely well, highest settings with absolutely no glitches, lag, crashes or anything else. On a Laptop!
Does anybody have any good resources on learning Wayland? I would like to learn how it works so I can write a compositor but it feels like everything expects you to have some sort of background in this stuff and I just don't...
My modified #PopOS is having a risky window system flaw where when a new window opens, sometimes the one underneath it retains focus... I've almost copy-pasted some stuff into a chat when it was supposed to go somewhere else.
My setup is really glitchy. I want to switch to something that works better, but I have so much config that might get lost... I think I'll hold out until #COSMICDE . At least until it works on #Nvidia + #Wayland !
img2sixel
in foot and display an image but if I run #Fastfetch with a custom image it just displays the normal ASCII logo. Yet if I use neofetch
it works as expected so to me it's not an Xorg or Wayland issue or terminal Xterm or Foot it is something with #Fastfetch or the way it's built on #FreeBSD ??As a long-time Sway window-manager user on #Linux, I gave #Cosmic a try today on a new laptop.
I was surprised that it it seems to support all the tiling keyboard shortcuts I wanted use and nearly all my other other configuration.
One feature missing for me was remapping some mouse keys via libinput.
I'll stick with Sway for now because I have it dialed in with no major complaints, but will keep an eye on Cosmic's future releases. Impressed.
Linux Mint 22.1 is behaving poorly on my Lenovo laptop - screen glitching a lot when using an external monitor. Even using the newer 6.11 kernel they offer. So I'm trying out #Debian #trixie #KDE as a daily driver for a while on my older laptop. After a few hours of use, no glitching! #Wayland is working well.
I ran into an embarrassing bug when re-arranging the panel items at the bottom of the screen. The items kept jumbling up, stacking on top of each other. A reboot helped clear it up - at least the items unjumbled.
I've watched half of the 2+ hour video linked in https://mastodon.art/@troy_s/114438525670479010 by Steve Yedlin, "Debunking HDR".
I strongly recommend it to everyone interested in #HDR . I also recommend taking a break every half an hour.
Their term "scene white" is the same as #wayland "reference white".
I shall now resume watching the rest of it.
got a hand-me-down 'thin client' chromebook I'm looking to repurpose into a beater laptop I can throw in a bike bag without much concern.
looking for appropriate desktop environment / window manager setups for
+ 4G memory & 8G disk, both slow and precious space
+ cramped screen: display bars, tiling, much beyond full-screen application windows isn't necessary
+ offload most control to CLI/TUI, don't need GUI widgets for network etc.
@courtney prefer ozone has been hit or miss for me in terms of things actually implementing it.
Over all performance is much better with #wayland (IME) with the exception of if there is hardware resource contention.
Depending on your display adapter you may or may not have functional hardware acceleration enabled - not familiar with Vivaldi’s settings, maybe another thing to look into though.
The performance of #Vivaldi web browser under #Manjaro (#Arch) Linux sucks toads. It gets very laggy and scroll jumpy.
I'm wondering if it's an issue with the browser ... or if it's because I switched my desktop from X11 to #Wayland. Anybody had experience with this?
*UPDATE*
Found this page: https://wiki.archlinux.org/title/Vivaldi#Native_Wayland_support
I switched "Preferred Ozone Platform" from "default" to "auto" and I'll see how that does.
Just installed #Hyprland after watching #ThePrimeagen's reaction to #Pewdiepie #Linux install, and I'm loving it so far. Had to tweak a few things to get it just right, but the shortcut game is strong. Switching between windows and workspaces is a breeze now.