Hi, Chris, I think you were too fast to answer, with a too small context of understanding.
Chris Forsythe wrote on 16/06/13:
This is why we ask that beta discussion be left on the beta list,
This thread has been started (and continued) on the growl-discuss list by John for a relevant reason: => his "bug-report" concerned the currently downloadable version from the App Store (2.0.1) reported as a "normal" user, not a developer, nor a beta-tester, nor a translator. Since nobody answered any solution to him, I confirmed I could also observe the same bug with the latest version I know: 2.1b6 (confirming this way that the problem can still happen)
since b7 has been posted for a bit now. :)
Maybe b7 hast been posted for a bit now, but I did not get any announcement of it the way I was usually informed: as a translator, I read the growl private localizations list and recently, only versions 2.1b6 and 2.1b5 were announced there: Subject: Growl 2.1b6, Date: Sat, 25 May 2013 00:40:44 -0500 Subject: Growl 2.1b5, Date: Thu, 9 May 2013 01:03:35 -0500 If b7 was ready to test, it's a pity not to have been informed as translators since previous builds still contained some slight modifications to be proofread before the release. On which list has it been announced? (I'm interested and can't find the message with Google-Group search) By the way, you mentioned above "the beta list". Which one are you speaking about? I subscribed to 4 Growl lists (Growl Development, Growl Discuss, Growl Localizations and Growl Private Localizations List) but none seems to be named "beta list". Is there a 5th one?
This problem is few and far between, and typically seems to be from a corrupt install.
This may be "rare" but it appeared for me from Growl generation 2 (that's why I disabled the autostart option), whereas generation 1.X never showed any problem like that on my laptop 10.7 Moreover, I recently switched to a brand new laptop, with OS 10.8 and I encounter exactly the same problem on a computer that never installed a version before 2.X from the App Store. It may be related for me to the use and test of beta version along with the existing App Store version, but I can't say. The fact is John observed and reported the same bug, and that me and a friend of mine using Growl can also observe it. To make a more precise bug-report, I could completely uninstall my current installation of Growl 2 in a better way than sending it to the Trash, but the procedure to completely uninstall Growl 2 is not documented there: http://growl.info/documentation/growl-package-removal.php And I will finish by re-affirming that using another system than automatic login items to implement "Start at login" is not very user-friendly for normal users that will still wonder why some "Starting at login" apps are there and other are not. Removing corrupted autostart could be easier that way ;-) Hoping help, Regards, -Yann. -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/growldiscuss. For more options, visit https://groups.google.com/groups/opt_out.
