Loading Profile...
Xmarks for safari not opening: classic view not supported
everytime i try and launch xmarks for safari ( i am running latest version of safari 4 and osx) I get this message...
can you help me out here??? id really appreciate a solution to this matter.
can you help me out here??? id really appreciate a solution to this matter.
I’m frustrated
3
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?Hi David,
This is a new one for us, and we can't reproduce it. Could you try uninstalling Xmarks for Safari on your Mac and then downloading it again from our site (http://download.xmarks.com/download)? We're hoping that will help start fresh and perhaps clear out whatever is confusing matters. -
Inappropriate?This same thing happens to me. The computer thinks Xmarks is a "Classic" (OS9) application, not an OSX application and therefore it will not run. I just tried installing and this happened on both my iMac and my MBP.
I’m frustrated
-
Inappropriate?I'm also having this issue on 10.6.1. I've uninstalled and reinstalled Xmarks. A side effect of having this be seen as a Classic application, Xmark's can't be launched nor be run automatically upon login. I've been using Xmarks for the Mac since a long time ... anything left over from earlier betas that may interfere.
-
Inappropriate?i just got this same error. any solutions yet?
-
Inappropriate?We have not been able to reproduce this in-house. We also don't have Classic bits in the product (at least, there shouldn't be any). We're still trying to find some clues on why this is happening to some people, but no breakthroughs yet. This thread is linked into our local bug report so I'll update here when we figure this out or have something for you to test.
-
Inappropriate?sorry for the delay. i figured it out i think. xmarks put an "application" (0kb in size) into my application folder, which when i clicked on it created the error message. xmarks actually works from the system preferences page, so no need for the app.
i assume i can just delete it from the applications folder and all will be well.
best!
I’m happy
3 Comments
Add a comment
This solves the problem
-
Ah! This is interesting. I wonder where the app is running from :) I have a sneaking suspicion that it may be in your Trash folder. Could you check? Right click on the Trash can in your dock and select Open. Is there an Xmarks for Safari.app in there? If not... is it possible that at some point while you were investigating this, you maybe moved an old copy of Xmarks for Safari.app from your /Applications folder to somewhere else to get it out the way? Thanks for following up - this is an interesting one. -
hey max - nothing in the trash, but there was another copy of xmarks for safari that was in another area (transfered from another computer) so looks like it was running on that. the safari app that i moved over was 2.8mb. everything seems ok. thanks!
-
Thanks for the follow-up. Looks like we should try to detect if we're running from somewhere unexpected and post a warning to the user that they might run into odd behavior. Thanks!
-
Inappropriate?Well, you can run xmarks from the preferences app. But the autolaunching xmarks app itself doesn't exist apart from just being a 0kb "application" in the applications menu. I'm surprised and disappointed this is taking SO long for you guys to figure out ...3 Comments Add a comment
This solves the problem
-
Right, so the proximal problem is the zero Kb /Applications/Xmarks for Safari.app - something went wrong during the install to drop that file there. You tried to re-install, so the same thing happened again. The interesting question is why is the install failing. (As an aside, we can't repro this, which is why we've not come up with a fix, sorry you're disappointed).
There's definitely an Xmarks for Safari.app *somewhere* on your system. That is *the* app that does the work - the prefs panel is nothing but a UI that sends messages to the app.
What I suspect is happening is that we are hitting a bug/feature in Apple's PackageMaker (known online as the "relocation bug/feature") which causes the Apple installer to try to drop an install on top of the previous version of a package rather than where we specify. So... if you for example were to move /Applications/Xmarks for Safari.app to someplace before applying a new version (the Trash is a possible candidate for a typical use-case), then the installer would update files *there*. Not what we intended.
That's why I am asking ckinker if he can find another instance of Xmarks for Safari.app on his system. Removing that and re-installing (or just moving that back to /Applications come to think of it) may well solve this problem.
On the assumption that this is the problem here, we worked on our build to make sure the PackageMaker doesn't hit this "feature" in the next release. -
Hmm ... that might fit the bill. Let me see where the "Xmarks for Safari.app" file/bundle exists. I'm away from my mac right now, but I do tend to arrange the apps into sub-folders before my apps menu becomes one gigantic mess... thanks for the explaination!
-
ok, so I booted up the mac and searched for "Xmarks for Safari". I noticed that I had moved around the applications to cleanup. So I relocated the actual .app file back to /Applications/ and re-ran setup.
Now:
1) I can see the actual .app (although it at the cluttered /Applications/ folder)
2) It appears it can autolaunch at login
3) It can sync properly
I don't know why the application/installer/daemon is hardcoded to sit at /Applications/ ... you should be offering the user the flexibility to cleanup their Applications folder, especially when you know each application happily dumps into that common folder (i.e. it's very easy to get cluttered).
I think it's very easy to reproduce this issue.
1) install xmarks (old version)
2) relocate the .app bundle
3) install a newer xmarks
4) see a 0 kb (confusing!) xmarks "application" in /Applications and this never autolaunched upon login (user observable failure).
EMPLOYEE
EMPLOYEE
