Console help, please!

Discussion in 'macOS' started by NoSmokingBandit, Jan 31, 2009.

  1. NoSmokingBandit macrumors 68000

    NoSmokingBandit

    Joined:
    Apr 13, 2008
    #1
    Starting yesterday my mouse occasionally gets jerky, almost like its caught on something, then it springs back a second later. I know its not my mouse because i use it in xp to game and it has no issues, so i was looking at the Console logs and found this:
    Code:
    1/31/09 3:21:37 PM com.apple.launchd[541] (org.freedesktop.dbus-session[1009]) posix_spawnp("/opt/local/bin/dbus-daemon", ...): No such file or directory 
    1/31/09 3:21:37 PM com.apple.launchd[541] (org.freedesktop.dbus-session[1009]) Exited with exit code: 1 
    1/31/09 3:21:37 PM com.apple.launchd[541] (org.freedesktop.dbus-session) Throttling respawn: Will start in 10 seconds
    
    That shows up every ten seconds, no matter what im doing. I closed every app but finder and console and it still showed up. I didnt install or tweak anything yesterday, so idk what the deal is. Any insight?
     
  2. monsi macrumors newbie

    Joined:
    Dec 11, 2009
    #2
    NoSmokingBandit,
    did you ever figure out what was causing this issue? I am facing the same thing and have had no luck in resolving the issue.
     
  3. madog macrumors 65816

    madog

    Joined:
    Nov 25, 2004
    Location:
    Korova Milkbar
    #3
    First, try repairing your permissions.

    If you've installed any new applications lately, possibly relating to X11, then go to ~/Library/Preferences and delete anything relating to freedesktop or dbus. Deleting preferences won't permanently harm anything.

    If you have installed something recently and know what it is, try going into

    1. /Library/LaunchAgents
    2. /Library/LaunchDaemons
    3. ~/Library/LaunchAgents
    4. ~/Library/LaunchDaemons
    5. System/Library/LaunchAgents
    6. System/Library/LaunchDaemons

    ...and deleting anything relating to that app. Otherwise, I won't be held responsible if you go into those folders and start deleting stuff that shouldn't be deleted. Doing so may be harmful. Otherwise if you do, restart your machine after for the affects to kick in.
     
  4. drspringfield macrumors newbie

    Joined:
    Dec 11, 2009
    #4
  5. cjmillsnun macrumors 68020

    Joined:
    Aug 28, 2009
    #5
    Looking at what it's used for I wouldn't disable it.

    CUPS (OS X's printing solution) uses it, as does Skype.

    I would suggest looking for a broken install instead.
     
  6. drspringfield macrumors newbie

    Joined:
    Dec 11, 2009
    #6
    No part of OS X requires anything in /Library/LaunchAgents. Feel free to uninstall it.
     
  7. NoSmokingBandit thread starter macrumors 68000

    NoSmokingBandit

    Joined:
    Apr 13, 2008
    #7
    This was posted back in January, since then i have upgraded to Snow Leopard and have so far evaded this issue.

    Next time lets try to not bump year old threads, mmmmkay?
     
  8. sidewinder macrumors 68020

    sidewinder

    Joined:
    Dec 10, 2008
    Location:
    Northern California
    #8
    Uh....did you see the post from monsi? He is having the same issue and wanted to know if your fixed and how? This is a perfect example of when it is appropriate to bring back an old thread.

    Okay?

    S-
     
  9. jon08 macrumors 65816

    Joined:
    Nov 14, 2008
    #9
    I'll borrow this thread real quick. Could someone help me with the following Console msgs?


    Dec 13 10:17:01 XXXXX-MacBook-Pro com.apple.Dock.agent[4018]: Sun Dec 13 10:17:01 XXXXX-MacBook-Pro.local Dock[4018] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 4: [0.000 0.000 0.000 0.000]

    Dec 13 10:17:01 XXXXX-MacBook-Pro com.apple.Dock.agent[4018]: Sun Dec 13 10:17:01 XXXXX-MacBook-Pro.local Dock[4018] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [0.000 0.000 0.000 0.000]

    Dec 13 10:17:01 XXXXX-MacBook-Pro Dock[4018]: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 4: [0.000 0.000 0.000 0.000]

    Dec 13 10:17:01 XXXXX-MacBook-Pro Dock[4018]: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [0.000 0.000 0.000 0.000]


    I keep getting hundreds of these msgs in my Console every day. What the hell is it?
     
  10. madog macrumors 65816

    madog

    Joined:
    Nov 25, 2004
    Location:
    Korova Milkbar
    #10
    I'll have to double check that, but that's good to know.
     
  11. wrldwzrd89 macrumors G5

    wrldwzrd89

    Joined:
    Jun 6, 2003
    Location:
    Solon, OH
    #11
    That's odd. I've never seen this message before. Since it's coming from the Dock, I'd look there first for the culprit.
     
  12. jon08 macrumors 65816

    Joined:
    Nov 14, 2008
    #12
    Looking at the Dock doesn't really help - I don't see any irregularities there.
     
  13. wrldwzrd89 macrumors G5

    wrldwzrd89

    Joined:
    Jun 6, 2003
    Location:
    Solon, OH
    #13
    I figured as much. We'll have to dig a bit deeper then. Try this:
    1. Move the Dock's preferences file (com.apple.Dock.plist) and database (com.apple.dock.db) to your desktop.
    2. Restart the Dock.
    If the log messages cease, then you'll have found the cause of your problem. If not, move the files back and restart the Dock again.

    If this fix helps, your Dock will revert to its default set of icons. Rebuilding it is fairly simple, especially if you grab a screenshot of your Dock before you attempt this fix. Command+Shift+4, then Spacebar, then click the Dock.
     
  14. jon08 macrumors 65816

    Joined:
    Nov 14, 2008
    #14
    Okay, I will probably give this a try tomorrow, thanks.
     
  15. monsi macrumors newbie

    Joined:
    Dec 11, 2009
    #15
    NoSmokingBandit,
    I too am on Snow Leopard and am having the issue. That is why I am bringing this up. By the way, drspringfield had it right. For some reason I had a plist file hanging around that didn't need to be there. Just in case I needed it I simply put a '.' in front and logged out and back in. Immediately I noticed that the console was no longer reporting the issue.
    Thank you drspringfield your advice was perfect.
     

Share This Page