Rhythmbox interfering with Shotwell and others

[Go Linux]

--- On Fri, 1/25/13, Go Linux <golinux at yahoo.com> wrote:

> From: Go Linux <golinux at yahoo.com>
> Subject: Rhythmbox interfering with Shotwell and others
> To: pkg-gnome-maintainers at lists.alioth.debian.org
> Cc: golinux at yahoo.com
> Date: Friday, January 25, 2013, 2:08 PM
> On Debian Squeeze with Gnome desktop
> . . .
> 
> I don't use my Canon Powershot A610 often.  Shotwell
> was working just fine in September.  As expected, it
> auto-launched and recognized the camera.
> 
> A few days ago it was broken.  I plugged in the camera
> and Shotwell did not auto-launch as usual and was unable to
> access the camera. The error message was:
> 
> "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."
> 
> After some sleuthing I found this in .xsessions-errors:
> 
> ----------------------------------------
> 
> 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!
> 
> ----------------------------------------
> 
> More sleuthing and I found a reference to rhythmbox.  I
> checked running processes and rhythmbox was sleeping. 
> I stopped it and Shotwell was able to recognize the camera
> again.
> 
> I tried several other options to access the camera and they
> were also broken until the rhythmbox process was stopped.
> 
> My system is updated and STABLE and I have never even used
> rhythmbox so I don't know what is launching this process.
> 
> Something has changed between September and now. Hope you
> can find and fix it.
> 
> Please copy responses to me as I am not a member of this
> list.
> 
> Thanks.  
> 

The Shotwell folks have tracked down these two bugs that describe what I have been experiencing.

https://bugs.launchpad.net/rhythmbox/+bug/544994
https://bugzilla.gnome.org/show_bug.cgi?id=615743

This hasn't been a problem since I installed squeeze in spring 2011 and everything was working properly in September.  Then in January 2013, I am experiencing this bug for the first time.   Was some sort of regression introduced in the last few months?

Will someone PLEASE respond?