First thing on the screen after login was a complaint of "unable to
connect to device" with a picture of a camera on it. This sits in front
of any other windows. It further advises "check the I/F cable ..." and
to turn the device off, then on, then try again.
Clicking the OK button does nothing (not even a flicker).
'top' in Terminal shows that 10% to 20% (goes up and down)
of the CPU is sucked up by
/System/Library/Image
Capture/Devices/TWAINBridge.app/Contents/MacOS/TWAINBridge
Killing that removes the complaint dialog.
'ps -aujxx' reveals the PPID is the windowserver, the process
owner is me. The sequence of PIDs suggests a connection with
the "Brother," which is a multifunction fax/copy/scan/print.
I have never had a digital camera hooked to this Mac, but also
I haven't scanned anything on the Brother in months.
Logged out and into my son's account - he gets it too.
Same for the admin account. So it's not a per-user
login item.
Brother.com has a technical question feedback form--which
does not work.
System.log shows that the last four logouts got an error from
TWAINBridgem but no other clues. The earliest such error was
when my son logged out right before I logged in and saw this
the first time.
He remembers no actions to explain it. Looked over his websurfing
history, and saw nothing seeming like a possibility.
I could write a cron script to kill 'TWAINBridge' but I'd much
prefer to learn what started this, how to stop it, and how to
prevent it.
Sound familiar to anyone?
(I'm hunting through Google for "TWAINBridge"
Many hits but so far, no help)

Signature
Wes Groleau
"Lewis's case for the existence of God is fallacious."
"You mean like circular reasoning?"
"He believes in God. Therefore, he's fallacious."
Wes Groleau - 27 Aug 2006 03:39 GMT
> First thing on the screen after login was a complaint of "unable to
> connect to device" with a picture of a camera on it. This sits in front
[quoted text clipped - 10 lines]
> (I'm hunting through Google for "TWAINBridge"
> Many hits but so far, no help)
Poked around on Google some more. Lots of places tell
what TWAINbridge does, but not too many say how it's
triggered, much less what triggers it when it's not
needed.
Anyway, I figured "why not" and rebooted and it's gone.
Perhaps iamge capture has an incoming queue just like print
has an outgoing. (I can turn off the printer, click print,
and log out. When I come back it's still in the queue waiting
to print. Only in the print case, the queue even survives
a reboot.

Signature
Wes Groleau
A pessimist says the glass is half empty.
An optimist says the glass is half full.
An engineer says somebody made the glass
twice as big as it needed to be.
Paul Sture - 30 Aug 2006 08:51 GMT
> Poked around on Google some more. Lots of places tell
> what TWAINbridge does, but not too many say how it's
> triggered, much less what triggers it when it's not
> needed.
I don't know what you dug up via Google, but TWAIN is a protocol
originally designed to provide a common software interface to scanners.
Do you have a scanner connected to your system?

Signature
Paul Sture
Wes Groleau - 31 Aug 2006 02:59 GMT
> I don't know what you dug up via Google, but TWAIN is a protocol
> originally designed to provide a common software interface to scanners.
>
> Do you have a scanner connected to your system?
Yes, I know, and I do (a Brother MFC) but we have
not scanned anything with it for months. However,
I am pretty sure that it has something to do with
this printer/scanner, not only because of the
sequence of processes that started around the same
time, but also because I noticed when this started
happening, when a phone call comes in, the display
that used to always give caller ID now merely says
"call pickup." In other words, someone has messed
with the settings. However, the FAX mode is still
"manual" as before.
Whatever this is, a reboot stops it--for a while.
I can reboot, and log in and out several times.
Then once it starts, it happens on every log in
until another reboot.

Signature
Wes Groleau
"Would the prodigal have gone home if
the elder brother was running the farm?"
-- James Jordan