[Wireshark-bugs] [Bug 15451] WISUN Channel Plan Spacing parsing incorrect

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15451

--- Comment #6 from Gerrit Code Review  ---
Change 31745 merged by Anders Broman:
Fix: WiSUN Explicit Channel Plan parsing

https://code.wireshark.org/review/31745

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13286] crash upon waking from sleep (with display on external monitor)

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13286

--- Comment #3 from Guy Harris  ---
(In reply to Guy Harris from comment #2)
> "Hi, I heard you like event loops so we're running an event loop inside your
> event loop so you can handle events while you're handling an event!"  That
> might work, but it could also cause hilarity to ensue.
> 
> Did we change that at some point, due to issues with updating interface
> lists?

No, we're still doing a screen update from sync_pipe_open_command():

/* we might wait for a moment till child is ready, so update screen now */
if (update_cb) update_cb();

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13286] crash upon waking from sleep (with display on external monitor)

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13286

--- Comment #2 from Guy Harris  ---
Stack trace:

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libobjc.A.dylib 0x7fffdc7e5a31 objc_retain + 33
1   com.apple.QuartzCore0x7fffcd9ccd32 -[CALayer
layoutSublayers] + 194
2   com.apple.QuartzCore0x7fffcd9c0210
CA::Layer::layout_if_needed(CA::Transaction*) + 366
3   com.apple.QuartzCore0x7fffcd9c008e
CA::Layer::layout_and_display_if_needed(CA::Transaction*) + 24
4   com.apple.QuartzCore0x7fffcd9b5878
CA::Context::commit_transaction(CA::Transaction*) + 280
5   com.apple.QuartzCore0x7fffcd8ac631
CA::Transaction::commit() + 475
6   com.apple.AppKit0x7fffc5ae2445 __37+[NSDisplayCycle
currentDisplayCycle]_block_invoke.31 + 323
7   com.apple.CoreFoundation0x7fffc7b9e397
__CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
8   com.apple.CoreFoundation0x7fffc7b9e307
__CFRunLoopDoObservers + 391
9   com.apple.CoreFoundation0x7fffc7b7ef39 __CFRunLoopRun + 873
10  com.apple.CoreFoundation0x7fffc7b7e974 CFRunLoopRunSpecific
+ 420
11  com.apple.HIToolbox 0x7fffc710aacc
RunCurrentEventLoopInMode + 240
12  com.apple.HIToolbox 0x7fffc710a901
ReceiveNextEventCommon + 432
13  com.apple.HIToolbox 0x7fffc710a736
_BlockUntilNextEventMatchingListInModeWithFilter + 71
14  com.apple.AppKit0x7fffc56b0ae4 _DPSNextEvent + 1120
15  com.apple.AppKit0x7fffc5e2b21f
-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:]
+ 2789
16  libqcocoa.dylib 0x000104a95fc7 0x104a77000 + 126919
17  org.wireshark.Wireshark 0x0001011817b3
sync_pipe_open_command + 627
18  org.wireshark.Wireshark 0x000101181f85
sync_pipe_run_command + 261
19  org.wireshark.Wireshark 0x000101182774
sync_interface_list_open + 388
20  org.wireshark.Wireshark 0x000101180670
capture_interface_list + 80
21  org.wireshark.Wireshark 0x0001011693b3
scan_local_interfaces + 307
22  org.wireshark.Wireshark 0x0001010e426b
iface_mon_event_cb(char const*, int) + 251
23  org.wireshark.Wireshark 0x000101184d68 iface_mon_event +
120
24  org.wireshark.Wireshark 0x0001011611ec
WiresharkApplication::qt_static_metacall(QObject*, QMetaObject::Call, int,
void**) + 1288
25  QtCore  0x000102c8eb6f
QMetaObject::activate(QObject*, int, int, void**) + 1871
26  QtCore  0x000102d1049c
QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) + 60
27  QtCore  0x000102c94ebd
QSocketNotifier::event(QEvent*) + 445
28  QtWidgets   0x0001017fdffc
QApplicationPrivate::notify_helper(QObject*, QEvent*) + 300
29  QtWidgets   0x000101800abb
QApplication::notify(QObject*, QEvent*) + 6187
30  QtCore  0x000102c5a932
QCoreApplication::notifyInternal(QObject*, QEvent*) + 114
31  libqcocoa.dylib 0x000104ae4b84 0x104a77000 + 449412
32  com.apple.CoreFoundation0x7fffc7bbd1e9 __CFSocketPerformV0
+ 985
33  com.apple.CoreFoundation0x7fffc7b9e981
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
34  com.apple.CoreFoundation0x7fffc7b7fa7d
__CFRunLoopDoSources0 + 557
35  com.apple.CoreFoundation0x7fffc7b7ef76 __CFRunLoopRun + 934
36  com.apple.CoreFoundation0x7fffc7b7e974 CFRunLoopRunSpecific
+ 420
37  com.apple.HIToolbox 0x7fffc710aacc
RunCurrentEventLoopInMode + 240
38  com.apple.HIToolbox 0x7fffc710a901
ReceiveNextEventCommon + 432
39  com.apple.HIToolbox 0x7fffc710a736
_BlockUntilNextEventMatchingListInModeWithFilter + 71
40  com.apple.AppKit0x7fffc56b0ae4 _DPSNextEvent + 1120
41  com.apple.AppKit0x7fffc5e2b21f
-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:]
+ 2789
42  com.apple.AppKit0x7fffc56a5465 -[NSApplication run]
+ 926
43  libqcocoa.dylib 0x000104a965e4 0x104a77000 + 128484
44  QtCore  0x000102c579ad
QEventLoop::exec(QFlags) + 381
45  QtCore  0x000102c5aee7
QCoreApplication::exec() + 359
46  org.wireshark.Wireshark 0x000100dc186d main + 4093
47  org.wireshark.Wireshark 0x000100dc0854 start + 52

"Hi, I heard you like event loops so we're running an event loop inside your
event loop so you can handle events while you'

[Wireshark-bugs] [Bug 13350] "Wireshark has stopped working" every time I quit

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13350

--- Comment #17 from Christopher Maynard  ---
(In reply to Justin from comment #16)
> Will do.

It's been a while since this bug has had any feedback.  Does Wireshark still
crash every time you quit Wireshark using the latest stable version of
Wireshark (currently 2.6.6)?  Note that Wireshark 2.2.x is no longer supported
as of September 7, 2018.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13326] RTP Stream dialog show wrong number lost

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13326

--- Comment #5 from Christopher Maynard  ---
(In reply to Pascal Quantin from comment #1)
> GTK UI is also impacted.
> Presumably it would be better to show 0% in case of duplicates packets,
> instead of a negative number (which could be raise questions)?

Note that with master Version 2.9.1 (v2.9.1rc0-567-g311dc2f1), the "Lost"
column now shows -28 (-2.5%) instead of 4294967268 (376091704.7%) with
Wireshark 2.6.6.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13293] RTP Streams: Wireshark crashes

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13293

--- Comment #13 from Christopher Maynard  ---
Wireshark 2.2.x is no longer supported as of September 7, 2018.  Can you retest
with the latest stable version of Wireshark and update the bug report with your
findings?

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13286] crash upon waking from sleep (with display on external monitor)

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13286

--- Comment #1 from Christopher Maynard  ---
(In reply to Eric Tiffany from comment #0)
> Wake from sleep causing this crash and stack trace (not always repeatable):

Wireshark 2.2.x is no longer supported as of September 7, 2018.  Can you retest
with the latest stable version of Wireshark and update the bug report with your
findings?

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13229] Feature request: Forced TCP Window Scaling factor on per-connection basis

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13229

Christopher Maynard  changed:

   What|Removed |Added

   Severity|Normal  |Enhancement
Version|2.2.2   |Git

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13228] Feature request: "custom multiplier" (scale factor) field on I/O graph

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13228

Christopher Maynard  changed:

   What|Removed |Added

   Severity|Normal  |Enhancement
Version|2.2.2   |Git

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13227] Wireshark crashes very quickly after start capture

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13227

Christopher Maynard  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Christopher Maynard  ---
(In reply to Peter Wu from comment #2)
> Unless evidence shows otherwise, I am going to assume it is a Qt UI issue.
> Maybe it is related to high traffic and capture file changes (due to use of
> ring).
> Needs further investigation.

Wireshark 2.2.x is no longer supported as of September 7, 2018, so I'm closing
the bug.  If the problem can be reproduced with the latest stable version of
Wireshark (and updated Qt package), then feel free to reopen the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13184] Access violation in Wireshark!rescan_packets+0x345

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13184

--- Comment #8 from Christopher Maynard  ---
A lot has changed since the 2+ years this bug has been filed and Wireshark
2.2.x is no longer supported as of September 7, 2018.  Can this bug still be
reproduced with the latest stable version of Wireshark?

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13105] Wireshark's RTP Player does not emit any audio

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13105

Christopher Maynard  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #10 from Christopher Maynard  ---
(In reply to Gerald Combs from comment #9)
> @zamar Can you try playback via your Creative card using Wireshark
> 2.3.0-1664 or later from https://www.wireshark.org/download/automated ? It
> should show an error message if the audio format is unsupported.

No feedback for over 2 years so closing as fixed.  Feel free to reopen if
that's not the case.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12811] Display filter autocomplete is too eager

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12811

--- Comment #5 from Guy Harris  ---
...and it looks as if ui/gtk/filter_autocomplete.c may be trying to
reverse-engineer what the parser wants, to some degree.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12811] Display filter autocomplete is too eager

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12811

--- Comment #4 from Guy Harris  ---
The subject line could probably be changed to "display filter autocomplete
works at the lexical level, rather than the grammatical level", without loss of
much correctness. :-)

If there's some way to get from Lemon, on a parse error, the types of token
that would make it able to continue parsing at that point, that would probably
help.  (We could perhaps even have display filter autocomplete support more
than just autocompleting field/protocol names - perhaps we could even
autocomplete

{named field with a value_string) ==

with a list of values from the value_string, for example.)

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12932] Flow Graph scrolls in the wrong direction vertically when pressing Up/Down

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12932

Christopher Maynard  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12918] capture filters not saved to recently used list

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12918

Christopher Maynard  changed:

   What|Removed |Added

 OS|Windows 7   |Windows
 Ever confirmed|0   |1
Version|2.0.5   |Git
 Status|UNCONFIRMED |CONFIRMED

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12910] Display jumps when opening packet in a new window on a dual-monitor system

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12910

--- Comment #1 from Christopher Maynard  ---
This bug no longer seems applicable, at least I can't reproduce it using the
latest stable version of Wireshark (currently 2.6.6) or with master.

The problem I do see is that the new packet window opens *behind* the main
Wireshark window instead of in front of it.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12811] Display filter autocomplete is too eager

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12811

Christopher Maynard  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #3 from Christopher Maynard  ---
(In reply to Stig Bjørlykke from comment #2)
> (In reply to Christopher Maynard from comment #1)
> > Can you elaborate a bit?
> 
> When you *start* typing the operator the autocomplete popup is displayed.
> 
> Type "data c" and you will see the popup listing all protocols starting with
> "c". None of the protocols starting with "c" is valid at this point in a
> display filter.

OK, thanks for clarifying.  I was confused by the terminology you used,
expecting some popup dialog box to appear, but it was the dropdown list you
were referring to.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12876] [SIGSEGV] crashes on OS X in QtWidgets

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12876

Stig Bjørlykke  changed:

   What|Removed |Added

 CC||s...@bjorlykke.org

--- Comment #6 from Stig Bjørlykke  ---
(In reply to Christopher Maynard from comment #5)
> Since Wireshark ships with an even newer version of Qt than 5.6.3, can this
> bug be closed now?

Wireshark on macOS still ships with Qt 5.3.2.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12908] The "find a packet" tool highlight the second half of the UTF-16 string in the "Packet Bytes" pane

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12908

Christopher Maynard  changed:

   What|Removed |Added

   Hardware|x86 |All
 OS|Windows 7   |Windows
 Ever confirmed|0   |1
Version|2.2.0   |Git
 Status|UNCONFIRMED |CONFIRMED

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12811] Display filter autocomplete is too eager

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12811

--- Comment #2 from Stig Bjørlykke  ---
(In reply to Christopher Maynard from comment #1)
> Can you elaborate a bit?

When you *start* typing the operator the autocomplete popup is displayed.

Type "data c" and you will see the popup listing all protocols starting with
"c". None of the protocols starting with "c" is valid at this point in a
display filter.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12876] [SIGSEGV] crashes on OS X in QtWidgets

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12876

--- Comment #5 from Christopher Maynard  ---
(In reply to Gerald Combs from comment #4)
> Quick updates:
> 
> Karabiner 10.22.0 includes a check for Wireshark and was released on October
> 31.
> 
> QTBUG-49907 was closed as fixed on November 17. The fix will be in Qt 5.6.3.

Since Wireshark ships with an even newer version of Qt than 5.6.3, can this bug
be closed now?

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12811] Display filter autocomplete is too eager

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12811

--- Comment #1 from Christopher Maynard  ---
(In reply to Stig Bjørlykke from comment #0)
> Build Information:
> Wireshark 2.3.0 (v2.3.0rc0-502-g717215d from master)
> --
> The autocomplete popup is displayed when starting typing a operator
> “contains”, "in" or “matches”.
> 
> This works correct in the old GTK.

If I start typing a display filter starting with "data contains", there's no
"autocomplete popup", so I'm not sure I understand what the bug actually is. 
Can you elaborate a bit?  Maybe it was resolved and it's no longer a bug?

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12527] Add Hungarian language support

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12527

--- Comment #14 from Guy Harris  ---
(In reply to Christopher Maynard from comment #10)
> 3 additional translations have been added since this comment was made, so we
> now also have:
> 
> wireshark_ru.ts
> wireshark_sv.ts
> wireshark_uk.ts

...but we still don't have wireshark_hu.ts.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12527] Add Hungarian language support

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12527

--- Comment #13 from Guy Harris  ---
(In reply to Guy Harris from comment #12)
> 2) *something* is confused, which is why there's *Finnish* text, rather than
> Hungarian text, in the buttons in the button rows of the dialogs.

  ...

> I don't know *whose* bug the second of those is - ours, Qt's, or something
> else?  Qt does, presumably, supply its own translations for text that they
> supply, such as, I think, "standard" buttons ("OK" and "Cancel", for
> example), but confusing Hungarian and Finnish is like confusing Icelandic
> and Farsi (in both cases, they're members of the same large language family,
> but sufficiently distant that I don't see somebody knowledgable confusing
> them), so I'm not sure quite how that would be happening.

If users whose UI language is set to Hungarian are still seeing Finnish
"OK"/"Cancel"/"Save" buttons, that should be filed as a separate bug.  This bug
should be for the lack of Hungarian translations for UI text that *we* supply.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12527] Add Hungarian language support

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12527

--- Comment #12 from Guy Harris  ---
(In reply to Christopher Maynard from comment #10)
> (In reply to Guy Harris from comment #9)
> > The list of .ts files we currently have is:
> > 
> > wireshark_de.ts
> > wireshark_en.ts
> > wireshark_fr.ts
> > wireshark_it.ts
> > wireshark_ja_JP.ts
> > wireshark_pl.ts
> > wireshark_zh_CN.ts
> 
> 3 additional translations have been added since this comment was made, so we
> now also have:
> 
> wireshark_ru.ts
> wireshark_sv.ts
> wireshark_uk.ts
> 
> > There's no wireshark_hu.ts, so the only translations to Hungarian in
> > Wireshark would be those supplied by Qt itself.  Qt presumably translates
> > button labels that it supplies; some are supplied by Wireshark and won't get
> > translated until somebody supplies translations through Transifex:
> > 
> > https://www.transifex.com/wireshark/wireshark/
> > 
> > but I'm surprised Qt *itself* would confuse Finnish with Hungarian.
> 
> Still no wireshark_hu.ts, so should the bug here be reclassified as an
> enhancement request with the summary changed to add Hungarian language
> support?  Or is this a Qt bug that may or may not already be resolved with
> the latest version of Qt 5.12.0, but either way implying that this bug can
> be closed as "NOTOURBUG"?

There appear to be two issues here:

1) We don't have any UI translations for Hungarian, which explains why there's
English text, rather than Hungarian text, in several of the dialogs;

2) *something* is confused, which is why there's *Finnish* text, rather than
Hungarian text, in the buttons in the button rows of the dialogs.

