Para_lyzed

The linked article does a great job explaining the process of creating a theme assuming you have the SVG files. If you are asking how to create SVG files, then just use any vector editor (like Inkscape, for instance). You can find plenty of tutorials on how to create vectors through online video tutorials.

Sorry for the late reply, I’m not on Lemmy often.

It seems that, according to a Reddit thread, the Nobara kernel should include support for ec_sys. What does the command modinfo ec_sys output? If it doesn’t return modinfo: ERROR: Module ec_sys not found., then you should just be able to enable it with sudo modprobe ec_sys and then enable it persistently across reboots with echo ec_sys | sudo tee -a /etc/modules

EDIT: Replaced output redirection with sudo tee in case you are not running the command as root.

I’m not really sure what it is you’re asking for here. As another commenter said, ps outputs a list of newline separated entries (using \n, the standard LF character). I even ran some sanity checks to make sure it wasn’t using \r\n (CR LF) with the following:

$ ps aux | grep $USER | tr -cd "\n" | wc -m
14
$ ps aux | grep $USER | tr -cd "\r" | wc -m
0

The output of ps aux | grep $USER is consistent with the formatting of ps aux. I also found that ps aux | grep $USER was consistent with ps -fp $(pgrep -d, -u $USER) except that ps -fp $(pgrep -d, -u $USER) shows the header (UID PID PPID C STIME TTY TIME CMD), does not show the processes related to the command (entries of ps aux and grep --color=auto $USER), and does not show grep’s keyword matching by highlighting all matches within a line. It is otherwise completely identical.

Can you provide the output that you are getting that is unsatisfactory to you? I don’t think I can otherwise understand where the issue is.

Can you paste the output of the build so we can see what specific package it is missing? Qt is not a single package, and it’s very likely that you need the developer package qt-devel and its associated libraries to build, not just the base package.

Just a thought, but since someone else in the thread said you can stream to Chromecast via VLC, you can desktop capture natively in VLC and stream that to your Chromecast. I can’t remember if the native capture can do sound or not, but if not, you can instead use OBS virtual cam (you’ll need v4l2loopback for the virtual cam to show up), and open that as a capture device in VLC. You should be able to attach an audio source to that as well. While I haven’t personally tested it with audio, I have used OBS virtual cam with VLC before, and it worked flawlessly for me. If you can’t find a more elegant solution, then it’s worth a shot to try and see if it works

While I haven’t personally tried it, I’ve heard people have issues with cooling when using the M.2 hat, especially when using their Pi for intensive applications (like hosting a Minecraft server). I’d honestly recommend just getting a 2.5" USB drive enclosure and an SSD. Costs about the same amount of money without the drawback of poor cooling. You can use it with any case, since it just connects via USB. I have been running my Pi this way for years (in fact I have never used an SD card in it).

I am also experiencing this issue on Fedora 40 with the Negativo drivers, and I believe this is a flatpak issue. Here is a GitHub issue detailing the problem. Allegedly it has been fixed, but I have updated to the latest commit and am still having the same issue, so I am unsure what to do (I’ve spent a number of hours trying to troubleshoot this). You might have luck just running a flatpak update, as that is supposed to solve this issue (YMMV though, it didn’t fix it for me).

Oh, on second look I suppose you are correct. Silverblue and Kinoite kept their names, but Sericea and Onyx (and all future spins) use the Fedora [DE] Atomic structure. I was under the impression based on the announcement that all of them followed that naming structure, since they are collectively referred to as Fedora Atomic Desktop spins now. That actually seems much weirder than having changed them all to the same structure, because it was intended to lessen confusion, but now half of the spins use a different naming scheme than the other? Strange choice imo.

Here’s the announcement I was referring to.

Fedora KDE Atomic Fedora Kinoite

