> -----Original Message-----
> From: Wireshark-dev <wireshark-dev-bounces@xxxxxxxxxxxxx> On Behalf Of
> Anders Broman via Wireshark-dev
> Sent: Tuesday, December 8, 2020 11:29 AM
> To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
> Cc: Anders Broman <anders.broman@xxxxxxxxxxxx>
> Subject: Re: [Wireshark-dev] Recent console warning from Qt?
>
> -----Original Message-----
> From: Wireshark-dev <wireshark-dev-bounces@xxxxxxxxxxxxx> On Behalf Of
> Maynard, Christopher via Wireshark-dev
> Sent: den 8 december 2020 16:20
> To: 'Developer support list for Wireshark' <wireshark-dev@xxxxxxxxxxxxx>
> Cc: Maynard, Christopher <Christopher.Maynard@xxxxxxx>
> Subject: Re: [Wireshark-dev] Recent console warning from Qt?
>
> > From: Wireshark-dev <wireshark-dev-bounces@xxxxxxxxxxxxx> On Behalf Of
> > Anders Broman via Wireshark-dev
> > Sent: Tuesday, December 8, 2020 3:55 AM
> > To: wireshark-dev@xxxxxxxxxxxxx
> > Cc: Anders Broman <anders.broman@xxxxxxxxxxxx>
> > Subject: [Wireshark-dev] Recent console warning from Qt?
> >
> > Hi,
> > Has anyone else seen this Main Warn QWinTaskbarButton:
> > qIID_ITaskbarList4 was not initialized: 0x00000000, ?
> > Regards
> > Anders
> >
>
> I'm not seeing that. Here's my Wireshark information for reference:
>
> 3.5.0 (v3.5.0rc0-316-gc876b34ed103)
>
> Compiled (64-bit) with Qt 5.15.2, with libpcap, with GLib 2.52.3, with zlib
> 1.2.11, with SMI 0.4.8, with c-ares 1.17.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.42.0, with brotli, with LZ4, with Zstandard, with
> Snappy, with libxml2 2.9.9, with QtMultimedia, with automatic updates using
> WinSparkle 0.5.7, with AirPcap, with SpeexDSP (using bundled resampler).
>
> Running on 64-bit Windows 10 (2004), build 19041, with Intel(R) Xeon(R) CPU
> E3-1505M v5 @ 2.80GHz (with SSE4.2), with 16231 MB of physical memory,
> with locale English_United States.utf8, with light display mode, without HiDPI,
> with Npcap version 1.00, based on libpcap version 1.9.1, with GnuTLS 3.6.3,
> with Gcrypt 1.8.3, with brotli 1.0.9, with AirPcap 4.1.0 build 1622, binary plugins
> supported (21 loaded).
>
> Built using Microsoft Visual Studio 2019 (VC++ 14.28, build 29333).
>
>
> I have
> Wireshark 3.5.0 (v3.5.0rc0-317-g9722eaf93456)
>
> Copyright 1998-2020 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
> License GPLv2+: GNU GPL version 2 or later <https://www.gnu.org/licenses/gpl-
> 2.0.html>
> 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.15.1, with libpcap, with GLib 2.52.3, with zlib
> 1.2.11, with SMI 0.4.8, with c-ares 1.17.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.42.0, with brotli, with LZ4, with Zstandard, with
> Snappy, with libxml2 2.9.9, with QtMultimedia, with automatic updates using
> WinSparkle 0.5.7, with AirPcap, with SpeexDSP (using bundled resampler).
>
> Running on 64-bit Windows 10 (1809), build 17763, with Intel(R) Core(TM) i7-
> 8650U CPU @ 1.90GHz (with SSE4.2), with 32611 MB of physical memory, with
> locale Swedish_Sweden.utf8, with Npcap version 0.9996, based on libpcap
> version 1.9.1, with GnuTLS 3.6.3, with Gcrypt 1.8.3, with brotli 1.0.9, with
> AirPcap
> 4.1.0 build 1622, binary plugins supported (0 loaded).
>
> Built using Microsoft Visual Studio 2019 (VC++ 14.28, build 29334).
>
> Perhaps it is fixed in Qt 5.15.2...
> Regards
> Anders
Perhaps. But on the other hand, the Windows buildbots[1] are still using Qt 5.15.1. If you download, install and run the latest automated build[2], do you still see that warning? If not, then it might be something unique to your environment.
- Chris
[1]: https://buildbot.wireshark.org/wireshark-master/waterfall
[2]: https://www.wireshark.org/download/automated/win64/
CONFIDENTIALITY NOTICE: This message is the property of International Game Technology PLC and/or its subsidiaries and may contain proprietary, confidential or trade secret information. This message is intended solely for the use of the addressee. If you are not the intended recipient and have received this message in error, please delete this message from your system. Any unauthorized reading, distribution, copying, or other use of this message or its attachments is strictly prohibited.
