Thanks for the reply, Zac. I'll try this when I get home. But there are no other users on the machine and no other instances of Growl running. I even rebooted to make sure. Also, it turned out I was smart enough to keep a backup of 1.3.1, which I'm running now without a hitch. The problem is definitely specific to 1.3.2.
On Dec 8, 10:47 am, Zac Bowling <[email protected]> wrote: > Yah. Your issue is not the same as the case sensitive bug. Your's looks like > someone is using Growl's port. Maybe another Growl instance (might be running > another user maybe?) > > Shutdown Growl and try running this and seeing what process is using the port: > > lsof -i :23053 | grep LISTEN > > -- > Zac Bowling > > > > > > > > On Wednesday, December 7, 2011 at 3:10 PM, HorseCalledHorse wrote: > > In case anyone's wondering, my file system is not case sensitive, so > > this is a different bug. > > Anyone got any ideas? > > > -- > > You received this message because you are subscribed to the Google Groups > > "Growl Discuss" group. > > To post to this group, send email to [email protected] > > (mailto:[email protected]). > > To unsubscribe from this group, send email to > > [email protected] > > (mailto:[email protected]). > > For more options, visit this group > > athttp://groups.google.com/group/growldiscuss?hl=en. -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
