Results 1 to 8 of 8

Thread: Cisco Packet Tracer, Segmentation Fault

  1. #1

    Default Cisco Packet Tracer, Segmentation Fault

    Hi.
    I'm trying to run Cisco Packet tracer on my openSuse 42.2 . But I've faced with the following error :

    Code:
    /usr/local/bin/packettracer: line 8: 16067 Segmentation fault      (core dumped) ./PacketTracer7 "$@" > /dev/null 2>&1
    and the contents of /usr/local/bin/packettracer are as follow:

    Code:
    #!/bin/bash 
    
    echo Starting Packet Tracer 7.0 
    
    PTDIR=/opt/pt 
    export LD_LIBRARY_PATH=$PTDIR/lib 
    pushd $PTDIR/bin > /dev/null 
    ./PacketTracer7 "$@" > /dev/null 2>&1 
    popd > /dev/null
    
    I could run exactly the same version on a Ubuntu system.
    Please guide me how I can fix this.
    Thanks

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,721

    Default Re: Cisco Packet Tracer, Segmentation Fault

    It loooks a s if the program PacketTracer7 is segfaulting.
    Where did you install it from?
    Henk van Velden

  3. #3
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    10,806
    Blog Entries
    1

    Default Re: Cisco Packet Tracer, Segmentation Fault

    It's very likely the app was coded improperly, perhaps with a fixed path instead of a variable path somewhere.

    This is something you have to write to the app's authors (Cisco).
    And then it would depend on whether Cisco has any interest in their app running on any other distro than Ubuntu (and possibly Debian).

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  4. #4
    Join Date
    Mar 2013
    Location
    Nicaragua
    Posts
    25

    Default Re: Cisco Packet Tracer, Segmentation Fault

    Hello,

    I am facing the same issue.
    Taking a look to an strace against the packet tracer shows they are looking for a lot of non-existing files on openSUSE.
    I am using tumbleweed and tried making symlinks to the right patch of locale files and others but the result is the same, segfault.

    Any other debug tool you recommend?

    Regards

  5. #5
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    10,806
    Blog Entries
    1

    Default Re: Cisco Packet Tracer, Segmentation Fault

    Quote Originally Posted by altmas5 View Post
    Hello,

    I am facing the same issue.
    Taking a look to an strace against the packet tracer shows they are looking for a lot of non-existing files on openSUSE.
    I am using tumbleweed and tried making symlinks to the right patch of locale files and others but the result is the same, segfault.

    Any other debug tool you recommend?

    Regards
    1. For at least a sampling of errors, you should inspect the exact line referenced to verify what I wrote in my prior post... That commands are hardcoded pointing to locations and not using a relative path. If you find this to be the case, then you can try symlinking the locations or complain to Cisco (I'd highly recommend).

    2. You can search for actual locations of files using the Find utility which is typically installed by default, but it's much faster to use the locate utility instead. You can install and configure as follows

    Install
    Code:
    zypper in mlocate
    Populate the locate database. This only has to be done initially, and later if you ever do anything and then want to search within 24 hrs of that change... Otherwise, the database will update automatically daily. In a root console, run the following
    Code:
    updatedb
    Now you're ready to cook. You can now search for any text string which might be just the file name or including a path or partial path
    Code:
    locate filename 
    HTH,
    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  6. #6

    Default Re: Cisco Packet Tracer, Segmentation Fault

    Quote Originally Posted by tsu2 View Post
    1. For at least a sampling of errors, you should inspect the exact line referenced to verify what I wrote in my prior post... That commands are hardcoded pointing to locations and not using a relative path. If you find this to be the case, then you can try symlinking the locations or complain to Cisco (I'd highly recommend).

    2. You can search for actual locations of files using the Find utility which is typically installed by default, but it's much faster to use the locate utility instead. You can install and configure as follows

    Install
    Code:
    zypper in mlocate
    Populate the locate database. This only has to be done initially, and later if you ever do anything and then want to search within 24 hrs of that change... Otherwise, the database will update automatically daily. In a root console, run the following
    Code:
    updatedb
    Now you're ready to cook. You can now search for any text string which might be just the file name or including a path or partial path
    Code:
    locate filename 
    HTH,
    TSU

    If you run the commands manualy

    linux-0f26:~> PTDIR=/opt/pt
    linux-0f26:~> export LD_LIBRARY_PATH=/opt/pt/lib
    linux-0f26:~> LD_LIBRARY_PATH=/opt/pt/lib
    linux-0f26:~> pushd /opt/pt/bin
    /opt/pt/bin ~
    linux-0f26:/opt/pt/bin> ./PacketTracer7


    You'll find that it fails with a known bug ...

    Warning: QMainWindow::addDockWidget: invalid 'area' argument
    Debug: CAnalyticsTracker::finished_request() - OK - url: "http://www.google-analytics.com/collect"
    Debug: CAnalyticsTracker::finished_request() - OK - data: "ec=app&ea=track&el=session&ev=1&sc=start&t=event&v=1&tid=UA-56074537-2&cid=907fa53d-8190-4298-a45d-0b414398d902&aiid=907fa53d-8190-4298-a45d-0b414398d902&an=Cisco%20Packet%20Tracer&av=7.0.0.0306&cd1=os_name:linux&ni=1"
    Debug: CAnalyticsTracker::finished_request() - OK - url: "http://www.google-analytics.com/collect"
    Debug: CAnalyticsTracker::finished_request() - OK - data: "ec=app&ea=track&el=init&ev=0&t=event&v=1&tid=UA-56074537-2&cid=907fa53d-8190-4298-a45d-0b414398d902&aiid=907fa53d-8190-4298-a45d-0b414398d902&an=Cisco%20Packet%20Tracer&av=7.0.0.0306&cd1=os_name:linux&ni=1"
    Debug: CAnalyticsTracker::finished_request() - OK - url: "http://www.google-analytics.com/collect"
    Debug: CAnalyticsTracker::finished_request() - OK - data: "ec=app&ea=track-screen&el=logical-workspace&ev=0&t=event&v=1&tid=UA-56074537-2&cid=907fa53d-8190-4298-a45d-0b414398d902&aiid=907fa53d-8190-4298-a45d-0b414398d902&an=Cisco%20Packet%20Tracer&av=7.0.0.0306&cd1=os_name:linux"
    Debug: CAnalyticsTracker::finished_request() - OK - url: "http://analytics01.cisco.netacad.com/Service02/analytics/v1/heartbeat3/{907fa53d-8190-4298-a45d-0b414398d902}/linux/ptdesktop/7.0.0.0306/app^track-screen^logical-workspace^0/"
    Debug: CAnalyticsTracker::finished_request() - OK - data: ""
    Debug: CAnalyticsTracker::finished_request() - OK - url: "http://analytics01.cisco.netacad.com/Service02/analytics/v1/heartbeat3/{907fa53d-8190-4298-a45d-0b414398d902}/linux/ptdesktop/7.0.0.0306/app^track^session^1/"
    Debug: CAnalyticsTracker::finished_request() - OK - data: ""
    Debug: CAnalyticsTracker::finished_request() - OK - url: "http://analytics01.cisco.netacad.com/Service02/analytics/v1/heartbeat3/{907fa53d-8190-4298-a45d-0b414398d902}/linux/ptdesktop/7.0.0.0306/app^track^init^0/"
    Debug: CAnalyticsTracker::finished_request() - OK - data: ""

    (PacketTracer7:19277): GLib-GObject-WARNING **: cannot register existing type 'GdkDisplayManager'

    (PacketTracer7:19277): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

    (PacketTracer7:19277): GLib-GObject-CRITICAL **: g_object_new: assertion 'G_TYPE_IS_OBJECT (object_type)' failed

    (PacketTracer7:19277): GLib-GObject-WARNING **: invalid (NULL) pointer instance

    (PacketTracer7:19277): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

    (PacketTracer7:19277): GLib-GObject-WARNING **: invalid (NULL) pointer instance

    (PacketTracer7:19277): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

    (PacketTracer7:19277): GLib-GObject-WARNING **: cannot register existing type 'GdkDisplay'

    (PacketTracer7:19277): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

    (PacketTracer7:19277): GLib-GObject-CRITICAL **: g_type_register_static: assertion 'parent_type > 0' failed

    (PacketTracer7:19277): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

    (PacketTracer7:19277): GLib-GObject-CRITICAL **: g_object_new: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
    Segmentation fault (core dumped)

  7. #7
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,301
    Blog Entries
    15

    Default Re: Cisco Packet Tracer, Segmentation Fault

    Hi
    Just installed it here and working fine on openSUSE 42.2 (Gnome), if in the extracted tarball as you user, run ldd against the binary in the bin directory, you might be missing a lib or too...

    I installed in my data directory rather than opt, that's about it....

    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  8. #8
    Join Date
    Mar 2013
    Location
    Nicaragua
    Posts
    25

    Default Re: Cisco Packet Tracer, Segmentation Fault

    Finally I installed packet tracer 6.3.
    I wasn't able to get packet tracer 7 running on opensuse Tumbleweed.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •