LUMINAR NEO terminates if a directory referenced in the Catalog is moved outside of NEO
AnsweredI understand that Catalog-controlled directories and files need to be moved while NEO is running, but an error should be returned telling the user to locate the moved resource. This is done by Adobe Lightroom, On1, and other software. It is a common practice for software to allow the user to recover rath than the application simply terminating with NO visible cause to the user.
But that is what NEO does now. I moved a directory referenced by NEO's catalog, and all NEO did was start up for a few seconds, and the NO indication of why back to me.
Being a 45-year retired software developer, I knew to look in the console log and found the text noted following (and there was a memory dump as well).
Please fix this by at the VERY LEAST returning an error to the desktop, and better yet, go ahead and start-up and require the user to re-locate the moved resource instead of NEO just dying with no indication why it has.
part of the crash test:
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------
Process: Luminar Neo [1944]
Path: /Applications/Luminar Neo.app/Contents/MacOS/Luminar Neo
Identifier: com.skylum.luminarneo
Version: 1.3.0 (12583)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2022-09-13 17:04:28.6179 +1000
OS Version: macOS 12.6 (21G115)
Report Version: 12
Anonymous UUID: CEB2C64F-FCF9-4600-6475-BDA31C821F52
Time Awake Since Boot: 1500 seconds
System Integrity Protection: enabled
Crashed Thread: 22 Dispatch queue: com.skylum.DBCoreWrapper.block-dispatcher.<MPDBCatalog: 0x6000003fc500>
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
abort() called
Application Specific Backtrace 0:
0 CoreFoundation 0x000000018c4f5148 __exceptionPreprocess + 240
1 libobjc.A.dylib 0x000000018c23fe04 objc_exception_throw + 60
2 CoreFoundation 0x000000018c5200cc _CFBundleGetValueForInfoKey + 0
3 DBCoreWrapper 0x0000000105acce90 -[MPDBCatalog handleDBReactorBlock:withDescription:raiseException:] + 428
4 DBCoreWrapper 0x0000000105ab9200 __70-[MPDBCatalog renamePath:withVolume:newPath:newVolume:withCompletion:]_block_invoke + 192
5 libdispatch.dylib 0x000000018c1e25f0 _dispatch_call_block_and_release + 32
6 libdispatch.dylib 0x000000018c1e41b4 _dispatch_client_callout + 20
7 libdispatch.dylib 0x000000018c1eb8a8 _dispatch_lane_serial_drain + 668
8 libdispatch.dylib 0x000000018c1ec404 _dispatch_lane_invoke + 392
9 libdispatch.dylib 0x000000018c1f6c98 _dispatch_workloop_worker_thread + 648
10 libsystem_pthread.dylib 0x000000018c3a4360 _pthread_wqthread + 288
11 libsystem_pthread.dylib 0x000000018c3a3080 start_wqthread + 8
console log output
EE | 2022/09/14 14:34:22:052 MPRawJpegService:220 "-[MPRawJpegService processChanges:]": [MPRawJpegService processChanges:]: mismatch 5
EE | 2022/09/14 14:34:22:059 MPDBCatalog:2124 "-[MPDBCatalog handleDBReactorBlock:withDescription:raiseException:]": MPDBCatalog handled exception: [DBCoreImpl::Transaction] process transaction failed: UNIQUE constraint failed: paths.volume_id_int_64, paths.path_wide_chUPDATE paths SET path_wide_ch=replace(path_wide_ch, 'Users/marty/Desktop/!InProgress/LuminaNEOPlay', 'Users/marty/Desktop/LuminaNEOPlay'), volume_id_int_64=3 WHERE volume_id_int_64=3 AND (path_wide_ch LIKE 'Users/marty/Desktop/!InProgress/LuminaNEOPlay' OR path_wide_ch LIKE 'Users/marty/Desktop/!InProgress/LuminaNEOPlay/%')
-
Hi Martin.
Please try the following steps:
- Hold down the Option key on your keyboard and start Luminar. Keep holding Option until you see a window with a list of available backups appear.
- Select a backup that was created before you encountered the issue with the library and click Restore from Backup.
Here is the video tutorial that may also be helpful: https://www.loom.com/share/2fad8457bbb34faa948ea766a002aad8
Please sign in to leave a comment.
Comments
1 comment