BUG:Crash adding new note in Logos Beta 1 and Verbum Beta 1 (38.0.502)
I've move the post https://community.logos.com/forums/p/226937/1326206.aspx#1326206 here.
I'm pretty confident this started since the last update. I'm on Windows 11 which also went through an update a couple days ago.
It doesn't matter if I select a verse or partial text to attach the note, or if I choose Add a Note from the pop up window or choose New Note from an existing open note.
Once I click add, a new note begins to open along with the notification circle that continuously chases itself around the dial for a couple seconds...then crash. The program shuts down completely.
Normally the added note would open with my last used icon also, but this tries to open with a purple check mark, which I don't use. Don't know if that means anything, but thought I'd throw it in there.
Has anyone else experienced this on Windows?
I'm hoping to get this resolved before Tuesday nights Bible study. Any help is appreciated.
I've added an error file via the paperclip, not sure if I did it right or if it's readable.
I tried rebooting but that did not help.
I called tech support. Their response was because it is on Beta they cannot help me.
Comments
-
Sorry to hear you are having problems
I've added an error file via the paperclip, not sure if I did it right or if it's readable.
I'm afraid that isn't the file we need.
Please ensure diagnostic logging is enabled and post logs in a reply to this thread after Logos has crashed and before restarting
0 -
oops!
0 -
Hope this works. Thanks for the instructions Graham.
0 -
Hope this works.
It looks like you restarted Logos before capturing the logs (as the crash happened before Logos is shown as starting in Logos.log Could you try again but take the logs before restarting.
The crash file does have:
Error ID: 9717
Error detail: ServiceException: 'style' is invalid: 'highlight' of 'custom' requires 'markupStyle' to be set.ServiceException: 'style' is invalid: 'highlight' of 'custom' requires 'markupStyle' to be set. (InvalidRequest)
at Facility.Core.ServiceResult.Verify() in /_/src/Facility.Core/ServiceResult.cs:line 52
at Facility.Core.ServiceResult`1.get_Value() in /_/src/Facility.Core/ServiceResult.cs:line 261
at LDLS4.Panels.NotesTool.NotesToolViewModel.CreateNotes(AsyncMethodContext context, JToken args)I don't know precisely what this error message means but it seems to be related to the highlighting styles you are using - which may be related to the purple check mark you mention.
Hopefully someone with more knowledge of the internals will be able to comment further.
0 -
It looks like you restarted Logos before capturing the logs (as the crash happened before Logos is shown as starting in Logos.log Could you try again but take the logs before restarting.
Logos was still shut down, but I just restarted using the ctrl key, got it to crash, left it shut down, collected the logs again and here they are.
Hope i did it right. Thanks again.
That particular icon I don't use. I use a blue check mark and a purple light bulb though.
For what its worth I have this Beta on another PC running W10 and it does the same thing there also.
I take it your windows device doesn't have this issue?
0 -
Bump for Logos employee please
0
