KDE Neon

Lightly half works for me on Plasma 6 following instructions on the qt6 version on GitHub. The window decorations and Lightly-related aspects of the plasma theme work, but I can’t apply the application style.

There is a fedora, couldn’t tell you what the distro is, though.

Still a better idea than the clunky pokemon trainer-like house Lord mechanic people were suggesting just before he was announced.

I’m a pretty satisfied Kontact user right now. I appreciate the integration of everything, but the one thing I would really look at improving is the RAM usage of Akonadi server, it eats up quite a lot of RAM for a program/backend meant just to integrate that information. Are there plans to improve that, or will Merkuro improve on that at all?

Sounds like it’s gonna be real cool. When does it hit the Neon User repos?

IIRC there’s a workaround that involves symlinks and/or copying some json files into the Firefox folder under .var, but I don’t quite remember how it works.

I solved the issues yesterday by building from source, which solved the crashing issue (guessing a packaging issue with the .deb version is one problem) and then after one restart of the app I was able to add my library. Works fine now.

I found that all I needed to do to add a library was close the app and reopen after the first time opening the version built from source. Built myself a layout similar to the Obsidian preset. Really nice customizable player! I have two recommendations: have some way for the Library Filter widget to show individual tracks so you can add them to a playlist, and have some way to actually view and edit the Playback Queue. Other than that, this is a great player!

Using an Ubuntu (22.04) based distro, I tried installing with the jammy .deb a couple times, which produced the constantly crashing result. I just built from source, which appears to have resolved the constant crashes, but I still can’t add a library.

I tried it out. I like the idea of the fully customizable UI. I can’t seem to get it to import anything as a library and it constantly crashes after roughly 5-10 minutes, though. Am I missing something or doing something wrong, or is that the expected behavior at this point in development?

Well, your guess was closer, we did get the Robins, but as separate units, with the odd choice of making Chrom the duo backpack.

We’re definitely getting kid Chrom, but trying to think who the other kid would be. Not guessing Robin because they don’t meet Robin until adulthood. We just got a Cordelia (as a duo backpack but still counts), so very likely not her. I could see a young Emmeryn to round out the royal siblings, and/or Sumia. Could maybe also see a Sully/Stahl duo?

I lean center-right myself (and yet somehow continue to use Lemmy) and still marvel at the complete lunacy of conspiracy theories about him that right-wingers can dream up.

I honestly have not had any issues in the past year using Neon, except this updating to 6.0. I’ve gotten everything working on it now aside from Discover, and it’s quite good. I just shouldn’t have had to spend all that time fixing it up on KDE’s own released system when it works great upon updating pretty much everywhere else.

A smooth release, which the KDE devs should be legit very proud of… except for your own flagship system, Neon. What happened there???

Full disclosure, I’m a Neon user who updated to a black screen and had to spend hours digging up fixes, and I’m the one who reported the issue with Discover on Neon that still isn’t fixed.

EDIT: Also, when running pkcon yesterday to install all the updates, it hit a fatal error after a few seconds due to the updates not installing in the proper order so one package ran into a dependency problem because another hadn’t updated yet. Ran update again, only that package that was the cause of the dependency problem showed up to update. After that, running pkcon, apt and checking in Muon, nothjng comes up. So I have no idea whether everything actually updated. And I can’t find the list of packages that were in the update anywhere to check.

Nice lineup. I mainly use these manuals for merges, and there’s lots of good ones to get for that here.

It would really be nice to have a greater variety of hardware options available for those of us who don’t want to be forced into Android or iOS here in the US and Canada. From what I understand, our lack of options is due to a variety of factors: business deals locking phones to a particular OS and/or carrier and locking down the bootloader, American phone models using CPUs that just can’t have the OS changed, and most alternative OS’es and open hardware models/standards being primarily developed in Europe and therefore focusing on the European market over North America, as well as others. It means we’re virtually stuck with the Google Pixel here, which is essentially paying Google to not have to use Google’s OS, which leaves a bad taste in my mouth. I’m using one of the very few non-Pixel options with /e/OS, the Murena One, but it leads to another problem, the non-Pixel options having very limited options for carriers because most carriers don’t know them so won’t touch them.

YES I UNDERSTAND THAT. I feel you’re not reading me right here. You’re getting hung up on the literal sense of the word “embedded” when I am just using it to relate it to the OP’s concerns.

Yes, I know that or else Plasma wouldn’t work for most people. What I mean is that it’s so “far embedded” in the sense that it uses an outsized amount of resources to do what it does compared to the rest of Plasma when it is installed, mainly for the sake of integration with those other parts of Plasma. But as far as I’m aware, KMail and other Kontact programs depend on it so you can’t remove it and have them work. Which is Kontact’s big problem, IMO. Way too taxing on the system for too little functionality at the end of the day.