[Bug 52100] New: foobar2000 crashes immediately after start
https://bugs.winehq.org/show_bug.cgi?id=52100 Bug ID: 52100 Summary: foobar2000 crashes immediately after start Product: Wine Version: 6.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winegstreamer Assignee: wine-bugs(a)winehq.org Reporter: matthias.grobarek(a)posteo.de Distribution: --- Since Wine 6.20, I’ve been experiencing crashes as soon as foobar2000 has started. Wine 6.21 and 6.22 are also affected. I saw in the 6.20 changelog that some winegstreamer implementations were moved to the wm_reader object. Maybe my crash is a side effect of that? I’m on Gentoo Linux so my Wine is self-built. Also note that I use wine-staging. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=52100 --- Comment #1 from matthias.grobarek(a)posteo.de --- Created attachment 71118 --> https://bugs.winehq.org/attachment.cgi?id=71118 Wine console output without WINEDEBUG flags -- 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.
https://bugs.winehq.org/show_bug.cgi?id=52100 --- Comment #2 from matthias.grobarek(a)posteo.de --- Created attachment 71119 --> https://bugs.winehq.org/attachment.cgi?id=71119 Wine console output with WINEDEBUG=warn+all -- 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.
https://bugs.winehq.org/show_bug.cgi?id=52100 matthias.grobarek(a)posteo.de changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Gentoo -- 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.
https://bugs.winehq.org/show_bug.cgi?id=52100 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #3 from Austin English <austinenglish(a)gmail.com> --- Did you build with USE=-gstreamer? What are your USE flags? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=52100 matthias.grobarek(a)posteo.de changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEEDINFO |RESOLVED --- Comment #4 from matthias.grobarek(a)posteo.de --- Oh my God, you are completely right, why haven’t I taken a look at this myself?! I had the USE flag gstreamer disabled because sometime in the past I didn’t want Portage to re-emerge dozens of packages with abi_x86_32. I reactivated the gstreamer USE flag and let Portage re-emerge all those packages. wine-staging 6.22 works properly now. I’m sorry to have bothered you with my own mistakes. :( -- 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.
https://bugs.winehq.org/show_bug.cgi?id=52100 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #5 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- Closing. -- 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.
participants (1)
-
WineHQ Bugzilla