Keyboard selection of user on login window

Since using Mountain Lion, when all users are logged out and the Mac goes to sleep, on wake up, I am no more able to select the user on the login window using the (bluetooth) keyboard.
However, if I click with the mouse on one of the users icon, selection using keyboard (left or right arrow) works again.
Any ideas or solutions to this problem which is not present on my other machines nor was present on the iMac under Lion.
Thanks for any input.

Similar Messages

Delay network users in login window

Halo,
i have 10.5.6 server OD installation. In preferences for quest computer i setup show network users. When i can login from Leopard client i must wait 1 - 2 min for list network users. In Tiger client all is OK. I use the same settings for both clients.
I try to solve this (turn off IPv6, Bonjoor ..) nothing help.
But everything looks fine. When i can not see users in login window i click to Other.. i fill user name and pass a client normally log in to server.
Please do you have any idea where is problem.
Many thanks
Message was edited by: Jiri10

Hi
You can do this with an MCX applied at hardware level. Once you've joined your workstations to OD launch WorkGroup Manager and create a Computer Group(s). Click on the Members tab and use the diaresis (. . .) button to 'add' those joined workstations. Click on the Preferences icon, click on Login, select Window, click Always and the rest if fairly obvious from there.
Not absolutely necessary but it's a good idea to restart the client workstations afterwards as sometimes hardware MCX does not 'take' immediately. You'll know soon enough.
Tony

Keyboard doesn't respond at login window... works in Single User mode

I have a G4 xServe (server 10.3) that won't accept keyboard input at login window, but the same keyboard, usb port, works fine when I'm booted into Single User Mode.
Booting into Single User mode, something interesting gets posted during boot:
"AppleCPUThermo got unsupported command"
Any thoughts?

Did you find a resolution to this issue? After I installed the latest security update to OSX Server 10.4.8 I am now experiencing the same problem. Any insight would be greatly appreciated.

Selective users in login window

Hi all,
When managing a computer login window using the Workgroup manager, I can setup each computer either to show or not to show all users names and pictures.
Is there a way to selectively show some users and leave the other... option to the rest?
Thanks,
Ziv

Hi
You can do this with an MCX applied at hardware level. Once you've joined your workstations to OD launch WorkGroup Manager and create a Computer Group(s). Click on the Members tab and use the diaresis (. . .) button to 'add' those joined workstations. Click on the Preferences icon, click on Login, select Window, click Always and the rest if fairly obvious from there.
Not absolutely necessary but it's a good idea to restart the client workstations afterwards as sometimes hardware MCX does not 'take' immediately. You'll know soon enough.
Tony

Store last user on "Login Window: Name and Password"

I have set my login window to display as "Name and password"
Is there any way to make a certain user always appear in the Username box - much like you can do on Windows? Basically, I want to only have to enter in a password and not the username everytime.
Thanks in advance.

I think the only way to do that is to set your login window to show "list of users" instead of "name and password". Why don't you do that?

Mysterious "Other" User at Login Window????

