like most apps on Linux, kde connect was never exclusive to any desktop. you don’t need gsconnect.

The Steam Deck works well if you have a particularly twisted definition of “working well”. SteamOS is certainly among the worst Linux distros I’ve used. It is certainly significantly worse than the average desktop-oriented distro. Sure, Valve has done good work with Proton, but basically every other piece of their stack is broken in some way.

Just a couple of days ago I had an issue where after the battery died and I plugged my Steam Deck into the charger, it simply failed to turn on. The fans would start spinning and that’s it. Nothing else worked. I could not get into the BIOS menu. I could not get into the recovery menu. The solution? Unplug the Deck, let the battery die from spinning fans and plug it back in, hoping that time it’ll turn on. Spinning fans take a long time to drain the battery, so this took me a couple of hours even though I’d only been plugged in for about ten minutes. I am not the first to deal with this issue. You can see posts online about it more than a year old. Those posts are how I was even able to figure out the solution.

I will never understand why SteamOS gets any kind of praise. This kind of issue is unacceptable. Any non-tech-savvy user will assume their device got bricked. I’ve seen several people mention they did RMA over this. And despite being a critical failure known for over a year, it hasn’t been fixed.

If you’re not a techy, SteamOS is garbage. It is ridiculously unpolished and keeps breaking in ways that can be difficult to fix. Every update (especially the client updates) has a 50/50 chance of breaking something, even on the stable update channel. You have to switch to desktop mode just to use a web browser. In fact, you have the switch to desktop mode for a lot of things, because gaming mode doesn’t let you do things like adding non-Steam games, install Flatpak applications or use a file manager. But desktop mode is entirely unsuited for gamepad controls and the on-screen keyboard feels particularly sluggish (though it can also get sluggish in gaming mode, just not as often).

If you’re a techy, SteamOS is also garbage. It is still ridiculously unpolished and the immutability is implemented in such a way that completely neuters the whole OS as anything you change gets wiped on every update (you can’t layer). There are hacks to do most things from gaming mode. You can run Firefox with some kind of weird setup where you run it inside a nested KWin session, because Gamescope is completely incapable of handling multiple windows, which would normally break all of the context menus and the hamburger menu in Firefox. Similar deal with Dolphin for file management. You can even run the entire Plasma desktop nested inside Gamescope, albeit with some caveats. Still need to switch to Desktop Mode to add non-Steam games tho, since you can’t run the desktop Steam Client from Nested Desktop. Things break occasionally, but it’s manageable. Figuring out all of these workarounds is quite time consuming though. This would not be the case if SteamOS was actually a good distro.

I am not. Clementine is not developed as part of KDE.

afaik they’re all dock widgets, meaning they can all be hidden, moved and resized at will. you can even split them off into their own windows if you want

Amarok, Elisa and JuK. That’s three, which is a lot, but it’s not entirely uncommon for KDE to have three (or more) applications with a similar purpose.

The problem with gaming mode is how quickly it falls appart the moment you try to use it for something other than gaming. Something as simple as having more than one window is impossible under Gamescope. That’s pretty problematic when a toolkit decides to implement something as a stealth window, like GTK context menus. Qt doesn’t do this as much as GTK does so using Qt applications isn’t as problematic, but it’s still a pain. For instance, you’re extracting a file with Dolphin and a pop up window shows up to report progress, making you completely unable to access the main Dolphin window until the operation has been completed.

The best part is that SteamOS displays a little “Switch Windows” section under the “Exit game” button when you have multiple windows opened, which literally just doesn’t work and as far as I can tell never has. The only thing that menu does is show you the names of the opened windows and let you close them by pressing X. Switching windows, the thing the section is literally named after, doesn’t work and never has since I got a Steam Deck last year. You select a window, it gets highlighted in the menu and that’s it. Nothing else happens. It doesn’t switch focus or switch the window displayed by Gamescope, it does nothing.

Another thing that’s often problematic is that you can’t maximize windows. Say your app decides to open itself windowed, Gamescope is just going to blow that 480x360 window up to full screen and makes zero attempt to actually resize the window to fit the screen, so you’re stuck with a very blurry and zoomed-in window. The maximize button in apps with CSD does nothing, but other built-in means of resizing windows or achieving full screen do often work. But these built-in means often don’t exist, because applications expect to be running on a window manager that’s actually capable of managing windows.

And then there’s just all kinds of bugs. Say you open a game with a certain aspect ratio/resolution while also having apps with a different aspect ration/resolution open, you’ll often find that when going back to your app you can’t move your mouse outside the boundaries of the window for the game you just opened. Another thing I’ve seen with many games is that the view often gets shrunk to a tiny square in the center of the screen. There’s a lot more, but I’m sick of ranting about gaming mode.

