Jaunty: preload breaks automatic login

Bug #356767 reported by Bernhard
10
Affects Status Importance Assigned to Milestone
gdm (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs
preload (Ubuntu)
New
Undecided
Unassigned
pulseaudio (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Simple bug description: if I have the "preload" package installed then automatic login does not work anymore, i.e. even if automatic login is enabled, it keeps sending me back to the gdm login screen.

This should be a bug, shouldn't it? I'm pretty sure preload and automatic login were compatible in intrepid.

Revision history for this message
Bernhard (b.a.koenig) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your bug report, could you look in /var/log/auth, messages, syslog for errors? could you add your configuration to the bug? what did you change to get it not working?

Changed in gdm (Ubuntu):
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

the description is not really clear, it seems that gdm start a session but this one crash, could you get the user .xsession-errors before starting the new sesison?

Revision history for this message
Bernhard (b.a.koenig) wrote :

I just checked again and it says

* (red star) Pulseaudio configured by user sessions

I don't think I did anything to the automatic login, I think it broke with one of the jaunty updates. I will attach my /var/log/auth.log.0, but it doesn't contain that particular pulseaudio error message.

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

what says that? could you get the .xsession-errors as requested too?

Revision history for this message
Bernhard (b.a.koenig) wrote :

Sorry, I forgot to attach the .xsession-errors, but actually that's not where this pulseaudio error message is in either. I don't know in which log it is but it was like this:

Ubuntu boots normally, then it tries to start X, but something goes wrong so I get a number of starred messages and one star in there is red and that one says:
pulseaudio configured for per-user session (that's the exact wording, my earlier one was incorrect, sorry).

Similar to http://ubuntuforums.org/showthread.php?p=6908131 (see post #3 in that thread).

description: updated
Bernhard (b.a.koenig)
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

could you take a screenshot showing the error?

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

when did you get this log? after the next login? it seems to have no error

Revision history for this message
Daniel T Chen (crimsun) wrote :

The message originates in the initscript (/etc/init.d/pulseaudio), which is only relevant for system-wide daemon invocations. I added that message explicitly so people would realise that the initscript is not the default/canonical method of using PulseAudio.

It is a red herring in your symptom and is utterly orthogonal to the login issue.

Changed in pulseaudio (Ubuntu):
status: New → Invalid
Revision history for this message
Bernhard (b.a.koenig) wrote :

If Daniel is right, then there must be some other reason why it didn't log me in automatically. How can I find a log that tells me why it didn't log me in?
Please note that after the failure of automatic login, I can log me into the gdm screen without any problems.

Revision history for this message
Bernhard (b.a.koenig) wrote :

I think the problem must be somewhere in here....

Apr 7 13:39:37 amilo dbus-daemon: Rejected send message, 4 matched rules; type="error", sender=":1.12" (uid=0 pid=2604 comm="/sbin/wpa_supplicant -u -f /var/log/wpa_supplicant") interface="(unset)" member="(unset)" error name="fi.epitest.hostap.WPASupplicant.InvalidInterface" requested_reply=0 destination=":1.9" (uid=0 pid=2586 comm="/usr/sbin/NetworkManager --pid-file /var/run/Netwo"))
Apr 7 13:40:01 amilo CRON[2936]: pam_unix(cron:session): session opened for user root by (uid=0)
Apr 7 13:40:05 amilo CRON[2936]: pam_unix(cron:session): session closed for user root
Apr 7 13:40:08 amilo gdm[2909]: pam_nologin(gdm:auth): cannot determine username
Apr 7 13:40:08 amilo gdm[2909]: pam_unix(gdm-autologin:session): session opened for user bkoenig by (uid=0)
Apr 7 13:40:08 amilo gdm[2909]: pam_ck_connector(gdm-autologin:session): nox11 mode, ignoring PAM_TTY :0

Revision history for this message
Bernhard (b.a.koenig) wrote :

13:40 was exactly the time I booted. I'm not an expert but it looks like it opens the session for root, then closes it for root (is that normal?) and then it says "cannot determine username", even though that username is clearly specified in my "Login Window" "Security" tab.

Revision history for this message
Bernhard (b.a.koenig) wrote :

No sorry! That's another red herring, it says "cannot determine username because I didn't type any and then it logs me in as a timed login....

Revision history for this message
Bernhard (b.a.koenig) wrote :

If anything, then the problem is in here:

Apr 7 13:53:56 amilo dbus-daemon: Rejected send message, 4 matched rules; type="error", sender=":1.12" (uid=0 pid=2599 comm="/sbin/wpa_supplicant -u -f /var/log/wpa_supplicant") interface="(unset)" member="(unset)" error name="fi.epitest.hostap.WPASupplicant.InvalidInterface" requested_reply=0 destination=":1.9" (uid=0 pid=2581 comm="/usr/sbin/NetworkManager --pid-file /var/run/Netwo"))

Bernhard (b.a.koenig)
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug has still no buggy .xsession-error nor useful information

Revision history for this message
Bernhard (b.a.koenig) wrote :

@Sebastien: well, I provided you with .xsession-error, I gave you the auth.log output from the particular time of the login. Fact is that automatic login is currently not working in jaunty. Tell me what other kind of info you need, I'm happy to help.

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

how did you get the .xsession-errors? as said before it has no error, if you loged in before getting it the new version will have overwritten the buggy one

Revision history for this message
Bernhard (b.a.koenig) wrote :

I really don't know how to give you what you want: if I have this bug (i.e. automatic login fails and sends me to gdm screen) I can go straight to a shell from the gdm screen but then I still have the old .xsession-errors from the previous session. So when automatic login fails, it never creates a new .xsession-errors. Then I log in via gdm screen and you get an .xsession-errors file without memory of the login failure. The only record of the login failure I can give you is the one I pasted above, what about this "InvalidInterface" business? Are you saying that this is completely normal? As I said, it's the only record I can give you, unless you can point me to some other log files.

Apr 7 20:04:29 amilo dbus-daemon: Rejected send message, 4 matched rules; type=
"error", sender=":1.12" (uid=0 pid=2609 comm="/sbin/wpa_supplicant -u -f /var/lo
g/wpa_supplicant") interface="(unset)" member="(unset)" error name="fi.epitest.h
ostap.WPASupplicant.InvalidInterface" requested_reply=0 destination=":1.9" (uid=
0 pid=2591 comm="/usr/sbin/NetworkManager --pid-file /var/run/Netwo"))
Apr 7 20:05:04 amilo login[2891]: pam_unix(login:session): session opened for u
ser bkoenig by LOGIN(uid=0)
Apr 7 20:05:58 amilo gdm[2915]: pam_unix(gdm:session): session opened for user
bkoenig by (uid=0)
Apr 7 20:05:58 amilo gdm[2915]: pam_ck_connector(gdm:session): nox11 mode, igno
ring PAM_TTY :0

