This is a fascinating discovery!  I recall a couple of years ago having some 
kind of problem with Rhythmbox and cameras, so this might be another variation 
on that, or a full-blown regression.

We're tracking this problem in our Redmine server.  Hopefully other people try 
what you did and lets us know if this is the source of our problems:

http://redmine.yorba.org/issues/4512

-- Jim

On Wed, Jan 23, 2013 at 11:33 PM, go linux <[email protected]> wrote:
On 1/24/13, Norbert Preining wrote: 
> Hi, 
> 
> On Mi, 23 Jan 2013, go linux wrote: 
>> "The camera is locked by another application. Shotwell can only access 
>> the camera when it's unlocked. Please close any other application 
>> using the camera and try again." 
> [...] 
>> I deleted Shotwell dot files in my /home directory, reinstalled 
>> Shotwell and even rebooted but no joy. Is there any way to get 
>> Shotwell working again? 
> 
> There is some other application holding the device. Maybe 
> some auto-mounting or auto import is running. 
> 
> My guess is that nothing whatsoever on the shotwell side can get 
> it working. 
> 
> Do you have sufficient permissions to the devices? 
> 
> Norbert 
> 

Thanks for responding. 

YEA!! I got it working. Here's how. I started from this logged in 
.xsessions-errors when trying to open the camera: 

---------------------------------------- 

Please report this VID/PID and the device model to the libmtp development team 
LIBMTP WARNING: no MTP vendor extension on device 16 on bus 3LIBMTP 
WARNING: VendorExtensionID: 0000000bLIBMTP WARNING: 
VendorExtensionDesc: (null)LIBMTP WARNING: this typically means the 
device is PTP (i.e. a camera) but not an MTP device at all. Trying to 
continue anyway.LIBMTP PANIC: could not inspect object property 
descriptions! 
LIBMTP PANIC: could not inspect object property descriptions! 

---------------------------------------- 

Then I looked at the libmtp packages and added libmtp-dev and 
mtp-tools just for the heck of it. Then I noticed that 
rhythmbox-plugins came up in the MTP search and also that rhythmbox 
was sleeping in the list of processes so I stopped that rhythmbox 
process. After all that, I was able to open Shotwell and access the 
camera. I don't remember ever using rhythmbox so don't know how it 
got started. Very strange. 
_______________________________________________ 
Shotwell mailing list 
[email protected] 
http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell 

_______________________________________________
Shotwell mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell

Reply via email to