[Wireshark-bugs] [Bug 15475] Qt menu keyboard shortcuts don't match Gtk shortcuts.

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15475 Alexis La Goutte changed: What|Removed |Added CC||alexis.lagou...@gmail.com ---

[Wireshark-bugs] [Bug 15445] Wireless toolbar is missing

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15445 V Capps changed: What|Removed |Added Summary|Check mark item for |Wireless toolbar is missing

[Wireshark-bugs] [Bug 14281] Wireshark error code Exception 0xc0000409

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14281 Christopher Maynard changed: What|Removed |Added See Also||https://bugs.wireshark.org/

[Wireshark-bugs] [Bug 15472] Wireshark gets EINVAL on Windows when trying to write capture file

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15472 Christopher Maynard changed: What|Removed |Added See Also||https://bugs.wireshark.org/

[Wireshark-bugs] [Bug 15475] New: Qt menu keyboard shortcuts don't match Gtk shortcuts.

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15475 Bug ID: 15475 Summary: Qt menu keyboard shortcuts don't match Gtk shortcuts. Product: Wireshark Version: Git Hardware: All OS: Windows Status: UNCONFIRMED

[Wireshark-bugs] [Bug 14281] Wireshark error code Exception 0xc0000409

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14281 Guy Harris changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED

[Wireshark-bugs] [Bug 15434] Logo Usage Guidelines

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15434 --- Comment #1 from Christopher Maynard --- Does the Wireshark Foundation have an official position on the use of the Wireshark logo in another application? -- You are receiving this mail because: You are watching all bug

[Wireshark-bugs] [Bug 14491] Dumpcap doesn't support a -Q flag

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14491 Christopher Maynard changed: What|Removed |Added Hardware|x86 |All

[Wireshark-bugs] [Bug 15472] Wireshark gets EINVAL on Windows when trying to write capture file

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15472 Christopher Maynard changed: What|Removed |Added CC||travis.str...@gmail.com

[Wireshark-bugs] [Bug 14281] Wireshark error code Exception 0xc0000409

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14281 Christopher Maynard changed: What|Removed |Added Resolution|--- |DUPLICATE

[Wireshark-bugs] [Bug 14252] ethers file processing

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14252 Christopher Maynard changed: What|Removed |Added Severity|Enhancement |Normal

[Wireshark-bugs] [Bug 15473] Invalid FC1 response from modbus dissector when response has no request frame

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15473 --- Comment #5 from bugzi...@graglia.fr --- >so at least for this case, it seems OK, no? yes 1st pcap, the one with 2 frames, is ok for me. >I think you meant to say, "The other pcap does not include the *request*" absolutely! sorry for

[Wireshark-bugs] [Bug 15473] Invalid FC1 response from modbus dissector when response has no request frame

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15473 --- Comment #4 from Christopher Maynard --- (In reply to Christopher Maynard from comment #3) > A possibly better solution in this case would be to check if num_reg is 0, > in which case to set it to the value of the byte count in the

[Wireshark-bugs] [Bug 15473] Invalid FC1 response from modbus dissector when response has no request frame

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15473 Christopher Maynard changed: What|Removed |Added OS|Linux |All Hardware|x86

[Wireshark-bugs] [Bug 15473] Invalid FC1 response from modbus dissector when response has no request frame

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15473 Christopher Maynard changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever

[Wireshark-bugs] [Bug 15473] Invalid FC1 response from modbus dissector when response has no request frame

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15473 Christopher Maynard changed: What|Removed |Added Severity|Major |Normal -- You are

[Wireshark-bugs] [Bug 15473] Invalid FC1 response from modbus dissector when response has no request frame

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15473 --- Comment #2 from Christopher Maynard --- Created attachment 16890 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16890=edit Extracted file 2 of 2 -- You are receiving this mail because: You are watching all bug

[Wireshark-bugs] [Bug 15473] Invalid FC1 response from modbus dissector when response has no request frame

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15473 Christopher Maynard changed: What|Removed |Added Attachment #16887|0 |1 is obsolete|

[Wireshark-bugs] [Bug 15474] New: Enhancement request: adding EBHSCR dissector

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15474 Bug ID: 15474 Summary: Enhancement request: adding EBHSCR dissector Product: Wireshark Version: Git Hardware: x86 OS: Windows 7 Status: UNCONFIRMED

[Wireshark-bugs] [Bug 15473] New: Invalid FC1 response from modbus dissector when response has no request frame

2019-02-01 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15473 Bug ID: 15473 Summary: Invalid FC1 response from modbus dissector when response has no request frame Product: Wireshark Version: 2.6.6 Hardware: x86