http://bugs.winehq.org/show_bug.cgi?id=33068
jackdachef@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jackdachef@gmail.com
--- Comment #5 from jackdachef@gmail.com 2013-07-16 13:39:08 CDT --- (In reply to comment #4)
I was able to reproduce this a few times by following the recipe in http://bugs.winehq.org/show_bug.cgi?id=30360#c23 (using the Sticky Note tool once and then saving seemed to be enough the first two times I ran it), but it wasn't reproducible enough to do a regression test.
Can someone give a foolproof recipe to reproduce the crash, ideally that doesn't involve reinstalling the app on each iteration?
Tested version 2.5 build 204, 2ba1dfa50890c10d7ea9009cd95ed84a22f9eb61 PDFXVwer.exe
yes,
something along the lines of [1st part is identical to the instruction posted]:
*) compiling wine 1.3.28 with gcc 4.7.2 (if that works)
*) export WINEPREFIX=/home/user/wine_pdfxchange32bit
*) export WINEARCH="win32"
*) install PDF-XChange (e.g. version 2.5.210) from PDFXVwer.exe
let it launch after the installation process
*) do some annotations via the "Comment and Markup Toolbar" on an opened PDF file (not a [PROTECTED] one)
*) attempt to save the modified PDF
[testing part]:
*) backup that folder (for further tests & regression testing) - and test whether annotations with that 32bit installation works - if yes, proceed
since wine itself (not sure if I understood it correctly) updates the wine bottle/prefix once newer versions are launched
only 2 variables need to be changed:
*) the new wine version that needs to be tested - e.g. wine 1.6 rc5-wip
*) copying over the backed up ("clean", master) version of /home/user/wine_pdfxchange32bit which then gets updated with the to-be-tested version of wine
*) launch wine with the prefix and do annotations, afterwards attempting to save those without having the app crash