https://bugs.winehq.org/show_bug.cgi?id=45010
Bug ID: 45010 Summary: Libs are right after Wine start on all Androidx86 machines Product: Wine Version: 3.6 Hardware: x86 OS: Android Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: ruthan@email.cz
Created attachment 61134 --> https://bugs.winehq.org/attachment.cgi?id=61134 Error message
There is some libs error on all Androidx86 machines which i tested, right after Wine start.. Look at picture.
https://bugs.winehq.org/show_bug.cgi?id=45010
--- Comment #1 from Alexandre Julliard julliard@winehq.org --- Is that a custom Wine package? These libraries are not included in the standard WineHQ package.
https://bugs.winehq.org/show_bug.cgi?id=45010
--- Comment #2 from RuThaN ruthan@email.cz --- No vanilla x86 Android release right from your web.
https://bugs.winehq.org/show_bug.cgi?id=45010
RuThaN ruthan@email.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Libs are right after Wine |Libs error are right after |start on all Androidx86 |Wine start on all |machines |Androidx86 machines
https://bugs.winehq.org/show_bug.cgi?id=45010
--- Comment #3 from Alexandre Julliard julliard@winehq.org --- Then it's the libraries included with your Android system that are broken. What's your exact Android OS version?
https://bugs.winehq.org/show_bug.cgi?id=45010
--- Comment #4 from RuThaN ruthan@email.cz --- Vanilla Androidx86 -64bit: http://www.android-x86.org/releases/releasenote-7-1-r1
Machine is Asus Q170T+ Intel Core i5 6500T => Intel HD530 GPU - its usign kernel 4.9 + Mesa.
https://bugs.winehq.org/show_bug.cgi?id=45010
--- Comment #5 from RuThaN ruthan@email.cz --- Its small pc desktop, it has enough horse power for Wine gaming and no ARM to x86 translation is needed for it would be ideal for Wine gaming, if would Wine run smoothly. Im using it also on my convertible Toshiba Z20, same errors.
https://bugs.winehq.org/show_bug.cgi?id=45010
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTOURBUG Status|UNCONFIRMED |RESOLVED
--- Comment #6 from Alexandre Julliard julliard@winehq.org --- You should probably file a bug with android-x86 then.
https://bugs.winehq.org/show_bug.cgi?id=45010
--- Comment #7 from RuThaN ruthan@email.cz --- Ok could you provide some more detail description where is error on Androidx86 side and path to log mentioned in error message?
https://bugs.winehq.org/show_bug.cgi?id=45010
--- Comment #8 from Alexandre Julliard julliard@winehq.org --- The ffmpeg libraries contain text relocations, IIRC their assembly code needs to be patched or disabled at build time. The log mentioned is probably what you get with 'adb logcat'.
https://bugs.winehq.org/show_bug.cgi?id=45010
Jactry Zeng jactry92@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jactry92@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=45010
--- Comment #9 from RuThaN ruthan@email.cz --- Ok here is some comment from Android x86 developers:
It's not really a bug, as the popup dialog has been intentionally added by Google engineers. The question is why does Wine try to load the 32-bits ffmpeg libraries from the OS (64bit), which is what triggers the popup dialog. Why it does that is something only the Wine people can answer.
https://bugs.winehq.org/show_bug.cgi?id=45010
RuThaN ruthan@email.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|NOTOURBUG |INVALID
https://bugs.winehq.org/show_bug.cgi?id=45010
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |NOTOURBUG
--- Comment #10 from Alexandre Julliard julliard@winehq.org --- If they are saying that we shouldn't be using 32-bit libraries at all, that's not feasible. Wine needs to be a 32-bit app in order to run 32-bit Windows binaries.
If they are saying that we shouldn't be loading these specific libraries, we are not doing that. There's no reference to any of these libraries in Wine. They are being loaded by some other system library that we don't control.
https://bugs.winehq.org/show_bug.cgi?id=45010
Chih-Wei Huang cwhuang@linux.org.tw changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cwhuang@linux.org.tw
--- Comment #11 from Chih-Wei Huang cwhuang@linux.org.tw --- I'm the founder of Android-x86 project. First of all, I have to clarify I didn't see anybody said like RuThaN quoted in comment 9. I'm not sure why or where he quoted that.
You can check the whole thread about the discussion: https://groups.google.com/forum/#!topic/android-x86/LaBqoKr6y14
As I explained in that thread, FFmpeg libraries need text relocations: https://trac.ffmpeg.org/ticket/4928
The only question I have is: "What does Wine have to do with FFmpeg's text relocations?" or equivalently "Why FFmpeg's text relocations is a problem to Wine?"
https://bugs.winehq.org/show_bug.cgi?id=45010
--- Comment #12 from Alexandre Julliard julliard@winehq.org --- (In reply to Chih-Wei Huang from comment #11)
The only question I have is: "What does Wine have to do with FFmpeg's text relocations?" or equivalently "Why FFmpeg's text relocations is a problem to Wine?"
Wine doesn't load or use FFmeg, and doesn't care about its text relocations. There's some system library loading ffmpeg, and some other system library (probably the linker) popping up a message about it.
https://bugs.winehq.org/show_bug.cgi?id=45010
--- Comment #13 from Chih-Wei Huang cwhuang@linux.org.tw --- OK. Thank you for the clarification. Since you said "your Android system are broken". I misunderstood you meant it's a problem to Wine. If not, then we agree there is no bug. Right?
https://bugs.winehq.org/show_bug.cgi?id=45010
--- Comment #14 from Alexandre Julliard julliard@winehq.org --- As far as I can see, the only bug is that the system is popping up an error message. If the text relocations can't be avoided, android-x86 would need to be patched to get rid of that error.
If the libraries fail to load, this may cause other bugs, but so far there doesn't seem to be evidence of that.
https://bugs.winehq.org/show_bug.cgi?id=45010
--- Comment #15 from RuThaN ruthan@email.cz --- Some clarifications:
Comment #9: I received this info by PM on Androidx86 Google Group from Michael Goffioul, i asked developers to respond to Wine bug tracker.. but nobody did (now im glad that Chhih did), some i posted what i received by PM. Its still better nothing. Its open source project so i dont know details about Michaels role in team.
Problem severity: My general guest was that startup error is not good at all, so i reported it.. I dont have any ARM device with bigger screen, keyboard and mouse to test Wine ARM build, so i dont know what is difference between ARM and x86 Wine build.
There is nothing like Android specific Wine changelog (original changelog is usless for Android where basic features not working..), so i through bad shape of Wine of x86 device is some specific Android x86 bug.. but its probably whole Wine problem :(
I have tried lots of games, but DirectX 2D games are not working at all, Dxdiag is not working, OpenGl is not working, Direct3D is not working, even Total Commander graphics is broken. Physical mouse behavior is half broken, Xbox 360 controller is not recognized by Wine, Wine desktop resolution is too small - so windows are bigger than screen.
I only managed old not DirectX 2D renderer games to get working - Quake I and Hexen II, Unreal Tournament 99 - it software mode, Deus Ex in software mode - but even these are crippled by - impossiblity to play in full screen and not working mouse look.
Pleas consider Android specific release notes, because standard multiplaform are really misleading for Android..
https://bugs.winehq.org/show_bug.cgi?id=45010
RuThaN ruthan@email.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|3.6 |3.8
https://bugs.winehq.org/show_bug.cgi?id=45010
--- Comment #16 from Chih-Wei Huang cwhuang@linux.org.tw --- (In reply to Alexandre Julliard from comment #14)
As far as I can see, the only bug is that the system is popping up an error message. If the text relocations can't be avoided, android-x86 would need to be patched to get rid of that error.
Agree. We could disable that annoying warning.
https://bugs.winehq.org/show_bug.cgi?id=45010
--- Comment #17 from RuThaN ruthan@email.cz --- Retested with Android x86 8.1-rc1 and Wine 3.11 dialog is gone, but still almost nothing is working in Wine on Android x86..
https://bugs.winehq.org/show_bug.cgi?id=45010
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #18 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=45010
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED
--- Comment #19 from Austin English austinenglish@gmail.com --- This was inadvertently caught up in my unclosed bugs filter. NOTOURBUG should only be closed when fixed upstream.
Setting back to RESOLVED NOTOURBUG.
Sorry for the spam.
-
wine-bugs＠winehq.org