L10 crashing with new Reading Plan
Every time I try to generate a Reading Plan, L10 closes unexpectedly. Anyone else have this problem? I tried removing and reinstalling the application with no luck.
Comments
-
Deleting the app is rarely a fix for the desktop app. If you would like assistance, provide more details and logs. See my signature line.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
That was the 1st thing that Logos said to try. If you want the log that shows up after Logos quits, I copied & pasted it.
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------/* deleted un-needed long report */
Model: MacBookPro12,1, BootROM 476.0.0.0.0, 2 processors, Dual-Core Intel Core i5, 2.7 GHz, 8 GB, SMC 2.28f7
Graphics: Intel Iris Graphics 6100, Intel Iris Graphics 6100, Built-In
Display: Color LCD, 2560 x 1600 Retina, Main, MirrorOff, Online
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1867 MHz, 0x80CE, 0x4B3445364533303445452D45474346000000
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1867 MHz, 0x80CE, 0x4B3445364533303445452D45474346000000
AirPort: spairport_wireless_card_type_wifi (0x14E4, 0x133), Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1710.4)
AirPort:
Bluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM0256G, 251 GB
USB Device: USB30Bus
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 27.10 -
Raymond Deck said:
That was the 1st thing that Logos said to try.
I think you misunderstood. Deleting the app is rarely a fix. Where did you recieve this advice?
Raymond Deck said:If you want the log that shows up after Logos quits, I copied & pasted it.
The log you posted is not what is needed. The log that is needed is called "logos.log" and is created by Logos, not by Apple. The Logos.log file will tell the techies step by step what happened "behind the scenes." Additionally, you should not "paste" logs into the forum as they are difficult to read in that format and make having a "conversation" difficult. Please see my signature line to learn how to enable and post logs. If you have any questions, please do feel free to follow up.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Here's a link to another report of this issue.
0 -
This would appear to be a Mac only issue as I had no problems creating Plans from two different sources i.e. the resource panel menu and the Docs menu.
Dave
===Windows 11 & Android 13
0 -
I've forwarded a link of your post to the Logos tech customer service rep who is trying to help me. (I also forwarded him a link to the other post where this problem is reported.)
It seems to be a rare problem - I've only found 3 of us experiencing it so far. It is interesting that we are all Mac users.
I suppose not everyone will have tried to create a reading plan this soon after installing Logos 10.
Also, for me, I'm able to create SOME reading plans. But others cause Logos to crash as soon as I hit "Create," every time, predictably.
I'm glad Logos tech is on it.
Maria
0 -
Found another person:
https://community.logos.com/forums/p/211696/1233959.aspx#1233959
0 -
I'm having the same issue. Here is my log and details to reproduce. I've also emailed this content to support@logos.com.
When I'm creating a reading plan, Logos unexpectedly closes.
Steps to Reproduce:1. Start Logos2. Click the Documents Icon in left navigation bar3. Click "New"4. Click "Reading Plan"5. Click "Generate a Reading Plan"6. Click "Start"I'm running Logos 10.1.0.0041 on an M1 Pro MacBook Pro running macOS 12.6.Note that only creating a Reading Plan using the second option, "Generate a Reading Plan" in step #4 creates this problem. The first and third selection option categories seem to work.Also note that after the crash, searching documents shows that the reading plan was actually created. However, it has not been populated or started. From here, it is possible to edit the reading plan. By changing any parameter of the reading plan and then selecting "Done", the reading plan will populate and start without crashing.0 -
I'm having the exact same problem as Stephen. Did anyone get a resolution?
I experience repeated crashes of Logos 10 when I try to create a new reading plan.- Open Logos Application
- Select "Documents"
- Select "New"
- Select "Reading Plan"
- Logos crashes
- Reopen Logos
- Select "Documents"
- "Untitled Reading Plan" shows in the Documents list and is editable.
The same behavior occurs if I try to select "Start Reading Plan" from within any resource (Bible, Monograph, Commentary, etc.)I emailed Logos Support with the Log file.
0 -
Welcome Max.
Max said:I emailed Logos Support with the Log file.
If you wish to receive support from the forum please attach the log file using the paperclip icon.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
If you wish to receive support from the forum please attach the log file using the paperclip icon.
Thanks, Dave! I attached the Log file.
0 -
Dave
===Windows 11 & Android 13
0 -
0
-
I discovered that the crash happens only when Multiple Book View is active in any tab. If there is any tab with Multiple book display active, the crash occurs when trying to make a reading plan either from the Documents or from an individual text, monograph, etc. But, if I de-select Multiple Book Display, I can create a new Reading Plan without the crash.
0 -
Max said:
I discovered that the crash happens only when Multiple Book View is active in any tab. If there is any tab with Multiple book display active, the crash occurs when trying to make a reading plan either from the Documents or from an individual text, monograph, etc. But, if I de-select Multiple Book Display, I can create a new Reading Plan without the crash.
I can reproduce that in Windows 11, Verbum 25.0.
Dave
===Windows 11 & Android 13
0 -
I have been having a similar problem since February.
https://community.logos.com/forums/p/214376/1252777.aspx
Windows 10, Logos 10
0 -
Willy Arnold said:
I have been having a similar problem since February.
For what it's worth, your issue (we have a case) is actually a separate issue. They are similar, but different pieces behind the scenes.
0 -
Hello all,
I was able to replicate the crash above and created a case for our team to further investigate.
0
