Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.mac.apps > #21064 > unrolled thread
| Started by | Dushan Mitrovich <dushanm@nnips.net> |
|---|---|
| First post | 2014-02-10 17:15 -0700 |
| Last post | 2014-02-11 11:29 +1100 |
| Articles | 11 on this page of 31 — 6 participants |
Back to article view | Back to comp.sys.mac.apps
pointer can't penetrate link area Dushan Mitrovich <dushanm@nnips.net> - 2014-02-10 17:15 -0700
Re: pointer can't penetrate link area philo <philo@privacy.net> - 2014-02-10 18:21 -0600
Re: pointer can't penetrate link area dushanm@nnips.net (DushanM) - 2014-02-11 12:18 -0700
Re: pointer can't penetrate link area philo <philo@privacy.net> - 2014-02-11 16:20 -0600
Re: pointer can't penetrate link area dushanm@nnips.net (DushanM) - 2014-02-13 19:29 -0700
Re: pointer can't penetrate link area dushanm@nnips.net (DushanM) - 2014-02-17 17:24 -0700
Re: pointer can't penetrate link area Jolly Roger <jollyroger@pobox.com> - 2014-02-18 00:59 +0000
Re: pointer can't penetrate link area dushanm@nnips.net (DushanM) - 2014-02-18 00:10 -0700
Re: pointer can't penetrate link area Jolly Roger <jollyroger@pobox.com> - 2014-02-18 16:44 +0000
Re: pointer can't penetrate link area Barry Margolin <barmar@alum.mit.edu> - 2014-02-18 12:31 -0500
Re: pointer can't penetrate link area Jolly Roger <jollyroger@pobox.com> - 2014-02-18 19:25 +0000
Re: pointer can't penetrate link area dushanm@nnips.net (DushanM) - 2014-02-22 00:48 -0700
Re: pointer can't penetrate link area Jolly Roger <jollyroger@pobox.com> - 2014-02-22 16:00 +0000
Re: pointer can't penetrate link area dushanm@nnips.net (DushanM) - 2014-02-24 19:45 -0700
Re: pointer can't penetrate link area dushanm@nnips.net (DushanM) - 2014-02-28 12:21 -0700
Re: pointer can't penetrate link area dushanm@nnips.net (DushanM) - 2014-03-06 16:01 -0700
Re: pointer can't penetrate link area Jolly Roger <jollyroger@pobox.com> - 2014-03-07 01:01 +0000
Re: pointer can't penetrate link area dushanm@nnips.net (DushanM) - 2014-03-08 14:50 -0700
Re: pointer can't penetrate link area Jolly Roger <jollyroger@pobox.com> - 2014-03-08 22:32 +0000
Re: pointer can't penetrate link area dushanm@nnips.net (DushanM) - 2014-03-10 18:45 -0600
Re: pointer can't penetrate link area Jolly Roger <jollyroger@pobox.com> - 2014-03-11 01:19 +0000
Re: pointer can't penetrate link area dushanm@nnips.net (DushanM) - 2014-03-18 14:12 -0600
Re: pointer can't penetrate link area dushanm@nnips.net (DushanM) - 2014-03-18 14:12 -0600
Re: pointer can't penetrate link area - SOLVED dushanm@nnips.net (DushanM) - 2014-03-21 21:58 -0600
Re: pointer can't penetrate link area - SOLVED Jolly Roger <jollyroger@pobox.com> - 2014-03-22 18:28 +0000
Re: pointer can't penetrate link area - UNSOLVED dushanm@nnips.net (DushanM) - 2014-03-24 20:35 -0600
Re: pointer can't penetrate link area - RE-SOLVED dushanm@nnips.net (DushanM) - 2014-04-03 13:37 -0600
Re: pointer can't penetrate link area - RE-SOLVED Jolly Roger <jollyroger@pobox.com> - 2014-04-03 21:10 +0000
Re: pointer can't penetrate link area - RE-SOLVED dushanm@nnips.net (DushanM) - 2014-04-09 16:09 -0600
Re: pointer can't penetrate link area dushanm@nnips.net (DushanM) - 2014-02-22 00:47 -0700
Re: pointer can't penetrate link area dorayme <do_ray_me@bigpond.com> - 2014-02-11 11:29 +1100
Page 2 of 2 — ← Prev page 1 [2]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2014-03-11 01:19 +0000 |
| Message-ID | <bo76klFpkscU2@mid.individual.net> |
| In reply to | #21476 |
On 2014-03-11, DushanM <dushanm@nnips.net> wrote: > Jolly Roger <jollyroger@pobox.com> wrote: > >> On 2014-03-08, DushanM <dushanm@nnips.net> wrote: >> > Jolly Roger <jollyroger@pobox.com> wrote: >> > >> >> 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 >> >> >> problem 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. >> > >> > Oh, maybe I see what you're driving at: when accounts get switched, data >> > in the 'from' account gets cached, then re-introduced when that account >> > is re-entered. And this does not happen - or at least not identically - >> > during a restart. Is that the general idea? >> >> My theory is because deleting caches fixes the problem, that's what is >> happening. >> >> > I can certainly try inventorying the cache files before and after a >> > restart and an account switch, and comparing. But then it would seem as >> > if the switching operation itself somehow carries the infection, or at >> > least activates it, since it wasn't active before the switch after a >> > restart. The mechanism for this is more and more puzzling to me. >> > >> > I try the cache inspection approach and see what I learn. >> > >> > Thanks for bearing with me on this problem. >> >> I think if you can figure out which specific cache file(s) are involved, >> that will lead you to the root caused (and the solution). > > Yesterday I spent several hours trying our different things, and learned > a little, but not what caused the problem or how to fix it. > > 0 in each case below the initial condition was the same: restart into my > wife's acct, with no sign of the problem; > > 1 I manually deleled every cache I could find on my wife's acct, both > system and user, switched to my acct and back, and the problem came > back; > > 2 ... then did the same thing using Cocktail, in case I'd missed some- > thing, and got identical results; > > 3 did nothing (no cache clearing), switched to the Guest acct and back, > and the problem was still gone; > > 4 did nothing (no cache clearing), logged out of wife's acct then logged > back into it, and the problem was still gone. > > These observations indicate that in fact clearing cache does not fix the > problem; only restarting does. > > To summarize: > -- switching from wife's acct to my acct, and _only_ to my acct, brought > on the problem > -- restarting is the only way I found to get rid of the problem - tempo- > rarily until I switch to my acct > -- I did not see deleting cache have any visible effect on the above be- > havior That sounds right to me. > So the question seems to be, how does a momentary switch to my acct con- > taminate my wife's on return? Great question! Sheesh... I'm running out of ideas as to what the cause could be. Have you tried making note of the exact times you log in/out/restart and looking at the console and system logs for entries with those time stamps to see if you might get a clue as to some error condition that might be at play? > Can you suggest more experiments? I thought of one: create a new acct > and see what effect it has on switching to it and back. That would be a good test. If it passes, you conceivably migrate your data from your old account to a new account to (hopefully) rid yourself of whatever is causing the problem. -- 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
[toc] | [prev] | [next] | [standalone]
| From | dushanm@nnips.net (DushanM) |
|---|---|
| Date | 2014-03-18 14:12 -0600 |
| Message-ID | <1libfb7.13mo49h8dpnxeN%dushanm@nnips.net> |
| In reply to | #21477 |
Jolly Roger <jollyroger@pobox.com> wrote: > On 2014-03-11, DushanM <dushanm@nnips.net> wrote: > > Jolly Roger <jollyroger@pobox.com> wrote: > > > >> On 2014-03-08, DushanM <dushanm@nnips.net> wrote: > >> > Jolly Roger <jollyroger@pobox.com> wrote: > >> > > >> >> 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 > >> >> >> problem 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. > >> > > >> > Oh, maybe I see what you're driving at: when accounts get switched, data > >> > in the 'from' account gets cached, then re-introduced when that account > >> > is re-entered. And this does not happen - or at least not identically - > >> > during a restart. Is that the general idea? > >> > >> My theory is because deleting caches fixes the problem, that's what is > >> happening. > >> > >> > I can certainly try inventorying the cache files before and after a > >> > restart and an account switch, and comparing. But then it would seem as > >> > if the switching operation itself somehow carries the infection, or at > >> > least activates it, since it wasn't active before the switch after a > >> > restart. The mechanism for this is more and more puzzling to me. > >> > > >> > I try the cache inspection approach and see what I learn. > >> > > >> > Thanks for bearing with me on this problem. > >> > >> I think if you can figure out which specific cache file(s) are involved, > >> that will lead you to the root caused (and the solution). > > > > Yesterday I spent several hours trying our different things, and learned > > a little, but not what caused the problem or how to fix it. > > > > 0 in each case below the initial condition was the same: restart into my > > wife's acct, with no sign of the problem; > > > > 1 I manually deleled every cache I could find on my wife's acct, both > > system and user, switched to my acct and back, and the problem came > > back; > > > > 2 ... then did the same thing using Cocktail, in case I'd missed some- > > thing, and got identical results; > > > > 3 did nothing (no cache clearing), switched to the Guest acct and back, > > and the problem was still gone; > > > > 4 did nothing (no cache clearing), logged out of wife's acct then logged > > back into it, and the problem was still gone. > > > > These observations indicate that in fact clearing cache does not fix the > > problem; only restarting does. > > > > To summarize: > > -- switching from wife's acct to my acct, and _only_ to my acct, brought > > on the problem > > -- restarting is the only way I found to get rid of the problem - tempo- > > rarily until I switch to my acct > > -- I did not see deleting cache have any visible effect on the above be- > > havior > > That sounds right to me. > > > So the question seems to be, how does a momentary switch to my acct con- > > taminate my wife's on return? > > Great question! Sheesh... I'm running out of ideas as to what the cause > could be. > > Have you tried making note of the exact times you log in/out/restart and > looking at the console and system logs for entries with those time > stamps to see if you might get a clue as to some error condition that > might be at play? No, I haven't, but that's a thought. I could compare switching to/from my acct with to/from another acct and see if there's a difference. If so, that should tell us something. > > Can you suggest more experiments? I thought of one: create a new acct > > and see what effect it has on switching to it and back. > > That would be a good test. If it passes, you conceivably migrate your > data from your old account to a new account to (hopefully) rid yourself > of whatever is causing the problem. I'll be travelling for a few days, so won't get to try these things until this w.e. I'll let you know the results next Monday. - Dushan
[toc] | [prev] | [next] | [standalone]
| From | dushanm@nnips.net (DushanM) |
|---|---|
| Date | 2014-03-18 14:12 -0600 |
| Message-ID | <1lipiwb.14b464t5h1wkyN%dushanm@nnips.net> |
| In reply to | #21477 |
Jolly Roger <jollyroger@pobox.com> wrote: > On 2014-03-11, DushanM <dushanm@nnips.net> wrote: > > Jolly Roger <jollyroger@pobox.com> wrote: > > > >> On 2014-03-08, DushanM <dushanm@nnips.net> wrote: > >> > Jolly Roger <jollyroger@pobox.com> wrote: > >> > > >> >> 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 > >> >> >> problem 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. > >> > > >> > Oh, maybe I see what you're driving at: when accounts get switched, data > >> > in the 'from' account gets cached, then re-introduced when that account > >> > is re-entered. And this does not happen - or at least not identically - > >> > during a restart. Is that the general idea? > >> > >> My theory is because deleting caches fixes the problem, that's what is > >> happening. > >> > >> > I can certainly try inventorying the cache files before and after a > >> > restart and an account switch, and comparing. But then it would seem as > >> > if the switching operation itself somehow carries the infection, or at > >> > least activates it, since it wasn't active before the switch after a > >> > restart. The mechanism for this is more and more puzzling to me. > >> > > >> > I try the cache inspection approach and see what I learn. > >> > > >> > Thanks for bearing with me on this problem. > >> > >> I think if you can figure out which specific cache file(s) are involved, > >> that will lead you to the root caused (and the solution). > > > > Yesterday I spent several hours trying our different things, and learned > > a little, but not what caused the problem or how to fix it. > > > > 0 in each case below the initial condition was the same: restart into my > > wife's acct, with no sign of the problem; > > > > 1 I manually deleled every cache I could find on my wife's acct, both > > system and user, switched to my acct and back, and the problem came > > back; > > > > 2 ... then did the same thing using Cocktail, in case I'd missed some- > > thing, and got identical results; > > > > 3 did nothing (no cache clearing), switched to the Guest acct and back, > > and the problem was still gone; > > > > 4 did nothing (no cache clearing), logged out of wife's acct then logged > > back into it, and the problem was still gone. > > > > These observations indicate that in fact clearing cache does not fix the > > problem; only restarting does. > > > > To summarize: > > -- switching from wife's acct to my acct, and _only_ to my acct, brought > > on the problem > > -- restarting is the only way I found to get rid of the problem - tempo- > > rarily until I switch to my acct > > -- I did not see deleting cache have any visible effect on the above be- > > havior > > That sounds right to me. > > > So the question seems to be, how does a momentary switch to my acct con- > > taminate my wife's on return? > > Great question! Sheesh... I'm running out of ideas as to what the cause > could be. > > Have you tried making note of the exact times you log in/out/restart and > looking at the console and system logs for entries with those time > stamps to see if you might get a clue as to some error condition that > might be at play? > > > Can you suggest more experiments? I thought of one: create a new acct > > and see what effect it has on switching to it and back. > > That would be a good test. If it passes, you conceivably migrate your > data from your old account to a new account to (hopefully) rid yourself > of whatever is causing the problem. This morning I tried the test user approach: created a Standard acct, restarted into wife's (Admin.) acct, verified no link-pointer problem, switched to test acct (no problem there either), then switched back to wife's acct... and still no evidence of the problem. So _only_ switching to my (Admin.) acct introduces the behavior. Friday I'll take the computer to the Apple Genius bar in town and see if they can make heads or tails of this. Will update this forum then. - Dushan
[toc] | [prev] | [next] | [standalone]
| From | dushanm@nnips.net (DushanM) |
|---|---|
| Date | 2014-03-21 21:58 -0600 |
| Subject | Re: pointer can't penetrate link area - SOLVED |
| Message-ID | <1liv38j.1nbield1lfa756N%dushanm@nnips.net> |
| In reply to | #21601 |
DushanM <dushanm@nnips.net> wrote: > Jolly Roger <jollyroger@pobox.com> wrote: > > > On 2014-03-11, DushanM <dushanm@nnips.net> wrote: > > > Jolly Roger <jollyroger@pobox.com> wrote: > > > > > >> On 2014-03-08, DushanM <dushanm@nnips.net> wrote: > > >> > Jolly Roger <jollyroger@pobox.com> wrote: > > >> > > > >> >> 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 problem 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. > > >> > > > >> > Oh, maybe I see what you're driving at: when accounts get switched, > > >> > data in the 'from' account gets cached, then re-introduced when > > >> > that account is re-entered. And this does not happen - or at least > > >> > not identically - during a restart. Is that the general idea? > > >> > > >> My theory is because deleting caches fixes the problem, that's what > > >> is happening. > > >> > > >> > I can certainly try inventorying the cache files before and after a > > >> > restart and an account switch, and comparing. But then it would > > >> > seem as if the switching operation itself somehow carries the > > >> > infection, or at least activates it, since it wasn't active before > > >> > the switch after a restart. The mechanism for this is more and > > >> > more puzzling to me. > > >> > > > >> > I try the cache inspection approach and see what I learn. > > >> > > > >> > Thanks for bearing with me on this problem. > > >> > > >> I think if you can figure out which specific cache file(s) are > > >> involved, that will lead you to the root caused (and the solution). > > > > > > Yesterday I spent several hours trying our different things, and > > > learned a little, but not what caused the problem or how to fix it. > > > > > > 0 in each case below the initial condition was the same: restart into > > > my wife's acct, with no sign of the problem; > > > > > > 1 I manually deleled every cache I could find on my wife's acct, both > > > system and user, switched to my acct and back, and the problem came > > > back; > > > > > > 2 ... then did the same thing using Cocktail, in case I'd missed some- > > > thing, and got identical results; > > > > > > 3 did nothing (no cache clearing), switched to the Guest acct and > > > back, and the problem was still gone; > > > > > > 4 did nothing (no cache clearing), logged out of wife's acct then > > > logged back into it, and the problem was still gone. > > > > > > These observations indicate that in fact clearing cache does not fix > > > the problem; only restarting does. > > > > > > To summarize: -- switching from wife's acct to my acct, and _only_ to > > > my acct, brought on the problem -- restarting is the only way I found > > > to get rid of the problem - tempo- rarily until I switch to my acct -- > > > I did not see deleting cache have any visible effect on the above be- > > > havior > > > > That sounds right to me. > > > > > So the question seems to be, how does a momentary switch to my acct > > > con- taminate my wife's on return? > > > > Great question! Sheesh... I'm running out of ideas as to what the cause > > could be. > > > > Have you tried making note of the exact times you log in/out/restart and > > looking at the console and system logs for entries with those time > > stamps to see if you might get a clue as to some error condition that > > might be at play? > > > > > Can you suggest more experiments? I thought of one: create a new acct > > > and see what effect it has on switching to it and back. > > > > That would be a good test. If it passes, you conceivably migrate your > > data from your old account to a new account to (hopefully) rid yourself > > of whatever is causing the problem. > > This morning I tried the test user approach: created a Standard acct, > restarted into wife's (Admin.) acct, verified no link-pointer problem, > switched to test acct (no problem there either), then switched back to > wife's acct... and still no evidence of the problem. So _only_ > switching to my (Admin.) acct introduces the behavior. Friday I'll take > the computer to the Apple Genius bar in town and see if they can make > heads or tails of this. Will update this forum then. > > - Dushan Last night I didn't just restart the iMac, but actually shut it down before restarting, to make sure the problem would be there at this morning's Genius Bar appt. And sure enough, the problem didn't show up! So I explained what the problem had been, and the tech said he'd seen that sort of thing before - a glitch in the graphics engine. It is disconnecting the power cord - a power management (SMC) Reset - that fixes it. So now the problem is gone, and I know what to do if it should ever return. But what caused it in the first place remains a mystery. Thanks all for your suggestions. - Dushan
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2014-03-22 18:28 +0000 |
| Subject | Re: pointer can't penetrate link area - SOLVED |
| Message-ID | <bp631rFck3gU1@mid.individual.net> |
| In reply to | #21626 |
On 2014-03-22, DushanM <dushanm@nnips.net> wrote: > > Last night I didn't just restart the iMac, but actually shut it down > before restarting, to make sure the problem would be there at this > morning's Genius Bar appt. And sure enough, the problem didn't show up! > > So I explained what the problem had been, and the tech said he'd seen > that sort of thing before - a glitch in the graphics engine. It is > disconnecting the power cord - a power management (SMC) Reset - that > fixes it. So now the problem is gone, and I know what to do if it > should ever return. But what caused it in the first place remains a > mystery. > > Thanks all for your suggestions. > > - Dushan Great! Thanks for reporting back! -- 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
[toc] | [prev] | [next] | [standalone]
| From | dushanm@nnips.net (DushanM) |
|---|---|
| Date | 2014-03-24 20:35 -0600 |
| Subject | Re: pointer can't penetrate link area - UNSOLVED |
| Message-ID | <1lj14q7.1e8yjyt16ifa02N%dushanm@nnips.net> |
| In reply to | #21627 |
Jolly Roger <jollyroger@pobox.com> wrote: > On 2014-03-22, DushanM <dushanm@nnips.net> wrote: > > > > Last night I didn't just restart the iMac, but actually shut it down > > before restarting, to make sure the problem would be there at this > > morning's Genius Bar appt. And sure enough, the problem didn't show up! > > > > So I explained what the problem had been, and the tech said he'd seen > > that sort of thing before - a glitch in the graphics engine. It is > > disconnecting the power cord - a power management (SMC) Reset - that > > fixes it. So now the problem is gone, and I know what to do if it > > should ever return. But what caused it in the first place remains a > > mystery. > > > > Thanks all for your suggestions. > > > > - Dushan > > Great! Thanks for reporting back! Dang, I spoke too soon. Just because the problem seemed to be gone at the Genius Bar, I thought it was gone for good. Not so! After I hooked everything back together at home, it came back as tho nothing had happened, thumbing its nose at me. So now I'm going to try to duplicate as exactly as I can the conditions at the Gbar: nothing plugged in to the USB ports at all (wireless keyboard and mouse). If the problem is gone, I'll start plugging things back in to see when it reappears. This is turning into a real puzzle. - Dushan
[toc] | [prev] | [next] | [standalone]
| From | dushanm@nnips.net (DushanM) |
|---|---|
| Date | 2014-04-03 13:37 -0600 |
| Subject | Re: pointer can't penetrate link area - RE-SOLVED |
| Message-ID | <1lj8oa8.mkoklmztdx8gN%dushanm@nnips.net> |
| In reply to | #21652 |
DushanM <dushanm@nnips.net> wrote: > Jolly Roger <jollyroger@pobox.com> wrote: > > > On 2014-03-22, DushanM <dushanm@nnips.net> wrote: > > > > > > Last night I didn't just restart the iMac, but actually shut it down > > > before restarting, to make sure the problem would be there at this > > > morning's Genius Bar appt. And sure enough, the problem didn't show up! > > > > > > So I explained what the problem had been, and the tech said he'd seen > > > that sort of thing before - a glitch in the graphics engine. It is > > > disconnecting the power cord - a power management (SMC) Reset - that > > > fixes it. So now the problem is gone, and I know what to do if it > > > should ever return. But what caused it in the first place remains a > > > mystery. > > > > > > Thanks all for your suggestions. > > > > > > - Dushan > > > > Great! Thanks for reporting back! > > Dang, I spoke too soon. Just because the problem seemed to be gone at > the Genius Bar, I thought it was gone for good. Not so! After I hooked > everything back together at home, it came back as tho nothing had > happened, thumbing its nose at me. > > So now I'm going to try to duplicate as exactly as I can the conditions > at the Gbar: nothing plugged in to the USB ports at all (wireless > keyboard and mouse). If the problem is gone, I'll start plugging things > back in to see when it reappears. This is turning into a real puzzle. > > - Dushan Okay, I finally got the real solution: A piece of software I'd installed a few months ago and forgotten about, that was active only on my account. That software is 'MagicMouse prefs'. Whenever I quit that program, the problem disappears, and whenever I re-start it, it re-appears. Apparently it didn't affect the account on which it was active (mine), but did drag along some contaminant that affected my wife's acct. So now I deleted that program, and all is well. I should probably inform the software's author of this mis-behavior. So long (for now), and thanks for all the fish (expression courtesy of Douglas Adams). - Dushan Mitrovich
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2014-04-03 21:10 +0000 |
| Subject | Re: pointer can't penetrate link area - RE-SOLVED |
| Message-ID | <bq612jF782rU1@mid.individual.net> |
| In reply to | #21713 |
On 2014-04-03, DushanM <dushanm@nnips.net> wrote: > DushanM <dushanm@nnips.net> wrote: > > Okay, I finally got the real solution: A piece of software I'd installed > a few months ago and forgotten about, that was active only on my > account. That software is 'MagicMouse prefs'. Whenever I quit that > program, the problem disappears, and whenever I re-start it, it > re-appears. Apparently it didn't affect the account on which it was > active (mine), but did drag along some contaminant that affected my > wife's acct. So now I deleted that program, and all is well. > > I should probably inform the software's author of this mis-behavior. > > So long (for now), and thanks for all the fish (expression courtesy of > Douglas Adams). Woot! I love the smell of success! Congrats! : ) I take it you mean MagicPrefs: <https://www.macupdate.com/app/mac/33095/magicprefs> It would definitely be a great idea to email the author about this. I would also suggest leaving a troubleshooting comment on the macupdate web site notifying others who use this software who may find themselves experiencing the same issue. Great detective work! Glad you finally figured out the cause! -- 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
[toc] | [prev] | [next] | [standalone]
| From | dushanm@nnips.net (DushanM) |
|---|---|
| Date | 2014-04-09 16:09 -0600 |
| Subject | Re: pointer can't penetrate link area - RE-SOLVED |
| Message-ID | <1ljuewc.16dbmlm1k2620wN%dushanm@nnips.net> |
| In reply to | #21714 |
Jolly Roger <jollyroger@pobox.com> wrote: > On 2014-04-03, DushanM <dushanm@nnips.net> wrote: > > DushanM <dushanm@nnips.net> wrote: > > > > Okay, I finally got the real solution: A piece of software I'd installed > > a few months ago and forgotten about, that was active only on my > > account. That software is 'MagicMouse prefs'. Whenever I quit that > > program, the problem disappears, and whenever I re-start it, it > > re-appears. Apparently it didn't affect the account on which it was > > active (mine), but did drag along some contaminant that affected my > > wife's acct. So now I deleted that program, and all is well. > > > > I should probably inform the software's author of this mis-behavior. > > > > So long (for now), and thanks for all the fish (expression courtesy of > > Douglas Adams). > > Woot! I love the smell of success! Congrats! : ) > > I take it you mean MagicPrefs: > > <https://www.macupdate.com/app/mac/33095/magicprefs> > > It would definitely be a great idea to email the author about this. I > would also suggest leaving a troubleshooting comment on the macupdate > web site notifying others who use this software who may find themselves > experiencing the same issue. > > Great detective work! Glad you finally figured out the cause! Thanks, JR. Yes, that's the one I meant. I will follow your suggestion about emailing the author (& also MacUpdate) to let them know about this quirk... as soon as I finish with all the ridiculously complex tax forms nonsense. - Dushan
[toc] | [prev] | [next] | [standalone]
| From | dushanm@nnips.net (DushanM) |
|---|---|
| Date | 2014-02-22 00:47 -0700 |
| Message-ID | <1lhc25j.144cceh1l5sly2N%dushanm@nnips.net> |
| In reply to | #21134 |
DushanM <dushanm@nnips.net> wrote: > Jolly Roger <jollyroger@pobox.com> wrote: > > > On 2014-02-18, DushanM <dushanm@nnips.net> wrote: > > > As suggested, I explored the CPU changes when the pointer freeze occurs. > > > Here is a compilation of observations: > > > > > > # I ran both the Activity Monitor and XRG, and neither report a change > > > in CPU usage level for the browser when the pointer has turned into a > > > frozen pointing hand, as opposed to when it is a freely moving pointer > > > > > > # the problem happens for _every_ link that causes the pointer to turn > > > into a pointing hand, whose depiction is frozen until the pointer > > > location moves out from the screen area allocated to the link > > > > > > # it happens for both the Magic Mouse and the Logitech trackball > > > > > > # it is independent of the browser used; I tried Firefox, Safari, > > > Roccat, and chromium > > > > > > # it only happens on one account, but not the other > > > > > > # the problem didn't exist until about two months ago > > > > > > Can anyone suggest any other tests I can run? > > > > I would be interested to know if anything at all is logged to the > > console or system logs when the pointer changes to the hand. Open > > /Applications/Utilities/Console and watch it while you do a test. Report > > results here. > > > > The fact that this happens only in one account is good - it means it's > > not a system-wide issue, and likely has something to do with a > > preference file or cache file in your user account. > > I may not get to check on that until the w.e. as I'm away from the iMac > 'til then. But when I get to it I'll check the Console. > > - Dushan heytrewq
[toc] | [prev] | [next] | [standalone]
| From | dorayme <do_ray_me@bigpond.com> |
|---|---|
| Date | 2014-02-11 11:29 +1100 |
| Message-ID | <do_ray_me-AFB1F6.11292211022014@news.albasani.net> |
| In reply to | #21064 |
In article <52f96b90$0$1307$c3e8da3$50776f34@news.astraweb.com>, Dushan Mitrovich <dushanm@nnips.net> wrote: > Using the Firefox browser on my wife's account, the pointer > moves around the screen as expected with either the Magic Mouse or the > Logitech trackball. > > Starting several weeks ago, wherever the pointer encounters a link the > pointer turns into a pointing hand and is unable to move further into > the screen area occupied by the link. It came move parallel with the > area boundary, and it can invisibly traverse the area to reappear as a > pointer on the other side, but it doesn't move within the link area > (though the link itself still works). > > This occurs with both the M.Mouse and the trackball, but it only occurs > on my wife's account and not on mine (I also use Firefox). I've read of > other people having similar issues the past couple of years, but didn't > notice a fix, nor a positive identification of the cause of this behavior. > > Has anyone here run across this peculiarity, and have some suggestions? On all links on all web pages? Give a URL and mention which link. -- dorayme
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | comp.sys.mac.apps
csiph-web