>> Xrandr will only by default show the modes that the monitor explicitly supports. So, how did you accidently do that?
Well we picked a resolution from the graphical dialog and the TV said it doesn't support that resolution and we never saw a display again. Like I said, the theory is that the dialog should only display the resolutions that the monitor supports, but in practice that's not the case and we get to waste a couple hours.
>> Also a reinstall, seriously? This sounds like you don't know very much about linux.
Did some googling, couldn't find anything solid. Tried a few things with no results. Faster to reinstall. Back in the day of static configuration this would have been easy to fix but I dunno where the graphical tools keep their config for resolution and nothing good turned up on google.
>> That sounds mighty strange. I've not seen a Linux system respond to monitor hotplug events with an action by default well, ever. They can respond but you have to set it up. Also, I note the problem was with *your* application. Are you sure it wasn't a bug in your code.
Only happened with TVs connected on HDMI, not PC monitors. Also happened with Qt Creator. So not a bug in our application, but possibly some bizarre combination of hardware and Qt and X bug. Again, several hours down the drain chasing stuff that should never be a problem.