Just to be clear, I don't control the Importance for the Ubuntu side of things. This bug on our Trac system is marked High and we're taking it very seriously. What's impacting us the most right now is that we can't reproduce this in-house, making it difficult to debug. We've tried reproducing this on Maverick and Lucid, using both older versions of gphoto2 (2.4.5) and the latest. It does appear to be a gphoto2 problem in the sense that when we ask it to auto-detect cameras it's causing the mouse to hang. It's possible the problem is in libusb itself (which gphoto2 relies on to talk to the cameras).
I realize that saying all this doesn't solve your bottom-line problem, but we are looking into it! It may be that we have to work around this in Shotwell somehow. That "somehow" is the $64,000 question at this moment.
gypsy_roadhog (and everyone else)
Just to be clear, I don't control the Importance for the Ubuntu side of things. This bug on our Trac system is marked High and we're taking it very seriously. What's impacting us the most right now is that we can't reproduce this in-house, making it difficult to debug. We've tried reproducing this on Maverick and Lucid, using both older versions of gphoto2 (2.4.5) and the latest. It does appear to be a gphoto2 problem in the sense that when we ask it to auto-detect cameras it's causing the mouse to hang. It's possible the problem is in libusb itself (which gphoto2 relies on to talk to the cameras).
I realize that saying all this doesn't solve your bottom-line problem, but we are looking into it! It may be that we have to work around this in Shotwell somehow. That "somehow" is the $64,000 question at this moment.
-- Jim