parallels no longer works after upgrade

Hi Chris,

Thanks for letting me know about this. We obviously tested it here and haven't seen that behavior - Can you please provide me with your kernel version?

Thanks!

-Brian

2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux

Also, nvidia binary xwin and ndiswrapper for broadcomm wireless.

confirmed here with fresh install of 2.2.2224-1gutsy1 on 7.10, 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux

Followed advice in thread http://forum.parallels.com/showthread.php?s=153826b43f2edd25ba877ac20c552614&p=98423#post98423 on Parallels forum and ran sudo parallels-config which returned the following:

Compiling Parallels Workstation 2.2 drivers...

Can not compile and/or link drivers. Read /usr/lib/parallels/doc/INSTALL
and follow instructions specified in this document.

Compilation log is available at /usr/lib/parallels/comp.log.6001.error

Attached is said log file. Also to note is that the INSTALL doc mentioned above does not exist, perhaps a different bug needs to be filed for that. Seems a few others are experiencing this also:

http://ubuntuforums.org/showthread.php?t=706378

Just wanted to update everyone here. This issue is a result of a setuid issue whereby in a previous build one executable had been setuid root and in this build a different executable had been setuid root and it wasn't handled properly. We are working with Parallels to resolve this issue (as well as another general error reported by their user base) and removing ALL setuid executables.

-Brian

Thanks for the update Brian!

Is there any sort of ETA for the corrected build? I hate to be a nudge, but after all, this is a commercial product, which I duly (and happily) paid for, and not FOSS ... I am contacting my Parallels account rep as well, to see if they have an ETA - I will post an update if/when I hear anything back.

FYI for folks on this list, in case this wasn't obvious from Brian's explanation, a workaround until we get a new build is to run parallels workstation via 'sudo' or else using a root login session, thus eliminating the setuid issue. Buyer beware, this is not a good practice, especially if you're using parallels on a linux host to sandbox windows environments (like myself), and, as always, YMMV. I've been successful with this workaround on an Athlon X2 with Gutsy kernel 2.6.22-14-generic.

HTH/HAND

--
immaginos

Hi,

Yes, it's a permissions issue, so running it with sudo should do the trick in the meantime. We are pushing for a fix for tomorrow night.

Thanks for the patience. They took this time to fix many other smaller bugs as well.

-Brian

Fixed in 2.2.2226-1gutsy1

Confirmed fixed & many thanks!