[Wireshark-bugs] [Bug 15422] Support for dissecting MPLS encapsulated BIER packet (RFC 8296)

[bugzilla-daemon]

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

--- Comment #1 from Gerrit Code Review  ---
Change 31552 had a related patch set uploaded by Rohan Saini:
BIER: support for dissecting MPLS encapsulated BIER packets (RFC 8296)

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

-- 
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 15422] New: Support for dissecting MPLS encapsulated BIER packet (RFC 8296)

[bugzilla-daemon]

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

Bug ID: 15422
   Summary: Support for dissecting MPLS encapsulated BIER packet
(RFC 8296)
   Product: Wireshark
   Version: Git
  Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
  Severity: Enhancement
  Priority: Low
 Component: Dissection engine (libwireshark)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: rohan.sa...@nokia.com
  Target Milestone: ---

Created attachment 16841
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16841=edit
MPLS encapsulated BIER data packet

Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
Add support for dissecting MPLS encapsulated BIER data packet as per RFC 8296.
Attached is a pcap containg an MPLS encapsulated BIER data packet.

-- 
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 15421] Support for dissecting IS-IS BIER Info Sub-TLV (RFC 8401)

[bugzilla-daemon]

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

--- Comment #1 from Gerrit Code Review  ---
Change 31551 had a related patch set uploaded by Rohan Saini:
IS-IS: support for dissecting IS-IS BIER Info Sub-TLV (RFC 8401)

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

-- 
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 15421] New: Support for dissecting IS-IS BIER Info Sub-TLV (RFC 8401)

[bugzilla-daemon]

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

Bug ID: 15421
   Summary: Support for dissecting IS-IS BIER Info Sub-TLV (RFC
8401)
   Product: Wireshark
   Version: Git
  Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
  Severity: Enhancement
  Priority: Low
 Component: Dissection engine (libwireshark)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: rohan.sa...@nokia.com
  Target Milestone: ---

Created attachment 16840
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16840=edit
IS-IS packet with BIER Info Sub-TLV

Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
Add support for dissecting IS-IS BIER Info Sub-TLV and BIER MPLS Encapsulation
Sub-sub-TLV, as per RFC 8401.

Attached is a pcap containg an IS-IS LSP with Extended IP Reachability (t=135,
l=169) TLV, which has an example of the BIER Info Sub-TLV and the MPLS Encap
Sub-sub-TLV.

-- 
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 15406] Memory leak with "-T ek" output format option

[bugzilla-daemon]

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

--- Comment #2 from Shinya Sasaki  ---
In the original code, singly linked list is reversed but attr_list keep a
pointer to its element in proto_tree_write_node_ek. This causes
g_slist_free_full to be passed a pointer to the last element in the list. We
used a patch like below to work around this issue. 

 static void proto_tree_write_node_ek(proto_node *node, write_json_data *pdata)
 {
 GSList *attr_list  = NULL;
 GHashTable *attr_table  = g_hash_table_new_full(g_str_hash, g_str_equal,
g_free, NULL);

 ek_fill_attr(node, _list, attr_table, pdata);

 g_hash_table_destroy(attr_table);

 // Print attributes
-GSList *current_attr = g_slist_reverse(attr_list);
+attr_list = g_slist_reverse(attr_list);
+GSList *current_attr = attr_list;
 while (current_attr != NULL) {
 GSList *attr_instances = (GSList *) current_attr->data;

 ek_write_attr(attr_instances, pdata);

 current_attr = current_attr->next;
 if (current_attr != NULL) {
 fputs(",", pdata->fh);
 }
 }

 g_slist_free_full(attr_list, (GDestroyNotify) g_slist_free);
 }

Unfortunately we aren't familiar with a development procedure of wireshark so
that would be helpful for us if someone apply a patch like above or better
solution to a master code.

-- 
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 11578] Upon 1st startup, the packet list should be visible.

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

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

--- Comment #5 from Christopher Maynard  ---
Wireshark 1.12.x is no longer supported, nor is the GTK+ UI.  I'm going to
assume that the bug was either fixed or is no longer applicable in the latest
stable version of Wireshark and Qt UI.  That said, if the bug can be reproduced
using the latest stable version of Wireshark and Qt UI, then feel free to
reopen the bug and update the 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 11622] Decryption keys not saved

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

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

