Bug #2269

Kensington mouse and other USB devices make Shotwell unusable

Added by Adam Dingle almost 3 years ago. Updated 24 days ago.

Status:Invalid Start date:07/13/2010
Priority:High Due date:
Assignee:Jim Nelson % Done:

0%
Category:-
Target version:-
Keywords:

Description

A couple of users have reported trouble using Shotwell with a Kensington mouse:

https://bugs.launchpad.net/ubuntu/source/shotwell/bug/555408

Not sure whether this is really our fault, but the mouse is cheap so we may as well order one and investigate a little bit at least.

History

#1
Updated by Adam Dingle almost 3 years ago

I've now ordered the mouse from Amazon. Should arrive at Yorba on Thursday.

#2
Updated by Adam Dingle almost 3 years ago

  • Status changed from Open to Review
  • Assignee changed from Anonymous to Jim Nelson

#3
Updated by Adam Dingle almost 3 years ago

  • Status changed from Review to 5
  • Resolution set to worksforme
  • % Done set to 0

We received the Kensington mouse and both Jim and I tried using it (Jim is running Ubuntu 10.10 alpha 2; I'm running Ubuntu Lucid Lynx). Neither of us could see any problem at all, so I'm marking this worksforme.

#4
Updated by Adam Dingle almost 3 years ago

  • Status changed from 5 to 4
  • Resolution deleted (worksforme)
  • % Done changed from 0 to 0
  • Priority deleted (High)

A user has reiterated that this is an important problem; reopening. Not sure how much we can do until we can reproduce here, but we're attempting to gather more information (see the Launchpad ticket linked above).

#5
Updated by Adam Dingle over 2 years ago

See also#2552, which is likely related.

#6
Updated by Adam Dingle over 2 years ago

  • Priority set to High

This bug is evidently affecting a number of users as reported as Launchpad. Upping to high.

#7
Updated by Jim Nelson over 2 years ago

Downstream it has been reported that this behavior is due to gphoto2's camera auto-detection, which we use to discover cameras when they're attached and detacted:

yes, I have exactly the same behaviour. It lists no devices, but half a second later my mouse gets disconnected again. It's fully reproducible.

#8
Updated by Adam Dingle over 2 years ago

  • Subject changed from trouble with Kensington mouse to Kensington mouse and other USB devices make Shotwell unusable

#9
Updated by Jim Nelson over 2 years ago

I posted the question on the gphoto2 mailing list. Marcus Meissner responded:

gphoto2 --auto-detect does not access the camera yet, it basically only walks the USB

device tree.

Probably “lsusb -v” would also cause this behaviour.

This is really more an issue of either the kernel or the hardware setup I guess.

Perhaps USB power requirements are not met.

I've asked on the Launchpad mailing list for people to try lsusb -v and see if the problem reproduces then.

#10
Updated by Adam Dingle over 2 years ago

  • Status changed from 4 to 5
  • Resolution set to wontfix
  • % Done changed from 0 to 0

It's become clear (see the comments on the downstream ticket) that this problem is related to!VirtualBox. It seems to affect users who are running a version of VirtualBox that can proxy USB events on the host to a virtual machine (the open source version of VirtualBox does not do this). As such, it's not a Shotwell bug. Marking as wontfix.

If anyone sees this behavior who does have VirtualBox installed, feel free to reopen.

#11
Updated by Charles Lindsay 24 days ago

  • Status changed from 5 to Invalid

Also available in: Atom PDF