https://bugs.winehq.org/show_bug.cgi?id=40567 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Foobar 2000 doesn't run or |Foobar2000 1.x doesn't run |takes too long to open |or takes too long to open CC| |focht(a)gmx.net Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Keywords| |download URL| |https://web.archive.org/web | |/20210217111254/https://www | |.foobar2000.org/files/fooba | |r2000_v1.1.18.exe --- Comment #7 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, with mainline Wine 1.8.x, Foobar2000 1.0 always reported "internal error/damaged components" on startup. The critical section timeout from OP's console output was likely something different, Wine-Staging specific. Anyway, it started working with mainline Wine 1.9.10 $ sha1sum foobar2000_v1.* 4deadea729bd1e1c8167ae37a7fe07e142eb15d0 foobar2000_v1.0.exe f3b010dbe90160ebb954544598ddefbb876651c4 foobar2000_v1.1.18.exe 14e088f3418e51991e9ec797819250094c2ffbb2 foobar2000_v1.3.exe $ du -sh foobar2000_v1.* 3.0M foobar2000_v1.0.exe 3.3M foobar2000_v1.1.18.exe 3.6M foobar2000_v1.3.exe $ wine --version wine-1.9.10 Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.