After restarting my machine it seems the error in the lower right corner is gone and there is also now a steam icon on my desktop.
However when I click it I get: There was an Error Launching this application
Hmm, this could be it. Your sources file only has the universe component and only the base noble suite, so apt can’t see main (where libutempter0 and gnome-terminal live) and hasn’t been getting updates or security patches either. The default Ubuntu 24.04 file has all four components and the updates and security suites.
That also lines up with the launch error you’re getting now. The Steam icon is there because the package got unpacked, but it can’t actually run until its dependencies come in.
You can replace the sources file with the default in one go. Paste this whole block into a terminal as is:
sudo tee /etc/apt/sources.list.d/ubuntu.sources > /dev/null << 'EOF'
Types: deb
URIs: http://archive.ubuntu.com/ubuntu/
Suites: noble noble-updates noble-backports
Components: main restricted universe multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg
Types: deb
URIs: http://security.ubuntu.com/ubuntu/
Suites: noble-security
Components: main restricted universe multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg
EOF
Then:
sudo apt update
sudo apt --fix-broken install
The update will pull a lot more than before since it’s been missing those repos. Once fix broken finishes cleanly, try the Steam icon again and let it do its first run setup, then install MV and open your project.
I’d also run sudo apt upgrade afterwards since the system has probably been behind on updates for a while.
What will the upgrade do?. Because my computer cannot go beyond Release 24.04. or Kernel Linux 6.14.0-36-generic x86_64 due to my hardware.
I am also nervous about messing with my repositories after a bad experience where I had to rebuild all of them from scratch after it was stuck with an incorrect install
Nothing to the release itself. apt upgrade only updates the packages already installed on your current 24.04, it never moves you to a newer Ubuntu version. That’s a separate command you’d have to run on purpose.
The kernel is the one thing worth being careful with. If a kernel meta package like linux-generic-hwe-24.04 is installed, an upgrade can bring in a newer kernel alongside your current one, and with your hardware limit I’d rather not risk that. So just skip the upgrade, it’s optional and not needed for any of this. The apt --fix-broken install step only installs what steam-launcher is missing and won’t touch the kernel.
On the repositories, totally fair. The change I posted is only to that one file and it’s easy to make reversible. Before pasting the block, back up the current one:
sudo cp /etc/apt/sources.list.d/ubuntu.sources ~/ubuntu.sources.bak
If anything looks wrong afterwards, copying it back puts you exactly where you are now:
sudo cp ~/ubuntu.sources.bak /etc/apt/sources.list.d/ubuntu.sources
sudo apt update
The new file doesn’t remove anything or add any third party sources, it just tells apt about the rest of Ubuntu’s own archive that the current file is leaving out. If you’d rather not touch it at all, the honest answer is that Steam (and a lot of other packages) won’t install until apt can see main, so I’m not aware of a way around it.
If you get a Software Updater popup after the update, you can ignore that for now.
I’m not sure if it’s too late or not. I did the block command and then told my software update tool to update. Which it is currently doing.
How can I tell if I messed something up?
It’s also asking me to restart my machine
Not too late, the update doing its thing is fine. Go ahead and restart when it asks.
The main thing I’d watch is the kernel. After the restart, run uname -r. If it still says 6.14.0-36 then nothing changed there. If it shows a newer one and your hardware acts up, the old kernel is still installed, you can pick it from the boot menu under Advanced options for Ubuntu (hold Shift or tap Esc right as the machine starts, depending on your BIOS) and we can pin it from there.
To check the rest went through, after the restart run these:
sudo apt --fix-broken install
apt policy libutempter0
The first should say nothing to install or it’ll finish off steam-launcher. The second should now show a version under Candidate instead of (none). If both look good, the sources change worked.
On the two Steam icons, I’m guessing one is left over from the Snap version. Before removing anything, find your MV projects folder and copy it somewhere safe like ~/Documents, since removing the Snap deletes everything it downloaded (games, MV, and anything saved inside its folder). Run snap list steam and if it shows up, send me the output of ls ~/snap/steam/common so we can make sure nothing important is in there first. Once that’s safe we can remove it, then launch the other Steam, let it do its first run setup, and install MV from there.
It’s said the Kernel is now 7.0.0-30-generic x86_64
I went to advance options and told it to use Kernel Linux 6.14.0-36-generic x86_64. Will it use that from now on whenever it boots up?
Also the website says I cannot post the read outs of the two commands you wanted me to do
Let me try again.
First command:
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
You can post it again, you got flagged for potential spam. I unflagged you, so if you could provide the info that would be awesome.
That should only lasts for the one boot. GRUB goes back to the newest kernel every time unless you tell it to remember your pick. You can make it stick with a small change to the GRUB config. First check what’s there:
grep -E '^GRUB_DEFAULT|^GRUB_SAVEDEFAULT' /etc/default/grub
If that shows GRUB_DEFAULT=0 and no GRUB_SAVEDEFAULT line, run these:
sudo sed -i 's/^GRUB_DEFAULT=.*/GRUB_DEFAULT=saved/' /etc/default/grub
echo 'GRUB_SAVEDEFAULT=true' | sudo tee -a /etc/default/grub
sudo update-grub
Then reboot, pick 6.14.0-36 from Advanced options one more time, and from then on it boots that one by default. If the grep shows something different, or update-grub prints any warning, tell me before rebooting.
On the command output, the forum’s spam filter flagged your account for posting a lot in a short time, that’s all it was. I’ve cleared it, so go ahead and post those two readouts again.
While you’re at it, this one would help too, so we can stop updates from pulling in any more kernels:
dpkg -l | grep -E 'linux-(image|generic|tuxedo)'
guild.rpgmakeroffical.com will not let me post the 2nd command output
Okay I did all of that.
Now what?
It still won’t let me post the second redout
Did the grep and update-grub steps go through without any warnings? If so, reboot, pick 6.14.0-36 from Advanced options one more time, and after it comes up run uname -r to make sure you’re on it.
After that I still need to see the readouts before going further. Post these three, a screenshot of the terminal is fine if the text won’t go through:
sudo apt --fix-broken install
apt policy libutempter0
dpkg -l | grep -E 'linux-(image|generic|tuxedo)'
DM me and see if that works.
When I go to your profile I’m not seeing the option to DM.
How do I do it?
