Logout a session causes X-Window changes from VT7 to VT9

Bug #172444 reported by Ricardo Pérez López
10
Affects Status Importance Assigned to Milestone
gdm (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: gdm

Steps to reproduce:

0. The GDM login screen appears. Ctrl-Alt-F1 goes you into a console terminal. With Ctrl-Alt-F7 you go back to X-Window.
1. Log into a GNOME session.
2. Log out the session, to go back to GDM.
3. The GDM login screen appears again.

Expected behavior:

The X-Window remains in virtual terminal #7 (Ctrl-Alt-F7)

Actual behavior:

The X-Window changes to virtual terminal #9 (Ctrl-Alt-F9)

Revision history for this message
Siegfried Gevatter (rainct) wrote :

I can confirm this with 1 computer.

Changed in gdm:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Nicolas M (nicolas-martin-gmail) wrote :

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 ?

Revision history for this message
Giorgio Vazzana (mywing) wrote :

When I upgraded from Feisty to Gutsy two days ago, I had the same problem. Looking at .xsession-errors I found the following error:

1198440598.912730 Session manager: gsm-remote-desktop.c:107: remote desktop server died, restarting
1198440598.916107 Session manager: gsm-remote-desktop.c:107: remote desktop server died, restarting
1198440608.837906 Session manager: gsm-remote-desktop.c:130: activation of OAFIID:GNOME_RemoteDesktopServer failed: System exception: IDL:omg.org/CORBA/COMM_FAILURE:1.0

This led me to think it was something related with remote desktop. So I fixed the problem by disabling it (the server name is "vino-server"). To do so, run from a terminal "vino-preferences" and disable remote desktop. Now reboot and it should work. This seems to fix bug #157622 too. I hope this helps.

P.S.: I think there might be a bug in vino or in the gnome-session package (since gsm-remote-desktop.c belongs to that package), so this is just a quick fix.

Revision history for this message
Nicolas M (nicolas-martin-gmail) wrote :

Just tried your tip but it does not work for me.

The remote server was already stopped.

Enabling or disabling it has no effect, the X server always restarts at logout, and always uses VT9 instead of VT7.

Revision history for this message
Giorgio Vazzana (mywing) wrote :

Oh, sorry Nicolas, you're right. I just checked again and I still have the problem about VT9, on two different machines (amd64 and i386) running gutsy. But I've noticed that, even if Xorg uses VT9 from the second login on, it works fine for me.

Anyway, that procedure resolved the problem with the remote desktop, so I think I should file a bug report on vino.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could somebody try if that's still an issue in karmic?

Changed in gdm (Ubuntu):
status: Confirmed → Incomplete
summary: - [Gutsy] Logout a session causes X-Window changes from VT7 to VT9
+ Logout a session causes X-Window changes from VT7 to VT9
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in gdm (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.