[Wireshark-bugs] [Bug 14350] When using R13 CIoT attach, Wireshark shows Attach Accept and Create Session Response messages partially as "Malformed Packet".

2018-01-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14350 Pascal Quantin changed: What|Removed |Added Status|UNCONFIRMED

[Wireshark-bugs] [Bug 14350] New: When using R13 CIoT attach, Wireshark shows Attach Accept and Create Session Response messages partially as "Malformed Packet".

2018-01-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14350 Bug ID: 14350 Summary: When using R13 CIoT attach, Wireshark shows Attach Accept and Create Session Response messages partially as "Malformed Packet". Product:

[Wireshark-bugs] [Bug 14349] New: Closing Enabled Protocols dialog crashes wireshark

2018-01-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14349 Bug ID: 14349 Summary: Closing Enabled Protocols dialog crashes wireshark Product: Wireshark Version: 2.4.2 Hardware: x86 OS: Solaris Status: UNCONFIRMED

[Wireshark-bugs] [Bug 14345] When reading from a pipe and using -l, TShark doesn't print packets as soon as they're written to the pipe

2018-01-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14345 Guy Harris changed: What|Removed |Added Summary|tshark packet dissection|When reading from

[Wireshark-bugs] [Bug 14345] tshark packet dissection from pipe: buffers input

2018-01-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14345 Guy Harris changed: What|Removed |Added Hardware|x86 |All Ever

[Wireshark-bugs] [Bug 14345] tshark packet dissection from pipe: buffers input

2018-01-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14345 --- Comment #3 from Christopher Maynard --- (In reply to Ralph from comment #2) > No. According to Guy on wireshark-users: > > > And the actual issue is in the low-level code (*very* low-level code) in > >

[Wireshark-bugs] [Bug 14345] tshark packet dissection from pipe: buffers input

2018-01-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14345 --- Comment #2 from Ralph --- No. According to Guy on wireshark-users: > And the actual issue is in the low-level code (*very* low-level code) in > libwiretap that TShark uses to read the capture; that code

[Wireshark-bugs] [Bug 14345] tshark packet dissection from pipe: buffers input

2018-01-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14345 --- Comment #1 from Christopher Maynard --- (In reply to Ralph from comment #0) > According to Guy on the mailing list, this is due to the *input* of tshark > being buffered. Would the use of stdbuf help

[Wireshark-bugs] [Bug 14348] "Clear" button changes filter input dialog background to grey color

2018-01-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14348 --- Comment #5 from Geoff Goas --- Created attachment 16079 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16079=edit Text can no longer be highlighted -- You are receiving this mail because: You are

[Wireshark-bugs] [Bug 14348] "Clear" button changes filter input dialog background to grey color

2018-01-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14348 --- Comment #4 from Geoff Goas --- Created attachment 16078 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16078=edit After the Clear button has been pressed -- You are receiving this mail because: You are

[Wireshark-bugs] [Bug 14348] "Clear" button changes filter input dialog background to grey color

2018-01-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14348 --- Comment #3 from Geoff Goas --- Created attachment 16077 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16077=edit Shows how the text looks when highlighted -- You are receiving this mail because: You

[Wireshark-bugs] [Bug 14348] "Clear" button changes filter input dialog background to grey color

2018-01-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14348 --- Comment #2 from Geoff Goas --- Created attachment 16076 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16076=edit Shows some text in the dialog -- You are receiving this mail because: You are watching

[Wireshark-bugs] [Bug 14348] "Clear" button changes filter input dialog background to grey color

2018-01-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14348 --- Comment #1 from Geoff Goas --- Created attachment 16075 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16075=edit Status immediately after application start -- You are receiving this mail because: You

[Wireshark-bugs] [Bug 14348] New: "Clear" button changes filter input dialog background to grey color

2018-01-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14348 Bug ID: 14348 Summary: "Clear" button changes filter input dialog background to grey color Product: Wireshark Version: 2.4.3 Hardware: x86 OS: Linux

[Wireshark-bugs] [Bug 14347] GlusterFS: Add support for GETVOLUMEINFO procedure

2018-01-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14347 Prashanth Pai changed: What|Removed |Added Ever confirmed|0 |1

[Wireshark-bugs] [Bug 14347] New: GlusterFS: Add support for GETVOLUMEINFO procedure

2018-01-16 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14347 Bug ID: 14347 Summary: GlusterFS: Add support for GETVOLUMEINFO procedure Product: Wireshark Version: Git Hardware: x86 OS: Linux Status: UNCONFIRMED