Magmarock: Think you’d learned something by now hey.
I could say *exactly* the same of you.
Magmarock: Okay lets recap. First I criticized the fragmented way in which dependencies are handled all throughout the world of Linux; which you can read about here.
https://www.gog.com/forum/general/preorder_trine_4_the_nightmare_prince_e3277/post56 Yes, I read that and responded already - see my earlier replies.
Magmarock: It was merely a speculation as to why Trine 1 & 2 required so much fiddling and also why I suspected so many games don’t work well on Linux. This is not the kind of problem that can be fixed with a homemade fan-patch because this requires a massive overhaul on how dependencies are distributed all throughout the world of Linux.
I’ve not really interest in Linux until this is done. That’s what I was getting at. I can tell you why Trine requires so much fiddling: it's because they (or rather, GOG) included certain core system libraries with the game. Libraries such as libstdc++, libX*, graphics driver libraries etc. Do the equivalent of this on Windows and you'll end up with a broken game there too.
Ethan Lee wrote a good post about packaging for Linux which I linked to earlier.
Trine 2 works, but not full screen (and that's a bug with the port itself).
Magmarock: Nonetheless After incessant nagging I reluctantly decided to try out the meta-package. I tested in on Linux Mint 19.2 installed on a virtual machine. It wasn’t a live environment. I did everything you said to do, (which was to just double click it). But it didn’t work and when I showed you proof; you insisted that it was my fault and that I was using a live environment.
I call bullshit here. The exact steps I followed were:
- Boot into the live environment and install Mint 19.x as usual (I tested 19, 19.1 and 19.2), then restart
- On the fresh Mint install, double-click the package
This worked just fine in my VirtualBox VMs, just as it has on all of my real PCs, just as it has on other user's PCs. The only way I was able to replicate the issue you had was when I booted into the live environment and tried to install it there.
That you alone seem to be having these issues with it is very suspect and I wonder what exactly you're doing differently to literally everyone else that's causing it to fail - how are you installing and testing Mint? Are you not using the official disc images to install it? etc.
EDIT: Remembering some correspondence I had with a developer I was assisting some time ago, I remember they had similar issues with running Ubuntu in a VM. It turned out they were using a pre-made Ubuntu VM from osboxes.org which was not set up like a proper install from the Ubuntu install media, and this was causing a variety of issues with certain things not being installed/not being set up etc.
Is this what you're using? Because if so, it's not going to work unless you follow the steps I outlined above for installing in the live environment (I just downloaded their Mint 19.2 Cinnamon image and can confirm that it has the same issue), and even then there are likely to be other issues with it as well. I'm not sure how osboxes set it up exactly but it's not representative of a properly installed version of Mint (edit 2: looks like this particular instance may just be a case of it needing to be updated first; see below posts).