The first of those *is* our bug, in that it's ultimately up to Wireshark to
supply the translation files.  That obviously requires somebody who knows
Hungarian to contribute, but that's what Transifex is all about.

I don't know *whose* bug the second of those is - ours, Qt's, or something
else?  Qt does, presumably, supply its own translations for text that they
supply, such as, I think, "standard" buttons ("OK" and "Cancel", for example),
but confusing Hungarian and Finnish is like confusing Icelandic and Farsi (in
both cases, they're members of the same large language family, but sufficiently
distant that I don't see somebody knowledgable confusing them), so I'm not sure
quite how that would be happening.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12375] Unable to set permanently any option in View menu

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12375

Christopher Maynard  changed:

   What|Removed |Added

 CC||jamin_tur...@trimble.com

--- Comment #5 from Christopher Maynard  ---
*** Bug 12737 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12737] Wireshark 2 Configuration Persistence

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12737

Christopher Maynard  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Christopher Maynard  ---


*** This bug has been marked as a duplicate of bug 12375 ***

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12527] Add Hungarian language support

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12527

Christopher Maynard  changed:

   What|Removed |Added

Version|2.0.4   |Git
 OS|Windows 7   |All
Summary|Faulty language settings in |Add Hungarian language
   |buttons |support
   Hardware|x86 |All
   Severity|Minor   |Enhancement

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12527] Faulty language settings in buttons

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12527

--- Comment #11 from Alexis La Goutte  ---
Set to Enhance request... the translation for Hungrian is only 1,4% for the
moment...

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12527] Faulty language settings in buttons

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12527

--- Comment #10 from Christopher Maynard  ---
(In reply to Guy Harris from comment #9)
> The list of .ts files we currently have is:
> 
> wireshark_de.ts
> wireshark_en.ts
> wireshark_fr.ts
> wireshark_it.ts
> wireshark_ja_JP.ts
> wireshark_pl.ts
> wireshark_zh_CN.ts

3 additional translations have been added since this comment was made, so we
now also have:

wireshark_ru.ts
wireshark_sv.ts
wireshark_uk.ts

> There's no wireshark_hu.ts, so the only translations to Hungarian in
> Wireshark would be those supplied by Qt itself.  Qt presumably translates
> button labels that it supplies; some are supplied by Wireshark and won't get
> translated until somebody supplies translations through Transifex:
> 
> https://www.transifex.com/wireshark/wireshark/
> 
> but I'm surprised Qt *itself* would confuse Finnish with Hungarian.

Still no wireshark_hu.ts, so should the bug here be reclassified as an
enhancement request with the summary changed to add Hungarian language support?
 Or is this a Qt bug that may or may not already be resolved with the latest
version of Qt 5.12.0, but either way implying that this bug can be closed as
"NOTOURBUG"?

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14357] Crash when opening Statistics -> I/O Graph

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14357

--- Comment #13 from Christopher Maynard  ---
(In reply to Jim Young from comment #12)
> I/O Graphs file with five graphs with the first four disabled.  Using this
> file triggers the  I/O Graphs crash. If the file is edited manually to
> delete the fifth the I/O Graphs dialog opens without crashing.

Using the attached io_graphs file, I was unable to reproduce the crash on
Windows 10 running either 2.6.6 or master.  Is this bug still relevant or can
it be closed?

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15443] repeated 'NFS' in Protocol Display field

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15443

--- Comment #8 from Gerrit Code Review  ---
Change 31782 had a related patch set uploaded by Guy Harris:
rpc: don't set fence on COL_PROTOCOL.

https://code.wireshark.org/review/31782

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 11840] Qt version of Wireshark doesn't have the edit packet option

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11840

--- Comment #2 from Gerald Combs  ---
If someone were to implement this feature, what should it look like? A few
options that come to mind are:

1) A field-centric editor. This could be implemented as a toolbar similar to
the column editor (right click on a column and select "Edit Column") that would
let you edit a selected packet detail item according to its type (integer,
string, bytes, etc.)

2) A byte-centric editor. This could be implemented as a traditional hex
editor, either directly in the packet bytes pane or in a separate hex editor
pane.

3) A stream editor, which would let you find fields or bytes in any or all
packets and transform them (i.e. replace them with different values or remove
them).

Note that item 3 wouldn't necessarily be exclusive to items 1 or 2.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15443] repeated 'NFS' in Protocol Display field

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15443

--- Comment #9 from Gerrit Code Review  ---
Change 31782 merged by Guy Harris:
rpc: don't set fence on COL_PROTOCOL.

https://code.wireshark.org/review/31782

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15443] repeated 'NFS' in Protocol Display field

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15443

--- Comment #7 from Gerrit Code Review  ---
Change 31781 merged by Guy Harris:
rpc: don't set fence on COL_PROTOCOL.

https://code.wireshark.org/review/31781

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15443] repeated 'NFS' in Protocol Display field

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15443

--- Comment #6 from Gerrit Code Review  ---
Change 31781 had a related patch set uploaded by Guy Harris:
rpc: don't set fence on COL_PROTOCOL.

https://code.wireshark.org/review/31781

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12417] Installer should stop asking if I want to remove a previous version

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12417

