Parallels Desktop 9 crashes on Yosemite DP 6

Didn't work for me...

$ sudo /Applications/Parallels\ Desktop.app/Contents/MacOS/Parallels\ Service.app/Contents/MacOS/prl_disp_service -e
WARNING: QApplication was not created in the main() thread.
QFileSystemWatcher::addPath: path is empty

Starting Parallels when the prl_disp_service is running results in the same error message.
 
Didn't work for me...

$ sudo /Applications/Parallels\ Desktop.app/Contents/MacOS/Parallels\ Service.app/Contents/MacOS/prl_disp_service -e
WARNING: QApplication was not created in the main() thread.
QFileSystemWatcher::addPath: path is empty

Starting Parallels when the prl_disp_service is running results in the same error message.

same here :(
 
Same here. Exact message and it still fails to launch

Same here. Exact message and it still fails to launch

Didn't work for me...

$ sudo /Applications/Parallels\ Desktop.app/Contents/MacOS/Parallels\ Service.app/Contents/MacOS/prl_disp_service -e
WARNING: QApplication was not created in the main() thread.
QFileSystemWatcher::addPath: path is empty

Starting Parallels when the prl_disp_service is running results in the same error message.
 
Yosemite Developer Preview 6 and Paralles 9.0.24237.1028877

I have on my test machine Yosemite DP 5 and Parallels 9.0.24237 was working fine until I updated to DP 6 a few hours ago. Since then Parallels is crashing on initial run. The message is:
Unable to start Parallels services. ... Problem ID:15381... CHeck this solution directs a REMOVED PAGE. Any ideas?

Oguz Algan
 
Okay, I have a temporary work-around solution.

Open Terminal and type:

sudo /Applications/Parallels\ Desktop.app/Contents/MacOS/Parallels\ Service.app/Contents/MacOS/prl_disp_service -e


This will launch the dispatcher service. Then you can start Parallels.

Worked for me! Thanks!
 
I got the same messages as Jan Paul, but when I started Parallels, it launched and runs just fine.

EDIT: I'm now getting

ERROR: invalid signature for com.parallels.filesystems.prlufs, will not load

over and over in the console. That makes me extremely nervous, as I don't know what state the filesystem will be in.
 
Last edited:
Okay, I have a temporary work-around solution.

Open Terminal and type:

sudo /Applications/Parallels\ Desktop.app/Contents/MacOS/Parallels\ Service.app/Contents/MacOS/prl_disp_service -e


This will launch the dispatcher service. Then you can start Parallels.

Unfortunately that didn't work for me.

Anyone from Parallels listening? Any thoughts for an immediate (even if "temporary") solution?
 
Back
Top