• offspec@lemmy.world
    link
    fedilink
    arrow-up
    9
    ·
    13 hours ago

    I’m not an obstructionist but having been forced in to Wayland by plasma 6.8 it is frustrating that orcaslicer just crashes unless I tell it to run in xwayland and desk flow requires being on unstable to work with my clipboard and discord canary just shares audio from my whole desktop instead of from just my game and AGHHH I just want my things to work! So frustrating

      • offspec@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        4 hours ago

        The only variable I changed in testing was switching between the x11 and Wayland versions of plasma while I still could. Discord no longer prompts to provide an audio source, desktop will but the screen share won’t work once I actually start it. Orca crashes the moment I hit slice unless I add an environment variable to make it use x11 compatibility mode.

          • offspec@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            1 hour ago

            They’re actually talking about this in the blog post they released this week. https://discord.com/blog/discord-linux-a-year-of-upgrades Push-to-Talk etc. on Wayland

            Global keybinds on Wayland were a long-standing pain point. Wayland (rightly) doesn’t let apps listen to your keyboard in the background. Instead, it provides a GlobalShortcuts API, but the implementation can be a little tricky. The spec says a shortcut looks like “<Control>z”, but KDE expects “CTRL+z”, so Discord figures out which desktop you’re on and speaks its dialect (send the wrong one and the portal session can fall over entirely). And since every bind request can pop up an approval dialog, we only ask again when your keybinds actually change, instead of nagging you every time Discord starts. Now, features like push-to-talk work on Linux, even when Discord isn’t focused. What’s Next: More Control of Sound Sharing

            We’ve covered a lot of Linux improvements, but there’s more to do before we reach parity with the other desktop platforms. That means changing to the Wayland infrastructure itself. We use xdg-desktop-portal for screenshare, but that doesn’t provide a handle to capture app audio. Linux users have to choose between sharing audio for their whole desktop or sharing no audio at all. That’s not an experience we can accept long term, so we’re building per-app audio sharing on Wayland and giving it to the Linux community.

            We’ve once again teamed up with Igalia to implement per-app audio sharing in xdg-desktop-portal, letting you pick exactly which app’s audio is shared. We’re even implementing it on GNOME and KDE ourselves to get it to users faster. This will take some time to reach critical mass across Linux desktops, but it’s a long-term investment to make a great Linux screenshare experience for both Discord and all screensharing apps. Stay tuned!

          • offspec@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            2 hours ago

            I’m not saying audio doesn’t work, I’m saying it doesn’t narrow down to just the application I’m sharing, this is a known regression with the discord client to the best of my knowledge, and as far as I know the orcaslicer crash is a mesa issue affecting just Wayland for whatever reason

      • XiJinpingStanAccount@lemmy.ml
        link
        fedilink
        arrow-up
        7
        ·
        11 hours ago

        It’s usually not as simple as is Wayland the issue or not in my experience. Wayland and the wm/DE and the application all have to get along and it gets along better with some than others. For a variety of reasons. I had an issue with gtk on niri where specific applications would not open up and I had to do a bunch of tweaking. It did eventually work, but it really should have just worked automatically. Wayland was getting instructions from the app that it didn’t know what to do with and instead of it trying to use xwayland instead it was just failing. A lot of the problems come from the fact that X11 is OLD and because its OLD it has taken the time to work out so many random little potential issues. Wayland is new enough that sometimes it just runs into stuff that it hasn’t been tweaked to work around yet. We’re in the polishing phase now tho so these will start to get worked out I think. It’ll just take time. X11 does need replacing as its convoluted as fuck but there’s a reason some people swear by it, and that is largely for this reason. It’s just got a lot of niche functionality that takes decades of dev time to fully flesh out.

      • thehatfox@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        11 hours ago

        I’ve had a bunch of issues with Orcaslicer and Wayland. Thankfully it’s currently working for me but the last year or so I kept having to switch back to X a lot for it.

    • DaTingGoBrrr@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      10 hours ago

      Orca craches for me if I don’t force the language to be English by setting the LC_ALL variable