Ubuntu edgy parallels-config error

R

rebuilder

Bit poster
Hello, I am trying to install the trial version of parallels workstation on an ubuntu edgy machine, but when doing "sudo parallels-config" I get the following:

[: 141: ==: unexpected operator
Compiling Parallels Workstation 2.2 drivers...
Drivers have been compiled successfully.
/usr/bin/parallels-config: 175: pushd: not found
/usr/bin/parallels-config: 186: popd: not found
Installing drivers...
Starting drivers...
/usr/lib/parallels/autostart/drivers_start: 19: Syntax error: "(" unexpected
Parallels Workstation drivers were successfully configured
and compiled but cannot be started (insmod command failed).
Run 'dmesg' command for more information.
exit: 3: Illegal number: -1

I'm kind of at a loss here...
 
I am getting the exact same errors as you posted above. I'm at a bit of a loss as well.. this only happened after upgrading from dapper to edgy.. I even tried with a complete fresh install, and i get the same error.. ughh. :confused:
 
It's the transition from bash to dash. Open up the parallels-config script and change the first line from #!/bin/sh to #!/bin/bash. You'll need to do this for a couple more I recall, like some networking scripts.
 
I tried this today and the configure script worked fine and I can now launch parallels but there is something crazy going on with the display, you can see what is going on here:

http://www.azcazandco.com/parallels.png

The files you need to edit are:

/usr/bin/parallels-configure
/usr/lib/parallels/auto_start/drivers_start
/usr/lib/parallels/auto_start/drivers_stop

HTH
 
It's the transition from bash to dash. Open up the parallels-config script and change the first line from #!/bin/sh to #!/bin/bash. You'll need to do this for a couple more I recall, like some networking scripts
Click to expand...
instead, you may solve this problem once and for all. first find out which shell is default
Code: 
ls -la /bin/sh
if it links to dash you're in trouble. if it links to bash your ok. amend it with
Code: 
sudo ln -sf /bin/bash /bin/sh
For more info, look at this bug filing. The right thing to do would be to change all scripts that are broken (like show in this thread) but if you just want an easy fix for all third party scripts...
 
Actually, that last "fix" has broken stuff for a lot of people. The idea of the transition to dash is to speed up most scripts. I find it easier to fix the random misbehaving one than lose the speed boost.
 
You must log in or register to reply here.
Back
Top