Package: wireshark
Version: 2.6.9-1
Severity: minor

I've got a capture file going 1031 seconds, 2.7GB.

When running the TCP connection statistics and sorting by "duration", I get 
different answers; once I got 1031 (as expected), after a wireshark restart 
with the same file I only got 820 or so.

Once I tried clicking "limit to display filter" (no filter was set!),  that
had the effect of recalculating and giving a different result.


Furthermore, checking "absolute time" isn't honored in the CSV export;  the
header field correctly says "Abs time",  but the numbers are still relative
to the beginning (ie. decimal numbers >=0, instead of 12:01:55 etc.).


I got a message that a 3.0.2 package is NEW (incoming), but I couldn't 
download that anywhere to test. Will do as soon as I see it.


-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.0.0-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_AT:de (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wireshark depends on:
ii  wireshark-qt  2.6.8-1.1

wireshark recommends no packages.

wireshark suggests no packages.

-- no debconf information

-- 

Reply via email to