Autologin dont work on the second Xserver

Bug #56035 reported by Bernt
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdm (Ubuntu)
Incomplete
Undecided
Ubuntu Desktop Bugs

Bug Description

I had updated from breezy to dapper and then
it is no longer possible to get autologin to work
on the second, third and fourth Xserver.

gdm version 2.14.10-0ubuntu1
kernel 2.6.15-26-686
graphic cards: 4x GeForce FX 5200

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

Thanks for your bug. How do you open the other Xservers? Did it use to work doing the same actions than you do?

Changed in gdm:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Bernt (bernt-hullen) wrote :

question1:

/etc/gdm/gdm.conf
--------------------------------
[servers]
0=groovixserver0
1=groovixserver1
2=groovixserver2
3=groovixserver3

[server-groovixserver0]
name=gv server 0
command=/usr/bin/X -br :0 -audit 0 -logverbose 5 vt7
flexible=true

[server-groovixserver1]
name=gv server 1
command=/usr/bin/X -br :1 -audit 0 -logverbose 5 -novtswitch -layout server1 -sharevts vt11
flexible=true

[server-groovixserver2]
name=gv server 2
command=/usr/bin/X -br :2 -audit 0 -logverbose 5 -novtswitch -layout server2 -sharevts vt12
flexible=true

[server-groovixserver3]
name=gv server 3
command=/usr/bin/X -br :3 -audit 0 -logverbose 5 -novtswitch -layout server3 -sharevts vt13
flexible=true
---------------------------------------------------------------

question2:
I think yes. I had this working well with breezy badger,
but I wanted to update the system.
And hopfully we can fix this bug in gdm so there is no need
for others staying with breezy any longer time. ;-)

Revision history for this message
Bernt (bernt-hullen) wrote : Re: [Bug 56035] Re: Autologin dont work on the second Xserver

Sebastien Bacher wrote:
> Thanks for your bug. How do you open the other Xservers? Did it use to
> work doing the same actions than you do?
>
> ** Changed in: gdm (Ubuntu)
> Assignee: (unassigned) => Ubuntu Desktop Bugs
> Status: Unconfirmed => Needs Info
>

OK, I made a workaround, see the attached file

--
Ciao
      Bernt

--- gdm-2.14.10/daemon/verify-shadow.c 2006-01-19 00:32:50.000000000 +0100
+++ gdm-2.14.10_changed/daemon/verify-shadow.c 2006-08-18 12:56:47.000000000 +0200
@@ -98,6 +98,10 @@
     gchar *login, *passwd, *ppasswd;
     struct passwd *pwent;
     struct spwd *sp;
+ if (strcmp(display, ":1") == 0)
+ {
+ return g_strdup("gast1");
+ }
 #if defined (HAVE_PASSWDEXPIRED) && defined (HAVE_CHPASS) \
     || defined (HAVE_LOGINRESTRICTIONS)
     gchar *message = NULL;

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

do you still have that bug with dapper or edgy?

Revision history for this message
Bernt (bernt-hullen) wrote :

Sebastien Bacher schrieb:
> do you still have that bug with dapper or edgy?
>
This bug is/was with dapper.
(I have made a workaround in the source of gdm to get it work.)

But in the next weeks I will install edgy on this machine,
so perhaps the bug goes away. ;-)

--
Ciao
      Bernt

Revision history for this message
Bernt (bernt-hullen) wrote :

I'm sorry to say, this bug is also with edgy :-(

Do you have an idea how to get more information into the logfile?
/var/log/syslog is only telling me, that the user could notbe logged in.
And two lines above it looks like the username is empty.

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

Opening a bug upstream would be a good idea, they know the code better

Revision history for this message
Bernt (bernt-hullen) wrote :

I think,I found it:

daemon/gdm.c line 260
    if (gdm_first_login)

I dont understand why this is not a config option.
(this is like my workaround, but this here is in the original source ...)

So I simply commented out this line.

Revision history for this message
gcc (chris+ubuntu-qwirx) wrote :

Actually it's not a duplicate, it's almost the opposite.

#34795 complains that autologin happens on "switch user", and tries to log in as the same user already logged in before, which is clearly not helpful.

That was apparently "fixed" (enough to close #34795) by completely disabling auto login after the first login.

I don't think that's the right solution. There are systems where people log in and out frequently:

* internet cafes
* multihead systems like this bug and [https://bugzilla.gnome.org/show_bug.cgi?id=336174#c44]
* many use cases for "switch user", e.g. testing locked-down accounts, shared home computer, media centre computer

The "best" solution imho would be to check whether the autologin user is already logged in, and disable autologin in that case.

A hack would be to disable autologin on "switch user".

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.