Does anyone have any idea how to get Cisco Packet Tracer running as was mentioned in the December blog?
[Beyond Gaming: X11 bridging in muvm - Asahi Linux]
It’s distributed as a .deb file and I’ve tried turning it into an appimage as well as a flatpak and had no luck getting either to run.
Any help is greatly appreciated as I enjoy studying on my macbook air vs
my older and heavier hardware.
Thanks!
Edit: In case anyone else is in a similar boat, I got it working by using this script [GitHub - thiagoojack/packettracer-fedora: Easily install Cisco Packet Tracer latest version on Fedora.] then tried “muvm packettracer” in the terminal and it launched. After that I edited the application launcher shortcut to “/usr/bin/muvm” with “packettracer” as the command line argument so I could launch it from there.
(Please read the comments after the commands, they are part of the instructions and contain necessary info to make this setup work!)
cd ~/Downloads/
ar x CiscoPacketTracer_900_Ubuntu_64bit.deb
tar xf
tar xf data.tar.xz
muvm -- FEXBash bash # for some reason for me it stalls and I have to press `C-C`. It still works for me after that though.
cd ~/Downloads/opt/pt
./packettracer.AppImage --appimage-extract
dnf download --repo=fedora --repo=updates --forcearch=x86_64 --best libxkbfile
rpmdev-extract libxkbfile-1.1.3-3.fc42.x86_64.rpm
echo export LD_LIBRARY_PATH=\$LD_LIBRARY_PATH:$(realpath libxkbfile-1.1.3-3.fc42.x86_64/usr/lib64/) # save the line outputted for later
./packettracer.AppImage --appimage-extract
#### run this particular line in another terminal (so without being inside VM)
xdg-open squashfs-root/AppRun # search for `export LD_LIBRARY_PATH` in the file that was opened. Right after that line add the line you saved for later.
####
./squashfs-root/AppRun
The app should now open. Please do comment to help improve this!
I currently scale the screen to 250% on my device, and packet tracer fonts are a little small when it opens. I changed the font size in packettracer preferences, although you can run commands inside muvm before starting it, so it is probably possible to scale the x11 display inside muvm instead to the same value (250% in my case), which could improve app resizing quirks.