Ubuntu-toolbox breaks my freshly installed system

[befanyt]

Describe the bug

So I've installed a fresh bluefin:gts in a VM, updated the system with ujust update to make sure I'm on the latest build.

After hitting Ctrl + Alt + u the ubuntu-toolbox did not launch, but it did bork the complete system.

It notifies you, Starting ubuntu-toolbox, please be patient so I wait. Nothing happens. Then you get a notification Restarting ubuntu-toolbox, please be patient followed by the last message ubuntu-toolbox not created properly... Bailing Out...

When I then type in the terminal

~ 
❯ pwd
/var/home/user

~ 
❯ touch $HOME/test
touch: cannot touch '/var/home/user/test': Read-only file system

~ 
❯ rpm-ostree update
note: automatic updates (stage) are enabled
error: Remounting /sysroot read-write: Invalid argument

What did you expect to happen?

Open the ubuntu-toolbox terminal.

Output of rpm-ostree status

State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:gts
                   Digest: sha256:58b249029bdbff5209503ee57a1b96590253767c3b038c826e41c775ecc2d9e4
                  Version: 40.20241102.0 (2024-11-03T17:58:35Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:gts
                   Digest: sha256:c45af744e700412409ab654637542479b5982c1e2470df045a38bec8944a15bf
                  Version: 40.20241029.0 (2024-10-29T18:29:12Z)

State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:latest
                   Digest: sha256:c3652ab844e727b137b977763dcdfc0c44a802e6e844cbef709676207f2d8532
                  Version: 41.20241104.0 (2024-11-04T04:54:11Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:gts
                   Digest: sha256:58b249029bdbff5209503ee57a1b96590253767c3b038c826e41c775ecc2d9e4
                  Version: 40.20241102.0 (2024-11-03T17:58:35Z)

Output of groups

user wheel

Extra information or context

To reproduce make sure, opening the ubuntu-toolbox is the first thing you do after a fresh installation via the shortcut. Because when I first create a distrobox manually with distrobox create testcontainer and then launch the ubuntu-toolbox after that, it works without any problems as shown below:

❯ distrobox create testcontainer
Trying to pull ghcr.io/ublue-os/ubuntu-toolbox:latest...
Getting image source signatures
Checking if image destination supports signatures
Copying blob 676925d0455d done   | 
Copying blob fcba3eaad1c2 done   | 
Copying config a9df871a57 done   | 
Writing manifest to image destination
Storing signatures
a9df871a57489996e269ca5b900b9720aeacff079f9e4ce014084cf015e81776
Creating 'testcontainer' using image ghcr.io/ublue-os/ubuntu-toolbox:latest  [ OK ]
Distrobox 'testcontainer' successfully created.
To enter, run:

distrobox enter testcontainer

~ took 1m37s 
❯ distrobox enter testcontainer 
Starting container...                        [ OK ]
Installing basic packages...                 [ OK ]
Setting up devpts mounts...                  [ OK ]
Setting up read-only mounts...               [ OK ]
Setting up read-write mounts...              [ OK ]
Setting up host's sockets integration...     [ OK ]
Integrating host's themes, icons, fonts...   [ OK ]
Setting up distrobox profile...              [ OK ]
Setting up sudo...                           [ OK ]
Setting up user's group list...              [ OK ]
Setting up existing user...                  [ OK ]
Ensuring user's access...                    [ OK ]

Container Setup Complete!
📦[user@testcontainer ~]$ exit
logout

~ took 4s 
❯ distrobox list
ID           | NAME                 | STATUS             | IMAGE                         
4a6d7c45f18a | testcontainer        | Up 9 seconds       | ghcr.io/ublue-os/ubuntu-toolbox:latest

~ 

hit the keyboard shortcut to open ubuntu-toolbox

❯ distrobox list
ID           | NAME                 | STATUS             | IMAGE                         
4a6d7c45f18a | testcontainer        | Up 17 seconds      | ghcr.io/ublue-os/ubuntu-toolbox:latest
90527410a173 | ubuntu-toolbox       | Up 3 seconds       | ghcr.io/ublue-os/ubuntu-toolbox:latest

~ 

Same thing happens on bluefin:latest Added log file from journalctl --user -u ubuntu-toolbox.service journalctl.txt

[castrojo]

I think this is the other way around from looking at the log, the read only fs is what caused the toolbox to break I think? Can you share the system log?

[befanyt]

Did a clean install again, bluefin:gts, after the message Welcome to bluefin, your computer is ready! I hit the ubuntu-toolbox shortcut. Log below

❯ rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:gts
                   Digest: sha256:c45af744e700412409ab654637542479b5982c1e2470df045a38bec8944a15bf
                  Version: 40.20241029.0 (2024-10-29T18:29:12Z)

log-full.txt

Will download a fresh copy of bluefin-gts.iso and try on a proxmox host, just to rule out my hardware

[befanyt]

Well good thing I tried it on another host, did not happen there. Sorry for the noise.

[castrojo]

Let's let others chime in, a little due diligence won't hurt. (Just in case)

[tulilirockz]

this issue also should be mitigated by #1901 (since there will be no ubuntu-toolbox container :p)