[Bug 49125] New: Logos Bible Software Indexing fails 64bit only 32bit works
https://bugs.winehq.org/show_bug.cgi?id=49125 Bug ID: 49125 Summary: Logos Bible Software Indexing fails 64bit only 32bit works Product: Wine Version: 5.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: johnpgoodman(a)gmail.com Distribution: --- Created attachment 67120 --> https://bugs.winehq.org/attachment.cgi?id=67120 Shows the indexer appears to have hung. Indexing in Logos Bible Software seems to hang for many users in 64bit. Since bug 47668 was fixed 32bit works. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 --- Comment #1 from m0rvj <johnpgoodman(a)gmail.com> --- Created attachment 67121 --> https://bugs.winehq.org/attachment.cgi?id=67121 console output Console output with indexing hung. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 Nick <nick.andrewes(a)phonecoop.coop> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nick.andrewes(a)phonecoop.coo | |p --- Comment #2 from Nick <nick.andrewes(a)phonecoop.coop> --- Created attachment 67169 --> https://bugs.winehq.org/attachment.cgi?id=67169 BUG CONFIRMED: OR IS IT?: unfolding story . . . Episode 1 This is terminal output form a Logos installation attempt. Debian Bullseye. How I got here: $ apt-cache policy winehq-devel winehq-devel: Installed: 5.8~bullseye Candidate: 5.8~bullseye Version table: *** 5.8~bullseye 500 500 http://dl.winehq.org/wine-builds/debian bullseye/main amd64 $ WINEPREFIX=/home/nick/wine-development-5.8-64bit-win10/ WINEARCH=win64 wineboot (clean prefix) $ WINEPREFIX=$HOME/wine-development-5.8-64bit-win10/ winetricks -q win10 dotnet48 corefonts fontsmooth=rgb ddr=gdi $ cp -R wine-development-5.8-64bit-win10/ wine-logos-development-5.8-64bit-win10 $ WINEPREFIX=~/wine-logos-development-5.8-64bit-win10/ winecfg ~/wine-logos-development-5.8-64bit-win10/ (this was used to set the windows version in wine back to win10 - it has shifted to win7) $ WINEPREFIX=$HOME/wine-logos-development-5.8-64bit-win10/ msiexec /i ~/Downloads/Logos-x64.msi WINEPREFIX=$HOME/wine-logos-development-5.8-64bit-win10/ wine64 ~/wine-logos-development-5.8-64bit-win10/drive_c/users/nick/Local\ Settings/Application\ Data/Logos/Logos.exe (this last was repeated after crashes) EPISODE 1: =========== All good so far. Resources downloaded. I'm still on 1% indexing. LogosIndexer process at 2.1Gb memory and slowly trending upwards (three steps up, two steps down). And here is the terminal log. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 --- Comment #3 from Nick <nick.andrewes(a)phonecoop.coop> --- Created attachment 67170 --> https://bugs.winehq.org/attachment.cgi?id=67170 EPISODE 2 Now it's crashed. But I did take the risk (after a while) of opening up Logos and messing around in it. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 --- Comment #4 from Nick <nick.andrewes(a)phonecoop.coop> --- Created attachment 67171 --> https://bugs.winehq.org/attachment.cgi?id=67171 EPISODE 2: Log file -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 --- Comment #5 from Nick <nick.andrewes(a)phonecoop.coop> --- Created attachment 67172 --> https://bugs.winehq.org/attachment.cgi?id=67172 EPISODE 3: Logos dies again -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 --- Comment #6 from Nick <nick.andrewes(a)phonecoop.coop> --- Created attachment 67173 --> https://bugs.winehq.org/attachment.cgi?id=67173 EPISODE 3: Backtrace -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 --- Comment #7 from Nick <nick.andrewes(a)phonecoop.coop> --- Created attachment 67174 --> https://bugs.winehq.org/attachment.cgi?id=67174 EPISODE 4: The morning after - Success? This time I ran it with the following command from my menu: env WINEPREFIX="/home/nick/wine-logos-development-5.8-64bit-win10" wine C:\\windows\\command\\start.exe /Unix /home/nick/wine-logos-development-5.8-64bit-win10/dosdevices/c:/users/nick/Start\ Menu/Programs/Logos\ Bible\ Software.lnk The terminal didn't seem to fire as it should. So I have no output. It appears to have successfully completed indexing, after taking 3 hours to get to 7% and then jumping to complete. I'm not sure how to confirm this. Initial perceptions are that Logos works without crashing. And winecfg shows that it is running in win10. It seems to me that crashes were experienced, but it did complete indexing. I will keep you updated. . . -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 --- Comment #8 from Nick <nick.andrewes(a)phonecoop.coop> --- Created attachment 67175 --> https://bugs.winehq.org/attachment.cgi?id=67175 EPISODE 5: Indexing from 0% (still 0% after 20 mins) This sample terminal output is attached. I restarted Logos. It started indexing. And is still 0% after 20 minutes. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 --- Comment #9 from Nick <nick.andrewes(a)phonecoop.coop> --- Created attachment 67181 --> https://bugs.winehq.org/attachment.cgi?id=67181 EPISODE 6: Crashing still - backtrace A few reboots and re-opens, and indexing progressing very slowly. It's crashed at 34% complete. Backtrace attached. NB This is with Logos 8.8.0.0046. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 --- Comment #10 from Nick <nick.andrewes(a)phonecoop.coop> --- Created attachment 67182 --> https://bugs.winehq.org/attachment.cgi?id=67182 EPISODE 6: Crashing still - terminal log Is this a potentially interesting line? 032c:fixme:advapi:RegisterEventSourceW ((null),L".NET Runtime"): stub 032c:fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000402,(nil),0x0001,0x00000000,0x2b74b960,(nil)): stub 032c:err:eventlog:ReportEventW L"Application: LogosIndexer.exe\nFramework Version: v4.0.30319\nDescription: The process was terminated due to an unhandled exception.\nException Info: System.AccessViolationException\n at System.String.InternalSplitKeepEmptyEntries(Int32[], Int32[], Int32, Int32)\n at System.String.Spl"... 032c:fixme:advapi:DeregisterEventSource (0xcafe4242) stub wine: Unhandled page fault on read access to 00007E0855936090 at address 0000064478578DCD (thread 032c), starting debugger... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 --- Comment #11 from Nick <nick.andrewes(a)phonecoop.coop> --- Created attachment 67200 --> https://bugs.winehq.org/attachment.cgi?id=67200 EPISODE 7: Now crashing without appearing to index - terminal output Sadly, I forgot to get the backtrace. This is the last report in the current sequence. Over the last few days, Logos had appeared to run OK (I hadn't used it much while it was open) but it still struggled with indexing. On one occasion getting to 34% and on another 10% without progressing further and without crashing. Today it crashed fairly soon after start up. My next task is to re-install in a clean bottle, but I've got access to a later version of the .msi file, and I'll test that to see what happens, with the same process as described here. For reference, the results above are with 8.8.0.0046. I don't recall any prompts to update beyond this version. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 --- Comment #12 from Nick <nick.andrewes(a)phonecoop.coop> --- Created attachment 67202 --> https://bugs.winehq.org/attachment.cgi?id=67202 Take 2: Episode 1 - terminal output. OK. I'm running as before: Debian Bullseye 64bit win10 setup in Wine Development 4.8 dotnet48 Logos installer version: 8.10.0.0032 Installation has gone through apparently successfully. I used the verifier on the dotnet48 which seemed to be fine. At this point, "preparing your library" has completed, and indexing has got to 1% Waiting to see what happens next. There's no apparent problem at this stage. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 --- Comment #13 from Nick <nick.andrewes(a)phonecoop.coop> --- Created attachment 67205 --> https://bugs.winehq.org/attachment.cgi?id=67205 Take 2: Episode 2 - Frozen. terminal output I've currently got to 31% indexing, and nothing has officially crashed. However, the indexing process appears to have frozen at 1,023,828 Kb RAM usage according to the Process viewer. This figure is not changing, and CPU percentage is zero. So either: (a) it's finished indexing, but reporting incorrectly - in which case, then, why has it stopped with 1Gb ram usage? or (b) it's stopped working (perhaps more likely). Logos is recorded as 1% - 4% CPU (fluctuating very little) and just under 1Gb RAM usage (again fluctuating very little). I've not entered Logos yet. I note that these lines may be significant - at least both sets contain the word "error", and appear to be the same error: 0548:fixme:process:NtFlushProcessWriteBuffers stub 0034:fixme:advapi:RegisterEventSourceW ((null),L".NET Runtime Optimization Service"): stub 0034:fixme:advapi:DeregisterEventSource (0xcafe4242) stub 0548:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFA, 0031FEB4 0548:fixme:ntdll:EtwEventUnregister (deadbeef) stub. 0548:fixme:ntdll:EtwEventUnregister (deadbeef) stub. 0034:err:ole:ifproxy_release_public_refs IRemUnknown_RemRelease failed with error 0x800706be 0524:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION and: 03f0:fixme:ole:NdrClearOutParameters (017AEE9C,017E2B5A,017AF5E8): stub 03f0:err:ole:ifproxy_release_public_refs IRemUnknown_RemRelease failed with error 0x800706ba 03f0:err:ole:ifproxy_release_public_refs IRemUnknown_RemRelease failed with error 0x800706ba 01f8:fixme:advapi:RegisterEventSourceW ((null),L".NET Runtime Optimization Service"): stub 01f8:fixme:advapi:DeregisterEventSource (0xcafe4242) stub -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 --- Comment #14 from Nick <nick.andrewes(a)phonecoop.coop> --- Created attachment 67206 --> https://bugs.winehq.org/attachment.cgi?id=67206 Take 2: Episode 3 - further output with errors I've gone into Logos, which hasn't crashed, but I've got some more output and some more errors. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 --- Comment #15 from Nick <nick.andrewes(a)phonecoop.coop> --- It's appearing to me that this is resolved, at least for me, for me in wine-staging 5.11 (and also seemed to have been resolved wine-staging 5.10) The process of downloading, preparing, indexing, and updating all goes smoothly EXCEPT: + there is a point in initial indexing when CPU is at 0% for LogosIndexer.ex and it seems to get stuck. If I close the Logos application, it hangs on reentry. If I reboot the system (probably = killing the process and restarting Logos), then it does complete indexing, downloads 3.5Gb of updates, and updates the app from 4.10.?? to 4.14.0.0010 Thereafter fast, presumably incremental, indexing. Thanks to someone for significantly moving this one forward - at least on my PC: Debian Bullseye, win10, 64bit, dotnet48. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 --- Comment #16 from Nick <nick.andrewes(a)phonecoop.coop> --- Actually, I'm not sure whether I'm misinterpreting the OP: In Win64, it appears not to work, but DOES work for me. This is probably what the OP meant, in which case, it still appears not to work, although it does, and the bug is not resolved, but confirmed. For me, just completing the indexing and updating on win64 and win10 is a first, hence my excitement! -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 --- Comment #17 from m0rvj <johnpgoodman(a)gmail.com> --- Thanks Nick, Indexing is the focus. It is unclear whether indexing is completing at all in 64bit. As you mention in comment 15 the indexing crashes. I think the Bug should be confirmed. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 --- Comment #18 from m0rvj <johnpgoodman(a)gmail.com> --- Ok so bit of good news: I just installed using option 5 of Daniel's script (https://github.com/ferion11/LogosLinuxInstaller). That is Logos 64bit using wine v5.11 appimage to install dotnet48 and then winehq packages of wine 5.16 to run Logos 8.15.0.0004. I had to terminate a lot of left over processes after the install before launching Logos but it downloaded and indexed in just over an hour. A small test library made up entirely of freebies (93 resources). That's the best result I've ever had with 64bit! -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 --- Comment #19 from m0rvj <johnpgoodman(a)gmail.com> --- Created attachment 68077 --> https://bugs.winehq.org/attachment.cgi?id=68077 Successful Indexing Log This log was generated by a successful index done on wine 5.16 with Logos 8.16.0.0002 uid and username redacted. The bug can be closed. I'm not sure which patch ultimately fixed it but it works. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 m0rvj <johnpgoodman(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #20 from m0rvj <johnpgoodman(a)gmail.com> --- Asking a developer to close the bug please. Thanks so much! -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #21 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 5.17. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49125 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |dotnet, download CC| |focht(a)gmx.net Summary|Logos Bible Software |Logos 8 Bible Software |Indexing fails 64bit only |(.NET 4.7 app): Indexing |32bit works |fails 64bit only 32bit | |works URL| |https://web.archive.org/web | |/20210209172851/https://dow | |nloads.logoscdn.com/LBS8/In | |staller/8.7.0.0039/Logos-x8 | |6.msi -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla