On Tue, Sep 16, 2014 at 02:14:56PM -0400, Martin Abente wrote:
James, Gonzalo,
Regarding the IBSS/Ad-hoc scenario, if I set the address manually,
collaborations work just fine. So this must be related to network
discovery.
Thanks, that's interesting. Can you tell me _how_ you set the
Hello James,
On Wed, Sep 17, 2014 at 5:18 AM, James Cameron qu...@laptop.org wrote:
On Tue, Sep 16, 2014 at 02:14:56PM -0400, Martin Abente wrote:
James, Gonzalo,
Regarding the IBSS/Ad-hoc scenario, if I set the address manually,
collaborations work just fine. So this must be related to
I enabled telepathy-salut logs by adding these to /etc/environment (note
that changing debug file does not work anymore):
G_MESSAGES_DEBUG=all
SALUT_DEBUG=all
SALUT_LOGFILE=/home/olpc/salut.log
I see a lot of activity when I connect to an access point (or to modified
ad-hoc network), but I when
Adding a gateway fixes Salut over ad-hoc.
For instance, using the pre-defined Ad-hoc Network 11, then typing
this command, makes buddy icons and shared activities appear:
sudo ip route add default via 169.254.1.1
The IP chosen need not exist on the network.
Therefore, it wasn't the
On Thu, Sep 18, 2014 at 10:38:56AM +1000, James Cameron wrote:
Adding a gateway fixes Salut over ad-hoc.
For instance, using the pre-defined Ad-hoc Network 11, then typing
this command, makes buddy icons and shared activities appear:
sudo ip route add default via 169.254.1.1
The
Summary: partially solved with new kernel.
The Chat activity was run with debug logging in Terminal:
% SUGAR_LOGGER_LEVEL=debug sugar-launch org.laptop.Chat
At the time the activity was shared, the log showed:
1410842095.436535 DEBUG sugar3.presence.activity: _ShareCommand object at
Thanks James for research and reporting!
On Tue, Sep 16, 2014 at 4:53 AM, James Cameron qu...@laptop.org wrote:
Summary: partially solved with new kernel.
The Chat activity was run with debug logging in Terminal:
% SUGAR_LOGGER_LEVEL=debug sugar-launch org.laptop.Chat
At the time
Hello James,
I included the new kernel (and reverted that commit) and now collaboration
works even between fc20+S0.102 and F18+S0.100.
I tested it using a wifi network (with DHCP enabled) and Chat activity.
Really awesome work James!
On Tue, Sep 16, 2014 at 3:53 AM, James Cameron
James, Gonzalo,
Regarding the IBSS/Ad-hoc scenario, if I set the address manually,
collaborations work just fine. So this must be related to network discovery.
My test goes like this:
* I use one XO with fc18+S0.100 to create an ad-hoc network network.
* From another XO, with fc20+S0.102, I
James, didn't we have an avahi workaround for this kinda thing before in the olden days, where having a simultaneous USB Ethernet and wireless connection caused self-assigned addresses to mess up the buddy visibility?I may be mis-remembering, or it may have been an unrelated issue, but forgive
G'day,
Activities shared by Fedora 20 systems do not appear in Network
Neighbourhood on Fedora 18 or Fedora 20 systems. Buddies appear.
Activities shared by Fedora 18 Sugar 0.98 systems appear.
So this is a failure to announce sharing of activities on Sugar 0.102
on Fedora 20.
tcpdump shows
11 matches
Mail list logo