--- Comment #1 from Christopher Maynard  ---
(In reply to Jonas Mellander from comment #0)
> When adding decryption keys through the Decryption Keys menu in the Wireless
> toolbar, these are not saved after clicking Apply and OK. 
> When I go into the same list again, it's empty.

I can't reproduce this problem using Wireshark 2.6.6 on Windows 10 64-bit. 
I've got an AirPcap adaptor and I've added a new decryption key via the
Wireless Toolbar.  It was saved as expected.  (Sadly, the Wireless Toolbar
isn't supported under Qt, at least not for AirPcap adaptors it seems.)

Of course, if you're not using an AirPcap adaptor, then you'd have to retest
this with the latest stable version of Wireshark using the Qt UI, as Wireshark
1.12.8 is no longer supported, nor is the GTK+ UI.  For now, I'm going to
assume that this problem has been fixed.  If that's not the case, feel free to
reopen the bug and update the 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 11638] WAP-WSP and SIP statistics broken.

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #4 from Christopher Maynard  ---
(In reply to Michael Mann from comment #3)
> Works in Qt, not in GTK.

Closing as WONTFIX then.

-- 
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 15420] New: First reassembled out-of-order packet does not get "Reassembled in" marking

[bugzilla-daemon]

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

Bug ID: 15420
   Summary: First reassembled out-of-order packet does not get
"Reassembled in" marking
   Product: Wireshark
   Version: Git
  Hardware: x86
OS: Windows 10
Status: UNCONFIRMED
  Severity: Minor
  Priority: Low
 Component: Dissection engine (libwireshark)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: cejackso...@gmail.com
  Target Milestone: ---

Created attachment 16839
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16839=edit
Z39.50 capture with out-of-order packets

Build Information:
Wireshark 2.9.1-cej (v2.9.1rc0-376-ge5f7f15b)

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.10.1, with WinPcap SDK (WpdPack) 4.1.2, with GLib
2.52.2, with zlib 1.2.11, with SMI 0.4.8, with c-ares 1.14.0, with Lua 5.2.4,
with GnuTLS 3.6.3 and PKCS #11 support, with Gcrypt 1.8.3, 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 (1809), build 17763, withIntel(R) Core(TM)
i5-2450M CPU @ 2.50GHz (with SSE4.2), with 8139 MB of physical memory, with
locale English_United States.1252, with Npcap version 0.99-r5, based on libpcap
version 1.8.1, with GnuTLS 3.6.3, with Gcrypt 1.8.3, with AirPcap 4.1.0 build
1622, binary plugins supported (0 loaded).

Built using Microsoft Visual Studio 2017 (VC++ 14.14, build 26428).
--
With out-of-order reassembly turned on, the very first segment diagnosed as
out-of-order does not get marked with the "Reassembled in" field. In the
attached capture, packet 14 is the first one marked out-of-order. It does not
have the "reassembled in packet 64" marking. Note that packet 13 and all of the
others of the set seem to have the marking. It's only packet 14 that's missing
it.

This capture was taken by capturing from both members of a BONDed interface and
using mergecap to merge the two captures. Since the system was spraying packets
between the two interfaces, nearly every outbound packet is out of order.

-- 
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 11651] Wireshark GTK+ GUI in Windows appears to freeze (no repaint?)

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

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

--- Comment #6 from Christopher Maynard  ---
(In reply to raysatiro from comment #5)
> (In reply to Alexis La Goutte from comment #4)
> > (In reply to raysatiro from comment #3)
> > > (In reply to Alexis La Goutte from comment #2)
> > > > Can you try with Qt GUI ?
> > > 
> > > I'm pretty sure it doesn't happen in the Qt GUI, I've used it a bunch of
> > > times and I don't recall that happening.
> > 
> > There is no active dev on GTK GUI (for Wireshark) and it is recommended to
> > use Qt
> > 
> > (You don't use Wireshark via a remote session ?)
> 
> I don't use it via remote session. I'll use Qt.

Since the GTK+ UI is no longer supported and everything apparently works OK
with the Qt UI, I'm closing 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 12113] Repeatedly Hitting the Restart Sniff Button Causes Error

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

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

--- Comment #1 from Christopher Maynard  ---
I can't reproduce this bug using Wireshark 2.6.6 on Windows 64-bit and Qt UI,
so I'm closing the bug.

This bug was filed against Wireshark 2.0.1 and the GTK+ UI, neither of which
are supported anymore.  If the bug can be reproduced using the latest stable
version of Wireshark and the Qt UI, 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 12126] RTP stream analysis: false positive bad packets for video mark frames ("incorrect timestamp")

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

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

--- Comment #13 from Christopher Maynard  ---
(In reply to Jon from comment #12)
> I can confirm that this is fixed after installing:
> 
> Wireshark-win64-2.3.0-2606-gd557643.exe

Closing as fixed then.

-- 
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 12147] Time (format as specified) column does not keep previous size

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

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

--- Comment #2 from Christopher Maynard  ---
(In reply to Stig Bjørlykke from comment #1)
> I think this has been fixed in gf9e8a8ad or g9d4a676f in the upcoming 2.0.2
> release.
> 
> Please try an automated build to see if the issue has been fixed for you:
> https://www.wireshark.org/download/automated/win64/

No feedback, so assuming it's been fixed.  If the problem can still be
reproduced using the latest stable version of Wireshark and with the Qt UI
(since the GTK+ UI is no longer supported), 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 12460] GTK window hangs on dual-NIC burst of DNS req/resp pkts from another Wireshark resolving 1500 IPs

[bugzilla-daemon]

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

--- Comment #8 from Christopher Maynard  ---
A lot has changed since this bug was opened:

1) The latest stable version of Wireshark is now 2.6.6.
2) The GTK+ UI is no longer supported; only the Qt UI is supported.
3) c-ares is now at version 1.14.0.
4) Other packages have been updated, including compiler, etc.

Can you still reproduce this bug with the latest stable version of Wireshark
and using the Qt UI?  If it can only be reproduced with the GTK+ UI, then the
bug won't be fixed since that UI is no longer supported.

-- 
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 12470] Segfault when too many recent capture files registered

[bugzilla-daemon]

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

--- Comment #3 from Christopher Maynard  ---
(In reply to Jaap Keuter from comment #2)
> Adding a 19th item to the recent.capture_file list in recent_common causes
> Wireshark (GTK) to crash at startup, with attached backtrace.

I could not reproduce this problem with Wireshark 2.6.6 on Windows 64-bit
running either the GTK+ or Qt UI's.  It would appear this bug has been fixed?

If you can reproduce the crash with the latest stable version of Wireshark and
Qt UI, then we can change the component to Qt UI, but if you can only reproduce
it with the GTK+ UI, then we should close it as "WONTFIX" since that UI is no
longer supported.  Of course if you can't reproduce it at all, then I guess we
can just close it as "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 12557] Statistics->Endpoints window column auto-size is broken when displayed records is >= 1000

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

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

--- Comment #1 from Christopher Maynard  ---
(In reply to starlight from comment #0)
> With 64-bit wireshark-gtk.exe the Statistics->Endpoints window column
> auto-size goes bonkers and sets wildly incorrect column widths once the
> number of displayed rows exceeds, precisely, 999 entries.
> 
> This applies to all the tabs, especially Ethernet, IPv4 and TCP.
> 
> Is true with Maxmind GeoIP active and inactive.

I'm not sure what "bonkers" means exactly, but what I do see with tabs such as
IPv4, TCP and UDP is that the contents of the last column, "Rx Bytes", is
right-justified and resizing the window with the GTK+ UI doesn't cause the last
column's contents to move along the right edge as you adjust the window's
width, whereas with the Qt UI the contents will follow the right edge of the
window.

Since the GTK+ UI is no longer supported, I'm closing the bug as "WONTFIX".  If
you still find a problem with the dialogs using the latest stable version of
Wireshark and the Qt UI, then feel free to reopen the bug and update the
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 12744] Field highlighting does not work when using a black background color

[bugzilla-daemon]

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

--- Comment #7 from Christopher Maynard  ---
(In reply to Pascal Quantin from comment #6)
> One way to workaround this while keeping the black background could be to
> change Preferences -> User Interface -> Layout -> Packet bytes highlight
> style from Inverse to Bold.

The GTK+ UI is no longer supported, so please retest with the latest stable
version of Wireshark and the Qt UI.  If it works OK with the Qt UI, then we can
close this bug as "WONTFIX" for the GTK+ UI; otherwise we can categorize it as
a Qt UI bug instead.  Or Pascal's suggested work-around is used and we just
close the bug regardless?

-- 
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 13095] Wireshark crashes in Live Capture Analysis using live interfaces/remote capture interfaces

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|INCOMPLETE  |RESOLVED

--- Comment #7 from Christopher Maynard  ---
(In reply to Jörg Mayer from comment #6)
> The issue preventing you from testing has been fixed. Please retest either
> against 2.2.5 (or newer) or against a nightly build.

It's been nearly 2 years without any feedback, so I'm closing this bug.  If the
problem can be reproduced with the latest stable version of Wireshark and with
the Qt UI, then feel free to reopen the bug with 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 13167] Wireshark stops responding while capturing through pipe interface

[bugzilla-daemon]

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

--- Comment #1 from Christopher Maynard  ---
Does this bug still occur when running the latest stable version of Wireshark
and the Qt UI?  Wireshark 2.0.4 is no longer supported, nor is the GTK+ UI. 
(See https://wiki.wireshark.org/Development/LifeCycle)

-- 
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 13314] Resizeable Filter Toolbar

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

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

--- Comment #5 from Christopher Maynard  ---
The GTK+ UI is no longer supported and the Qt UI auto-resizes the display
filter entry box, so you should switch to the Qt UI.

-- 
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 12597] Export filtered displayed packets won't save IP fragments of SCTP fragments needed to reassemble a displayed frame

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

 CC||mazu...@gazeta.pl

--- Comment #9 from Christopher Maynard  ---
*** Bug 13318 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 13318] Export First Marked to Last Marked Packet - packet fragments not exported

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

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

--- Comment #2 from Christopher Maynard  ---
(In reply to Pascal Quantin from comment #1)
> Hi,
> 
> sounds like a duplicate of bug 12597. Could you confirm this is the case?

No feedback after 2 years, so I'm going to assume this bug is a duplicate and
close it.

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

-- 
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 13450] All of wireshark's gui is set right to left

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

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

--- Comment #2 from Christopher Maynard  ---
(In reply to Gerald Combs from comment #1)
> Can you paste in your build information?

No feedback for nearly 2 years, so closing this bug.  

If the problem can be reproduced with the latest stable version
of Wireshark running the Qt UI, then feel free to reopen the bug and update the
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 13661] Wireshark is crashing after 5-10 seconds of startup.

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|INCOMPLETE  |RESOLVED

--- Comment #4 from Christopher Maynard  ---
No feedback for nearly 2 years.  Version 1.10.7 is no longer supported, nor is
the GTK+ UI.  If the problem can be reproduced with the latest stable version
of Wireshark running the Qt UI, then feel free to reopen the bug and update the
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 13717] On copying data from I/O graph time of day is not copied (time of day button is check marked)

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

Version|2.2.5   |Git
 Status|UNCONFIRMED |CONFIRMED
   Hardware|x86 |All
 OS|Windows 8.1 |Windows
  Component|GTK+ UI |Qt UI
 Ever confirmed|0   |1

--- Comment #4 from Christopher Maynard  ---
Since we only care about the Qt UI now, I've changed the component accordingly.

-- 
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 13782] Monitor Mode check box not present in Interface options

[bugzilla-daemon]

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

Guy Harris  changed:

   What|Removed |Added

   Hardware|x86 |All
  Component|GTK+ UI |Dumpcap

--- Comment #6 from Guy Harris  ---
(In reply to Christopher Maynard from comment #5)
> In light of comment 4, changing the resolution to "NOTOURBUG" in the more
> likely event that it is.  In any case, this doesn't appear to be a GTK+ UI
> bug, but I'm not sure how to categorize it if it's a libpcap issue -
> Dumpcap?  Extras? ...

Dumpcap for now; Wireshark finds out from dumpcap whether an interface supports
monitor mode or not, and dumpcap, in turn, depends on libpcap.

-- 
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 13782] Monitor Mode check box not present in Interface options

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |NOTOURBUG

--- Comment #5 from Christopher Maynard  ---
In light of comment 4, changing the resolution to "NOTOURBUG" in the more
likely event that it is.  In any case, this doesn't appear to be a GTK+ UI bug,
but I'm not sure how to categorize it if it's a libpcap issue - Dumpcap? 
Extras? ...

-- 
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 13782] Monitor Mode check box not present in Interface options

[bugzilla-daemon]

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

--- Comment #4 from Guy Harris  ---
This could be a libpcap issue; no OS makes monitor mode support easy, but Linux
isn't making it as relatively easy as it is on, for example, macOS.  Supporting
it inside libpcap requires complicated code and, for mac80211 interfaces, the
code currently requires libnl, but linking libpcap with libnl causes issues if
libpcap uses a version of libnl different from the one an application using
libpcap is using, so most distributions don't build libpcap with libnl, so it
doesn't handle monitor mode as well as it could.

-- 
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 13719] Export Info not displayed in menu "Analyze => Expert Info" if it has not been added already during the initial dissector run

[bugzilla-daemon]

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

--- Comment #4 from Christopher Maynard  ---
(In reply to Guy Harris from comment #2)
> What happens if the capture is large enough that not all packets are visible
> in the packet list when you read the file in *and* the packet that adds the
> expert info isn't visible - in both the Qt and GTK+ UIs?

I think we can forget about the GTK+ UI now.  So is this bug still relevant for
the Qt UI?

> The Qt UI might *currently* do two passes when reading in the file, but
> that's inefficient, and if it does that, it should be changed not to.

I'm not sure if that means this bug should be closed and a new bug should be
opened to address this for the Qt UI?

This couldn't possibly be due to code wrapped within an "if (tree) { ... }"
block, could 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 13782] Monitor Mode check box not present in Interface options

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

 Status|INCOMPLETE  |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #3 from Christopher Maynard  ---
(In reply to Michael Mann from comment #2)
> Did the checkbox appear for older versions of Wireshark?  Note that 1.10 was
> end-of-lifed a few years ago.  Can you still reproduce on a supported
> version of Wireshark?

No feedback for nearly 2 years, so closing the bug.  If the bug can be
reproduced with the latest stable version of Wireshark using the Qt UI, 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 13820] Provide a 'Use KeyTab File for this session' menu item in the right-click menu for KRB-containing packets

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

Version|2.2.7   |Git
   Hardware|x86 |All
   Severity|Major   |Enhancement
  Component|GTK+ UI |Dissection engine
   ||(libwireshark)
 OS|Windows 10  |All

--- Comment #5 from Christopher Maynard  ---
(In reply to Pascal Quantin from comment #3)
> No it does not.
> So what you are looking for is (if I got you right) is a UAT table allowing
> to define the decryption file for a given set of conversations (identified
> by IP addresses and ports? Or Hatever is relevant for this protocol).
> If so, this would be a change in libwireshark and not in the GUI.
> 
> The current right click method allows you to access much quicker the strings
> so as to swap the keytab file.

Changing component to libwireshark based on this comment and also marking this
bug as an 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 13882] IO Graph initially displays trace attributes (packet count) incorrectly

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

 OS|Windows 7   |Windows
Version|2.2.7   |Git
   Hardware|x86 |All
   Severity|Major   |Normal
  Component|GTK+ UI |Qt UI

-- 
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 13920] By default on Windows, WS should probably check with user if NPF service/driver relevant but not started, and offer to start it

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

  Component|GTK+ UI |Qt UI
 Status|UNCONFIRMED |INCOMPLETE
   Hardware|x86-64  |All
Version|unspecified |Git
 Ever confirmed|0   |1
 OS|Windows 8.1 |Windows

