https://bugs.winehq.org/show_bug.cgi?id=51983
Bug ID: 51983 Summary: foobar2000 v1.5.1+ crashes on startup with Wine v6.6+ with Windows version set to "Windows 10" Product: Wine Version: 6.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: the.derivative.of.calculus@gmail.com Distribution: ---
Created attachment 70970 --> https://bugs.winehq.org/attachment.cgi?id=70970 foobar2000 1.5.1 crash with windows 10 profile
I had an old version of foobar2000 that I had never got around to upgrading, so I only recently came across this issue. Looking online it appears that a few people ran into it starting with v6.6, and it still exists with v6.20 (and as far as I can tell no one bothered to report it): https://forum.winehq.org/viewtopic.php?t=35166 https://hydrogenaud.io/index.php?topic=54933.525
When you start foobar2000 with Windows version set to "Windows 8.1" or below it runs normally. However, if you use "Windows 10" the application window briefly appears before the whole application crashes. Testing it, this affects foobar2000 v1.5.1+
Looking through foobar2000's changelog: https://www.foobar2000.org/changelog
The one thing mentioning Windows 10 is: Reworked integration with Windows 10 Universal Volume Control. Enabled by default once again.
Looking at the error messages: 0024:fixme:combase:RoGetActivationFactory (L"Windows.Media.Playback.BackgroundMediaPlayer", {00000035-0000-0000-c000-000000000046}, 0032F9E4): semi-stub 0024:err:combase:RoGetActivationFactory Failed to find library for L"Windows.Media.Playback.BackgroundMediaPlayer"
I'm wondering if there's a regression with Wine's handling of media controls for Windows 10 or equivalent.