fastsupply / growl

Automatically exported from code.google.com/p/growl
0 stars 0 forks source link

Growl does the update check even if it quits because another Growl is already running #221

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
Something along the lines of:
1. Install two versions of Growl, one of which is older than the other.
2. Start the newer Growl.
3. Start the older Growl.

What is the expected output?
The older Growl, being the one started second, simply quits.

What do you see instead?
2011-07-08 23:32:27 GrowlHelperApp[39248]   It appears that at least one other 
instance of Growl is running. This one will quit.
2011-07-08 23:32:30 GrowlHelperApp[39248]   1.2.2 <=> 1.2.1? 1
[older Growl sends its update notification to the winning [newer] Growl process]
2011-07-08 23:32:30 GrowlHelperApp[39248]   WARNING: could not register 
GrowlNotificationCenter for interprocess access

This appears to be the cause of the persistent update notifications that some 
users are seeing. We still don't know why they still have multiple versions 
installed (see #177), but this is an alternate way that they're still getting 
update notifications (besides the obvious case of the older Growl being the one 
that's running).

Original issue reported on code.google.com by p...@growl.info on 9 Jul 2011 at 6:49

GoogleCodeExporter commented 9 years ago
Of course, the Mac App Store obsoletes any updater-related bugs. I filed this 
one only to document it.

Original comment by p...@growl.info on 9 Jul 2011 at 6:49