I don't want to completely eliminate Rhythmbox (or MTP handling) from this, but there's kind of a third agent here, namely gphoto2. Since all this software (GVFS, Rhythmbox, Shotwell) is talking to one piece of hardware through a common library, it's difficult to know just where the problem lies. Or if there's only one problem, when there might be two.
If there is a regression with Rhythmbox, then yes, that's something they need to attack. However, it does seem like there's one case where we can eliminate Rhythmbox from the equation and still see the problem. -- Jim On Tue, Jan 29, 2013 at 2:49 PM, go linux <[email protected]> wrote: Oh and why was it working properly in September but not in January? Seems some sort of regression was introduced in the months since then. On 1/29/13, go linux wrote: > On 1/29/13, Colin Law wrote: >> On 28 January 2013 23:10, Jim Nelson wrote: >>> I've mentioned it on a Rhythmbox ticket on Launchpad, but haven't gone >>> any >>> farther than that. I'm not certain this is a de facto Rhythmbox bug, at >>> least for the majority of our users. >>> >>> If you look at Luis' comments, it does look like there's something going >>> on with how we're talking to the camera, so it's quite possible this is >>> fundamentally a Shotwell bug. Hopefully we'll know more in the next >>> couple of days. >>> >>> -- Jim >>> >>> On Mon, Jan 28, 2013 at 12:49 PM, go linux wrote: >>> On 1/28/13, Jim Nelson wrote: >>>> Hey everyone, >>>> >>>> Luis Arias has been looking into this problem and has done some >>>> fantastic >>>> debugging. I recommend looking at his notes from the past couple of >>>> days: >>>> >>>> http://redmine.yorba.org/issues/4512 >>>> >>>> -- Jim >>>> >>> >>> Great that shotwell is looking into this bug. So far there has been >>> no response to my query on the pkg-gnome-maintainers mailing list. :( >>> >>> While it would be great to get shotwell fixed, I'm thinking . . . if >>> the same bug not only affects shotwell but f-spot and gtkam too, isn't >>> the problem outside of shotwell? Have you communicated at all with the >>> rhythmbox folks? Or other apps that are tied into rhtyhmbox? >> >> I am confused, is it not exactly this bug [1], which references [2] >> which was reported in the version of Rhythmbox the OP is using and >> seems to have been fixed in a later version. >> >> [1] https://bugs.launchpad.net/rhythmbox/+bug/544994 >> [2] https://bugzilla.gnome.org/show_bug.cgi?id=615743 >> >> Colin >> > > That certainly sounds like what I have experienced. If there is a > fix, why hasn't it found its way into squeeze or the backports? I'll > post those two references on the pkg-gnome-maintainers list to jog > their collective memories . . . > _______________________________________________ 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
