133
Where is Linux not working well in your daily usage? Share your pain points as of 2026, so we can respectfully discuss (libretechni.ca)
submitted 6 months ago by to c/linux@programming.dev
149 comments fedilink hide all child comments
 

Thought I'd create a distinct thread from the previous one asking about daily use, because I really do want to hear more on people's pain points. Great to know people are generally sounding pretty positive in those posts who recently switched, but want to know your difficulties as well! This way old and new users can share their thoughts, hopefully to inspire a respectful discussion.

OQB @kiol@discuss.online

you are viewing a single comment's thread
view the rest of the comments
[–] 41 points 6 months ago* (3 children)

I guess the biggest thing I'm missing right now is VR gaming.

But since my VR googles need WMR to work, I wouldn't be any better off with Windows 11 either.

  • permalink
  • fedilink
  • source
  • hideshow 6 child comments
    •
  • [–] 26 points 6 months ago (2 children)

    I'm looking forward to the Steam Frame, hopefully it'll support SteamOS out of the box

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 13 points 6 months ago (2 children)

    I would be a lot more excited if I wasn’t worried it was going to cost +$1,099. I hope that I am wrong.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 4 points 6 months ago (1 child)

    They said they are shooting for less than the price of the index so that’s $999 or less, not sure if they will reneg on that due to ram prices.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 11 points 6 months ago (1 child)

    Same. Quest 2. Fedora 43. 5700X3D / 9070 XT. Steam Link can't find AMD video decoder on the pc to run. ALVR has death wobble-like reprojection jitter. WiVrn works when Envision feels like it, which is never as it constantly errors out compiling due to some dependency I can't find for the life of me.

    I know compiling from source is preferred as "the linux way", but I would like to spend more time actually using my pc than fixing it. There's no reason the VR software needs to be recompiled just to change a setting. Maybe bake in the ability to change settings instead of hardcoding everything.

    Wine would be super helpful if they can find way to make older (2019 and older) Quickbooks run reliably. Lots of small businesses locked into old platforms because the accountants or the people who do accounting themselves can't learn how to use anything else, and the linux alternatives require a phd in linuxology to learn and don't offer the easy business-in-a-box functionality.

    Waydroid is neat, but poorly integrated in the desktop. It runs as a full screen app, and doesn't task switch easily.

    Please, Valve, make Steam a 64-bit native client! So few people use 32-bit systems that the few that do probably aren't running Steam to save on memory.

    Pipewire audio devices and webcam support needs to be smoother. I've never seen so much console shim hacks just to get a virtual webcam working.

    I haven't even begun to try my NXT Gladiator flight stick in linux... that might be a whole nother can of trouble to open.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 6 months ago*

    I had the same issue as you with steam link and my 7800xt. Putting this in my launch args for SteamVR fixed it RADV_PERFTEST=video_decode,video_encode DRI_PRIME=1 ~/.local/share/Steam/steamapps/common/SteamVR/bin/vrmonitor.sh %command% and if you try that and get a different error code from before, ( I think it was like 1033) swap your mesa drivers to the freeworld variety. That should be sudo dnf swap mesa-vulkan-drivers mesa-vulkan-drivers-freeworld .

    The only thing is, steamvr can't display your desktop properly if you're using wayland, it simply doesn't support it. BUT here's a cool project that can help you work around it, for some reason there's currently a bug with their pipewire implementation (or something like that) such that you have to manually connect the display streams in the coppwr pipewire gui (helvum and carla don't work), otherwise it'll only show one frame of the display stream.

    y'know what, I'm actually gonna make a post about this, since it took me many hours of searching forums to find this solution.

  • permalink
  • fedilink
  • source
  • parent