https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8993
Christopher Maynard changed:
What|Removed |Added
Severity|Major |Normal
--- Comment #8 from
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
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9636
Christopher Maynard changed:
What|Removed |Added
Resolution|--- |WORKSFORME
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
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9062
Christopher Maynard changed:
What|Removed |Added
Resolution|--- |WONTFIX
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15402
Christopher Maynard changed:
What|Removed |Added
Severity|Major |Enhancement
--
You are
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
>
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8269
Christopher Maynard changed:
What|Removed |Added
Component|GTK+ UI |Qt UI
--- Comment #11 from
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8273
Christopher Maynard changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9058
Christopher Maynard changed:
What|Removed |Added
Component|GTK+ UI |Qt UI
--- Comment #5 from
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8628
Christopher Maynard changed:
What|Removed |Added
Resolution|--- |WONTFIX
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7671
Christopher Maynard changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8007
Christopher Maynard changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9114
Christopher Maynard changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14713
Christopher Maynard changed:
What|Removed |Added
Resolution|--- |WONTFIX
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13978
Christopher Maynard changed:
What|Removed |Added
Hardware|x86 |All
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://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12557
Christopher Maynard changed:
What|Removed |Added
Resolution|--- |WONTFIX
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14327
Christopher Maynard changed:
What|Removed |Added
Version|2.4.4 |2.6.6
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14260
Christopher Maynard changed:
What|Removed |Added
Ever confirmed|0 |1
Version|2.4.2
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13820
Christopher Maynard changed:
What|Removed |Added
Version|2.2.7 |Git
Hardware|x86
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
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
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13782
Christopher Maynard changed:
What|Removed |Added
Resolution|WORKSFORME |NOTOURBUG
--- Comment #5
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13661
Christopher Maynard changed:
What|Removed |Added
Resolution|--- |WORKSFORME
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
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9602
Christopher Maynard changed:
What|Removed |Added
Resolution|--- |WORKSFORME
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9115
Christopher Maynard changed:
What|Removed |Added
Resolution|--- |WONTFIX
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14139
Christopher Maynard changed:
What|Removed |Added
Status|INCOMPLETE |RESOLVED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14145
Christopher Maynard changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
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.
>
>
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13920
Christopher Maynard changed:
What|Removed |Added
Component|GTK+ UI |Qt UI
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13882
Christopher Maynard changed:
What|Removed |Added
OS|Windows 7 |Windows
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13782
Christopher Maynard changed:
What|Removed |Added
Status|INCOMPLETE |RESOLVED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13717
Christopher Maynard changed:
What|Removed |Added
Version|2.2.5 |Git
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13314
Christopher Maynard changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
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
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14605
Christopher Maynard changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15299
Balling changed:
What|Removed |Added
Severity|Minor |Normal
Priority|Low
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
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
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13782
Guy Harris changed:
What|Removed |Added
Hardware|x86 |All
Component|GTK+ UI
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13318
Christopher Maynard changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12597
Christopher Maynard changed:
What|Removed |Added
CC||mazu...@gazeta.pl
---
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13095
Christopher Maynard changed:
What|Removed |Added
Resolution|--- |WORKSFORME
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4960
Christopher Maynard changed:
What|Removed |Added
CC||osu_m...@mail.ru
---
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14401
Christopher Maynard changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13450
Christopher Maynard changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
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
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12126
Christopher Maynard changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11638
Christopher Maynard changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11622
Christopher Maynard changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
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:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11651
Christopher Maynard changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12147
Christopher Maynard changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12113
Christopher Maynard changed:
What|Removed |Added
Resolution|--- |WORKSFORME
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11578
Christopher Maynard changed:
What|Removed |Added
Resolution|--- |WORKSFORME
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
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
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
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
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
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
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12901
Petr Sumbera changed:
What|Removed |Added
Resolution|--- |FIXED
64 matches
Mail list logo