Comment 6 for bug 1424769

I quote the irc conversation (with permission from mlankhorst):
as said before there is no easy solution, and for me (unfortunately) this is a "won't fix"

<mlankhorst> LocutusOfBorg1: in general vm's should use the unrenamed stack, and trusty 14.04.1
<mlankhorst> you can still use the lts-utopic kernel if you want
<LocutusOfBorg1> mlankhorst, I'm the virtualbox maintainer lol
<LocutusOfBorg1> I'm asking how to (if possible) fix the "bug"
<mlankhorst> create a virtualbox-x11-lts-utopic :P
<LocutusOfBorg1> yes, I was thinking about something like that, how to trigger the rebuild with the -lts-utopic packages?
<LocutusOfBorg1> and how can I be sure users will pick up it?
<LocutusOfBorg1> seems a big trouble
<mlankhorst> they won't pick it up, you need to create a rename for the -lts-utopic package
<mlankhorst> you need to create a separate virtualbox-lts-utopic package
<LocutusOfBorg1> and maintain it ;)
<mlankhorst> or advise users to stay on 14.04.1, they can upgrade the kernel if they want
<mlankhorst> the problem is that newer xorg may break the x11 api, so you can't just rebuild the old virtualbox against a newer xorg in some cases
<LocutusOfBorg1> I guess I need (in case of breakage) to patch the code like I do with the kernel