Most install guides for CutefishOS assume there is one project with one ISO, and that stopped being true a while ago. The original releases ended years back, the old cutefishos.com site no longer answers, and the newest Ubuntu based ISO that survives on SourceForge is a community rebuild called CutefishOS YoYo: the Cutefish desktop, renamed Yoyo, on top of Ubuntu 22.04. It still installs, but it has quirks the old tutorials never mention, and one of them leaves you staring at a black screen after the first reboot.
We’ll walk through what this build actually is, how to download and verify it, how the installer behaves, why the installed system boots to nothing, and the one line fix that brings the login screen back. The behavior described here was checked against the CutefishOS 22.04.0 YoYo beta ISO (Ubuntu 22.04.3 LTS base, kernel 6.8.0-149-generic after updates) on a 4 vCPU, 4 GB KVM virtual machine with UEFI firmware in November 2026.
If you want the maintained project rather than this frozen Ubuntu build, read our tested guide to the revived Debian 13 based Cutefish instead.
What the YoYo build is, and how it differs from the Debian revival
CutefishOS YoYo is an Ubuntu 22.04 remaster with the Cutefish desktop packaged under new names. The CutefishOS Reborn download page calls it Beta 1 and credits the YoYo team for it, and once it’s installed the Settings app stops saying Cutefish at all, because the About page reports Yoyo OS. That matters in practice, since almost every package you’ll touch carries the yoyo prefix and an apt search for cutefish finds the wrong thing.
Four layers make up the installed system, and knowing which one owns a file tells you who will ever fix it:
- Ubuntu jammy base: kernel, systemd, apt and the security archive come straight from Canonical, so these keep getting updates until the Ubuntu 22.04 support window closes.
- Yoyo desktop packages: 29 desktop packages such as yoyo-dock, yoyo-launcher, yoyo-statusbar and yoyo-sddm-theme, served from a repository on yoyo-os.github.io whose index hasn’t changed since July 2022.
- Third-party sources: the image ships apt entries for Microsoft Edge, the Mozilla Team PPA, the graphics-drivers PPA and the Spark Store, a Chinese app store whose repository is hosted on deepinos.org.cn.
- Bundled apps: WPS Office, Discord, Telegram Desktop, Motrix and uTools sit in the launcher on first boot and add to the 16 GB footprint.
Only the first layer is still maintained. The revived Cutefish is a separate codebase with a Debian 13 base, nightly ISOs and active commits, so nothing below applies to it. This guide is for people who already have the YoYo ISO, need the Ubuntu package ecosystem, or want to see the desktop as it looked before the project restarted, and for them the fixes below are the difference between a working machine and a blank monitor.
How to download the ISO and check it wasn’t corrupted
The image lives on the cutefish-ubuntu SourceForge project, and the default redirect picked a mirror that crawled at roughly 0.3 MB/s for us. Pinning a mirror with the use_mirror parameter made the same 4.2 GB download about a hundred times faster. Add it before you start, because a stalled 4 GB transfer is the slowest part of this whole install:
wget -nv --content-disposition "https://sourceforge.net/projects/cutefish-ubuntu/files/ISO/Ubuntu/CutefishOS-22.04.0-YoYo-beta-amd64.iso/download?use_mirror=gigenet" -O CutefishOS-22.04.0-YoYo-beta-amd64.iso
The download page publishes no checksums, but SourceForge shows both an MD5 and a SHA256 in the file’s info panel. Compare against the SHA256, because MD5 is weak against a deliberate forgery, and treat the MD5 as a quick second check. Neither proves who built the image, only that your copy matches what the project uploaded:
md5sum CutefishOS-22.04.0-YoYo-beta-amd64.iso
sha256sum CutefishOS-22.04.0-YoYo-beta-amd64.iso
Our copy matched both published values exactly, and the transfer reported 4,428,580,864 bytes. If your SHA256 does not match, download it again from another mirror before writing it anywhere:
a5b5676293002d1ffce3d4b479c32e56 CutefishOS-22.04.0-YoYo-beta-amd64.iso
b621fb8b602bd54cdef93c840ec9ec2481c5a71764284c3f98781801e1fce97f CutefishOS-22.04.0-YoYo-beta-amd64.iso
The whole download and check ran on a separate workstation, with the mirror URL wget resolved to in its log line:

For bare metal, write the ISO to a stick with any of the methods in our guide to creating a bootable USB on Linux and macOS, or drop it onto a Ventoy multiboot drive next to your other images. A virtual machine needs nothing more than the ISO attached as a CD drive. We would treat 4 GB of RAM and a 30 GB disk as the floor, because the installed system already uses 16 GB of disk before you add anything.
What happens when the live image boots
The ISO boots through GRUB on UEFI, with a plain Ubuntu style menu. The first entry starts the live desktop, and the safe graphics entry is the one to reach for if the screen goes blank on an older GPU. We never needed it on the virtio display, since the default entry reached the desktop without any kernel parameters added.

The live session lands on the Yoyo desktop with an “Install CutefishOS” icon in the corner, and that icon is the first trap. Neither a double click nor selecting it and pressing Enter launched anything in our run, so the obvious path looks broken. The installer behind it is Ubiquity, the same GTK installer Ubuntu itself used through the 22.04 release, and starting it from the live terminal worked on the first try:
ubiquity gtk_ui
Give it close to a minute. The window took about 55 seconds to appear on our VM, with no feedback in the meantime, and its title bar reads “Install (as superuser)”. We left the terminal open for the whole install, which is useful because its log lines show where a page stalled if one ever does.
How the installer walks through disks and users
Ubiquity’s welcome page combines the language list with Try and Install buttons. Pick your language, then click Install CutefishOS on the welcome page, since you’re already in the live desktop and the other button has nothing new to offer. Every page after this one is the stock Ubuntu flow with the name swapped, so anyone who has installed Ubuntu 22.04 will recognise it.

None of the remaining pages needs anything unusual. They come in this order:
- Keyboard layout.
- Updates and other software, where “Download updates while installing CutefishOS” is ticked by default and the third-party software option sits just below it.
- Installation type, covered in the next figure.
- A confirmation listing the partitions it’s about to write.
- Your time zone on a map.
- Who are you, the account page.
On a dedicated disk or a VM, select Erase disk and install CutefishOS, which wipes the disk and lays out the partitions for you, and then press Install Now. The confirmation dialog that pops up is the last chance to back out before anything is written, so read the device name on it. When Ubiquity detects another operating system it also offers to install alongside it, and “Something else” is the manual route if you want to place the partitions yourself.

- 1Erase disk and install CutefishOS
- 2Install Now
The account page is where the black screen story starts, even though nothing on it looks wrong. Fill in your name, the computer’s name and Pick a username, set a password, and keep Require my password to log in selected. Then press Continue and the file copy begins behind Ubuntu’s own slideshow, which still says “Welcome to Ubuntu” because nobody rebranded it.

- 1Pick a username
- 2Require my password to log in
- 3Continue
With update downloads enabled, the whole install took about 12 minutes from launching the installer to the restart prompt. Remove the ISO when the prompt asks for it, so the machine boots from the disk you just wrote rather than the live image. If it lands in the live session again, the ISO is still first in the boot order.
Why the installed system boots to a black screen
The first boot of the installed system ends on a black screen with no login prompt. The kernel and systemd are fine, and the display manager is the part that fails. A configuration file left over from the live image is to blame: /etc/sddm.conf still tells SDDM to log in a user named live automatically, and the installed system has no such user.
Switch to a text console with Ctrl+Alt+F2 and log in with the account you created. SDDM writes every login attempt to the journal, so asking it for the autologin lines shows exactly what went wrong:
journalctl -b -u sddm --no-pager | grep -E "autologin|Authentication|exited"
PAM cannot find the user, the helper gives up, and SDDM never falls back to drawing its greeter. That last part is what turns a bad config line into a dead screen, since nothing offers you a login prompt instead:
Nov 13 17:41:29 cutefish-vm sddm-helper[541]: pam_unix(sddm-autologin:account): could not identify user (from getpwnam(live))
Nov 13 17:41:29 cutefish-vm sddm-helper[541]: [PAM] acctMgmt: Authentication failure
Nov 13 17:41:29 cutefish-vm sddm[468]: Authentication error: "Authentication failure"
Nov 13 17:41:29 cutefish-vm sddm[468]: Auth: sddm-helper exited with 1
Two more checks explain where the setting comes from. dpkg -S shows the file belongs to the yoyo-sddm-theme package, so it was baked into the package rather than written by the live session. The Autologin block then names a user that getent can’t find. Notice the typo Relogin=ture as well, which suggests nobody exercised this block on an installed system.

