After some tweaking in the launching of the App to make it more Mac like (Instead of using the Terminal) it is working quite well.Īdiumerror.tiff (78.89 KiB) Viewed 18871 times adiumsettings.tiff (85. To get around this problem I have installed Pidgin using Macports. I have no other accounts with other protocols to try. I don't think I mentioned this, this problem with Adium is happening when I use a AIM account. Now I'm not saying that an adjustment to Adium's source code couldn't fix the problem. I would think what ever is causing the error would have to be external to the Adium application itself. As I am only getting the error from Lion 10.7.5 and not from Mountain Lion 10.8.5 with Adium 1.5.10.4 in both. I have not looked at the source code itself. The error is coming from libpurple and they do their own SSL handshaking and not one of the other libraries (OpenSSL, etc) Yeah I know, the file coping fix method is probably frowned upon, but if it fixes it, I'll be happy. Whether it be a setting someplace or coping a file from one os to the other. Ideally what I want to do is change the one thing on my Lion that is different from my Mountain Lion, to get Adium to connect again. If somebody could point me in the right direction, I would be most appreciative. With nothing obvious like a certificate that has just expired.Īnd there you have it. I looked at the certificates in Keychain Access on both Lion and Mountain Lion and they are awfully similar. I realize the error probably has something to do with a certificate expiring or something like that. Oh, I also updated the Openssl library of Lion to the same version that Mountain Lion uses, from 0.9.8za to 0.9.8zg, but that didn't change anything. Once the transfer is complete, restart Adium and perform the File. The fresh installs were done on other Mac Minis, just for testing purposes. Note: Your Users/Library folder is hidden in OS X Lion, so youll have to manually.
#Adium for mac mountain lion upgrade#
I was wondering if somebody could tell me what these error numbers mean? Or point me in the right direction to find that out.Īlso I realize the simplest solution would be just to upgrade my Lion to Mountain Lion, but that particular Mac Mini is my main Mac and I'm not going to do that. On the Lion it doesn't work on, I looked in the Console log and found these two error messages.Ħ/22/17 10:03:17.193 PM.
#Adium for mac mountain lion mac os x#
I then tried it on a fresh install of Mac OS X Mountain Lion with all the updates, and installed the same Adium and it WORKED!!! I did a fresh install of Mac OS X Lion and installed all the updates and installed Adium of course, and I still got the same error. No changes were made to the OS from one day to the next. The next day, Adium wouldn't connect with that error. One day a month ago or so everything was fine. I am experiencing the same error with Adium when I try to connect.
0 kommentar(er)
