Comments

This profile is from a federated server and may be incomplete. Browse more on the original instance.

KarnaSubarna, to linux in GNOME Sees Progress On Variable Refresh Rate Setting, Adding Battery Charge Control
@KarnaSubarna@lemmy.ml avatar

My monitor is old, doesn’t support VRR 😕

KarnaSubarna, to linux in GNOME Sees Progress On Variable Refresh Rate Setting, Adding Battery Charge Control
@KarnaSubarna@lemmy.ml avatar

If you are using Arch, it can be enabled (though it’s still experimental) [1]

[1] wiki.archlinux.org/title/Variable_refresh_rate#GN…

KarnaSubarna, to linux in GNOME Sees Progress On Variable Refresh Rate Setting, Adding Battery Charge Control
@KarnaSubarna@lemmy.ml avatar

I believe it’s actually a Mutter thing [1]

[1] gitlab.gnome.org/GNOME/mutter/-/…/1154

KarnaSubarna, to linux in GNOME Sees Progress On Variable Refresh Rate Setting, Adding Battery Charge Control
@KarnaSubarna@lemmy.ml avatar

Quality control is important for a project that is going to be supported for long time, and used by many. Slow but steady is a right approach for open source project, IMO.

KarnaSubarna, to linux in Mesa's NVIDIA Vulkan Driver "NVK" Now Exposes Vulkan 1.3 Support
@KarnaSubarna@lemmy.ml avatar
KarnaSubarna, to linux in NVIDIA 550 Linux Beta Driver Released With Many Fixes, VR Displays & Better (X)Wayland
@KarnaSubarna@lemmy.ml avatar

It’s still in Beta stage.

KarnaSubarna, to linux in AMD Publishes XDNA Linux Driver: Support For Ryzen AI On Linux
@KarnaSubarna@lemmy.ml avatar
KarnaSubarna, to linux in GNOME Network Displays Adds Support For Chromecast & Miracast MICE Protocols
@KarnaSubarna@lemmy.ml avatar

The application will stream the selected monitor if the mutter screencast portal is available. If it is unavailable, a fallback to X11 based frame grabbing will happen. As such, it should work fine in almost all setups.

Source: gitlab.gnome.org/GNOME/gnome-network-displays

KarnaSubarna, to linux in I feel like I'm missing out by not distro-hopping
@KarnaSubarna@lemmy.ml avatar

If your use cases (a.k.a. requirements) are met by your current distro, never switch.

If you are satisfied with stability, availability of support, quick availability of security patches, never switch.

This is particularly important when you are using your Linux desktop as your daily driver.

Most you can do is to check what additional features other distros are offering (rolling release, hardened/zen kernel, x86-64-v2/3 support, file system type, user base, availability of packages, package formats, overall documentation etc.), validate if you really need those features.

If you are interested or just curious to test those features, install that distro on a VM (QEMU/KVM) to try it out first safely. Use it on VM for a while, make yourself comfortable with it. Once you are satisfied with it, only then switch.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • fightinggames
  • All magazines