Hi folks,
Ive just updated my old iMac G3 to Tiger 10.4.3 (from OS9) and connected it to my Powermac G5 (10.4.3) via a network cable. The thing is for some reason when the iMac boots up the login window shows the correct user (my wife) but also shows another icon underneath called "other" I recognize the icon (it's the shilhouetted guy with the blue background, Admin?) but my wife's is the only account on the machine. If i type her details in the "other" user it logs in as her the same as if i login with her icon? What is this and how can i get rid of it?
Thanks.

I seem to remember this "Other" as an option in Jaguar or Panther, but I can't seem to find it in Tiger. Have you enabled the root user? That's usually what this "Other" user was for — it presented the Name and Password fields instead of a list of users so you could type in "root" and the root password to log in as root. (If you don't know what root is, don't worry about it.)
To get rid of it, I would try switching some of the Login Options in the Accounts preference pane. Specifically, pick the option that says Display login window as Name and password instead of List of users. Log out, see if that sticks, log back in, switch back to List of users. Log out, see if it's fixed. That's definitely the first thing I would try.

Unhide user in login window?

If I create a new user on the command line, e.g.
dscl . create /Users/harri
dscl . create /Users/harri UserShell /bin/bash
dscl . create /Users/harri RealName "Harri"
dscl . create /Users/harri UniqueID 1000
dscl . create /Users/harri PrimaryGroupID 1000
dscl . create /Users/harri NFSHomeDirectory /Users/harri
dscl . passwd /Users/harri 123
dscl . append /Groups/admin GroupMembership harri
then the account is not shown on the login window. How comes? How can I tell Mavericks to show?

"List of users" is already set, of course. The other users are shown. Only the new account is missing.
NFS is not involved. AFAICS the "NFSHomeDirectory" ist just an attribute name pointing to $HOME of the user. Its the same as the 6th parameter in a passwd entry of a real Unix system.
Just to be sure: The new user can login using the "Others" option. $HOME is set accordingly.

Missing user from login window at startup

I upgraded to Yosemite a few weeks ago and have had a problem with a user I migrated from Mavericks. The user won't show up in the login window at startup but will once I login with a different user and then logout back to the login window. How can I get my migrated user to show up in the login window at startup?
I did a clean install of Yosemite and then used Migration Assistant to move over my old user from a Mavericks install. My original plan was to import my old user's Document and other data directories and copy them over to a new user's home directory so that my data would be available but I'd clean out old application settings by not moving that as well. Due to how Migration Assistant worked and my disinterest in diving into the details to make this work, I ended up using the migrated account instead.
Here's the problem, the migrated account was using a different home directory path than I preferred ("user_migrated" rather than "user"). I modified pertinent settings in the advanced configuration form available in the Users & Groups preference pane. Everything appears to work fine, except this user does not show up in the login window when I first boot up the machine. If I login to another user, then log out, my migrated user appears and I'm able to login.
I've looked around in Users & Groups and checked settings, but I'm not seeing any difference between my migrated user's settings and other user's (who does show up in the login window) settings.
If anyone has any suggestions, please share!

Found the answer in a post from 2012:
User accounts not appearing in login window
The problem was the migrated user was not authorized to unlock the disk. This is easily fixed by opening up FileVault settings and enabling the missing users.

Clicking on my user on login window occasionally causes display errors. Graphics chip dying?

Hi. Occasionally (but happening more and more often), when I boot my computer and it goes to the login window, when I click on my username, suddenly the screen corrupts a bit around the username and while I can move my mouse, nothing is clickable anymore. The corrupt pattern always differs, and the only way to fix it for me is to force turn off the computer. When I reboot it, it works normally, and I can type my password to login. However today, I received the problem, and when I rebooted it, the problem happened again. I didn't want to shut it down this time to look for another solution so I just shut the lid, put the computer to sleep, and reopened it to see if the problem was fixed, but to no avail, the glitches (mostly random patches of black and white dispersed with small sprinkled pixels of varying colors) this time filled the entire screen.
I think it may relate to the GPU, and in the case of the GPU, I can recall an event where I was using Final Cut to export something while I was also exporting something in Premiere, and suddenly the computer just stopped moving, and closing the lid didn't stop the harddisk or stop the fans (probably overtaxed with heat). After that, I've been noticing this happening.
My temporary solution with this issue is to change the graphics card I am using.
My MacBook Pro has the "better battery life" and "better performance" option, in which the 9400M is for "better" and the 9600M GT (or whatever) is for "performance", and requires me to log out and sign back in for any changes. For a while now, I have been using the "better performance" option since I started using final cut more often. Since it requires me to log out and sign back in in order to change, I feel that the 9600M GT which I might have possibly damaged could have something to do with it, since it seems that when I click on my username, the internal preference files change the graphics preference to "better performance", and that change may cause the glitches.
Did I toast my 9600? How should I resolve this issue? I feel if I turn this computer on again it will never go back to it's normal mode.
edit: read other topics, in case anyone brings up a heat theory: No I do not see any association with heat. I have had the glitch occur when I turn the computer on in the cold or when I turn it on a couple minutes after I turn it off, in which the board is still warm

You have the MacBook pro 5,1 2008?
Have you installed this firmware update, which brings you up to MBP51.007E.B06 (EFI 2.8)
MacBook Pro EFI Firmware Update 2.8
Download
This update is recommended for MacBook Pro (15-inch, late 2008) models. The update resolves a graphics issue that may cause the internal display to flicker.

New 'unwanted' user at login window

Deleted - found the answer in another discussion
Message was edited by: cgarch

Is this part of 'Find My Mac?"
Yes. With FMM enabled as guest user is available for whoever "finds" your lost/stolen computer to be able to login, connect to the internet and report it's location.

User listing unavailable on login window

Hey!
Ever since I upgraded to Leopard (10.5.1) my login window has changed from user listing to requiring a username and a password. If I set it to "List of users" the login window still asks for a username, and weirdly the "Show the restart, sleep and shutdown buttons" will cease functioning as well, i.e. no matter if I check it or not no buttons show up.
I have tried deleting all the com.apple.loginwindow.plist files in both my home and the root library to no avail.
Is this a Leopard-specific bug or maybe a result of upgrading directly from Tiger? Any ideas as to what i could do, please?

I created a new admin user account: when I logged out now only the new admin account was selectable, my old one was accessible only when clicking "Other..." and typing in the account name. So it did kind of solve the problem, but not how I wanted it.
Looks like as is my old account is like the Administrator/root account, that does not appear on the user listing. I read somewhere that some of the plist files control which users are added to the login screen, maybe I can meddle with that?
I cannot reinstall 10.5.1, my Install DVD came with it built-in.

Mac Client Login Window Takes Long Time "Other"

Mac 10.6.x client is successfully joined to the Windows Server 2008 based domain. But it’s taking too much time (approx. 5 to 7 minutes) to shows the “Other” option (using that, log on by AD user) in login window on Mac client.
Has anyone idea, why is it taking that long time.

Are you connected wirelessly or wired?
Which Mac are you using?

ZENworks user source login won't go away

Not sure where the best place to put this is.
ZCM 11.2.1
Server 2008R2 - Embedded DB
Win7 Clients - Not sure about XP, we're moving to Win7 only ASAP
Active Directory
When logging into a laptop and NOT connected to the domain LAN, it gets stuck on the Novell ZENworks user source login windows indefinitely. I can try logging into local machine and this happens every time.
In my old environment, with Novell Client, I could click workstation only and get the ZENworks login and cancel.
Not sure what to do to fix this or change the behavior.
Suggestions? TIA!

Originally Posted by farmeunitWPSD
Sorry, gave up on getting help with this.
After logging into AD, a "User Source Login" box appears in the upper left. There are no buttons or prompts at that point. Just the box. The box NEVER goes away. If we put the laptops to sleep instead of shutting down, then they can login normally. I found ONE thread about holding SHIFT down before hitting enter after entering login credentials. If they hold SHIFT until the ZENworks login box comes up, then they can cancel that and are logged in fine.
Any chance they're using wireless adapter and have it set to auto-connect?
We have the same thing, but only on Windows XP being reported. Seems it only happens if the person has added a wireless network (XP has slightly diff. options than Windows 7) AND have it set to auto-login/connect.

My MacBook Pro Retina's Bluetooth chipset unknown/odd login message on the login screen states Login Window Authentication Login window Name edit text has keyboard focus. In addition, the login screen is not remembering me

I have been experiencing several issues with my MacBook Pro Retina mid 2012. My MBPR is scheduled to go into the depot. However, I am wondering if anyone may be able to shed light on a few issues as this is the third "official" time my MBPR is going back for service ("one depot" trip; "one authorized" dealer; several in-store visits).
My Bluetooth is stating that the Bluetooth Chipset is Unknown (0). I also have had Bluetooth Preferences mysteriously change on me. In addition, while Bluetooth is off there are two serial modems turning on. I have turned them off, but they continue to pop up.
In addition, when I log in, my MBPR is not remembering me and my login name is not appearing on the slate-gray screen. The name and password are blank and the following message appears in the lower left hand corner. "login window authentication login window Name edit text has keyboard focus." As a side note, I am the only user. The login issue is a recent occurrence as we just totally wiped it again via a Command + R, and I don't believe I have an accessibility setting set to anything that would cause this, but wanted to check.
Should I be concerned here? Has anyone else had issues like this? I don't want to worry if I don't have to. I have had so many issues over the course of nine months. 5-6 wipes. Airport card replaced and I am about to pull my hair out if my MBPR doesn't come back worldly like clock work this time. I just can't send my days trying to get a $2300 product to work for me any longer. No idea what is wrong with it, but it is driving me insane. Cross your fingers for me and any guidance you have or thoughts would be welcomed. Thank you. EMM

A few more issues...
In Console, the following is greyed out:
User and Diagnostic reports
Com.apple.launchd.peruser.0
Com.apple.launchd.peruser.88
Com.apple.launchd.peruser.89
Com.apple.launchd.peruser.92
Com.apple.launchd.peruser.97
Com.apple.launchd.peruser.200
Com.apple.launchd.peruser.201
Com.apple.launchd.peruser.202
Com.apple.launchd.peruser.212
*[user logs are accessible]
Krb5kdc
Radius
My guest files are locked, but again I am the administrator of MBPR.
I am worried about a keystroke logged or at least, trying to rule it out.
Also:
Mdworker32(225) [and other mdworker numbers] are sandboxing; stating deny Mach-lookup
Com.apple.Powermanagement.control, etc. long attachment with those files with version: ??? (???).
Postinstall: removing applications/Microsoft Office 2011/Microsoft Outlook.app
WARNINGS in Console include:
[NSImage compositeToPoint:fromRect:operation:fraction:] is deprecated in MacOSX 19.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction] instead.
There are a ton of other warnings. Before I go through this again, can someone tell me if this is normal (all of it -- above too); or if these are symptoms is a keystroke logger or hardware issues?
I ask because originally, when my computer went in for diagnostics (more than once), Apple stated the hardware was fine (other than Airport Card -- finally). However, if I've done 5-6 total wipes; created new users; do not have sharing set-up; have not played around in Terminal; and am up-to-date with versions -- and various issues KEEP COMING BACK -- I am left wondering if a keystroke logger would be possible here?!? I thought maybe a faulty logic board, but why would diagnostics be okay, then? Not trying to be hyperbole, just desperate.
Please help me rule keystroke logger out or at least, tell me so I know, so I can take appropriate action. If you think it could be the logic board with symptoms above, that would be a great too.
All I want to do is use the computer as intended, but I can't seem to get a real answer, so after nine months -- I am turning to the communities to see if anyone -- anyone at all -- can help. The last thing I can do is have the MBPR come back from the depot and the same thing occur. Any guidance or advice would be so gratefully appreciated.

