This bug was already reported and fixed upstream at [1]. Wireshark as built from current SVN decodes the sample correctly.
Ubuntu will automatically pick up the fix when Wireshark releases 1.8 and we sync it in from Debian. If you want the fix in Precise, you can manually run a Wireshark development version, or you can ask the Wireshark devs to backport the fix into the stable 1.6 stream. Once there's a 1.6 release with the fix, you can ask the Ubuntu devs to pull the updated 1.6 package from Debian via an SRU [2]. Precise will not be receiving any 1.8 Wireshark packages, as they will not qualify for an SRU. Marking this bug as "Fix Committed" to denote that there is a known fix available upstream, but it has not made it into Ubuntu yet. Thanks, Evan [1] https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6115 [2] https://wiki.ubuntu.com/StableReleaseUpdates ** Bug watch added: Wireshark Bugzilla #6115 http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6115 ** Changed in: wireshark (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002142 Title: Can't decode OpenBSD 5.0 pflog files properly on Ubuntu 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/1002142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs