Discussion:
[Synce-cvslog] SF.net SVN: synce: [3320] trunk/trayicon
Iain Buchanan
2008-03-20 01:00:25 UTC
Permalink
Hi,
Revision: 3320
http://synce.svn.sourceforge.net/synce/?rev=3320&view=rev
Author: mark_ellis
Date: 2008-03-19 16:21:14 -0700 (Wed, 19 Mar 2008)
-----------
* create and remove sync-engine partnerships in device info
not sure how "ready" that commit is, but it crashes when I view device
status. Output below. Do you want a backtrace?

$ synce-trayicon -f
** (synce-trayicon:7975): DEBUG: Running in foreground
** (synce-trayicon:7975): DEBUG: odccm_client_init_comms_impl: adding device: /org/synce/odccm/Device/_2C343682_C645_9887_675F_401F60866DD0_
** (synce-trayicon:7975): DEBUG: odccm_add_device: Received connect from odccm: /org/synce/odccm/Device/_2C343682_C645_9887_675F_401F60866DD0_
** Message: Hal reports no devices connected
** (synce-trayicon:7975): DEBUG: device_connected_cb: looking for preexisting device IO2
** (synce-trayicon:7975): DEBUG: module_load_all: loading module /usr/lib/synce-trayicon/modules/gnomevfs-trayicon-module.so
** (synce-trayicon:7975): DEBUG: module_load_all: loading module /usr/lib/synce-trayicon/modules/test-mod.so
** (synce-trayicon:7975): DEBUG: g_module_check_init: running from trayicon test module for /usr/lib/synce-trayicon/modules/test-mod.so
** (synce-trayicon:7975): DEBUG: partners_setup_view_store_synceng: partnership 0 id: 7518327
** (synce-trayicon:7975): DEBUG: partners_setup_view_store_synceng: partnership 0 guid: {170E2CCA-6426-ECB9-500F-FF955915708E}
** (synce-trayicon:7975): DEBUG: partners_setup_view_store_synceng: partnership 0 name: Orpheus
** (synce-trayicon:7975): DEBUG: partners_setup_view_store_synceng: partnership 0 host name: orpheus
** (synce-trayicon:7975): DEBUG: partners_setup_view_store_synceng: partnership 0 device name: IO2
** (synce-trayicon:7975): DEBUG: partners_setup_view_store_synceng: partnership 0 sync_items 0: 0
** (synce-trayicon:7975): DEBUG: partners_setup_view_store_synceng: partnership 0 sync_items 1: 7
** (synce-trayicon:7975): DEBUG: partners_setup_view_store_synceng: partnership 0 sync_items 2: 1
Cannot access memory at address 0x0
Cannot access memory at address 0x0

cya,
--
Iain Buchanan <iaindb at netspace dot net dot au>

