After 1.3.1 Growl will not work

6 views
Skip to first unread message

Christopher Landrigan

unread,
Nov 3, 2011, 8:51:26 PM11/3/11
to Growl Discuss
I updated to 1.3.1 from 1.3 on the Mac App Store and now growl will
not launch. I'm not sure what was done to it from the previous
version, but it doesn't even give me an error notification.
Uninstalling and reinstalling from the MAS did nothing and I'm left
with the same problem. Please help; I'd hate to leave an application
I've grown to love.

Josh

unread,
Nov 3, 2011, 9:14:20 PM11/3/11
to growld...@googlegroups.com
can you see any growl-related messages in console.app?

> --
> You received this message because you are subscribed to the Google Groups "Growl Discuss" group.
> To post to this group, send email to growld...@googlegroups.com.
> To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
>

Charlie S

unread,
Nov 3, 2011, 9:21:11 PM11/3/11
to growld...@googlegroups.com
There should be some message in the console

--
You received this message because you are subscribed to the Google Groups "Growl Discuss" group.
To post to this group, send email to growld...@googlegroups.com.
To unsubscribe from this group, send email to growldiscuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.




--


----
Charlie Schloss

Grab Opera the fastest browser on earth @
http://my.opera.com/community/download.pl?ref=Chas4&p=opera_desktop


Why Open the Web?

Despite the connecting purpose of the Web, it is not entirely open to all of
its users. When used correctly, HTML documents can be displayed across
platforms and devices. However, many devices are excluded access to Web
content.

http://my.opera.com/community/openweb/info/


Christopher Landrigan

unread,
Nov 3, 2011, 9:40:49 PM11/3/11
to growld...@googlegroups.com
You're right. I had no idea what console.app was until I searched for it. It shows an Unresolved error followed by a Coredata: Fatal error. I'm guessing this isn't a good thing?
Reply all
Reply to author
Forward
0 new messages