Yes, as noted in the bug report. The trigger is user 1 logging out
back to gdm while user 2 still has a session going. When user 2 logs
in through gdm back to their running session.
This has happened reliably for me, 100% of the time so far after a
small number of attempts. My auth.log corresponds to Mark's findings
as follows. Also, using Ctrl+Alt+F-keys to get back to the gdm prompt
stops the repeat. A message is briefly present indicating exactly what
the auth.log is reporting, ie that the username or password is
invalid. Perhaps this is a simple as an enter key being effectively
held down in the X session gdm is using?
auth.log output from around the time the login attention sound starts:
May 16 14:16:23 lillian dbus-daemon: Rejected send message, 1 matched
rules; type="method_call", sender=":1.105" (uid=1002 pid=10668
comm="/usr/lib/indicator-applet/indicator-applet --oaf-a")
interface="org.freedesktop.DBus.Properties" member="Get" error
name="(unset)" requested_reply=0 destination=":1.124" (uid=0 pid=2961
comm="/usr/sbin/gdm "))
May 16 14:16:31 lillian dbus-daemon: Rejected send message, 1 matched
rules; type="method_call", sender=":1.105" (uid=1002 pid=10668
comm="/usr/lib/indicator-applet/indicator-applet --oaf-a")
interface="org.freedesktop.DBus.Properties" member="Get" error
name="(unset)" requested_reply=0 destination=":1.125" (uid=0 pid=2961
comm="/usr/sbin/gdm "))
May 16 14:16:32 lillian gdm[2961]: pam_unix(gdm:auth): check pass; user unknown
May 16 14:16:32 lillian gdm[2961]: pam_unix(gdm:auth): authentication
failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=
May 16 14:16:34 lillian gdm[2961]: pam_unix(gdm:auth): check pass; user unknown
May 16 14:16:34 lillian gdm[2961]: pam_unix(gdm:auth): authentication
failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=
May 16 14:16:36 lillian gdm[2961]: pam_unix(gdm:auth): check pass; user unknown
May 16 14:16:36 lillian gdm[2961]: pam_unix(gdm:auth): authentication
failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=
May 16 14:16:38 lillian gdm[2961]: pam_unix(gdm:auth): check pass; user unknown
May 16 14:16:38 lillian gdm[2961]: pam_unix(gdm:auth): authentication
failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=
May 16 14:16:40 lillian gdm[2961]: pam_unix(gdm:auth): check pass; user unknown
May 16 14:16:40 lillian gdm[2961]: pam_unix(gdm:auth): authentication
failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=
2009/5/14 Sebastien Bacher <email address hidden>:
> do you have a reliable way to trigger the issue?
>
> --
> Login attention sound on continuous repeat after user switch
> https://bugs.launchpad.net/bugs/373961
> You received this bug notification because you are a direct subscriber
> of the bug.
>
Yes, as noted in the bug report. The trigger is user 1 logging out
back to gdm while user 2 still has a session going. When user 2 logs
in through gdm back to their running session.
This has happened reliably for me, 100% of the time so far after a
small number of attempts. My auth.log corresponds to Mark's findings
as follows. Also, using Ctrl+Alt+F-keys to get back to the gdm prompt
stops the repeat. A message is briefly present indicating exactly what
the auth.log is reporting, ie that the username or password is
invalid. Perhaps this is a simple as an enter key being effectively
held down in the X session gdm is using?
auth.log output from around the time the login attention sound starts: usr/lib/ indicator- applet/ indicator- applet --oaf-a") "org.freedeskto p.DBus. Properties" member="Get" error ":1.124" (uid=0 pid=2961 usr/lib/ indicator- applet/ indicator- applet --oaf-a") "org.freedeskto p.DBus. Properties" member="Get" error ":1.125" (uid=0 pid=2961
May 16 14:16:23 lillian dbus-daemon: Rejected send message, 1 matched
rules; type="method_call", sender=":1.105" (uid=1002 pid=10668
comm="/
interface=
name="(unset)" requested_reply=0 destination=
comm="/usr/sbin/gdm "))
May 16 14:16:31 lillian dbus-daemon: Rejected send message, 1 matched
rules; type="method_call", sender=":1.105" (uid=1002 pid=10668
comm="/
interface=
name="(unset)" requested_reply=0 destination=
comm="/usr/sbin/gdm "))
May 16 14:16:32 lillian gdm[2961]: pam_unix(gdm:auth): check pass; user unknown
May 16 14:16:32 lillian gdm[2961]: pam_unix(gdm:auth): authentication
failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=
May 16 14:16:34 lillian gdm[2961]: pam_unix(gdm:auth): check pass; user unknown
May 16 14:16:34 lillian gdm[2961]: pam_unix(gdm:auth): authentication
failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=
May 16 14:16:36 lillian gdm[2961]: pam_unix(gdm:auth): check pass; user unknown
May 16 14:16:36 lillian gdm[2961]: pam_unix(gdm:auth): authentication
failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=
May 16 14:16:38 lillian gdm[2961]: pam_unix(gdm:auth): check pass; user unknown
May 16 14:16:38 lillian gdm[2961]: pam_unix(gdm:auth): authentication
failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=
May 16 14:16:40 lillian gdm[2961]: pam_unix(gdm:auth): check pass; user unknown
May 16 14:16:40 lillian gdm[2961]: pam_unix(gdm:auth): authentication
failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=
2009/5/14 Sebastien Bacher <email address hidden>: /bugs.launchpad .net/bugs/ 373961
> do you have a reliable way to trigger the issue?
>
> --
> Login attention sound on continuous repeat after user switch
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>