starting synce on archlynux

[a***@hotmail.com]

Sorry, I thought I had sent this out already.

$ sudo odccm -f -l 6
** (odccm:2550): DEBUG: _odccm_interface_address: waiting for IP
address on ppp0
** (odccm:2550): DEBUG: _odccm_interface_address: waiting for IP
address on ppp0
** (odccm:2550): DEBUG: _odccm_interface_address: waiting for IP
address on ppp0
** (odccm:2550): DEBUG: _odccm_interface_address: waiting for IP
address on ppp0
** (odccm:2550): DEBUG: _odccm_interface_address: waiting for IP
address on ppp0
process 2550: arguments to dbus_move_error() were incorrect, assertion
"(dest) == NULL || !dbus_error_is_set ((dest))" failed in file
dbus-errors.c line 278.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Aborted

Hmm, not very enlightening was it. I could knock up some messages into a
patch for odccm, but not for a while. That woukd only be a guide to
where the failure is though, since you had it working before.
I'm completely unfamiliar with archlinux, so it could frankly be
anything in the setup. How about the obvious, what's the output of
iptables -L ?

I'm not an expert on iptables, so until I learn what's what, I installed ufw and set it up with a default policy of deny. Since when I'm connecting through synce, I'm not using the internet, I just run "ufw disable" (with the internet box shut off) before odccm and re-enable it

when I'm done. After running ufw disable this is the result of iptables -L:

$ iptables -L

Chain INPUT (policy ACCEPT)
target prot opt source destination
ufw-before-logging-input all -- anywhere anywhere
ufw-before-input all -- anywhere anywhere
ufw-after-input all -- anywhere anywhere
ufw-after-logging-input all -- anywhere anywhere
ufw-reject-input all -- anywhere anywhere
ufw-track-input all -- anywhere anywhere

Chain FORWARD (policy ACCEPT)
target prot opt source destination
ufw-before-logging-forward all -- anywhere anywhere
ufw-before-forward all -- anywhere anywhere
ufw-after-forward all -- anywhere anywhere
ufw-after-logging-forward all -- anywhere anywhere
ufw-reject-forward all -- anywhere anywhere

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ufw-before-logging-output all -- anywhere anywhere
ufw-before-output all -- anywhere anywhere
ufw-after-output all -- anywhere anywhere
ufw-after-logging-output all -- anywhere anywhere
ufw-reject-output all -- anywhere anywhere
ufw-track-output all -- anywhere anywhere

Chain ufw-after-forward (1 references)
target prot opt source destination

Chain ufw-after-input (1 references)
target prot opt source destination

Chain ufw-after-logging-forward (1 references)
target prot opt source destination

Chain ufw-after-logging-input (1 references)
target prot opt source destination

Chain ufw-after-logging-output (1 references)
target prot opt source destination

Chain ufw-after-output (1 references)
target prot opt source destination

Chain ufw-before-forward (1 references)
target prot opt source destination

Chain ufw-before-input (1 references)
target prot opt source destination

Chain ufw-before-logging-forward (1 references)
target prot opt source destination

Chain ufw-before-logging-input (1 references)
target prot opt source destination

Chain ufw-before-logging-output (1 references)
target prot opt source destination

Chain ufw-before-output (1 references)
target prot opt source destination

Chain ufw-reject-forward (1 references)
target prot opt source destination

Chain ufw-reject-input (1 references)
target prot opt source destination

Chain ufw-reject-output (1 references)
target prot opt source destination

Chain ufw-track-input (1 references)
target prot opt source destination

Chain ufw-track-output (1 references)
target prot opt source destination

_________________________________________________________________
The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail.
http://www.windowslive.com/campaign/thenewbusy?tile=multicalendar&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5