Path Finder 4.8: known issues on Leopard
October 23, 2007
Now you probably got surprised when you’ve read this topic name, because we repeatedly told that Path Finder 4.8 is compatible with Leopard. For the most part it certainly is, but unfortunately the last Leopard seed reserved a couple of surprises for us that I thought you would like to know when planning your Leopard upgrade.
As I eluded alluded in my previous blog post on this topic, testing on an unfinished OS is a tricky business. I saw Path Finder bugs appear in one OS seed, disappear in the next couple of seeds, reappear in the fourth one and then disappear again. Generally if we saw a bug that persisted through more than two seeds, we proceeded with fixing it. Therefore you can understand why Mac developers are getting annoyed by the fact that Apple didn’t give us access to the Leopard Gold Master seed before the general release date - we have no idea if some of the issues below will still persist on the Leopard GM which is to be released on Friday. Here’s the current list of the known Path Finder 4.8 bugs on the pre-release Leopard build:
A folder popping up in the Dock while copying/moving/deleting files. Path Finder uses a helper tool called “ctask” to do its copy/move/delete operations - it launches and quits when the operation is complete. Somehow this background tool materialized in a form of a folder which behaves like an application popping up in the Dock when it launches. It doesn’t affect the quality of the copy at all - it is just kind of funny to watch. The history of this bug looks as following: fixed itself in build 9A343, reappeared in 9A466, fixed again in 9A527 and reappeared on the last seed. Now Steve’s bet that it disappears in the GM, and I’m still kind of nervous that it won’t.
Operations as root fail - this is a biggie that suddenly appeared on the last Leopard seed. The bug manifests itself as following: one operation as root is usually possible the first time upon installation of Path Finder, all further operations as root fail, also as a side effect - the “Quit” menu gets disabled when such operation was unsuccessful. After discovering the issue we immediately contacted Apple to ask what’s going on. It turned out that they implemented some additional restrictions for helper tools running as root to make the OS more secure. It is now considered unsafe to use any relative load paths in setuid helper programs. So the fix number one suggested by Apple -
-is to use absolute paths. Usually @executable_path is just used by apps that want to be drag installable. Apple typically ships an installer for software that requires setuid helpers, but we can understand the desire to maintain Path Finder as a drag-installable app.
Yes, we don’t really want to ship as an installer, because it seems that people generally don’t like them. Most of users prefer just to drag their app to the /Applications folder, because it seems more transparent and intuitive.
Another possibility to fix suggested by Apple would be
to replace your setuid helper tool with a daemon started by launchd. This is the direction we would like to see developers go and it’s a more secure approach.
Now this is also a bit problematic - the cool part of our helper tool is that it is not hanging around all the time. It quits and launches when needed. A daemon would always work in the background which is probably less desirable. However if we don’t have any other choice we will prefer this option. This requires some considerable work in restructuring our code and we still hope that there’s an easier solution. We’re still discussing this issue with Apple and will hopefully decide soon which road to take. This bug is highly unlikely to disappear by itself and we’re really sorry for the inconvenience that this issue might cause you.
When you reveal the PF Desktop in Expose - the Finder Desktop is shown instead. This is because we used an undocumented hack to make Path Finder desktop “stick” when hitting Expose, and it’s not surprising that this method got broken on Leopard. We hope we will find another hack soon :)
Issues with tooltips in Column View - when you hover over long file names in Column View, it should normally show you the full name in a tooltip, but it shows some weird numbers instead. This issue would be completely harmless if the Size Browser wouldn’t take it so badly - unfortunately it crashes because of this for some reason. Steve thinks that this issue will fix itself on the Leopard GM build, but I again remain skeptical. We placed bets yesterday - if he’s right I will have to send him a T-Shirt with “München” written on it :)
We hope to address those issues as soon as possible. We’re especially upset about the operations as root issue, since it has taken us by surprise and so late - we were testing Path Finder on Leopard since more than one year and if those OS restrictions were implemented earlier, we would have had more time to find a solution.
Update : looks like all issues mentioned above are still present on the GM build. The final build also brought some new bugs - issues with Connect to Server dialog, cosmetic issue with Desktop selection and a bug where “move to” contextual menu item copies files instead of moving them. We’re now intensively working on fixing all those issues as soon as possible in the next maintenance update. We’re sorry for the inconvenience.
Posted by grotsasha at October 23, 2007 10:51 AMComments
Thanks for the tip. That is the solution I was planning on adding, but I am still waiting to see if it happens in 10.5 GM. I'm still hoping it will be fixed.
I use Tiger and have the desktop issues, too ;)
I can confirm the pop-up folder problem in the Dock for 10.5 GM Retail. I just installed it (here in Europe) and I see the folder appearing when I copy/move/delete stuff. :)
There is also a second problem I noticed: I upgraded PF to 4.8.1 from the Update within PF - the "upgrade and relaunch" window never finished what it was doing. I had to force quit that and download PF from the website.
Thanks for confirming the folder problem on the GM seed.
The second problem is also a known one - Sparkle auto-update framework which is included in 4.8 doesn't work on Leopard, but we fixed it in 4.8.1. Since I assume that there are only few people who wanted to auto-update PF 4.8 to 4.8.1 on Leopard, I didn't include it in the list of known issues, since it's basically already fixed. You're welcome to report any additional issues you find on Leopard - you can do it on the forum for example.
Thanks for the fix Bryan Schappel, but where does the Launcher actually live? It's not in Applications or Utilities.
You wrote:
---
Now this is also a bit problematic - the cool part of our helper tool is that it is not hanging around all the time. It quits and launches when needed. A daemon would always work in the background which is probably less desirable.
---
Your launchd Daemon should be launch-on-demand, and should exit if not used after a couple of minutes.
But this doesn't solve the drag-install issue, since you'll need to add a plist in /Library/LaunchDaemons if you want it to run with root privileges. You'll probably want to install it when the PF user does its first operation requiring admin privileges.
There is also the security issue of making it point to a binary where regular users can write. Think carefully about security implications there.
The weird number tooltip problem in column view is still there in the GM release.
There is another issue I am not seeing listed here.
When we shut down our MacBook Pro then we see a messages saying that "Path Finder canceled shut down". After hitting "OK" and being back in Path Finder we can also not quit Path Finder anymore because the quit menu is greyed out. All there is left to do is to force quit the application.
Networks do not show up in pathfinder in ox 10.5
Connecting to AFP servers in PF does not work for me. Any volume connected via Finder shows up normally, but trying cmd-K i PF only gives an error after choosing which server to connect to.
I think you mean alluded, not eluded
Oh, thanks. It just sounds so similar *blush* I'm not English native as you might have guessed already and I always appreciate someone correcting me. Thanks!
On the side note, we have good news - we've already fixed a major part of the issues above (including Connect to Server issues) in our internal seed and we're currently testing it.
I've also found that I can't connect to remote Apple File Servers (same as Morten above) through Pathfinder 4.8.1, but can through the Finder on Leopard.
I don't know what exact method you're using for the desktop-expose hack, but I just now wrote up a quick test app on leopard using the method found at http://www.cocoadev.com/index.pl?DontExposeMe, along with "NSWindowCollectionBehaviorCanJoinAllSpaces" (seems to) work perfectly.
Yes, we're using this sticky bit hack from CocoaDev. I think that PF's Desktop stays anyway in all Spaces without having to set it explicitely. As far as I remember the sticky bit hack doesn't even get called in PF, but Steve didn't look at this problem yet. It's good to know that it works in a test app! Thanks!
The "Launchers" live here:
~/Library/Application\ Support/Path\ Finder/PlugIn\ Support/Launchers
Remember the "~" means your home folder.
There may be multiple Launchers within this folder. Here's a link to a working Info.plist file:
http://www.rts-software/download/Info.plist.zip
Grab that file, unzip it, and copy it into the "Contents" folder within each Launcher. You may need to quit and relaunch PF after doing this.
Sorry, typed the link incorrectly. Should be this:
I absolutely LOVE PF and wish you all the best in fixing the problems created by Leopard. You guys totally rock!
Hi Ben, your link seems to have disappeared, how are we supposed to fix the expose-desktop problem with pathfinder?
Thanks
Hi! Tiger 10.4.11 + Path Finder ... who wants Leopard? I downgraded to 10.4.11 ... I have to say Path Finder gives more features than Leopard... plus the system is still stable :)
Has the disabled Quit command bug in post #9 been resolved? I just encountered it in Leopard today. Thanks.
Post a comment
Remember Me?
Comments Preview:

I have a solution for the "Launcher folder in the dock" bug. Add an "NSBGOnly" number key to the Info.plist file in the Launcher/Contents folder. Set the value of the key to "1". This stops the folder from appearing in the dock.