https://bugs.winehq.org/show_bug.cgi?id=51703
Bug ID: 51703 Summary: Opening Omnisphere Authorization window with a large amount of text on the clipboard causes an unhandled page fault Product: Wine-staging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: andrew@amorgan.xyz CC: leslie_alistair@hotmail.com, z.figura12@gmail.com Distribution: ---
Created attachment 70576 --> https://bugs.winehq.org/attachment.cgi?id=70576 backtrace
I'm attempting to register my Spectatronics Omnisphere installation, which requires pasting an authorization code into the application.
However, it appears that during authorization Omnisphere will attempt to read the contents of the clipboard in order to validate the authorization code, but upon doing so with any clipboard size that is significantly large, the application will crash with a page fault.
Unfortunately, I cannot work around this issue as there is no option to type in the authorization code rather than pasting it in in full.
Running the application with a small amount of text on the clipboard works fine. I also found that simply having 500 letter 'A's on my clipboard ('AAAAA...') will also cause the application to crash, so it appears that the characters involved does not matter - only the size of the clipboard's content does.
Through trial and error I have found that a string of 110 A's is fine, but 111 A's on the clipboard will cause the application to crash.
https://bugs.winehq.org/show_bug.cgi?id=51703
--- Comment #1 from andrew@amorgan.xyz --- Created attachment 70577 --> https://bugs.winehq.org/attachment.cgi?id=70577 terminal logs
https://bugs.winehq.org/show_bug.cgi?id=51703
--- Comment #2 from andrew@amorgan.xyz --- Created attachment 70578 --> https://bugs.winehq.org/attachment.cgi?id=70578 Screenshot of the application
https://bugs.winehq.org/show_bug.cgi?id=51703
andrew@amorgan.xyz changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |6.16
https://bugs.winehq.org/show_bug.cgi?id=51703
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- Thanks for the detailed report. Does this bug appear in upstream (non-staging) wine?
https://bugs.winehq.org/show_bug.cgi?id=51703
--- Comment #4 from andrew@amorgan.xyz --- (In reply to Zebediah Figura from comment #3)
Thanks for the detailed report. Does this bug appear in upstream (non-staging) wine?
It does appear in the 'wine' package, v6.16-1, from the official Arch Linux repo: https://archlinux.org/packages/multilib/x86_64/wine/.
I can try building from a checkout of wine as well if necessary.
https://bugs.winehq.org/show_bug.cgi?id=51703
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |-unknown CC| |dark.shadow4@web.de Product|Wine-staging |Wine
--- Comment #5 from Fabian Maurer dark.shadow4@web.de ---
It does appear in the 'wine' package, v6.16-1, from the official Arch Linux repo
Moving to wine then.(In reply to andrew from comment #4)
I can try building from a checkout of wine as well if necessary.
It certainly would be useful to have debug symbols, to see where exactly it crashes. Should make fixing a lot easier, since it crashes inside wine code.
https://bugs.winehq.org/show_bug.cgi?id=51703
--- Comment #6 from andrew@amorgan.xyz --- Created attachment 70620 --> https://bugs.winehq.org/attachment.cgi?id=70620 winedbg logs
https://bugs.winehq.org/show_bug.cgi?id=51703
--- Comment #7 from andrew@amorgan.xyz --- I've read through the documentation and built wine from the `master` branch (commit 36cc3d4c9cd) with the following options:
export CFLAGS="-march=x86-64 -mtune=generic -pipe -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -Og"
../wine/configure \ --prefix='/usr' \ --libdir='/usr/lib' \ --with-x \ --with-gstreamer \ --enable-win64
make -j4
make prefix="${pkgdir}/usr" \ libdir="${pkgdir}/usr/lib32" \ dlldir="${pkgdir}/usr/lib32/wine" \ install
And have ran Omnisphere.exe through `winedbg`. This resulted in another backtrace, but with my untrained eyes does not appear to offer any more debugging information (although does no longer complain about missing symbols).
Please let me know if there is a better way to get more information out of the backtrace and I'll do my best :)
https://bugs.winehq.org/show_bug.cgi?id=51703
--- Comment #8 from Fabian Maurer dark.shadow4@web.de --- Is there a way to download the program without buying it? Then we would be able to test it, I mean, you don't need a valid code for the crash, right?
https://bugs.winehq.org/show_bug.cgi?id=51703
--- Comment #9 from andrew@amorgan.xyz --- Created attachment 70621 --> https://bugs.winehq.org/attachment.cgi?id=70621 Omnisphere player/activator executable
you don't need a valid code for the crash, right?
You do not. Simply copy/paste the following string into your clipboard, run the executable and click "Paste":
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
You should see the page fault occur.
Omnisphere is music software and the bulk of the copyrighted work are the instrument samples it includes. Throwing the activator binary up is probably fine.
https://bugs.winehq.org/show_bug.cgi?id=51703
--- Comment #10 from Alexandre Julliard julliard@winehq.org --- The content of attachment 70621 has been deleted for the following reason:
Please don't attach copyrighted binaries
https://bugs.winehq.org/show_bug.cgi?id=51703
--- Comment #11 from andrew@amorgan.xyz --- Apologies! If someone can direct me on how to get a useful backtrace on my system I'd be happy to do so.
https://bugs.winehq.org/show_bug.cgi?id=51703
Eduardo eduardo.cruz@kdemail.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |eduardo.cruz@kdemail.net
--- Comment #12 from Eduardo eduardo.cruz@kdemail.net --- I’m affected too. Can I help provide any additional information?