Wireshark-bugs: [Wireshark-bugs] [Bug 10672] New: SMPP does not display properly the hour field
Date: Thu, 06 Nov 2014 18:23:34 +0000
Bug ID 10672
Summary SMPP does not display properly the hour field in the Submit_sm Validity Period field
Product Wireshark
Version 1.12.1
Hardware x86-64
OS Ubuntu
Status UNCONFIRMED
Severity Minor
Priority Low
Component Qt UI
Assignee bugzilla-admin@wireshark.org
Reporter gusgonnet@gmail.com

Created attachment 13236 [details]
packet showing the fault

Build Information:
Version 1.12.1 (Git Rev Unknown from unknown)

Copyright 1998-2014 Gerald Combs <gerald@wireshark.org> and contributors.
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 GTK+ 3.10.8, with Cairo 1.13.1, with Pango 1.36.3, with
GLib 2.40.2, with libpcap, with libz 1.2.8, with POSIX capabilities (Linux),
without libnl, with SMI 0.4.8, with c-ares 1.10.0, with Lua 5.2, without
Python,
with GnuTLS 2.12.23, with Gcrypt 1.5.3, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Feb 25 2014 21:09:53), with AirPcap.

Running on Linux 3.13.0-39-generic, with locale en_US.UTF-8, with libpcap
version 1.5.3, with libz 1.2.8, GnuTLS 2.12.23, Gcrypt 1.5.3, without AirPcap.
Intel(R) Core(TM) i5 CPU       M 540  @ 2.53GHz

Built using gcc 4.8.2.

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
Wireshark seems to display a wrong hour of the Validity Period.

Example
what is displayed in the packet details:
Validity period: Oct 30, 2014 08:29:20.800000000 UTC

what is displayed in the packet bytes:
141030092920800+.

If I'm not mistaken the correct time to display should be 09:29:20 and not
08:29:20

Packet showing the fault attached.

In Windows version 1.06 this is not happening, the hour is displayed correctly
as 09:29:20.

thank you!
Gustavo.

PS: I am not sure exactly where the bug belongs, so I am filing this bug as an
UI bug.
Please correct me if it should be under a different component.


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