As usual, I'm overstating the case to knock a few neurons loose, but the
truth is usually somewhere in the muddle, uh, middle.
-- Larry Wall in <***@wall.org>
Mark Ellis
2008-03-20 08:46:50 UTC
Permalink
Post by Iain Buchanan
Hi,
Revision: 3320
http://synce.svn.sourceforge.net/synce/?rev=3320&view=rev
Author: mark_ellis
Date: 2008-03-19 16:21:14 -0700 (Wed, 19 Mar 2008)
-----------
* create and remove sync-engine partnerships in device info
not sure how "ready" that commit is, but it crashes when I view device
status. Output below. Do you want a backtrace?
Obviously not ready at all :) Yes please, backtrace would be great.
Post by Iain Buchanan
$ synce-trayicon -f
** (synce-trayicon:7975): DEBUG: Running in foreground
** (synce-trayicon:7975): DEBUG: odccm_client_init_comms_impl: adding device: /org/synce/odccm/Device/_2C343682_C645_9887_675F_401F60866DD0_
** (synce-trayicon:7975): DEBUG: odccm_add_device: Received connect from odccm: /org/synce/odccm/Device/_2C343682_C645_9887_675F_401F60866DD0_
** Message: Hal reports no devices connected
** (synce-trayicon:7975): DEBUG: device_connected_cb: looking for preexisting device IO2
** (synce-trayicon:7975): DEBUG: module_load_all: loading module /usr/lib/synce-trayicon/modules/gnomevfs-trayicon-module.so
** (synce-trayicon:7975): DEBUG: module_load_all: loading module /usr/lib/synce-trayicon/modules/test-mod.so
** (synce-trayicon:7975): DEBUG: g_module_check_init: running from trayicon test module for /usr/lib/synce-trayicon/modules/test-mod.so
** (synce-trayicon:7975): DEBUG: partners_setup_view_store_synceng: partnership 0 id: 7518327
** (synce-trayicon:7975): DEBUG: partners_setup_view_store_synceng: partnership 0 guid: {170E2CCA-6426-ECB9-500F-FF955915708E}
** (synce-trayicon:7975): DEBUG: partners_setup_view_store_synceng: partnership 0 name: Orpheus
** (synce-trayicon:7975): DEBUG: partners_setup_view_store_synceng: partnership 0 host name: orpheus
** (synce-trayicon:7975): DEBUG: partners_setup_view_store_synceng: partnership 0 device name: IO2
** (synce-trayicon:7975): DEBUG: partners_setup_view_store_synceng: partnership 0 sync_items 0: 0
** (synce-trayicon:7975): DEBUG: partners_setup_view_store_synceng: partnership 0 sync_items 1: 7
** (synce-trayicon:7975): DEBUG: partners_setup_view_store_synceng: partnership 0 sync_items 2: 1
Cannot access memory at address 0x0
Cannot access memory at address 0x0
cya,
Iain Buchanan
2008-03-20 13:00:12 UTC
Permalink
Post by Mark Ellis
Post by Iain Buchanan
Hi,
Revision: 3320
...
Post by Mark Ellis
Post by Iain Buchanan
not sure how "ready" that commit is, but it crashes when I view device
status. Output below. Do you want a backtrace?
Obviously not ready at all :) Yes please, backtrace would be great.
sure :)

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6b406f0 (LWP 17508)]
0x0805afb6 in sync_item_sort (a=0x1, b=0x0) at device-info.c:648
648 device-info.c: No such file or directory.
in device-info.c
(gdb) thread apply all bt

