Been using #Deskflow with my #Debian #Linux #KDE #Plasma #Wayland box as the "server" and my #NetBSD #ctwm #X11 laptop as the "client" or second screen.

It's amazing that it works, but it's buggy. I'll get a few repeat keystrokes, and sometimes the control key gets stuck.

#DontHateTheHashtagPlayaHateTheHashtagGame

What's good for hardware is good for the budget … and environment! 🌻

LliureX #Linux with #KDEPlasma in Valencian schools saves the public administration *3.5 million euros a year* for 110,000 computers.

[1]* School HW has lifespan up to 18 years while running up-to-date software
[2]* Cheap easy-to-manage "light clients" ideal for very old upcycled HW
[3]* LliureX-Shutdowner saves energy by turning off unused computers school-wide

[4]@kde

#KDE #KDEEco #FreeSoftware #OpenSource #Valencia

Still playing osu! with ar11 random mirror mods.

Unlike most "gamers", I use 1366x768 60 Hz VGA monitor, btw. Never managed to buy some modern monitor with modern res cos monehhh, plus it still works.

I bought the main one with my own money and the second monitor, I just got it from my old workplace, lol.

Oh I also stopped using KDE. Wayland gets in the fucking way of me having fun when I have AR11, HP11, and OD11 set on osu!. The latency is noticeable. Feels like my mousepad is "well-oiled" when I'm in X11, Still love KDE tho but yeah..

#youtube: youtu.be/Hjal3Q-mYDA
#twitch: twitch.tv/reallylazybear

#linuxgaming #osulazer #rhythmgame #osu #osugame #opensource #eldenring #gaming #archlinux #cachyos #x11 #wayland #freesoftware #kde

This is my biggest pain point:

gitlab.freedesktop.org/spice/l…

#KDE #Wayland

what don't you like about Wayland?

I've been running it on all but one system and it's as good or bad as xorg in my experience. One system wont run KDE over Wayland - which bugs me. I've had issues with both, but can't say one is drastically better than the other at the moment.

#Debian #kde #XOrg #Wayland

ARGH

if you've been having your keyboard layout settings wiped on every login on KDE Wayland, it's apparently fcitx's fault

github.com/fcitx/fcitx5/issues…

and they're just... not agreeing to not do that? because they seem to think KDE's native input settings should be nuked and replaced with Only fcitx? guh

