Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.mac.system > #58342 > unrolled thread
| Started by | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| First post | 2014-04-05 18:07 -0400 |
| Last post | 2014-04-19 10:12 -0400 |
| Articles | 20 on this page of 77 — 18 participants |
Back to article view | Back to comp.sys.mac.system
Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-05 18:07 -0400
Re: Dock won't pop up Warren Oates <warren.oates@gmail.com> - 2014-04-06 07:37 -0400
Re: Dock won't pop up dorayme <do_ray_me@bigpond.com> - 2014-04-07 10:36 +1000
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-07 16:47 -0400
Re: Dock won't pop up John McWilliams <jpmcw@comcast.net> - 2014-04-07 15:44 -0700
Re: Dock won't pop up dorayme <do_ray_me@bigpond.com> - 2014-04-08 10:37 +1000
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-08 17:09 -0400
Re: Dock won't pop up John McWilliams <jpmcw@comcast.net> - 2014-04-12 18:57 -0700
Re: Dock won't pop up dorayme <do_ray_me@bigpond.com> - 2014-04-13 13:07 +1000
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-13 09:31 -0400
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-13 09:31 -0400
Re: Dock won't pop up android <here@there.was> - 2014-04-13 16:58 +0200
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-13 12:08 -0400
Re: Dock won't pop up android <here@there.was> - 2014-04-13 18:25 +0200
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-13 12:28 -0400
Re: Dock won't pop up Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-16 13:29 +0000
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-16 17:10 -0400
Re: Dock won't pop up JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-04-16 17:34 -0400
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-16 18:20 -0400
Re: Dock won't pop up Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-16 23:59 +0000
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-17 15:02 -0400
Re: Dock won't pop up JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-04-16 17:37 -0400
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-16 18:20 -0400
Re: Dock won't pop up Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-17 00:01 +0000
Re: Dock won't pop up JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-04-13 16:00 -0400
Re: Dock won't pop up Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-16 13:28 +0000
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-16 17:02 -0400
Re: Dock won't pop up Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-16 13:26 +0000
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-08 17:08 -0400
Re: Dock won't pop up Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-09 14:46 +0000
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-09 20:59 -0400
Re: Dock won't pop up Dorian Grey <oscar@wild.net> - 2014-04-06 10:10 -0400
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-06 11:07 -0400
Re: Dock won't pop up billy@MIX.COM - 2014-04-06 15:23 +0000
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-06 11:46 -0400
Re: Dock won't pop up billy@MIX.COM - 2014-04-07 01:54 +0000
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-07 16:47 -0400
Re: Dock won't pop up Your Name <YourName@YourISP.com> - 2014-04-07 09:01 +1200
Re: Dock won't pop up JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-04-06 16:40 -0400
Re: Dock won't pop up David Ritz <dritz@mindspring.com> - 2014-04-06 17:24 -0500
Re: Dock won't pop up Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-04-06 17:20 +0000
Re: Dock won't pop up Paul Sture <nospam@sture.ch> - 2014-04-06 20:16 +0200
Re: Dock won't pop up doctor@doctor.nl2k.ab.ca (The Doctor) - 2014-04-06 20:29 +0000
Re: Dock won't pop up billy@MIX.COM - 2014-04-07 01:57 +0000
Re: Dock won't pop up Your Name <YourName@YourISP.com> - 2014-04-07 16:05 +1200
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-07 16:50 -0400
Re: Dock won't pop up russotto@grace.speakeasy.net (Matthew Russotto) - 2014-04-09 02:46 +0000
Re: Dock won't pop up JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-04-06 16:42 -0400
Re: Dock won't pop up Warren Oates <warren.oates@gmail.com> - 2014-04-06 18:28 -0400
Re: Dock won't pop up Dorian Grey <oscar@wild.net> - 2014-04-06 19:23 -0400
Re: Dock won't pop up JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-04-06 19:38 -0400
Re: Dock won't pop up Paul Sture <nospam@sture.ch> - 2014-04-07 20:55 +0200
Re: Dock won't pop up Your Name <YourName@YourISP.com> - 2014-04-08 08:47 +1200
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-06 20:36 -0400
Re: Dock won't pop up Dorian Grey <oscar@wild.net> - 2014-04-07 10:18 -0400
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-07 16:54 -0400
Re: Dock won't pop up JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-04-07 17:17 -0400
Re: Dock won't pop up Warren Oates <warren.oates@gmail.com> - 2014-04-07 18:12 -0400
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-07 18:38 -0400
Re: Dock won't pop up Warren Oates <warren.oates@gmail.com> - 2014-04-07 19:10 -0400
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-08 17:09 -0400
Re: Dock won't pop up Dorian Grey <oscar@wild.net> - 2014-04-07 19:45 -0400
Re: Dock won't pop up Ted Lee <tmplee@gmail.com> - 2014-04-08 08:03 -0500
Re: Dock won't pop up Your Name <YourName@YourISP.com> - 2014-04-09 09:03 +1200
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-08 17:14 -0400
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-08 17:12 -0400
Re: Dock won't pop up Dorian Grey <oscar@wild.net> - 2014-04-09 10:18 -0400
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-09 20:58 -0400
Re: Dock won't pop up Jolly Roger <jollyroger@pobox.com> - 2014-04-10 01:54 +0000
Re: Dock won't pop up Barry OGrady <atheist@hotmail.com.au> - 2014-04-19 13:34 +1000
Re: Dock won't pop up Your Name <YourName@YourISP.com> - 2014-04-19 16:29 +1200
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-19 09:42 -0400
Re: Dock won't pop up Michelle Steiner <michelle@michelle.org> - 2014-04-19 06:50 -0700
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-19 09:59 -0400
Re: Dock won't pop up Michelle Steiner <michelle@michelle.org> - 2014-04-19 07:51 -0700
Re: Dock won't pop up Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-19 11:00 -0400
Re: Dock won't pop up Warren Oates <warren.oates@gmail.com> - 2014-04-19 10:12 -0400
Page 2 of 4 — ← Prev page 1 [2] 3 4 Next page →
| From | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| Date | 2014-04-17 15:02 -0400 |
| Message-ID | <TI2dnczvNY65uM3OnZ2dnUVZ_gWdnZ2d@giganews.com> |
| In reply to | #58584 |
On 2014.04.16, 19:59 , Lewis wrote:
> In message <534ef778$0$17053$c3e8da3$dd9697d2@news.astraweb.com>
> JF Mezei <jfmezei.spamnot@vaxination.ca> wrote:
>> On 14-04-16 17:10, Alan Browne wrote:
>
>>> All timer coalescing does is group time based events into a coarser
>>> schedule to reduce the number of idle2wake transitions. This is
>>> beneficial in terms of power draw at a level that is important for
>>> battery driven laptops but hardly significant to a desktop machine.
>
>
>> It also depends on what type of aplications you run. If you are running
>> a real time collection of data or controlling machinery, you don't want
>> the OS to delay delivery of any timed events. But if you are doing word
>> processing, you don't care if the clock skips a second because one timer
>> event was "coalesced" and by the time it was delivered, another second
>> had passed.
>
> This might be an issue if it was a second. It's not, it's 1/1000th of a
> second or maybe 1/100th of a second.
1/100th I believe since that is the is the OS time slice period. The
graph on the Apple page suggests coalescing is even coarser than that
(but that just might be for illustration purposes so not sure). If it
as coarse as Apple's graphic it would not be suitable for real time
purposes and could cause issues with some apps and possibly VM's.
--
"Big data can reduce anything to a single number,
but you shouldn’t be fooled by the appearance of exactitude."
-Gary Marcus and Ernest Davis, NYT, 2014.04.07
[toc] | [prev] | [next] | [standalone]
| From | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| Date | 2014-04-16 17:37 -0400 |
| Message-ID | <534ef81e$0$17053$c3e8da3$dd9697d2@news.astraweb.com> |
| In reply to | #58576 |
On 14-04-16 17:10, Alan Browne wrote: > All timer coalescing does is group time based events into a coarser > schedule to reduce the number of idle2wake transitions. I am told the Apple target market is hipsters who spend all day at Starbucks sipping coffee and showing off their fancy Apple laptops. For that target market, timer coalescing would likely have no visible impact. However, if you are a recording professional, or videographer, you probably do notice such things. (consider timecode insertion by time instead of frames, you want the timer to be procise).
[toc] | [prev] | [next] | [standalone]
| From | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| Date | 2014-04-16 18:20 -0400 |
| Message-ID | <KcmdnZkLqua-n9LOnZ2dnUVZ_qudnZ2d@giganews.com> |
| In reply to | #58579 |
On 2014.04.16, 17:37 , JF Mezei wrote:
> On 14-04-16 17:10, Alan Browne wrote:
>
>> All timer coalescing does is group time based events into a coarser
>> schedule to reduce the number of idle2wake transitions.
>
> However, if you are a recording professional, or videographer, you
> probably do notice such things. (consider timecode insertion by time
> instead of frames, you want the timer to be procise).
That depends on the source of timemarks. If they are generated by the
external equipment (as they should be) then those stamps drive the
content - not when things are actually processed. For that matter
processed frames take more or less time than realtime - so coalescing is
irrelevant to content.
--
"Big data can reduce anything to a single number,
but you shouldn’t be fooled by the appearance of exactitude."
-Gary Marcus and Ernest Davis, NYT, 2014.04.07
[toc] | [prev] | [next] | [standalone]
| From | Lewis <g.kreme@gmail.com.dontsendmecopies> |
|---|---|
| Date | 2014-04-17 00:01 +0000 |
| Message-ID | <slrnlku6f9.1b7j.g.kreme@amelia.local> |
| In reply to | #58579 |
In message <534ef81e$0$17053$c3e8da3$dd9697d2@news.astraweb.com> JF Mezei <jfmezei.spamnot@vaxination.ca> wrote: > On 14-04-16 17:10, Alan Browne wrote: >> All timer coalescing does is group time based events into a coarser >> schedule to reduce the number of idle2wake transitions. > I am told the Apple target market is hipsters who spend all day at > Starbucks sipping coffee and showing off their fancy Apple laptops. For > that target market, timer coalescing would likely have no visible impact. > However, if you are a recording professional, or videographer, you > probably do notice such things. (consider timecode insertion by time > instead of frames, you want the timer to be procise). You have *NO* idea what you are talking about. Coalescing has nothing to do with any of that an no, it would not impact it in the slightest. It does affect the simulator for iOS 6 in Xcode, probably because that simulator was written with certain (bad) assumptions. However, since it's for an obsolete OS it is not that big a deal, and becoming an even lesser deal every day. -- WORDS IN THE HEART CANNOT BE TAKEN --Feet of Clay
[toc] | [prev] | [next] | [standalone]
| From | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| Date | 2014-04-13 16:00 -0400 |
| Message-ID | <534aece1$0$9243$c3e8da3$9f400e27@news.astraweb.com> |
| In reply to | #58521 |
If the Dock keeps in hiding, perhaps it is not a physical problem but an emotional one with the Dock affraid to come out of hiding and showing itself. Suggest you get a phychotherapist to analyse the Dock's problem and why it is so shy and affraid to come out of hiding. Lack if self confidence could be a serious issue, especially when in the past, many have criticised the Dock's appearance. Perhaps it is shy because of it's icon's size, and if you made the icons bigger, it wouldn't be affraid. Despite users always saying that the size of the icon doesn't matter, it is how you use it that counts, every process knows that the size of the icon does matter. Or perhaps it is busy "interfacing" with a female process with large stacks and can't really come out and reveal itself in its current state. And if you were like Austin Powers and busy with inter-process exchanges with 2 twin japanese processes, would you interrupt that activity because the user's mouse was hovering near you ?
[toc] | [prev] | [next] | [standalone]
| From | Lewis <g.kreme@gmail.com.dontsendmecopies> |
|---|---|
| Date | 2014-04-16 13:28 +0000 |
| Message-ID | <slrnlkt1b6.m1e.g.kreme@amelia.local> |
| In reply to | #58521 |
In message <hrWdnZHK8t0UK9fOnZ2dnUVZ_hsAAAAA@giganews.com> Alan Browne <alan.browne@FreelunchVideotron.ca> wrote: > Ironically while I've installed luxury levels of memory, Mavericks > introduced new, more efficient memory management. And compression that > I would just as soon turn off on this iMac - yes, it's CPU efficient, > but I don't really need it at all. (Currently @ 2.1 MB - less than > 1/100 of a percent of installed memory). > So, just before I posted this, I went into interwebverse and found a way > to turn off memory compression. Other post with details posted. You tuned off memory compression for absolutely no reason? -- I draw the line at 7 unreturned phone calls.
[toc] | [prev] | [next] | [standalone]
| From | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| Date | 2014-04-16 17:02 -0400 |
| Message-ID | <ivGdnYgpFZtLctPOnZ2dnUVZ_vadnZ2d@giganews.com> |
| In reply to | #58566 |
On 2014.04.16, 09:28 , Lewis wrote:
> In message <hrWdnZHK8t0UK9fOnZ2dnUVZ_hsAAAAA@giganews.com>
> Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
>> Ironically while I've installed luxury levels of memory, Mavericks
>> introduced new, more efficient memory management. And compression that
>> I would just as soon turn off on this iMac - yes, it's CPU efficient,
>> but I don't really need it at all. (Currently @ 2.1 MB - less than
>> 1/100 of a percent of installed memory).
>
>> So, just before I posted this, I went into interwebverse and found a way
>> to turn off memory compression. Other post with details posted.
>
> You tuned off memory compression for absolutely no reason?
I turned it off because there is no reason to have it active.
--
"Big data can reduce anything to a single number,
but you shouldn’t be fooled by the appearance of exactitude."
-Gary Marcus and Ernest Davis, NYT, 2014.04.07
[toc] | [prev] | [next] | [standalone]
| From | Lewis <g.kreme@gmail.com.dontsendmecopies> |
|---|---|
| Date | 2014-04-16 13:26 +0000 |
| Message-ID | <slrnlkt189.m1e.g.kreme@amelia.local> |
| In reply to | #58519 |
In message <bqvmvpFk7ldU1@mid.individual.net> android <here@there.was> wrote: > In article <77KdncRtxpMCDNfOnZ2dnUVZ_hOdnZ2d@giganews.com>, > Alan Browne <alan.browne@FreelunchVideotron.ca> wrote: >> On 2014.04.12, 21:57 , John McWilliams wrote: >> > On 4/8/14 PDT, 2:09 PM, Alan Browne wrote: >> >> On 2014.04.07, 20:37 , dorayme wrote: >> >>> In article <lhv9o0$hr8$1@dont-email.me>, >> >>>> >> >>>> What makes you take steps to avoid restarting a computer? Often >> >>>> enough a >> >>>> restart does good things. >> >>> >> >>> Puzzled me too, a restart is like opening the window to a good breeze >> >>> when someone has farted. >> >> >> >> For MS Windows I agree. >> >> >> >> OS' that need a reboot for "freshness" are flawed. >> >> >> > Ah, so you're the Christian Scientist of Macdom! >> >> I'm just a rational user who has a stable OS that runs w/o issues or >> memory leaks (that in part is I don't seem to have apps that leak much). >> I'm certainly not the only one who does this. > I would agree since i sometimes only reboot the putter once a week or > so, but... > If you've managed to generate a lot of swap then it' can be a good idea > to reboot since the OSX do not eat back the swaps that promptly after > the apps that craved them have been closed and the removal of those > swaps seem to speed up things quite a bit. > Oki, I'm on SL here and fresher cats and cattle might behave differently. I'm pretty happy: $ ll /var/vm/ total 10616832 2097152 -rw------- 1 root wheel 1.0G Mar 18 07:55 swapfile1 131072 -rw------- 1 root wheel 64M Mar 18 07:55 swapfile0 8388608 -rw------T 1 root wheel 4.0G Apr 16 06:01 sleepimage ~/ $ uptime 7:25 up 28 days, 23:30, 4 users, load averages: 2.84 1.91 1.78 -- 'Ah... I see that the new traffic division is having the desired effect.' He indicated a large pile of paper. 'I am getting any amount of complaints from the Carters' and Drovers' Guild. Well done. Do pass on my thanks to Sergeant Colon and his team.' 'I will, sir.' 'I see in one day they clamped seventeen carts, ten horses, eighteen oxen and one duck.' 'It was parked illegally, sir.'
[toc] | [prev] | [next] | [standalone]
| From | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| Date | 2014-04-08 17:08 -0400 |
| Message-ID | <nMednWGIHvT_-NnOnZ2dnUVZ_vmdnZ2d@giganews.com> |
| In reply to | #58389 |
On 2014.04.07, 18:44 , John McWilliams wrote:
> On 4/7/14 PDT, 1:47 PM, Alan Browne wrote:
>> On 2014.04.06, 20:36 , dorayme wrote:
>>> In article <53413c5d$0$46052$c3e8da3$88b277c5@news.astraweb.com>,
>>> Warren Oates <warren.oates@gmail.com> wrote:
>>>
>>>> In article <hfCdnYJ-yqYx493OnZ2dnUVZ_q6dnZ2d@giganews.com>,
>>>> Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
>>>>
>>>>> I haven't seen this happen in a very long time - but my Dock froze
>>>>> (would not pop up).
>>>>>
>>>>> After a bit of bumping around I CMD-Tabbed to Finder, did "About
>>>>> Finder"
>>>>> and then it worked. (Nothing else did).
>>>>
>>>> This is a bit obscure, but when that happened to me once, it was
>>>> because
>>>> the mouse had lost the ability to "hover" (I'm assuming you mean
>>>> that it
>>>> wouldn't pop up when you moused over it). Unplugging and replugging the
>>>> mouse fixed it. There were also other hover operations that I couldn't
>>>> perform, but I disremember right now what they were.
>>>
>>> I have had this problem now and then. A restart fixes generally.
>>
>> Not needed in this case. As much as possible I avoid restarting my
>> computer if there is a fix that will work. The problem is finding the
>> fix.
>
> What makes you take steps to avoid restarting a computer? Often enough a
> restart does good things.
When it's something stuck as Finder gets from time to time (or the dock
as I originally posted) I can usually get it sorted out quickly enough
that I can avoid a reboot (whether by learned trick or fumbling around).
I don't boot my computer unless I need to (and I did last week due to
a s/w install - it was "recommended" by the vendor). But often my
computer goes weeks to even months w/o a reboot.
--
"Big data can reduce anything to a single number,
but you shouldn’t be fooled by the appearance of exactitude."
-Gary Marcus and Ernest Davis, NYT, 2014.04.07
[toc] | [prev] | [next] | [standalone]
| From | Lewis <g.kreme@gmail.com.dontsendmecopies> |
|---|---|
| Date | 2014-04-09 14:46 +0000 |
| Message-ID | <slrnlkanag.36k.g.kreme@amelia.local> |
| In reply to | #58404 |
In message <nMednWGIHvT_-NnOnZ2dnUVZ_vmdnZ2d@giganews.com> Alan Browne <alan.browne@FreelunchVideotron.ca> wrote: > On 2014.04.07, 18:44 , John McWilliams wrote: >> On 4/7/14 PDT, 1:47 PM, Alan Browne wrote: >>> On 2014.04.06, 20:36 , dorayme wrote: >>>> In article <53413c5d$0$46052$c3e8da3$88b277c5@news.astraweb.com>, >>>> Warren Oates <warren.oates@gmail.com> wrote: >>>> >>>>> In article <hfCdnYJ-yqYx493OnZ2dnUVZ_q6dnZ2d@giganews.com>, >>>>> Alan Browne <alan.browne@FreelunchVideotron.ca> wrote: >>>>> >>>>>> I haven't seen this happen in a very long time - but my Dock froze >>>>>> (would not pop up). >>>>>> >>>>>> After a bit of bumping around I CMD-Tabbed to Finder, did "About >>>>>> Finder" >>>>>> and then it worked. (Nothing else did). >>>>> >>>>> This is a bit obscure, but when that happened to me once, it was >>>>> because >>>>> the mouse had lost the ability to "hover" (I'm assuming you mean >>>>> that it >>>>> wouldn't pop up when you moused over it). Unplugging and replugging the >>>>> mouse fixed it. There were also other hover operations that I couldn't >>>>> perform, but I disremember right now what they were. >>>> >>>> I have had this problem now and then. A restart fixes generally. >>> >>> Not needed in this case. As much as possible I avoid restarting my >>> computer if there is a fix that will work. The problem is finding the >>> fix. >> >> What makes you take steps to avoid restarting a computer? Often enough a >> restart does good things. > When it's something stuck as Finder gets from time to time (or the dock > as I originally posted) I can usually get it sorted out quickly enough > that I can avoid a reboot (whether by learned trick or fumbling around). > I don't boot my computer unless I need to (and I did last week due to > a s/w install - it was "recommended" by the vendor). But often my > computer goes weeks to even months w/o a reboot. My laptop: $ uptime 8:46 up 22 days, 51 mins, 4 users, load averages: 1.85 1.91 1.80 -- It was sad music. But it waved its sadness like a battle flag. It said the universe had done all it could, but you were still alive.
[toc] | [prev] | [next] | [standalone]
| From | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| Date | 2014-04-09 20:59 -0400 |
| Message-ID | <Cf-dneptHulDcdjOnZ2dnUVZ_o8AAAAA@giganews.com> |
| In reply to | #58423 |
On 2014.04.09, 10:46 , Lewis wrote:
> In message <nMednWGIHvT_-NnOnZ2dnUVZ_vmdnZ2d@giganews.com>
> Alan Browne <alan.browne@FreelunchVideotron.ca> wrote:
>> When it's something stuck as Finder gets from time to time (or the dock
>> as I originally posted) I can usually get it sorted out quickly enough
>> that I can avoid a reboot (whether by learned trick or fumbling around).
>> I don't boot my computer unless I need to (and I did last week due to
>> a s/w install - it was "recommended" by the vendor). But often my
>> computer goes weeks to even months w/o a reboot.
>
> My laptop:
> $ uptime
> 8:46 up 22 days, 51 mins, 4 users, load averages: 1.85 1.91 1.80
Sure. I've had this Mac go close to 2 months, but eventually something
comes around that I need to reboot. My SO's MBA is more likely to go
longer (and has) because we don't install s/w there much anymore.
--
"Big data can reduce anything to a single number,
but you shouldn’t be fooled by the appearance of exactitude."
-Gary Marcus and Ernest Davis, NYT, 2014.04.07
[toc] | [prev] | [next] | [standalone]
| From | Dorian Grey <oscar@wild.net> |
|---|---|
| Date | 2014-04-06 10:10 -0400 |
| Message-ID | <lhrn8u$fas$1@news.albasani.net> |
| In reply to | #58342 |
On 4/5/14, 6:07 PM, Alan Browne wrote: > > I haven't seen this happen in a very long time - but my Dock froze > (would not pop up). > > After a bit of bumping around I CMD-Tabbed to Finder, did "About Finder" > and then it worked. (Nothing else did). > A cold reboot can clear out a jam-up like that. Dumping the PRAM and resetting the system management controller could straighten you out too. -- The difference between stupidity and genius is that genius has its limits. —Albert Einstein
[toc] | [prev] | [next] | [standalone]
| From | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| Date | 2014-04-06 11:07 -0400 |
| Message-ID | <bYmdnYFeJNRb8NzOnZ2dnUVZ_sudnZ2d@giganews.com> |
| In reply to | #58356 |
On 2014.04.06, 10:10 , Dorian Grey wrote:
> On 4/5/14, 6:07 PM, Alan Browne wrote:
>>
>> I haven't seen this happen in a very long time - but my Dock froze
>> (would not pop up).
>>
>> After a bit of bumping around I CMD-Tabbed to Finder, did "About Finder"
>> and then it worked. (Nothing else did).
>>
>
> A cold reboot can clear out a jam-up like that. Dumping the PRAM and
> resetting the system management controller could straighten you out too.
I'm not going to cold boot when there are other options (such as doing
something in Finder that is probably unrelated but results in something
being changed to a state where the dock then becomes responsive).
I'm just surprised that such mis-behaviours still exist in OS X.
Last night I also had a random brief dock appearance while watching a
movie on Netflix (Mac->AirPlay->AppleTV->Television).
I had seen this occur a few times immediately after installing 10.9.
(Ironically, I was watching the "Jobs" movie...).
--
Privacy has become an essential personal chore that most
people are not trained to perform.
- Jaron Lanier, Scientific American, 2013.11.
[toc] | [prev] | [next] | [standalone]
| From | billy@MIX.COM |
|---|---|
| Date | 2014-04-06 15:23 +0000 |
| Message-ID | <lhrrhv$5bf$1@reader2.panix.com> |
| In reply to | #58358 |
Alan Browne <alan.browne@freelunchvideotron.ca> writes:
> I'm just surprised that such mis-behaviours still exist in OS X.
Yes, it's sad that bug fixes are not given the attention they deserve.
Billy Y..
--
sub #'9+1 ,r0 ; convert ascii byte
add #9.+1 ,r0 ; to an integer
bcc 20$ ; not a number
[toc] | [prev] | [next] | [standalone]
| From | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| Date | 2014-04-06 11:46 -0400 |
| Message-ID | <M-GdnW1t4d8j69zOnZ2dnUVZ_uidnZ2d@giganews.com> |
| In reply to | #58359 |
On 2014.04.06, 11:23 , billy@MIX.COM wrote:
> Alan Browne <alan.browne@freelunchvideotron.ca> writes:
>
>> I'm just surprised that such mis-behaviours still exist in OS X.
>
> Yes, it's sad that bug fixes are not given the attention they deserve.
Bugs such as this go into databases (bug trackers) which assign various
weights to parameters around the issue (criticality, frequency of
occurrence, workaround, effect on the user, cost to fix, opportunity
cost, availability of resources, etc.).
The bug I describe is infrequent. I know enough to fool around with
various things that might 'release' it. But I know a lot of people (my
SO, one of my buddies, etc.) who would be flummoxed and would likely
re-start their computer in a good or bad way.
--
Those who have reduced our privacy, whether they are state
or commercial actors, prefer that we do not reduce theirs.
- Jaron Lanier, Scientific American, 2013.11.
[toc] | [prev] | [next] | [standalone]
| From | billy@MIX.COM |
|---|---|
| Date | 2014-04-07 01:54 +0000 |
| Message-ID | <lht0g3$51u$2@reader2.panix.com> |
| In reply to | #58360 |
Alan Browne <alan.browne@freelunchvideotron.ca> writes:
> The bug I describe is infrequent. I know enough to fool around with
> various things that might 'release' it. But I know a lot of people (my
> SO, one of my buddies, etc.) who would be flummoxed and would likely
> re-start their computer in a good or bad way.
Having crashed one of my 10.9.2 machines several times today,
I can say the filesystem journaling is working quite well. I
even get an offer to restart all the programs, which I did try
once just to see how that worked (also quite well).
Billy Y..
--
sub #'9+1 ,r0 ; convert ascii byte
add #9.+1 ,r0 ; to an integer
bcc 20$ ; not a number
[toc] | [prev] | [next] | [standalone]
| From | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| Date | 2014-04-07 16:47 -0400 |
| Message-ID | <SeSdnR7a1LR7k97OnZ2dnUVZ_sidnZ2d@giganews.com> |
| In reply to | #58376 |
On 2014.04.06, 21:54 , billy@MIX.COM wrote:
> Alan Browne <alan.browne@freelunchvideotron.ca> writes:
>
>> The bug I describe is infrequent. I know enough to fool around with
>> various things that might 'release' it. But I know a lot of people (my
>> SO, one of my buddies, etc.) who would be flummoxed and would likely
>> re-start their computer in a good or bad way.
>
> Having crashed one of my 10.9.2 machines several times today,
> I can say the filesystem journaling is working quite well. I
> even get an offer to restart all the programs, which I did try
> once just to see how that worked (also quite well).
Bittersweet success I suppose.
--
"Big data can reduce anything to a single number,
but you shouldn’t be fooled by the appearance of exactitude."
-Gary Marcus and Ernest Davis, NYT, 2014.04.07
[toc] | [prev] | [next] | [standalone]
| From | Your Name <YourName@YourISP.com> |
|---|---|
| Date | 2014-04-07 09:01 +1200 |
| Message-ID | <070420140901266205%YourName@YourISP.com> |
| In reply to | #58359 |
In article <lhrrhv$5bf$1@reader2.panix.com>, <billy@MIX.COM> wrote: > Alan Browne <alan.browne@freelunchvideotron.ca> writes: > > > > I'm just surprised that such mis-behaviours still exist in OS X. > > Yes, it's sad that bug fixes are not given the attention they deserve. It may not even be a Mac OS X issue, but a bug in whatever other software may be running at the time. I get a "Dock no-show" occasionally in Mac OS X 10.1 and 10.2 when Firefox is "busy" doing something or other, but eventually it finishes and the Dock reappears.
[toc] | [prev] | [next] | [standalone]
| From | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| Date | 2014-04-06 16:40 -0400 |
| Message-ID | <5341bbd9$0$2722$c3e8da3$66d3cc2f@news.astraweb.com> |
| In reply to | #58358 |
On 14-04-06 11:07, Alan Browne wrote: > I'm not going to cold boot when there are other options (such as doing > something in Finder that is probably unrelated but results in something > being changed to a state where the dock then becomes responsive). I've had Dock be unrespnsive a few times. (Mine is always on, I find the "on/off very annoying when you work near it). Activity Monitor: select "Dock" , "Quit process". (either gentle quit or if that doesn't work, Force Quit). Can't remember if Launchd monitors Dock and restarts it automatically within a few minutes or if you have to restart manually. In later case, it is in the /System/Library/CoreServices/Dock.App
[toc] | [prev] | [next] | [standalone]
| From | David Ritz <dritz@mindspring.com> |
|---|---|
| Date | 2014-04-06 17:24 -0500 |
| Message-ID | <alpine.OSX.2.11.1404061720160.46517@mako.ath.cx> |
| In reply to | #58365 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday, 06 April 2014 16:40 -0400,
in article <5341bbd9$0$2722$c3e8da3$66d3cc2f@news.astraweb.com>,
JF Mezei <jfmezei.spamnot@vaxination.ca> wrote:
> On 14-04-06 11:07, Alan Browne wrote:
>> I'm not going to cold boot when there are other options (such as
>> doing something in Finder that is probably unrelated but results in
>> something being changed to a state where the dock then becomes
>> responsive).
> I've had Dock be unrespnsive a few times. (Mine is always on, I
> find the "on/off very annoying when you work near it).
> Activity Monitor: select "Dock" , "Quit process". (either gentle
> quit or if that doesn't work, Force Quit).
This is easily accomplished from the commandline.
killall Dock
> Can't remember if Launchd monitors Dock and restarts it
> automatically within a few minutes or if you have to restart
> manually. In later case, it is in the
The Dock relaunches, automatically. The DashboardClient does not.
- --
David Ritz <dritz@mindspring.com>
Be kind to animals; kiss a shark.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (Darwin)
iEYEARECAAYFAlNB1DUACgkQUrwpmRoS3uusQACgmgcvC7p0VJ+nyRsXNOlrr8pE
4sQAoKqy6HAGSQudVMr4bI8OB0bdkUaS
=zoNL
-----END PGP SIGNATURE-----
[toc] | [prev] | [next] | [standalone]
Page 2 of 4 — ← Prev page 1 [2] 3 4 Next page →
Back to top | Article view | comp.sys.mac.system
csiph-web