--- Comment #1 from Christopher Maynard  ---
(In reply to Stilez from comment #0)
> On Windows, some interfaces (including the main wired LAN) won't be
> capturable unless the NPF service/driver is started.

There are at least 2 capture drivers available on the Windows platform, WinPcap
and npcap.

> Starting NPF is simple once you know it's needed.

How is Wireshark to know that it's needed?  Perhaps Wireshark is installed on
training machines and capturing isn't allowed?  Maybe Wireshark's only purpose
is to simply analyze capture files already taken elsewhere?  And if Wireshark
were to somehow determine that no capture driver was loaded, which service
should it attempt to start, npf or npcap?

> This isn't really a PCap-only issue. The capture capability is fine, just
> needs the appropriate driver started by default which it isn't always,
> although it should be.  It's also confusing, and can be trivially avoided. 

The capture driver should *not* necessarily always be started.

-- 
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 13978] Expression button limitations

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

   Hardware|x86 |All
Version|2.4.0   |Git
  Component|GTK+ UI |Qt UI
 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 14064] When using resolution 3440x1440 wireshark crashes when in "maximize" window mode.

[bugzilla-daemon]

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

--- Comment #4 from Christopher Maynard  ---
(In reply to Patrik Lindh from comment #0)
> When using resolution 3440x1440 wireshark crashes when in "maximize" window
> mode.
> Per default wireshark is maximized when freshly installed.
> 
> Seems to work with 2560x1440 and lower, couldn't try any resolutions between
> 2560x1440 and 3440x1440 due to screen limitations.
> 
> Workaround is to lower the resolution and then "restore" the window to not
> be "maximized" and then it will work with any resolution until maximized
> again.

Does this problem still occur with the latest stable version of Wireshark and
the Qt UI?  The GTK+ UI is no longer supported, so if the problem only occurs
with that UI, then the bug won't be fixed, but if it still happens even with
the Qt UI, then the component can be changed from GTK+ UI to Qt UI.

-- 
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 14139] The window does not fit on the screen.

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

 Status|INCOMPLETE  |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #2 from Christopher Maynard  ---
(In reply to Alexis La Goutte from comment #1)
> Do you have try with Qt (wireshark-qt) because there is no dev with GTK Gui

As Alexis mentioned, the GTK+ UI is no longer supported, so any bugs associated
with it won't be 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 14145] Wireshark 2.4.X crashes when attempting to merge pcap files

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

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

--- Comment #1 from Christopher Maynard  ---
(In reply to kalias5 from comment #0)
> There are no issues with the Qt GUI though

The GTK+ UI is no longer supported.

-- 
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 14260] .csv export exports "\t" rather then translating \t to ascii horizontal tab

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

 Ever confirmed|0   |1
Version|2.4.2   |2.6.6
  Component|GTK+ UI |Qt UI
 OS|Windows 7   |Windows
 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 9115] Default capture filter (not SSH or not RDP) has precedence over last-used capture filter

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

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

--- Comment #4 from Christopher Maynard  ---
The GTK+ UI is no longer supported and with the latest stable Wireshark version
and Qt UI, the filter to exclude RDP traffic is no longer automatically
applied, so this bug isn't relevant anymore, nor will it be fixed in the old
UI.

-- 
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 15299] Telephony -> VOIP Calls -> Flow Sequences strange behavior after you Play stream

[bugzilla-daemon]

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

Balling  changed:

   What|Removed |Added

   Severity|Minor   |Normal
   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 15299] Telephony -> VOIP Calls -> Flow Sequences strange behavior after you Play stream

[bugzilla-daemon]

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

Balling  changed:

   What|Removed |Added

Version|2.6.5   |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 14327] wont use default interface specified in preferences

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

Version|2.4.4   |2.6.6
   Severity|Major   |Normal
   Hardware|x86 |All
  Component|GTK+ UI |Qt UI
 OS|Windows 8.1 |Windows

-- 
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 4960] RTP Player: Audio and visual feedback get rapidly out of sync

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

 CC||osu_m...@mail.ru

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

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.___
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 14401] RTP Player: Audio and visual feedback get rapidly out of sync. Slow RTP audio data playback

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

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

--- Comment #1 from Christopher Maynard  ---


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

-- 
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 14605] "Drop by Jitter Buff" is no longer available.

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

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

