[Bug 55143] New: unimplemented function winegstreamer.dll.winegstreamer_create_video_decoder called in 32-bit code (0x7b012566)
https://bugs.winehq.org/show_bug.cgi?id=55143 Bug ID: 55143 Summary: unimplemented function winegstreamer.dll.winegstreamer_create_video_decoder called in 32-bit code (0x7b012566) Product: Wine Version: 8.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winegstreamer Assignee: wine-bugs(a)winehq.org Reporter: zeroredgrave(a)gmail.com Distribution: --- Created attachment 74705 --> https://bugs.winehq.org/attachment.cgi?id=74705 Cannot Launch the App probably the introduction of the game( before main menu) cannot create a video decoder i think Max Payne 2 Cannot Launch due an unimplemented function winegstreamer.dll.winegstreamer_create_video_decoder called in 32-bit code (0x7b012566) -- 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=55143 --- Comment #1 from Rafał Mużyło <galtgendo(a)o2.pl> --- First of all, screenshots of console output are of negative added value over just the text output. The message itself is a bit odd. As you say it's 32bit code, chances are you're either running out of memory or vm space. -- 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=55143 --- Comment #2 from zeroredgrave(a)gmail.com --- (In reply to Rafał Mużyło from comment #1)
First of all, screenshots of console output are of negative added value over just the text output.
The message itself is a bit odd. As you say it's 32bit code, chances are you're either running out of memory or vm space.
i have no clue on why i got an error. And i don't have ideas how to fix the issue on Max Payne 2 using wine-stable version 8.0.1. i have 16GB of RAM though -- 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=55143 --- Comment #3 from Nikolay Sivov <bunglehead(a)gmail.com> --- It's possible you have a build without winegstreamer, because gstreamer wasn't available at build time for example. If the game tries to use ir50_32.dll, it will crash like that. So check if you have winegstreamer binaries in your build. -- 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=55143 --- Comment #4 from zeroredgrave(a)gmail.com --- (In reply to Nikolay Sivov from comment #3)
It's possible you have a build without winegstreamer, because gstreamer wasn't available at build time for example. If the game tries to use ir50_32.dll, it will crash like that. So check if you have winegstreamer binaries in your build.
i checked on system32 and there is no wingstreamer.dll. So that's why i got an error. But how can add wingstreamer.dll on winetricks? -- 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=55143 --- Comment #5 from Nikolay Sivov <bunglehead(a)gmail.com> --- (In reply to zeroredgrave from comment #4)
(In reply to Nikolay Sivov from comment #3)
It's possible you have a build without winegstreamer, because gstreamer wasn't available at build time for example. If the game tries to use ir50_32.dll, it will crash like that. So check if you have winegstreamer binaries in your build.
i checked on system32 and there is no wingstreamer.dll. So that's why i got an error. But how can add wingstreamer.dll on winetricks?
You can't add it with winetricks, wine should be built with gstreamer support. -- 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=55143 --- Comment #6 from zeroredgrave(a)gmail.com --- (In reply to Nikolay Sivov from comment #5)
(In reply to zeroredgrave from comment #4)
(In reply to Nikolay Sivov from comment #3)
It's possible you have a build without winegstreamer, because gstreamer wasn't available at build time for example. If the game tries to use ir50_32.dll, it will crash like that. So check if you have winegstreamer binaries in your build.
i checked on system32 and there is no wingstreamer.dll. So that's why i got an error. But how can add wingstreamer.dll on winetricks?
You can't add it with winetricks, wine should be built with gstreamer support.
how can i fix? -- 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=55143 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #7 from Zeb Figura <z.figura12(a)gmail.com> --- How did you build or obtain Wine? -- 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=55143 --- Comment #8 from Rafał Mużyło <galtgendo(a)o2.pl> --- At this point, I'd like to remind you of bug 53819, which, while referring to a different lib/function, basically is word-for-word equivalent. That's why I suspect OOM/VMS problem. -- 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=55143 --- Comment #9 from Rafał Mużyło <galtgendo(a)o2.pl> --- ..on unrelated note: Zeb, would you look at the patches in bug 54034 ? First is almost certainly correct, second has a better code quality, but has an additional part that's pure guesstimate on below tea leaves quality, so it would be better to just lift the correct part out of it. -- 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=55143 --- Comment #10 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Rafał Mużyło from comment #8)
At this point, I'd like to remind you of bug 53819, which, while referring to a different lib/function, basically is word-for-word equivalent.
That's why I suspect OOM/VMS problem.
This error message is not related to address space exhaustion, and for that matter I see no evidence that 53819 is either. (In reply to Rafał Mużyło from comment #9)
..on unrelated note: Zeb, would you look at the patches in bug 54034 ?
First is almost certainly correct, second has a better code quality, but has an additional part that's pure guesstimate on below tea leaves quality, so it would be better to just lift the correct part out of it.
Please stop bringing up unrelated bugs. -- 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=55143 --- Comment #11 from Rafał Mużyło <galtgendo(a)o2.pl> --- The message itself isn't, but there also a function, that definitely is implemented, is reported as missing due to using delayed load mechanism. As for being a nag, I only do that if I receive no valid feedback *and* I'm nearly sure I have a good point. In that particular case, the bug is over 6 months old *and* that first patch almost certainly does what the API docs tell it's supposed to do (as a random bonus, the main part of that particular bug - unrelated to the patches - is about dying due to excessive memory consumption by graphics). -- 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=55143 --- Comment #12 from zeroredgrave(a)gmail.com --- there is way to fix or wait for new update patches for next release version? -- 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=55143 --- Comment #13 from Rafał Mużyło <galtgendo(a)o2.pl> --- If it actually *is* a memory consumption / VMS problem, it would *at minimum* take the devs figuring out why so much memory is being consumed. Btw., for a 32bit windows program, you don't have 16GB, only 4 - and that includes all the backend libs. As for seeing if it's pure OOM or the VMS variant, you can see VMS values in /proc/<pid>/status (top also shows that value in its default setup). -- 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=55143 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick(a)piezo-forte.be --- Comment #14 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to zeroredgrave from comment #12)
there is way to fix or wait for new update patches for next release version?
(In reply to Zeb Figura from comment #7)
How did you build or obtain Wine?
Hello, Please answer the question. 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.
https://bugs.winehq.org/show_bug.cgi?id=55143 --- Comment #15 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Rafał Mużyło from comment #11)
The message itself isn't, but there also a function, that definitely is implemented, is reported as missing due to using delayed load mechanism.
Yes. There are also far more likely ways for that to be the case than address space exhaustion. Failure to load winegstreamer is unlikely to be due to address space exhaustion because it is far more likely to be due to winegstreamer never having been compiled. Failure to load uxtheme is unlikely to be due to address space exhaustion because it is loaded almost immediately during user32 initialization.
As for being a nag, I only do that if I receive no valid feedback *and* I'm nearly sure I have a good point. In that particular case, the bug is over 6 months old *and* that first patch almost certainly does what the API docs tell it's supposed to do (as a random bonus, the main part of that particular bug - unrelated to the patches - is about dying due to excessive memory consumption by graphics).
No, you misunderstand. I did not say "stop bringing up unrelated bugs unless you feel entitled to a response". I said "stop bringing up unrelated bugs". Period. Yes, sometimes your bug goes unexamined for months or even years. That is the consequence of reporting bugs to a volunteer-driven project. It is especially the consequence when you consistently ignore the bug tracker directions, or requests for information, because you think you know better. -- 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=55143 --- Comment #16 from Rafał Mużyło <galtgendo(a)o2.pl> --- ...if I trimmed it down to the first part, I'd consider the patch good enough to be sent to be sent to the list, but I've only written it after you've switched to merge requests only, so :shrug:... -- 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=55143 --- Comment #17 from Rafał Mużyło <galtgendo(a)o2.pl> --- ...also, I've said 'plain OOM *or* VMS'; In that uxtheme bug, uxtheme is only loaded for the crash dialog, so at that point it could be either. It actually doesn't matter; what does is that being unable to load library due to lack of memory (in one sense or the other) is far more likely than the library that has very little code (and seemingly no conditionals) not getting built. -- 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=55143 --- Comment #18 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Rafał Mużyło from comment #17)
...also, I've said 'plain OOM *or* VMS';
The same point applies. uxtheme is going to be loaded early in the process, before the program is likely to do anything that eats up memory, virtual or physical. -- 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=55143 --- Comment #19 from Rafał Mużyło <galtgendo(a)o2.pl> --- ...OK, let the reporter talk for themself: are you using your own build of wine or is it a package you've downloaded from a site or installed by your package manager ? (also, you may also need to check syswow64 dir too, not just system32 - they're actually reversed to what the number at the end suggests (unless you've explicitly created a pure 32bit prefix, but that seems unlikely)) -- 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=55143 --- Comment #20 from zeroredgrave(a)gmail.com ---
(In reply to Zeb Figura from comment #7)
How did you build or obtain Wine? i just install on terminal not build & compiling
-- 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=55143 --- Comment #21 from zeroredgrave(a)gmail.com ---
(In reply to Zeb Figura from comment #7)
How did you build or obtain Wine? i installed wine stable version on linux mint terminal not build & compiling
-- 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=55143 --- Comment #22 from zeroredgrave(a)gmail.com --- (In reply to Rafał Mużyło from comment #19)
...OK, let the reporter talk for themself: are you using your own build of wine or is it a package you've downloaded from a site or installed by your package manager ?
i download in mint repository and try upgrade from latest wine stable version on website
(also, you may also need to check syswow64 dir too, not just system32 - they're actually reversed to what the number at the end suggests (unless you've explicitly created a pure 32bit prefix, but that seems unlikely))
i never created any wine prefix until now and i'm using a default wine prefix. i checked on dir and found syswow64 dir inside windows dir -- 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=55143 --- Comment #23 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to zeroredgrave from comment #22)
(also, you may also need to check syswow64 dir too, not just system32 - they're actually reversed to what the number at the end suggests (unless you've explicitly created a pure 32bit prefix, but that seems unlikely))
i never created any wine prefix until now and i'm using a default wine prefix. i checked on dir and found syswow64 dir inside windows dir
Hello, What he says is to check if winegstreamer.dll is present or not in windows/syswow64 dir, not just that the dir exists. It is 'winegstreamer.dll' not 'wingstreamer.dll'. Notice the 'e' in 'wine'. It may be a typo in your comment but it's better to double check that you didn't make the same typo when searching in the directories. (In reply to zeroredgrave from comment #22)
i download in mint repository and try upgrade from latest wine stable version on website
Linux Mint doesn't provide its own Wine packages. It has a wine-installer package that install an ancient version of Wine stable [1]. I can only guess that it downloads the winehq-stable packages from winehq.org. It's highly doubtful that those packages were build without gstreamer support. You may have missed dependencies when upgrading. What are the exact commands you used in the terminal to upgrade wine to the latest stable version?. Regards. [1] https://forums.linuxmint.com/viewtopic.php?t=394972 -- 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=55143 --- Comment #24 from zeroredgrave(a)gmail.com --- (In reply to Olivier F. R. Dierick from comment #23)
(In reply to zeroredgrave from comment #22)
(also, you may also need to check syswow64 dir too, not just system32 - they're actually reversed to what the number at the end suggests (unless you've explicitly created a pure 32bit prefix, but that seems unlikely))
i never created any wine prefix until now and i'm using a default wine prefix. i checked on dir and found syswow64 dir inside windows dir
Hello,
What he says is to check if winegstreamer.dll is present or not in windows/syswow64 dir, not just that the dir exists.
It is 'winegstreamer.dll' not 'wingstreamer.dll'. Notice the 'e' in 'wine'. It may be a typo in your comment but it's better to double check that you didn't make the same typo when searching in the directories.
Sorry, i got mistake that winegstreamer.dll exist on both system32 and syswow64 I Apologize for my mistaken
(In reply to zeroredgrave from comment #22)
i download in mint repository and try upgrade from latest wine stable version on website
Linux Mint doesn't provide its own Wine packages. It has a wine-installer package that install an ancient version of Wine stable [1].
I can only guess that it downloads the winehq-stable packages from winehq.org. It's highly doubtful that those packages were build without gstreamer support.
You may have missed dependencies when upgrading. What are the exact commands you used in the terminal to upgrade wine to the latest stable version?.
This is what command i follow from winehq sudo dpkg --add-architecture i386 sudo wget -nc -O /usr/share/keyrings/winehq-archive.key https://dl.winehq.org/wine-builds/winehq.key sudo wget -NP /etc/apt/sources.list.d/ https://dl.winehq.org/wine-builds/ubuntu/dists/jammy/winehq-jammy.sources sudo apt update sudo apt install --install-recommends winehq-stable <<-- Got this an error, Don't Let me install which is what i remember So, I was a looking for an answer on how to install latest wine version from foss website because mint doesn't ship a latest version of wine so i have do it by my own and i have to delete winehq.list file from /etc/apt/source.list.d. After that i decided follows foss step by step tutorial on how to install wine latest version sudo apt install software-properties-common wget curl sudo apt-get update ls /etc/apt/sources.list.d/ sudo rm /etc/apt/sources.list.d/winehq.list sudo apt install software-properties-common wget curl wget -O - https://dl.winehq.org/wine-builds/winehq.key | sudo apt-key add - sudo add-apt-repository 'deb https://dl.winehq.org/wine-builds/ubuntu/ impish main' sudo apt update sudo apt install winehq-stable After processing, i upgrade and installed with the latest version. This is what i remember last 1 or 2 years ago i think ToT -- 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=55143 --- Comment #25 from Rafał Mużyło <galtgendo(a)o2.pl> --- The question was to ensure you're not using some quirky build of wine (yours or your distro's). As you seem to claim to be using winehq package, that's not the case and my guess gets far more likely. I mean the memory numbers on the screenshot might have already suggested that, but sometimes it's hard to distinguish video card and system memory. At least doubly so in wine, where some rare cases end up consuming far more memory than they reasonably should - after all, the main part of bug 54034 is most likely such, if unrelated, case too. If you had means to log memory/VMS consumption from the start till the crash, that could help, but only slightly, because in such cases general consumption is less important than what exactly is being allocated and why (and sometimes why it's not getting released). Given the context it's most likely something on the graphical stack, but that too broad. -- 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=55143 --- Comment #26 from zeroredgrave(a)gmail.com --- All the game I tried to test and it works just fine especially on max Payne 1 and 3 only. I'm gonna try to run the game on another hardware since I'm only using discrete AMD Ryzen GPU to run the game for older titles if I have vacant time to test the game. Anyway if someone can mimic the same error that I encounter on, please let me know. Cheers! -- 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=55143 Matheus <matheus.venturini(a)acad.ufsm.br> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matheus.venturini(a)acad.ufsm | |.br --- Comment #27 from Matheus <matheus.venturini(a)acad.ufsm.br> --- I just did my annual Max Payne 1 and 2 playtrough today (and yesterday) with Wine 8.11 and had no issues, in MP2 the intro video played with no issues while in MP1 it doesn't play and skips straight to the main menu (which has always happened with Wine as far as I know). I did not compile Wine myself, I downloaded the wine-devel package as recommended in the wiki, as in comment 24. -- 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=55143 --- Comment #28 from Rafał Mużyło <galtgendo(a)o2.pl> --- (In reply to Matheus from comment #27) ...first, compare your initial console output with the one (:sigh:) on the screenshot - it might be something like using a lower resolution. Other potential option is that this is a Mesa/hardware difference - perhaps one of you is using integrated card while other is not and that either make a memory consumption different on its own or the driver does something differently resulting in the consumption difference. -- 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=55143 --- Comment #29 from Matheus <matheus.venturini(a)acad.ufsm.br> --- Created attachment 74829 --> https://bugs.winehq.org/attachment.cgi?id=74829 Console output when lauching MaxPayne2.exe with Wine 8.12 This is the console output when launching the game with 8.12. It's completely different from the one in the bug description. The only similarities are the "wbemprox" and "ddraw" warnings. I can't get this crash to happen no matter the settings I use. This might indeed be an AMD thing. I have an ol' trusty Intel HD Graphics 2000 iGPU, Intel Core i5-2320 CPU @ 3.00GHz. In case it's helpful, Max Payne 1 and 2 have demos that can be downloaded from these links: Max Payne: https://archive.org/details/MaxPayneDemo Max Payne 2: https://archive.org/details/max-payne-2-demo Max Payne 3 doesn't have a demo, but that one isn't good anyway. -- 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=55143 --- Comment #30 from Matheus <matheus.venturini(a)acad.ufsm.br> --- I forgot to mention that both games crash when exiting, thus the segmentation fault at the end of the log. This doesn't cause any real issues, however. -- 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=55143 --- Comment #31 from Rafał Mużyło <galtgendo(a)o2.pl> --- ...why does your console output fail to capture the output from the game (the engine lines) ? -- 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=55143 --- Comment #32 from Matheus <matheus.venturini(a)acad.ufsm.br> --- I'm assuming you mean the lines starting with "info" in the screenshot taken by zeroredgrave. Unfortunately I'm really not sure, these never appear when I run anything with Wine. Apparently all he did was run "wine MaxPayne2.exe" like I did, but maybe he somehow had another debug channel active which is what made it output that information? Or maybe that is a DXVK thing, since my GPU is OpenGL-only. -- 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=55143 --- Comment #33 from Rafał Mużyło <galtgendo(a)o2.pl> --- ...might be a completely different problem then.... Just to establish a thing: are you using that fixed dll wrt. mentioned Ryzen 3 problem ? -- 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=55143 --- Comment #34 from zeroredgrave(a)gmail.com --- I already fixed the issue by reinstalled my linux mint and i have no issue on winegstreamer.dll anymore because i found out that my OS inside of SSD was installed using old intel pentium 4 laptop and i tried to boot on ryzen 3 then run max payne 2. i just got an error from winegstreamer.dll. maybe there is some issue between migrating old hardware to new hardware. So i have to reinstalled and try to run again with same wine version, it is run normally now. -- 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=55143 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #35 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to zeroredgrave from comment #34)
I already fixed the issue by reinstalled my linux mint and i have no issue on winegstreamer.dll anymore because i found out that my OS inside of SSD was installed using old intel pentium 4 laptop and i tried to boot on ryzen 3 then run max payne 2. i just got an error from winegstreamer.dll. maybe there is some issue between migrating old hardware to new hardware. So i have to reinstalled and try to run again with same wine version, it is run normally now.
Hello, Thanks for the feedback. Marking invalid. 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.
https://bugs.winehq.org/show_bug.cgi?id=55143 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #36 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.
http://bugs.winehq.org/show_bug.cgi?id=55143 Bernhard Übelacker <bernhardu(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bernhardu(a)mailbox.org --- Comment #37 from Bernhard Übelacker <bernhardu(a)mailbox.org> --- Just adding this note to this bug to make it findable. I received this message with a split oldwow64 mingw64 build. Building this with just the 64-bit side having gstreamer enabled leads to a wineprefix containing also just one c:/windows/system32/winegstreamer.dll. Then even after fixing the 32-bit build to contain winegstreamer.dll this error is still given, because it seems it relies on having at least some c:/windows/syswow64/winegstreamer.dll in place. After fixing the 32-bit one way might be to run `wine wineboot --update --force` to have both files in place: c:/windows/syswow64/winegstreamer.dll c:/windows/system32/winegstreamer.dll With the fixed build and both files in place the error from commen #0 is gone for me. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=55143 osu_Vanilla(a)126.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |osu_Vanilla(a)126.com --- Comment #38 from osu_Vanilla(a)126.com --- Checking if the file winegstreamer.dll exists in your wineprefix is a good idea. In my case, NixOS's pkgs.wine / pkgs.wine64 (single-architecture wine) has but pkgs.wineWowPackages.stable / pkgs.wineWowPackages.unstable not. Switch to pkgs.wineWowPackages.stableFull / pkgs.wineWowPackages.unstableFull solves my problem. -- 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