No keyboard at login window after logout

Hello all,
I'm just starting state testing and have been presented with a problem. When a student logs out of a machine in order to log into the testing account the login window won't accept input from the keyboard.
Bacground and details:
We have labs of computers using workgroup manager and open directory for management. In a normal lab the machine will boot to a login window. This is so that the preferences will be refreshed before a student logs in. The student will login as a local user (student) and procede to do whatever for the day.
We have recently started state mandated testing. I have set up an OD account which is very locked down and keeps the student on track while testing. This requires someone to log the normal user out and login as the OD user. This is where the problem arises.
About 50% of the time the keyboard will no longer funtion after logout. No keys of any sort work. The mouse still works. Even keystrokes through ARD do nothing. A end user is then required to reboot the system in order to do ANYTHING. This is not ideal for elementary kids.
From my digging in log files and poking around i noticed that the loginwindow process was hanging or crashing. If i kill the process the login window blinks and then works just fine. I'm sure i could write a logout script that drops a process into the background to kill the loginwindow process after so many seconds, but thats messy. Has anyone seen this? Any thoughts or solution? Only happens on a logout, never on an initial bootup.
I have found that 95% of these issues occur on Mac Mini's. I can consistantly replicate the issue on a mini. If i clone the mini to a macbook, i no longer have the problem (using carbon copy cloner). So either the hardware is part of the issue or the clone fixed something in the process.
OSX 10.5.8
/var/log/windowserver.log (on logout)
May 02 16:27:30 [252] kCGErrorIllegalArgument: CGXSetWindowListTags: Operation on a window 0x6 not owned by caller loginwindow
May 02 16:27:32 [252] CGXRestartSessionWorkspace: session workspace exited for session 256 ( on console )
May 02 16:27:32 [252] loginwindow connection closed; closing server.
May 02 16:27:33 [352] Server is starting up
May 02 16:27:36 [352] CGXMappedDisplayStart: Unit 0: no display alias property
May 02 16:27:36 [352] kCGErrorFailure: IOHIDSetCursorEnable returns -536870208
May 02 16:27:36 [352] kCGErrorFailure: Set a breakpoint at CGErrorBreakpoint() to catch errors as they are returned
May 02 16:27:36 [352] CGXPerformInitialDisplayConfiguration
May 02 16:27:36 [352] Display 0x41dc9d00: VirtualDisplay Unit 0; Vendor 0x756e6b6e Model 0x76697274 S/N 0; online enabled built-in (0,0)[1280 x 1024], base addr 0xb0021000
May 02 16:27:36 [352] AGCAttach: Couldn't find any matches
May 02 16:27:43 [352] kCGErrorIllegalArgument: CGXSetWindowListTags: Operation on a window 0x2 not owned by caller SecurityAgent
May 02 16:27:45 [352] kCGErrorIllegalArgument: CGXOrderWindow: Operation on a window 0x2 not owned by caller SecurityAgent

>kCGErrorIllegalArgument: CGXSetWindowListTags: Operation on a window 0x2 not owned by caller SecurityAgent
In those cases there may be threads and/or processes trying to do things with windows that they don't own. In other words, some programmers may have goofed up a little bit someplace.
But might try the one Helpful marked post here...
https://discussions.apple.com/thread/987826?start=0&tstart=0

Keyboard selection of user on login window

Similar Messages

Maybe you are looking for