How to solve blank Safari Window / Safari crash (10.1.2)?











up vote
5
down vote

favorite
1












Running Yosemite 10.10.5 on MacBook Air (early 2014), with Safari v. 10.1.2.



New Safari windows come up blank. Typing a URL into them doesn't load the pages.



Quitting Safari and relaunching causes System error:




Safari cannot be opened because of a problem.



Check with the developer to make sure Safari works with this version of Mac OSX. You may have to reinstall the application. Be sure to sure to install any available updates for the application and Mac OSX."




Crash report (and launching Safari from Terminal) shows this error:



dyld: Library not loaded: /usr/lib/libcrypto.35.dylib
Referenced from: /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice
Reason: image not found
Trace/BPT trap


Listing the directory shows that files were updated here (presumably because of iTunes update) that are proximate to this problem:



drwxr-xr-x   3 root  wheel      102 Dec 14 08:52 AppleMobileDeviceHelper.app
drwxr-xr-x 3 root wheel 102 Dec 14 08:52 AppleMobileSync.app
-rwxr-xr-x 1 root wheel 4119552 Oct 16 21:31 MobileDevice
drwxr-xr-x 45 root wheel 1530 Oct 16 21:31 Resources
drwxr-xr-x 3 root wheel 102 Oct 16 20:49 _CodeSignature
-rwxr-xr-x 1 root wheel 43936 Oct 16 21:31 reenumerate_ios_devices


(two December 14th files indicate recent update compared to older files)



Timestamps of those updated files coincide with iTunes being updated to 12.8.1.2.



Hypothesis: Updating iTunes to 12.8.1.2
updated /System/Library/PrivateFrameworks/MobileDevice.framework to a version incompatible with Safari 10.1.2. Workaround 2 (below) supports hypothesis.



WORKAROUND 1: Install/Use Firefox



WORKAROUND 2: Move /System/Library/PrivateFrameworks/MobileDevice.framework to the trash (or somewhere else)
WORKAROUND 3 (not yet verified but presumed to work): Install macOS Mojave.



Posted here in case someone has a direct fix for users who can't update to Mojave, don't want to lose capabilities that MobileDevice.framework provides, and can't (or don't want to be forced to) switch to Firefox.










share|improve this question







New contributor




Khan Klatt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • To address the previous comments: 1. Safari updates itself. 2. The file is not on the system, Apple probably forgot to include it or linked to a version not existant on Yosemite. 3. /usr is definitely not a user library, it is the UNIX path to where non-kernel (userland) software reside (among other things).
    – geira
    2 hours ago















up vote
5
down vote

favorite
1












Running Yosemite 10.10.5 on MacBook Air (early 2014), with Safari v. 10.1.2.



New Safari windows come up blank. Typing a URL into them doesn't load the pages.



Quitting Safari and relaunching causes System error:




Safari cannot be opened because of a problem.



Check with the developer to make sure Safari works with this version of Mac OSX. You may have to reinstall the application. Be sure to sure to install any available updates for the application and Mac OSX."




Crash report (and launching Safari from Terminal) shows this error:



dyld: Library not loaded: /usr/lib/libcrypto.35.dylib
Referenced from: /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice
Reason: image not found
Trace/BPT trap


Listing the directory shows that files were updated here (presumably because of iTunes update) that are proximate to this problem:



drwxr-xr-x   3 root  wheel      102 Dec 14 08:52 AppleMobileDeviceHelper.app
drwxr-xr-x 3 root wheel 102 Dec 14 08:52 AppleMobileSync.app
-rwxr-xr-x 1 root wheel 4119552 Oct 16 21:31 MobileDevice
drwxr-xr-x 45 root wheel 1530 Oct 16 21:31 Resources
drwxr-xr-x 3 root wheel 102 Oct 16 20:49 _CodeSignature
-rwxr-xr-x 1 root wheel 43936 Oct 16 21:31 reenumerate_ios_devices


(two December 14th files indicate recent update compared to older files)



Timestamps of those updated files coincide with iTunes being updated to 12.8.1.2.