--- Comment #1 from Christopher Maynard  ---
(In reply to Harvey S. Cohen from comment #0)
> Wireshark used to allow the user to specify a jitter buffer size, and then
> Wireshark would display the number of RTP packets dropped by the jitter
> buffer. This capability has disappeared.

The GTK+ UI is no longer supported so any bugs associated with it won't be
fixed.  The RTP Player dialog using the Qt UI does show the jitter buffer, so I
assume this bug isn't relevant to the Qt UI.

-- 
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 14713] graph analysis GTK does not work properly (not possible to scroll down or select)

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|INCOMPLETE  |RESOLVED

--- Comment #6 from Christopher Maynard  ---
(In reply to Michal Turek from comment #5)
> (In reply to Guy Harris from comment #4)
> > What happens with the Qt UI?
> > 
> > The GTK+ UI will not be supported in 3.0.
> 
> QT UI works fine

As Guy mentioned, the GTK+ UI is deprecated, so this "GTK+ only" bug won't be
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 15359] rpm-package target fails for tagged releases in git

[bugzilla-daemon]

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

--- Comment #6 from Gerrit Code Review  ---
Change 31504 merged by Gerald Combs:
tarball+RPM: Fetch our version from CMake.

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

-- 
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 9602] GUI hang in display filter dialog on Mac OS X 10.9

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

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

--- Comment #2 from Christopher Maynard  ---
(In reply to Christopher Maynard from comment #1)
> Does this still occur with the latest 1.10.8 version?

There's been no feedback for 5 years, so I'm closing the bug.

Note that Wireshark 1.10.5 is no longer supported, nor is the GTK+ UI, but if
the bug can be reproduced with the latest stable version of Wireshark and Qt
UI, 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 9114] Memory not released when starting a new capture w/o saving last capture

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

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

--- Comment #4 from Christopher Maynard  ---
A lot of memory leaks have been found and fixed in Wireshark since this bug was
filed, and there are tools, such as asan, that continue to help catch/plug
leaks; it's basically a never-ending, ongoing process.

I do believe the worst of the memory leaks have been fixed for a long time
though and in any case, since 1.10.0 is no longer supported, nor is the GTK+
UI, I'm closing the bug as fixed.  If more memory leaks are found with the
latest stable version of Wireshark and the Qt UI, then they will most likely be
found and fixed anyway, so I don't think there's any point in keeping this bug
open.

-- 
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 9062] Visual C++ Runtime Library Error "The application has requested the Runtime to terminate it in an unusual way." when trying to look at Statistics/IO Graph and Flow Graph

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|CONFIRMED   |RESOLVED

--- Comment #8 from Christopher Maynard  ---
(In reply to Evan Huus from comment #7)
> That's very odd. As far as I know, Wireshark relies on third-party libraries
> (GTK, Pango, Cairo) for most of its graph rendering, so if that is the
> problem then I suspect there isn't much we can do at our end.

Wireshark no longer supports the GTK+ UI, but has switched to the Qt UI.  If
the problem still exists with the GTK+ UI, then it won't be fixed, so I'm
closing the bug.  If the problem can be reproduced with the latest stable
Wireshark version using the Qt UI, 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 9058] Error in RTP Saving Payload format in raw form when RTP Payload is different from G.711.

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

  Component|GTK+ UI |Qt UI

--- Comment #5 from Christopher Maynard  ---
(In reply to Michal Puczynski from comment #3)
> I confirm this issue. It is present also in new releases 2.2.8 and 2.4.0 in
> both GUIs.

Since it seems that this bug is present in both GUI's, I've changed the
component to Qt UI because the GTK+ UI is no longer supported.

(In reply to Pavel Sindelka from comment #4)
> If a G.722 trace without any privacy concerns is needed to help debug, let
> me know.

If you can supply a capture file to help demonstrate and ultimately resolve
this bug, then please do.

-- 
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 8528] VoIP Graph Analysis window - INVITE not showing codecs

[bugzilla-daemon]

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

--- Comment #4 from Christopher Maynard  ---
Can someone confirm whether this bug still exists with the latest stable
version of Wireshark and the Qt UI?  The GTK+ UI is no longer supported, so if
it's not a problem with the Qt UI, this bug will be closed as WONTFIX.

-- 
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 15402] We should perhaps have a C extcap sample program

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

   Severity|Major   |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 8273] Changing configuration profile causes packet display to be processed multiple times

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #3 from Christopher Maynard  ---
This problem does not appear to exist with the Qt UI and latest stable version
of Wireshark.  Since the GTK+ UI is deprecated, I'm closing the bug as WONTFIX.

