Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / General / General / June 2006



Tip: Looking for answers? Try searching our database.

Problem: when my computer go to screensaver

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Wes Groleau - 28 Jun 2006 01:13 GMT
Once in a while, our 350MHz G3 iMac gets black screen instead of any
screen saver.  When that happens, we can't get it back.  It isn't
"sleeping" and actually we can get it back by remotely logging in
and carefully killing certain processes.  I don't think it's hardware
because 90% of the occurrences are one one login account.

OS 10.3.9

Signature

Wes Groleau

He that complies against his will is of the same opinion still.
                  -- Samuel Butler, 1612-1680

Alice Faber - 28 Jun 2006 01:28 GMT
> Once in a while, our 350MHz G3 iMac gets black screen instead of any
> screen saver.  When that happens, we can't get it back.  It isn't
[quoted text clipped - 3 lines]
>
> OS 10.3.9

Hmmm...I think a while back there was one particular screen saver I had
to stop using because of that. Does it happen with all the screen
savers, or just a specific one? Some of them are more memory-demanding
than others.

Signature

AF
"Non Sequitur U has a really, really lousy debate team."
             --artyw raises the bar on rec.sport.baseball

Wes Groleau - 28 Jun 2006 04:06 GMT
> Hmmm...I think a while back there was one particular screen saver I had
> to stop using because of that. Does it happen with all the screen
> savers, or just a specific one? Some of them are more memory-demanding
> than others.

When all you have is black, there's no way to identify in 'ps -aux'
which one it was.

Signature

Wes Groleau

   I've noticed lately that the paranoid fear of computers becoming
   intelligent and taking over the world has almost entirely disappeared
   from the common culture.  Near as I can tell, this coincides with
   the release of MS-DOS.
                                 -- Larry DeLuca

Alice Faber - 28 Jun 2006 04:15 GMT
> > Hmmm...I think a while back there was one particular screen saver I had
> > to stop using because of that. Does it happen with all the screen
[quoted text clipped - 3 lines]
> When all you have is black, there's no way to identify in 'ps -aux'
> which one it was.

Huh?

I selected a screen saver. It caused problems. So I selected a different
one.

Signature

AF
"Non Sequitur U has a really, really lousy debate team."
             --artyw raises the bar on rec.sport.baseball

Wes Groleau - 29 Jun 2006 00:41 GMT
>> When all you have is black, there's no way to identify in 'ps -aux'
>> which one it was.
>
> Huh?
> I selected a screen saver. It caused problems. So I selected a different
> one.

They're all available (random).  Yes, of course I can cut back to one
and wait three weeks to see whether nothing happens.  Which I will
likely do.  Was just hoping someone knew something to save me the time.

Alan Baker wrote:
> Try turning on "Remote Login" under the Sharing preference pane. Then
> provided the machine isn't completely hung, you can ssh into it and
> see what's going on...

As I said, remote login is how I do the 'ps -aux'   It tells me
the PID of the screensaver, but not which screensaver it is.
Nor does it say why it does that.

Unfortunately, though, killing the screen saver doesn't give you back
your display.  The only way to avoid reboot is to kill most of the
processes of the logged in user.

On Solaris with CDE, the lockscreen/screensaver process could be
killed by root and everything else would be immediately usable
at the machines local keyboard/display.

I suppose one could call what happens here a security feature,
but I suspect "coincidence" would be more accurate.  :-)

Signature

Wes Groleau

Even if you do learn to speak correct English,
whom are you going to speak it to?
                    -- Clarence Darrow

Alice Faber - 29 Jun 2006 01:46 GMT
> >> When all you have is black, there's no way to identify in 'ps -aux'
> >> which one it was.
[quoted text clipped - 19 lines]
> your display.  The only way to avoid reboot is to kill most of the
> processes of the logged in user.

Have you looked through the various log files to see if there's anything
informative?

Signature

AF
"Non Sequitur U has a really, really lousy debate team."
             --artyw raises the bar on rec.sport.baseball

Wes Groleau - 30 Jun 2006 03:12 GMT
> Have you looked through the various log files to see if there's anything
> informative?

Nothing that shouts "Screensaver" There are a few graphics
related things, but they're all during boot up.

Some of them don't quite shout, but raise their voice
a little to say "Somebody at Apple is lazy"

Signature

Wes Groleau

Always listen to experts.  They'll tell you
what can't be done and why.  Then do it.
                    -- Robert A. Heinlein

Alan Baker - 28 Jun 2006 08:20 GMT
> > Hmmm...I think a while back there was one particular screen saver I had
> > to stop using because of that. Does it happen with all the screen
[quoted text clipped - 3 lines]
> When all you have is black, there's no way to identify in 'ps -aux'
> which one it was.

Try turning on "Remote Login" under the Sharing preference pane. Then
provided the machine isn't completely hung, you can ssh into it and see
what's going on...
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.