puredyne-team team mailing list archive

[danstowell <danstowell+launch@xxxxxxxxx>]

OK so this is getting a bit tangled but:

 * will remove virtualbox-ose-guest-x11 - aymeric, you said in Comment 1 "Removing the xorg.conf solves the problem" but maybe you were rewinding to a version that removed xorg.conf as well as virtualbox-ose-guest-x11? If so then all is consistent. If not then there's an anomaly with aymeric's machine. And, I hope there is some other way you can get it to run in virtualbox!
 * assuming the first case above, it seems the xorg.conf isn't actually causing any problems.
 * scripting "(sleep 1;xset s off -dpms &)&" seems to me a bit obscure in that it could cause problems for users if it's bundled, since they might not know how to get at that script.
 * the current version of gdm doesn't seem to have options that would let us control DPMS (the options did exist in older 2.20 gdm). So I don't think it can be done via gdm.

The motivation for disabling DPMS is because it interferes with audio,
causes yucky xruns on wakeup. Whether or not this is serious enough to
warrant the xorg.conf may be debatable; I don't think the xorg.conf
interferes with automagic. But if folks think it would be cleaner to
leave the xorg.conf out and have the user deal with DPMS if they want
to, then I can live with that. Opinions welcome pls

-- 
xorg.conf and virtualbox-ose-guest-x11 conflict
https://bugs.launchpad.net/bugs/490067
You received this bug notification because you are a member of puredyne
team, which is the registrant for Puredyne Live.

Status in Puredyne liveCD/DVD/USB/HD: Confirmed

Bug description:
Seems like the barebones /etc/X11/xorg.conf which I added, and virtualbox-ose-guest-x11, may conflict. Having them both causes a x11+gdm crash loop when booting a live-USB on my Eee 701, the last message showing being "VirtualBox Additions disabled, not in a Virtual Machine".

IIRC, it was the xorg.conf which caused problems in aymeric's virtualbox and led to the addition of virtualbox-ose-guest-x11 in the first place. So maybe it's just a rubbish xorg.conf :(