-- 
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 8269] can't search hex string in the current packet and highlight it with Ctrl+F

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

  Component|GTK+ UI |Qt UI

--- Comment #11 from Christopher Maynard  ---
The bug still exists with the Qt UI, so changing the component since the GTK+
UI is no longer supported.

-- 
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 8007] UI gets confused on playing decoded audio in rtp_player

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #6 from Christopher Maynard  ---
The GTK+ UI is no longer supported.

-- 
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 7935] Wrong Timestamps in RTP Player-Decode

[bugzilla-daemon]

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

--- Comment #3 from Christopher Maynard  ---
(In reply to Bertrand from comment #2)
> Looking at the RTP Player code it looks like Wrong Timestamps is incremented
> when the difference between 2 successive timestamps is not consistent (in
> samples) with the number of decoded bytes/2 in the former of the 2
> timestamps. I guess the decoded bytes/2 is due to the G711 decoding creating
> 2 bytes per sample?
> I still don't think this happens with this particular set of data?

Can someone confirm whether this bug still exists with the latest supported
version of Wireshark and the Qt UI?  Because Wireshark 1.8.2 is no longer
supported and neither is the GTK+ UI.

-- 
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 7671] capture options crashes when using named pipes

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

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

--- Comment #2 from Christopher Maynard  ---
(In reply to peter.kenyon from comment #1)
> is this related to 7511

No feedback for nearly 7 years.  Since bug 7511 was resolved and since
Wireshark 1.8.2 is no longer supported, nor is the GTK+ UI, for which this bug
was filed against, I'm going to close this bug.  If the problem can be
reproduced with a supported version of Wireshark using the Qt UI, then feel
free to reopen the bug and update the 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 3523] Inconsistent results of started_with_special_privs(), potential security hole

[bugzilla-daemon]

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

--- Comment #4 from Christopher Maynard  ---
(In reply to Guy Harris from comment #2)
> (I'm also not sure whether GTK+, when running as root, will load user
> theming plugins; Wireshark is a GTK+ application)

Not for much longer.  The GTK+ UI is deprecated.  Is this bug still relevant
then with the Qt UI, or can it be closed?

-- 
You are receiving this mail because:
You are the assignee for the bug.
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 9636] Voip player issue showing black

[bugzilla-daemon]

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

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)
> Any news... ?!

No news since the bug was opened 5 years ago, and the bug was filed against the
GTK+ UI component of the 1.10.5 version of Wireshark.  Since the GTK+ UI is
deprecated and that version of Wireshark is no longer supported, I'm closing
the bug.  If the problem can be reproduced with a supported version of
Wireshark and the Qt UI, then feel free to reopen the bug and update the
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 8993] The Wireshark icon doesn't show up in OS X 10.5

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

   Severity|Major   |Normal

--- Comment #8 from Christopher Maynard  ---
Does this bug still exist?  If so, should it be categorized as applicable to
the Qt UI, or perhaps even "Build process"?

-- 
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 8628] Capture columns disappear

[bugzilla-daemon]

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

Christopher Maynard  changed:

   What|Removed |Added

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

--- Comment #3 from Christopher Maynard  ---
I believe this bug is only relevant to the GTK+ UI, not to the Qt UI.  Since
the Gtk+ UI is deprecated, if the problem still exists it won't be 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 12901] make-version.pl shouldn't define VCSVERSION when building from a release source archive

[bugzilla-daemon]

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

Petr Sumbera  changed:

   What|Removed |Added

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

--- Comment #9 from Petr Sumbera  ---
I'm ok with the fix (Wireshark 2.6.6 (v2.6.6)). Closing. Thank you!

-- 
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 15413] RFC 8287 : IPv4 IGP-Prefix Segment ID section is not decoded by Wireshark.

[bugzilla-daemon]

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

--- Comment #13 from Dipankar Shaw  ---
@Uli,
Many thanks, Tested on version 
Version : Wireshark-win64-2.9.1-370-g34c3d010.exe
It is working fine.

-- 
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