I think there is a bug somewhere. It can be in GIMX, in the system, or in a shared library used by GIMX.
Is your Ubuntu system up-to-date? To make sure you are running the latest software, run in a terminal:
Any time I go more than a few days without turning the box on, I give it 10-15 minutes to check for updates before I fire up GIMX. It usually updates at least a few things.
I think it auto-updated before I ran the GIMX update, but I will force it to update.
After that should I allow GIMX to update automatically and update the firmware to see if I can get 4.2 to run?
1) Ran sudo apt-get update && sudo apt-get upgrade - Ubuntu did update a few things
2) Tested GIMX 3.5 - Works correctly
3) Reset Teensy to baseline condition by installing blink_slow_Teensy2.hex
4) Installed GIMX firmware (/firmwares-4.1/EMUPS3/atmega32u4.hex)
5) Ran GIMX and allowed update to run
6) Powered off PC & PS3, reconnected all cables, powered on PC & PS3.
7) Ran GIMX 4.2-1 - Does not work
At this point, I ran the jstest-gtk loopback test and I was seeing commands so I just started trying to eliminate things. After rebooting many times, I get the following results:
1) Running GIMX 4.2-1 from the launcher will not work for me at all - Tested & repeated
2) Running GIMX 4.2-1 from the command line works every time - Tested & repeated
3) If I run GIMX from the command line and then close the terminal window, I can run GIMX from the launcher - Tested & repeated
Does the launcher do something different than when you run GIMX from the command line?
I can reproduce the issue, it turns out I wasn't using gimx-launcher, which adds the --force-updates argument.
When adding the --force-updates argument, it also fails from the terminal.
Since I wasn't able to quickly fix the EMUPS3 firmware, I took the decision to disable the force-update when the EMUPS3 firmware is detected. This temporary fix is included in GIMX 4.3.