The following tutorial is the result of my successful installation attempt for Packet Tracer 7.3.0 on an openSUSE Tumbleweed. State of the openSUSE packages was around December, 2019. For other Linux distributions you have to look whether this works the same way. Especially the needed and already available libraries might differ in your system.<\/p>\n\n\n\n
Why was this necessary at all? Well … Cisco always only supported the Ubuntu distribution of Linux, although they always delivered the software with an installer, and not as .deb. or .rpm-package. Obviously Cisco now decided to go one step further, and to stop the development of the generic Linux installer. Instead they only deliver a DEB-package, that can not be installed directly on a lot of other Linux-distributions, especially not on RPM-based distributions. And for Packet Tracer 7.3.0 Cisco also says that the software is only for Ubuntu 18.04.03 LTS.<\/p>\n\n\n\n
It is of course also possible to look for Disclaimer:<\/strong> Although I have tried to document all procedures properly, I do not take any responsibility for this tutorial.<\/p>\n\n\n\n It is assumed that you have the old installation in We are still in the directory Lines to have in To get these settings active on your workstation, log off and log in again. Settings in the startup profiles, are then automatically done. Control them with the commands If PT is still not starting after all this, you should have a deeper look what’s wrong with the installation. For this, go to Then, still from a command line shell, go again to the directory The above output seems to be the „normal“ output of a working Packet Tracer. If anything else is shown, try to interpret the problem or send the output to someone for help.<\/p>\n","protected":false},"excerpt":{"rendered":" The following tutorial is the result of my successful installation attempt for Packet Tracer 7.3.0 on an openSUSE Tumbleweed. State of the openSUSE packages was around December, 2019. For other Linux distributions you have to look whether this works the same way. Especially the needed and already available libraries might differ in your system. Why … Weiterlesen<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[18,19],"class_list":["post-1624","post","type-post","status-publish","format-standard","hentry","category-allgemein","tag-cisco-systems-packet-tracer","tag-opensuse-tumbleweed"],"_links":{"self":[{"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/posts\/1624","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/comments?post=1624"}],"version-history":[{"count":11,"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/posts\/1624\/revisions"}],"predecessor-version":[{"id":1708,"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/posts\/1624\/revisions\/1708"}],"wp:attachment":[{"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/media?parent=1624"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/categories?post=1624"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/grupp-web.de\/cms\/wp-json\/wp\/v2\/tags?post=1624"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}alien<\/code>, a tool to install DEB-packets on RPM-based systems. But as alien<\/code> is not in the standard repos for openSUSE Tumbleweed, and I also wanted to see for myself once the inside mechanisms of a DEB-packet, I did this work that might work on several RPM-based distributions.<\/p>\n\n\n\nUnpack DEB-file for Packet Tracer<\/h2>\n\n\n\n
mkdir \/tmp\/PacketTracerInst\ncp PacketTracer_730_amd64.deb \/tmp\/PacketTracerInst\ncd \/tmp\/PacketTracerInst\nar -xv PacketTracer_730_amd64.deb\nmkdir control\ntar -C control -Jxf control.tar.xz\nmkdir data\ntar -C data -Jxf data.tar.xz\ncd data<\/code><\/pre>\n\n\n\nRemove current PT installation<\/h2>\n\n\n\n
\/opt\/pt<\/code><\/p>\n\n\n\nrm -rf \/opt\/pt\nrm -rf \/usr\/share\/applications\/cisco-pt7.desktop\nrm -rf \/usr\/share\/applications\/cisco-ptsa7.desktop\nrm -rf \/usr\/share\/icons\/hicolor\/48x48\/apps\/pt7.png\nxdg-desktop-menu uninstall \/usr\/share\/applications\/cisco-pt7.desktop\nxdg-desktop-menu uninstall \/usr\/share\/applications\/cisco-ptsa7.desktop\nupdate-mime-database \/usr\/share\/mime\ngtk-update-icon-cache --force \/usr\/share\/icons\/gnome\nrm -f \/usr\/local\/bin\/packettracer<\/code><\/pre>\n\n\n\nInstallation of new PT-files<\/h2>\n\n\n\n
\/tmp\/PacketTracerInst\/data<\/code><\/p>\n\n\n\ncp -r usr \/\ncp -r opt \/<\/code><\/pre>\n\n\n\nIn openSUSE-Tumbleweed – symlink for a needed library<\/h2>\n\n\n\n
ln -s \/usr\/lib64\/libdouble-conversion.so.3.1.5 \/usr\/lib64\/libdouble-conversion.so.1<\/code><\/pre>\n\n\n\nAfter the installation of files, update icon and file assocation<\/h2>\n\n\n\n
sudo xdg-desktop-menu install \/usr\/share\/applications\/cisco-pt7.desktop\nsudo xdg-desktop-menu install \/usr\/share\/applications\/cisco-ptsa7.desktop\nsudo update-mime-database \/usr\/share\/mime\nsudo gtk-update-icon-cache --force --ignore-theme-index \/usr\/share\/icons\/gnome\nsudo xdg-mime default cisco-ptsa7.desktop x-scheme-handler\/pttp<\/code><\/pre>\n\n\n\nSymlink to PT-starter<\/h2>\n\n\n\n
sudo ln -sf \/opt\/pt\/packettracer \/usr\/local\/bin\/packettracer<\/code><\/pre>\n\n\n\nEnvironment settings<\/h2>\n\n\n\n
\/etc\/profile<\/code>, or if supported the preferred placement is in \/etc\/profile.local<\/code><\/p>\n\n\n\nPT7HOME=\/opt\/pt\nexport PT7HOME\nQT_DEVICE_PIXEL_RATIO=auto\nexport QT_DEVICE_PIXEL_RATIO<\/code><\/pre>\n\n\n\necho $PT7HOME<\/code> and echo $QT_DEVICE_PIXEL_RATIO<\/code> in a command line shell. You should see the above values!<\/p>\n\n\n\nPT still not working?<\/h2>\n\n\n\n
\/opt\/pt<\/code> and copy the text-file packettracer<\/code>, already available in this place, to a file ptdebug<\/code>. This can for example be done by using the command cp -p \/opt\/pt\/packettracer \/opt\/pt\/ptdebug<\/code>. Then, in this new file, replace \/ remove all redirections in the last three lines. The redirections start with a greater sign ><\/code>. Including the ><\/code> remove the rest of the line. The relevant lines in the file should now be:<\/p>\n\n\n\n#!\/bin\/bash\nPTDIR=\/opt\/pt\nexport LD_LIBRARY_PATH=\/opt\/pt\/bin\npushd \/opt\/pt\/bin\n.\/PacketTracer7 \"$@\"\npopd<\/code><\/pre>\n\n\n\n\/opt\/pt<\/code> and there enter the command .\/ptdebug<\/code>. In my situation, with a working PT installation, the output looks like this:<\/p>\n\n\n\nandreas@r-andreas:\/opt\/pt> .\/ptdebug \nStarting Packet Tracer 7.3.0\n\/opt\/pt\/bin \/opt\/pt\n.\/PacketTracer7: \/opt\/pt\/bin\/libcrypto.so.1.0.0: no version information available (required by .\/PacketTracer7)\nQt WebEngine ICU data not found at \/home\/ptbuild\/Desktop\/qt-5.12.4-ubuntu64-release-bin\/resources. Trying parent directory...\nQt WebEngine ICU data not found at \/home\/ptbuild\/Desktop\/qt-5.12.4-ubuntu64-release-bin. Trying application directory...\nInstalled Qt WebEngine locales directory not found at location \/home\/ptbuild\/Desktop\/qt-5.12.4-ubuntu64-release-bin\/translations\/qtwebengine_locales. Trying application directory...\nQt WebEngine resources not found at \/home\/ptbuild\/Desktop\/qt-5.12.4-ubuntu64-release-bin\/resources. Trying parent directory...\nQt WebEngine resources not found at \/home\/ptbuild\/Desktop\/qt-5.12.4-ubuntu64-release-bin. Trying application directory...\n<\/code><\/pre>\n\n\n\n