brent They'll most likely support it for a while at least until all of the bugs have been worked out. Like GNOME and Plasma though at some point Wayland will become the "default" session and the X11 one will get buggier as developers stop working on it.

    Actually from previous statements it sounds like there won't be a coexistence of Wayland and X11 sessions for Budgie, and once it goes Wayland, it goes Wayland-only.

    While our goal in 2023 was only to start experimenting with Wayland compositors and to take the learnings from those experiments to apply to a "future Budgie WM compositor" built for Budgie 11, we made a significant shift in our development focus starting middle of last year to accelerate our Wayland plans and work towards Budgie 10 being Wayland-only (and continuing to be Wayland-only going into Budgie 11)
    [...]
    For Q3 and Q4, our focus is to deliver a Budgie 10 series release that is Wayland-only.[...]

    https://buddiesofbudgie.org/blog/state-of-the-budgie-2023

    libxfce4windowing enables us to port functionality to support Wayland without negatively impacting use under X11, facilitate early "dogfooding" when our porting work is complete, and more effortlessly "flip the switch" to support Wayland and fully drop X11.

    https://buddiesofbudgie.org/blog/budgie-10-9-released

    Of course some of that might have changed in the meantime (as has the timeline), or I'm misunderstanding the finer points, but it sounds like there will be no more X11 session once the Wayland session is usable (outside of early testing, which will happen in parallel).

    Greatly appreciate the heads up. Wayland still does not have native proton/wine, still has issues with nvidia, and last I tried it has significant issues with context menus (as in it don't like to draw them). I'll be sticking with X. Wayland is the way forward, but still a Ways off.

      zmaint
      if there is no X11 option I may have to move on from the only DE I've used since 2017...40% of problem posts in any given forum seem Wayland-related and that's 39% too many for me. I like LOVE my goof off time but Solus is mostly productivity-used. Maybe Josh & Co. will have it dialed in by then but for now I am getting ahead of myself. Staudey quotes from the Source but I hope Reilly's gut is right.
      Again...way down the road so no worries right now.

          Two Plasma and one Budgie, all on baremetal upgraded without issues.
          My thanks to all contributors

          • [deleted]

          • Post #18
          • Edited

          Hmm.. fooyin does not start anymore. : (

          Terminal output:
          bruce@bruce-solus ~ $ fooyin
          fy.scanner: Scan of "Music" took "0:00.015000"
          Segmentation fault (core dumped)

          System information:
          Operating System: Solus 4.6
          KDE Plasma Version: 6.2.3
          KDE Frameworks Version: 6.8.0
          Qt Version: 6.7.3
          Kernel Version: 6.11.10-310.current (64-bit)
          Graphics Platform: Wayland
          Processors: 8 × Intel® Core™ i5-10300H CPU @ 2.50GHz
          Memory: 15.4 GiB of RAM
          Graphics Processor: Mesa Intel® UHD Graphics
          Manufacturer: Micro-Star International Co., Ltd.
          Product Name: GF65 Thin 10SDR
          System Version: REV:1.0

            For a long time, panel at the bottom of my screen (like a "dock") for Plasma has been starting with all the contents compressed into a single small square. That's been easy to restore back to its normal size, with "Show panel configuration" in the context menu, but it was annoying. With today's sync, apparently KDE finally got it right. It now starts out with its normal size, no workarounds needed!

            EDIT: Aw, fsck! The above seems to apply to my laptop only. When I updated my wife's and restarted it, the dock remained compressed into small square with its three contents squeezed to incredibly tiny icons. Since both laptops are identical DELL Latitudes, and both are running Solus Plasma, both fully updated, I'm not sure why that issue seems to be fixed on mine and not on hers. Again, easily worked around, but annoying nonetheless.

            MORE EDIT: After thinking about it for a while, I believe I've found the difference. Because of all the X11 vs. Wayland discussion on the forum lately, when I restarted my laptop after updating it this morning, I was curious and first launched an X11 session. Indeed, the "dock" opened to its normal size and contents. Then I rebooted and launched my usual Wayland session, and it too opened to its normal size and contents. That's why I wrote the first message above. However, I didn't open an X11 session on my wife's laptop, but just started Wayland after a reboot, and as I noted, the dock issue was still present.

            I had forgotten that I restarted the two laptops differently this time. Apparently X11's being started first made it so that Wayland also started up correctly. I hate mysteries.

              Since Kernel 6.11 I have an issue with CPU frequency in idle, it just goes down to 2.403 Mhz.
              With Kernel 6.10 or with the LTS Kernel it goes down to 400 Mhz (at it should be).
              Having a AMD Ryzen 7 8700G APU.
              Any Thoughts?

              UncleSlacky Yes, I'll be moving back to MX Linux if it's Wayland or the highway.

              How long do you figure it will be before MX Linux also drops X11 for lack of support?

                Having reinstalled my laptop's OS recently, I've needed to re-create my four Solus VMs. All went well, until I got to Xfce.

                In the Calameres installer for Xfce, I could only get this far. Notice that there's no "Next" button, so there was no way for me to create this VM.

                zmaint Wayland still does not have native proton/wine, still has issues with nvidia, and last I tried it has significant issues with context menus (as in it don't like to draw them).

                The latest Wine releases builds the Wayland support by default, so it should now probably get more testing and developer attention. It still prefers XWayland when available, but this can be worked around (for testing purposes) by launching wine with DISPLAY= wine to unset the display. I'm seeing some issues under Wayland though.

                When it comes to NVIDIA I honestly notice no real difference between Wayland and X11 these days, except that the former feels smoother (on GNOME). Haven't experienced the context menu issue.

                Oh yeah, the way notifications work is a bit annoying. Hopefully they can improve that some day.

                    Staudey It's been a couple months since I last tried it, will give it another go. Glad we have X to fall back to. Will let you know if I see any issues.

                    Most of my friends and family will not notice because they don't game, will just be me and my daughter that find the gaming bugs...

                      Staudey Does Anydesk work in Wayland? Last I checked I couldn't get any remote desktop software to work.

                          zmaint

                          Yes since V6.4 but I haven't checked the remote connection. Previously the remote had to be X11 and host could be either although that didn't always work in V6.3.

                            WetGeek

                            For a long time, panel at the bottom of my screen (like a "dock") for Plasma has been starting with all the contents compressed into a single small square.

                            That's a known issue, which has has quite a few reports on the KDE tracker. Bugs like that aren't something Solus would cause or can fix.

                              Folks, please use this thread to discuss your experience with this week's sync. For other issues or topics of interest, please start new threads. Thanks.