Ok, the xrandr "bug" (it is a bug! EDIT: NO, it is not a bug, some set ups do support 1368x768) is superfluous, 1368x768 resolution is not possible, it's neither supported by your card or monitor.
Interestingly, the nv driver does not support 1366x768 for your card, says so in your Xorg.0.log @line 439
Code: Select all
[ 36.055] (II) NV(0): Not using driver mode "1366x768" (width too large for virtual size)
Code: Select all
[ 36.049] (II) NV(0): h_active: 1366 h_sync: 1436 h_sync_end 1579 h_blank_end 1792 h_border: 0
[ 36.049] (II) NV(0): v_active: 768 v_sync: 771 v_sync_end 774 v_blanking: 798 v_border: 0
Code: Select all
[ 36.049] (II) NV(0): #0: hsize: 1280 vsize 720 refresh: 60 vid: 49281
[ 36.049] (II) NV(0): #1: hsize: 1280 vsize 800 refresh: 60 vid: 129
I am going to report this bug to the xrandr maintainer. It doesn't fix your issue but it will clarify things in the "firstrun" dialog for resolution. It would also be possible in the mean time to filter out any reference to "1368", so until I hear from the xrandr devs that will do. I'll post a patch soon and inform shinobar and Barry (firstrun and quicksetup maintainers).No, not doing this now.I will contact the devs and see why your's lists 1368.
On further research there are things you can do to "fix" your issue. I wouldn't expect that noobs would bother. If the problem is only that the display is shifted then that's easily fixed with your monitors hard settings, most noobs know that, especially if they have older monitors. Maybe "xvidtune" would work too. This issue is out of my hands. If this is not apparent in Lupu I'd like to know the screen res you get. If Xorg is choosing it it's self then likely it's not 1366x768, could be wrong though.
Attachment removed, it wont make a difference.