[Wireshark-bugs] [Bug 12853] New: File does not exist

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12853 Bug ID: 12853 Summary: File does not exist Product: Wireshark Version: 2.2.0 Hardware: x86 OS: Windows 7 Status: UNCONFIRMED Severity: Major

[Wireshark-bugs] [Bug 12854] New: Buildbot crash output: randpkt-2016-09-09-14931.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12854 Bug ID: 12854 Summary: Buildbot crash output: randpkt-2016-09-09-14931.pcap Product: Wireshark Version: unspecified Hardware: x86-64 URL:

[Wireshark-bugs] [Bug 12855] Follow TCP Stream shows duplicate stream data

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12855 --- Comment #1 from nobletr...@gmail.com --- Created attachment 14895 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=14895=edit screenshot of bug -- You are receiving this mail because: You are watching all bug changes.

[Wireshark-bugs] [Bug 11755] Unrecognized text: CDATA in XML not parsed correctly

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11755 Thomas W. changed: What|Removed |Added Status|RESOLVED|VERIFIED ---

[Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845 --- Comment #17 from Pavel Sindelka --- (In reply to Roland Knall from comment #13) > The number of interfaces should not be an issue, androiddump generates a lot > more. As one of the guys at ask.wireshark.org

[Wireshark-bugs] [Bug 12793] Expert Info ssl.resumed incorrect after TLS renegotiate

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12793 --- Comment #20 from Peter Wu --- (In reply to Andre Luyer from comment #18) > Maybe there is another way: in case of a resumed session both ServerHello > and ChangeCipherSpec will be in the same frame (so that frame

[Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845 --- Comment #18 from Roland Knall --- (In reply to Pavel Sindelka from comment #17) > (In reply to Roland Knall from comment #13) > > The number of interfaces should not be an issue, androiddump generates a lot > > more.

[Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845 --- Comment #19 from Pavel Sindelka --- (In reply to Roland Knall from comment #18) > (In reply to Pavel Sindelka from comment #17) > > (In reply to Roland Knall from comment #13) > > > The number of interfaces

[Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845 --- Comment #20 from Pavel Sindelka --- (In reply to Pavel Sindelka from comment #17) > (In reply to Roland Knall from comment #13) > > The number of interfaces should not be an issue, androiddump generates a lot

[Wireshark-bugs] [Bug 12855] New: Follow TCP Stream shows duplicate stream data

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12855 Bug ID: 12855 Summary: Follow TCP Stream shows duplicate stream data Product: Wireshark Version: 2.3.x (Experimental) Hardware: x86 OS: Mac OS X 10.11

[Wireshark-bugs] [Bug 12856] New: Buildbot crash output: randpkt-2016-09-09-31157.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12856 Bug ID: 12856 Summary: Buildbot crash output: randpkt-2016-09-09-31157.pcap Product: Wireshark Version: unspecified Hardware: x86-64 URL:

[Wireshark-bugs] [Bug 12857] New: Wireshark becomes unresponsive while capturing packets.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12857 Bug ID: 12857 Summary: Wireshark becomes unresponsive while capturing packets. Product: Wireshark Version: 2.2.0 Hardware: x86 OS: Windows 10

[Wireshark-bugs] [Bug 12859] New: Display data rate fields for VHT rates invalid with BCC modulation

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12859 Bug ID: 12859 Summary: Display data rate fields for VHT rates invalid with BCC modulation Product: Wireshark Version: 2.2.0 Hardware: All OS: All

[Wireshark-bugs] [Bug 12558] Inconsistent VHT data rate

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12558 Ashish Shukla changed: What|Removed |Added Blocks||12859 --

[Wireshark-bugs] [Bug 12826] usage http-tcp dissector from lua dissector lead to Segmentation fault

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12826 Peter Wu changed: What|Removed |Added CC|

[Wireshark-bugs] [Bug 12839] Buildbot crash output: randpkt-2016-09-08-27704.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12839 Peter Wu changed: What|Removed |Added Status|CONFIRMED |RESOLVED

[Wireshark-bugs] [Bug 12858] New: Buildbot crash output: randpkt-2016-09-09-12063.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12858 Bug ID: 12858 Summary: Buildbot crash output: randpkt-2016-09-09-12063.pcap Product: Wireshark Version: unspecified Hardware: x86-64 URL:

[Wireshark-bugs] [Bug 12826] usage http-tcp dissector from lua dissector lead to Segmentation fault

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12826 --- Comment #11 from Guy Harris --- (In reply to Peter Wu from comment #8) > Comment 5 uses an approach that seems quite common for Lua dissectors (I > think it is also documented in an example Lua dissector): obtain

[Wireshark-bugs] [Bug 12860] New: Buildbot crash output: randpkt-2016-09-09-24105.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12860 Bug ID: 12860 Summary: Buildbot crash output: randpkt-2016-09-09-24105.pcap Product: Wireshark Version: unspecified Hardware: x86-64 URL:

[Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845 --- Comment #8 from Roland Knall --- Just a thought. If USPPcap hangs the first time, it seems that it is trying to gather information on some socket, and therefore cannot finish the extcap detection process properly. It

[Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845 Pascal Quantin changed: What|Removed |Added CC|

[Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845 Graham Bloice changed: What|Removed |Added CC|

[Wireshark-bugs] [Bug 12846] Live capture from USBPcap fails immediately

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12846 --- Comment #4 from Pavel Sindelka --- > Simply click on the wheel icon, which is on the left of the USBPcap > interface name Grrr... I was clicking the text all the time :-) > Not exactly: it's not a check box,

[Wireshark-bugs] [Bug 12846] Live capture from USBPcap fails immediately

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12846 --- Comment #5 from Pascal Quantin --- (In reply to Pavel Sindelka from comment #4) > > Simply click on the wheel icon, which is on the left of the USBPcap > > interface name > Grrr... I was clicking the text all

[Wireshark-bugs] [Bug 12846] Live capture from USBPcap fails immediately

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12846 Alexis La Goutte changed: What|Removed |Added CC|

[Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845 --- Comment #6 from Graham Bloice --- If there are pdb files available for USBPCapCMD, then a dump of the process can be examined to determine where it's stuck. -- You are receiving this mail because: You

[Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845 --- Comment #7 from Pascal Quantin --- I do not have the .pdb file: the program was built by Gerald. One way to discriminate whether Wiresahrk or USBPcap is the culprit is to deinstall the -5 version and

[Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845 --- Comment #4 from Pavel Sindelka --- (In reply to Pascal Quantin from comment #2) > Is it solely happening with USBPcapCMD.exe, or does your extcaptest.exe > alone program also trigger the issue? It is

[Wireshark-bugs] [Bug 12851] New: Buildbot crash output: fuzz-2016-09-09-25074.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12851 Bug ID: 12851 Summary: Buildbot crash output: fuzz-2016-09-09-25074.pcap Product: Wireshark Version: unspecified Hardware: x86-64 URL:

[Wireshark-bugs] [Bug 12850] New: Buildbot crash output: randpkt-2016-09-09-7566.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12850 Bug ID: 12850 Summary: Buildbot crash output: randpkt-2016-09-09-7566.pcap Product: Wireshark Version: unspecified Hardware: x86-64 URL:

[Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845 Pascal Quantin changed: What|Removed |Added CC|

[Wireshark-bugs] [Bug 12837] Qt: Gigantic format list when open capture file

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12837 --- Comment #6 from Guy Harris --- The dialog box shown in https://msdn.microsoft.com/en-us/library/windows/desktop/dn742498(v=vs.85).aspx shows "All Picture Files" without any list of extensions, so it appears

[Wireshark-bugs] [Bug 12763] tshark print 'TCP flags' with non-ascci chars on some console

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12763 --- Comment #7 from Gerald Combs --- Can you try tshark ... | iconv -f UTF-8 -t ASCII//TRANSLIT | less It's a bit clunky but it translates arrows and middle dots to their ASCII equivalents here. -- You are

[Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845 --- Comment #9 from Pavel Sindelka --- > So, short question, if you have a hanging usbpcap and start wireshark a > second time, can you actually capture on the shown usb devices? If so, the > main issue is within

[Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845 --- Comment #10 from Roland Knall --- (In reply to Pavel Sindelka from comment #9) > Repeating the question I've asked Pascal - will it move you further if I use > the Process Monitor and tell you what the command line

[Wireshark-bugs] [Bug 12837] Qt: Gigantic format list when open capture file

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12837 --- Comment #5 from Gerrit Code Review --- Change 17605 had a related patch set uploaded by Dario Lombardo: Qt: shorten the list for file selection. https://code.wireshark.org/review/17605 -- You are

[Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845 --- Comment #11 from Pavel Sindelka --- (In reply to Roland Knall from comment #10) > (In reply to Pavel Sindelka from comment #9) > > Repeating the question I've asked Pascal - will it move you further if I use >

[Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845 --- Comment #16 from Michal Labedzki --- Roland, I check text coding (add Polish letter like "ąąą", "łłł") in various places like: interface display name, interface name, preference display name (it saves

[Wireshark-bugs] [Bug 12839] Buildbot crash output: randpkt-2016-09-08-27704.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12839 --- Comment #3 from Peter Wu --- *** Bug 12844 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.

[Wireshark-bugs] [Bug 12844] Buildbot crash output: randpkt-2016-09-08-5112.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12844 Peter Wu changed: What|Removed |Added Status|CONFIRMED |RESOLVED

[Wireshark-bugs] [Bug 12826] usage http-tcp dissector from lua dissector lead to Segmentation fault

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12826 --- Comment #10 from Peter Wu --- (In reply to Michael Mann from comment #9) > (In reply to Peter Wu from comment #8) > > Maybe we should drop this data parameter and use p_add_proto_data: > > I would rather rewrite

[Wireshark-bugs] [Bug 12839] Buildbot crash output: randpkt-2016-09-08-27704.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12839 --- Comment #6 from Peter Wu --- *** Bug 12852 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.

[Wireshark-bugs] [Bug 12852] Buildbot crash output: randpkt-2016-09-09-30969.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12852 Peter Wu changed: What|Removed |Added Status|CONFIRMED |RESOLVED

[Wireshark-bugs] [Bug 12853] "File does not exist" error when capturing from a pipe

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12853 Guy Harris changed: What|Removed |Added Summary|File does not exist |"File does not

[Wireshark-bugs] [Bug 12853] File does not exist

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12853 --- Comment #1 from Guy Harris --- That's an appropriate file name when capturing from the standard input; perhaps there's a race condition where the "here's the capture file" message arrives in Wireshark before the

[Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845 Roland Knall changed: What|Removed |Added CC|

[Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845 --- Comment #14 from Michal Labedzki --- I can reproduce something else but it may be root cause. I have a crash when new refresh interface list (sometimes Wireshark hangs). Does usbpcap or your extcap has

[Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845 --- Comment #15 from Pavel Sindelka --- (In reply to Michal Labedzki from comment #14) > Does usbpcap or your extcap has dynamic interfaces like androiddump? > (interface that can show and gone all the time)

[Wireshark-bugs] [Bug 12845] First start with non-empty extcap folder after install or reboot hangs at "initializing tap listeners"

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12845 --- Comment #12 from Pavel Sindelka --- Created attachment 14892 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=14892=edit Process Monitor log illustrating the issue -- You are receiving this mail

[Wireshark-bugs] [Bug 12852] New: Buildbot crash output: randpkt-2016-09-09-30969.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12852 Bug ID: 12852 Summary: Buildbot crash output: randpkt-2016-09-09-30969.pcap Product: Wireshark Version: unspecified Hardware: x86-64 URL:

[Wireshark-bugs] [Bug 12839] Buildbot crash output: randpkt-2016-09-08-27704.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12839 --- Comment #2 from Peter Wu --- oops, picked the wrong file. Corrected output: randpkt-2016-09-08-27704.pcap Stats: 101M malloced (30M for red zones) by 1156816 calls Stats: 9M realloced by 15816 calls Stats: 98M

[Wireshark-bugs] [Bug 12839] Buildbot crash output: randpkt-2016-09-08-27704.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12839 --- Comment #4 from Peter Wu --- *** Bug 12848 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.

[Wireshark-bugs] [Bug 12849] Buildbot crash output: fuzz-2016-09-08-582.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12849 Peter Wu changed: What|Removed |Added Status|CONFIRMED |RESOLVED

[Wireshark-bugs] [Bug 12826] usage http-tcp dissector from lua dissector lead to Segmentation fault

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12826 --- Comment #9 from Michael Mann --- (In reply to Peter Wu from comment #8) > Maybe we should drop this data parameter and use p_add_proto_data: I would rather rewrite the dissector function signature (to have "data

[Wireshark-bugs] [Bug 12861] New: Buildbot crash output: randpkt-2016-09-10-29402.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12861 Bug ID: 12861 Summary: Buildbot crash output: randpkt-2016-09-10-29402.pcap Product: Wireshark Version: unspecified Hardware: x86-64 URL:

[Wireshark-bugs] [Bug 11850] Buildbot crash output: fuzz-2015-12-03-17013.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11850 Gerald Combs changed: What|Removed |Added See Also|

[Wireshark-bugs] [Bug 12700] Buildbot crash output: fuzz-2016-08-02-16422.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12700 Gerald Combs changed: What|Removed |Added See Also|

[Wireshark-bugs] [Bug 12751] Invalid memory access in UMTS-FP dissector

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12751 Gerald Combs changed: What|Removed |Added See Also|

[Wireshark-bugs] [Bug 12750] Buffer overflow in Catapult DCT2000 dissector

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12750 Gerald Combs changed: What|Removed |Added See Also|

[Wireshark-bugs] [Bug 12752] Stack overflow in Catapult DCT2000 dissector

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12752 Gerald Combs changed: What|Removed |Added See Also|

[Wireshark-bugs] [Bug 12848] Buildbot crash output: randpkt-2016-09-09-20651.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12848 Peter Wu changed: What|Removed |Added Status|CONFIRMED |RESOLVED

[Wireshark-bugs] [Bug 12850] Buildbot crash output: randpkt-2016-09-09-7566.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12850 Peter Wu changed: What|Removed |Added Status|CONFIRMED |RESOLVED

[Wireshark-bugs] [Bug 12839] Buildbot crash output: randpkt-2016-09-08-27704.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12839 --- Comment #5 from Peter Wu --- *** Bug 12850 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.

[Wireshark-bugs] [Bug 12862] New: Buildbot crash output: randpkt-2016-09-10-1188.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12862 Bug ID: 12862 Summary: Buildbot crash output: randpkt-2016-09-10-1188.pcap Product: Wireshark Version: unspecified Hardware: x86-64 URL: