****UPDATE****
alright, turns out that i wasn't waiting long enough for the UserEventAgent to stop responding... it WAS, in fact, the BluetoothUserAgent-Plugin that the poster that i quoted stated below. I realized that it wasn't the BTMMPortInUseAgent.plugin when i returned all the plugins EXCEPT that one to their original folder and the UserEventAgent ceased to work once again. So i restarted the test and waiting about a minute for each until I realized the Bluetooth plugin was the problem.
As for my "ps. chime issue" ... I have been using an m-box for some mixing in protools and instead of listening through headphone or connecting other speakers, I have been using my computer speakers (i wasn't doing any heavy, serious mixing... or else I would have been using something WAY better than computer speakers, so don't give me flack about it
), and in doing so i unplugged them from the headphone jack of the mac mini and plugged them into my mbox. Unplugging the speakers activated the internal speaker of the mac mini, so i turned it down so the random noises wouldn't distract me... and never turned it back up. i didn't realize that there are, in reality, two different "volumes", if you will, which i discovered after restarting my computer WITHOUT my speakers plugged in to see what would happen... and when my desktop showed I saw that the volume was magically turned down... so i turned it back up... plugged my speakers back in, and restarted and the chime has made a triumphant return!
Sorry for clogging your forum with useless questions. I tried to find a way to delete this thread, but i couldnt find one, so if someone knows how and wants to let me know, or an admin wants to do it, feel free.
Thanks again
***************************************************************
Hello, I am new to the forum... as well as to macs... i just recently bought a mac mini and it was running fine, until i noticed two things. 1... that there was a "UserEventAgent - not responding" showing in my activity monitor and 2. that the startup chime has ceased to exist...
so in an effort to figure out what process was not running correctly and to fix the problem i searched for an answer and found this suggestion to narrow it down:
buzzz
Jan 16, 2008, 05:46 PM
I opened the folder UserEventPlugins which can be found in System > Library > UserEventPlugins and moved all the plugins to another folder. You must then delete the plugins from the UserEventPlugins folder which requires authorization. I restarted and opened the Activity Monitor. UserEventAgent was working fine. I then added each plugin one at a time back to the UserEventPlugins folder with a restart in between (which incidentally takes forever since installing Leopard). I kept adding, restarting then checking Activity Monitor until UserEventAgent stopped responding. I finally found the culprit. It was BluetoothUserAgent-Plugin. Since I removed it UserEventAgent is working fine - so far.
So this is what i did and when i placed BTMMPortInUseAgent.plugin back into the UserEventPlugins folder the UserEventAgent stopped working again.
... I've found my culprit... but what IS it? I want to know if its something i actually NEED or if its something that jumped onto my computer for a program I downloaded... or what the deal is. and ive search for an answer, but I just keep coming up with scans that people have done in which it shows up, not anyone actually talking about what it is.
Anyone have any clues?
Thanks in advance!
ps... if anyone has any suggestions as to why you think the "start-up chime" has ceased to exist on my computer as well... they are welcome... that's my next adventure... to figure out what happened... i miss my mac saying hello to me in the morning.
alright, turns out that i wasn't waiting long enough for the UserEventAgent to stop responding... it WAS, in fact, the BluetoothUserAgent-Plugin that the poster that i quoted stated below. I realized that it wasn't the BTMMPortInUseAgent.plugin when i returned all the plugins EXCEPT that one to their original folder and the UserEventAgent ceased to work once again. So i restarted the test and waiting about a minute for each until I realized the Bluetooth plugin was the problem.
As for my "ps. chime issue" ... I have been using an m-box for some mixing in protools and instead of listening through headphone or connecting other speakers, I have been using my computer speakers (i wasn't doing any heavy, serious mixing... or else I would have been using something WAY better than computer speakers, so don't give me flack about it
), and in doing so i unplugged them from the headphone jack of the mac mini and plugged them into my mbox. Unplugging the speakers activated the internal speaker of the mac mini, so i turned it down so the random noises wouldn't distract me... and never turned it back up. i didn't realize that there are, in reality, two different "volumes", if you will, which i discovered after restarting my computer WITHOUT my speakers plugged in to see what would happen... and when my desktop showed I saw that the volume was magically turned down... so i turned it back up... plugged my speakers back in, and restarted and the chime has made a triumphant return!Sorry for clogging your forum with useless questions. I tried to find a way to delete this thread, but i couldnt find one, so if someone knows how and wants to let me know, or an admin wants to do it, feel free.
Thanks again
***************************************************************
Hello, I am new to the forum... as well as to macs... i just recently bought a mac mini and it was running fine, until i noticed two things. 1... that there was a "UserEventAgent - not responding" showing in my activity monitor and 2. that the startup chime has ceased to exist...
so in an effort to figure out what process was not running correctly and to fix the problem i searched for an answer and found this suggestion to narrow it down:
buzzz
Jan 16, 2008, 05:46 PM
I opened the folder UserEventPlugins which can be found in System > Library > UserEventPlugins and moved all the plugins to another folder. You must then delete the plugins from the UserEventPlugins folder which requires authorization. I restarted and opened the Activity Monitor. UserEventAgent was working fine. I then added each plugin one at a time back to the UserEventPlugins folder with a restart in between (which incidentally takes forever since installing Leopard). I kept adding, restarting then checking Activity Monitor until UserEventAgent stopped responding. I finally found the culprit. It was BluetoothUserAgent-Plugin. Since I removed it UserEventAgent is working fine - so far.
So this is what i did and when i placed BTMMPortInUseAgent.plugin back into the UserEventPlugins folder the UserEventAgent stopped working again.
... I've found my culprit... but what IS it? I want to know if its something i actually NEED or if its something that jumped onto my computer for a program I downloaded... or what the deal is. and ive search for an answer, but I just keep coming up with scans that people have done in which it shows up, not anyone actually talking about what it is.
Anyone have any clues?
Thanks in advance!
ps... if anyone has any suggestions as to why you think the "start-up chime" has ceased to exist on my computer as well... they are welcome... that's my next adventure... to figure out what happened... i miss my mac saying hello to me in the morning.