Hypothesis: Updating iTunes to 12.8.1.2
updated /System/Library/PrivateFrameworks/MobileDevice.framework to a version incompatible with Safari 10.1.2. Workaround 2 (below) supports hypothesis.



WORKAROUND 1: Install/Use Firefox



WORKAROUND 2: Move /System/Library/PrivateFrameworks/MobileDevice.framework to the trash (or somewhere else)
WORKAROUND 3 (not yet verified but presumed to work): Install macOS Mojave.



Posted here in case someone has a direct fix for users who can't update to Mojave, don't want to lose capabilities that MobileDevice.framework provides, and can't (or don't want to be forced to) switch to Firefox.










share|improve this question







New contributor




Khan Klatt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • To address the previous comments: 1. Safari updates itself. 2. The file is not on the system, Apple probably forgot to include it or linked to a version not existant on Yosemite. 3. /usr is definitely not a user library, it is the UNIX path to where non-kernel (userland) software reside (among other things).
    – geira
    2 hours ago













up vote
5
down vote

favorite
1









up vote
5
down vote

favorite
1






1





Running Yosemite 10.10.5 on MacBook Air (early 2014), with Safari v. 10.1.2.



New Safari windows come up blank. Typing a URL into them doesn't load the pages.



Quitting Safari and relaunching causes System error:




Safari cannot be opened because of a problem.



Check with the developer to make sure Safari works with this version of Mac OSX. You may have to reinstall the application. Be sure to sure to install any available updates for the application and Mac OSX."




Crash report (and launching Safari from Terminal) shows this error:



dyld: Library not loaded: /usr/lib/libcrypto.35.dylib
Referenced from: /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice
Reason: image not found
Trace/BPT trap


Listing the directory shows that files were updated here (presumably because of iTunes update) that are proximate to this problem:



drwxr-xr-x   3 root  wheel      102 Dec 14 08:52 AppleMobileDeviceHelper.app
drwxr-xr-x 3 root wheel 102 Dec 14 08:52 AppleMobileSync.app
-rwxr-xr-x 1 root wheel 4119552 Oct 16 21:31 MobileDevice
drwxr-xr-x 45 root wheel 1530 Oct 16 21:31 Resources
drwxr-xr-x 3 root wheel 102 Oct 16 20:49 _CodeSignature
-rwxr-xr-x 1 root wheel 43936 Oct 16 21:31 reenumerate_ios_devices


(two December 14th files indicate recent update compared to older files)



Timestamps of those updated files coincide with iTunes being updated to 12.8.1.2.



Hypothesis: Updating iTunes to 12.8.1.2
updated /System/Library/PrivateFrameworks/MobileDevice.framework to a version incompatible with Safari 10.1.2. Workaround 2 (below) supports hypothesis.



WORKAROUND 1: Install/Use Firefox



WORKAROUND 2: Move /System/Library/PrivateFrameworks/MobileDevice.framework to the trash (or somewhere else)
WORKAROUND 3 (not yet verified but presumed to work): Install macOS Mojave.



Posted here in case someone has a direct fix for users who can't update to Mojave, don't want to lose capabilities that MobileDevice.framework provides, and can't (or don't want to be forced to) switch to Firefox.










share|improve this question







New contributor




Khan Klatt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











Running Yosemite 10.10.5 on MacBook Air (early 2014), with Safari v. 10.1.2.



New Safari windows come up blank. Typing a URL into them doesn't load the pages.



Quitting Safari and relaunching causes System error:




Safari cannot be opened because of a problem.



Check with the developer to make sure Safari works with this version of Mac OSX. You may have to reinstall the application. Be sure to sure to install any available updates for the application and Mac OSX."




Crash report (and launching Safari from Terminal) shows this error:



dyld: Library not loaded: /usr/lib/libcrypto.35.dylib
Referenced from: /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice
Reason: image not found
Trace/BPT trap


Listing the directory shows that files were updated here (presumably because of iTunes update) that are proximate to this problem:



drwxr-xr-x   3 root  wheel      102 Dec 14 08:52 AppleMobileDeviceHelper.app
drwxr-xr-x 3 root wheel 102 Dec 14 08:52 AppleMobileSync.app
-rwxr-xr-x 1 root wheel 4119552 Oct 16 21:31 MobileDevice
drwxr-xr-x 45 root wheel 1530 Oct 16 21:31 Resources
drwxr-xr-x 3 root wheel 102 Oct 16 20:49 _CodeSignature
-rwxr-xr-x 1 root wheel 43936 Oct 16 21:31 reenumerate_ios_devices


(two December 14th files indicate recent update compared to older files)



Timestamps of those updated files coincide with iTunes being updated to 12.8.1.2.



Hypothesis: Updating iTunes to 12.8.1.2
updated /System/Library/PrivateFrameworks/MobileDevice.framework to a version incompatible with Safari 10.1.2. Workaround 2 (below) supports hypothesis.



WORKAROUND 1: Install/Use Firefox



WORKAROUND 2: Move /System/Library/PrivateFrameworks/MobileDevice.framework to the trash (or somewhere else)
WORKAROUND 3 (not yet verified but presumed to work): Install macOS Mojave.



Posted here in case someone has a direct fix for users who can't update to Mojave, don't want to lose capabilities that MobileDevice.framework provides, and can't (or don't want to be forced to) switch to Firefox.







itunes yosemite safari crash






share|improve this question







New contributor




Khan Klatt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Khan Klatt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Khan Klatt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 5 hours ago









Khan Klatt

261




261




New contributor




Khan Klatt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Khan Klatt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Khan Klatt is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












  • To address the previous comments: 1. Safari updates itself. 2. The file is not on the system, Apple probably forgot to include it or linked to a version not existant on Yosemite. 3. /usr is definitely not a user library, it is the UNIX path to where non-kernel (userland) software reside (among other things).
    – geira
    2 hours ago


















  • To address the previous comments: 1. Safari updates itself. 2. The file is not on the system, Apple probably forgot to include it or linked to a version not existant on Yosemite. 3. /usr is definitely not a user library, it is the UNIX path to where non-kernel (userland) software reside (among other things).
    – geira
    2 hours ago
















To address the previous comments: 1. Safari updates itself. 2. The file is not on the system, Apple probably forgot to include it or linked to a version not existant on Yosemite. 3. /usr is definitely not a user library, it is the UNIX path to where non-kernel (userland) software reside (among other things).
– geira
2 hours ago




To address the previous comments: 1. Safari updates itself. 2. The file is not on the system, Apple probably forgot to include it or linked to a version not existant on Yosemite. 3. /usr is definitely not a user library, it is the UNIX path to where non-kernel (userland) software reside (among other things).
– geira
2 hours ago










2 Answers
2






active

oldest

votes

















up vote
4
down vote













Same happened to me--same error, same OS X and same Safari version. The following files in /System/Library/PrivateFrameworks/ had today's timestamp on my computer. I restored these files from my backup in Time Machine. Safari is working again.



drwxr-xr-x  5 root  wheel  170 Dec 14 12:30 iTunesAccess.framework
drwxr-xr-x 6 root wheel 204 Dec 14 12:30 CoreFP.framework
drwxr-xr-x 6 root wheel 204 Dec 14 12:30 CoreADI.framework
drwxr-xr-x 5 root wheel 170 Dec 14 12:30 MobileDevice.framework
drwxr-xr-x 5 root wheel 170 Dec 14 12:30 DeviceLink.framework
drwxr-xr-x 6 root wheel 204 Dec 14 12:30 AirTrafficHost.framework





share|improve this answer








New contributor




Ellen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.


















  • Also running Yosemite 10.10.5 on iMac (2009), with Safari v. 10.1.2., Apple auto upgraded iTunes and several other apps last night, my Safari froze, thought it was my internet connect, restarted Safari, but wouldn't start, coming up with generic problem statement, Ignore or Send to Apple. Search the internet using Chrome, and came across your post. So I just deleted the files in /System/Library/PrivateFrameworks/, tried Safari again and it came up. Thanks for the advice.
    – D C
    2 hours ago


















up vote
0
down vote













Indeed, updating the OS to a newer version works. I updated from Yosemite to El Capitan to solve this.






share|improve this answer








New contributor




Lone Wolf is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

















    protected by Community 1 hour ago



    Thank you for your interest in this question.
    Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



    Would you like to answer one of these unanswered questions instead?














    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    4
    down vote













    Same happened to me--same error, same OS X and same Safari version. The following files in /System/Library/PrivateFrameworks/ had today's timestamp on my computer. I restored these files from my backup in Time Machine. Safari is working again.



    drwxr-xr-x  5 root  wheel  170 Dec 14 12:30 iTunesAccess.framework
    drwxr-xr-x 6 root wheel 204 Dec 14 12:30 CoreFP.framework
    drwxr-xr-x 6 root wheel 204 Dec 14 12:30 CoreADI.framework
    drwxr-xr-x 5 root wheel 170 Dec 14 12:30 MobileDevice.framework
    drwxr-xr-x 5 root wheel 170 Dec 14 12:30 DeviceLink.framework
    drwxr-xr-x 6 root wheel 204 Dec 14 12:30 AirTrafficHost.framework





    share|improve this answer








    New contributor




    Ellen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.


















    • Also running Yosemite 10.10.5 on iMac (2009), with Safari v. 10.1.2., Apple auto upgraded iTunes and several other apps last night, my Safari froze, thought it was my internet connect, restarted Safari, but wouldn't start, coming up with generic problem statement, Ignore or Send to Apple. Search the internet using Chrome, and came across your post. So I just deleted the files in /System/Library/PrivateFrameworks/, tried Safari again and it came up. Thanks for the advice.
      – D C
      2 hours ago















    up vote
    4
    down vote













    Same happened to me--same error, same OS X and same Safari version. The following files in /System/Library/PrivateFrameworks/ had today's timestamp on my computer. I restored these files from my backup in Time Machine. Safari is working again.



    drwxr-xr-x  5 root  wheel  170 Dec 14 12:30 iTunesAccess.framework
    drwxr-xr-x 6 root wheel 204 Dec 14 12:30 CoreFP.framework
    drwxr-xr-x 6 root wheel 204 Dec 14 12:30 CoreADI.framework
    drwxr-xr-x 5 root wheel 170 Dec 14 12:30 MobileDevice.framework
    drwxr-xr-x 5 root wheel 170 Dec 14 12:30 DeviceLink.framework
    drwxr-xr-x 6 root wheel 204 Dec 14 12:30 AirTrafficHost.framework





    share|improve this answer








    New contributor




    Ellen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.


















    • Also running Yosemite 10.10.5 on iMac (2009), with Safari v. 10.1.2., Apple auto upgraded iTunes and several other apps last night, my Safari froze, thought it was my internet connect, restarted Safari, but wouldn't start, coming up with generic problem statement, Ignore or Send to Apple. Search the internet using Chrome, and came across your post. So I just deleted the files in /System/Library/PrivateFrameworks/, tried Safari again and it came up. Thanks for the advice.
      – D C
      2 hours ago













    up vote
    4
    down vote










    up vote
    4
    down vote









    Same happened to me--same error, same OS X and same Safari version. The following files in /System/Library/PrivateFrameworks/ had today's timestamp on my computer. I restored these files from my backup in Time Machine. Safari is working again.



    drwxr-xr-x  5 root  wheel  170 Dec 14 12:30 iTunesAccess.framework
    drwxr-xr-x 6 root wheel 204 Dec 14 12:30 CoreFP.framework
    drwxr-xr-x 6 root wheel 204 Dec 14 12:30 CoreADI.framework
    drwxr-xr-x 5 root wheel 170 Dec 14 12:30 MobileDevice.framework
    drwxr-xr-x 5 root wheel 170 Dec 14 12:30 DeviceLink.framework
    drwxr-xr-x 6 root wheel 204 Dec 14 12:30 AirTrafficHost.framework





    share|improve this answer








    New contributor




    Ellen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.









    Same happened to me--same error, same OS X and same Safari version. The following files in /System/Library/PrivateFrameworks/ had today's timestamp on my computer. I restored these files from my backup in Time Machine. Safari is working again.



    drwxr-xr-x  5 root  wheel  170 Dec 14 12:30 iTunesAccess.framework
    drwxr-xr-x 6 root wheel 204 Dec 14 12:30 CoreFP.framework
    drwxr-xr-x 6 root wheel 204 Dec 14 12:30 CoreADI.framework
    drwxr-xr-x 5 root wheel 170 Dec 14 12:30 MobileDevice.framework
    drwxr-xr-x 5 root wheel 170 Dec 14 12:30 DeviceLink.framework
    drwxr-xr-x 6 root wheel 204 Dec 14 12:30 AirTrafficHost.framework






    share|improve this answer








    New contributor




    Ellen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.









    share|improve this answer



    share|improve this answer






    New contributor




    Ellen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.









    answered 3 hours ago









    Ellen

    411




    411




    New contributor




    Ellen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.





    New contributor





    Ellen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.






    Ellen is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.












    • Also running Yosemite 10.10.5 on iMac (2009), with Safari v. 10.1.2., Apple auto upgraded iTunes and several other apps last night, my Safari froze, thought it was my internet connect, restarted Safari, but wouldn't start, coming up with generic problem statement, Ignore or Send to Apple. Search the internet using Chrome, and came across your post. So I just deleted the files in /System/Library/PrivateFrameworks/, tried Safari again and it came up. Thanks for the advice.
      – D C
      2 hours ago


















    • Also running Yosemite 10.10.5 on iMac (2009), with Safari v. 10.1.2., Apple auto upgraded iTunes and several other apps last night, my Safari froze, thought it was my internet connect, restarted Safari, but wouldn't start, coming up with generic problem statement, Ignore or Send to Apple. Search the internet using Chrome, and came across your post. So I just deleted the files in /System/Library/PrivateFrameworks/, tried Safari again and it came up. Thanks for the advice.
      – D C
      2 hours ago
















    Also running Yosemite 10.10.5 on iMac (2009), with Safari v. 10.1.2., Apple auto upgraded iTunes and several other apps last night, my Safari froze, thought it was my internet connect, restarted Safari, but wouldn't start, coming up with generic problem statement, Ignore or Send to Apple. Search the internet using Chrome, and came across your post. So I just deleted the files in /System/Library/PrivateFrameworks/, tried Safari again and it came up. Thanks for the advice.
    – D C
    2 hours ago




    Also running Yosemite 10.10.5 on iMac (2009), with Safari v. 10.1.2., Apple auto upgraded iTunes and several other apps last night, my Safari froze, thought it was my internet connect, restarted Safari, but wouldn't start, coming up with generic problem statement, Ignore or Send to Apple. Search the internet using Chrome, and came across your post. So I just deleted the files in /System/Library/PrivateFrameworks/, tried Safari again and it came up. Thanks for the advice.
    – D C
    2 hours ago












    up vote
    0
    down vote













    Indeed, updating the OS to a newer version works. I updated from Yosemite to El Capitan to solve this.






    share|improve this answer








    New contributor




    Lone Wolf is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.






















      up vote
      0
      down vote













      Indeed, updating the OS to a newer version works. I updated from Yosemite to El Capitan to solve this.






      share|improve this answer








      New contributor




      Lone Wolf is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.




















        up vote
        0
        down vote










        up vote
        0
        down vote









        Indeed, updating the OS to a newer version works. I updated from Yosemite to El Capitan to solve this.






        share|improve this answer








        New contributor




        Lone Wolf is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        Indeed, updating the OS to a newer version works. I updated from Yosemite to El Capitan to solve this.







        share|improve this answer








        New contributor




        Lone Wolf is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        share|improve this answer



        share|improve this answer






        New contributor




        Lone Wolf is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered 3 hours ago









        Lone Wolf

        11




        11




        New contributor




        Lone Wolf is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        Lone Wolf is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        Lone Wolf is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.

















            protected by Community 1 hour ago



            Thank you for your interest in this question.
            Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



            Would you like to answer one of these unanswered questions instead?