My personal take is that SteamOS’s Big Picture/Gaming Mode shell sucks balls. It’s impossible to make most desktop apps work well in Gaming mode without bending over backwards to work around the myriad of issues it has (for the ones that can even be worked around) and since it’s closed source there’s nothing you can do about it. Thus, the best solution would be to develop a new Gamepad-centric open source shell to replace it. I also think rather than repurposing Plasma Mobile applications like Angelfish it would be better to design new ones that are truly designed for gamepads. Perhaps Plasma Big Picture could be used as a starting point. But it would be a really big undertaking and there probably aren’t enough devs interested right now.

KDE3’s Plastik style was closer to XP’s Luna than Vista/7’s Aero. The default icon theme CrystalSVG had a colorful pastel and cartoonish style. There’s a full port of it to Plasma 5 here. It should still work fine in Plasma 6.

The Plasma 4 Oxygen style was much closer to the detailed realistic skeuomorphic style of Aero (though it was probably more so inspired by early OSX Aqua). It is still usable on Plasma 6 and packages for the theme should be available in your preferred distributions’ repositories.

Crystal Remix is really a mix of three icon themes designed by Everaldo Coelho in the 2000s. Only the first of these, the aforementioned CrystalSVG, was ever an official KDE theme. The second is Crystal Clear, the successor to CrystalSVG. It had a more detailed and realistic style compared to CrystalSVG, looking far closer to Aero. The third one is Crystal Project, the final iteration of Crystal. It went further into Crystal Clear’s direction and erased the last vestiges of CrystalSVG’s more cartoonish style. Crystal Project’s icons are particularly detailed and I’d consider it a really underappreciated piece of skeuomorphic icon design.

Personally, I’m not that big on Crystal Remix. I’d prefer either a complete CrystalSVG-styled icon theme or a complete Crystal Project-styled icon theme. Preferably the latter because the former already pretty much exists. The two styles don’t mesh together all that well, IMO. Crystal Remix’s coverage (especially for action icons) is also a bit lacking and it’s pretty common to run into unthemed Breeze icons in some applications.

Crystal Dock doesn’t strike me as particularly KDE3-ish. It’s basically nothing like KDE3’s Kicker, though there were a lot of popular third party docks in the KDE3 era like KoolDock, which were actually quite similar to this project. All of them are gone by now and there’s been a lot of demand for new third party docks since the death of Latte Dock. So I anticipate this project will make quite a few people happy.

Kontact is on Flathub, so it is definitely possible.

EDIT: Merkuro is apparently bundled with the Kontact Flatpak. Seems like they’re just shoving anything that uses Akonadi in that package. So on one hand, it seems there is a Merkuro Flatpak already. On the other hand, it’s bundled with a bunch of extra stuff you probably don’t need if you’re using Merkuro (like the entire Kontact suite), so you’re probably better off with distro packages.

Firefox and LibreOffice aren’t part of KDE, but Kate and Okular are. So the fact only the former two support this feature indicates it’s not from KDE. This should probably be supported by KDE though (or by Qt? perhaps this should be done on the toolkit level rather than on the application level). Holding ctrl to multi-select is standard behaviour in a lot of applications and is quite useful. For what it’s worth, Krita does support this, but you need to hold shift instead of ctrl.

seems they meant the accent color

deleted by creator

KDE is based in Germany, just like Mercedes and BMW. GNOME is based in the US, so they should instead get sponsored by General Motors or Ford to keep the rivalry going.

Breeze for iced and Cosmic for Qt. That’s the elephant in the room, I’d say. Another solution would be to attempt a common theming system for Qt and iced. Both solutions are particularly high effort, but it’s easily what’s going to have the most noticeable impact.

I assume the Cosmic people already know this, but it’s also important to make an effort to follow the usual cross-desktop standards, like the icon-theme-spec, icon-naming-spec, sound-theme-spec, org.freedesktop.appearance accent-color, org.freedesktop.appearance color-scheme or org.freedesktop.portal.FileChooser.

It would also be nice to support a few unofficial standards KDE uses, like appmenus.

For some reason this got me wondering what the anti-default Plasma install would be like, with every single option set to a non-default value.

My opinion is that this instance is too small for it to be worth it. We already have other communities and they are very inactive. The Krita and LabPlot communities barely see any activity and they’re some of KDE’s biggest applications. The KDE Edu and Akademy communities are even deader. Even by combining everything else into one community this instance isn’t exactly busting with activity, so best not divide things further. It’s already seeing fierce competition from the more official KDE Discuss (and the Krita Discuss) and the more popular KDE subreddit (and the Kdenlive and Krita subreddits).

Work on a KF5 release had already started years ago and was mostly completed. With the recent revival of the project, it made sense to take things one step at a time and complete the KF5 port first.

Yes. Arch does not support partial upgrades. Always update every package. You can try to delete it, but you might still have a package that depends on it if you have an application that hasn’t yet made the move to Qt6. Also, using Discover for package management on Arch-based distros is not recommended. Discover uses PackageKit for distro packages and its use is discouraged by Arch due to a number of issues.

right, spellcheck didn’t catch it since both is also a word. already caught and edited, tho.

mpc-qt is also pretty good

they don’t seem analog tho