Hello,
Just a quick bug report: Growl notifications from Adium no longer work as of version 1.2. All other application's growl notifications seem unaffected. If I reinstall Growl 1.1.4 then the notifications start working again.
I am running 10.5.1 with all current patches on a C2D Macbook Pro. Growl is installed at the latest version.
I am willing to provide any debugging information required in order to help resolve this issue if you let me know what I need to post...
Thanks!
EDIT: I forgot to mention that I am running Adium without any addons/extensions other then what comes with it out of the box.
Adium 1.2 regression vs Adium 1.1.4 (growl broke)
-
unused_user_name
- Harmless
- Posts: 3
- Joined: Wed Jan 09, 2008 12:04 am
I believe you mean that if you reinstall Adium 1.1.4 then growl messages from Adium events start working again, is that correct?
Have you checked the Adium configuration in the Growl preferences pane?
System Preferences -> Growl -> Applications -> Select Adium and click on the "Configure" button
The other thing to check would be the events tab in Adium preferences to make sure that the events still have the growl notification option tied to them.
I haven't seen an issue with growl notifications in Adium 1.2.
Have you checked the Adium configuration in the Growl preferences pane?
System Preferences -> Growl -> Applications -> Select Adium and click on the "Configure" button
The other thing to check would be the events tab in Adium preferences to make sure that the events still have the growl notification option tied to them.
I haven't seen an issue with growl notifications in Adium 1.2.
-
unused_user_name
- Harmless
- Posts: 3
- Joined: Wed Jan 09, 2008 12:04 am
Hrm...
It seems that my ~/Library/Application Support/Growl directory was chmodded 400 (-r--------) for some reason. rm'ing the directory and reinstalling Growl fixed the problem. I'm not sure how it got set to that in the first place, but it is working now. It is strange that Growl never complained that its data directory had incorrect permissions...
Anyways, all is working now. Thanks for the suggestions!
It seems that my ~/Library/Application Support/Growl directory was chmodded 400 (-r--------) for some reason. rm'ing the directory and reinstalling Growl fixed the problem. I'm not sure how it got set to that in the first place, but it is working now. It is strange that Growl never complained that its data directory had incorrect permissions...
Anyways, all is working now. Thanks for the suggestions!
To complain in such a fashion Growl would need to do such a check, which I don't believe it does.
Try my software!
#define ADIUMX pimp //by me
#define QUESTION ((2b) || (!2b))
Have you hugged a programmer today?
#define ADIUMX pimp //by me
#define QUESTION ((2b) || (!2b))
Have you hugged a programmer today?
-
Guitar King
- Harmless
- Posts: 16
- Joined: Sun Dec 30, 2007 2:34 am
- Location: Canada
-
unused_user_name
- Harmless
- Posts: 3
- Joined: Wed Jan 09, 2008 12:04 am
This is what I did.
1) Turn off growl in the system preferences
2) Run the following in a terminal, when logged in as the user having growl problems.
Make sure that growl is NOT running when you do this. (see step 1)
3) reinstall growl.
4) restart adium
Note that this method will revert all growl preferences to default in the growl system preferences pane.
Use this at your own risk.
1) Turn off growl in the system preferences
2) Run the following in a terminal, when logged in as the user having growl problems.
Make sure that growl is NOT running when you do this. (see step 1)
Code: Select all
rm -rf ~/Library/Application Support/Growl
4) restart adium
Note that this method will revert all growl preferences to default in the growl system preferences pane.
Use this at your own risk.