February 21, 2010
I just installed the Pukka software. I get this message
There was a login failure! There was a login failure with the my_account_name account. Please be sure that your password is correct.
I have the right password
in the console I get this
===== 2010-02-22 12:48:32 +1100 =====
Pukka/1.8.3 started
===== 2010-02-22 12:48:36 +1100 =====
Login failure while trying to fetch timestamp for my_account_name
can you please help
February 22, 2010
#1
I've been having the same
I've been having the same problem for the past couple of days. It used to be intermittent and opening the preferences and then closing them again would cause it to work correctly but since this app isn't free and has been exhibiting this behavior for quite some time can someone please fix this permanently?
February 22, 2010
#2
If I'm understanding things
If I'm understanding things correctly, both of you are seeing this problem in the background, only evidenced by the console log message and Pukka not updating your bookmarks right away? Are either of you seeing this when posting to Delicious?
I'm sorry for the problem with this. For whatever reason, Delicious is returning a login error. When this happens, if you can visit this URL and use your login, it may help debug the problem:
https://api.del.icou.us/v1/posts/update
If you are using Safari, you may have to use View > View Source to see the output. But it should indicate whether the login is working or not.
If it is not, there is not much that Pukka can do. This is why Pukka keeps trying back later and no longer alerts the user actively, since this is during background caching.
February 22, 2010
#3
When I click that link right
When I click that link right now (Pukka is exhibiting the problem) I get this in Safari:
"The service is not available. Please try again later."
February 22, 2010
#4
Hmm, that seems to point to
Hmm, that seems to point to Delicious uptime problems. If you wait some time, does your Pukka eventually connect and pull down your latest bookmarks?
February 23, 2010
#5
I just noticed how long Pukka
I just noticed how long Pukka will sit idle and stop fetching a week ago as I started running it on two different machines (home and work) and for the longest time I couldn't understand why something I had bookmarked earlier wasn't available on the other machine.
When I found out about the console log Pukka keeps last week I noticed that both copies had been sitting for over 4 days without updating.
Only after posting a new link will the cache update.
I just tried it again tonight by adding a bookmark after repeatedly getting the login error when Pukka launched and not being able to force the cache to update by opening and closing the preferences. It added the bookmark and then updated the cache.
After doing this I clicked that link you provided here again and it still says "service unavailable"
February 24, 2010
#6
Diagnostic URL
Hi Justin,
There was a typo in the URL posted. The URL should be https://api.delicious.com/v1/posts/update
When I load that up I get this, which looks correct:
<update time="2010-02-24T15:14:34Z" inboxnew="0"/>
<!-- fe02.api.del.ac4.yahoo.net uncompressed/chunked Wed Feb 24 08:04:21 PST 2010 -->
I was getting the same error message in the console as the others
===== 2010-02-24 15:58:19 +0000 =====
Login failure while trying to fetch timestamp for <my username>!
I think I have a fix for this issue though. It started happening after I had run the console line
defaults write /Applications/Pukka.app/Contents/Info LSUIElement 1
that was suggested in your article about hiding the Dock icon. This did work, in that Pukka loaded without adding itself to the Dock, but the login process started to fail. My guess is this is something to do with code signing and interaction with Keychain Access.
If you are having this problem, try re-downloading Pukka and replacing your copy of it. Undoing the command line change doesn't work. Pukka is working for me again now (I'm on 10.6). Cheers.
March 1, 2010
#7
Thanks for the followup,
Thanks for the followup, rufous. Changing the app contents would probably cause a problem like that.
As for troubledwine, are you still experiencing the problem? It has sounded all along as a Delicious availability problem. If it's still happening, I will contact Delicious and see if I can get an ETA on a fix for it.
Want to join the forums? Create an account or login.
