Comment 6 for bug 555408

Hi Jim,

I don't see this problem with a wired Logitech, or Bluetooth MS mouse. It only seems to affect my Kensington mouse.
No special drivers, or anything for the Kensington mouse.

Please find new lsusb (Line 612) and shotwell log files attached.

I attached two Shotwell logs, one with the Kensington mouse attached (shotwell_with_kensington_mouse.log), another without the Kensington mouse (shotwell_no_kensington_mouse.log).

I think, you were right with your assumption:

  "When gudev reports of a device attach/detach, Shotwell will scan the device bus looking for all camera-looking devices to
   determine what's been added or removed. It's this step I'm thinking is causing a problem. However, it should only happen
   when a device is added or removed (it does *not* happen continuously). I'm concerned that it's this step that's causing issues,
   perhaps because the mouse is not responding (or responding in an unusual way) and that either Shotwell or gudev keeps
   pinging it for information."

I see these lines in the shotwell log file when the Kensington mouse is attached

L 8435 2010-07-10 15:57:15 [DBG] CameraTable.vala:315: udev event: remove on 1-1.4.2:1.0
L 8435 2010-07-10 15:57:15 [DBG] CameraTable.vala:315: udev event: remove on 1-1.4.2
L 8435 2010-07-10 15:57:15 [DBG] CameraTable.vala:315: udev event: add on 1-1.4.2
L 8435 2010-07-10 15:57:15 [DBG] CameraTable.vala:315: udev event: add on 1-1.4.2:1.0

BR// Rupert