If I have TMDS-1 output to an external monitor, and LVDS disabled, then there's no blanking while Totem (et al) start.
If I have TMDS-1 and LVDS both enabled, there's a long blank while Totem starts.
So this isn't just VGA, it also affects DVI (i.e. TMDS-1) output, with VGA always disabled.
Also, how is the presence/absence of TV output relevant when Totem starts anyway?
I sometimes do this with a TV attached, and all that happens is I get a window as normal, or I can run it full screen on the TV head. It doesn't seen to _do_ anything with the knowledge that there's a TV connected. It behaves exactly the same as any other external display.
So is it just that Totem enumerates the multi-head display properties, the same as running xrandr, and this always causes a full re-detection even though it's not really necessary when no properties are being changed?
I think it would be quite reasonable if starting Totem could just read the info reported by xrandr last time it did a detection. (Similarly, xrandr could do with an option --report-last-values). If you really want to detect or act on changes to what's plugged in, you'll run xrandr or an equivalent tool explicitly anyway.
I can confirm unggnu's observation:
If I have TMDS-1 output to an external monitor, and LVDS disabled, then there's no blanking while Totem (et al) start.
If I have TMDS-1 and LVDS both enabled, there's a long blank while Totem starts.
So this isn't just VGA, it also affects DVI (i.e. TMDS-1) output, with VGA always disabled.
Also, how is the presence/absence of TV output relevant when Totem starts anyway?
I sometimes do this with a TV attached, and all that happens is I get a window as normal, or I can run it full screen on the TV head. It doesn't seen to _do_ anything with the knowledge that there's a TV connected. It behaves exactly the same as any other external display.
So is it just that Totem enumerates the multi-head display properties, the same as running xrandr, and this always causes a full re-detection even though it's not really necessary when no properties are being changed?
I think it would be quite reasonable if starting Totem could just read the info reported by xrandr last time it did a detection. (Similarly, xrandr could do with an option --report- last-values) . If you really want to detect or act on changes to what's plugged in, you'll run xrandr or an equivalent tool explicitly anyway.