tuxpoldo

I tried one of the mirrors ( http://de.releases.ubuntu.com/trusty/ ) but I see no PPC there. Am I visually impaired? In any case you have to use the YeaSoft Repository since the LaunchPad PPA does not provide binaries for PPC.

From your description I would say that perhaps the server package is more suitable for your needs, since you will not need btsync as a desktop application for the currently logged in user but as a background service provided by the server. Please take a look at this thread and consider moving to the server package. Make sure, you understand the implications (permission stuff, different storage location of internal settings and database, etc...) before moving.

Thanks! All changes will be included in the next release.

Hi Folks, just back from holiday. I see a lot of new posts here - let's try to give some advice... OK - The line numbers in the error messages definitively are wrong. But it seems that the error occurs every time a line similar to if ! $DAEMON --help > /dev/null 2> /dev/null; then or if [ -f /usr/lib/btsync-common/btsync-core-i686 ]; then is executed. This indicates that there is something different as in any other debian-derived systems it was tested before. Perhaps a different default shell? Please tell us: Which specific distribution are you using? Which shell are you using? Is this also set as the system default shell? The .btsync directory is the default storage_path is no configuration file is present. This is not the case when installing the btsync package. Each instance must have a unique storage_path that will be defined in the corresponding configuration file. If you have a default instance configured by debconf, the storage_path is /var/lib/btsync Which repository are you using? The PPA does not provide support for PowerPC, so there is no btsync-common package for PowerPC - that's the reason for the error message. All other packages are platform independent, since they contain only scripts or interpreted/jitted languages. If you want to install the PowerPC version, you have to use the YeaSoft-Repository (See initial posting of this thread). Question: where do you get an Ubuntu 14.04 for PowerPC from? On the download page I see that only amd64 is supported....

I also noticed that the current version of btsync sometimes crashes - but this has never happened with one of my Linux servers. The crashes were mainly happening on my Mac OSX machines. If you would like to send some more information to the btsync developers, you should take the btsync log file and not the syslog since you will not find any useful information there. You can find the log file in the storage_path and it is named sync.log. See this topic for more details. I suppose that the the credentials btsync was using previously had not the required access privileges to the folders you were sharing. One solution is to run it as root (but in this case also all newly created files and directories will be owned by root), the other solution is to adjust the access privileges of the folders to allow the user btsync is running to do what it needs to do.

Are you sure? The standard installation of btsync-user (BTW: Issues regarding btsync-user have their own thread) has never allowed to connect to the Web UI from other computers. But there is a way you can achieve that, of you want: you can create a a custom configuration file that allows connections from any computer. See the initial posting of the btsync-user thread for more information on how to create a custom configuration file.

I will take this post as occasion for sharing some insights in the future development of btsync-gui and give some outlook on the next version. Let's start with the icon stuff: This is a known issue and also other users have asked for it (See Issue #136). The next version will provide support for selecting a dark set of icons. Since the Icons are included (and also stored on GitHub), feel free to send me your proposals for modified versions. There are two different approaches to provide different icon sets, and I'm quite not sure which one to take: Store all icons inside the package (with different names) and let the software decide which one to take. This implies modifications to the software each time an icon set is added. Store the icons in separate (dependent) packages (btsync-gui-icons-light, btsync-gui-icons-dark, btsync-gui-icons-xyz, etc.) providing the same functionality (btsync-gui-icons). This would permit to create an infinite number of icon sets without adapting the software but would generate some overhead in packaging...Let me know what you think about it. About "Click to minimize": Nice idea. I think I will implement it (if possible). About the short GUI freezes: this is an ugly thing that affects also some other future developments. Let's start with some explanation: currently btsync-gui is a single threaded application. This means, that at (originally) regular intervals the application requests status data using the sync API in order to keep the GUI updated. The number of these calls directly proportional to the number of shared folders. During this operation, the GUI freezes since the application is not able to process user input. This was not relevant, since the API calls were very fast. With 1.3.x something has changed and the processing time of the API calls has considerably slowed down. In order to avoid API flooding, I implemented a dynamic poll interval that will be computed based on the measured duration of the API calls. Currently I'm trying to implement also some active notification (See Issue #137) and the major problem I have is that I need to add more API calls (that would additionally increase this problem). For this reason I'm seriously planning to make a major redesign of the application trying to separate the internal GUI management from the status refresh mechanism in two separate threads... (and here I have to learn how to implement multi-threaded GUI programming in Python). I think that the next release will not address this problem but only contain some UI enhancement (like the icon thing). After that, I will start this major redesign - but perhaps I will also wait for BitTorrent Inc. to release an updated version of the Sync API before starting some major work.

Create the share first on the Debian box. Then you can get the read only key from the web interface. Now you can create the share on the Mac specifying the read only key.

OK. It's the one maintained by the BitTorrent Sync executable itself. Since you are the only one reporting this kind of problem, I would try to find out, if there are some special environmental situations on your machines like special permissions or similar. Can you reproduce this behaviour on a freshly installed machine? Is there any chance we can have a collaborative session on one of your machines trying to analyze the problem?

Yes. The option is not parsed by btsync itself, but by the daemon init script. The daemon init script manages all advanced things like process credentials, UMASK, NICE level, etc. This is the only advanced setting not managed by debconf. This means: if added to the default instance, it will be overwritten (in this case deleted) each time debconf regenerates the configuration file (generally on update and on manual reconfigure with dpkg-reconfigure).

If you are using the btsnyc server package, please see usage notes in the initial posting. There is an extended config file setting that can be used for enabling debug logging.

Perhaps you have played around with the "Change username or password"-Function of the Web UI. At every restart, the internally stored settings are overwritten by the settings specified in the config file except if you have no credentials configured in the config file. In this case, the internally stored settings will win. HOWTO If you have configured your web UI with no authentication and subsequently changed the credentials in the Web UI and forgot it or want to revert to not asking any credentials, you must do the following to reset them: Set the credentials of the Web UI to something known using dpkg-reconfigure btsync Log in into the Web UI using the known credentials. Remove credentials by specifying an empty password in "Change username or password" DO NOT RESTART btsync Remove also the credentials using dpkg-reconfigure btsync

I never encountered a problem like this, but I must admit, that I have no 14.04 machines currently in my infrastructure. In any case a question: which PID file are you talking about? The init script of the server package generates two PID file for each instance (one maintained by btsync itself, the other by the daemon manager). The PID file maintained by btsync is normally found in the storage_directory (with the default instance in /var/lib/btsync), the PID file maintained by the daemon manager is stored in /var/run. Which one must be deleted in order to make it work?

I would also really appreciate this (including support in the Sync API). Both btsync-gui and btsync-user provide this functionality but only with a "dirty workaround".

@suhrim When you get the testing builds from the support engineer, you can replace the binary installed by the package. The binary you will get, is named "btsync". You have to move it in place of the binary installed by the package and then restart the service. Assuming you are in the same directory where you unpacked the binary, you should perform the following commands if you are logged in as root: service btsync stopmv btsync /usr/lib/btsync-common/btsync-coreservice btsync start or the following commands, if you are logged in as a regular user: sudo service btsync stopsudo mv btsync /usr/lib/btsync-common/btsync-coresudo service btsync start

I'm aware of this problem. I'm still thinking about how to solve it. Basically I could provide a second set of icons with a different name, but in that case I have to provide an internal mechanism to switch between them (or try detecting the effective colour of the bar. I'm still thinking about it. In any case I created Issue #136 in order to track this important feature.

Ahem... I was so stupid... I read your mail but I missed looking at the screenshot. Since you write you are using Ubuntu 14.04 I believed by mistake you were using btsync-gui, but the problem seems to be related to the Web UI. This is definitively an issue for the developers of BitTorrent Sync... Sorry.

Not really. Unfortunately I'm on a business trip. I will take a look tomorrow at the code and give you some additional information.

I understand from your description that you are missing a feature or something is wrong in the Web UI. The Web UI is part of the official BitTorrent Sync executable - therefore I cannot tell you anything about it (you should know: the BitTorrent Packages for Debian and Ubuntu are an unofficial open source project). Perhaps you could take a look at btsync-gui - the successor of btsync-user. I remember that you made a test in the very beginning phase and you preferred to revert to btsync-user, but after several months the application is now very stable and provides the same access to the Web UI that also btsync-user gives you. And if you still do not like it, here is the link to our previous conversation with the instructions for roll back to btsync-user.

The main problem was the incompatibility between btsyncindicator.py and the new web ui. I waited 2 weeks before updating btsync-common, and in order to avoid conflicts, I added a "breaks:" dependency with btsync-user. This should have prevented the update of btsync-common on machines with btsync-user, but if you perform an apt-get dist-upgrade, you force the upgrade (and btsync-user will be uninstalled). Nowadays Mark Johnson has updated btsyncindicator.py and I released an updated btsync-user, but I'm not really sure, that he fixed really all bugs. You can find more information here: http://forum.bittorrent.com/topic/19560-debian-and-ubuntu-legacy-desktop-unofficial-packages-for-bittorrent-sync/?p=84616

It is a problem to switch from a manually deployed BitTorrent Sync to the standard deployment via Debian packages, since they may store the stuff in different places. Please read the initial topic about the Debian Package for server use (that is probably the most suitable for Raspberry PI usage), get familiar with the main concepts, and then decide, if you want to migrate.

This behaviour is due to the way BitTorrent Sync handles the configuration file and the internal storage of configuration data. You will find more information about this in the following postings: http://forum.bittorrent.com/topic/18974-debian-and-ubuntu-server-unofficial-packages-for-bittorrent-sync/?p=83129 http://forum.bittorrent.com/topic/29589-changing-online-password-on-raspberry-pi/

No problem! My concern is only that your report is not read by the right people.

Sorry, but you are in the wrong thread. The Web UI is part of the core BitTorrent Sync code, therefore you should report this in a separate topic.

And here it is: btsync-user (1.16.0-1) unstable; urgency=low * New upstream release 0.16 on btsyncindicator - Made compatible with new Web UI of BitTorrent Sync version 1.3.105 (Closes #btsyncindicator/50) -- Leo Moll <leo.moll@yeasoft.com> Mon, 02 Jun 2014 23:59:52 +0100