but you can go to input method settings, configure addons, Wayland, uncheck "allow overriding system XKB settings" (it's the only setting in there for us)

#linux #KDE

Ok, I think I've got this display card under control - or so it seems. It hasn't crashed since Wednesday.

I guess this is a combo AMD RDNA3 Navi23 and KDE Plasma (+ Wayland?) bug...

I backed out all my Linux kernel command line switches for AMD GPUs and it crashed to green screen in less than a half hour. So, re-adding them stopped that from happening.

... amdgpu.dcdebugmask=0x410 amdgpu.tmz=0 amdgpu.gpu_recovery=1 amdgpu.sg_display=0 ...

And then the cursor thing is fixed <?!> by adding

KWIN_FORCE_SW_CURSOR=1

Currently this is what is set:

`cat /proc/$(pidof kwin_wayland)/environ | tr '\0' '\n' | grep KWIN` :

KWIN_DRM_NO_AMS=1
KWIN_DRM_NO_DIRECT_SCANOUT=1
KWIN_FORCE_SW_CURSOR=1

From a user experience point of view I don't see any difference with that software cursor setting.

There's another wrinkle to this that might be a factor but I can't really test around it currently. This is a multi-head machine and one screen is connected via HDMI and one is DP.

Perhaps this wouldn't be a problem if both screens were connected via the same type of connector.

Both screens are set to the same refresh frequency. But, in the display control app one reads back at 60.00 Hz while the other is 60.000 Hz. Minor thing right? But in trying to make this work I've seen references to AMD GPU weirdness in multi-head configurations where the refresh rates were different between screens. Red herring perhaps.

Anyway, don't know if there are (or will be) any people trying to make a RX 5800 XT GPU behave under Linux but this seems to be what worked for me and my dual head setup. I'll update if anything changes.

#Linux #AMD #AMDGPU #KDE #KDEPlasma #Plasma #AlpineLinux #kwin #Wayland

This morning I did get #kde #plasma #wayland up and running, had first fight with #sddm , this for my old monitors had really big colour difference, one darker and a grey/yellow taint. So I thought one of the monitors was breaking down, I spent weeks to looks for what next and spent money on new monitors. I have the same issue, so I decided to switch #Xorg for wayland, sure the issue is till there... and gosh wayland ain't the best on handling sessions IMHO, as which VT seems to be a bit randomish, you are stuck with "Switch User" and gosh it's SLOW like hell and easy to make plasmashell to crash on a session you are switching to. sddm don't allow you to specify the VTs you want to use, not even which VT to start with.

Plasma had the nice feature where you could scale old #X11 applications that don't have built in scaling, but then it would affect all X11 applications, this should have been a Special Window/Application rule, then it had been a lot more useful. Enabling #HDR , it works just for one monitor.

When #plasmashell crashes when you try to switch back, the view port seems to change to something a lot smaller. I can't get #yakuake to appear (either it's for it's far outside the view port or shift-f12 don't work when plasmashell wyaland crashes (in Xorg it works and the view is still full resolution).

It feels like everyone nowadays only develops a single user experience, desktop manager that can't handle multiple session (darn I miss #KDM , best ever desktop manager), desktop environments just don't handle that they aren't active. Multi monitor setups is nowadays a lot more experimental than it was in the 1990's.

As my main issue didn't get solved, I will revert back to Xorg and get a bit more stability. Maybe there will come something better to replace wayland, once in the time I was enthusiastic about it, but with time I just think it's just been a waste of time which could have been spent on gutting out all the old in Xorg and add new features.

Peak Desktop Experience 🥺

#KDE

I guess I'll relegate this account into my solutions dump, like a scratch paper, so uhh starting now, I've found that sometimes the "portal" for selecting a window for screen sharing doesn't pop up on KDE sometimes when I'm using OBS

Running "systemctl --user restart pipewire.socket xdg-desktop-portal.service" fixes it. I use Arch, btw.

I might investigate this problem when it pops up again cos it happens randomly...

#archlinux #kde #wayland #linux #freesofware #opensource

The current version of #KDE on my machine (6.7) seems to be very buggy in terms of what happens when I try to add extra monitor(s) in the #Wayland version, whether it’s via #HDMI or #USB with #Displaylink. The screens go haywire and I can even get a terminal open. I’ve had to revert back to the #X11 version just as I’d got used to Wayland. I’m no fanboy of Wayland or X11 but when such a major breaking of the system happens, it forces my hand. Not good at all.

#Fedora #Linux #Desktop #KDE6_7

SonicDE Launches as a KDE-Based Desktop for X11 Holdouts

｢ The project’s main goal is to maintain compatibility with X.Org Server for as long as possible and to adopt new XLibre features when feasible. Plus, to serve those who still rely on a full X11 session and wish to retain that experience in a KDE-based environment ｣

linuxiac.com/sonicde-launches-…

#kde #x11 #sonicde #xlibre #opensource

SonicDE

We forked the #KDE Plasma Login Manager. It now runs on #X11, drops privileges after init, and supports #systemd-free too. We tested it on Artix Linux with OpenRC, CachyOS with systemd, and on the #FreeBSD-based GhostBSD. #SonicDE sonic-login-manager

x.com/SonicDesktop/status/2056…

Need to use an ‘input method’ for Japanese characters, but said ‘input method’ forces only a single keyboard layout on the system level, so I can no longer type Czech characters using Alt Gr on the Czech layout without first turning off the option that adds Esperanto characters to Alt Gr on the first system keyboard layout.

Incidentally, I can add another system keyboard layout in KDE, but it’s automatically deleted on startup. My solution would be to write a script which either turns the Esperanto characters on/off or adds a keyboard layout, but it seems like there is nothing like setxkbmap under Wayland, so my best option would be poking at KDE settings with severely underdocumented command-line tools.

Why does technology always have to turn ugly?

#lang_en #KDE #setxkbmap #technology #Wayland #X11

We live in the worst time where real people ask real questions in forums like stackexchange and nobody bothers to write an answer anymore, because it is so much easier to ask AI.
askubuntu.com/questions/154037…

While AI (Mistral) just hallucinated that there is an "advanced tab" in the KDE settings, where you can set the layout per device with a maximum of four keyboards.
Spoiler: there is no such thing.
#AI #kde #linux #Wayland #keyboard

Great #wayland is forcing me to buy a new keyboard as there's no support for custom shortcuts any more, and hasn't been for years under it, so unlikely to suddenly get sorted...

bugs.kde.org/show_bug.cgi?id=4…

#kde #accessibility #linux

just downgraded to 5.3.1, specifically, uh, "git 9069dbc".

not only i can open up the font dropdown menu, but also i can change the font of the text on the fly. tho it still feel finicky.

i can't change the font size in the paragraph tab, but i can in the character tab with or without selection.

#krita #kde #plasma

Has anyone able to change a font on #krita 6.0.1? Before, I couldn't open the dropdown menu. Now I can see my fonts, but cannot change the font of the text by selecting any of the fonts.

Operating System: #EndeavourOS
#KDE #Plasma Version: 6.6.4
KDE Frameworks Version: 6.25.0
#Qt Version: 6.11.0
Graphics Platform: #Wayland