If you're certain it's got enough information, you shouldn't fight with the bug bot, just set the bug to Wishlist or Triaged.
However, in looking at it myself I see there is not really enough information here to guess at what's wrong. "Xvfb failed to start" just brings up so many other questions. Why did it fail? What happens if you run it in isolation? Why is it being used on sparc on the buildd's? Why are buildd's set up on sparc and who maintains them and can they do a manual Xvfb run to get more info (and an Xorg.0.log)? Can the issue be reproduced on x86 or amd64? If Xvfb is not supported on sparc and it does fail only there, can the applications trying to use it (presumably for testing) simply skip running it if they are running on sparc? If you think this is an important issue, I'd encourage you to do some additional legwork on it. I generally never look at sparc problems myself, but if you locate a patch that fixes it I'd be happy to look at including it in Karmic if there's still time. -- Xvfb failed to start on sparc https://bugs.launchpad.net/bugs/410711 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
