Hmm ... I use a Logitech wireless mouse and have not seen this problem. We use a wide variety of mices around the office here (Logitech, Dell, Microsoft, Dynex) and have not seen either.
Regarding the log file: this changed in 0.6. The command Martin supplied no longer works. If you run Shotwell like this: % SHOTWELL_LOG=1 shotwell You'll get a log file written to ~/.cache/shotwell/shotwell.log If you could attach that to this report, that could be useful. Also, does your Kensington mouse have any special software installed for it (i.e. mouse assistants, notifiers, mouse button mappers, etc.)? Or are you using special drivers? The original reporter speculated we poll the USB bus. This is technically incorrect. We use gudev to notify us when USB devices are added and removed in order to monitor for cameras. Now, gudev might be polling (although I doubt it). 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. Looking over your dmesg.txt, I see this repeated every two seconds or so: [ 4744.513164] usb 1-1.1: usbfs: USBDEVFS_CONTROL failed cmd shotwell rqt 128 rq 6 len 1000 ret -110 [ 4744.708903] usb 1-1.1: USB disconnect, address 62 [ 4744.936150] usb 1-1.1: new low speed USB device using ehci_hcd and address 63 [ 4745.036249] usb 1-1.1: configuration #1 chosen from 1 choice [ 4745.040817] input: Kensington Kensington Ci75m Wireless Notebook Mouse as /devices/pci0000:00/0000:00:1d.7/usb1/1-1/1-1.1/1-1.1:1.0/input/input183 [ 4745.041075] generic-usb 0003:047D:1048.00AE: input,hidraw3: USB HID v1.10 Mouse [Kensington Kensington Ci75m Wireless Notebook Mouse] on usb-0000:00:1d.7-1.1/input0 I've been unable to find a definitive reference for the meaning of the -110 return code on the first line, but I've seen on message boards where people say it's a USB time-out. Also, I don't see the Kensington mouse anywhere in the lsusb output you attached. The only mouse-type device in the list is the Apple Keyboard (does it have a trackpad on it?). When you made this log, where was the mouse attached? -- Shotwell makes USB mouse flaky https://bugs.launchpad.net/bugs/555408 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