Since the bad block ships inside a package, every fresh install from this ISO hits it, on real hardware as much as in a VM. Once you know that, the black screen stops looking like a driver problem. You can skip the usual detour through nomodeset and GPU drivers and go straight to the config file.
How to bring the login screen back
Comment out the three Autologin lines so SDDM has nothing to try, and it shows the greeter instead. A single sed command from the same tty2 session handles all three, so you don’t need an editor on a machine with no working desktop:
sudo sed -i 's/^User=live/#User=live/; s/^Session=plasma.desktop/#Session=plasma.desktop/; s/^Relogin=ture/#Relogin=ture/' /etc/sddm.conf
Confirm the block now reads as comments before restarting anything. A typo in the pattern would leave a line untouched, and then the restart changes nothing:
grep -n -A3 "^\[Autologin\]" /etc/sddm.conf
Each of the three keys should start with a hash. The line numbers may differ on your copy, but the block always sits under the Autologin header:
30:[Autologin]
31-#User=live
32-#Session=plasma.desktop
33-#Relogin=ture
On the lab VM the edit and the check looked like this, line numbers included:

Restarting the display manager is enough, so there is no need to reboot. SDDM rereads its config on start and this time finds no autologin to attempt:
sudo systemctl restart sddm
The Yoyo greeter appears with your user and a password field. Logging in from here took about three seconds to reach the desktop, and in our run the fix held across every later reboot, including the one after the full upgrade below.

We comment the lines out rather than deleting them so the original values stay visible. If the black screen ever comes back after an update, a quick look at that block tells you whether a package put the live user back, and the same sed command fixes it again.
What the desktop runs on once you’re in
Inside, you get the familiar Cutefish layout: a translucent status bar on top, a centred dock at the bottom, and a full screen launcher behind the rocket icon. Everything is drawn by the yoyo processes on a KWin X11 compositor. There is no Wayland session at all, since /usr/share/wayland-sessions doesn’t exist and the only session files are yoyo-xsession and a leftover plasma entry.

Open the launcher and you see how much the YoYo team bundled on top of the desktop. Spark Store, the WPS Office suite, Discord, Telegram, Thunderbird, VLC and a handful of Chinese utilities come preinstalled. That’s convenient if you wanted them and dead weight if you didn’t, so plan a cleanup pass with apt if disk space matters.

Settings, About is where the rename becomes obvious. It reports Yoyo OS built on Ubuntu 22.04 with system version 0.8, so the Cutefish name only survives in the ISO, the installer and the boot menu.

Underneath, it is plain Ubuntu, and lsb_release says so without any branding. Run it whenever a guide asks which Ubuntu you’re on, because the answer decides which PPAs and packages will install:
lsb_release -a
We captured this before the full upgrade, so the point release is the one the ISO was built from. The upgrade later in this guide pulls a newer base-files package, and after it you should expect a later 22.04 point release here:
Distributor ID: Ubuntu
Description: Ubuntu 22.04.3 LTS
Release: 22.04
Codename: jammy
We ran it next to uname -r to record the kernel that the base’s updates had already pulled in:

That Ubuntu base is the reason this build is still usable at all. Drivers, firmware and security patches keep arriving through the jammy archive even though the desktop itself is frozen, so the system stays patched while the shell on top stays exactly as it shipped.
Why apt update reports a certificate error
Run the first package refresh and you’ll get one failure among the hits. The Spark Store entry in /etc/apt/sources.list.d/sparkstore.list points at d.store.deepinos.org.cn, and the certificate that host presents doesn’t match its name. Apt refuses the connection, as it should, and moves on to the next source:
sudo apt update
Every other source answers, including the frozen Yoyo repository. This excerpt keeps the hits, the failing source and the upgrade count. The full run, with its warnings, is in the screenshot after it:
Hit:3 https://yoyo-os.github.io/packages kokomi InRelease
Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease
Hit:5 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Hit:6 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:7 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:8 https://ppa.launchpadcontent.net/graphics-drivers/ppa/ubuntu jammy InRelease
Hit:9 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease
Err:1 https://d.store.deepinos.org.cn/store InRelease
Certificate verification failed: The certificate is NOT trusted. The name in the certificate does not match the expected. Could not handshake: Error in the certificate verification. [IP: 203.0.113.10 443]
Reading package lists...
Building dependency tree...
Reading state information...
472 packages can be upgraded. Run 'apt list --upgradable' to see them.
The full run, with the ignored retries and the closing warnings, looked like this on the VM:

