[nvidia] Switch user causes screen resolution to change

Having about the same problem.

Just after install of nvidia drivers 9631 everything seemed to work fine. I tested immediately the "switch user" functionality, it looked promising. After a shot while the problem appeared again: switch user causes pop up of a login screen but in a wrong resolution: 640x480@60Hz. And after logging in one cannot switch a resolution: 640x480@60Hz is the only available for GNOME preferences. Optimal resolution for my monitor (Philips 190B) is 1280x1024@60Hz.

I tried to remove from xorg.conf all available resolutions except the optimal one, but it did not help at all.

AFAIR, I did not have such a problem with open "nv" driver, but I have to try more to see if it is actually like that.

Currently, I am trying "nvidia-glx" driver from the official repository.

Other problem, that I have is caused (sometimes) by the following sequence of events:
1. log in with some user
2. switch user
3. try to switch user again
Sometimes on the 3rd step system just locks. It does not respond to any keys Ctrl-Alt-Backspace, Ctrl-Alt-F1 or whatever.

Probably, these problems are related.

They also may be related to the bugs #72229 and #68855.

My system: ASUS A7N8X, Athlon XP 2500+ with nvidia GeFroce 4 Ti 4200 (XFX). Ubuntu 6.10 with latest updates.

I would really appreciate any tips: what log files may I study to locate the source of problem? What additional information may I provide to resolve these issues?

I have the same issue.. as soon as I click switch user my resolution drops down to 640x480.. there are no settings available in the gnome panel to change the resolution.. i usually have to restart gdm to get my settings back to normal..

sorry.. my setup is a p4 2.8, using an nvidia geforce 4 ti4200 and the nvidia-glx drivers.. I am using ubuntu 7.40 clean install..

"Other problem, that I have is caused (sometimes) by the following sequence of events:
1. log in with some user
2. switch user
3. try to switch user again
Sometimes on the 3rd step system just locks. It does not respond to any keys Ctrl-Alt-Backspace, Ctrl-Alt-F1 or whatever."

I have a similar problem with Beryl running, when I choose Metacity as my Window Manager it works just fine.

same problem here, using a clean install of 7.04 and nvidia ti4200 with nvidia-glx drivers from repos.
when i select "switch user", either with compiz or metacity (it makes no difference), gdm resolution is scaled down to 640x480.
if i log in with another account, i am not able to change it.

i modified xorg.conf this way:

Section "Screen"
        Identifier "Default Screen"
        Device "nVidia Corporation NV25 [GeForce4 Ti 4200]"
        Monitor "SyncMaster"
        Defaultdepth 24
        SubSection "Display"
                Depth 24
                Modes "1024x768"
        EndSubSection
EndSection

but there was no difference.

the problem is still present on gutsy

Beyond this, if I try to change user then change the screen resolution, to what the other user was. The screen goes black. Dark, only way to save it is CTRL + ALT + BKSPC.

Kind of kills "multiuser" ability in Linux, don't ya think? Lol

Let me elaborate, I read over and realized it sounded bad.

If I am user A, and my Resolution is: 1152x864 @ 51 Hz and I goto switch to user B, the screen defaults at 1280x1024 @ 50 Hz.

If I try to set user B to 1152x864 @ 51 Hz, the screen refreshes (like it's going to set it), but never returns. The screen stays black.

I'm not sure the cause, seeing I don't know much of the code-wise aspect on how this whole switching works. It would be nice to be able to switch to the same Resolution. But you know, too bad so sad (as they say).

You can easily back-out to the login prompt via CTRL + ALT + BACKSPACE, but it's kind of annoying.

But I know, this will be fixed.
Linux's Manifesto: If it's broken, fix it.
Microsoft Manifesto: If it's broken, make crash recovery easier.

Adding on again, because I am an airhead.

I am using an old NVidia FX 5200 with an aging Pentium 4 Proc running at 2.80 gHz (underclocked to 2.79 somehow [don't ask; it's a dell])

Ain't nothing like a slice of underclock. ;-)

Thanks for reporting this issue with the binary drivers. Could you attach your /var/log/Xorg.0.log and the output from `sudo ddcprobe`?

The default user account is capable of higher resolutions, but on my secondary user account (with regular user privileges), I no longer have the ability to select higher resolutions. This is something that wasn't the case a few days ago.

For example, yesterday, I logged into my secondary account an had a high resolution. Today, before I logged in, I noticed the the login screen was huge. After logging in my resolution was at 640X480. When I go to change it, 640X480 is the only available option at Gnome > System > Preferences > Screen Resolution.

However, If I try to login using the account that was initially set up during installation, the resolution remains set to the higher resolution I expect.

It almost seems like a privileges issue; its like my secondary account no longer has the authority to select higher resolution options. Again, this was not the case yesterday.

I don't think this is video driver issue because if it were I'd think it have problems with resolution on all accounts. Perhaps it has to do with permission regarding restricted drivers. Maybe the super user has authority to use the restricted driver and the regular user account doesn't.

I'm using the restricted driver that Ubuntu 7.10 offered for the NVIDIA fx5200XT.

/var/log/Xorg.0.log:

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0.dfsg-12ubuntu8)
Current Operating System: Linux george-desktop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
Build Date: 29 September 2007
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Nov 8 17:52:26 2007
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "DELL P780"
(**) | |-->Device "nVidia Corporation NV34 [GeForce FX 5200]"
(**) |-->Input Device "Generic Keyboard"
(**) |-->Input Device "Configured Mouse"
(WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
 Entry deleted from font path.
(==) FontPath set to:
 /usr/share/fonts/X11/misc,
 /usr/share/fonts/X11/100dpi/:unscaled,
 /usr/share/fonts/X11/75dpi/:unscaled,
 /usr/share/fonts/X11/Type1,
 /usr/share/fonts/X11/100dpi,
 /usr/share/fonts/X11/75dpi,
 /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType
(==) RgbPath set to "/etc/X11/rgb"
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Loader magic: 0x81ea440
(II) Module ABI versions:
 X.Org ANSI C Emulation: 0.3
 X.Org Video Driver: 1.2
 X.Org XInput driver : 0.7
 X.Org Server Extension : 0.3
 X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules//libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
 compiled for 1.3.0, module version = 1.0.0
 ABI class: X.Org Video Driver, version 1.2
(++) using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 10de,00d1 card 1043,80c5 rev a4 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 10de,00d0 card 1043,80c5 rev f6 class 06,01,00 hdr 80
(II) PCI: 00:01:1: chip 10de,00d4 card 1043,80c5 rev a4 class 0c,05,00 hdr 80
(II) PCI: 00:02:0: chip 10de,00d7 card 1043,80c5 rev a5 class 0c,03,10 hdr 80
(II) PCI: 00:02:1: chip 10de,00d7 card 1043,80c5 rev a5 class 0c,03,10 hdr 80
(II) PCI: 00:02:2: chip 10de,00d8 card 1043,80c5 rev a2 class 0c,03,20 hdr 80
(II) PCI: 00:05:0: chip 10de,00d6 card 1043,80a7 rev a5 class 02,00,00 hdr 00
(II) PCI: 00:06:0: chip 10de,00da card 1043,8095 rev a2 class 04,01,00 hdr 00
(II) PCI: 00:08:0: chip 10de,00d5 card 1043,80c5 rev a5 class 01,01,8a hdr 00
(II) PCI: 00:0a:0: chip 10de,00dd card 0000,0000 rev a2 class 06,04,00 hdr 01
(II) PCI: 00:0b:0: chip 10de,00d2 card 0000,0000 rev a4 class 06,04,00 hdr 01
(II) PCI: 00:18:0: chip 1022,1100 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:1: chip 1022,1101 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:2: chip 1022,1102 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:18:3: chip 1022,1103 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 01:00:0...

sudo ddcprobe :
________________

vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: NV34 Board - p118dtn Chip Rev
memory: 131072kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x16
mode: 1024x768x256
mode: 1280x1024x16
mode: 1280x1024x256
mode: 320x200x64k
mode: 320x200x16m
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
edid:
edid: 1 3
id: ad18
eisa: ACRad18
serial: 50200409
manufacture: 2 2005
input: sync on green, analog signal.
screensize: 34 27
gamma: 2.200000
dpms: RGB, active off, suspend, standby
timing: 720x400@70 Hz (VGA 640x400, IBM)
timing: 720x400@88 Hz (XGA2)
timing: 640x480@60 Hz (VGA)
timing: 640x480@67 Hz (Mac II, Apple)
timing: 640x480@72 Hz (VESA)
timing: 640x480@75 Hz (VESA)
timing: 800x600@60 Hz (VESA)
timing: 800x600@72 Hz (VESA)
timing: 800x600@75 Hz (VESA)
timing: 832x624@75 Hz (Mac II)
timing: 1024x768@87 Hz Interlaced (8514A)
timing: 1024x768@70 Hz (VESA)
timing: 1024x768@75 Hz (VESA)
timing: 1280x1024@75 (VESA)
ctiming: 1280x1024@60
ctiming: 1152x864@75
dtiming: 1280x1024@70
monitorserial: ETL1809031
monitorname: Acer AL1714
monitorrange: 30-82, 50-75

Thanks for attaching logs.

Please let me know how which log files and Id be more than happy to post
them for you.

On Dec 13, 2007 6:54 PM, Henrik Nilsen Omma <email address hidden> wrote:

> Thanks for attaching logs.
>
> ** Changed in: xorg (Ubuntu)
> Importance: Undecided => Medium
> Status: New => Confirmed
>
> --
> Switch user causes screen resolution to change
> https://bugs.launchpad.net/bugs/44562
> You received this bug notification because you are a direct subscriber
> of the bug.
>

vbe: VESA 3.0 detected.
oem: NVidia
vendor: NVidia Corporation
product: NV25 Board Chip Rev
memory: 131072kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x16
mode: 1024x768x256
mode: 1280x1024x16
mode: 1280x1024x256
mode: 320x200x64k
mode: 320x200x16m
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
edid:
edid: 1 3
id: 66ca
eisa: NEC66ca
serial: 01010101
manufacture: 42 2006
input: analog signal.
screensize: 41 26
gamma: 2.200000
dpms: RGB, active off, suspend, standby
timing: 720x400@70 Hz (VGA 640x400, IBM)
timing: 720x400@88 Hz (XGA2)
timing: 640x480@60 Hz (VGA)
timing: 640x480@67 Hz (Mac II, Apple)
timing: 640x480@72 Hz (VESA)
timing: 640x480@75 Hz (VESA)
timing: 800x600@60 Hz (VESA)
timing: 800x600@75 Hz (VESA)
timing: 832x624@75 Hz (Mac II)
timing: 1024x768@87 Hz Interlaced (8514A)
timing: 1024x768@70 Hz (VESA)
timing: 1024x768@75 Hz (VESA)
timing: 1280x1024@75 (VESA)
ctiming: 1280x800@60
ctiming: 1280x1024@60
ctiming: 1440x1440@60
ctiming: 1440x1440@75
ctiming: 1152x864@75
dtiming: 1440x900@86
monitorrange: 31-81, 56-76
monitorname: 1940WCXM
monitorserial: 6X104314TA

and the Xorg.0.log file [attached]

Hi All,

This bug was reported a while ago and there hasn't been any recent activity. The Hardy Heron Alpha series was recently released. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . If you can, please verify if this bug still exists or not and report back your results. You should be able to test via the LiveCD. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ . Thanks.

This bug's fairly far out of date and has no recent testing activity, but the original issue is probably fixed. We've implemented a new Screen Resolution tool since the last comment, which includes xrandr-based per-user resolution setting that I *think* will address the crux of the issue here.

The issue with the gdm login screen having its own resolution is a separate issue and already reported elsewhere. (Also there's nothing we can easily do about it in the near term.) gdm has changed a bit since this original report, so maybe the current behavior is more acceptable (in my testing it seems ok on some systems, but still not quite right on others, but I think it might be a missing-EDID problem.)

Bug is still present in Hardy. Previous post is both inaccurate and does not address the issue. Please let me know if I can provide any logs or information to help troubleshoot this issue.

I have the same problem.
My system relevant info is:
-HP Laptop
-Intel Pentium 4 CPU 3.4 Ghz w/ NVIDIA chip
-Resolution 1680x1050, 50Hz
-Have upgraded to Heron from Gutsy (never tried to switch user while in Gutsy).

vbe: VESA 3.0 detected.
oem: NVIDIA
vendor: NVIDIA Corporation
product: NV36 Board - e183n Chip Rev
memory: 131072kb
mode: 640x400x256
mode: 640x480x256
mode: 800x600x16
mode: 800x600x256
mode: 1024x768x16
mode: 1024x768x256
mode: 1280x1024x16
mode: 1280x1024x256
mode: 320x200x64k
mode: 320x200x16m
mode: 640x480x64k
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
edid:
edidfail

Xorg log file attached...

Bump.

Any news on this? Have we isolated what setup causes this behavior? Is it NVIDIA, GDM, user switch applet? Can we expect any resolution to this issue? I will have a hard time justifying upgrading the rest of the machines in my shop if multi-user Hardy will not function properly.

- Jeff

JeffH: what happens if you type:
sudo nvidia-settings

and set the resolution from there (saving your settings).

Please restart the Xserver and see if you can still reproduce the problem.

Here is my xorg.conf before making the changes in nvidia-settings

# xorg.conf (X.Org X Window System server configuration file)
<--- comments removed --->

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "us"
EndSection

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "mouse"
 Option "CorePointer"
EndSection

Section "Device"
 Identifier "Configured Video Device"
 Driver "nvidia"
 Option "NoLogo" "True"
EndSection

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
 Defaultdepth 24
 Option "AddARGBGLXVisuals" "True"
EndSection

Section "ServerLayout"
 Identifier "Default Layout"
   Screen "Default Screen"
EndSection

Section "Module"
 Load "glx"
EndSection

Here it is after "sudo nvidia-settings" and saving the resolution. (merged xorf.conf flag was checked)

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (buildd@vernadsky) Tue Mar 4 20:24:34 UTC 2008

# xorg.conf (X.Org X Window System server configuration file)
<--- comments removed --->

Section "ServerLayout"
    Identifier "Default Layout"
    Screen 0 "Screen0" 0 0
EndSection

Section "Module"
    Load "glx"
EndSection

Section "ServerFlags"
    Option "Xinerama" "0"
EndSection

Section "InputDevice"
    Identifier "Generic Keyboard"
    Driver "kbd"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    Option "XkbLayout" "us"
EndSection

Section "InputDevice"
    Identifier "Configured Mouse"
    Driver "mouse"
    Option "CorePointer"
EndSection

Section "Monitor"
    Identifier "Configured Monitor"
EndSection

Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "IBM L190p"
    HorizSync 30.0 - 81.0
    VertRefresh 55.0 - 76.0
EndSection

Section "Device"
    Identifier "Configured Video Device"
    Driver "nvidia"
    Option "NoLogo" "True"
EndSection

Section "Device"
    Identifier "Videocard0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce4 Ti 4600"
EndSection

Section "Screen"
    Identifier "Default Screen"
    Device "Configured Video Device"
    Monitor "Configured Monitor"
    DefaultDepth 24
    Option "AddARGBGLXVisuals" "True"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device "Videocard0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "TwinView" "0"
    Option "metamodes" "1280x1024_72 +0+0; nvidia-auto-select +0+0"
EndSection

I will post results after I restart X server....

Still no success. I noticed there were duplicate sections in my xorg.conf file so I cleaned it up some and restarted my xserver. Still nothing. I get 640x480 when trying to switch users.

Any other ideas? Should I assume this bug is really not all that pervasive and only limited to a very small subset of users or do very few Ubuntu users have multi-user setups? There seems to be so little activity on this issue.

- Jeff

Current xorg.conf file:

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (buildd@vernadsky) Tue Mar 4 20:24:34 UTC 2008

# xorg.conf (X.Org X Window System server configuration file)
<--- Comments removed --->

Section "Module"
    Load "glx"
EndSection

Section "ServerFlags"
    Option "Xinerama" "0"
EndSection

Section "InputDevice"
    Identifier "Generic Keyboard"
    Driver "kbd"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    Option "XkbLayout" "us"
EndSection

Section "InputDevice"
    Identifier "Configured Mouse"
    Driver "mouse"
    Option "CorePointer"
EndSection

Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "IBM L190p"
    HorizSync 30.0 - 81.0
    VertRefresh 55.0 - 76.0
EndSection

Section "Device"
    Identifier "Videocard0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce4 Ti 4600"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device "Videocard0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "TwinView" "0"
    Option "metamodes" "1280x1024_72 +0+0; nvidia-auto-select +0+0"
    Option "AddARGBGLXVisuals" "True"
EndSection

Section "ServerLayout"
    Identifier "Default Layout"
    Screen "Screen0"
EndSection

To JeffH:
I think it's the latter, most users do not have a multiple-user ubuntu install. One of the problems, I had noted, when I changed the resolution back from 640x480 to 1024x768...the screen went black.

Let me boot into my Ubuntu partition and I'll respond once more.

[Unnecessary to have this bug opened against both l-r-m and xorg, just l-r-m is sufficient.]

It does not appear that it is being worked in any case - so why does it
matter?

Bryce Harrington wrote:
> [Unnecessary to have this bug opened against both l-r-m and xorg, just
> l-r-m is sufficient.]
>
> ** Changed in: xorg (Ubuntu)
> Status: New => Invalid
>
> ** Changed in: linux-restricted-modules-2.6.24 (Ubuntu)
> Status: Confirmed => Triaged
>
>

Bryce,

You have made a mockery of this bug reporting system by first trying to close this bug without resolution (only an assumption of resolution) and now determining which package the bug should go against without proper triage or problem determination.

In any case it probably does not matter as this issue either does not effect that large of a population and/or does not warrant attention from the Ubuntu community. Unfortunately this issue was a deal breaker for me and I have had to move on away from Hardy.

If in the future you need my assistance to work on this bug, please let me know. I am sure I can reproduce it on my system(s) again.

- Jeff

Thank you for your comment. To maintain a respectful atmosphere, please follow the code of conduct - http://www.ubuntu.com/community/conduct/ . Bug reports are handled by humans, the majority of whom are working on a vast number of bugs, and failure to follow the code of conduct can reduce the likelihood your bug will receive any further attention.

I have the same problem as Jeff, also on a Nvidia Ti4xxx card (as reported by more people here) ... coincidence?

nvidia-settings runs fine. system boots, resolution is as is set (1680x1050). Login, resolution remains at 1680x1050. But after user-switching resolution drops to 640x480, though the desktop renderer still thinks its rendering at 1680x1050, because I can see only the top-left part of the login-screen.

- Turning off compiz does not seem to help the problem.
- No errors added to .xsession.errors on trying to switch
- Nothing added to dmesg on trying to switch
- '/var/log/Xorg.0.log' adds '(II) NVIDIA(0): Setting mode "nvidia-auto-select+0+0"'

So I tried changing the line
 Option "metamodes" "nvidia-auto-select +0+0; 1680x1050_60 +0+0"
in '/etc/X11/xorg.conf' to
 Option "metamodes" "1680x1050_60 +0+0; nvidia-auto-select +0+0"

But, allas, to no avail. This results in the login screen *always* dropping to 640x480 (even on restarting gdm).

oh ... and be nice to eachother! ;)

I too have a ti 4200, and still experiencing the drops in resolution..

BTW - I never found a fix to this issue and got tired of the very slow
defect resolution process. Ended up upgrading video cards and
everything works fine.

On 8/3/08, nixon <email address hidden> wrote:
> I too have a ti 4200, and still experiencing the drops in resolution..
>
> --
> [nvidia] Switch user causes screen resolution to change
> https://bugs.launchpad.net/bugs/44562
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Hello there, with must recent hardy updates (as of August 7,2008) this problem is fixed for me.

This problem is an issue for me on Intrepid. I am running:
* amd64
* fglrx 8.57.2 (date Jan 14 2009)
* ati 9800 running at 1920x1200@60Hz
* kernel 2.6.27-14-generic

When this issue occurs I see
/var/log/Xorg.0.log
* (II) AIGLX: Resuming AIGLX client after VT switch
* (EE) fglrx(0): Cannot get requested mode 0 x 0 @ 0.000000
* (EE) fglrx(0): Falling back to last mode in modelist 320 x 200 @ 60.000000

This suggests that the wrong mode is being passed during user switch. I'm not yet sure where the issue lies. Fooie.

I'm currently seeing this, in ubuntu 11.04, with latest updates.

Symptoms for my setup are:

* Works fine for single display.

* Switching user, I get a new display that LOOKS like 640x480; not sure of the exact res.

* The X server doesn't seem to be AWARE of the new hardware res, as the login window is only partially on-screen, and things looks stretched on my 1920x1080 monitor (as if it's not aware of the 4:3 aspect either).

* Switching to another user/display and back to the new one fixes it, apparantly by ACTUALLY setting the resolution that the x server THOUGHT it already had.