[Bug 50262] New: Xibo Player 1.7.3 crashes on start

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50262

Bug ID: 50262
           Summary: Xibo Player 1.7.3 crashes on start
           Product: Wine
           Version: 6.0-rc1
          Hardware: x86-64
               URL: https://github.com/xibosignage/xibo-cms/releases/downl
                    oad/1.7.3/xibo-client-1.7.3-win32-x86.msi
                OS: Mac OS X
            Status: NEW
          Keywords: download
          Severity: normal
          Priority: P2
         Component: wmi&wbemprox
          Assignee: [e-mail]
          Reporter: [e-mail]

Created attachment 68796
  --> https://bugs.winehq.org/attachment.cgi?id=68796
+wmiutils,+wbemprox log

This is probably related to Bug 35567. I tested using Wine-Mono, but native
dotnet exhibits the same issue.

Attached is a +wmiutils,+wbemprox log.

[Bug 50262] Xibo Player 1.7.3 crashes on start

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50262

--- Comment #1 from Hans Leidekker  ---
That suggests you have a non-loopback network adapter for which we can't get
retrieve the MAC address. Can you post the output of ifconfig?

[Bug 50262] Xibo Player 1.7.3 crashes on start

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50262

--- Comment #2 from Gijs Vermeulen  ---
Created attachment 68797
  --> https://bugs.winehq.org/attachment.cgi?id=68797
ifconfig output

Here you go. Not sure if it matters, but this is on macOS 10.14.6 (Wine
compiled with 10.13 SDK).

[Bug 50262] Xibo Player 1.7.3 crashes on start

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50262

--- Comment #3 from Hans Leidekker  ---
Thanks. Could you also post the output of this command (run from build root):

../wine/tools/runtest -P wine -T . -M iphlpapi.dll -p
dlls/iphlpapi/tests/iphlpapi_test.exe iphlpapi

That should tell us which interface gets index 2.

[Bug 50262] Xibo Player 1.7.3 crashes on start

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50262

--- Comment #4 from Gijs Vermeulen  ---
Created attachment 68799
  --> https://bugs.winehq.org/attachment.cgi?id=68799
test output

Done.

[Bug 50262] Xibo Player 1.7.3 crashes on start

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50262

--- Comment #5 from Hans Leidekker  ---
(In reply to Gijs Vermeulen from comment #4)
> Created attachment 68799 [details]
> test output

You actually have a number of interfaces without a MAC address (gif0, stn0,
XHC20, utun0). These are all software devices without a data link layer, so
it's expected. This also happens on Windows. A Wireguard VPN tunnel returns
VT_NULL for Win32_NetworkAdapterConfiguration.MACAddress, for example.

[Bug 50262] Xibo Player 1.7.3 crashes on start

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50262

--- Comment #6 from Gijs Vermeulen  ---
(In reply to Hans Leidekker from comment #5)
> (In reply to Gijs Vermeulen from comment #4)
> > Created attachment 68799 [details]
> > test output
>
> You actually have a number of interfaces without a MAC address (gif0, stn0,
> XHC20, utun0). These are all software devices without a data link layer, so
> it's expected. This also happens on Windows. A Wireguard VPN tunnel returns
> VT_NULL for Win32_NetworkAdapterConfiguration.MACAddress, for example.

Does that make this bug INVALID? I also tested 1.8.3 of this app, which doesn't
have this issue, so they must've changed/fixed something.

[Bug 50262] Xibo Player 1.7.3 crashes on start

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50262

--- Comment #7 from Hans Leidekker  ---
(In reply to Gijs Vermeulen from comment #6)
> (In reply to Hans Leidekker from comment #5)
> > (In reply to Gijs Vermeulen from comment #4)
> > > Created attachment 68799 [details]
> > > test output
> >
> > You actually have a number of interfaces without a MAC address (gif0, stn0,
> > XHC20, utun0). These are all software devices without a data link layer, so
> > it's expected. This also happens on Windows. A Wireguard VPN tunnel returns
> > VT_NULL for Win32_NetworkAdapterConfiguration.MACAddress, for example.
>
> Does that make this bug INVALID? I also tested 1.8.3 of this app, which
> doesn't have this issue, so they must've changed/fixed something.

Yes, I checked and it also crashes on Windows if I remove the ethernet
interface. It seems to have a hardcoded assumption that the interface at index
2 is a physical adapter.

[Bug 50262] Xibo Player 1.7.3 crashes on start

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50262

Gijs Vermeulen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

--- Comment #8 from Gijs Vermeulen  ---
(In reply to Hans Leidekker from comment #7)
> (In reply to Gijs Vermeulen from comment #6)
> > (In reply to Hans Leidekker from comment #5)
> > > (In reply to Gijs Vermeulen from comment #4)
> > > > Created attachment 68799 [details]
> > > > test output
> > >
> > > You actually have a number of interfaces without a MAC address (gif0, stn0,
> > > XHC20, utun0). These are all software devices without a data link layer, so
> > > it's expected. This also happens on Windows. A Wireguard VPN tunnel returns
> > > VT_NULL for Win32_NetworkAdapterConfiguration.MACAddress, for example.
> >
> > Does that make this bug INVALID? I also tested 1.8.3 of this app, which
> > doesn't have this issue, so they must've changed/fixed something.
>
> Yes, I checked and it also crashes on Windows if I remove the ethernet
> interface. It seems to have a hardcoded assumption that the interface at
> index 2 is a physical adapter.

Resolving INVALID in that case.

[Bug 50262] Xibo Player 1.7.3 crashes on start

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50262

Gijs Vermeulen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #9 from Gijs Vermeulen  ---
Closing.