This discussion is archived
2481 Views 6 Replies Latest reply: Jun 3, 2008 5:59 AM by riseroo
Currently Being ModeratedMay 2, 2008 1:40 PM (in response to Abble)Is this bug ever going to get fixed???? We need to be able to add/remove login items for our users. Yet, this bug hasn't been fixed in 2 service releases? Apple, are you kidding? This is a glaring bug, esp for users in AD environments!!!!Dual 2GHz, Mac OS X (10.5.2)
Currently Being ModeratedMay 7, 2008 7:09 AM (in response to DevCom)I am experiencing the same issue.
We are in a Windows/AD environment with a few lone Macs. I can't get the login items to launch when logged in as a network user. If I click on the Login Items button as a network user, system preferences dialog box completely freezes up so that I have to quit it.
If anyone knows of a fix, please let us know. Thnx so much. rroo ;-)~
MacIntel, 2.16 GHz Intel Core 2 Duo
1.5 GB 667 MHz DDR2 SDRAM
SATA 250 Gig933 MHz PowerPC G4, 2mb L3 Cache, Mac OS X (10.4.11), 1.5 GB SDRAM
Currently Being ModeratedMay 7, 2008 9:31 AM (in response to riseroo)I am also experiencing the same issue. The ability to specify login items in 10.4 was such useful feature because I would set my machine up to start up 10 minutes before I got to work in the morning so that when I got there, all my apps were running. The only way I've been able to specify login items has been to add them to my dock, control-click and then select Open at Login. The down side to that tactic is that you don't get the option to hide the application after it starts up. As a consequence, all my applications clutter up my desktop every morning.
It seems odd that Apple hasn't addressed this issue yet. Let's all keep our fingers crossed for an update soon!iMac 2.8GHz Intel Core 2 Duo, Mac OS X (10.5.2), 4 GB 667 MHz DDR2 SDRAM
Currently Being ModeratedMay 19, 2008 5:21 AM (in response to ReLeaf)I have been experiencing this problem too...I was wanting to edit the list of login items but every time I go into the Login Items tab the accounts dialogue freezes...I presume that there isn't a fix/solution out there yet?macbook pro, Mac OS X (10.4.10)