Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Wireshark segmentation fault

  1. #1
    Junior Member
    Join Date
    Feb 2015
    Posts
    6

    Wireshark segmentation fault

    I'm getting a Wireshark seg fault when I tried to execute the application today.

    System fully updated running in VMWare 12.1.
    Host is Windows 10 Home x64

    This is a Kali 2016.2 XFCE version with the awesome g0tmi1k post install script. Machine running great for the last 12 months.

    Details:
    Code:
    [root:/]# uname -a
    Linux kali 4.6.0-kali1-amd64 #1 SMP Debian 4.6.4-1kali1 (2016-07-21) x86_64 GNU/Linux
    [root:/]# cat /etc/*-release
    DISTRIB_ID=Kali
    DISTRIB_RELEASE=kali-rolling
    DISTRIB_CODENAME=kali-rolling
    DISTRIB_DESCRIPTION="Kali GNU/Linux Rolling"
    PRETTY_NAME="Kali GNU/Linux Rolling"
    NAME="Kali GNU/Linux"
    ID=kali
    VERSION="2016.2"
    VERSION_ID="2016.2"
    ID_LIKE=debian
    ANSI_COLOR="1;31"
    HOME_URL="http://www.kali.org/"
    SUPPORT_URL="http://forums.kali.org/"
    BUG_REPORT_URL="http://bugs.kali.org/"
    [root:/]# cat /proc/version 
    Linux version 4.6.0-kali1-amd64 (devel@kali.org) (gcc version 5.4.0 20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1kali1 (2016-07-21)
    [root:/]# cat /etc/issue
    Kali GNU/Linux Rolling \n \l

    Here's the gdb backtrace:

    [root:~/Downloads]# gdb /usr/bin/wireshark
    GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
    Copyright (C) 2016 Free Software Foundation, Inc.
    License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
    This is free software: you are free to change and redistribute it.
    There is NO WARRANTY, to the extent permitted by law. Type "show copying"
    and "show warranty" for details.
    This GDB was configured as "x86_64-linux-gnu".
    Type "show configuration" for configuration details.
    For bug reporting instructions, please see:
    <http://www.gnu.org/software/gdb/bugs/>.
    Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.
    For help, type "help".
    Type "apropos word" to search for commands related to "word"...
    Reading symbols from /usr/bin/wireshark...(no debugging symbols found)...done.
    (gdb) run
    Starting program: /usr/bin/wireshark
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
    [New Thread 0x7fffe1352700 (LWP 90217)]
    [New Thread 0x7fffdb7fd700 (LWP 90218)]
    [New Thread 0x7fffdaffc700 (LWP 90219)]
    [New Thread 0x7fffd8e36700 (LWP 90223)]
    [New Thread 0x7fffd17c7700 (LWP 90224)]
    [New Thread 0x7fffd0fc6700 (LWP 90225)]
    [New Thread 0x7fffcbfff700 (LWP 90226)]

    Thread 1 "wireshark" received signal SIGSEGV, Segmentation fault.
    0x00007ffff0ab175b in wtap_encap_string () from /usr/lib/x86_64-linux-gnu/libwiretap.so.6
    (gdb) bt
    #0 0x00007ffff0ab175b in wtap_encap_string () from /usr/lib/x86_64-linux-gnu/libwiretap.so.6
    #1 0x00007ffff445af9d in ?? () from /usr/lib/x86_64-linux-gnu/libwireshark.so.8
    #2 0x00007ffff4ccf38f in register_all_protocols () from /usr/lib/x86_64-linux-gnu/libwireshark.so.8
    #3 0x00007ffff4172868 in ?? () from /usr/lib/x86_64-linux-gnu/libwireshark.so.8
    #4 0x00007ffff414ddc7 in epan_init () from /usr/lib/x86_64-linux-gnu/libwireshark.so.8
    #5 0x00005555556a26fa in main ()
    (gdb)
    Already tried to remove and resintall with no luck.

    Any idea what to try?

    Thanks a lot.
    Last edited by hopes; 2017-03-18 at 07:53 AM. Reason: Added system details as per the rules

  2. #2
    Junior Member
    Join Date
    Mar 2017
    Posts
    6
    Hi,

    same with me. Fully updated, running on Lenovo Thinkpad.
    Segmentation fault, with /var/log/messages saying:

    Mar 13 16:40:08 kali kernel: [ 64.353472] wireshark[1477]: segfault at 0 ip 00007efd9477c75b sp 00007ffca9924440 error 4 in libwiretap.so.6.0.4[7efd9473a000+67000]
    Code:
    root@kali:~# uname -a
    Linux kali 4.6.0-kali1-amd64 #1 SMP Debian 4.6.4-1kali1 (2016-07-21) x86_64 GNU/Linux
    root@kali:~# cat /etc/*-release
    DISTRIB_ID=Kali
    DISTRIB_RELEASE=kali-rolling
    DISTRIB_CODENAME=kali-rolling
    DISTRIB_DESCRIPTION="Kali GNU/Linux Rolling"
    PRETTY_NAME="Kali GNU/Linux Rolling"
    NAME="Kali GNU/Linux"
    ID=kali
    VERSION="2016.2"
    VERSION_ID="2016.2"
    ID_LIKE=debian
    ANSI_COLOR="1;31"
    HOME_URL="http://www.kali.org/"
    SUPPORT_URL="http://forums.kali.org/"
    BUG_REPORT_URL="http://bugs.kali.org/"
    root@kali:~# cat /proc/version
    Linux version 4.6.0-kali1-amd64 (devel@kali.org) (gcc version 5.4.0 20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1kali1 (2016-07-21)
    root@kali:~# cat /etc/issue
    Kali GNU/Linux Rolling \n \l
    Last edited by mec; 2017-03-18 at 03:41 PM.

  3. #3
    Junior Member
    Join Date
    Mar 2017
    Posts
    1
    Hello guys,
    Please, i booted Kali (virtual box image) successfully. But when i tried to launch wireshark ( command line / gui) i received an error of Segmentation fault. Though, the screen flickers as if it would launch but nothing shows.
    Thanks.

    Host: Windows 10 / HP Zbook core i7 32gb ram nvidia quadro k3100
    Virtual Machine: VirtualBox
    Guest: Kali linux..latest

  4. #4
    Junior Member
    Join Date
    Mar 2017
    Posts
    6
    Hi,

    although there was an update for wireshark and libraries today, which made me confident, unfortunately it still does not work. Anyone ideas?

  5. #5
    Senior Member
    Join Date
    Apr 2013
    Location
    in a computer
    Posts
    520
    Wireshark is working fine for me. Granted, I haven't updated Kali in a few days. Here's a screenshot of the Help/About.about.jpg

  6. #6
    Junior Member
    Join Date
    Feb 2015
    Posts
    6
    I think we definitely have something broken with our setup cause I tried with a couple of other installs and everything works just fine.
    Now the point is trying to understand what is broken...

    p.s. added my system details in the first post as per admin request. Sorry to not have followed the rules.

  7. #7
    Junior Member
    Join Date
    Mar 2013
    Posts
    10
    I would update if I were you then see if it fixes itself. You are defiantly not fully updated.

    Code:
    root@Pihole_kali:~# uname -a
    Linux Pihole_kali 4.9.0-kali3-686-pae #1 SMP Debian 4.9.13-1kali3 (2017-03-13) i686 GNU/Linux
    root@Pihole_kali:~# cat /etc/*-release
    DISTRIB_ID=Kali
    DISTRIB_RELEASE=kali-rolling
    DISTRIB_CODENAME=kali-rolling
    DISTRIB_DESCRIPTION="Kali GNU/Linux Rolling"
    PRETTY_NAME="Kali GNU/Linux Rolling"
    NAME="Kali GNU/Linux"
    ID=kali
    VERSION="2016.2"
    VERSION_ID="2016.2"
    ID_LIKE=debian
    ANSI_COLOR="1;31"
    HOME_URL="http://www.kali.org/"
    SUPPORT_URL="http://forums.kali.org/"
    BUG_REPORT_URL="http://bugs.kali.org/"
    root@Pihole_kali:~# cat /proc/version
    Linux version 4.9.0-kali3-686-pae (devel@kali.org) (gcc version 6.3.0 20170205 (Debian 6.3.0-6) ) #1 SMP Debian 4.9.13-1kali3 (2017-03-13)root@Pihole_kali:~#
    Update with this
    Code:
    apt clean && apt update && apt -y upgrade && apt -y dist-upgrade && apt autoclean
    You might have to use apt-get not sure if 4.6 could use apt.
    Last edited by sml156; 2017-03-20 at 05:36 AM.

  8. #8
    Junior Member
    Join Date
    Mar 2017
    Posts
    6
    Wow! Dist-upgrade indeed worked, thank you very much!
    As I had downloaded the iso just recently I had thought to have the latest version. Anyhow, wireshark now is running. :-)

  9. #9
    Junior Member
    Join Date
    Mar 2017
    Posts
    1
    Quote Originally Posted by sml156 View Post
    ...

    Update with this
    Code:
    apt clean && apt update && apt -y upgrade && apt -y dist-upgrade && apt autoclean
    You might have to use apt-get not sure if 4.6 could use apt.
    Fixed it for me too, thank you. I had also recently installed fresh from rolling repository but this caught quite a few things to update.

  10. #10
    Junior Member
    Join Date
    Feb 2015
    Posts
    6
    Thanks a lot!
    It worked for me too.
    I missed we updated to kernel 4.9
    Up and running again.
    Cheers
    wireshark.jpg

Posting Permissions

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