Revision history for this message
Bernhard (b.a.koenig) wrote :

OK, I finally figured out the problem. It's the preload package, if preload is installed then automatic login does not work. I will update the description.

description: updated
tags: added: automatic login preload
removed: apport-bug i386
summary: - Jaunty: automatic login does not work
+ Jaunty: preload breaks automatic login
Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue is not a gdm bug

Changed in gdm (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for figuring that, next time reassign the task rather than opening a new one, now gdm subscribers will still get the comments on this bug since there is a still a gdm task listed

Revision history for this message
Bernhard (b.a.koenig) wrote :

OK, sorry about that. Even though gdm is not buggy as such, preload worked for the intrepid gdm and not for jaunty. So the problem is (imho) that preload is not configured correctly for the new jaunty gdm.

Revision history for this message
YannUbuntu (yannubuntu) wrote :

Dear all,
I am under Jaunty (upgraded from Intrepid), I have preload and prelink installed, and my automatic login works well.
Don't hesitate to ask me for more information if needed.

Revision history for this message
Bernhard (b.a.koenig) wrote :

Just tested and the problem still persists for me in jaunty. Prelink is no problem but preload breaks the automatic login.

Revision history for this message
satfan39 (pik-scarlet) wrote :

I had the same problem after migrating from ubuntu 8.10 to ubuntu 9.04 ( gdm ). I solved the problem by changing the priorites of /etc/init.d/gdm at boot using the update-rc.d command

Initial config

   /etc/rc0.d/K01gdm
   /etc/rc1.d/K01gdm
   /etc/rc2.d/S30gdm
   /etc/rc3.d/S30gdm
   /etc/rc4.d/S30gdm
   /etc/rc5.d/S30gdm
   /etc/rc6.d/K01gdm

Updated config

   /etc/rc0.d/K01gdm ( no change )
   /etc/rc1.d/K01gdm ( no change )
   /etc/rc2.d/S80gdm ( renamed the file )
   /etc/rc3.d/S80gdm ( renamed the file )
   /etc/rc4.d/S80gdm ( renamed the file )
   /etc/rc5.d/S30gdm ( renamed the file )
   /etc/rc6.d/K01gdm ( no change )

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.