FS#19769 - [wireshark] capture stops

Attached to Project: Arch Linux
Opened by Byron Clark (byronc) - Friday, 11 June 2010, 18:01 GMT
Last edited by Ionut Biru (wonder) - Saturday, 19 February 2011, 19:27 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Ionut Biru (wonder)
Guillaume ALAUX (galaux)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After I start a capture in wireshark, I see a few packets, but then no more packets seem to be captured. When this happens, I see messages like this in the terminal where I ran wireshark:

11:56:29 Warn Error "Less data was read than was expected" while reading: "/tmp/wiresharkXXXXOKjpO5"

11:56:30 Warn Error "File contains a record that's not valid" while reading: "/tmp/wiresharkXXXXOKjpO5"

11:56:31 Warn Error "File contains a record that's not valid" while reading: "/tmp/wiresharkXXXXOKjpO5"

11:56:32 Warn Error "File contains a record that's not valid" while reading: "/tmp/wiresharkXXXXOKjpO5"

11:56:33 Warn Error "File contains a record that's not valid" while reading: "/tmp/wiresharkXXXXOKjpO5"

11:56:34 Warn Error "File contains a record that's not valid" while reading: "/tmp/wiresharkXXXXOKjpO5"

11:56:35 Warn Error "File contains a record that's not valid" while reading: "/tmp/wiresharkXXXXOKjpO5"

11:56:36 Warn Error "File contains a record that's not valid" while reading: "/tmp/wiresharkXXXXOKjpO5"


Additional info:
* package version(s)
wireshark 1.2.9-1

Steps to reproduce:
- Open wireshark
- Start capturing on an interface
This task depends upon

Closed by  Ionut Biru (wonder)
Saturday, 19 February 2011, 19:27 GMT
Reason for closing:  Fixed
Additional comments about closing:  is fixed in our current package. we have to be carefully in the future
Comment by Ionut Biru (wonder) - Friday, 11 June 2010, 18:30 GMT
i guess the zlib bug wasn't fixed 100%.

http://bugs.archlinux.org/task/19547

please report this upstream again
Comment by Byron Clark (byronc) - Tuesday, 29 June 2010, 18:46 GMT
Reported upstream: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4955
Comment by Gerardo Exequiel Pozzi (djgera) - Saturday, 03 July 2010, 19:19 GMT
  • Field changed: Status (Unconfirmed → Assigned)
  • Field changed: Category (Packages: Extra → Upstream Bugs)
  • Task assigned to Ionut Biru (wonder)
Assigned to the latest packager.
Comment by Ionut Biru (wonder) - Sunday, 05 September 2010, 18:19 GMT
still an issue with wireshark 1.4.0 ?
Comment by Byron Clark (byronc) - Monday, 06 September 2010, 18:30 GMT
Still happens with 1.4.0.
Comment by Ionut Biru (wonder) - Monday, 20 September 2010, 21:07 GMT
this can be solved with recompiling the package with --without-zlib

we had this issue in the past but it was somehow fixed

Loading...