Excluding Fedora because it’s “too close to RH” doesn’t make any sense at all. Fedora is not controlled by Red Hat, and Red Hat has no interest in a consumer desktop platform that they can’t sell. Fedora’s development is managed by FESCo, a community elected board that represents the interests of the community. They are kept intentionally separate from Red Hat’s development, and don’t tailor their development to Red Hat’s wants or needs (in fact they often do the opposite, as Fedora pushes for change in the way things are done, not stability, as can be seen by the exclusion of X11 from Fedora 40, for example). That stands in direct contradiction with RHEL’s goals. The features that are pushed by Red Hat developers would not be approved if they stood against the wants of the community, so anything Red Hat does contribute benefits the community as well. Red Hat’s entire business is in enterprise solutions, as their business model relies on them selling support for their software. There is exactly $0 in potential revenue from Red Hat trying to take over Fedora, it just doesn’t make sense. They can’t sell anything, and since Red Hat doesn’t employ all of the thousands of active contributors, such a takeover would simply result in a new fork. In fact, it would be against their interests, as Red Hat actively benefits from the developments of the community. Taking over control of the project would lose them all of the constant volunteer work put in by the community, which costs far less for them to sponsor than it would to employ a team a fraction of the size on salary. I’ve discussed this topic at length many times before, so I’ll just link to a few comments that explain the situation in more detail (including how the project is funded, managed, and separated from Red Hat).

https://lemmy.world/comment/7490965

https://lemmy.world/comment/7494803

The best fit for your criteria is Fedora. If you want uBlue spins, you’re still getting Fedora, just a more opinionated version. All of the major development of uBlue’s images comes from Fedora though, as they don’t maintain their own distro, they just repackage Fedora.

Just to clarity the relationship between Red Hat, IBM, and Fedora, Fedora is only sponsored by Red Hat. They make all their own decisions, and while they receive financial support from Red Hat and Red Hat owns the Fedora trademark, their decisions and development are independent of Red Hat (and by extension IBM), with the single exception that they cannot risk violating the law (i.e. copyright infringement), else it risks Red Hat legal trouble (and Fedora would risk losing their sponsorship as a result). Red Hat benefits from Fedora’s development by the community, given that Fedora is RHEL’s upstream, hence why it continues to sponsor Fedora. But it isn’t Red Hat that is in charge of Fedora’s development, it’s FESCo, which is entirely community elected, and does not stand for the interests of Red Hat, but rather for the interests of the community.

Eliminating Fedora from contention in that regard is essentially like eliminating Debian because you don’t like Canonical, who makes Ubuntu, a downstream of Debian.

Add on top of that the fact that IBM and Red Hat are major contributors to the Linux kernel, and you absolutely cannot avoid connections to them while using Linux. I mean, that’s quite frankly a ridiculous exclusion criteria in the context of Linux. If you’re looking to avoid an operating system OWNED by Red Hat or IBM, then Fedora should not be included in that list. Neither of them have any say or pull in the development of Fedora, which is a completely community-driven project (no, owning the trademark doesn’t change that fact; if Red Hat tried to take over, the Fedora community would simply fork the project, rebrand, and continue on their own). Besides, Red Hat has no interest in controlling Fedora, because it doesn’t benefit them. Their only interest is in enterprise applications, which is not a good use case for Fedora. The only operating systems Red Hat actually has any control over are RHEL, CentOS, and any derivatives of those operating systems like Rocky Linux, Oracle Linux, and such (though Red Hat’s control over derivatives was only the result of those projects being downstream, not actual ownership).

So with that in mind, I’d recommend the Fedora KDE spin if you want a normal, stable, snap-free, no DIY required distro with KDE, or if you want the immutable version, Fedora Kinoite is what you’d be looking for. And Fedora has the major advantage over Debian-based distros of actually receiving package and kernel updates regularly, so you can stay up to date and enjoy new features, all while maintaining stability.

Fedora Kinoite is absolutely the best immutable distro fitting your criteria. Anything else will have a much smaller community and less support as a result. rpm-ostree has great documentation, and all of the Fedora Atomic Spins have a huge userbase available in case you ever have questions.