Wireshark-bugs: [Wireshark-bugs] [Bug 13113] Preference udp.port has already been registered
Date: Thu, 10 Nov 2016 14:09:32 +0000

Comment # 5 on bug 13113 from
(In reply to Michael Mann from comment #4)
> (In reply to Marko Hrastovec from comment #0)
> > Build Information:
> > TShark (Wireshark) 2.0.2 (SVN Rev Unknown from unknown)
> > 
> > I am compiling the latest git version.
> These two things seems to be in disagreement, but this issue is certainly
> more possible on the current master branch.

Oops. You are right. I forgot to use the right path when calling tshark and
then the version installed with packages was called. The correct one is:

TShark (Wireshark) 2.3.0 (v2.3.0rc0-1430-g7531318)

Copyright 1998-2016 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with libpcap, without POSIX capabilities, without libnl, with
GLib 2.48.1, with zlib 1.2.8, with SMI 0.4.8, with c-ares 1.10.0, with Lua
5.1.5, with GnuTLS 3.4.10, with Gcrypt 1.6.5, with MIT Kerberos, with GeoIP,
without nghttp2, without LZ4, without Snappy.

Running on Linux 4.4.0-45-generic, with Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
(with SSE4.2), with 15928 MB of physical memory, with locale
LC_CTYPE=en_US.UTF-8, LC_NUMERIC=sl_SI.UTF-8, LC_TIME=sl_SI.UTF-8,
LC_COLLATE=en_US.UTF-8, LC_MONETARY=sl_SI.UTF-8, LC_MESSAGES=en_US.UTF-8,
LC_PAPER=sl_SI.UTF-8, LC_NAME=sl_SI.UTF-8, LC_ADDRESS=sl_SI.UTF-8,
LC_TELEPHONE=sl_SI.UTF-8, LC_MEASUREMENT=sl_SI.UTF-8,
LC_IDENTIFICATION=sl_SI.UTF-8, with libpcap version 1.7.4, with GnuTLS 3.4.10,
with Gcrypt 1.6.5, with zlib 1.2.8.

Built using gcc 5.4.0 20160609.

> Do you have any custom plugins?  Do you primarily just work with ASTERIX?

No. I do not have any custom plugins. I use wireshark for ASTERIX most of the
time, but I use it for other protocols too.


You are receiving this mail because:
  • You are watching all bug changes.