Comment # 5 on bug 971885 from Egbert Eich

(In reply to Felix Miata from comment #4)
> (In reply to Egbert Eich from comment #3)
> > (In reply to Felix Miata from comment #2)
> 
> > > 	This applies only when using Intel driver
>  
> > I very much doubt this as I have conducted my tests on an AMD only system:
> > it has an AMD GPU so no Intel graphics and a discrete Radeon card.
> 
> Using the hardware, not a VM (if it could matter?)? No VMs used here except
> for running DOS apps using OS/2.
> ...
I've tested on a VM first, but due to boo#971907 I moved to real hardware.

> >The list below is not really relevant...
> 
> Dunno exactly what you mean by list, but...

The one I've deleted as the comment was getting a bit lenghty.

> ...
> >> As the breakage is Intel gfx dependent,
> 
> > I'm fairly certain that this is not Intel specific. As mentioned, I've seen
> > this on AMD graphics as well. I will conduct some more tests to be certain
> > once I find time.
> 
> I did show you 1 nouveau and 3 radeon TW installations updated post-February
> that work the same as in 42.1 and earlier, same as the Intels did before
> mid-February. Maybe hardware age would explain the difference if you see it
> on AMD. My newest AMD is HD5450. Could port choice could be involved, maybe
> you on HDMI or DisplayPort? All the tests I listed here were using the same
> VGA cable and LCD. Conversion from DVI output was needed only for the 8600GT.

No, definitely not. The behaviour is more or less the same for all vintages and
outputs. 'more or less' as different generations and different outputs may have
different limitations and restrictions. 
It could well be that those limitations don't let you do what you would like to
do. After all, the only pattern I see from your list in comment #2 is that some
systems using Intel graphics are clamped to 1440x900 and don't get up to
1680x1050.

> >> 	[Module-kscreen]
> >> 	autoload=false 
> 
> > Right - how long did you have to google to find that?
> 
> Maybe none? :-) That was many moons ago. Could be that Alex Fiestas or
> Thomas L�bking told me on a KDE mailing list, or someone on KDE IRC. I was
> obviously well aware of it by 30 months ago:
> https://bugs.kde.org/show_bug.cgi?id=320561#c58

Sure. The point I was trying to make was: this is nothing that's documented in
one place and in a way that you'd just go to the documentation, read a bit and
find the answer. Your approach didn't invalidate my point.