all 3 comments

sorted by: hot top controversial new old
[–] 3 points 5 months ago (2 children)

Can anyone with experience chime in if removing support in 6.8 makes sense compared to 7.0? The only thing I'm coming up with is that you don't have to worry about all the other breaking changes associated with a major release but it seems to go against semver doing this before a major release..

  • source
  • hideshow 2 child comments
  • 25 comments in c/linux@lemmy.ml view that post
    [–] 4 points 5 months ago (1 child)

    I really want to run wayland but there are still some missing bits required for my workflow. Of particular importance to me, the ability to connect to RustDesk auto-launched on a headless server, and clipboard sharing in DeskFlow. My understanding is that these are still broken only because the devs are still waiting for wayland back-end additions to be implemented.

    I'm all for wayland, but they need to catch up first.

  • source
  • hideshow 1 child comment
  • [–] 2 points 5 months ago (6 children)

    I also switched to Wayland when the news came X11 would go away. It just sucks they aren't fixing all the input issues on Wayland, especially since I'm using touchpad most of the time.

    95% on Wayland is a bit hard to believe, 100% of KDE users I know both use X11.

  • source
  • hideshow 6 child comments
  • [–] 8 points 5 months ago (4 children)

    Well, now you know one who doesn't and hasn't for years

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 5 months ago (2 children)

    I also use wayland on both my laptop and desktop.

    The only issue I have is the lack of some utility which I can use to type my german umlauts using macros. On windows I had an autohotkey script so that alt + a would become ä and so on.

    I've tried a couple programs that work on wayland, but without success in getting them to work how I wanted. The last time I checked there were a couple promising candidates left that are explicitly not working on Wayland though.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 5 months ago (1 child)

    This reads like quite a different workflow, but AFAIK the standard in both x and wayland for inserting special characters is using a compose key. You can set up a key as the compose key in the keyboard settings of any de/wm/compositor (right alt in my case) and use it in a key sequence to assemble special characters. I use it all the time to type italian accent characters on a us keyboard and it's always dependable and quite intuitive even for characters I don't regularly use.

    Some examples:

    • compose a " → ä
    • compose e ' → é
    • compose c , → ç
    • compose o o → °
    • compose - > → →

    I'm not saying your use case is invalid, but it falls well into unsupported territory I feel like, and reminds me of this.

    xkcd 1172 - "Workflow"

    This said, there must be a way for an application to simulate input, that's what virtual keyboards do, including steam's virtual keyboard which is not integrated in the desktop environment, so your workflow can likely be replicated. You might need to spend some time finding the right tool for it, or possibly creating your own, but wayland and plasma wayland in particular have all the bits in place to make this happen.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 5 months ago

    I am aware of the compose key, I was just never a fan of it. I have it set up to replicate my previous autohotkey script on my laptop but I found that in some rare cases, pressing the next key for a word I am typing would change the letter from what I intended to something else.

    Using the compose key like 'compose + " a' also feels unintuitive to me and introduces one more key for me to press, though I could likely get used to it with some effort.

  • source
  • parent
  • load more comments (1 reply)
    [–] 2 points 5 months ago* (last edited 5 months ago)

    Hah, every time I try to switch to Wayland on my Debian 13 desktop I end up going back to X11. Wayland ultimately feels slower and more sluggish compared to X11 almost like a regression that occurs over time, applications that work on X11 may not work on Wayland and in my situation open but display a blank screen and, recently learned MangoHud that ships with Debian 13 has issues capturing the GPU usage while running games.

  • source
  • [–] 1 point 5 months ago

    Wayland is a mess for me with Plasma 6 (Fedora) but i'm not going back to X11. Quite a few features i use(d) have been broken along the way.

    On the upside high DPI support is getting better and better

  • source
  • [–] 1 point 5 months ago (13 children)

    so if everyone in the world used kde, "only" the usa would be on x11.

    meanwhile i still get random blackouts, frame rate desyncs, and sleep mode crashes when running wayland.

  • source
  • hideshow 13 child comments
  • [–] 11 points 5 months ago (1 child)

    Are you on plasma 6.6?

    Also "The metrics also show that basically no one is testing or developing Plasma on X11 anymore. The platform was already, for all intents and purposes, abandoned by KDE contributors." There just isn't the man power to keep supporting it

  • source
  • parent
  • hideshow 1 child comment
  • [–] 5 points 5 months ago

    i know all the reasons that switching to wayland is imperative for the distros. i also know that it still has massive gaps in the implementation that are required of a working desktop, like accessibility. it's been almost 20 years and yet here we are.

  • source
  • parent
  • [–] 4 points 5 months ago (4 children)

    I think I'm on Wayland and it's been fine?

  • source
  • parent
  • hideshow 4 child comments
  • [–] 0 points 5 months ago (3 children)
  • [–] [S] 1 point 5 months ago (1 child)

    Interesting, what hardware do you run?

    I haven't used Plasma for any significant length of time since 5.27. Coincidentally, the first major version of Plasma where Wayland was actually daily drivable for me, previous versions would have at least one desktop crash a day.

    But my experience on Gnome Wayland has always been good. At least, better than X11, even on NVIDIA before the Wayland compatibility was "good". Don't remember exactly dates or version umbers, but it was shortly after it got hardware accelerated Xwayland and before NVIDIA added GBM support. And when I switched to AMD, it only got smoother and more stable.

    And recently have been trying out labwc/wlroots and it's been a very stable experience too.

  • source
  • parent
  • hideshow 1 child comment