For anyone curious (like I was) the reason this is happening is that the legacy launcher installed to /opt/minecraft (least when I originally installed it via the Debian package). The new launcher (installed the same ) places files in /opt/minecraft-launcher.
At the time I (and probably many others) made a symbolic link to the minecraft.sh script. By doing so no matter how many times I upgraded I always ran the old version. I (and likely others) never thought this is was problem because us Linux folks are used to never having updates to programs especially with past MS history (imagine the egg on my face).
I fixed the problem by downloading the latest Debian package from the download page, Installed it, and re-pointing my symlink to the new executable:
Devin Weaver
For anyone curious (like I was) the reason this is happening is that the legacy launcher installed to
/opt/minecraft(least when I originally installed it via the Debian package). The new launcher (installed the same ) places files in/opt/minecraft-launcher.At the time I (and probably many others) made a symbolic link to the
minecraft.shscript. By doing so no matter how many times I upgraded I always ran the old version. I (and likely others) never thought this is was problem because us Linux folks are used to never having updates to programs especially with past MS history (imagine the egg on my face).I fixed the problem by downloading the latest Debian package from the download page, Installed it, and re-pointing my symlink to the new executable: