Trouble in file sharing with kdeconnect-kde

[vineet garg]

I don't think packet size of 4096 is an issue. We have been using it from a
long time and it was working quite fine when I was working with kde4
version.
The issue is when we receive the payload, instead of reading 4096 bytes,
sometime socket just reads some random number of bytes, frequency of 248
was most. The payload from android is sent successfully and received
successfully, as seen in Wireshark. The code looks fines but still it is
not working.
 Well this[1] might be the reason but I'm not sure as it was asked about 5
years ago. We are using 4096 currently.

[1]
http://stackoverflow.com/questions/2613734/maximum-packet-size-for-a-tcp-connection


*Regards,*
*Ashish Bansal*
*http://ashish-bansal.in <http://ashish-bansal.in>*

On Wed, Apr 1, 2015 at 12:10 AM, vineet garg <grgvineet at gmail.com> wrote:

> What is happening to file transfers in your case?
> Is the file received incompletely, or it just stuck on receiving file.
> If it just stuck, I believe that is due to some assert statements and
> daemon exits due to that. Like in qvariant2qobject function in network
> package why do we assert on property.isValid() is we want to do some stuff
> on property.isValid() later on.
>
> On Tue, Mar 31, 2015 at 9:54 PM, Aleix Pol <aleixpol at kde.org> wrote:
>
>> I've just been trying to send over some files, I wasn't able to
>> receive it either, couldn't debug it though.
>> Love is required. :)
>>
>> Aleix
>>
>> On Mon, Mar 30, 2015 at 10:55 PM, vineet garg <grgvineet at gmail.com>
>> wrote:
>> > Initially I was getting files written directly to root, but out of
>> nowhere,
>> > later it started working fine. Later I discovered that the files are not
>> > complete, or I can say that they are sent complete but socket wasn't
>> reading
>> > full data, instead of 4096 bytes, it was reading some random number of
>> > bytes.
>> > These strange bugs always get in my way, but thanks for telling me that
>> I am
>> > not alone. I will dive in deeper to fine the root cause.
>> > I don't think either that, that commit was causing it. But out of many
>> > strange things I encountered yesterday, this was also one them :)
>> > I will check this all again.
>> > Thanks
>> >
>> > On 31-Mar-2015 2:08 AM, "Albert Vaca" <albertvaka at gmail.com> wrote:
>> >>
>> >> This happens sometimes, I don't know the cause but I would say it's not
>> >> related to the commit you pointed out, because it happened to me
>> before. I
>> >> have no idea why does it happen, but it's probably caused by a
>> connection
>> >> reset or something like this, that causes the socket to close. Do you
>> say
>> >> that the files are actually sent but they are not received correctly
>> by the
>> >> desktop client? That could be a hint to start investigating.
>> >>
>> >> On Mar 29, 2015 2:35 PM, "vineet garg" <grgvineet at gmail.com> wrote:
>> >>>
>> >>> Now working fine. Still a mystery what happened.
>> >>> But now every file is sent incomplete :( . Although I can see in the
>> >>> Wireshark that the file sent completely reaches to destination.
>> >>> Are these known or happening to me only?
>> >>>
>> >>> On Mon, Mar 30, 2015 at 1:49 AM, vineet garg <grgvineet at gmail.com>
>> wrote:
>> >>>>
>> >>>> Hi
>> >>>> I was working on to show application icon from android in kde in
>> >>>> notifications plugin.
>> >>>> I found out that there is some problem with file transfers and I am
>> not
>> >>>> able to figure out why is this happening.
>> >>>> After commit b06038e60ed2ec358f43282fd2c24a322c977568 (Prefer the
>> usage
>> >>>> of QUrl::toLocalFile to QUrl::path), it is trying to write the file
>> directly
>> >>>> on root.
>> >>>> Link to the screenshot is provided below where we can see the
>> >>>> destination of the file is "/filename".
>> >>>> File transfer is working fine in previous
>> >>>> commit(463aa0cbf9046a8f2c826b8b14552da0fbdd6e69).
>> >>>>
>> >>>> Screenshot :
>> >>>>
>> https://drive.google.com/file/d/0B7UrqqDErPX4ZDFIVkdnZnJPdEk/view?usp=sharing
>> >>>>
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> KDEConnect mailing list
>> >>> KDEConnect at kde.org
>> >>> https://mail.kde.org/mailman/listinfo/kdeconnect
>> >>>
>> >
>> > _______________________________________________
>> > KDEConnect mailing list
>> > KDEConnect at kde.org
>> > https://mail.kde.org/mailman/listinfo/kdeconnect
>> >
>>
>
>
> _______________________________________________
> KDEConnect mailing list
> KDEConnect at kde.org
> https://mail.kde.org/mailman/listinfo/kdeconnect
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdeconnect/attachments/20150401/c058b63c/attachment.html>