Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
2.0.2.8 Issues
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  8 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
TheBurningOr  
View profile  
 More options Mar 21 2010, 4:35 pm
From: TheBurningOr <christopher.bur...@gmail.com>
Date: Sun, 21 Mar 2010 13:35:36 -0700 (PDT)
Local: Sun, Mar 21 2010 4:35 pm
Subject: 2.0.2.8 Issues
Since I updated to Growl 2.0.2, I get message that 'Growl has stopped
working' and 'A problem has caused the program to stop working
correctly. Windows will close the program and notify you if a solution
is available.'

The odd thing is that while this dialog box is on the screen, Growl
works perfectly, but as soon as I hit the x button or the 'close
program' button, Growl goes away.  I wish I could give more
information on the error, but there aren't any other details I can
see.  I'm running Windows 7 and have been using Growl successfully for
many months now.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
CoolJazz  
View profile  
 More options Mar 21 2010, 7:14 pm
From: CoolJazz <erikjan...@gmail.com>
Date: Sun, 21 Mar 2010 16:14:54 -0700 (PDT)
Local: Sun, Mar 21 2010 7:14 pm
Subject: Re: 2.0.2.8 Issues
I have no further information  but do want to report the exact same
issue.
Also been using the program a couple of months without problems but
since the update to 2.0.2, it's unusable because of the issue stated
above.

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Brian Dunnington  
View profile  
 More options Mar 21 2010, 9:34 pm
From: Brian Dunnington <briandunning...@gmail.com>
Date: Sun, 21 Mar 2010 18:34:19 -0700
Local: Sun, Mar 21 2010 9:34 pm
Subject: Re: 2.0.2.8 Issues
if either of you could do the following, it would help out a ton with
regards to finding the cause of the error:

1. close Growl if it is running
2. launch Growl from the command line with the debug parameter:
Growl.exe /debug:true
3. wait until the error message appears, then choose Close Program to exit
4. go to the location where Growl stores its user prefs (ex:
%USERPROFILE%\Local Settings\Application Data\Growl\2.0.0.0)
5. find the file called debug.txt and copy and paste its contents here
(or upload the file if that is easier)

thanks for reporting the issue - i am sure we can get to the bottom of
it if you can send me that debug log.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Brian Dunnington  
View profile  
 More options Mar 21 2010, 9:38 pm
From: Brian Dunnington <briandunning...@gmail.com>
Date: Sun, 21 Mar 2010 18:38:31 -0700
Local: Sun, Mar 21 2010 9:38 pm
Subject: Re: 2.0.2.8 Issues
also: are either of you running any additional displays, such as
Translucent Dark? if so and you manually installed them into your
Program Files location, that might be the cause. i will have to wait
until i see the debug log to be certain, but if you *are* using custom
displays, you can try copying the folder that contains the custom
display from the Program Files/Display directory to the Display
directory located at %USERPROFILE%\Local Settings\Application
Data\Growl\2.0.0.0

On Sun, Mar 21, 2010 at 6:34 PM, Brian Dunnington


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
TheBurningOr  
View profile  
 More options Mar 21 2010, 10:37 pm
From: TheBurningOr <christopher.bur...@gmail.com>
Date: Sun, 21 Mar 2010 19:37:26 -0700 (PDT)
Local: Sun, Mar 21 2010 10:37 pm
Subject: Re: 2.0.2.8 Issues
3/21/2010 7:30:18 PM    Bad arguments: The given path's format is not
supported.
3/21/2010 7:30:18 PM    PROGRAM FOLDER: C:\Program Files\Growl for
Windows
3/21/2010 7:30:18 PM    USER FOLDER: C:\Users\Christopher\AppData\Local
\Growl\2.0.0.0\
3/21/2010 7:30:19 PM    ContextMenu Handle: 1114990
3/21/2010 7:30:19 PM    TIMESTAMP - Before DisplayStyleManager.Load():
2.167124
3/21/2010 7:30:19 PM    Display 'Standard' was loaded successfully
3/21/2010 7:30:19 PM    Display 'Standard' handles the 'Standard' display
style
3/21/2010 7:30:19 PM    Display 'Smokestack' was loaded successfully
3/21/2010 7:30:19 PM    Display 'Smokestack' handles the 'Smokestack'
display style
3/21/2010 7:30:19 PM    Display 'Plain' was loaded successfully
3/21/2010 7:30:19 PM    Display 'Plain' handles the 'Plain' display style
3/21/2010 7:30:19 PM    Display 'Toast' was loaded successfully
3/21/2010 7:30:19 PM    Display 'Toast' handles the 'Toast' display style
3/21/2010 7:30:19 PM    Display 'Visor' was loaded successfully
3/21/2010 7:30:19 PM    Display 'Visor' handles the 'Visor' display style
3/21/2010 7:30:19 PM    Settings file 'C:\Users\Christopher\AppData\Local
\Growl\2.0.0.0\displayPluginInfo.settings' does not exist.
3/21/2010 7:30:19 PM    TIMESTAMP - After DisplayStyleManager.Load():
2.2601293
3/21/2010 7:30:19 PM    TIMESTAMP - Before
ForwardDestinationManager.Load(): 2.2961314
3/21/2010 7:30:19 PM    Forwarder 'Bonjour Forwarder' was loaded
successfully
3/21/2010 7:30:19 PM    Forwarder 'Manual Forwarder' was loaded
successfully
3/21/2010 7:30:19 PM    Forwarder 'Prowl' was loaded successfully
3/21/2010 7:30:19 PM    Forwarder 'Twitter' was loaded successfully
3/21/2010 7:30:19 PM    Forwarder 'Email' was loaded successfully
3/21/2010 7:30:19 PM    TIMESTAMP - After
ForwardDestinationManager.Load(): 2.3551347
3/21/2010 7:30:19 PM    TIMESTAMP - Before SubscriptionManager.Load():
2.3651353
3/21/2010 7:30:19 PM    Subscriber 'GNTP Subscription' was loaded
successfully
3/21/2010 7:30:19 PM    Subscriber 'Notify.io' was loaded successfully
3/21/2010 7:30:19 PM    Settings file 'C:\Users\Christopher\AppData\Local
\Growl\2.0.0.0\subscriberPluginInfo.settings' does not exist.
3/21/2010 7:30:19 PM    TIMESTAMP - After SubscriptionManager.Load():
2.3821363
3/21/2010 7:30:19 PM    FINAL LOAD TIME: 2.4531404
3/21/2010 7:30:19 PM    idle timer stopped.
3/21/2010 7:30:19 PM    idle timer stopped.
3/21/2010 7:30:19 PM    Settings file 'C:\Users\Christopher\AppData\Local
\Growl\2.0.0.0\sysnot.list' does not exist.
3/21/2010 7:30:20 PM    The plugin at 'C:\Users\Christopher\AppData\Local
\Growl\2.0.0.0\Displays\Chrome Twitter Display' could not be loaded.
System.TypeLoadException: Method 'CancelClosing' in type
'ChromeTwitterDisplay.FadeAnimator' from assembly
'ChromeTwitterDisplay, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=null' does not have an implementation.
   at System.Reflection.Assembly._GetExportedTypes()
   at System.Reflection.Assembly.GetExportedTypes()
   at Growl.PluginFinder.Search[T](String path, TypeFoundDelegate del,
List`1 ignoreList)
3/21/2010 7:30:20 PM    Bonjour service detected: Growl on CHRISTOPHER-
WIN

On Mar 21, 6:38 pm, Brian Dunnington <briandunning...@gmail.com>
wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
TheBurningOr  
View profile  
 More options Mar 21 2010, 10:38 pm
From: TheBurningOr <christopher.bur...@gmail.com>
Date: Sun, 21 Mar 2010 19:38:25 -0700 (PDT)
Local: Sun, Mar 21 2010 10:38 pm
Subject: Re: 2.0.2.8 Issues
So based on this data, I found that I had an old display (Chrome
Twitter Display) which I had deleted from within Growl, but evidently
had no deleted the actual folder in the displays directory.  I deleted
that and it works fine now.

On Mar 21, 7:37 pm, TheBurningOr <christopher.bur...@gmail.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Brian Dunnington  
View profile  
 More options Mar 21 2010, 11:11 pm
From: Brian Dunnington <briandunning...@gmail.com>
Date: Sun, 21 Mar 2010 20:11:10 -0700
Local: Sun, Mar 21 2010 11:11 pm
Subject: Re: 2.0.2.8 Issues
thanks so much for that - your assessment is exactly right.

i also saw a report on Twitter that the Chrome Twitter display wasnt
working for someone else as well, so i tried installing it and got the
same issue. glad to hear it is working again for you, and hopefully
anyone else with this issue will be able to solve it as well.

(for anyone that is interested: in versions prior to 2.0.2.8, each
individual display required GfW to reload all of the common plugin
assemblies for each individual display. this was good in that it
allowed each display to provide their own version of the common
assemblies, but it was bad because lots of duplicate code was being
loaded and retained in memory. as of 2.0.2.8, all display plugins
reference one set of common assemblies, so the duplicate overhead is
removed. however, in the case of Chrome Twitter, it was using a very
old version of the common assemblies that was not compatible with the
new common assemblies. i thought i had verified that every custom
display still worked with the new version, but i overlooked that one,
so i take full responsibility for the bug).

On Sun, Mar 21, 2010 at 7:38 PM, TheBurningOr


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
CoolJazz  
View profile  
 More options Mar 22 2010, 5:05 am
From: CoolJazz <erikjan...@gmail.com>
Date: Mon, 22 Mar 2010 02:05:41 -0700 (PDT)
Local: Mon, Mar 22 2010 5:05 am
Subject: Re: 2.0.2.8 Issues
Deleting the 2.0.0 display folder solves the issue for me as well.
tnx

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »