It sounds like you might (both) be confused about something. If the RPGMaker editor suddenly closes, there’s absolutely no chance that that’s caused by a plugin. Even if you’re seeing the game crash on playtest, it’s not very likely to be caused by a plugin (though it is possible).
Since the editor is what’s closing and not the playtest, a few things I’d try to narrow it down.
Check that Steam isn’t running it through a compatibility layer. Right click RPG Maker MV in your library → Properties → Compatibility, and make sure force compatibility tool is unchecked. MV has a native Linux build and Proton tends to cause trouble with it.
Try launching it outside Steam from a terminal so you can see what it prints when it dies. Go to your Steam library folder (something like ~/.steam/steam/steamapps/common/RPG Maker MV) and run:
./"RPG Maker MV.sh"
Then open the project and paste whatever shows up in the terminal right before it closes. That output is what would tell us if it’s permissions, a missing library, or something else.
Couple of other questions. Is Steam installed from the Flatpak or Snap version? I’ve seen reports of the sandboxed versions breaking MV. And is the project on the same drive as your home folder, or somewhere like an external or NTFS drive?
Also, when you say it can open a project listed in Steam management fine, do you mean a project created from inside MV opens but one you copied in doesn’t? Want to make sure I’m following.
I was not running it through a compatibility layer.
Could not launch the RPG Maker MV.sh outside of steam.
Though I do think the issue is permissions based. As when I did run it through Proton I was no longer getting the issue. On my Linux system Steam in installed via Snap.
When I mean something listed inside steam management fine. I mean something I got via subscription from Steam’s Workshop
Ok thanks for the info. Two things I’d try, in order:
Move your project into your home folder, somewhere like ~/Documents/RPG Maker MV, then open it from there. If it’s currently on another drive or outside home, that’s the first thing I’d rule out. If it’s on an external drive, running snap connect steam:removable-media in a terminal may also open that up.
If that doesn’t do it, I’d uninstall the Snap version and install the official .deb from Steam’s site instead: https://store.steampowered.com/about/
Seems the sandboxed Steam builds can break MV on Linux, and the .deb doesn’t have those restrictions. Where is the project folder sitting right now?
Ok, then I’d go with the .deb at this point. /games is outside the Snap sandbox so I’d expect that one to fail, but the default home location failing too makes me think it’s the Snap build itself and not where the folder lives.
One quick check before you reinstall, if you make a brand new project from inside MV (File → New Project) and open that, does it close too? If a fresh one opens fine then it’s something in that specific project and not the install. If it closes the same way, the .deb swap is the next thing I’d try.
That broken dependencies message looks like a known thing with Steam on Ubuntu. The Steam client needs 32 bit libraries and Ubuntu doesn’t have the 32 bit (i386) architecture enabled by default, so apt can’t find them and reports the deps as broken.
Run the last one from wherever you downloaded the .deb (usually ~/Downloads). Using apt install ./file.deb instead of double clicking the .deb or using dpkg -i lets apt pull the dependencies in on its own.
If you’d rather skip the downloaded file, Ubuntu’s own repo version works too after the first two commands:
sudo apt install steam-installer
If either one still errors, paste the exact output here and we can go from there.
After all that is gives me this
sudo apt install steam-installer
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Note, selecting ‘steam-launcher’ instead of ‘steam-installer’
steam-launcher is already the newest version (1:1.0.0.87).
You might want to run ‘apt --fix-broken install’ to correct these.
The following packages have unmet dependencies:
steam-launcher : Depends: xterm or
gnome-terminal but it is not installable or
konsole but it is not going to be installed
Recommends: steam-libs-amd64
Recommends: steam-libs-i386
E: Unmet dependencies. Try ‘apt --fix-broken install’ with no packages (or specify a solution).
That output is apt saying the .deb got half installed (steam-launcher is on the system but its dependencies weren’t pulled in), and it won’t try anything else until that’s fixed. So the first thing I’d run is the command it’s asking for:
sudo apt --fix-broken install
If that goes through, Steam should be installed and you can launch it normally.
If it errors out, the part that stands out to me is gnome-terminal showing as not installable. On a stock 24.04 that package should always be available, so I’m wondering if the package lists didn’t refresh properly. Run this and paste everything it prints, especially any lines that say Err or Failed:
sudo apt update
Then try the fix broken command again. If it still complains about the terminal dependency, installing xterm directly should satisfy it:
sudo apt install xterm
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
xterm : Depends: libutempter0 (>= 1.1.5) but it is not installable
Recommends: luit but it is not installable or
x11-utils (< 7.7+6~) but 7.7+6build2 is to be installed
E: Unable to correct problems, you have held broken packages.
Something looks off with the Ubuntu package sources themselves rather than Steam. libutempter0 is a regular package in Ubuntu’s main repo, so apt telling you it’s not installable on noble, right after a clean apt update, makes me think apt isn’t seeing the full Ubuntu archive. Another thing I noticed in your update output is it only lists noble, where Ubuntu’s default sources also include noble-updates and noble-security, so maybe something in the sources list got changed or trimmed at some point.
If the first file doesn’t exist, try cat /etc/apt/sources.list instead.
The error in the corner is from steam-launcher sitting half installed, it’ll keep nagging until the dependencies get sorted. If you want it quiet in the meantime, sudo dpkg --remove steam-launcher should take it back off cleanly, and we can reinstall once apt is happy.
cat /etc/apt/sources.list.d/ubuntu.sources
Types: deb
URIs: Index of /ubuntu
Suites: noble
Components: universe
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg
pt policy libutempter0
libutempter0:
Installed: (none)
Candidate: (none)
Version table: