Wow, this is an old one. Assuming it's fixed though.
X will configure the outputs differently depending on what's connected at startup, so this could be expected behavior. You may have to unclone or unmirror the displays after starting up this way before you can change things.
Wow, this is an old one. Assuming it's fixed though.
X will configure the outputs differently depending on what's connected at startup, so this could be expected behavior. You may have to unclone or unmirror the displays after starting up this way before you can change things.