Christopher Maynard  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #3 from Christopher Maynard  ---
(In reply to brian.mathis from comment #2)
> As it is, without that
> context, it really just leaves you hanging with no idea what is the correct
> answer.

Just because there is a newer version available does not mean it should be
updated.  Besides the points Jeff made, the user may not even have sufficient
privileges to update the installer and the user's system may not even be
compatible with the latest update (see:
https://wiki.wireshark.org/Development/LifeCycle).  The user may not wish to
update Wireshark for a variety of reasons, so the user must decide what to do
here.

If you don't want to be reminded about updates, you have the option to disable
the feature via, "Edit -> Preferences -> Advanced -> gui.update.enabled ->
FALSE".

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 11840] Qt version of Wireshark doesn't have the edit packet option

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11840

Guy Harris  changed:

   What|Removed |Added

Summary|Edit packet option missing  |Qt version of Wireshark
   |in Wireshark 2.0|doesn't have the edit
   ||packet option

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 11898] IO Graph Save As ... button retains default focus

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11898

Graham Bloice  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #4 from Graham Bloice  ---
I can't recreate this either.  Close it out.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15361] macOS DMG appears to have duplicate files

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15361

Peter Wu  changed:

   What|Removed |Added

 CC||thomas.baude...@gmail.com

--- Comment #8 from Peter Wu  ---
*** Bug 15461 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15461] macOS app 2.6.6 size of 480MB - Compiled with Debug Symbols

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15461

Peter Wu  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Peter Wu  ---
It will be fixed with the next release, fixed since v2.6.6rc0-39-gf28f8049f7.

*** This bug has been marked as a duplicate of bug 15361 ***

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12389] Qt Wireshark doesn't remember what monitor it last ran on when maximized on 2nd monitor

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12389

Christopher Maynard  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 OS|Windows 7   |Windows
   Hardware|x86 |All
Summary|Qt Wireshark doesn't|Qt Wireshark doesn't
   |remember what monitor it|remember what monitor it
   |last ran on |last ran on when maximized
   ||on 2nd monitor
Version|2.0.3   |Git
 Ever confirmed|0   |1

--- Comment #6 from Christopher Maynard  ---
(In reply to Jim Aragon from comment #5)
> When Wireshark (now 2.0.4) is running maximized on the second monitor and is
> shut down, the next time it's launched, it opens maximized on the first
> monitor.

This is the only remaining part of this bug.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 11951] Pane resizing quit working

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11951

Pierre Fortin  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|CONFIRMED   |RESOLVED

--- Comment #5 from Pierre Fortin  ---
Closing -- looks OK on 2.2.17

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12375] Unable to set permanently any option in View menu

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12375

Christopher Maynard  changed:

   What|Removed |Added

   Hardware|x86 |All
 OS|Windows 7   |All
Version|2.0.2   |Git

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12350] OS/application option from IDB isn't shown in Capture File Properties (a.k.a. Summary)

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12350

--- Comment #2 from Christopher Maynard  ---
(In reply to Christopher Maynard from comment #1)
> (In reply to Jasper Bongertz from comment #0)
> > Build Information:
> > Version 2.1.0-2677-g6b963e9 (v2.1.0rc0-2677-g6b963e9 from master)
> > --
> > The OS / capture application information options has been moved from the SHB
> > to the IDB for PCAPng files in 2.1.x. Both options are not shown anymore in
> > the "Statistics" -> "Capture File Properties" dialog where they used to be
> > for the SHB. They should probably turn up in the table listing the interface
> > entries.
> 
> I believe this is fixed now, as the information is showing up under both the
> "Statistics -> Capture File Properties" as well as in capinfos output when
> tested with both Wireshark 2.6.6 and master on Windows 10.
> 
> Please confirm so the bug can be closed.

Or is the bug that capture files captured prior to the change don't show the OS
and application information with post 2.1.x changes?  My tests above were with
a capture file using 2.6.6 and master, not with one taken with say, 2.0.x.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12350] OS/application option from IDB isn't shown in Capture File Properties (a.k.a. Summary)

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12350

--- Comment #1 from Christopher Maynard  ---
(In reply to Jasper Bongertz from comment #0)
> Build Information:
> Version 2.1.0-2677-g6b963e9 (v2.1.0rc0-2677-g6b963e9 from master)
> --
> The OS / capture application information options has been moved from the SHB
> to the IDB for PCAPng files in 2.1.x. Both options are not shown anymore in
> the "Statistics" -> "Capture File Properties" dialog where they used to be
> for the SHB. They should probably turn up in the table listing the interface
> entries.

I believe this is fixed now, as the information is showing up under both the
"Statistics -> Capture File Properties" as well as in capinfos output when
tested with both Wireshark 2.6.6 and master on Windows 10.

Please confirm so the bug can be closed.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12346] Missing "Resolve Name" in right click context menu

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12346

Christopher Maynard  changed:

   What|Removed |Added

Version|2.2.1   |Git
   Severity|Major   |Normal

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12250] Lua console closes on "Analyze -> reload lua plugins"

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12250

Christopher Maynard  changed:

   What|Removed |Added

Version|2.0.2   |Git
   Hardware|x86 |All
 OS|OS X 10.11  |All

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12178] Option to disable No Packets Captured dialog

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12178

Christopher Maynard  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
   Hardware|x86 |All
 Ever confirmed|0   |1
Version|2.0.1   |Git
 OS|Windows 7   |All

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12148] Unable to open two Wireshark instances simultaneously

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12148

--- Comment #2 from Christopher Maynard  ---
I can't reproduce this problem with the latest stable version of Wireshark
PortableApps (currently 2.6.6) running on Windows 10 64-bit.

For reference:

Version 2.6.6 (v2.6.6)

Compiled (32-bit) with Qt 5.12.0, with WinPcap (4_1_3), with GLib 2.38.0, with
zlib 1.2.11, with SMI 0.4.8, with c-ares 1.14.0, with Lua 5.2.4, with GnuTLS
3.4.11, with Gcrypt 1.7.6, with MIT Kerberos, with MaxMind DB resolver, with
nghttp2 1.14.0, with LZ4, with Snappy, with libxml2 2.9.4, with QtMultimedia,
with AirPcap, with SBC, with SpanDSP, with bcg729.

Running on 64-bit Windows 10, build 17763, with Intel(R) Xeon(R) CPU E3-1505M
v5 @ 2.80GHz (with SSE4.2), with 16225 MB of physical memory, with locale
English_United States.1252, with Npcap version 0.99-r9, based on libpcap
version 1.8.1, with GnuTLS 3.4.11, with Gcrypt 1.7.6, with AirPcap 4.1.0 build
1622, binary plugins supported (17 loaded). Built using Microsoft Visual Studio
2017 (VC++ 14.15, build 26730).

Please update to the latest stable version and confirm that this problem is
resolved.  Without feedback, I'll assume the problem is fixed and close the bug
soon.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12111] Unable to open without error DBusMenuExporterPrivate

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12111

--- Comment #2 from Christopher Maynard  ---
(In reply to Balint Reczey from comment #1)
> Seems to be a bug in Qt, not GTK UI.

Is this bug still applicable with the latest stable version of Wireshark (and
updated Qt)?  Wireshark 2.0.x is no longer supported as of November 18, 2017
and Qt 5.2.1 is quite old.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12098] Unable to disable decoding

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12098

Christopher Maynard  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
   Hardware|x86-64  |All
 Ever confirmed|0   |1
 OS|Windows 7   |All
Version|2.0.1   |Git

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12069] I can't scroll horizontally in the packet list pane

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12069

Christopher Maynard  changed:

   What|Removed |Added

   Severity|Major   |Normal

--- Comment #6 from Christopher Maynard  ---
(In reply to Jim Young from comment #2)
> One workaround appears to be to click on the resize columns button.

(In reply to RG from comment #5)
> The horizontal scroll bar will disappear and the window has to be resized or
> colums auto-resized to cause the scroll bar to re-appear. 

Since there are work-arounds for getting the horizontal scrollbar to be
displayed, I've lowered the severity.  (Perhaps it was only set to "Major" due
to bug 14174?)

I assume the bug is still relevant?  If not, feel free to close it.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15461] macOS app 2.6.6 size of 480MB - Compiled with Debug Symbols

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15461

Alexis La Goutte  changed:

   What|Removed |Added

 OS|Mac OS X 10.4   |macOS 10.14
 CC||alexis.lagou...@gmail.com,
   ||pe...@lekensteyn.nl

--- Comment #1 from Alexis La Goutte  ---
Peter, it is not fixed on 2.9.x ? (and not backported ?)

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12035] Qt Wireshark hangs when stopping the capture

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12035

Christopher Maynard  changed:

   What|Removed |Added

Version|2.0.1   |2.4.1

--- Comment #11 from Christopher Maynard  ---
(In reply to Florian from comment #10)
> 2.4.1 on Windows 10 still has the same issue, so I don't think it's a
> duplicate :)

Is this bug still applicable with the latest stable version of Wireshark,
currently 2.6.6?  (I can't reproduce this problem myself.)

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15461] New: macOS app 2.6.6 size of 480MB - Compiled with Debug Symbols

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15461

Bug ID: 15461
   Summary: macOS app 2.6.6 size of 480MB - Compiled with Debug
Symbols
   Product: Wireshark
   Version: unspecified
  Hardware: x86
OS: Mac OS X 10.4
Status: UNCONFIRMED
  Severity: Critical
  Priority: Low
 Component: Build process
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: thomas.baude...@gmail.com
  Target Milestone: ---

Build Information:
Version 2.6.6 (v2.6.6-0-gdf942cd8) 
Copyright 1998-2019 Gerald Combs  and contributors.
License GPLv2+: GNU GPL version 2 or later
 This is free software;
see the source for copying conditions. There is NO warranty; not even for
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. 
Compiled (64-bit) with Qt 5.3.2, with libpcap, without POSIX capabilities, with
GLib 2.37.6, with zlib 1.2.5, with SMI 0.4.8, with c-ares 1.12.0, with Lua
5.2.4, with GnuTLS 3.4.17, with Gcrypt 1.7.7, with MIT Kerberos, with MaxMind
DB resolver, with nghttp2 1.21.0, with LZ4, with Snappy, with libxml2 2.9.4,
with QtMultimedia, with SBC, with SpanDSP, with bcg729. 
Running on Mac OS X 10.14.3, build 18D42 (Darwin 18.2.0), with Intel(R)
Core(TM) i5-4278U CPU @ 2.60GHz (with SSE4.2), with 8192 MB of physical memory,
with locale C, with libpcap version 1.8.1 -- Apple version 79.200.4, with
GnuTLS 3.4.17, with Gcrypt 1.7.7, with zlib 1.2.11, binary plugins supported
(14 loaded). Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM
build 2336.9.00). 
Wireshark is Open Source Software released under the GNU General Public
License. 
Check the man page and http://www.wireshark.org for more information. 
--
v2.6.6 on macOS, once installed is 480MB, when it was 150MB in 2.4.12.

