Ticket #9545 (new defect)

Opened 5 years ago

Last modified 4 years ago

icons persist in Neighborhood View after resources gone

Reported by: mikus Owned by: marco
Priority: normal Milestone: 1.5-software-later
Component: sugar Version: Development build as of this date
Keywords: Cc: sayamindu, sascha_silbe
Action Needed: never set Verified: no
Deployments affected: Blocked By:
Blocking:

Description

Started ad-hoc network. Started Chat and Write and in each clicked on "share with neighborhood" - their icons showed up in own Neighborhood View. Stopped Chat and Write. Stopped ad-hoc network (would not disconnect from Neighborhood View icon - would from Frame icon).

The icons for Chat and Write *persist* in Neighborhood View (for at least 20 minutes), even though those Activities are no longer active.

Attachments

snap.png (28.6 kB) - added by mikus 5 years ago.
Neigh. showing leftover icons - frame shows those activities gone. (Customized 'me' icon)

Change History

Changed 5 years ago by mikus

Neigh. showing leftover icons - frame shows those activities gone. (Customized 'me' icon)

follow-up: ↓ 3   Changed 5 years ago by mikus

The icons for Chat and Write showed up again on Neighborhood View - some minutes **after** a reboot. [Those Activities themselves were not ever launched after the reboot.]

  Changed 5 years ago by dsd

  • cc sayamindu added

in reply to: ↑ 1 ; follow-up: ↓ 4   Changed 5 years ago by sayamindu

Replying to mikus:

The icons for Chat and Write showed up again on Neighborhood View - some minutes **after** a reboot. [Those Activities themselves were not ever launched after the reboot.]

Were these ghost icons (slightly grayed out) ? I remember some discussions on the sugar IRC channel about the ejabberd server that is being used as causing these ghost icons to appear (a server restarted was required to get rid of the icons).

in reply to: ↑ 3   Changed 5 years ago by mikus

Replying to sayamindu:

Were these ghost icons (slightly grayed out) ?

They were fully colored, as far as I could tell.

I remember some discussions on the sugar IRC channel about the ejabberd server that is being used as causing these ghost icons to appear (a server restarted was required to get rid of the icons).

I was not using ejabberd, but an ad-hoc network between the two XOs.


Just now, I tried to duplicate the #9545 problem using an XO-1 running build 9 and an XO-1.5 running build 46. The problem did NOT show up today - Neighborhood View showed only the Activities which either were still running in the same XO, or for which another XO had issued a 'share with me' invitation. Whenever the "sharing" XO closed its Activity, that Activity's icon was immediately removed from the Neighborhood View of an XO which was not a participant.

When I have the time for it, I will repeat the test using four XOs on the ad-hoc network.

  Changed 5 years ago by triagebot

  • milestone changed from 1.5-software to 1.5-software-update

changed by irc user Quozl:

  Changed 5 years ago by Quozl

I've also reproduced unintended persistence of neighbourhood view activity icons on os64, in the context of an ad-hoc network.

  Changed 4 years ago by erikos

I did testing this for quite a while and was only able to produce one unintentional behavior. One activity was still showing on machine B even so it was closed on A (was never opened on B). Would be great to get a reproducible way for this bug.

  Changed 4 years ago by sascha_silbe

  • cc sascha_silbe added

I've seen the same symptom quite a few times on different hardware (XO-1 without idle-suspend, desktop PC; wired / WLAN in infrastructure mode). Hopefully Tomeus work on making Sugar a regular Telepathy client will either fix it or at least make it easier to pinpoint.

  Changed 4 years ago by Quozl

Related #10308.

follow-up: ↓ 11   Changed 4 years ago by mikus

I was testing the new ad-hoc wireless network support per #9845. After I shut down all XOs that had participated in the ad-hoc connection, the remaining XO-1s in the environment - some os851, some os373py (they were without the #9845 rpms, and had continued to maintain contact over the MESH, independent of the ad-hoc network) - *continued* to display in their Neighborhood an icon for (connecting to) the (now no longer existing) ad-hoc network.

in reply to: ↑ 10   Changed 4 years ago by Quozl

Replying to mikus:

... *continued* to display in their Neighborhood an icon for (connecting to) the (now no longer existing) ad-hoc network.

Different icon types have different expiry mechanisms. Radio scan results (that you refer to now) do indeed seem to expire at a much different rate to the shared activity icons (that were initially referred to in this ticket). They will be different causes, I expect.

Note: See TracTickets for help on using tickets.