Heya,
On 31/10/13 09:03, Yves-Alexis Perez wrote:
> On Thu, 2013-10-31 at 00:36 +0100, Emilio Pozuelo Monfort wrote:
>> OK, I assumed it was gvfsd-gphoto2 as that's what #707681 was about.
>
> Do you think this is unrelated and want me to open another bug report?
I think this is unrelated yes, b
On Thu, 2013-10-31 at 00:36 +0100, Emilio Pozuelo Monfort wrote:
> OK, I assumed it was gvfsd-gphoto2 as that's what #707681 was about.
Do you think this is unrelated and want me to open another bug report?
--
Yves-Alexis
signature.asc
Description: This is a digitally signed message part
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
On 30/10/13 18:51, Yves-Alexis Perez wrote:
> 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
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 pa
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 th
On Wed, 2013-10-30 at 16:24 +0100, Emilio Pozuelo Monfort wrote:
> On 30/10/13 15:48, Yves-Alexis Perez wrote:
> > On Wed, 2013-10-30 at 11:16 +0100, Emilio Pozuelo Monfort wrote:
> >> On 30/10/13 09:13, Yves-Alexis Perez wrote:
> >>> Is someone actually looking at bug reports and can investigate i
On 30/10/13 15:48, Yves-Alexis Perez wrote:
> On Wed, 2013-10-30 at 11:16 +0100, Emilio Pozuelo Monfort wrote:
>> On 30/10/13 09:13, Yves-Alexis Perez wrote:
>>> Is someone actually looking at bug reports and can investigate if it's a
>>> problem in gvfs, in libusb or elsewhere?
>>
>> Get a gdb bac
On Wed, 2013-10-30 at 11:16 +0100, Emilio Pozuelo Monfort wrote:
> On 30/10/13 09:13, Yves-Alexis Perez wrote:
> > Is someone actually looking at bug reports and can investigate if it's a
> > problem in gvfs, in libusb or elsewhere?
>
> Get a gdb backtrace with debugging symbols (the one in the bu
On 30/10/13 09:13, Yves-Alexis Perez wrote:
> Is someone actually looking at bug reports and can investigate if it's a
> problem in gvfs, in libusb or elsewhere?
Get a gdb backtrace with debugging symbols (the one in the bug report is
useless), and ideally send it to bugzilla.gnome.org.
Emilio
As said in the subject, it happens also with gvfs 1.18.2-1 from
experimental.
Is someone actually looking at bug reports and can investigate if it's a
problem in gvfs, in libusb or elsewhere?
Regards,
--
Yves-Alexis
signature.asc
Description: This is a digitally signed message part
11 matches
Mail list logo
