GNOME Bugzilla – Bug 330330
Applet / Evo config GUI trashes backup conduit & net hotsync configs
Last modified: 2006-03-09 16:53:50 UTC
Please describe the problem: (This is two-ish bugs for the price of one...) Using the preference GUI will trash the following valid pre-existing configs even if the related sections / tabs are not accessed. Note the GUI does not have functionality to edit the affected entries (if it did I'm sure it wouldn't trash them ;-) But it does pretend to offer network hotsync configuration). The most important aspected of this bug is that people believe gpilot does not support a network hotsync. It does (ta da) - if you stay out the GUI and tweak the config files manually. There are some going nowhere pre-existing "NEED INFO" duplicate bugs 134708 145869 301407 (I appear to have already commented on the last one). These can be closed as duplicates of this master as this one covers backup as well. Steps to reproduce: 1. Set up your basic config using the GUI. 2. If you wish to use a network hotsync edit the [DeviceN] section of $HOME/.gnome2/gnome-pilot.d/gpilotd. A valid example (NB details must exactly match the network hot sync settings on the pilot): [Device0] type=4 name=Net ip=192.168.103.59 host=vmcevo2 netmask=255.255.255.0 timeout=7 3. Define excludes for the backup conduit in $HOME/.gnome2/gnome-pilot.d/backup-conduit . A useful example of the line is: exclude_files=WiFiCoreLib Shim\\ Logs ImgFile-Foto Jpeg-Foto J9\\ MIDP\\ Bundle J9\\ Java\\ VM 4. Use the GUI. Then diff the two edited files. Your edits are toast. Actual results: Loss of network notsync and / or broken backup conduit. After and before GUI diffs for the example edits: < ip= < host= < netmask= --- > ip=192.168.103.59 > host=vmcevo2 > netmask=255.255.255.0 < exclude_files=WiFiCoreLib,Shim Logs,ImgFile-Foto,Jpeg-Foto,J9 MIDP Bundle,J9 Java VM --- > exclude_files=WiFiCoreLib Shim\\ Logs ImgFile-Foto Jpeg-Foto J9\\ MIDP\\ Bundle J9\\ Java\\ VM Expected results: A working network hotsync with backup. (If you were being greedy the desired functionality would be configurable via the GUI) Does this happen every time? Absolutely Other information: The backup issue was noticed with respect to bug 320025 comment #9 Version info for my environment can be taken from that bug.
Two points: * I imagine the GUI works on a - parse everything, store, rewrite everything model, which would be sensible except it rewrites the wrong syntax for the backup. What it does with the network hotsync is a complete mystery. * While posting to the duplicates I noticed bug 145869 comment #2 mentions some patches regarding the network hotsync side of things. As you might have guessed I'm not a coder ;-) Therefore this one has not yet reached my pain threshold for getting my hands dirty in the code.
The netsync issue is addressed in #328396. The underlying netsync code has been updated in CVS, along the lines of the patch you refer to. You're lucky if you have a functioning network hotsync with gnome-pilot 2.0.12/13. In many configurations (such as NAT) it is impossible. The changes made in CVS should make netsync reliable and easier to configure.
Turns out the exclude_files bug was already fixed in CVS. See bug #130520. Closing this bug. *** This bug has been marked as a duplicate of 130520 ***