Thread 1 (Thread 0xb6b406f0 (LWP 17508)):
#0 0x0805afb6 in sync_item_sort (a=0x1, b=0x0) at device-info.c:648
#1 0xb6e9a8bb in g_list_sort_real (list=<value optimized out>,
compare_func=0x805afb0 <sync_item_sort>, user_data=0x0) at
glist.c:906
#2 0xb6e9a87b in g_list_sort_real (list=0x8184e40,
compare_func=0x805afb0 <sync_item_sort>, user_data=0x0) at
glist.c:952
#3 0xb6e9a87b in g_list_sort_real (list=0x819c790,
compare_func=0x805afb0 <sync_item_sort>, user_data=0x0) at
glist.c:952
#4 0xb6e9a87b in g_list_sort_real (list=0x818e700,
compare_func=0x805afb0 <sync_item_sort>, user_data=0x0) at
glist.c:952
#5 0x0805d5b1 in partners_setup_view_store_synceng (
self=<value optimized out>) at device-info.c:801
#6 0x0805dd0d in wm_device_info_set_property (obj=0x81537c0,
property_id=1,
value=0xbfe5f688, pspec=0x80cc390) at device-info.c:890
#7 0xb6f41669 in g_object_constructor (type=135741224,
n_construct_properties=1, construct_params=0x80f6958) at
gobject.c:697
#8 0xb6f3f777 in IA__g_object_newv (object_type=135741224,
n_parameters=1,
parameters=0x8178240) at gobject.c:937
#9 0xb6f403ab in IA__g_object_new_valist (object_type=135741224,
first_property_name=0x8060d3b "device", var_args=0xbfe5f8ac "")
at gobject.c:1027
#10 0xb6f404a0 in IA__g_object_new (object_type=135741224,
---Type <return> to continue, or q <return> to quit---
first_property_name=0x8060d3b "device") at gobject.c:795
#11 0x08052053 in menu_device_info (button=0x808d880, device=0x808cda0)
at synce-trayicon.c:501
#12 0xb6f46d8a in IA__g_cclosure_marshal_VOID__VOID (closure=0x80f0730,
return_value=0x0, n_param_values=1, param_values=0xbfe5fafc,
invocation_hint=0xbfe5fa0c, marshal_data=0x8052029) at gmarshal.c:77
#13 0xb6f3a87e in IA__g_closure_invoke (closure=0x80f0730,
return_value=0x0,
n_param_values=1, param_values=0xbfe5fafc,
invocation_hint=0xbfe5fa0c)
at gclosure.c:490
#14 0xb6f4a2fe in signal_emit_unlocked_R (node=0x80f0840, detail=0,
instance=0x808d880, emission_return=0x0,
instance_and_params=0xbfe5fafc)
at gsignal.c:2440
#15 0xb6f4b7d7 in IA__g_signal_emit_valist (instance=0x808d880,
signal_id=136,
detail=0, var_args=0xbfe5fd3c ",\226����\222�") at gsignal.c:2199
#16 0xb6f4b990 in IA__g_signal_emit (instance=0x808d880, signal_id=136,
detail=0) at gsignal.c:2243
#17 0xb7837d54 in IA__gtk_widget_activate (widget=0x808d880)
at gtkwidget.c:4709
#18 0xb7733ad5 in IA__gtk_menu_shell_activate_item
(menu_shell=0x812a120,
menu_item=0x808d880, force_deactivate=1) at gtkmenushell.c:1150
#19 0xb7735555 in gtk_menu_shell_button_release (widget=0x812a120,
event=0x808cd50) at gtkmenushell.c:674
#20 0xb772cf98 in gtk_menu_button_release (widget=0x812a120,
event=0x808cd50)
---Type <return> to continue, or q <return> to quit---
at gtkmenu.c:2725
#21 0xb7727557 in _gtk_marshal_BOOLEAN__BOXED (closure=0x80a3df8,
return_value=0xbfe5ff90, n_param_values=2, param_values=0xbfe6006c,
invocation_hint=0xbfe5ff7c, marshal_data=0xb772ced3) at
gtkmarshalers.c:84
#22 0xb6f39115 in g_type_class_meta_marshal (closure=0x80a3df8,
return_value=0xbfe5ff90, n_param_values=2, param_values=0xbfe6006c,
invocation_hint=0xbfe5ff7c, marshal_data=0xb4) at gclosure.c:567
#23 0xb6f3a87e in IA__g_closure_invoke (closure=0x80a3df8,
return_value=0xbfe5ff90, n_param_values=2, param_values=0xbfe6006c,
invocation_hint=0xbfe5ff7c) at gclosure.c:490
#24 0xb6f4a928 in signal_emit_unlocked_R (node=0x80a40c0, detail=0,
instance=0x812a120, emission_return=0xbfe6022c,
instance_and_params=0xbfe6006c) at gsignal.c:2478
#25 0xb6f4b5a0 in IA__g_signal_emit_valist (instance=0x812a120,
signal_id=45,
detail=0, var_args=<value optimized out>) at gsignal.c:2209
#26 0xb6f4b990 in IA__g_signal_emit (instance=0x812a120, signal_id=45,
detail=0) at gsignal.c:2243
#27 0xb78337d2 in gtk_widget_event_internal (widget=0x812a120,
event=0x808cd50)
at gtkwidget.c:4678
#28 0xb772130f in IA__gtk_propagate_event (widget=0x812a120,
event=0x808cd50)
at gtkmain.c:2336
#29 0xb7722333 in IA__gtk_main_do_event (event=0x808cd50) at
gtkmain.c:1556
#30 0xb7579ee6 in gdk_event_dispatch (source=0x808f048, callback=0,
---Type <return> to continue, or q <return> to quit---
user_data=0x0) at gdkevents-x11.c:2351
#31 0xb6e9caaa in IA__g_main_context_dispatch (context=0x808f090)
at gmain.c:2003
#32 0xb6e9fc8b in g_main_context_iterate (context=0x808f090, block=1,
dispatch=1, self=0x8066190) at gmain.c:2636
#33 0xb6ea002e in IA__g_main_loop_run (loop=0x80ab5e0) at gmain.c:2844
#34 0xb7722787 in IA__gtk_main () at gtkmain.c:1163
#35 0x08050284 in main (argc=Cannot access memory at address 0x0
) at main.c:145

