Kinoite, a KDE (and now XFCE) version of Fedora Silverblue

Great! Keep in mind that I don’t build F32 updates anymore.

@Siosm any idea what is wrong?

From your logs, you have plasmashell crashing:

Nov 30 00:46:36 host systemd-coredump[16404]: Process 16371 (plasmashell) of user 1001 dumped core.

Can you report that in the Fedora bugtracker with the log output, the coredump from systemd-coredump and the version from rpm -qi plasma-workspace?

Just rebased to Pantheon and quite liking it although vpn settings werent working - had to install NetworkManager-openvpn-gnome to get them working.

1 Like

Got a good deal on a used Radeon card now so that I can run F33 without any proprietary drivers. Thanks for providing this awesome project @Siosm

1 Like

Hello @Siosm,
I would like to add swaywm support to your project

is it neccesary to add sway to corps first ?

1 Like

Hey @stbischof!

No this is only needed if you want to re-use existing package lists created for Fedora Spins but I don’t think there is a Sway spin.

Thanks for doing that! I held off doing that for now and created the Base variant instead as I know that people who usually use minimal desktop environments also like to handpick their tools / components a lot more that KDE or GNOME users where we have a clear standard offering.

With the new Fedora archive repo, there should basically be no downsides to package layering and building on top of the base image should be easier than building more variants which is something that I am currently reluctant to do as it takes time.

So thanks for doing that but I’m probably not going to work on that for now as I am currently focusing on making the KDE edition official. You can however try to find like minded individuals to start working on an official Sway Spin / Edition in Fedora itself.

@stbischof: Meanwhile, if you’re fine with building your own version, a co-worker of mine (@martinpitt) has built his own Silverblue-like Fedora with Sway:

You could use his scripts to built it yourself… or if you’d like, I think you could even rebase a Silverblue installation to his build:

sudo ostree remote add --no-gpg-verify piware
sudo rpm-ostree rebase piware:pitti-desktop

Thank you @garrett,

i had an open issue on @martinpitt s project. could not rebase · Issue #1 · martinpitt/ostree-pitti-workstation · GitHub

This is mostly what i searched. ( just flatpak is missing…)

The combination of this Project and

Would be great. Lets see what the time brings.

To account for the increase in traffic on the repo, I moved it to a beefier server which should help with updates. Let me know if you have issues.

I have been late pushing updates recently due to unplanned internet access issues. I am currently pushing updates for the F33 branch. Rawhide is currently paused.

Unfortunately for the KDE variant, this issue is still here for this update. I have a hint about the root issue but have not been able to figure it out yet. Hopefully this should go away when Kinoite is merged upstream for Fedora 35 (see the proposed change).

As always, as I made some change on the server side, please let me know if you do not see the update or if something is wrong.

I have updated the Rawhide refs! Let me know if you encounter issues.

Thanks. What Plasma version does the Rawhide ref include?
I’m one of the Plasma devs, and searching for convenient way to bisect bugs. Like this: 432317 – Can't logout session - it restarts immediately.
I think it would be useful if you make refs for Plasma Beta branch, or even master.
Similarly the way KDE neon does.


Rawhide currently has the latest Beta packages (plasma-desktop-5.20.90-3.fc34.x86_64).

I agree that it would be great to have master builds but I need someone (or a group of people) to maintain the RPM packages as a Copr for example.

For the reference: I spent days debugging this, just because my Plasma Dev installation was dirty.
Bisecting this was a pain because it involved several repos rebuild.
Still I had no choice because there is no OSTree-based Plasma distribution known to me.

1 Like

Improving the situation on this front is definitely on my TODO list once we have Kinoite build by Fedora infrastructure. The best option would be having daily master Plasma / Qt builds on top of stable Fedora available for KDE developers to test via Kinoite.

Ideally it should build as frequent as CI here: All [Plasma] [Jenkins].
But even daily builds would help a lot.

1 Like

Fedora 34 has been branched, so I’ve published f34 refs for all variants. I’ve only lightly tested the KDE ref so beware dragons!

Fedora Kinoite (KDE) has also been accepted for Fedora 35! :tada: Rawhide builds will appear first in the coming weeks/months.



Another temporary solution for the SDDM error at login is to add the following tmpfiles config in /etc/tmpfiles.d/sddm.conf:

Z /var/lib/sddm - sddm sddm - -

I don’t know why, but moving the KDE plasma settings in depth makes the kinoite 33 and 34 buggy

With other interfaces this does not happen