Looking at the package, every binary comes with an associated .dSYM file, for
debug symbols.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12028] More capture and display filter bookmarks would be useful

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12028

Christopher Maynard  changed:

   What|Removed |Added

   Severity|Major   |Enhancement
 OS|OS X 10.9   |All
   Hardware|x86 |All

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12001] Using Profiles from before the upgrade to 2.0.1 is causing WS to consume large amounts of RAM

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12001

Christopher Maynard  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #4 from Christopher Maynard  ---
I extracted the profile and saw one named, "Transum Profile". I believe the
Transum Lua plugin had some problems, but it's now a built-in Wireshark C
plugin.  Wireshark 2.0.x is also end of life as of November 18, 2017.  Anyway,
a lot has changed since this bug was opened and I can't reproduce any high RAM
usage problem on my Windows 10 system running Wireshark 2.6.6 with either
profile attached to this bug report, so I'm closing the bug.

If the problem can be reproduced with the latest stable version of Wireshark,
then feel free to reopen the bug and update all relevant build and other
information.  Besides the profiles, please also attach a specific capture file
that can be used for testing.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12067] Unable to resize the packet list pane, packet details pane

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12067

--- Comment #19 from Christopher Maynard  ---
Is there any update on this bug?  Wireshark 2.0.x is end of life as of November
18, 2017 and Wireshark 2.2.x is end of life as of September 7, 2018.  Does the
bug still exist even with the latest stable version of Wireshark?  If so,
please provide updated build and other relevant information.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 11951] Pane resizing quit working

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11951

Christopher Maynard  changed:

   What|Removed |Added

   See Also||https://bugs.wireshark.org/
   ||bugzilla/show_bug.cgi?id=12
   ||067

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12067] Unable to resize the packet list pane, packet details pane

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12067

Christopher Maynard  changed:

   What|Removed |Added

   See Also||https://bugs.wireshark.org/
   ||bugzilla/show_bug.cgi?id=11
   ||951

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 11951] Pane resizing quit working

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11951

--- Comment #4 from Christopher Maynard  ---
Is there any update on this bug?  Wireshark 2.0.x is end of life as of November
18, 2017; does it still exist even with the latest stable version of Wireshark?
 If so, please provide updated build and other relevant information.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 11946] Display Filter Macros no longer identified after creating new display filter macro.

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11946

Christopher Maynard  changed:

   What|Removed |Added

   Hardware|x86-64  |All
Version|2.0.1   |Git
 OS|Windows 7   |All

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 11909] Add "grey out focus" feature to packet list

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11909

Christopher Maynard  changed:

   What|Removed |Added

   Hardware|x86-64  |All
Version|2.0.0   |Git
 OS|Windows 7   |All

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 11898] IO Graph Save As ... button retains default focus

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11898

--- Comment #3 from Christopher Maynard  ---
Is this still a problem with the latest stable version of Wireshark?  I'm not
sure how to reproduce this myself, so as far as I can tell this bug can be
closed.  Can someone confirm?

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 11882] Crash wireshark on EXIT {libqcocoa.dylib}

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11882

Christopher Maynard  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Christopher Maynard  ---
(In reply to Alexis La Goutte from comment #2)
> Hi Andrey,
> 
> 
> You get the crash with any pcap file ?
> it is a "fresh" install or upgrade of Wireshark ?
> Do you have try to remove preference ?

No feedback in over 3 years, and Wireshark 2.0.x is no longer supported as of
November 18, 2017, so I'm closing this bug.  If the crash can be reproduced
with the latest stable version of Wireshark, then feel free to reopen the bug
and provide updated information.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 11840] Edit packet option missing in Wireshark 2.0

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11840

Christopher Maynard  changed:

   What|Removed |Added

Version|2.0.0   |Git

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 11807] Round Trip Time Graph is blank initially.

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11807

--- Comment #1 from Christopher Maynard  ---
(In reply to Mingjiang Shi from comment #0)
> Created attachment 14072 [details]
> Round Trip Time Graph that is shown initially.
> 
> Build Information:
> Version 2.0.0 (v2.0.0-0-g9a73b82 from master-2.0)
> 
> --
> Click Statistics via the Menu, then click TCP Stream Graphs -> Round Trip
> Time. The graph is blank initially, the graph is displayed by switching to
> other type of graph then switch back to Round Trip Time.

Wireshark 2.0 is no longer supported as of November 18, 2017.  Does this
problem still exist with the latest stable version of Wireshark or with master?
 If it does, please provide full Wireshark version information from "About ->
Wireshark" (or "tshark -v" output).

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15447] Stack-based off-by-one buffer overflow in dissect_ber_GeneralizedTime

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15447

Peter Wu  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||pe...@lekensteyn.nl
Summary|Wireshark stack-based   |Stack-based off-by-one
   |buffer overflow in  |buffer overflow in
   |dissect_ber_GeneralizedTime |dissect_ber_GeneralizedTime
  Group|private |
 Status|CONFIRMED   |RESOLVED

--- Comment #8 from Peter Wu  ---
Fixed in
v2.9.1rc0-563-g3cd5ac36e2
v2.6.7rc0-36-gd632d88025
v2.4.13rc0-18-gf8fbe9f934

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14431] sshdump does not exit tcpdump

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14431

Peter Wu  changed:

   What|Removed |Added

 OS|Windows 10  |All
 CC||rkn...@gmail.com,
   ||s...@bjorlykke.org
   Hardware|x86 |All
   Priority|Low |Medium

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14431] sshdump does not exit tcpdump

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14431

