On Mon, Jan 03, 2011 at 09:14:47PM +0100, Philippe Marschall wrote:
> On 03.01.2011 16:42, David T. Lewis wrote:
> > On Mon, Jan 03, 2011 at 03:57:07PM +0100, Philippe Marschall wrote:
> >> On 01/03/2011 03:25 PM, Alexandre Bergel wrote:
> >>> Hi!
> >>>
> >>> Sorry for the late answer. The student is now in my office and there is indeed a problem.
> >>> UUIDPlugin is not present on his harddisk. Maybe built in the VM.
> >>>
> >>> I found the class UUID and remove the call to the primitive. It works. Strange problem. Shall I report it in codegoogle?
> >>
> >> Has been known for two years, shouldn't happen, nobody cares.
> >>
> >
> > Huh ?!?!? What do you mean "nobody cares"?
>
> Nodby cares enough to get to the bottom of it and fix it once and for
> all. And yes, that includes me. It's just an observation. So if this is
> really critical for somebody then he'll have to fix it himself.
> Reporting the same bug again won't make a difference. That's just how
> open source is.
>
> Cheers
> Philippe
>

Yep :)

But I do want to make it clear that it seems the bug is not in
the plugin, it is in the libuuid implementations. We've all been
trying to find workarounds, but unfortunately not with much
success. For a while we could work around it by compiling the
plugin internally (which somehow prevents the bug from being
exposed), but now we have some 64-bit Linux distros that accidentally
left the 32-bit libuuid out of the distro, which prevents the VM
from running if the plugin was compiled internally. I'm sure it
has been fixed in up to date distros, but now we have one set of
Linux users with buggy libuuid libraries, and another set of Linux
users with missing 32-bit libuuid libraries, so somebody is going
to get screwed either way now :-/

I'm sure there must be some way to fix this that we're all missing,
so if anyone wants to look at it with a fresh set of eyes that
would be great.

Dave