I surely will do so.
Since you mentioned doing the install via the command line, is there some documentation for that (I assume you mean using cmd from the booted installer)?
Or use standard fedora live cd to install kinoite?

All of this has to be done from a Fedora installer with the official installer Anaconda (doc).

I’m up and running. Thank you for all the work you do. You are awesome!

1 Like

but the gnome community doesn’t seem to be interested in aesthetics. what counts is technique and code, but not the end-user.

As I know many people in the GNOME community, I can assure you that this is manifestly not true. Let’s please keep the conversation here positive and on topic. Particularly, this thread isn’t about gathering opinions on GNOME design. It’s about building other options on the same rpm-ostree technology. The latter is awesome and let’s stick to discussing that. Thank you.

7 Likes

from 30.20190412.n.0 trying:

rpm-ostree rebase kinoite:fedora/30/x86_64/kinoite
Forbidden base package replacements:
  systemd-pam 241-4.gitcbf14c9.fc30 -> 241-5.git3d835d0.fc30 (fedora)
  systemd-udev 241-4.gitcbf14c9.fc30 -> 241-5.git3d835d0.fc30 (fedora)
  systemd-libs 241-4.gitcbf14c9.fc30 -> 241-5.git3d835d0.fc30 (fedora)
  systemd-rpm-macros 241-4.gitcbf14c9.fc30 -> 241-5.git3d835d0.fc30 (fedora)
  systemd 241-4.gitcbf14c9.fc30 -> 241-5.git3d835d0.fc30 (fedora)

i enabled updates-testing and i get many more forbidden replacements. i assume it doesn’t support updates and updates-testing

  systemd-pam 241-4.gitcbf14c9.fc30 -> 241-6.gita2eaa1c.fc30 (updates-testing)
  liberation-serif-fonts 1:2.00.3-3.fc30 -> 1:2.00.5-1.fc30 (updates-testing)
  libblkid 2.33.1-3.fc30 -> 2.33.2-1.fc30 (updates-testing)
  libmount 2.33.1-3.fc30 -> 2.33.2-1.fc30 (updates-testing)
  util-linux 2.33.1-3.fc30 -> 2.33.2-1.fc30 (updates-testing)
  liberation-sans-fonts 1:2.00.3-3.fc30 -> 1:2.00.5-1.fc30 (updates-testing)
  libuuid 2.33.1-3.fc30 -> 2.33.2-1.fc30 (updates-testing)
  systemd 241-4.gitcbf14c9.fc30 -> 241-6.gita2eaa1c.fc30 (updates-testing)
  liberation-mono-fonts 1:2.00.3-3.fc30 -> 1:2.00.5-1.fc30 (updates-testing)
  systemd-libs 241-4.gitcbf14c9.fc30 -> 241-6.gita2eaa1c.fc30 (updates-testing)
  systemd-rpm-macros 241-4.gitcbf14c9.fc30 -> 241-6.gita2eaa1c.fc30 (updates-testing)
  libsmartcols 2.33.1-3.fc30 -> 2.33.2-1.fc30 (updates-testing)
  liberation-fonts-common 1:2.00.3-3.fc30 -> 1:2.00.5-1.fc30 (updates-testing)
  systemd-udev 241-4.gitcbf14c9.fc30 -> 241-6.gita2eaa1c.fc30

I have never encountered such an error before. Do you have overlayed packages? Enabling updates & updates-testing repositories feels strange on an ostree install. What did you do exactly?

hello @Siosm and many thanks for doing that!!

On Silverblue 30 beta updates and updates-testing are enabled by default :confused: and i couldnt even disable them, b/c it will break my NVIDIA driver

now im re-trying on a clean SB installation on KVM, but im sure that i’ll get the same errors, but i will try to remove the updates and updates-testing to see if it works then

my OSTree Status i tested on before

● ostree://fedora-workstation:fedora/30/x86_64/silverblue
                   Version: 30.20190413.n.1 (2019-04-13T17:46:44Z)
                BaseCommit: 0b7872e963813d5400fe96be5c63982ee551c0024da6ea8b3e7b092e85cc3f0f
              GPGSignature: Valid signature by F1D8EC98F241AAF20DF69420EF3C111FCFC659B9
           LayeredPackages: akmod-nvidia chromium dconf-editor ffmpeg gnome-boxes gnome-tweaks kmod-nvidia libvirt
                            libxcrypt-compat qemu-kvm tilix unrar util-linux-user virt-install xorg-x11-drv-nvidia
                            xorg-x11-drv-nvidia-cuda zsh
             LocalPackages: rpmfusion-nonfree-release-30-0.2.noarch cuda-repo-fedora29-10.1.105-1.x86_64
                            rpmfusion-free-release-30-0.2.noarch google-chrome-stable-73.0.3683.103-1.x86_64
                    Pinned: yes

oh! it worked on KVM!!! SUPER COOL! even if testing and updates-testing are enabled!!

EVIDENCES :))))) …but why Dolphin isn’t preinstalled? although i know there is a Flatpak for it, but it has issues

1 Like

Indeed! That’s a recent addition (see PR).

Could you be more specific about the issues with Dolphin from Flathub?

wait! i need to retest on Kinoite, because in GNOME (Silverblue image) maybe i had issues coz missing Plasma stuff!

EDIT: LoL it started! after a couple of minutes :confused:

so, first issue is that Dolphin doesnt even start on Kinoite

flatpak run org.kde.dolphin 

First start: running kbuildsycoca5
kbuildsycoca5 running...
Qt: Session management error: Could not open network socket

everytime you’re starting Dolphin, it gets like a minute to launch, so it isn’t just the first time; also it cant see Konsole, so the embedded Terminal doesn’t work; there are also some Todos and things that dont work on Flathub Repo

i believe it would be just fine to include it on Kinoite image; besides it is the filemanager, not something that someone wouldnt possible want to have …plus it has to work super correctly!!

Indeed. I’ll add back file managers for all variants with the next update.

1 Like

I just tried a rebase to this and it worked perfectly. I agree it does need a file manager. Thanks so much for the work on this and the other desktops. Silverblue rocks!

1 Like

sorry, not wanting to use flatpak at all, add dolphin, ive actually spun up a bunch or thing i require, and really dont get the concept of flatpak … feels dockerish, anyway using silverblue / kinoite, so i can keep a clean system and not have to install a bunch of extra crap…

oh boy, you are kinda missing the point by a mile…
Flatpaks are intended companion for SB unless you don’t need anything other then what is on the base image.

im sorry to say however flatpak wount give you everything, i barely see the app i use daily on flathub, so why should i not just rpm-ostree install them and not waste more space with flatpak, and stay on one techhonogy…