I Confirm the bug, as I just migrated from Feisty to Gutsy a couple of days ago.
Logout from the Gnome session causes:
- gdm to restart (Nvidia logo reappears, lots of display flickering)
- the new X windows session to be attached to VT9 instead of initial VT7.
Note: other login/logout will still cause gdm to restart, but the VT stays stuck to VT9.
In /var/log/Xorg.0.log, I can read this:
-----------------------------------------
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
.../... then later in file:
(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 9
(II) PCI: PCI scan (all values are in hex)
.../... then rest of the file.
-----------------------------------------
So: Would it be a command line script somewhere that requests use of VT9 instead of VT7 ?
I Confirm the bug, as I just migrated from Feisty to Gutsy a couple of days ago.
Logout from the Gnome session causes:
- gdm to restart (Nvidia logo reappears, lots of display flickering)
- the new X windows session to be attached to VT9 instead of initial VT7.
Note: other login/logout will still cause gdm to restart, but the VT stays stuck to VT9.
In /var/log/ Xorg.0. log, I can read this: ------- ------- ------- ------- ------
-------
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
.../... then later in file:
(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 9
(II) PCI: PCI scan (all values are in hex)
.../... then rest of the file. ------- ------- ------- ------- ------
-------
So: Would it be a command line script somewhere that requests use of VT9 instead of VT7 ?