On 28 January 2013 23:10, Jim Nelson <[email protected]> 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 <[email protected]> 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 _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