Peter Wu  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 CC||pe...@lekensteyn.nl
   See Also||https://bugs.wireshark.org/
   ||bugzilla/show_bug.cgi?id=13
   ||119

--- Comment #2 from Peter Wu  ---
This is still an issue and it is a quite bad one.

Some network interfaces (like nflog) only permit a single reader per group, so
this bug makes capturing from such interfaces pretty hard (one has to manually
kill sshdump on the client or kill dumpcap on the server).

It also affects restarts.

There is another failure case I ran into which may or may not be related: after
stopping the capture and killing the process, the next capture is corrupted (it
is detected as ERF and the dissection makes no sense). I have to actually exit
Wireshark and restart it for any effect. Found with v2.9.1rc0-558-geec3ce3bb2
on Arch Linux.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13119] extcap: stop/restart capture yields a zombie process

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13119

Peter Wu  changed:

   What|Removed |Added

   See Also||https://bugs.wireshark.org/
   ||bugzilla/show_bug.cgi?id=14
   ||431

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13119] extcap: stop/restart capture yields a zombie process

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13119

Peter Wu  changed:

   What|Removed |Added

 CC||pe...@lekensteyn.nl

--- Comment #20 from Peter Wu  ---
A zombie process is the result if a child process is not reaped (e.g. with
waitpid) as described in comment 14 for example. Is this still an issue?

I do observe that extcap processes are not exited on a capture stop, but I
believe that is tracked by bug 14431.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15442] dfilter: Memory leak on error with certain display filter function

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15442

Peter Wu  changed:

   What|Removed |Added

 Status|IN_PROGRESS |RESOLVED
 Resolution|--- |FIXED

--- Comment #7 from Peter Wu  ---
Fixed in v2.9.1rc0-558-geec3ce3bb2
(it could potentially be cleanly backported but is probably not that big of an
issue.)

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15442] dfilter: Memory leak on error with certain display filter function

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15442

--- Comment #6 from Gerrit Code Review  ---
Change 31758 merged by Peter Wu:
dfilter: fix memory leaks on dfilter compile errors involving a set

https://code.wireshark.org/review/31758

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15442] dfilter: Memory leak on error with certain display filter function

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15442

--- Comment #5 from Gerrit Code Review  ---
Change 31757 merged by Peter Wu:
dfilter: fix memory leaks if a dfilter fails to compile

https://code.wireshark.org/review/31757

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15443] repeated 'NFS' in Protocol Display field

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15443

Dario Lombardo  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15443] repeated 'NFS' in Protocol Display field

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15443

--- Comment #5 from Gerrit Code Review  ---
Change 31755 merged by Dario Lombardo:
rpc: don't set fence on COL_PROTOCOL.

https://code.wireshark.org/review/31755

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15460] New: Asterix CATEGORY 020 support

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15460

Bug ID: 15460
   Summary: Asterix CATEGORY 020 support
   Product: Wireshark
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: Enhancement
  Priority: Low
 Component: Dissection engine (libwireshark)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: marko.hrasto...@gmail.com
  Target Milestone: ---

Created attachment 16878
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16878&action=edit
CAT020 sample

Build Information:
Wireshark 2.9.1 (v2.9.1rc0-553-g4dbb26fd)

Copyright 1998-2019 Gerald Combs  and contributors.
License GPLv2+: GNU GPL version 2 or later

This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with Qt 5.9.5, with libpcap, with POSIX capabilities (Linux),
with libnl 3, with GLib 2.56.3, with zlib 1.2.11, with SMI 0.4.8, with c-ares
1.14.0, with Lua 5.1.5, with GnuTLS 3.5.18 and PKCS #11 support, with Gcrypt
1.8.1, with MIT Kerberos, with MaxMind DB resolver, with nghttp2 1.30.0, with
LZ4, with Snappy, with libxml2 2.9.4, with QtMultimedia, with SBC, with
SpanDSP,
with bcg729.

Running on Linux 4.15.0-43-generic, with Intel(R) Core(TM) i7-6700 CPU @
3.40GHz
(with SSE4.2), with 15921 MB of physical memory, with locale
LC_CTYPE=en_US.UTF-8, LC_NUMERIC=sl_SI.UTF-8, LC_TIME=sl_SI.UTF-8,
LC_COLLATE=en_US.UTF-8, LC_MONETARY=sl_SI.UTF-8, LC_MESSAGES=en_US.UTF-8,
LC_PAPER=sl_SI.UTF-8, LC_NAME=sl_SI.UTF-8, LC_ADDRESS=sl_SI.UTF-8,
LC_TELEPHONE=sl_SI.UTF-8, LC_MEASUREMENT=sl_SI.UTF-8,
LC_IDENTIFICATION=sl_SI.UTF-8, with libpcap version 1.8.1, with GnuTLS 3.5.18,
with Gcrypt 1.8.1, with zlib 1.2.11, binary plugins supported (0 loaded).

Built using gcc 7.3.0.

--
There is a new support added for ASTERIX Category 020 for review
(https://code.wireshark.org/review/#/c/31766/).

The sample file with traffic is uploaded here to see that dissector works
correctly with sample data.

Change-Id: I867f48c3d4299c22f68edf1e3f9cdbcfabc47eb4

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15446] Buildbot crash output: fuzz-2019-01-25-4370.pcap

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15446

Pascal Quantin  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|IN_PROGRESS |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe