search

brettpoole / growl

Automatically exported from code.google.com/p/growl
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Error sending GNTP messages from Python library #521

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Testing with Growl 2.0b5

Using the gntp python library
https://github.com/kfdm/gntp

I have a simple password setup in Growl.

From the terminal
$ gntp -vvm test -P <password>

GNTP/1.0 REGISTER NONE 
MD5:803AB82458AF871ECA6AC84CD695C17D.A6A69A7330B29817AFFFB44CB48C9CA2
Application-Name: Python GNTP Test Client
Origin-Platform-Version: Darwin-12.0.0-x86_64-i386-64bit
Origin-Software-Version: 0.7
Origin-Machine-Name: rena
Origin-Software-Name: gntp.py
Origin-Platform-Name: Darwin
Notifications-Count: 1

Notification-Enabled: True
Notification-Name: Notification

GNTP/1.0 -ERROR NONE
Error-Code: 0
Response-Action: REGISTER
Error-Description: (null)

From the OSX console log

2012/08/09 21:29:45.805 Growl[8751]: Failed to retrieve password for service: 
Growl with account: Growl from keychain. Error: -25293

If I leave the password set in Growl, but then send the message again without a 
password, it goes through

$ gntp -vvm test 
...
GNTP/1.0 -OK NONE
Response-Action: REGISTER
...
GNTP/1.0 -OK NONE
Response-Action: NOTIFY

Original issue reported on code.google.com by kungfudi...@gmail.com on 10 Aug 2012 at 4:32

GoogleCodeExporter commented 8 years ago 
Unable to reproduce.
gntp -vvm test -P <password>
worked just fine
This is most likely a password retrieval failure given the keychain error.  
Even if you unset the password, and reset it, that might not be enough to fix 
it.  Deleting the item from the keychain entirely (Should be labeled just 
Growl, with account name Growl), and then resetting the password should fix 
this.  
This is most likely caused by Growl 2.0 beta's being signed with our 
DeveloperID cert, and our app store being signed by apple, as well as our 
previous beta's for 1.4 and older being signed most likely with our developer 
signing certs. Keychain services get cranky when signatures change. 
Closing as CantReproduce as the test runs fine here on a box with a keychain 
item for the password that isn't causing issues (Im almost never not on the dev 
id cert, so I don't generally face these issues)

Original comment by dan...@growl.info on 13 Aug 2012 at 11:52