I should note that after noticing it wasn’t detected by the boot menu, I formatted as NTFS. It is detected in the list of drives that the bios has however
I’m not sure if your issues are related to the distro(s) used and not to the hardware. But if you wish immutable distros…
You can try to use Ubuntu, but installing all the apps as snaps (and/or flatpaks). That will give you immutable-like experience on a regular Ubuntu installation. Otherwise, I’d recommend to try Fedora Silverblue and openSUSE Aeon.
I’d you want immutability and things that just works, snaps are the exact opposite of what he needs. I’m gearing up to swap away from Ubuntu for the same reasons as him, and the snap ecosystem is utterly fucked and accelerating my timetable daily.
I’ve never seen something so damn broken, and it gets more so every update. It’s gotten to the point of where snap store will just straight up log me out of my session out of the blue when it finds an update so it can install it, losing all of my work.
There are many reasons Microsoft software is only “good” (and I’m using that word loosely) in business and home settings. Can you imagine a rocket taking off and windows suddenly “rebooting to complete updates” (or whatever it is that it says along those lines)?
Correct, missiles use something like RTEMS, which is named because it was used for missiles (no really, it originally stood for Real Time Executive for Missile Systems) and the operating demands for missiles have to be real-time given their unique edge cases.
I recommend that you transition instead of switching. That way you have a way to roll back If the distro you are trying out proves not to be what you expected.
I’m generally more of a Debian user, when I use Linux at least, so anything red hat based doesn’t even occur to me to recommend. I generally don’t get involved in distro discussions though.
My main interaction with Linux is Ubuntu server, and that’s where my knowledge generally is. I can’t really fix issues in redhat, so if someone is using it, I’m mostly lost on how to fix it.
There’s enough difference in how redhat works compared to Debian distributions that I would need to do a lot of work to understand what’s happening and fix any problems.
Updates I can ssh into the thing since WiFi is working and turn off I use the power button might have to change some devrules because now it’s long press is mapped to reboot a single nothing, but that should be about it.
Yeah cage is an Wayland kiosk, and for what I tested in my main machine runs KOreader with no problem and should have a virtual keyboard.
Last week the GNOME 47 development code saw Wayland DRM lease protocol support for enhancing VR headset handling and separately was also accent color support for GNOME Shell.
Adding to the recent slew of changes landing for GNOME 47, the GNOME Shell and Mutter code can now be successfully compiled – optionally – without any X11 support or requiring any X11 build dependencies.
For those wanting to build a Wayland-only Linux desktop experience without carrying any aging X11 baggage, GNOME 47 will be able to optionally offer Wayland-only support without carrying X11/X.Org support.
That landed today along with this GNOME Shell merge request for being able to disable X11 support too.
In turn this closes a two year old issue tracker over making X11 dependencies optional on GNOME.
GNOME 47 is shaping up to be a very exciting desktop update due for release in September and will be found with the likes of Fedora 41 and Ubuntu 24.10.
The original article contains 172 words, the summary contains 158 words. Saved 8%. I’m a bot and I’m open source!
How is it relying on XWayland? I don’t know of any KDE Plasma components that require X11. The apps you install might need XWayland but that is separate from the Plasma desktop.
Uninstalling Xwayland breaks it, you’re greeted to a black background and your mouse pointer.
Additionally, as per their own website, it says “The workspaces have been developed for X11 and much functionality relies on X11. To be able to make proper use of Wayland these bits have to be rewritten.”
I used Ubuntu for a long while, then Debian for a new PC because the video card or display just wasn’t working on Ubuntu.
Couple of weeks ago I finally tried this distro hopping thing people have been on about. I’d stuck with Ubuntu for so long due to an apparently misguided belief that it was stable.
I’m now using Project Bluefin from Universal Blue, a derivative of Fedora Silverblue and I’m blown away by how good it is. It uses Gnome and the maintainer has packaged a few tweaks to keep it similar in user experience to Ubuntu, along with a fantastic array of great software I never knew existed.
I’d highly recommend it to anyone historically loyal to Debian or Ubuntu.
For gaming you can easily install Bazzite as a container to access Steam. I can’t say I fully follow the tech stack that makes it work, but it just does. Whereas my boilerplate Steam install on Debian was completely botched.
Has been working for me. The issues I’ve encountered so far are all minor flatpak issues (Firefox not allowed to sleep-lock so the laptop screen shuts off watching videos etc)
Kde has a disable sleep button in the power/battery icon menu which I use as a work around, still annoying and yet another quality of life issue that Just Works ™ on other platforms
I wonder how long it’ll be possible to build Gnome with Xorg support. If I had to guess I’d say there won’t be any support within the next 3 years, because keeping future Gnome working with Xorg is work nobody wants to put in.
That said, Xwayland will likely keep being around for the foreseeable future.
Out of curiosity, do you use Xorg and if yes, what’s keeping you from using Wayland?
@wer2@Chewy7324 exactly the same here. I too daily drive XFCE, never really change my setup, and don't require anything special that wayland offers. My setup just works for the most part....
Those are all good reasons. XFCE aims to support Wayland with the next release, so if they choose to use an established compositor it shouldn’t be too buggy.
With XFCE porting their apps over the setup shouldn’t change much, unless you’re using Xorg specific tools.
Over the last few years most features I’d expect from a windowing system were added to Wayland, so I expect the drama to cool down. (I don’t even know what’s still missing (except accessibility), with VRR, tearing, DRM leasing (VR), and global hotkeys being done. It’s just apps like Discord that have to cave in under the pressure to fix their apps.)
Once everything works, there’s no point talking about it.
@Chewy7324@wer2 I'll happily use wayland once XFCE officially releases support. I'm sure there may be a few kinks to work out or whatever with the initial release, but that's to be expected....
@Chewy7324@GolfNovemberUniform I'd say as soon as screen readers work properly under Wayland, they could drop X11 builds. But they should definitely not do it before fixing that.
The actual implementation would be per desktop. The desktop draws to the screen and then the apps connect to the desktop. We already have a window capture XDG portal that is used by things like OBS. We could huild a simular portal for just text on the screen. We would just need some way of either recognizing text or even better some sort of image to text engine like what is in Firefox.
Not OP, but I use sunshine and moonlight for streaming my pc to various devices. Wayland forces me to use kms and I can’t turn the monitors off while I’m doing it. Someone was working on a pipewire backend, so hopefully that goes somewhere.
GreenWithEnvy is also a nuisance on Wayland while Nvidia Settings Panel doesn’t even work. I have a custom script just to control my fans on Wayland, but I’m eventually switching from Nvidia anyways, so it won’t matter for much longer.
The primary maintainer stepped down, but there has still been work done by other contributors. The primary problem is that the underlying library is reliant on x11. This is the same reason why nvidia-settings doesn’t have all of its features on wayland. Basically if nvidia’s on tool doesn’t work then there is no way that green with envy can either. There is an open merge request attempting to switch to a different library that Nvidia says they plan to move to eventually, but it is slow going.
Xclicker is a GUI autoclicker. I heard of a command line tool for Wayland, but it didn’t seem to exactly be an autoclicker, and I don’t really like command line tools in general.
Oh I absolutely get it. But I guess someone will eventually end up making a GUI for ydotool (or so I hope). Alternatively, there is this (Wayland support is WIP): github.com/RMPR/atbswp
When I say I get it, I mean there was a time I kept Xorg around only so I can use PyAutoGUI (I no longer need it but if I did, I’d have probably created wrapper scripts to allow PyAutoGUI to call grim instead of scrot when on Wayland, or something like that).
I switched to Wayland after GNOME 46 release because it fixed the issues I had with it (artifacts and persistent display failures). Many people may still prefer X11 at least because of the lack of input latency on slow machines.
Chances are at some point it will be removed as it requires valuable man hours to maintain. At some point it will be a massive hindrance. I don’t think it will be removed for a while but it probably will be forgotten about.
I typically run fedora kde, both server and desktop. I’ve a laptop using hyprland which is great once you remember all the shortcuts you’ve setup, but fedora kde is worth its weight.
I disagree… The problem actually is that Wayland is optional, and still is.
So everyone was dragging their heels (and some still are). If all the major distro’s set a cut off date, then things would speed up. The biggest reason for delay was Nvidia imho, so now that they’re sorted, it seems things are falling into place faster.
X11 still hasn’t solved any of their real issues, and its still a security nightmare (which can’t be fixed). Furthermore, most of the developers have moved off it.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.