[resolved] 6.0a: BUG: PBB error when rebuilding
Comments
-
this workaround is unlikely to help Mac
You said unlikely; I just confirmed that it would not work [:D]
Really cannot understand why you cannot reproduce it as it has been a bug since at least L5 for me—and others.
0 -
I can confirm that none of the suggested fixes work for me, running on a Mac. Sorry, I posted details in the original thread, thinking this was a PBB Sync discussion, with which I have no familiarity.
Can only do one Personal Books compile without a Logos restart
0 -
When you get the "Could not remove existing resource" error, trying opening a new resource from the Library (that's not already open). Then click Finished then Build Book again; does that avoid the error?
Yes, for me that does seem to allow me to build the book again without errors. Just that one time, though. If I tried to build it yet again right away, it fails. But if I open another new resource, then I can go back and build that PB successfully. Weird.
So at least you've found a workaround for Windows, and hopefully this might give you a clue as to how to fix it so we don't have to do the workaround. But I see from the others that it doesn't fix it for Mac.
0 -
0
-
More information from a Mac user.
After the first PB compile, I cannot recompile that, or any other PB in my library. However, I can add a new PB and compile it successfully. I just did about four new PBs in a row. This is true even if there is an unsuccessful recompile of an existing PB in the sequence. (I tried that just to eliminate a variable.)
0 -
Rosie Perera said:
When you get the "Could not remove existing resource" error, trying opening a new resource from the Library (that's not already open). Then click Finished then Build Book again; does that avoid the error?
Yes, for me that does seem to allow me to build the book again without errors. Just that one time, though. If I tried to build it yet again right away, it fails. But if I open another new resource, then I can go back and build that PB successfully. Weird.
So at least you've found a workaround for Windows, and hopefully this might give you a clue as to how to fix it so we don't have to do the workaround. But I see from the others that it doesn't fix it for Mac.
Rosie, I mentioned in the bug aggregate thread that I was able to reproduce the issue with your provided document. We have active cases for a few different issues pertaining to recompiling personal books, and there are developers actively looking into it. I don't know how far they are from completely fixing the issue, but I will say that progress was made as recently as Monday.
Just wanted to reply here as well.
0 -
Dylan Rondeau said:
Rosie, I mentioned in the bug aggregate thread that I was able to reproduce the issue with your provided document. We have active cases for a few different issues pertaining to recompiling personal books, and there are developers actively looking into it. I don't know how far they are from completely fixing the issue, but I will say that progress was made as recently as Monday.
Great. Thanks! It will be good to finally get this taken care of. I'm not sure why it's been so hard to reproduce, but glad my document helped.
0 -
Rosie Perera said:Dylan Rondeau said:
Rosie, I mentioned in the bug aggregate thread that I was able to reproduce the issue with your provided document. We have active cases for a few different issues pertaining to recompiling personal books, and there are developers actively looking into it. I don't know how far they are from completely fixing the issue, but I will say that progress was made as recently as Monday.
Great. Thanks! It will be good to finally get this taken care of. I'm not sure why it's been so hard to reproduce, but glad my document helped.
This should be fixed in 6.1 Beta 1. [:D]
0 -
0
-
0
-
Rosie Perera said:
Bummer! This is broken again in 6.2 Beta 2:
PBB Log file:
7446.PBB_61d6de97b89a407e838a7dc386135f13_2015-03-13T10_41_29Z.log
Logos Log file (note that I uploaded this before quitting Logos so it's not a complete session; and there's a ton of other stuff in there above the key point where the error occurred; I rebuilt one more time after the error and it succeeded that time):
0 -
Hi Rosie,
I'm sorry you had trouble rebuilding your personal book. I'm even more sorry that I haven't been able to reproduce the error on my machine. In my experience, this bug is usually caused when some other part of the application has the personal book open in some way and does not "play nice" and release it when asked. Between when you built the book the first time, and rebuilt it the time it failed, did you do any work with it within Logos? Did you have any other panels, menus or searches open or active at that time?
I'm struck that you were able to rebuild it successfully after the initial failure. That might mean that whatever was holding on to the book did release it, just a little too slowly for the personal book builder. I'd love to hunt this one down for you! If it's not too much trouble for you to talk me through the steps needed to trigger it again and send me a full screenshot of the app, not just the small portion above, that would be tremendously helpful.
Thank you very much!
Matthew
0 -
Rosie Perera said:
I rebuilt one more time after the error and it succeeded that time
That's a great improvement. In "former times" the error always needed a restart of Logos.
Have joy in the Lord!
0 -
Hi Matthew,
Here's a full screenshot, though it might not be exactly what my layout looked like when this problem came up last night, however it's pretty close, since I haven't been using Logos at all today.
Alas, I don't have time to see if I can reproduce this now. But what I had done at the time was have Word open with the .docx file. I made a change in the .docx file and then switched back to Logos and rebuilt the book. Then I switched back to Word and made another change in the .docx file and then switched back to Logos and rebuilt the book again. The second rebuild caused the failure. I don't recall doing anything else in Logos other than looking at the PB to see if the change I'd done made any difference. I might have opened the PBB log file (in Notepad) to look at the warnings, and I might have left it open. But leaving it open other times has not seemed to cause this bug to appear so I doubt that was the culprit.
0 -
NB.Mick said:Rosie Perera said:
I rebuilt one more time after the error and it succeeded that time
That's a great improvement. In "former times" the error always needed a restart of Logos.
Still requires a restart in the Mac version [:'(]
0 -
I can reproduce this every time, in the following way:
Download the files for the Biblical Illustrator series that has been posted in the Files forum, and build them as Personal Books.
Once they are all built, what I did this morning on Verbum 6.2 beta 2 was just start going down the list, click Edit then Build, you will get, depending on the speed of your computer, about 10-12 or so queued up to build, and all will be well. A soon as the first one completes, and displays, then the error wil result, and it will continue with every PB you attempt to build. You have to close the panels (on Windows) to get the error one(s) to build.
0 -
0
-
Rosie, Jack
Is this (perennial) finally fixed?
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Rosie, Jack
Is this (perennial) finally fixed?
Successfully rebuilt a PB twice—once while it was closed and even while it was open. Guess we can call it fixed.
BTW: Dave, thanks for calling these old bug reports to our attention.
0 -
Dave Hooton said:
Rosie, Jack
Is this (perennial) finally fixed?
Yes, it appears to be fixed on my one simple trial just now. I haven't been building PBBs lately, though, so if there's an intermittent problem still there I wouldn't likely encounter it for a while.
0
