https://bugs.winehq.org/show_bug.cgi?id=53160
Bug ID: 53160 Summary: Ancestral Quest 16.0.11: Data from linked FamilySearch shrinks and then disappears Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs@winehq.org Reporter: drjk011@live.com Distribution: ---
Ancestral Quest is software designed for storing and managing personal family history data. When a person is linked to FamilySearch (free account) and 'Review with FamilySearch" is selected, data from FamilySearch is retrieved and the textbox is supposed to be populated so local data can be compared with FamilySearch data.
The data momentarily is presented, then shrinks smaller and smaller until it disappears from view. With text data, there are no error messages, just disappearing text.
If Ancestral Quest is a registered version, then photos may be compared with FamilySearch as well. In this case, the same action occurs until the there is a divide-by-zero error and the program crashes.
Hardware: PclinuxOS 2022 KDE Plasma 5.24.5 Ryzen 5-3600, 23.5 GiB Ram, NVIDIA GTX 1060 Wine 7.6
Software: Ancestral Quest 16.0.11 by Incline Software http://www.ancestralquestonline.com/updates/getlatest.asp?demo=1 Error demonstrated with the “Scrapbook Sample Database” freely downloadable from the publisher http://www.ancquest.com/download.htm
Connecting to FamilySearch by the Church of Jesus Christ of Latter Day Saints. One must be registered, but it is a free account. https://www.familysearch.org/en/
Attachments: Four (4) screenshots from Windows of how it is supposed to look: Screenshot_main.png; Screenshot_sub-details.png; Screenshot_sources.png; and Screenshot_sub-photos.png
Two (2) mpg files showing what is actually seen: "RealTime.mpg" shows accessing the above mentioned 4 areas, and "Clips slowed 90%.mpg" showing what is happening slow enough to actually evaluate.
One (1) backtrace file "backtrace.txt" showing information when the photos cause the program failure.
Comment:
From my working with this issue and attempting to find a resolution, to me it
seems that this is not exactly a failure of Wine, but rather a procedure or function dealing with size and placement (located in User32.dll) that is not yet fully implemented. I could not find any patches or work that addresses this issue. One backtrace (that I cannot yet duplicate) referenced a WINPOS_SysCommandSizeMove procedure followed by a WINPROC_call_window procedure; indicating that there were missing parameters.
I would be happy to provide more details and/or logs if that would be helpful. Thanks...