The failure is harmless to the rest of the system, because apt simply ignores that index and uses the others. It does mean apt cannot install or update anything from the Spark Store repository. We left the file in place for the run, and the upgrade below completed with the warning still printing each time, so nothing forces you to deal with it today.
How much the desktop costs at idle
Measured about ten minutes after boot with a terminal open, the session used just over 1 GB of RAM, booted in a little over four seconds, and took 16 GB of the 29 GB root filesystem. These four commands give the whole picture in one pass:
free -m
ps -eo rss,comm --sort=-rss | head -8
systemd-analyze
df -h /
The memory list is the interesting part. Three Yoyo components and the KWin compositor each hold more than 200 MB, and the launcher is the heaviest process on the box even while it is hidden:
total used free shared buff/cache available
Mem: 3909 1084 1237 58 1587 2536
Swap: 3219 0 3219
RSS COMMAND
273796 yoyo-launcher
237476 yoyo-desktop
226924 yoyo-statusbar
210996 kwin_x11
180820 yoyo-terminal
171116 yoyo-dock
143208 update-apt-xapi
Startup finished in 2.634s (kernel) + 1.608s (userspace) = 4.242s
graphical.target reached after 1.598s in userspace
Filesystem Size Used Avail Use% Mounted on
/dev/vda2 29G 16G 13G 56% /
All four commands ran in one terminal on the desktop. The apt-xapian indexer (update-apt-xapi) was still working in the background, so a fully quiet session sits a little lower than this:

Do not add up the RSS column, though. Every Yoyo shell piece is a separate Qt process, and RSS counts the shared Qt libraries again in each one, so the sum overstates the real cost. The honest number is the 1084 MB in the used column, which leaves a 4 GB machine comfortable and a 2 GB one tight. If that’s too much, a lighter Xfce system like the one in our MX Linux install guide is the usual answer.
What a full upgrade does to it
Because the base is jammy, the 472 pending updates are almost all Ubuntu packages, and they install cleanly. We ran the upgrade non-interactively and told dpkg to keep existing config files, so a package that ships a new sddm.conf can’t quietly undo the fix:
sudo DEBIAN_FRONTEND=noninteractive apt-get -y -o Dpkg::Options::=--force-confold full-upgrade
It took about four minutes on the VM. The tail of the log shows the last triggers, ending with an initramfs rebuild for the kernel that was already running:
Processing triggers for ca-certificates (20260816ubuntu0.22.04.2) ...
Updating certificates in /etc/ssl/certs...
rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL
27 added, 44 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Processing triggers for initramfs-tools (0.140ubuntu13.5) ...
update-initramfs: Generating /boot/initrd.img-6.8.0-149-generic
After a reboot, check that the display manager came back and nothing else broke. Two commands cover it, and an empty second result is the good outcome:
systemctl is-active sddm
systemctl --failed --no-legend
SDDM reported active, the failed list was empty, the greeter came up normally and the Autologin block was still commented. None of the Yoyo packages changed version, which is what you would expect when their repository hasn’t published anything since 2022.
Ubuntu’s own calendar is the bigger deadline. Canonical’s release cycle page puts the end of standard support for Ubuntu 22.04 in May 2027, with Expanded Security Maintenance through Ubuntu Pro after that, which Canonical offers free for personal use on up to five machines. A release upgrade like the one in our Ubuntu 22.04 to 24.04 upgrade guide is the obvious next move. We didn’t test it on this build, though, and the Yoyo repository was built for jammy and has not changed since 2022, so expect the desktop to be the part that breaks.
Where this build breaks down
Once the login fix is in, the YoYo build is a pleasant, quick Ubuntu desktop. The trouble is everything around it, and you should know these limits before putting it on a machine you depend on:
- Frozen desktop: no Yoyo package has been rebuilt since 2022, so desktop bugs like the SDDM autologin stay unfixed and you patch them by hand.
- Beta label: the download page still calls it Beta 1, and the installer icon that does nothing shows how little final testing it got.
- X11 only: there’s no Wayland session, so none of the Wayland work landing in newer desktops will reach this one.
- Broken store repository: the Spark Store apt source fails certificate verification, so nothing installs or updates from it until its host is fixed.
- Fixed end date: security updates track Ubuntu 22.04, and standard support for that release runs out in May 2027.
For a VM to study the original Cutefish design, or an old laptop you’ll keep for a year, it’s fine. For anything longer, development continues on the revived Cutefish on Debian 13. If the macOS style dock is what drew you in, our roundup of the best Linux desktop distributions covers maintained options with a similar look.