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.
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