https://bugs.winehq.org/show_bug.cgi?id=44470
Bug ID: 44470 Summary: libmpg123.so.0: cannot open shared object file Product: Wine Version: 3.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: loader Assignee: wine-bugs@winehq.org Reporter: bghome@gmail.com Distribution: ---
Created attachment 60411 --> https://bugs.winehq.org/attachment.cgi?id=60411 Console output of winecfg
When I run winecfg, it get an error saying that libmpg123.so.0 cannot be loaded (see attached log for the full message). Fortunately winecfg works well despite of this error.
I have checked the file exists and readable by users: $ file /usr/lib/libmpg123.so.0 /usr/lib/libmpg123.so.0: symbolic link to libmpg123.so.0.44.7
$ file /usr/lib/libmpg123.so.0.44.7 /usr/lib/libmpg123.so.0.44.7: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=037a06d675c5ddd57e1e9872ab589c8be6b00d15, stripped
$ ls -l /usr/lib/libmpg123.so.0.44.7 -rwxr-xr-x 1 root root 322624 Dec 25 10:54 /usr/lib/libmpg123.so.0.44.7
What could be the problem then?
https://bugs.winehq.org/show_bug.cgi?id=44470
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|loader |-unknown
https://bugs.winehq.org/show_bug.cgi?id=44470
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #1 from Fabian Maurer dark.shadow4@web.de --- Does that also happen in a clean WINEPREFIX? Because winecfg shouldn't even use that. Also, did you install both 32 and 64bit versions of the library?
https://bugs.winehq.org/show_bug.cgi?id=44470
--- Comment #2 from Géza Búza bghome@gmail.com --- (In reply to Fabian Maurer from comment #1)
Does that also happen in a clean WINEPREFIX? Because winecfg shouldn't even use that.
That does not make a difference.
Also, did you install both 32 and 64bit versions of the library?
Well, no only the 64-bit version is present. Installing lib32-mpg123 makes the error go away. However when I run winecfg by defining the architecture to 64 bit, like WINEARCH=win64 WINEPREFIX=~/.wine winecfg, and I expected it to use only 64-bit binaries in this case.
https://bugs.winehq.org/show_bug.cgi?id=44470
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #3 from Fabian Maurer dark.shadow4@web.de ---
Does that also happen in a clean WINEPREFIX? Because winecfg shouldn't even use that.
That does not make a difference.
That's odd, then I don't know what's going on here.
However when I run winecfg by defining the architecture to 64 bit, like WINEARCH=win64 WINEPREFIX=~/.wine winecfg, and I expected it to use only 64-bit binaries in this case.
You need to keep in mind that it's not a pure 64bit installation, it's a wow64 installation, with 32bit support.
Anyways, since this is not a wine bug, I'm closing it.
https://bugs.winehq.org/show_bug.cgi?id=44470
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #4 from Zebediah Figura z.figura12@gmail.com --- (In reply to Fabian Maurer from comment #3)
That's odd, then I don't know what's going on here.
winecfg depends on winmm (for the audio devices tab) which depends on msacm32, which loads the ACM drivers during DllMain().
However when I run winecfg by defining the architecture to 64 bit, like WINEARCH=win64 WINEPREFIX=~/.wine winecfg, and I expected it to use only 64-bit binaries in this case.
You need to keep in mind that it's not a pure 64bit installation, it's a wow64 installation, with 32bit support.
Anyways, since this is not a wine bug, I'm closing it.
To be more specific, any builtin application will start in 32-bit mode unless explicitly started with `wine64`. winecfg (as well as regedit) will always restart themselves in 64-bit mode if this happens, but the dependency is at load-time so the error will still occur.
It is, though, as was said, harmless, since it's a dynamic dependency.
https://bugs.winehq.org/show_bug.cgi?id=44470
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv@dawncrow.de Status|RESOLVED |CLOSED
--- Comment #5 from André H. nerv@dawncrow.de --- closing invalid
-
wine-bugs＠winehq.org