m5l.eu is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
Linux-Desktopumgebung mit Update: KDE Plasma 6.8 mit Audio bei Bildschirmaufnahmen und mehr https://www.computerbase.de/news/betriebssysteme/linux-desktopumgebung-mit-update-kde-plasma-6-8-mit-audio-bei-bildschirmaufnahmen-und-mehr.98351/ #kde #plasma6 #linux #desktop #opensource #update
Ich benutze auf meinem privaten Notebook CachyOS als #Linux Desktop mit #KDE und bin damit sehr zufrieden. Die letzten 2 Jahre gab es trotz Rolling Updates keine Probleme. Auch habe ich die Festplattenverschluesselung aktiviert. Spiele laufen mittels Steam hervorragend.
Aber welches OS und welche #GUI wuerdet Ihr fuer den #Business Desktop PC empfehlen? Derzeit habe ich Tuxedo OS drauf, weil es stabil und ohne Probleme laeuft. Da ich beruflich Linux verwenden darf, wuerde mich Eure Meinung interessieren.
this KDE security advisory (from 2020) is hilarious: https://kde.org/info/security/advisory-20201002-1.txt
Workaround: stop kdeconnectd. but, you can't do that because it's started from dbus, so it's literally impossible to stop. the only solution is to remove the package, but good luck doing that when it's part of your OS's KDE metapackage.
what is this super important daemon that must be running 100% of the time and cannot be stopped or removed? well, it lets you control your desktop PC from your phone. something which i'm sure at least 0.001% of KDE users have ever done, or ever will do...
what the fuck are you doing, software developers.
I know that the answer here is complex, and I haven't found an answer that actually works for me. I'm on a laptop, and use a secondary monitor as my primary. Whenever I have both the laptop screen and the secondary monitor active, there is a massive performance drop. I've tried attempting to make the laptop screen use the UHD graphics and the HDMI connected laptop use the separate GPUs (I don't think it worked, and don't remember what I tried). Is this something that just can't be overcome? I can give more details/logs if needed. #archlinux #garudalinux #kde #wayland
Interesting on my ancient Dell Laptop the Mastodon Instance seems to trigger a bug in falkon-qt6 on GhostBSD.
Scrolling the page locks the box up and after short while screen turns black for a second or two and gets back responsible back then, so you can click on the close button to close falkon. If you don't it turns black again, rinse and repeat.
falkon-qt6 does work fine on another machine with GhostBSD and it wasn't nothing like that before, so it must have been a recent deprecation.
Tried downgrading drm-kmod but to no avail, geckobased and blinkbased works, so switching now to ungoogled-chromium now.
---
/e1: FYI, tested with xlibre, same bug
/e2: turning on/off hw accell, same bug
/e3: dooble (also qtwebengine) triggers the same bug... It is a bit more verbose and utters something about "context lost via EXT_robustness. Reset status = GL_GUILTY_CONTEXT_RESET_KHR" and later "context lost during make current" in all sorts of parts of chromium.
/e4: et tu "qutebrowser" and qutebrowser-qt5: Same bug, same error msgs in qtwebengine as dooble.
/workaround: export "QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu" enviroment variable
---
Wait.. I *did* disable hw accel tick box in the browser. Oh, let me guess: "it's just the browser that doesn't use hw accel now, nobody spoke of mOdErN qtwebengine, eh!?!"
Anyway, this fixed it for me.
Now, off to work... later shift.
#runbsd #browser #webengine #gpu #oldhardware #drm #freebsd #ghostbsd #qt #falkon #kde
Trying FreeBSD as a Linux user – Kenvexity – YouTube
https://www.youtube.com/watch?v=bdUwCQttWKM&t=25s
I enjoyed this video. Very down-to-earth.
Some key points at <https://www.reddit.com/r/freebsd/comments/1ubn8mp/trying_freebsd_as_a_linux_user_kenvexity/>.
#FreeBSD #KDE #Plasma #Xorg #TWM #graphics #hardware #Firefox #Linuxulator #Steam
I have bit of a problem with getting SDDM to start a Plasma session under Wayland on FreeBSD 15.1.
I've installed KDE Plasma using "kde-installer-dialogs" from alfix (link below). After rebooting, the SDDM greeter shows up as expected, but entering my credentials just returns me to the greeter.
Disabling SDDM, and manually starting a session with "% exec dbus-launch ck-launch-session startplasma-wayland" works fine.
Any ideas?
Excerpt from /var/log/sddm.log:
[17:55:08.941] (II) DAEMON: Greeter starting...
[17:55:08.942] (II) DAEMON: Greeter stopping...
[17:55:08.942] (WW) DAEMON: Error from greeter session: "Process crashed"
[17:55:08.942] (WW) DAEMON: Auth: sddm-helper (--socket /tmp/sddm-auth-0646d0ea-c7ba-4fac-99d1-69f703416d2c --id 6 --start /usr/local/bin/sddm-greeter-qt6 --socket /tmp/sddm-:0-ikHaiz --theme /usr/local/share/sddm/themes/breeze --user sddm --greeter) crashed (exit code 1)
[17:55:08.942] (WW) DAEMON: Error from greeter session: "Process crashed"
[17:55:08.942] (WW) DAEMON: Auth: sddm-helper exited with 9
[17:55:08.942] (II) DAEMON: Greeter stopped. SDDM::Auth::HelperExitStatus(9)
[17:55:08.963] (II) HELPER: [PAM] Starting...
[17:55:08.963] (II) HELPER: [PAM] Authenticating...
[17:55:08.963] (II) HELPER: [PAM] returning.
[17:55:08.963] (II) HELPER: Writing cookie to "/tmp/xauth_pDPLBN"
[17:55:08.963] (II) HELPER: Starting X11 session: "" "/usr/local/bin/sddm-greeter-qt6 --socket /tmp/sddm-:0-FSIfCO --theme /usr/local/share/sddm/themes/breeze"
[17:55:08.965] (II) DAEMON: Greeter session started successfully
[17:55:09.013] (II) DAEMON: Message received from greeter: Connect
[18:07:19.151] (WW) DAEMON: Signal received: SIGTERM
[18:07:19.152] (II) DAEMON: Greeter stopping...
Anyone know why using sftp with Dolphin in Plasma is so slow in Alpine Linux?
Using Debian, doing the same thing is like greased lightning.
It's not network, ssh/scp/rsync/sftp command line works wicked fast between hosts with Alpine.
Something about Alpine and Plasma it seems. This has been an on-going thing.
Anyone know a workaround, beside using a different protocol I mean? This should "just work" like on other distros.
#Linux #AlpineLinux #Alpine #Plasma #KDE #KDEPlasma #Dolphin #sftp
KDE Plasma 6.7 Beta arrives with Plasma Bigscreen, new Union theme system https://www.gamingonlinux.com/2026/05/kde-plasma-6-7-beta-arrives-with-plasma-bigscreen-new-union-theme-system/
Until now I've never bothered to look into the internals of keyboard software support and whatnot, but for a long time I somehow put up with #Alpine #Linux (or maybe it was a #KDE / #Wayland issue?) not enabling by default key repeat - or however you call holding a button and have it register as continuous holding instead of a single press.
Lo and behold, on #OpenBSD that just works. On the other hand, changing the language on my keyboard when using cwm instead of something like KDE?...
setxkbmap -layout ro does not output an error, but still doesn't mean it actually switched me to Romanian (however, something like French actually just works). wsconsctl keyboard.encoding=ro outputs the error that ro is not a valid encoding. According to the documentation, encodings are apparently listed in /usr/include/dev/wscons/wsksymdef.h - and indeed, there seems to be no "ro" in there. Changing locale didn't seem to help either.
Then I took a deep dive into the man page of wsconsctl(8). There it says: "The current mapping can be printed with wsconsctl keyboard.map. The value for each keycode specifies the keysym that is output when each of Key, Shift + Key, AltGr + Key, or Shift + AltGr + Key is pressed" A magic thing then happens... I test wsconsctl keyboard.map+="keycode 15 = l L at" - afterwards, I see in the keyboard mapping "l L at at"; the output is a Polish l=L with slash. I decide to test AltGr with every other key on my keyboard... I burst into laughter when I realized that I do have now Romanian characters: they were hidden with AltGr. I can't seem to spot them in keyboard.map, where according to the documentation all keysyms should be specified. Maybe setxbkmap did the magic on top? At least I am grateful I can type ăâșîț and not have to copy paste the characters.
I'm running Plasma 6.6 on a box and I'm kind of struggling with the lack of adjustable window outline intensity. I really miss this... whined about it elsewhere.
Examples attached of with and without and where to set it in pre-6.6 and 6.6.
Anyone know how to get this setting back, either via command line or smoke signal or whatever?
A tool that doesn't get enough love is the KDE "ISO Image Writer".
Sure there's dd and there's tools like Rufus, Etcher, and whatnot, but if it's effectively a tool meant for your platform then why not?
[ Currently writing Alpine v3.23 to a stick to wipe/replace my garage 'droid from Debian to Alpine after work ]
#KDE #KDEPlasma #Plasma #AlpineLinux #iso #iso9660 #USBStick
More monkeying around with OpenBSD. I spent a bunch of time getting LXQt working but the themeing was taking too much time so I threw more ram at the VM and installed KDE. The goal was to learn about OpenBSD, not LXQT. Ha.
Lots of the standard apps are there in OpenBSD but I need to find out how to get Librewolf and Waterfox going. Having done zero research, I'm assuming I need to compile from source.
I saw an article out using "Molly" as an alternate Signal Messenger client (xn--gckvb8fzb.com/if-you-must-use-signal-use-molly/). May try it in the future.
The KDE Plasma version is 6.4.5. IIRC KDE is stopping X11 support so I will need to figure out something else I guess. I've seen threads about Wayland on OpenBSD but didn't go down the rabbit hole yet. What little I read implied not ready for prime time.
The VM feels pretty snappy even though the QEMU agent doesn't really help with video options. This is using the VGA driver setup to get a decent resolution.
I really need to get this Jeep back on the road. I miss it.
#OpenBSD #KDE #KDEPlasma #LXQt #VM #QEMU #Librewolf #Waterfox #X11 #Wayland #Signal
Plasma: high CPU usage whilst the screen is locked
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293820>
Can anyone suggest a workaround?