To reproduce:
1-boot to multi-user.target on Intel gfxcard
2-put some valid xrandr command(s) in a file in /etc/X11/xinit/xinitrc.d/, at
least one of which would override EDID and/or Xorg configuration defaults,
e.g.:
xrandr --dpi 108 --output VGA1 --mode 1680x1050
3-ensure no conflict exists in etc/X11/xorg.con* or by overriding user settings
4a-startx a K* session, e.g.:
WINDOWMANAGER=/opt/kde3/bin/startkde startx
WINDOWMANAGER=startkde startx
startx /opt/kde3/bin/startkde
startx startkde
startx, or
4b1-start KDM4 or KDM3
4b2-start KDE3 or Plasma5 or IceWM session
Actual results:
1-xrandr commands have been disregarded as of when session finishes
initializing
Expected results:
1-all valid xrandr commands in /etc/X11/xinit/xinitrc.d/ are in effect by the
time the DE session finishes initializing (same as when using nouveau or radeon
driver)
Comments:
1-Hosts tested today: big41 ATI gfx & Intel gfx & Nouveau gfx 20160318 Plasma5,
big31 Intel gfx 20160307 KDE3 & 20160307 Plasma5, gx27b ATI gfx 20160307
Plasma5, gx280 Intel gfx 201601## KDE3, gx28b ATI gfx 20160303, Intel gfx gx780
20160228 KDE3, hpg33 Intel gfx 20160318 Plasma5, hs80e ATI gfx 20160222
Plasma5, kt88b nouveau gfx 20160209 KDE3, msi85 Intel gfx 20160222 KDE3;
various others KDE4, Plasma 5 and KDE3 in 42.1, 13.2, 13.1.
2-Initially I thought this was about bug 929016 but that seems to be a separate
issue of old, while this is only a month or so old, broken as of TW 20160222,
OK as of TW 20160209. Whether
https://bugs.freedesktop.org/show_bug.cgi?id=94403 is truly identical or merely
overlaps I'm not 100% sure, as not all types of X sessions pay any heed to
scripted xrandr somewhere in /etc/X11/*. I only use TDE (not available for TW),
KDE3 (primarily), Plasma and KDE4, except occasionally IceWM and rarely XFCE
for comparing basic X behavior and bug triage.
3-As per comment 7 in upstream bug, xrandr > /dev/null preceding causes the
subsequent otherwise failing xrandr command to be obeyed (on host big41 at
least, not today tested elsewhere).