Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!news-1.dfn.de!news.dfn.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Jolly Roger <jollyroger@pobox.com>
Newsgroups: comp.sys.mac.apps
Subject: Re: pointer can't penetrate link area
Date: 7 Mar 2014 01:01:04 GMT
Organization: People for the Ethical Treatment of Pirates
Lines: 54
Message-ID: <bnsk2fFigrjU1@mid.individual.net>
References: <52f96b90$0$1307$c3e8da3$50776f34@news.astraweb.com> <ldbqdm$o3c$1@dont-email.me> <1lgwki7.tcwq1dvibuN%dushanm@nnips.net> <lde7mn$35d$2@dont-email.me> <1lh0tx9.dj1l1r1n1kupqN%dushanm@nnips.net> <1lh8233.1qz4769f898waN%dushanm@nnips.net> <bmfpjhFg8tU1@mid.individual.net> <1lh8lj7.clgjcx12fjiv4N%dushanm@nnips.net> <bmhgv1FbhmfU1@mid.individual.net> <1lhg1ql.1koqeiroo4md2N%dushanm@nnips.net> <bmrvtqFicpbU1@mid.individual.net> <1lhl7q4.1uoj5za1jgm0rsN%dushanm@nnips.net> <1lhs1au.1o96fd0eoynmkN%dushanm@nnips.net> <1li3g17.3fgmo91khc0m2N%dushanm@nnips.net>
X-Trace: individual.net oI30cDhAHG/QAW9L1tepbgsogRZ+AiBGun0J+OkzaiF/meThmk
Cancel-Lock: sha1:jld2htK/u3HKvk4a6lFL5ak2Jq0=
X-Face: _.g>n!a$f3/H3jA]>9pN55*5<`}Tud57>1<n@LQ!aZ7vLO_nWbK~@T'XIS0,oAJcU.qLM dk/j8Udo?O"o9B9Jyx+ez2:B<nx(k3EdHnTvB]'eoVaR495,Rv~/vPa[e^JI+^h5Zk*i`Q;ezqDW< ZFs6kmAJWZjOH\8[$$7jm,Ogw3C_%QM'|H6nygNGhhl+@}n30Nz(^vWo@h>Y%b|b-Y~()~\t,LZ3e up1/bO{=-)
User-Agent: slrn/1.0.1 (Darwin)
Xref: csiph.com comp.sys.mac.apps:21366

On 2014-03-06, DushanM <dushanm@nnips.net> wrote:
> DushanM <dushanm@nnips.net> wrote:
>
>> DushanM <dushanm@nnips.net> wrote:
>> 
>>  <snip>
>> > 
>> > Oops - I spoke too soon: this weekend the problem was back.  Now I'll
>> > have to see whether it was just the restarting that made it go away
>> > temporarily, or whether clearing out the cache was involved.  And if the
>> > cache, maybe deleting the System cache will fix the problem for good.
>> > Also, after the problem disappears I'll be on the lookout for what was
>> > just done before it re-appeared.  It'll be Thursday before I can check
>> > that, and will report back.
>> > 
>> > - Dushan
>> 
>> I did a bit more experimentation and observed this:
>> 
>> # a restart is all that's needed to make the pointer-freeze problem
>>   disappear in my wife's account; no cache deleting is necessary
>> 
>> # the problem seems to stay gone so long as I stay on my wife's account,
>>   tho statistics are still sparse,
>> 
>> # but when I switch to my account and then back to my wife's, the prob-
>>   lem reappears
>> 
>> # meanwhile, I've done nothing in either account except invoke Firefox
>> 
>> I'll experiment more this w.e.
>> 
>> - Dushan
>
> I've little to add to the above, except that I don't have to do anything
> at all to re-introduce the pointer problem in my wife's account except
> switch to my account, then immediately back: the problem's there.  So
> apparently the switching itself was responsible, probably when account
> data was being re-assembled.  So what is done in that process that is
> not done during restart (the restart is directly to my wife's account)?

Something must get cached. You previously said that deleting cache files
temporarily fixed the issue, right? 

I believe you can find out which cache files are being deleted by
examining the system log after deleting them. That may be a place to
start. You could try manually (selectively) deleting certain ones or
groups of them to see which one(s) are at fault.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR