Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

growlmail quits with an error message (in console) after clicking a new mail bubble #12

Closed
GoogleCodeExporter opened this issue Dec 8, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Install osx 10.6
2. Install growl/growlmail 1.2 beta prerelease
3. Receive new mail with Mail.app and growlmail running. Click on the growl 
alert.

What is the expected output? What do you see instead?
It should bring the new Mail message to the forefront and growlmail should keep 
running. 
Instead growlmail quits with an error.

What version of the product are you using? On what operating system?
growlmail 1.2 beta prerelease package. OSX 10.6 Snow Leopard

Please provide any additional information below.
The error messages in Console:

8/29/09 1:41:33 PM  Mail[1288]  WARNING: Mail is not behaving in the way that 
GrowlMail 
expects. This is probably because GrowlMail is incompatible with the version of 
Mail you're using. 
GrowlMail will now turn itself off. Please check the Growl website for a new 
version. If you're a 
programmer and want to debug this error, run gdb, load Mail, set a breakpoint 
on 
GMShutDownGrowlMailAndWarn, and run.
8/29/09 1:41:33 PM  Mail[1288]  Furthermore, the caller provided a more specific 
message: 
GMSingleMessageViewer does not respond to -
initForViewingMessage:showAllHeaders:viewingState:fromDefaults:
8/29/09 1:41:33 PM  Mail[1288]  GrowlApplicationBridge: The Growl delegate did 
not supply a 
registration dictionary, and the app bundle at /Applications/Mail.app does not 
have one. Please 
tell this application's developer.

Original issue reported on code.google.com by shr...@gmail.com on 29 Aug 2009 at 5:48

@GoogleCodeExporter
Copy link
Author

should be fixed in 4327:57500edce4a2

Original comment by rarich...@gmail.com on 29 Aug 2009 at 6:09

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant