trayicon

[Iain Buchanan]

Hi Mark,

thanks for the recent svn commits - trayicon is more stable now!

Hi,
didn't see your message - I went offline for a little while. Can you
get to #synce easily?
Explore with filemanager works. The popup % readings work. View device
status crashes it!

Excellent !

(synce-trayicon:3563): GLib-WARNING **: GError set over the top of a
previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL
before it's set.
The overwriting error message was: The name org.synce.SyncEngine was not
provided by any .service files
The trace wasn't very useful. Do you want me to get a better one?
thanks,

No, that's fine for now. This is happening in the code for displaying
partnerships for WM5, which is really really experimental. That's next
on my list of things to do. I'll keep you up to date on how its going.
In the meantime, if you want to avoid the crash, in the file
src/device_info.c is a function partners_setup_view. If you put in a
return; statement as the very first line, it'll skip the whole
partnership code, and you'll be able to try the other parts of the
device info dialog.

This wasn't necessary.

[Mark Ellis]

Post by Iain Buchanan
Hi Mark,
thanks for the recent svn commits - trayicon is more stable now!

Hi,
didn't see your message - I went offline for a little while. Can you
get to #synce easily?
Explore with filemanager works. The popup % readings work. View device
status crashes it!

Excellent !

(synce-trayicon:3563): GLib-WARNING **: GError set over the top of a
previous GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL
before it's set.
The overwriting error message was: The name org.synce.SyncEngine was not
provided by any .service files
The trace wasn't very useful. Do you want me to get a better one?
thanks,

No, that's fine for now. This is happening in the code for displaying
partnerships for WM5, which is really really experimental. That's next
on my list of things to do. I'll keep you up to date on how its going.
In the meantime, if you want to avoid the crash, in the file
src/device_info.c is a function partners_setup_view. If you put in a
return; statement as the very first line, it'll skip the whole
partnership code, and you'll be able to try the other parts of the
device info dialog.

This wasn't necessary.

[Iain Buchanan]

Hi Mark,

welcome back! Hope your trip was ( holiday ? enjoyable : productive )!
[snip]

Hi Iain
I'd just like to say doh! Wrong bus, I needed session, not system, try
it now for the partnership list.

I started odccm, then sync-engine, then trayicon -f. This is the
console output:

$ synce-trayicon -f
** (synce-trayicon:20723): DEBUG: Running in foreground
** (synce-trayicon:20723): DEBUG: odccm_client_init_comms_impl: adding
device: /org/synce/odccm/Device/_2C343682_C645_9887_675F_401F60866DD0_
** (synce-trayicon:20723): 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:20723): DEBUG: device_connected_cb: looking for
preexisting device IO2

** (synce-trayicon:20723): WARNING **:
wm_device_manager_find_by_name_impl: Device IO2 not found
** (synce-trayicon:20723): DEBUG: module_load_all: loading
module /usr/lib/synce-trayicon/modules/gnomevfs-trayicon-module.so
** (synce-trayicon:20723): DEBUG: module_load_all: loading
module /usr/lib/synce-trayicon/modules/test-mod.so
** (synce-trayicon:20723): DEBUG: g_module_check_init: running from
trayicon test module for /usr/lib/synce-trayicon/modules/test-mod.so


===== Select "View device status" =====


(synce-trayicon:20723): GLib-GObject-CRITICAL **: g_value_get_pointer:
assertion `G_VALUE_HOLDS_POINTER (value)' failed

(synce-trayicon:20723): GLib-GObject-CRITICAL **: g_value_get_pointer:
assertion `G_VALUE_HOLDS_POINTER (value)' failed

(synce-trayicon:20723): GLib-CRITICAL **: g_array_free: assertion
`array' failed


===== Select the (only) partnership =====


** (synce-trayicon:20723): DEBUG: partners_selection_changed_cb: You
selected index 0, id 7518327, name orpheus


===== PDA went into standby, then I turned it back on =====


** (synce-trayicon:20766): DEBUG: module_disconnect_func: running from
trayicon test module for IO2
** (synce-trayicon:20766): 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:20766): WARNING **: synce_info_from_odccm: Failed to
get a connection for IO2: 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.
** Message: Hal reports no devices connected


And now trayicon doesn't respond (clicking on icon doesn't bring up
menu).

The create and remove buttons were greyed out. The Battery status etc.
looked good as usual.

thanks,

[Mark Ellis]

Post by Iain Buchanan
Hi Mark,
welcome back! Hope your trip was ( holiday ? enjoyable : productive )!
[snip]

Hi Iain
I'd just like to say doh! Wrong bus, I needed session, not system, try
it now for the partnership list.

I started odccm, then sync-engine, then trayicon -f. This is the
$ synce-trayicon -f
** (synce-trayicon:20723): DEBUG: Running in foreground
** (synce-trayicon:20723): DEBUG: odccm_client_init_comms_impl: adding
device: /org/synce/odccm/Device/_2C343682_C645_9887_675F_401F60866DD0_
** (synce-trayicon:20723): 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:20723): DEBUG: device_connected_cb: looking for
preexisting device IO2
wm_device_manager_find_by_name_impl: Device IO2 not found
** (synce-trayicon:20723): DEBUG: module_load_all: loading
module /usr/lib/synce-trayicon/modules/gnomevfs-trayicon-module.so
** (synce-trayicon:20723): DEBUG: module_load_all: loading
module /usr/lib/synce-trayicon/modules/test-mod.so
** (synce-trayicon:20723): DEBUG: g_module_check_init: running from
trayicon test module for /usr/lib/synce-trayicon/modules/test-mod.so
===== Select "View device status" =====
assertion `G_VALUE_HOLDS_POINTER (value)' failed
assertion `G_VALUE_HOLDS_POINTER (value)' failed
(synce-trayicon:20723): GLib-CRITICAL **: g_array_free: assertion
`array' failed

Hmm, so near and yet so far. I know exactly what this is, but
unfortunately dont know how to fix it yet. Using dbus in C with
moderately complex method signatures gets a bit hairy, documentation is
sparse, and there dont seem to be many examples out there to follow. But
we'll get there.

Post by Iain Buchanan
===== Select the (only) partnership =====
** (synce-trayicon:20723): DEBUG: partners_selection_changed_cb: You
selected index 0, id 7518327, name orpheus

Can I assume this is corrrect, and there is one partnership called
orpheus ?

Post by Iain Buchanan
===== PDA went into standby, then I turned it back on =====
** (synce-trayicon:20766): DEBUG: module_disconnect_func: running from
trayicon test module for IO2
** (synce-trayicon:20766): 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:20766): WARNING **: synce_info_from_odccm: Failed to
get a connection for IO2: 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.
** Message: Hal reports no devices connected
And now trayicon doesn't respond (clicking on icon doesn't bring up
menu).

Ooo, that looks nasty, I wonder whats causing that ? When the device
goes into standby it is obviously picked up by odccm, and trayicon
registers that, but I can't think why it should have trouble
reconnecting. I might have to send you a patch with lots of debug
statements at some point, but in the meantime I've committed a fix that
will hopefully stop the freezing.

Post by Iain Buchanan
The create and remove buttons were greyed out. The Battery status etc.
looked good as usual.

That's ok, I've deliberately disabled them until I can at least list
partnerships correctly.

Ta
Mark

[Iain Buchanan]

Post by Mark Ellis

Post by Iain Buchanan
===== Select the (only) partnership =====
** (synce-trayicon:20723): DEBUG: partners_selection_changed_cb: You
selected index 0, id 7518327, name orpheus

Can I assume this is corrrect, and there is one partnership called
orpheus ?

sorry, yes!

Post by Mark Ellis

Post by Iain Buchanan
===== PDA went into standby, then I turned it back on =====
And now trayicon doesn't respond (clicking on icon doesn't bring up
menu).

Ooo, that looks nasty, I wonder whats causing that ? When the device
goes into standby it is obviously picked up by odccm, and trayicon
registers that, but I can't think why it should have trouble
reconnecting. I might have to send you a patch with lots of debug
statements at some point, but in the meantime I've committed a fix that
will hopefully stop the freezing.

bring on the patch!

The current svn doesn't lockup when I disconnect:

** (synce-trayicon:26773): DEBUG: module_disconnect_func: running from
trayicon test module for IO2

and reconnect:

** (synce-trayicon:26773): 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:26773): DEBUG: device_connected_cb: looking for
preexisting device IO2

** (synce-trayicon:26773): WARNING **:
wm_device_manager_find_by_name_impl: Device IO2 not found
** (synce-trayicon:26773): DEBUG: module_connect_func: running from
trayicon test module for IO2


that warning about "Device IO2 not found" comes up a lot throughout the
process. (IO2 is the name of my device). It doesn't appear to be
fatal.

Post by Mark Ellis

Post by Iain Buchanan
The create and remove buttons were greyed out. The Battery status etc.
looked good as usual.

That's ok, I've deliberately disabled them until I can at least list
partnerships correctly.

np. The icon is still an "x" as well. Not sure why... I'm looking
through strace and such, will keep you posted.

thanks,

[Mark Ellis]

Post by Iain Buchanan

Post by Mark Ellis

Post by Iain Buchanan
===== Select the (only) partnership =====
** (synce-trayicon:20723): DEBUG: partners_selection_changed_cb: You
selected index 0, id 7518327, name orpheus

Can I assume this is corrrect, and there is one partnership called
orpheus ?

sorry, yes!

Post by Mark Ellis

Post by Iain Buchanan
===== PDA went into standby, then I turned it back on =====
And now trayicon doesn't respond (clicking on icon doesn't bring up
menu).

Ooo, that looks nasty, I wonder whats causing that ? When the device
goes into standby it is obviously picked up by odccm, and trayicon
registers that, but I can't think why it should have trouble
reconnecting. I might have to send you a patch with lots of debug
statements at some point, but in the meantime I've committed a fix that
will hopefully stop the freezing.

bring on the patch!
** (synce-trayicon:26773): DEBUG: module_disconnect_func: running from
trayicon test module for IO2
** (synce-trayicon:26773): 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:26773): DEBUG: device_connected_cb: looking for
preexisting device IO2
wm_device_manager_find_by_name_impl: Device IO2 not found
** (synce-trayicon:26773): DEBUG: module_connect_func: running from
trayicon test module for IO2

Hooray !

Post by Iain Buchanan
that warning about "Device IO2 not found" comes up a lot throughout the
process. (IO2 is the name of my device). It doesn't appear to be
fatal.

Yeah, I need to change that, it's just a check to make sure that it
doesn't already know about the device, so it's not actually a warning.

Post by Iain Buchanan

Post by Mark Ellis

Post by Iain Buchanan
The create and remove buttons were greyed out. The Battery status etc.
looked good as usual.

That's ok, I've deliberately disabled them until I can at least list
partnerships correctly.

np. The icon is still an "x" as well. Not sure why... I'm looking
through strace and such, will keep you posted.

Ok, I'll have a think.

Ta
Mark

[Mark Ellis]

Post by Mark Ellis

Post by Iain Buchanan

Post by Mark Ellis

Post by Iain Buchanan
===== Select the (only) partnership =====
** (synce-trayicon:20723): DEBUG: partners_selection_changed_cb: You
selected index 0, id 7518327, name orpheus

Can I assume this is corrrect, and there is one partnership called
orpheus ?

sorry, yes!

Ok, commited a patch which should retrieve the partnership info
properly. I haven't done anything else with the display yet, but all the
details of the partnership will be sent to the console so we can check
it. Now for adding and removing ....

Post by Mark Ellis

Post by Iain Buchanan

Post by Mark Ellis

Post by Iain Buchanan
===== PDA went into standby, then I turned it back on =====
And now trayicon doesn't respond (clicking on icon doesn't bring up
menu).

Ooo, that looks nasty, I wonder whats causing that ? When the device
goes into standby it is obviously picked up by odccm, and trayicon
registers that, but I can't think why it should have trouble
reconnecting. I might have to send you a patch with lots of debug
statements at some point, but in the meantime I've committed a fix that
will hopefully stop the freezing.

bring on the patch!
** (synce-trayicon:26773): DEBUG: module_disconnect_func: running from
trayicon test module for IO2
** (synce-trayicon:26773): 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:26773): DEBUG: device_connected_cb: looking for
preexisting device IO2
wm_device_manager_find_by_name_impl: Device IO2 not found
** (synce-trayicon:26773): DEBUG: module_connect_func: running from
trayicon test module for IO2

Hooray !

Post by Iain Buchanan
that warning about "Device IO2 not found" comes up a lot throughout the
process. (IO2 is the name of my device). It doesn't appear to be
fatal.

Yeah, I need to change that, it's just a check to make sure that it
doesn't already know about the device, so it's not actually a warning.

And now I've got rid of it at last.

Post by Mark Ellis

Post by Iain Buchanan

Post by Mark Ellis

Post by Iain Buchanan
The create and remove buttons were greyed out. The Battery status etc.
looked good as usual.

That's ok, I've deliberately disabled them until I can at least list
partnerships correctly.

np. The icon is still an "x" as well. Not sure why... I'm looking
through strace and such, will keep you posted.

Ok, I'll have a think.

Here's a thought. You're gentoo yes ? Keep in mind I know nothing about
gentoo. Did you install via some build mechanism/package manager, or
manually ?

If DESTDIR is set at install time, the icon cache is not updated, the
assumption being it's building a package for later installation. Check
the output from make install for gtk-update-icon-cache.

Or it could be some kind of gnome prefix thing ?

Mark

[Iain Buchanan]

Hi again,

Post by Mark Ellis
Ok, commited a patch which should retrieve the partnership info
properly. I haven't done anything else with the display yet, but all the
details of the partnership will be sent to the console so we can check
it. Now for adding and removing ....

output now looks like this:
$ synce-trayicon -f
** (synce-trayicon:23503): DEBUG: Running in foreground
** (synce-trayicon:23503): DEBUG: odccm_client_init_comms_impl: adding device: /org/synce/odccm/Device/_2C343682_C645_9887_675F_401F60866DD0_
** (synce-trayicon:23503): 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:23503): DEBUG: device_connected_cb: looking for preexisting device IO2
** (synce-trayicon:23503): DEBUG: module_load_all: loading module /usr/lib/synce-trayicon/modules/gnomevfs-trayicon-module.so
** (synce-trayicon:23503): DEBUG: module_load_all: loading module /usr/lib/synce-trayicon/modules/test-mod.so
** (synce-trayicon:23503): DEBUG: g_module_check_init: running from trayicon test module for /usr/lib/synce-trayicon/modules/test-mod.so

select "view device status"

** (synce-trayicon:23503): DEBUG: partners_setup_view_store_synceng: partnership 0 id: 7518327
** (synce-trayicon:23503): DEBUG: partners_setup_view_store_synceng: partnership 0 guid: {170E2CCA-6426-ECB9-500F-FF955915708E}
** (synce-trayicon:23503): DEBUG: partners_setup_view_store_synceng: partnership 0 name: Orpheus
** (synce-trayicon:23503): DEBUG: partners_setup_view_store_synceng: partnership 0 host name: orpheus
** (synce-trayicon:23503): DEBUG: partners_setup_view_store_synceng: partnership 0 device name: IO2
** (synce-trayicon:23503): DEBUG: partners_setup_view_store_synceng: partnership 0 sync_items 0: 0
** (synce-trayicon:23503): DEBUG: partners_setup_view_store_synceng: partnership 0 sync_items 1: 7
** (synce-trayicon:23503): DEBUG: partners_setup_view_store_synceng: partnership 0 sync_items 2: 1

select partnership

** (synce-trayicon:23503): DEBUG: partners_selection_changed_cb: You selected index 0, id 7518327, name orpheus

and that's it. This is some output from sync-engine:

2008-03-19 09:51:53,289 INFO engine.partnerships.Partnership :
AttemptToBind : bound partnership P1: id=0x72b877,
guid="{170E2CCA-6426-ECB9-500F-FF955915708E}", hostname="orpheus",
name="Orpheus", sync_items=[ Calendar, Tasks, Contacts ] - running
config

so that seems to match up.

Post by Mark Ellis

Post by Mark Ellis

Post by Iain Buchanan
np. The icon is still an "x" as well. Not sure why... I'm looking
through strace and such, will keep you posted.

Ok, I'll have a think.

Here's a thought. You're gentoo yes ? Keep in mind I know nothing about
gentoo. Did you install via some build mechanism/package manager, or
manually ?

I installed through the package manager for which I created the
package :)

Post by Mark Ellis
If DESTDIR is set at install time, the icon cache is not updated, the
assumption being it's building a package for later installation. Check
the output from make install for gtk-update-icon-cache.

ah, now you're talking sense :) I didn't call gtk-update-icon-cache :)
There's a package feature to do that in Gentoo, but I'm having problems
with it. When I updated other gnome packages (which ran
gtk-update-icon-cache) I now see the icon. So it's not your fault, it
was mine!

thanks,

[Mark Ellis]

Post by Iain Buchanan
Hi again,

Post by Mark Ellis
Ok, commited a patch which should retrieve the partnership info
properly. I haven't done anything else with the display yet, but all the
details of the partnership will be sent to the console so we can check
it. Now for adding and removing ....

$ synce-trayicon -f
** (synce-trayicon:23503): DEBUG: Running in foreground
** (synce-trayicon:23503): DEBUG: odccm_client_init_comms_impl: adding device: /org/synce/odccm/Device/_2C343682_C645_9887_675F_401F60866DD0_
** (synce-trayicon:23503): 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:23503): DEBUG: device_connected_cb: looking for preexisting device IO2
** (synce-trayicon:23503): DEBUG: module_load_all: loading module /usr/lib/synce-trayicon/modules/gnomevfs-trayicon-module.so
** (synce-trayicon:23503): DEBUG: module_load_all: loading module /usr/lib/synce-trayicon/modules/test-mod.so
** (synce-trayicon:23503): DEBUG: g_module_check_init: running from trayicon test module for /usr/lib/synce-trayicon/modules/test-mod.so
select "view device status"
** (synce-trayicon:23503): DEBUG: partners_setup_view_store_synceng: partnership 0 id: 7518327
** (synce-trayicon:23503): DEBUG: partners_setup_view_store_synceng: partnership 0 guid: {170E2CCA-6426-ECB9-500F-FF955915708E}
** (synce-trayicon:23503): DEBUG: partners_setup_view_store_synceng: partnership 0 name: Orpheus
** (synce-trayicon:23503): DEBUG: partners_setup_view_store_synceng: partnership 0 host name: orpheus
** (synce-trayicon:23503): DEBUG: partners_setup_view_store_synceng: partnership 0 device name: IO2
** (synce-trayicon:23503): DEBUG: partners_setup_view_store_synceng: partnership 0 sync_items 0: 0
** (synce-trayicon:23503): DEBUG: partners_setup_view_store_synceng: partnership 0 sync_items 1: 7
** (synce-trayicon:23503): DEBUG: partners_setup_view_store_synceng: partnership 0 sync_items 2: 1
select partnership
** (synce-trayicon:23503): DEBUG: partners_selection_changed_cb: You selected index 0, id 7518327, name orpheus
AttemptToBind : bound partnership P1: id=0x72b877,
guid="{170E2CCA-6426-ECB9-500F-FF955915708E}", hostname="orpheus",
name="Orpheus", sync_items=[ Calendar, Tasks, Contacts ] - running
config
so that seems to match up.

Excellent, getting somewhere. I've just committed some improvements to
the UI, and add and remove partnership stuff.

Mark