KDE Ends Out October With More Fixes, Continued Polishing To Plasma Wayland

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • bple2137
    replied
    Originally posted by TemplarGR View Post

    I know, but what i meant was for it to become the defacto standard of the Linux desktop. That way apps may begin to use it instead of pulseaudio emulation.
    As I understand it, there are no plans of replacing PulseAudio API at the moment, hust like there's no plan to introduce JACK replacement. In a interview I read few months ago, Wim Taymans said that those APIs are now used as "audio toolkits" and until somebody will come out with some new API that will be better, there's no need to replace them - if I'm getting it correctly. Another thing is apps that do something more to the audio on lower level, like PulseEffect. They already prefer PW to PA from what I see.

    I think PW will become standard, default audio server much sooner than Wayland will become the default display protocol. There are no huge blockers or anything that would straight up prevent most users from switching already. Just need some time to prove it's worth switching by default for distros.

    Leave a comment:


  • pracedru
    replied
    Having tried Plasma Wayland on my new laptop a little bit. I can say that it is really close to being ready. Looks great. Keep on going!!

    Leave a comment:


  • TemplarGR
    replied
    Originally posted by scottishduck View Post

    For most regular users, you could go all pipewire right now and not have any issues. Have been doing so for some time.
    I know, but what i meant was for it to become the defacto standard of the Linux desktop. That way apps may begin to use it instead of pulseaudio emulation.

    Leave a comment:


  • Nth_man
    replied
    Originally posted by bple2137 View Post

    > still useless with multi screen for me, keeps placing my icons and tray on the wrong monitor.

    The good thing is, KDE devs know that it's bad for now and are addressing the issue. My guess is that it will take few more releases to sort it out.
    Yesterday that was solved:

    Leave a comment:


  • scottishduck
    replied
    Originally posted by TemplarGR View Post
    It is great that KDE has fully embraced Wayland at last. It is improving fast and is quite usable today with only a few major issues left to fix. Now with Nvidia also playing ball with GBM, we can expect Wayland to dominate the Linux desktop soon. Next stop: Pipewire...
    For most regular users, you could go all pipewire right now and not have any issues. Have been doing so for some time.

    Leave a comment:


  • Random_Jerk
    replied
    Originally posted by ALRBP View Post

    From what I heard, Pipewire already works pretty well. While I am sticking to Xorg due to Kwin's Wayland implementation still not managing multiscreen properly, I am seriously thinking about switching to Pipewire.
    KDE X11 also has issues with multi-monitor support. It still doesn't work with monitors of different refresh rates, it pretty much forces the higher refresh rate monitor to work at 60 Hz or whatever the lower monitor works at. On KDE Wayland, it works perfectly, but is marred by the issues mentioned here. It's a 'pick your poison' type situation right now.

    Leave a comment:


  • er888kh
    replied
    Originally posted by RealNC View Post
    So if I start an infinite loop of icon loading at startup, Plasma will asymptotically approach infinite speed and zero memory over time. Brilliant!
    It might instead approach a limit, and be still strictly decreasing/increasing. Kind of like Basel problem.

    Leave a comment:


  • ALRBP
    replied
    Originally posted by TemplarGR View Post
    It is great that KDE has fully embraced Wayland at last. It is improving fast and is quite usable today with only a few major issues left to fix. Now with Nvidia also playing ball with GBM, we can expect Wayland to dominate the Linux desktop soon. Next stop: Pipewire...
    From what I heard, Pipewire already works pretty well. While I am sticking to Xorg due to Kwin's Wayland implementation still not managing multiscreen properly, I am seriously thinking about switching to Pipewire.

    Leave a comment:


  • TemplarGR
    replied
    It is great that KDE has fully embraced Wayland at last. It is improving fast and is quite usable today with only a few major issues left to fix. Now with Nvidia also playing ball with GBM, we can expect Wayland to dominate the Linux desktop soon. Next stop: Pipewire...

    Leave a comment:


  • bug77
    replied
    Originally posted by ALRBP View Post

    Similar for me, but with krunner and full-screen programs.

    These multiscreen placing issues have to be solved to make Wayland a real full replacement for Xorg.
    It's on the KDE Wayland's list of blockers. It doesn't restore Wayland native windows at all, which is super-annoying since I'm used to having about a dozen tabs open in Konsole, which I now lose on every restart

    Leave a comment:

Working...
X