Take the 2-minute tour ×
Ask Different is a question and answer site for power users of Apple hardware and software. It's 100% free, no registration required.

Basically, after using Fast User Switching to go back and forth between my wife's login and my own, we begin to experience loss of capactive touch functions on the Magic TrackPad. This occurred on both Snow Leopard and now Lion. A little more detail is in my post here: https://discussions.apple.com/message/15712385#15712385

share|improve this question
    
I'm seeing Launchpad getting stuck and preventing folder renaming after multi user switches. Are you seeing that at the same time as the trackpad wonkyness? killall Dock might help you jump start the processing of multitouch if they are the same issue. –  bmike Aug 1 '11 at 17:16
    
That's interesting. I will certainly look at the processes and also try a restart of Dock when I sit down to look at this again. Thank-you for the suggestion, and I'll post back here. –  Brian Aug 2 '11 at 20:31
    
Any luck? Anything else listed in the system logs or console logs around the time it fails? –  bmike Aug 9 '11 at 20:56
add comment

1 Answer

Okay, may have found something, posted to my other thread on this topic: https://discussions.apple.com/message/15963083#15963083

Okay, some potentially good news:

Under System Preferences > Bluetooth > Advanced > option to Allow Bluetooth devices to wake this computer

This is turned on by default and is apparently a per-user setting, not a global setting, which is where the conflict begins, from what I can tell.

My guess is that, when turned on for all users, like it is by default, when the computer goes to sleep, the bluetooth signal gets screwy, probably stepping over itself, to listen for incoming requests for both users for both keyboard and trackpad. And/or, when a user wakes the computer by pressing one of these devices, the signal tries to relaunch the Bluetooth stack for both users for both devices immediately, again probably stepping over itself, setting up a chain of events that will cause Bluetooth connectivity to fail altogether after a few sleep/wake and/or Fast User Switching cycles.

So, for a couple days now I've been running with this option turned off for one user and on for the other user. So, depending on which user is currently logged into the console, you may have to wake the computer by way of the power button or the keyboard/trackpad. The good news, though, is that it would typically foul up after no more than a day, and it's gone a couple of days thus far without issue.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.