Scansnap Home wont work anymore since upgrade to Ventura

I have sent other posts about problems I am experiencing since the upgrade to Ventura. I have a Macbook Air with Version 13.4.1 (c) (22F770820d) of Ventura.


One problem i am experiencing recently is that ScanSnap Home, an application to use Fujitsu / Ricoh scanners, fails now when opened.


The report of the error is


-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               ScanSnapHomeMain [36167]
Path:                  /Applications/ScanSnapHomeMain.app/Contents/MacOS/ScanSnapHomeMain
Identifier:            com.fujitsu.pfu.ScanSnapHome
Version:               2.12.0 (8)
Build Info:            ScanSnap Home-8~8
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2023-07-29 11:54:11.5653 +0400
OS Version:            macOS 13.4.1 (22F770820d)
Report Version:        12
Bridge OS Version:     7.5 (20P5060)
Anonymous UUID:        CE985213-6254-7C7B-3399-32981C03FF6E

Sleep/Wake UUID:       ECD71E5F-6D32-41C5-BE3E-174508CC901D

Time Awake Since Boot: 290000 seconds
Time Since Wake:       40092 seconds

System Integrity Protection: enabled

Crashed Thread:        0

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000

Termination Reason:    Namespace DYLD, Code 1 Library missing
Library not loaded: /usr/local/opt/ffmpeg/lib/libavcodec.58.dylib
Referenced from: <2214BC40-B6E6-30AF-9CDB-D982B51DCC65> /usr/local/lib/libopencv_videoio.3.4.0.dylib
Reason: tried: '/Applications/ScanSnapHomeMain.app/Contents/Lib/libavcodec.58.dylib' (no such file), '/usr/local/opt/ffmpeg/lib/libavcodec.58.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/opt/ffmpeg/lib/libavcodec.58.dylib' (no such file), '/usr/local/opt/ffmpeg/lib/libavcodec.58.dylib' (no such file), '/usr/lib/libavcodec.58.dylib' (no such file, not in dyld cache), '/Applications/ScanSnapHomeMain.app/Contents/Lib/libavcodec.58.dylib' (no such file), '/usr/local/Cellar/ffmpeg/5.1.2_5/lib/libavcodec.58.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/Cellar/ffmpeg/5.1.2_5/lib/libavcodec.58.dylib' (no such file), '/usr/local/Cellar/ffmpeg/5.1.2_5/lib/libavcodec.58.dylib' (no such file), '/usr/lib/libavcodec.58.dylib' (no such file, not in dyld cache)
(terminated at launch; ignore backtrace)


I am going to attach the full copy. Does anyone have any clue if this can be fixed and if it is a Ventura problem ? Fujitsu has been updating ScanSnap Home so this application must be working for other people. I wonder if this is a problem specific for my machine and given its upgrade.


MacBook Air 13″, macOS 13.4

Posted on Jul 29, 2023 12:59 AM

Reply

Similar questions

11 replies

Jul 29, 2023 1:19 AM in response to bizmate

Sorry I missed the last part where you mentioned the software is up to date.


What you are experiencing is not normal. Rather than assuming that it matches what most Ventura users are experiencing - it’s not - we may try to figure out if there is something peculiar to your setup that may be a part of the problem. Please run Etrecheck and post its full report here.

Use the “additional text” button and paste the report into the text box.

Usually issues that occur after an OS upgrade tend to be caused by old low level system modifications like kernel extensions or daemons.

Jul 29, 2023 3:14 AM in response to bizmate

Thank you for posting the Etrecheck report. This is far more intelligible for most people than the crash reports, which are mostly for developers or engineers.


It is clear from the report that this mac has stuff that has been carried from OS to OS and across different macs over a long time. For example, you still have Perian, even though it has been unsupported for many years. Same thing with flip4mac. And I guess several of the things installed with macports were intel versions and may be crashing or at least a native M1 version could be used. (Or maybe you did this years ago and don’t even use it anymore, I don’t know).


I think you can begin to experience the real performance of your mac with just a little effort.

With recent macs, you don’t even need to reinstall the OS, which would be a pain.


l will describe the process.


1) Make a Time Machine backup. You should really have this, even if there were no problems.


2) **** From System Settings->General->Transfer or Reset, click

Erase All Content and Settings **** don’t do this without the Time Machine backup!!!


3) When it finishes it will as if you want to migrate your data. Choose “From another mac, startip drive or Time Machine backup”, select your backup, and ***CRUCIAL*** check ONLY the user accounts. Do not check anything else.


This will leave behind all the old system modifications and keep all your documents, photos, mail, preferences, etc


Jul 29, 2023 1:10 AM in response to Luis Sequeira1

They keep updating the app as I mentioned and indeed Ventura is supported. I just regret updating, personally I lost a lot of productivity and time with Ventura, I cannot scan anymore, the shell is messed up too and tooling I had installed before just wont work and i get other problems such as Is there a fix to kernel_task high cpu wh… - Apple Community that remain unresolved and completely block the laptop.


Currently due to all these problems I will not renew my Apple hardware in the future as one of the main reason to get a Mac was the quality and stability of both hardware and software without messing too much around. However right now I am spending a lot of time trying troubleshooting instead of doing work.


Going back to my original post do you have any suggestion that is specific to this error or how this can be escalated to someone in the Mac team ? I have also asked Fujitsu but no help from there either.


Jul 30, 2023 9:04 AM in response to Luis Sequeira1

I have selected all the items excluding macport. I need a list of all apps and their set up as I had. Also starting from scratch to set it up will be painful. I LL see how it behaves and if I have more problems I LL try again but I must say this is a sledge hummer approach that is really time consuming. Hopefully Apple should take care of inconsistencies and conflicts before and during upgrades or really point out to the real crash problem. At the moment none of the errors I see seem consistent and pointing to a clear cause. If a file is conflict or needs updating it would be nice if the error was explicit in that way

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Scansnap Home wont work anymore since upgrade to Ventura

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.