The app store installer isn't the culprit, the OS is supposed to make the container.
So how did you get into this situation? That's the million dollar question. Repair permissions maybe? We're trying to figure the how out. On Tue, Mar 11, 2014 at 4:10 PM, Bryan Rentoul <[email protected]> wrote: > Hello > > A bug report for you, I believe ... > > My system was running very slow, with lots of constant disk activity. > Looking at console logs, I found that crash reports were being generated > every ten seconds, complaining about com.growl.GrowlLauncher, thusly ... > > 12/03/14 9:51:49.196 am xpcd[320]: GrowlLauncher[478]: registration >> request failed: (0x11, 0x0) Could not obtain real path to the container >> root (*~/Library/Containers/com.growl.GrowlLauncher/Data*): The >> operation couldn't be completed. No such file or directory >> 12/03/14 9:51:49.378 am com.apple.launchd.peruser.501[294]: >> (com.growl.GrowlLauncher[478]) Job appears to have crashed: Illegal >> instruction: 4 >> 12/03/14 9:51:49.378 am com.apple.launchd.peruser.501[294]: >> (com.growl.GrowlLauncher) Throttling respawn: Will start in 9 seconds >> 12/03/14 9:51:52.220 am ReportCrash[470]: Saved crash report for >> GrowlLauncher[478] version 1.0 (1) to >> /Users/bryan/Library/Logs/DiagnosticReports/GrowlLauncher_2014-03-12-095151_Vista.crash > > > Simply creating the missing folder, > *~/Library/Containers/com.growl.GrowlLauncher/Data*, fixed the problem. > > This issue appeared after a fresh installation of Growl v2.1.3 directly > from the App Store (on a fresh OS X system) -- today, being 2014-03-12 > (NZDT). > > It would therefore seem that the App Store installer program is not > creating the folder in question, leading to this problem. Perhaps > GrowlLauncher itself should check for the folder and create it, if it's > missing? > > Note that, even with the missing folder, Growl loads normally when > launched manually, from its Launchpad icon. (This is not surprising.) > > From Googling the problem, it would appear (vaguely, as is usually the > case :p) that there are quite a few others having this issue, though none > of them appear to have found a solution and have opted for the sledge > hammer approach of removing Growl and never returning. A shame. It's a good > program and indeed relied on by many others, which I use and enjoy. So, I > hope this report helps stop the problems for others, sooner than later. > > Gruvin. > > -- > 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/d/optout. > -- Chris Forsythe @The_Tick <http://twitter.com/The_Tick> -- 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/d/optout.
