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?
@Jessica it was explicitly stated when those features were introduced, that they're meant to be building blocks for a later real tiling implementation either within #kwin or 3rd party extensions.
I've got udev rules that trigger a shell script when I turn the mouse off/on. That's the first part!
Still haven't been able to find a way to use libinput, kcfg (Python CLI for modifying KDE settings), probably something else to disable the touchpad or stop processing its events.
Listen, I love #fedora. Bar none it's one of the best distros out there, but more than that it's been the stomping grounds for #linux#desktop innovation. Don't believe me? You've got #Wayland, #PipeWire, contributions to #xdg, to the Linux kernel proper, etc. Fedora is more than a distro, it's a #comunity of people who wish to push the envelope.
That's why I am for #plasma becoming the new workstation standard, because of the good it did #GNOME. Let me explain...
If I were to give a review of the #kde#plasma desktop, I'd give it a few honourable mentions because of the effort put in - but I found myself a bit disappointed.
It's probably a problem of release cadence and steering the unyielding man-of-war that is the Plasma stack, which most likely made #Wayland integration into #kwin a challange and a half.
But for me, the whole Plasma paradigm needs to be rethought because usability wise it's showing it's age. This did not "feel" like a milestone.
So, since KDE is planning to abandon X11 one day² and Wayland feels sluggish on my 2013 laptop, I've been looking for alternatives which fully embrace X11.
And now I'm really REALLY itching to try out Xfce4 with that Windows XP total conversion pack¹.
That, or I just wait for the Wayland implementation of Plasma/KWin to get optimised. They are working on it, apparently.
Very good... #kwin, the thing which comes with KDE Plasma by default, is a surprisingly solid & easy to use window manager
Managed to reproduce most of my useful hotkeys from sway/river into kwin fairly easily. Which of course... is quite useful for a laptop, since I don't often have a mouse with me
Apparently, when saving an image with Firefox running under KWin / Wayland, I am supposed to enter the filename into the window decoration (aka title bar) now.
I stand by my opinion: Client-side window decorations are a bad idea for two major reasons: They add inconsistency and make it more inconvenient to kill frozen graphical applications.
Regarding inconsistency: Other applications on my systems have a close button at the top right, drawn by the window manager. When my muscle memory guides me to click that button, I expect the application to be closed or the current dialog to be cancelled. Here I have the save button, doing quite the opposite of cancelling the current action. Apart from that, it looks completely different from every other window decoration – not to say it looks uglier either.
Regarding killing frozen applications: KWin has this nice feature to pop up a dialog asking users whether they want to kill the application, when they click on the close button and the application does not respond. This obviously cannot work with client side decorations. While that's just an inconvenience to me, it might be a bigger problem for novice users.
@realkrzysiek Uruchomiłem specjalnie #Midori, które samo z siebie nie zagospodarowuje wydajnie paska tytułu, by pokazać ci standardowe menu okna i podstawowe opcje w #KDE#Neon. Tutaj sesja #Wayland, #KWin, #Plasma. KDE Neon to "pseudodystrybucja" od twórców KDE, sztandarowa, oparta o Ubuntu. Są wersje stabilne i deweloperskie. Używam od lat bo potrzebuję czegoś co po prostu działa, do pracy. Lekki jak LXQt, szybki, bardzo dużo "skórek" wyglądu, świetna, zunifikowana integracja z Gtk / Gnome.
I wrote about all the porting work done recently for Plasma in yesterday’s Plasma 6 update. That work consumed a lot of time due to a big push to get it all done, so this week there...
I've pretty much got my #NixOS setup figured out now.
Post-config, I'm still such a fan of how it works. I tend to impulsively install a ton of packages that I often forget about, so NixOS is fantastic for making me stop and think about what I'm doing, not to mention having an easy access, always-up-to-date record of my previous decisions.
#KDEPlasma is a first-rate DE that looks and works amazingly.
And system backup is so unbelievably effortless now, so that's pretty awesome too.
The only thing that I'm not totally acclimatized to already is #Bismuth for #KWin but I'm learning.
I ran into a weird issue where the settings were showing up but the shortcuts weren't, but it started working after a proper restart or two, so we're off to the races now.
Now I just have to learn all of the available functions and memorize the shortcuts, and then I'll be good to go :P
After solely using stacking window managers like #KWin for years, self-introspection led me to realize that I only ever open applications full screen or split screen. I am therefore embarking on a journey into #TilingWM window managers; wish me luck.
Still haven't looked at notifications, but just FYI, I found out you can use #Kwin rules to force new #konsole windows to be 80x25 (assuming you don't change the font/size)
That solves my last gripe with konsole & #Wayland. (Still at least one minor gripe with Wayland, but I'm sure they'll squash the bugs eventually.
This week in KDE: porting, Dolphin, and KWin (pointieststick.com)
I wrote about all the porting work done recently for Plasma in yesterday’s Plasma 6 update. That work consumed a lot of time due to a big push to get it all done, so this week there...