You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Bug #560: Apparent Alias issue

Kind bug
Product Synergy
When Created , updated
Status open
Reporter Michael G
Tags no tags

Description

I am having problems with an error report of broken aliases which appears in the Console Log for every program but would appear to be associated with Synergy.

The current version of the Log entries (regardless of the program called) is:

Mail[163]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Install Synergy 3.1.1 Mail[163]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Install Synergy 3.1.1 Mail[163]: [FM] FSResolveAliasWithMountFlags() returns #-43 for alias_manager.pdf Mail[163]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Maroon Mail[163]: [FM] FSResolveAliasWithMountFlags() returns #-43 for alias_manager.pdf Mail[163]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Maroon

"Maroon" is the file name of a JPG image associated with an album in iTunes.

Before I uninstalled and reinstalled Synergy a further two JPG file names for albums were also reported. One of these was in Synergy's Temporary Album Covers folder.

Before I reinstalled Synery I was using the previous Beta version and this was being reported in place of Synergy 3.1.1, which is now the alleged missing alias per the above listing since I reinstalled.

This installer file and "alias_manager.pdf" (Apple's listing of Carbon error codes) have both been deleted by me and now appear as broken aliases.

Any light you can shed on this would be appreciated.

By the way, I do not have any programming skills although I am computer-literate.

Thanks

Comments

  1. Greg Hurrell

    The beginning of each entry begins with "Mail[163]" which indicates that Mail.app is the one issuing those messages. Did someone mail the installer to you as an attached or anything like that? It would be interesting to see what is on your file system that matches the name "Install Synergy 3.1.1". One way of finding out is to run a find from the command line:

    find / -name "*Install Synergy 3.1.1*"

  2. Michael G

    Thanks for the reply.

    Actually, every prog or process launched reports the same lost alias. For example, this consecutive extract from the log:

    Safari[162]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Install Synergy 3.1.1 Safari[162]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Install Synergy 3.1.1 Safari[162]: [FM] FSResolveAliasWithMountFlags() returns #-43 for alias_manager.pdf Safari[162]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Maroon Safari[162]: [FM] FSResolveAliasWithMountFlags() returns #-43 for alias_manager.pdf Safari[162]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Maroon Mail[163]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Install Synergy 3.1.1 Mail[163]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Install Synergy 3.1.1 Mail[163]: [FM] FSResolveAliasWithMountFlags() returns #-43 for alias_manager.pdf Mail[163]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Maroon Mail[163]: [FM] FSResolveAliasWithMountFlags() returns #-43 for alias_manager.pdf Mail[163]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Maroon Finder[98]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Install Synergy 3.1.1 Finder[98]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Install Synergy 3.1.1 Finder[98]: [FM] FSResolveAliasWithMountFlags() returns #-43 for alias_manager.pdf Finder[98]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Maroon Finder[98]: [FM] FSResolveAliasWithMountFlags() returns #-43 for alias_manager.pdf Finder[98]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Maroon Console[305]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Install Synergy 3.1.1 Console[305]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Install Synergy 3.1.1 Console[305]: [FM] FSResolveAliasWithMountFlags() returns #-43 for alias_manager.pdf Console[305]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Maroon Console[305]: [FM] FSResolveAliasWithMountFlags() returns #-43 for alias_manager.pdf Console[305]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Maroon System Preferenc[308]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Install Synergy 3.1.1 System Preferenc[308]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Install Synergy 3.1.1 System Preferenc[308]: [FM] FSResolveAliasWithMountFlags() returns #-43 for alias_manager.pdf System Preferenc[308]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Maroon System Preferenc[308]: [FM] FSResolveAliasWithMountFlags() returns #-43 for alias_manager.pdf System Preferenc[308]: [FM] FSResolveAliasWithMountFlags() returns #-43 for Maroon

    Running the search at the command line that you suggested returns the following but I don't know how to interpret:

    find / -name "*Install Synergy 3.1.1*" find: /.Spotlight-V100: Permission denied find: /.Trashes: Permission denied

  3. Michael G

    Sorry, should have mentioned that the installer was downloaded through the link at Versiontracker.

  4. Greg Hurrell

    Well, the "-43" error code means "File or directory not found; incomplete pathname", according to the developer docs. I've never seen this kind of thing before but if I had to make an educated guess I would say that it's not actually related to Synergy; rather, I think you might have some mild filesystem corruption and it just so happens that those two files, one of them being the Synergy installer, were affected.

    So I would try some of the usual troubleshooting steps to see if this goes away:

    - seeing if it happens in another user account

    - seeing if it persists across a log out/log in

    - seeing if it persists across a reboot

    - seeing if you can fix any errors on your disk by booting from your installation CD/DVD and running Disk First Aid

    - resetting your Launch Services database (see http://www.thexlab.com/faqs/resetlaunchservices.html and http://www.macosxhints.com/article.php?story=20031215144430486)

    So those are the things I would start with. That last one I mention because you said it happens when you launch any app at all, so perhaps it has something to do with a corrupt Launch Services database...

  5. Michael G

    Thanks. I've tried the steps you have suggested but the problem persists. I will speak to Apple tech and see what they advise.

  6. Greg Hurrell

    Ok, let me know how you go!

Add a comment

Comments are now closed for this issue.

Menu