Helen

Administrators
  • Posts

    2,719
  • Joined

  • Last visited

Everything posted by Helen

  1. Where do you have it installed - internal memory or SD card? Did you move it from here to there? Try reinstalling, if you haven't yet. If it still crashes, you will need Files app to collect dumps. go to Documents-> debug and see if there are BitTorrent Sync dumps. Send the latest to us - we'll send invitation link to upload it.
  2. Chris V, To start from scratch, you need to first uninstall Sync and its settings, here's instruction Identity - is a new feature for Sync 2.0, as Sync 2.0 uses Public key infrastructure to share the folder. It's more secure . You just need to create a separate identity for each of your devices (pick This is my first device") and then add and share the folder via links between identities as you used to do in Sync 1.4. If the problem remains, the questions for you: was this folder ever added to Sync from any other peer with RO key, and then re-shared with RW ? Or did you initially add the folder on this peer and went to share it right away? Any details on how you ended up with this folder so that we could reproduce it would be much appreciated. Thank you.
  3. it's already fixed. But as Roman Z indicated, it's not included into 2.0.105 build. It will be available in the following release.
  4. Basajaun, Failed to create empty suffix for file - means that the receiving side was not able to start downloading file ABC.pdf due to error 22 - invalid argument. Some parameter in the file is not good, whether its name, structure, date, etc. Do you see anything like 'failed to verify signature" or "failed to verify group signature" in the log? Try renaming the file and re-adding the file to the folder on the source peer.
  5. This case is being investigated, but please note that it comes from core of the app, so adjusting Sync to work with that new Lollipop's API will require core changes, which is not a quick one night's fix, thank you for understanding.
  6. piersh, was this folder ever added to Sync from any other peer with RO key, and then re-shared with RW ? Or did you initially add the folder on this peer and went to share it right away?
  7. Be sure, developers are aware of this API, they are not behind it all. This API works via file descriptors and through them it gives write access. Sync's core code works with files directly, the API doesn't allow it. That's why Sync is now allowed to write to SD card.
  8. Can you share a few screenshots - of Sync UI showing this folder, and it's key (all letters but first one blurred) if its a 1.4 folder. The only possible case of a remote peer receiving RO link when share RW link is when one clicks "Copy" or "Email the link *before* switching to RW in "Share" window (RO is picked by default).
  9. haraldthi, Please double cases. IMG/img or JPG/jpg can cause conflicts. Sync actually checks that the new file is the same as local, differing only in letter case. Since local file system cannot allow Filename and filename, conflicts are created. The problem is complicated if there are some Linux peers (where Filename and filename are allowed), and when they both come to a Windows or Mac.
  10. can you please check out this article on the problem? it has some tips on what needs to be checked in network settings
  11. Fault module MxMUm.dll belongs to product Matrox M-Series Display Driver. Please update your video driver and the whole system via windows update.
  12. Try 2.0.104 Prior to installing it, delete %Appdata%\BitTorrent Sync folder. If it crashes, collect latest .dmp file from %Appdata%\BitTorrent Sync folder. Also, put a debug.txt file there, put FFFFFFFF inside this file, and restart Sync. after some 10 minutes with crashing reproduced, please send sync.log from %Appdata%\BitTorrent Sync together with dmp file. I've sent an invite to your current mail, please upload files there. Thank you.
  13. Antony, link your computers in 'Disconnected" mode. In this case a folder added to Sync on one laptop, will appear on the other as "disconnected" and you will be able to pick a fancy location for it when connecting. You can see and change the mode in Sync -> cog icon -> My devices. As for folders that you already have in Sync, you can just move them in File Explorer. Sync shall adjust the path to it. Please note that it will work only if you move it within one letter drive.
  14. sgmiller, Thank you. The problem with Mac is known to us and seems to be already fixed. Fix will be available ASAP. As for windows, details from your machines are still welcomed, as we still cannot reproduce it. Thanks!
  15. This still looks like a regular letter case conflict. On Mac you had ANIMUSIC.m4v in iTunes Media, and this was conflicting with file on Windows. Quit Sync, completely delete ANIMUSIC.m4v and Animusic.m4v from folders, Trash, Archive on both. Plus there are some records about Text.xts and conflicting TEXT.txt being renamed to Animusic.Conflict.m4v, which may also lead to conflicts appearing. Is it the Animusic.m4v - the previous conflicting Text.txt file?
  16. @all, it looks like it's already fixed. The fixed build should be released soon (sorry, there's no exact date). you are all invited to give it a try and let us know about the result. Thank you.
  17. on Mac, right? Can you please send full debug logs from both peers to us . Please indicate which file you update/delete, to ease tracing it down in the log. Thanks
  18. rstarkov, go to the storage (described in step 3) or the 'storage_path',if you are using a config and echo "FFFFFFFF" to debug.txt file there. restart Sync
  19. narnold1, Unfortunately, there is no crash report from this devices among reports we receive. Can you please send a feedback from your phone after another crash, and agree to attach logs. In the text please indicate that it's from narnold1 and mention this forum topic. Thanks
  20. Tarcisio, If Android allows it - yes,. If it doesn't allow it - no. before adding the folder. Sync checks if it has write permissions there.
  21. All movies were moved to Archive on NAS? Looks like PC is not read-only peer. Your understanding of how RO works is correct , so when file changes on RO peer, this file gets invalidated in the folder tree, so the changes do not affect other peers. Just a simple thing to check - does the folder on PC have a "crossed pencil" icon?