Wayland does not work properly on Nvidia Hardware: It keeps on getting closer but is not there yet, or so I’ve heard. Apparently, the issue is with the proprietary drivers, as noveau works well. But I use AMD, so I’m only working off rumours and opinions here.
Posting this from Hyprland on NVIDIA, arch (btw) and the nvidia-open-dkms driver, but yes, NVIDIA isn’t fully there yet.
I keep reading this all the time but I have the same setup and I don’t understand what’s supposedly wrong or broken with it. It just seems to work fine. What am I missing here?
Same here. being subscribed to unixporn community, hyprland always makes me wanna try it. but everytime i did, i just couldn’t make it as my norm. Then i return to my good old Gnome.
(what sereral months of DE/WM hopping made me realize was i am not good at using WM’s. The only one i used atleast few months was openbox in archcraft )
I made a quick plugin to also run stuff from path, and am currently working on a proper ssh plugin for that - extending them is a bit more involved than the simple rofi/wofi scripts, but there’s a lot more things an anyrun plugin can do.
@theshatterstone54@buzz The rumors are real. I've tested Wayland on several distros on several machines and it has always been a disaster. On Debian Bookworm KDE on a FRESH install, the first thing I did was open the Discover app and it crashed. Every time I opened it the compositor took a dump.
Wayland is garbage and its apologists have an agenda. Their agenda does not include working software.
My first ever distro was EndeavourOS. I installed it when I was 13 or 14 years old because someone on reddit said it’s customizable. I never felt like I need to switch to anything else.
While I’ve looked into Fedora Silverblue, that distro is limited to only install Flatpaks, which is fine for “apps”, but seems to be more of a problem with managing system- and CLI tools.
No. Your understanding to Fedora Silverblue is wrong. I can just run rpm-ostree install package.name in Silverblue, like other Fedora spins. The small disadvantage is that I need to reboot to apply this update. (re-construct)
but doesn’t that result in new A/B snapshots, or something like that?
Well, you can call it snapshots, but there is no need to think about it. In most cases, the system points to the newest snapshot (deployment 0). If a rollback is needed, I can pin to the older deployments. When a major change is to be applied (Like bump Fedora version), I’d manually mark the current deployment as dont-auto-delete.
Sure, but I’d like to have a more seamless experience, i.e. not having to open/start any “containers” or something like that.
I never used toolbox in my Fedora Silverblue system. I feel that I can’t tell the difference between using Silverblue and the default Fedora spin
It depends on if the changes needs it or not. You can set a reboot flag on a given task and at the end the system will reboot, but if no reboot is needed then it will just make the change live.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.