Bug#707681: Happens also with 1.18.2-1

Emilio Pozuelo Monfort pochu at debian.org
Wed Oct 30 23:36:39 UTC 2013


On 30/10/13 19:51, Yves-Alexis Perez wrote:
> On Wed, 2013-10-30 at 17:52 +0100, Emilio Pozuelo Monfort wrote:
>> Hey,
>>
>> On 30/10/13 16:33, Yves-Alexis Perez wrote:
>>> gvfsd-gphoto2 seems dbus activated so it's not really practical. And
>>> rebuilding the whole stuff is pretty painful actually, which is why I
>>> asked some help from the package maintainers…
>>
>> I think it's /usr/lib/gvfs/gvfs-gphoto2-volume-monitor that is dbus activated,
>> but not /usr/lib/gvfs/gvfsd-gphoto2 which is the one that is crashing. I suppose
>> the latter is started by the former when a camera is plugged in, but I don't
>> know gvfs so well as to know that off-hand and I can't check right now...
>>
>> Cheers,
>> Emilio
> What's crashing is gvfs-gphoto2-volume-monitor:
> 
> Oct 30 16:36:53 scapa kernel: [130854.725634] traps:
> gvfs-gphoto2-vo[6060] general protection ip:7f57f404a0d0 sp:7fff70f17cb8
> error:0 in libusb-1.0.so.0.1.0[7f57f4046000+16000]
> 
> Error creating proxy: Error calling StartServiceByName for
> org.gtk.Private.GPhoto2VolumeMonitor:
> GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildSignaled:
> Process /usr/lib/gvfs/gvfs-gphoto2-volume-monitor received signal 11
> (g-dbus-error-quark, 26)

OK, I assumed it was gvfsd-gphoto2 as that's what #707681 was about.

Emilio



More information about the pkg-gnome-maintainers mailing list