Re: [Wireshark-dev] Glitches in UI when using recent buildbot development versions
Submitted https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15885 for the highlight issue. On Sat, Jun 29, 2019 at 7:59 AM Jason Cohen wrote: > One major annoyance with dark mode that I've been meaning to check if a > bug already exists, or report one, or fix... > > When you select something, the highlight is white (grey?) and the text > withing the highlight remains white (grey?). Thus you can't see it. > > Now, this may be just because in System Preferences | General, I have my > highlight color set to Graphite. Haven't worked through any permutations > yet. > > > > On Sat, Jun 29, 2019 at 12:47 AM Jaap Keuter > wrote: > >> Hi Jim, >> >> Any dark mode stuff going on? >> >> Thanks, >> Jaap >> >> On 28 Jun 2019, at 18:11, Jim Young wrote: >> >> Hello, >> >> I almost exclusively run development versions of Wireshark when doing my >> day to day troubleshooting tasks and I typically (but not always) do the >> analysis on a macOS system. >> >> >> >> ___ >> Sent via:Wireshark-dev mailing list >> Archives:https://www.wireshark.org/lists/wireshark-dev >> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev >> mailto:wireshark-dev-requ...@wireshark.org >> ?subject=unsubscribe > > ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Glitches in UI when using recent buildbot development versions
Could you post your Qt version? You will find it in the about dialog. > Am 29.06.2019 um 17:44 schrieb Ivan Nardi : > > Hi > >> On Fri, 28 Jun 2019 at 18:12, Jim Young wrote: >> >> The first glitch has to do with "Apply as filter". With this glitch I had >> right-mouse selected the tcp.stream field and then selected the Apply as >> filter. But instead an unexpected display filter was applied. I thought I >> had mis-clicked on the packet details items so I tried again but had the >> same results. I then expanded the frame tree and right-mouse clicked on >> frame.interface_id followed by Apply as filter but again the wrong filter >> was entered into the display filter field. At this point I opted to >> shutdown and restart Wireshark since this particular instance of Wireshark >> had been running for perhaps day or two and I had captured and opened >> numerous trace files. > > I am randomly facing the same issue: when a field is selected, if I select > "Apply/Prepare as filter" an unexpected filter (probably a previous one) is > executed > Environment: ubuntu 18.04, today master (but I have been seeing this glitch > from a couple of days) > Let me know if you need further information > > Ivan > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Glitches in UI when using recent buildbot development versions
Qt 5.9.5 Thanks Ivan On Sat, 29 Jun 2019 at 21:51, Roland Knall wrote: > Could you post your Qt version? You will find it in the about dialog. > > Am 29.06.2019 um 17:44 schrieb Ivan Nardi : > > Hi > > On Fri, 28 Jun 2019 at 18:12, Jim Young wrote: > >> >> The first glitch has to do with "Apply as filter". With this glitch I >> had right-mouse selected the tcp.stream field and then selected the Apply >> as filter. But instead an unexpected display filter was applied. I >> thought I had mis-clicked on the packet details items so I tried again but >> had the same results. I then expanded the frame tree and right-mouse >> clicked on frame.interface_id followed by Apply as filter but again the >> wrong filter was entered into the display filter field. At this point I >> opted to shutdown and restart Wireshark since this particular instance of >> Wireshark had been running for perhaps day or two and I had captured and >> opened numerous trace files. >> > > I am randomly facing the same issue: when a field is selected, if I select > "Apply/Prepare as filter" an unexpected filter (probably a previous one) is > executed > Environment: ubuntu 18.04, today master (but I have been seeing this > glitch from a couple of days) > Let me know if you need further information > > Ivan > > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe > > > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Question about dissector "enhancement" / bug
On Jun 28, 2019, at 7:11 AM, Maynard, Chris wrote:
> You can find the download link by navigating from https://www.wireshark.org/
> -> Download -> More downloads and documentation can be found on the downloads
> page -> Live on the Bleeding Edge: You can download source code packages and
> Windows installers which are automatically created each time code is checked
> into the source code repository. These packages are available in the
> automated build section of our download area.
You'll also find that if you're running Linux, you'll have to compile the
binary yourself, as we're not building binary RPMs/DEBs/etc. or Flatpak/{your
favorite distribution-independent packaging format} versions.
(That's also a problem with vendor-distributed plugins - they are often
oriented towards a world in which Microsoft literally has a 100% share of the
desktop/notebook computing market, as they often offer only Windows compiled
versions of the plugin.
Perhaps this is another reason to have a built-in ability to read protocol
descriptions in a format such as WSGD, or to make Lua a mandatory dependency,
so the vendors could distribute dissector plugins in source form so that
*anybody* can use them conveniently.)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Ubuntu 16.04 Debian build fails missing symbols - crypto_scalarmult_curve25519@Base 2.9.0
On Mon, Jun 17, 2019 at 03:17:13PM +, Anders Broman wrote: > Hi, > > dpkg-gensymbols: warning: some symbols or patterns disappeared in the > symbols file: see diff output below > > dpkg-gensymbols: warning: debian/libwsutil0/DEBIAN/symbols doesn't match > completely debian/libwsutil0.symbols > > --- debian/libwsutil0.symbols (libwsutil0_3.1.0_amd64) > > +++ dpkg-gensymbolsasqzzn 2019-06-17 16:50:31.010999810 +0200 > > @@ -50,8 +50,8 @@ > > create_tempfile@Base 1.12.0~rc1 > > create_timestamp@Base 2.5.0 > > crypt_des_ecb@Base 2.3.0 > > - crypto_scalarmult_curve25519@Base 2.9.0 > > - crypto_scalarmult_curve25519_base@Base 2.9.0 > > +#MISSING: 3.1.0# crypto_scalarmult_curve25519@Base 2.9.0 > > +#MISSING: 3.1.0# crypto_scalarmult_curve25519_base@Base 2.9.0 > > data_file_url@Base 2.3.0 > > decrypt_xtea_ecb@Base 2.5.0 > > decrypt_xtea_le_ecb@Base 2.5.0 > > > > Do we need dummy versions if gcrypt is not of the right version? Why did it > not fail before? No consumer until now? This API is used by the WireGuard dissector (since Wireshark 3.0) and requires Libgcrypt 1.7 which is not present in Ubuntu 16.04, Debian Jessie and RHEL6/7. Debian Jessie is already EOL, ubuntu 16.04 is EOL in April 2021 however. Callers must check for the availability of an appropriate Libgcrypt version before calling it. For simplicity, I have a slight preference for not adding dummy versions, but if you think it is better to have it, it could be done anyway? -- Kind regards, Peter Wu https://lekensteyn.nl ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Certificate Request not being displayed by Wireshark even when that info is in the packet
Hi Jaime, To correctly reconstruct out-of-order TCP segments, you have to enable "Reassemble out-of-order segments" in the TCP preferences. See https://www.wireshark.org/docs/wsug_html_chunked/ChAdvReassemblySection.html#ChAdvReassemblyTcp Kind regards, Peter On Mon, Jun 10, 2019 at 07:04:04PM -0500, Jaime Hablutzel wrote: > Hi Peter, I'm sorry for the delay. > > I've just found the "Certificate Request" in a subsequent "TCP > Out-Of-Order" packet (see https://filebin.ca/4kArOrO9xTaL). > > Thank you. > > On Mon, Jun 3, 2019 at 9:05 AM Peter Wu wrote: > > > Hi Jaime, > > > > On Sun, Jun 02, 2019 at 10:59:18PM -0500, Jaime Hablutzel wrote: > > > I'm not an expert in the TLS protocol but I've just stumbled upon the > > > following packet (and I didn't have enough time to debug this further), > > > https://filebin.ca/4jHrWy2tkGQ6, which contains the "Certificate > > Request" > > > list of accepted certificates, but Wireshark is failing to display it as > > it > > > can be observed in https://i.imgur.com/HrKevzC.png. > > > > > > Is it possibly a bug?. > > > > Could you share a capture file with the next non-empty TCP segment? The > > hidden part is a TLS record of 3577 (0xdf9) bytes and fits a handshake > > message (Certificate Request) of 3569 (0xdf1) bytes. If TCP reassembly > > is enabled, it should have been reconstructed in the next TCP segment. > > -- > > Kind regards, > > Peter Wu > > https://lekensteyn.nl ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Glitches in UI when using recent buildbot development versions
One major annoyance with dark mode that I've been meaning to check if a bug already exists, or report one, or fix... When you select something, the highlight is white (grey?) and the text withing the highlight remains white (grey?). Thus you can't see it. Now, this may be just because in System Preferences | General, I have my highlight color set to Graphite. Haven't worked through any permutations yet. On Sat, Jun 29, 2019 at 12:47 AM Jaap Keuter wrote: > Hi Jim, > > Any dark mode stuff going on? > > Thanks, > Jaap > > On 28 Jun 2019, at 18:11, Jim Young wrote: > > Hello, > > I almost exclusively run development versions of Wireshark when doing my > day to day troubleshooting tasks and I typically (but not always) do the > analysis on a macOS system. > > > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Glitches in UI when using recent buildbot development versions
Hi On Fri, 28 Jun 2019 at 18:12, Jim Young wrote: > > The first glitch has to do with "Apply as filter". With this glitch I had > right-mouse selected the tcp.stream field and then selected the Apply as > filter. But instead an unexpected display filter was applied. I thought I > had mis-clicked on the packet details items so I tried again but had the > same results. I then expanded the frame tree and right-mouse clicked on > frame.interface_id followed by Apply as filter but again the wrong filter > was entered into the display filter field. At this point I opted to > shutdown and restart Wireshark since this particular instance of Wireshark > had been running for perhaps day or two and I had captured and opened > numerous trace files. > I am randomly facing the same issue: when a field is selected, if I select "Apply/Prepare as filter" an unexpected filter (probably a previous one) is executed Environment: ubuntu 18.04, today master (but I have been seeing this glitch from a couple of days) Let me know if you need further information Ivan ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Glitches in UI when using recent buildbot development versions
Hi I cannot confirm those glitches on macOS. Especially the second one seems very strange to me. At this point I think it would be best if you add a bug report. If you are running the most recent macOS (Mojave), you could also create a video very easily (cmd+shift+5 for the builtin screen recorder) and attach that to the bug. Please CC me on the bug, as I am currently messing around with the context menus, and it might be caused by that. But I would more prominently suggest, that the used Qt version is buggy. Nethertheless, we have to investigate. cheers Roland Am Sa., 29. Juni 2019 um 07:47 Uhr schrieb Jaap Keuter < jaap.keu...@xs4all.nl>: > Hi Jim, > > Any dark mode stuff going on? > > Thanks, > Jaap > > On 28 Jun 2019, at 18:11, Jim Young wrote: > > Hello, > > I almost exclusively run development versions of Wireshark when doing my > day to day troubleshooting tasks and I typically (but not always) do the > analysis on a macOS system. > > > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Ubuntu 16.04 Debian build fails missing symbols - crypto_scalarmult_curve25519@Base 2.9.0
Den lör 29 juni 2019 13:24Peter Wu skrev: > On Mon, Jun 17, 2019 at 03:17:13PM +, Anders Broman wrote: > > Hi, > > > > dpkg-gensymbols: warning: some symbols or patterns disappeared in the > > symbols file: see diff output below > > > > dpkg-gensymbols: warning: debian/libwsutil0/DEBIAN/symbols doesn't match > > completely debian/libwsutil0.symbols > > > > --- debian/libwsutil0.symbols (libwsutil0_3.1.0_amd64) > > > > +++ dpkg-gensymbolsasqzzn 2019-06-17 16:50:31.010999810 +0200 > > > > @@ -50,8 +50,8 @@ > > > > create_tempfile@Base 1.12.0~rc1 > > > > create_timestamp@Base 2.5.0 > > > > crypt_des_ecb@Base 2.3.0 > > > > - crypto_scalarmult_curve25519@Base 2.9.0 > > > > - crypto_scalarmult_curve25519_base@Base 2.9.0 > > > > +#MISSING: 3.1.0# crypto_scalarmult_curve25519@Base 2.9.0 > > > > +#MISSING: 3.1.0# crypto_scalarmult_curve25519_base@Base 2.9.0 > > > > data_file_url@Base 2.3.0 > > > > decrypt_xtea_ecb@Base 2.5.0 > > > > decrypt_xtea_le_ecb@Base 2.5.0 > > > > > > > > Do we need dummy versions if gcrypt is not of the right version? Why did > it > > not fail before? No consumer until now? > > This API is used by the WireGuard dissector (since Wireshark 3.0) and > requires Libgcrypt 1.7 which is not present in Ubuntu 16.04, Debian > Jessie and RHEL6/7. Debian Jessie is already EOL, ubuntu 16.04 is EOL in > April 2021 however. > > Callers must check for the availability of an appropriate Libgcrypt > version before calling it. For simplicity, I have a slight preference > for not adding dummy versions, but if you think it is better to have it, > it could be done anyway? > -- > Kind regards, > Peter Wu > https://lekensteyn.nl I just want the build to succeed :-) > > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Glitches in UI when using recent buildbot development versions
I'm still running on High Sierra (10.13.6) so do not have any option to enable Dark mode. The version of Qt deployed on the macOS buildbot changed recently.When I previously tested with the development buildbot version 3.1.0rc0-1125-g263969168747 it reported "Compiled (64-bit) with Qt 5.12.1". The later versions where I saw transparent context menu issue reported "Compiled (64-bit) with Qt 5.12.4". I forced the development buildbot to rebuild the Wireshark 3.1.0rc0-1125-g263969168747 which now reports Qt 5.12.4 and now see the transparent context menu issue. This transparent context menu issue can be triggered in the file list on the Wireshark UI Welcom page. Looks like might be something specific to Qt 5.12.4. Best regards, Jim Y. On Sat, Jun 29, 2019 at 8:24 AM Roland Knall wrote: > Hi > > I cannot confirm those glitches on macOS. Especially the second one seems > very strange to me. At this point I think it would be best if you add a bug > report. If you are running the most recent macOS (Mojave), you could also > create a video very easily (cmd+shift+5 for the builtin screen recorder) > and attach that to the bug. > > Please CC me on the bug, as I am currently messing around with the context > menus, and it might be caused by that. But I would more prominently > suggest, that the used Qt version is buggy. Nethertheless, we have to > investigate. > > cheers > Roland > > Am Sa., 29. Juni 2019 um 07:47 Uhr schrieb Jaap Keuter < > jaap.keu...@xs4all.nl>: > >> Hi Jim, >> >> Any dark mode stuff going on? >> >> Thanks, >> Jaap >> >> On 28 Jun 2019, at 18:11, Jim Young wrote: >> >> Hello, >> >> I almost exclusively run development versions of Wireshark when doing my >> day to day troubleshooting tasks and I typically (but not always) do the >> analysis on a macOS system. >> >> >> >> ___ >> Sent via:Wireshark-dev mailing list >> Archives:https://www.wireshark.org/lists/wireshark-dev >> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev >> mailto:wireshark-dev-requ...@wireshark.org >> ?subject=unsubscribe > > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
