#wayland on #OpenBSD seems to be pretty damn solid. I ported my #sway configure over after installing a handful of apps and it just damn works. Though I can not find a wayland native terminal emulator in the repos but just getting started here. I just need to compile #waybar and hope it works than I'm all set!
I'd actually prefer a spin built on @YaLTeR's niri compositor (https://github.com/YaLTeR/niri). It's a similarly young project, but it seems much cooler and original.
So I wanted to give Fallout 2 a go on my media center PC. I was messing around with Wine and 32-bit vs 64-bit weirdness until I discovered Fallout 2 Community Edition which simply works on Linux flawlessly. It even supports Wayland if you specify SDL_VIDEO_DRIVER=wayland. I'm amazed at how many of these community driven source ports and reimplementations exist. I should make a website about these. :drgn_flat_happy:
Today I updated to #Fedora#KDE 40 using dnf. After I log into my main user, I get a black screen (and Discord, which opens automatically). I’ve had this issue before. I’m using a Radeon card, so it’s not that Nvidia issue. And most importantly, the desktop does work with a brand new user, which means it’s something in the user configuration. In journalctl, qt.qpa.wayland: Wayland does not support QWindow:requestActivate() is a recurring error. Is this enough info? Thanks.
Nvm, that's the #X11 variable. The relevant variable here is $WAYLAND_DISPLAY, which is set by default to wayland_1. Anybody has any idea? Or can it be that nobody cares about my problems?
Upgrading broke things in some surprising ways. Most (not all) icons are gone in my Plasma panels now. It's a good excuse for me to finally play with #sway and go full #wayland though, which has been excellent 😁. I suspect it's my config that broke as opposed to some flaw in the new release (or maybe both?).
Thanks to everyone on these projects for your hard work. You're making a difference and pushing open source forward!
Oh damn, caught a nasty one. Was trying to use chromium for something but audio was not playing at all, no errors, just clicking play on things like r-a-d.io gave a "fuck you"...
Was checking if it was wayland or something like that that broke it... (And no, it doesn't open in #wayland, transparent window with the beautiful mouse dragging effect on the screen), but it was nothing related to it...
It seems that the problem was the #plasma integration extension that hijacks things and broke!!
A customer of mine is looking for a #Wayland expert to contract, related to frame capture as part of a streaming stack. Let me know if you or someone you know would be a good fit!
Und das ohne Probleme! Höchstwerte der Team-Einheiten auf dem Feld: meldrian 1800, xilef 1000 und comrad 400. Die KI hielt mit zusammen knapp 600 Einheiten dagegen.
@nixCraft I've been using #vim for 20 years (now using #neovim ). It's still lean and mean when used "vanilla". However, if I enable the autocomplete, autocompile, auto spellcheck, treesitter, folding, etc. then it noticeably takes up CPU as I type. I don't mind paying some CPU for this...
But for eyecandy I really couldn't care less. Loved my keyboard only #fvwm setup. When I switched to #wayland I finally gave up fvwm for #kde . Happily, kde is lean and fast even with eye candy...