cya,
--
Iain Buchanan <iaindb at netspace dot net dot au>

Tuesday After Lunch is the cosmic time of the week.
Mark Ellis
2008-03-20 15:48:57 UTC
Permalink
Post by Iain Buchanan
Post by Mark Ellis
Post by Iain Buchanan
Hi,
Revision: 3320
...
Post by Mark Ellis
Post by Iain Buchanan
not sure how "ready" that commit is, but it crashes when I view device
status. Output below. Do you want a backtrace?
Obviously not ready at all :) Yes please, backtrace would be great.
sure :)
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6b406f0 (LWP 17508)]
0x0805afb6 in sync_item_sort (a=0x1, b=0x0) at device-info.c:648
648 device-info.c: No such file or directory.
in device-info.c
(gdb) thread apply all bt
#0 0x0805afb6 in sync_item_sort (a=0x1, b=0x0) at device-info.c:648
#1 0xb6e9a8bb in g_list_sort_real (list=<value optimized out>,
compare_func=0x805afb0 <sync_item_sort>, user_data=0x0) at
glist.c:906
#2 0xb6e9a87b in g_list_sort_real (list=0x8184e40,
compare_func=0x805afb0 <sync_item_sort>, user_data=0x0) at
glist.c:952
It's one of life's constant wonders that programming bugs always appear
where you least expect them :)

Ok, think I've fixed that now.

Mark
Iain Buchanan
2008-03-21 04:29:04 UTC
Permalink
Post by Mark Ellis
It's one of life's constant wonders that programming bugs always appear
where you least expect them :)
Ok, think I've fixed that now.
surprise!

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6b816f0 (LWP 32767)]
0x0805d740 in partners_setup_view_store_synceng (self=<value optimized
out>)
at device-info.c:830
830 device-info.c: No such file or directory.
in device-info.c
(gdb) thread apply all bt

Thread 1 (Thread 0xb6b816f0 (LWP 32767)):
#0 0x0805d740 in partners_setup_view_store_synceng (
self=<value optimized out>) at device-info.c:830
#1 0x0805dd0b in wm_device_info_set_property (obj=0x8151640,
property_id=1,
value=0xbf8e0918, pspec=0x80d49b8) at device-info.c:908
#2 0xb6f82669 in g_object_constructor (type=135087808,
n_construct_properties=1, construct_params=0x8171ba8) at
gobject.c:697
#3 0xb6f80777 in IA__g_object_newv (object_type=135087808,
n_parameters=1,
parameters=0x8168928) at gobject.c:937
#4 0xb6f813ab in IA__g_object_new_valist (object_type=135087808,
first_property_name=0x8060d3b "device", var_args=0xbf8e0b3c "")
at gobject.c:1027
#5 0xb6f814a0 in IA__g_object_new (object_type=135087808,
first_property_name=0x8060d3b "device") at gobject.c:795
#6 0x08052053 in menu_device_info (button=0x808d880, device=0x808cc60)
at synce-trayicon.c:501
#7 0xb6f87d8a in IA__g_cclosure_marshal_VOID__VOID (closure=0x80d3a00,
return_value=0x0, n_param_values=1, param_values=0xbf8e0d8c,
invocation_hint=0xbf8e0c9c, marshal_data=0x8052029) at gmarshal.c:77
#8 0xb6f7b87e in IA__g_closure_invoke (closure=0x80d3a00,
return_value=0x0,
n_param_values=1, param_values=0xbf8e0d8c,
invocation_hint=0xbf8e0c9c)
at gclosure.c:490
---Type <return> to continue, or q <return> to quit---
#9 0xb6f8b2fe in signal_emit_unlocked_R (node=0x80fd7b8, detail=0,
instance=0x808d880, emission_return=0x0,
instance_and_params=0xbf8e0d8c)
at gsignal.c:2440
#10 0xb6f8c7d7 in IA__g_signal_emit_valist (instance=0x808d880,
signal_id=128,
detail=0, var_args=0xbf8e0fcc ",����\017\227�") at gsignal.c:2199
#11 0xb6f8c990 in IA__g_signal_emit (instance=0x808d880, signal_id=128,
detail=0) at gsignal.c:2243
#12 0xb7878d54 in IA__gtk_widget_activate (widget=0x808d880)
at gtkwidget.c:4709
#13 0xb7774ad5 in IA__gtk_menu_shell_activate_item
(menu_shell=0x80e6138,
menu_item=0x808d880, force_deactivate=1) at gtkmenushell.c:1150
#14 0xb7776555 in gtk_menu_shell_button_release (widget=0x80e6138,
event=0x808cf80) at gtkmenushell.c:674
#15 0xb776df98 in gtk_menu_button_release (widget=0x80e6138,
event=0x808cf80)
at gtkmenu.c:2725
#16 0xb7768557 in _gtk_marshal_BOOLEAN__BOXED (closure=0x80a3df8,
return_value=0xbf8e1220, n_param_values=2, param_values=0xbf8e12fc,
invocation_hint=0xbf8e120c, marshal_data=0xb776ded3) at
gtkmarshalers.c:84
#17 0xb6f7a115 in g_type_class_meta_marshal (closure=0x80a3df8,
return_value=0xbf8e1220, n_param_values=2, param_values=0xbf8e12fc,
invocation_hint=0xbf8e120c, marshal_data=0xb4) at gclosure.c:567
#18 0xb6f7b87e in IA__g_closure_invoke (closure=0x80a3df8,
return_value=0xbf8e1220, n_param_values=2, param_values=0xbf8e12fc,
---Type <return> to continue, or q <return> to quit---
invocation_hint=0xbf8e120c) at gclosure.c:490
#19 0xb6f8b928 in signal_emit_unlocked_R (node=0x80a40c0, detail=0,
instance=0x80e6138, emission_return=0xbf8e14bc,
instance_and_params=0xbf8e12fc) at gsignal.c:2478
#20 0xb6f8c5a0 in IA__g_signal_emit_valist (instance=0x80e6138,
signal_id=45,
detail=0, var_args=<value optimized out>) at gsignal.c:2209
#21 0xb6f8c990 in IA__g_signal_emit (instance=0x80e6138, signal_id=45,
detail=0) at gsignal.c:2243
#22 0xb78747d2 in gtk_widget_event_internal (widget=0x80e6138,
event=0x808cf80)
at gtkwidget.c:4678
#23 0xb776230f in IA__gtk_propagate_event (widget=0x80e6138,
event=0x808cf80)
at gtkmain.c:2336
#24 0xb7763333 in IA__gtk_main_do_event (event=0x808cf80) at
gtkmain.c:1556
#25 0xb75baee6 in gdk_event_dispatch (source=0x808f048, callback=0,
user_data=0x0) at gdkevents-x11.c:2351
#26 0xb6eddaaa in IA__g_main_context_dispatch (context=0x808f090)
at gmain.c:2003
#27 0xb6ee0c8b in g_main_context_iterate (context=0x808f090, block=1,
dispatch=1, self=0x8066190) at gmain.c:2636
#28 0xb6ee102e in IA__g_main_loop_run (loop=0x80ab5e0) at gmain.c:2844
#29 0xb7763787 in IA__gtk_main () at gtkmain.c:1163
#30 0x08050284 in main (argc=0, argv=0x7) at main.c:145
(gdb)

:)
--
Iain Buchanan <iaindb at netspace dot net dot au>

"We need to change that attitude about how prolific we can be with the
people's money."

George W. Bush
March 16, 2001
Mark Ellis
2008-03-22 16:20:51 UTC
Permalink
Post by Iain Buchanan
Post by Mark Ellis
It's one of life's constant wonders that programming bugs always appear
where you least expect them :)
Ok, think I've fixed that now.
surprise!
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6b816f0 (LWP 32767)]
0x0805d740 in partners_setup_view_store_synceng (self=<value optimized
out>)
at device-info.c:830
830 device-info.c: No such file or directory.
in device-info.c
(gdb) thread apply all bt
#0 0x0805d740 in partners_setup_view_store_synceng (
self=<value optimized out>) at device-info.c:830
!!!??@@!!?

glib is a wonderful library, but just sometimes you wondr what they're
playing at.

Ok, that should be better now.

Mark
Iain Buchanan
2008-03-27 10:50:39 UTC
Permalink
Post by Mark Ellis
glib is a wonderful library, but just sometimes you wondr what they're
playing at.
Ok, that should be better now.
hm. I was going to say nothing happened, but there was some timeout
going on, and eventually I got this message:

"Failed to retrieve partnership information: Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken."

And the partnership list is empty. Pressing the "create" button does a
similar thing.

Console output:

$ synce-trayicon -f
** (synce-trayicon:17947): DEBUG: Running in foreground
** (synce-trayicon:17947): DEBUG: odccm_client_init_comms_impl: adding
device: /org/synce/odccm/Device/_2C343682_C645_9887_675F_401F60866DD0_
** (synce-trayicon:17947): DEBUG: odccm_add_device: Received connect
from
odccm: /org/synce/odccm/Device/_2C343682_C645_9887_675F_401F60866DD0_
** Message: Hal reports no devices connected
** (synce-trayicon:17947): DEBUG: device_connected_cb: looking for
preexisting device IO2
** (synce-trayicon:17947): DEBUG: module_load_all: loading
module /usr/lib/synce-trayicon/modules/gnomevfs-trayicon-module.so
** (synce-trayicon:17947): DEBUG: module_load_all: loading
module /usr/lib/synce-trayicon/modules/test-mod.so
** (synce-trayicon:17947): DEBUG: g_module_check_init: running from
trayicon test module for /usr/lib/synce-trayicon/modules/test-mod.so


(message popped up here)


** (synce-trayicon:17947): CRITICAL **:
partners_setup_view_store_synceng: Error fetching sync item list: Did
not receive a reply. Possible causes include: the remote application did
not send a reply, the message bus security policy blocked the reply, the
reply timeout expired, or the network connection was broken.

(synce-trayicon:17947): Gtk-CRITICAL **: gtk_tree_view_get_selection:
assertion `GTK_IS_TREE_VIEW (tree_view)' failed
** (synce-trayicon:17947): DEBUG:
partners_create_button_clicked_synceng_cb: create button_clicked

** (synce-trayicon:17947): CRITICAL **:
partners_create_button_clicked_synceng_cb: Error creating partnership
via sync-engine: Did not receive a reply. Possible causes include: the
remote application did not send a reply, the message bus security policy
blocked the reply, the reply timeout expired, or the network connection
was broken.
** (synce-trayicon:17947): DEBUG: module_disconnect_func: running from
trayicon test module for IO2

(synce-trayicon:17947): GLib-GObject-WARNING **:
IA__g_object_weak_unref: couldn't find weak ref 0x805b0a2(0x814f540)

:) thanks,
--
Iain Buchanan <iaindb at netspace dot net dot au>

Misery loves company, but company does not reciprocate.
Mark Ellis
2008-03-27 11:04:10 UTC
Permalink
Post by Iain Buchanan
Post by Mark Ellis
glib is a wonderful library, but just sometimes you wondr what they're
playing at.
Ok, that should be better now.
hm. I was going to say nothing happened, but there was some timeout
"Failed to retrieve partnership information: Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken."
And the partnership list is empty. Pressing the "create" button does a
similar thing.
$ synce-trayicon -f
** (synce-trayicon:17947): DEBUG: Running in foreground
** (synce-trayicon:17947): DEBUG: odccm_client_init_comms_impl: adding
device: /org/synce/odccm/Device/_2C343682_C645_9887_675F_401F60866DD0_
** (synce-trayicon:17947): DEBUG: odccm_add_device: Received connect
from
odccm: /org/synce/odccm/Device/_2C343682_C645_9887_675F_401F60866DD0_
** Message: Hal reports no devices connected
** (synce-trayicon:17947): DEBUG: device_connected_cb: looking for
preexisting device IO2
** (synce-trayicon:17947): DEBUG: module_load_all: loading
module /usr/lib/synce-trayicon/modules/gnomevfs-trayicon-module.so
** (synce-trayicon:17947): DEBUG: module_load_all: loading
module /usr/lib/synce-trayicon/modules/test-mod.so
** (synce-trayicon:17947): DEBUG: g_module_check_init: running from
trayicon test module for /usr/lib/synce-trayicon/modules/test-mod.so
(message popped up here)
partners_setup_view_store_synceng: Error fetching sync item list: Did
not receive a reply. Possible causes include: the remote application did
not send a reply, the message bus security policy blocked the reply, the
reply timeout expired, or the network connection was broken.
I don't understand why this is, sync-engine is obviously running because
a connection is available, so why a simple request to provide sync types
should fail is bizarre.
Post by Iain Buchanan
assertion `GTK_IS_TREE_VIEW (tree_view)' failed
Yeah this is bizarre too, Adam Williamson is seeing the same thing. Can
you try it with the attached debugging patch.
Post by Iain Buchanan
partners_create_button_clicked_synceng_cb: create button_clicked
partners_create_button_clicked_synceng_cb: Error creating partnership
via sync-engine: Did not receive a reply. Possible causes include: the
remote application did not send a reply, the message bus security policy
blocked the reply, the reply timeout expired, or the network connection
was broken.
When you see this result, can you run the following command to make sure
sync-engine is responding, sorry this is going to word wrap horribly :)

