dbus activation problem caused by leftover files from ancient macports install

[Ryan Schmidt]

On Feb 24, 2013, at 15:00, Rainer Müller wrote:
> On 2013-02-24 21:07, Lars Sonchocky-Helldorf wrote:
>> This might be caused by the fact I had a very outdated macports installed before (from 10.4 something) which I wasn't able to upgrade. So I removed everything manually but did not look into /Library/LaunchAgents/ and /Library/LaunchDaemons/
>> 
>> Is there a way to uninstall everything from an ancient macports install?
> 
> The uninstall instructions in the guide list all the paths ever used by
> MacPorts and even those back from the days when it was still called
> DarwinPorts:
> 
> http://guide.macports.org/#installing.macports.uninstalling

But they do not include the files Lars listed. MacPorts only provides recommendations for where files should be installed, and the uninstall instructions uninstall files installed in those locations. MacPorts has to install its launchd plists in the standard system directory for launchd plists, so the uninstall instructions only uninstall launchd plists with the MacPorts bundle identifier in the name. Ports could install files anywhere, and the dbus port installs launchd plists with non-MacPorts bundle ids so they're not included in our uninstallation instructions, since we have no way of knowing whether those files came from MacPorts or from a manual installation of dbus.

It might be nice if the dbus port would rename those plists to have the MacPorts bundle identifier. Or maybe there's a good reason why it's not doing that.

Lars, forcing the activation as you've already done is fine. You can manually remove the files with the mp_1361736070 suffix that MacPorts moved for you, or you can leave them; they're not causing a problem.