Ever since installing openSuse 10.3 (I am using 11.0 now), when I do a normal shut down of my desktop system at the end of the day, when the computer turns off, sometimes my printer starts up as if it is going to print a page.
No printed material comes out of the printer because as quickly as it starts up, it stops and just runs its internal fan to cool the laser element for about 10 minutes, then turns off completely.
This does not happen after every system shut down.
It seems to happen only if I have printed something during the current session/day.
This is just a nuisance but I wish someone could tell me were to look in a config file or whatever to fix this problem.
> Ever since installing openSuse 10.3 (I am using 11.0 now), when I do a
> normal shut down of my desktop system at the end of the day, when the
> computer turns off, sometimes my printer starts up as if it is going to
> print a page.
>
> No printed material comes out of the printer because as quickly as it
> starts up, it stops and just runs its internal fan to cool the laser
> element for about 10 minutes, then turns off completely.
>
> This does not happen after every system shut down.
> It seems to happen only if I have printed something during the current
> session/day.
>
> This is just a nuisance but I wish someone could tell me were to look
> in a config file or whatever to fix this problem.
Might be something as simple as a stream getting closed, after use to
address the printer. The equivalent to the EOF, in a way.
I doubt you’ll be able to remove that behaviour, but obviously I hope
someone proves me wrong.
Could you please give brand/model of that printer?
Ad maybe the way you connect to it (IPP, lpr, centronics, usb, …) ?
–
The sand remembers once there was beach and sunshine
but chip is warm too
– haiku from Effector Online, Volume 1, Number 6
I have a Brother HL-5040 B&W laser printer connected via USB.
It is also connected to my Window$ computer via Centronics, (I control both computers via a KVM switch) but this computer is used only occasionally and is not on when this problem occurs and typically has not been on during the session when I see this problem.
(BTW, turning the Window$ machine off, while my Suse box is on, does not produce this phenomenon.)
Regarding your idea that it is a closing of a stream.
That is possible, but the actual “signal” seems to come after all services have switched to run level 0, at the moment the power supply shuts off.
I did not think there were any active programs at that point to send any kind of data/signal.
Obviously there is SOMETHING still active enough at that point to send out one last bit.