dbus-send --session --type=method_call --print-reply
--dest=org.synce.SyncEngine /org/synce/SyncEngine
org.synce.SyncEngine.GetItemTypes

And you could also try

dbus-send --session --type=method_call --print-reply
--dest=org.synce.SyncEngine /org/synce/SyncEngine
org.synce.SyncEngine.GetPartnerships


Mark
Post by Iain Buchanan
** (synce-trayicon:17947): DEBUG: module_disconnect_func: running from
trayicon test module for IO2
IA__g_object_weak_unref: couldn't find weak ref 0x805b0a2(0x814f540)
:) thanks,
Iain Buchanan
2008-03-27 12:15:51 UTC
Permalink
Post by Iain Buchanan
hm. I was going to say nothing happened, but there was some timeout
[snip]

ok, I think it was some weird connection problem like a bad cable or
something. It seems to be showing the partnership now, although the
Index column has all zero's in it for partnership items (is this just
the partnership index ala list_partnerships.py?) and no items are
active, even though I have contacts in this partnership.

Well I'll have to continue another night. Let me know if you want more
debugging info :)

thanks heaps,
--
Iain Buchanan <iaindb at netspace dot net dot au>

If you lived today as if it were your last, you'd buy up a box of rockets
and fire them all off, wouldn't you?
-- Garrison Keillor
Mark Ellis
2008-03-27 15:37:18 UTC
Permalink
Post by Iain Buchanan
Post by Iain Buchanan
hm. I was going to say nothing happened, but there was some timeout
[snip]
ok, I think it was some weird connection problem like a bad cable or
something. It seems to be showing the partnership now, although the
Index column has all zero's in it for partnership items (is this just
the partnership index ala list_partnerships.py?) and no items are
active, even though I have contacts in this partnership.
Well I'll have to continue another night. Let me know if you want more
debugging info :)
thanks heaps,
Yeah I couldn't quite work out what to do with the display, so it
probably doesn't make much sense at the moment. Can you do me a
screenshot of the partnership display, and I can try and fix it up a
bit.

Mark

Guido Diepen
2008-03-27 12:19:44 UTC
Permalink
Hi Mark,
Post by Mark Ellis
I don't understand why this is, sync-engine is obviously running because
a connection is available, so why a simple request to provide sync types
should fail is bizarre.
I think it does not fail, it just takes too long. In case sync-engine is
doing some stuff on the phone, other calls that depend on the
process_config rapi-call might block. For example, when you are
uninstalling a program, which is done through a process_config, retrieving
a list of installed programs or any other call that makes use of
process_config seems to block.

I have seen some minor issues with this also when I rewrote synce-kpm to
use dbus. I solved it by adding a larger timeout while calling the
function (which in python is done via adding a timeout=xxx parameter to
the original dbus-call)


Guido Diepen
--
Aviation is proof that given the will, we have the capacity to achieve
the impossible.
--Eddie Rickenbacker
Loading...