It's a good thing that KDE 6 is coming out soon because holy cow, that's a big secondary version number.
ipacialsection
joined 2 years ago
I remember when gitlab.com was the most accessible alternative to GitHub out there, but it seems they're only interested in internal enterprise usage now. Their main page was already completely unreadable to someone not versed in enterprise tech marketing lingo, and now this.
Thankfully Gitea and Forgejo have gotten better in the meantime, with Codeberg as a flagship instance of the latter.
Debian needs a better installer. It'd be awesome if it had something more akin to Fedora/RHEL's Anaconda, or even just made Calamares the default (so long as it didn't install every single locale available like their live inages currently do).
Looking online, there are some suggestions to either (re)install xapp:
sudo apt install --reinstall xapp
or a related library:
sudo apt install --reinstall gir1.2-xapp-1.0
However, usually I find that errors like this mean nothing, so I wouldn't be surprised if these steps change nothing.
Definitely flatpak related then. Try running one of your flatpak apps from the terminal, and post the output here; might help pinpoint the issue. You can list the ones you have installed with flatpak list, then flatpak run .
/dev/nvme0 is probably your SSD. But if it passed you probably have nothing to worry about
It still sounds to me like something's up with the disk. Can't think of any solutions to suggest but I would run a SMART health check on it:
sudo apt install smartmontools
sudo smartctl -a /dev/sda
If you prefer a graphical tool, you can do the same thing with GNOME Disks, which also has options for disk benchmarking.
In the resulting report, the overall health state should be "PASSED", the "Type" column should show "Pre-fail" and "Old age" values, and the "Media-Wearout-Indicator" should be close to 100. If the overall health state is "FAILED", then you will want to back up your files immediately and consider getting a new SSD.
GNOME and Plasma are so far separated that a merger would be impossible, without either eliminating one of the two or completely rewriting both, and I think they cover different niches. GNOME is for people who want a tightly integrated experience, and KDE is for people who want to customize their system. (I would also argue that it's not possible for there to be only one distro or DE, so long as all the components are open-source. Savvy users will always make their own stuff if they're allowed to.)
There's already plenty of cooperation between GNOME and KDE devs on common standards, support for each other's apps, etc. I hope this continues, and makes both desktops better. A lot of behind-the-scenes stuff, like Wayland extensions, could definitely become shared between the two desktops.
You can start anywhere you want! I often recommend starting with Star Trek: The Next Generation, since it's aged a little better than the original series. You might prefer to jump ahead to season 2 or 3 to get to the really good stuff, but even season 1 is worth watching.
Up until Enterprise season 3 it's pretty much all episodic (or in DS9's case, mostly episodic with a subset of the episodes forming a series-long story arc), so you can pick a random episode or movie with a cool-sounding description and start there if you want. That's how I got into Trek, just picking random TNG and Voyager episodes.
I'd say it started at a 6 or 7, and grew to a strong 8 over its runtime. Most of the characters have always been beautifully nuanced, but the stakes of its plots have always been unnecessarily inflated, and the endings for each story arc are of very mixed quality. After the jump to the 31st century, the storylines became much more Star Trek-ian, and the show started to display more of its own identity separate from classic Trek and action movie tropes, and that pushed it into properly great territory.
And because of that, custom configurations are wonderfully easy to make, technical issues are rare, and the few issues you do experience are quite possible to solve. Which is why I settled on Debian.