Opened 6 years ago

Closed 6 years ago

#7776 closed defect (fixed)

Access point and mesh circles don't show up on neighborhood view

Reported by: carrano Owned by: cscott
Priority: blocker Milestone: 8.2.0 (was Update.2)
Component: distro Version: not specified
Keywords: Cc: mtd, garycmartin
Blocked By: Blocking:
Deployments affected: Action Needed: qa signoff
Verified: no

Description

Updated from candidate-708 to joyride-2245

Only other XOs show up on the neighborhood view. No access points and no icons for mesh (1, 6 or 11).

Attachments (2)

shell.log (14.4 KB) - added by garycmartin 6 years ago.
shell.log from joyride-2248
messages (55.2 KB) - added by garycmartin 6 years ago.
messages file from joyride-2248

Download all attachments as: .zip

Change History (25)

comment:1 Changed 6 years ago by carrano

Just to add that iwlist scan returns the access points correctly.

comment:2 Changed 6 years ago by carrano

Another piece of information. Downgrading to joyride-2200 fixes this. So the bug is somewhere between joyride-2201 and joyride-2245.

comment:3 follow-up: Changed 6 years ago by tvoverbeek

It does work properly on joyride-2230 (XOs, accesspoints and mesh icons show).

comment:4 in reply to: ↑ 3 Changed 6 years ago by carrano

Replying to tvoverbeek:

It does work properly on joyride-2230 (XOs, accesspoints and mesh icons show).

Good! It seems that this narrows down the problem to the following changes:

(some of this itens are not natural candidates, of course, and the kernel has beem replaced twice)

+olpc-utils 0.82-1.olpc3

+sugar-artwork 0.81.3-1.olpc3

+sugar-journal 96-1.fc9

+sugar 0.81.8-1.fc9

+sugar-base 0.81.3-1.fc9

+sugar-datastore 0.8.4-1.fc9

+sugar-toolkit 0.81.8-1.fc9

+kernel 2.6.25-20080801.1.olpc.4cb5af5103d70b9

+rsyslog 3.18.1-1.fc9

+sugar-update-control 0.5-1

+olpc-contents 2.4-1

+olpc-update 2.13-1

+etoys 3.0.2068-1

+squeak-vm 3.10-3olpc7

+kernel 2.6.25-20080730.1.olpc.85e8ce3752b87a2

comment:5 Changed 6 years ago by Gerbal

Same or similar error
http://dev.laptop.org/ticket/7789

comment:6 follow-up: Changed 6 years ago by garycmartin

Just moved from joyride-2241 to 2248 and now seeing an empty neighborhood and no network access (just my XO icon in the centre). I should see 4 or 5 APs, and the 3 mesh channel icons.

ifconfig shows eth0 is up, but has no inet address associated with it. msh0 looked better (had an inet with an ipaddress), but I have no other mesh devices to test with.

Booting back to 2241 shows the neighborhood working again.

(FYI: A bunch of activities also fail to start under 2248. Log and Terminal are fine, but Paint and my own Moon activity immediately bomb after launch. Not sure if this is related).

comment:7 in reply to: ↑ 6 Changed 6 years ago by carrano

Replying to garycmartin:

Just moved from joyride-2241 to 2248 and now seeing an empty neighborhood and no network access (just my XO icon in the centre). I should see 4 or 5 APs, and the 3 mesh channel icons.

ifconfig shows eth0 is up, but has no inet address associated with it. msh0 looked better (had an inet with an ipaddress), but I have no other mesh devices to test with.

Booting back to 2241 shows the neighborhood working again.

(FYI: A bunch of activities also fail to start under 2248. Log and Terminal are fine, but Paint and my own Moon activity immediately bomb after launch. Not sure if this is related).

That's very useful. It narrows the problem root somewhere between 2241(works) and 2245 (doesn't work).

The only change according to the logs is:

joyride build 2245 (pkgs)

Size delta: 0.00M

-olpc-utils 0.81-1.olpc3

+olpc-utils 0.82-1.olpc3

there is no record on joyrides 2242-44.

The question now is: would a bug/change in olpc-utils explain that?

comment:8 Changed 6 years ago by marco

  • Component changed from sugar to distro
  • Owner changed from marco to mstone

There is no olpc-utils component, so reassigning to m_stone/distro.

comment:9 Changed 6 years ago by marco

  • Cc mtd added

comment:10 Changed 6 years ago by mtd

I'm running joyride-2240 but with olpc-dm changes that I think were the moral equivalent of the tty-related olpc-dm change in olpc-utils 0.82-1. I'm not sure how changing the tty would cause this symptom, but I'll update to joyride-latest to check.

In the meantime, have you checked ~olpc/.sugar/default/logs/shell.log and /var/log/messages? If you set SUGAR_LOGGER_LEVEL=debug in ~olpc/.xsession (as in http://wiki.laptop.org/go/Attaching_Sugar_Logs_to_Tickets ) you should see very useful information in there.

comment:11 follow-up: Changed 6 years ago by carrano

The narrowing down process was based on inputs from many people. The overall result was that joyride-2241 was ok, while joyride-2245 presented this bug. It might be the case that this is somehow unreliable (other variables ignored). So, if olpc-utils can't possibly be related to that, it seems we have to keep searching in a wider area.

comment:12 in reply to: ↑ 11 Changed 6 years ago by mtd

Replying to carrano:

The narrowing down process was based on inputs from many people. The overall result was that joyride-2241 was ok, while joyride-2245 presented this bug. It might be the case that this is somehow unreliable (other variables ignored). So, if olpc-utils can't possibly be related to that, it seems we have to keep searching in a wider area.

No, I would not say "can't possibly".

If nobody has any logs to hand I should have some in a few hours.

comment:13 Changed 6 years ago by garycmartin

  • Cc garycmartin added

comment:14 Changed 6 years ago by mstone

  • Action Needed changed from never set to diagnose
  • Owner changed from mstone to cscott

comment:15 Changed 6 years ago by garycmartin

Just about to upload shell and messages log – bit of a pain without network ;-) FWIW: I tested a few more activities in 2248 before rebooting back to 2241.

These all instantly fail on launch (leave empty log files): Calculator, Chat, Browse, Record, Maze, Write, Speak, TurteArt, Moon.

These all work: Analyze, Log, Terminal

comment:16 Changed 6 years ago by mstone

Gary - I think you wanted to report those results on a different bug.

Changed 6 years ago by garycmartin

shell.log from joyride-2248

Changed 6 years ago by garycmartin

messages file from joyride-2248

comment:17 Changed 6 years ago by garycmartin

Just to narrow down the search if it helps, I happen to have now also tried joyride-2242 (where neighborhood works as expected), and joyride-2245 (empty neighborhood). So after a look at Berts diff web site script, that just leaves +olpc-utils.i386 0:0.82-1.olpc3 as the rogue ;-)

comment:18 Changed 6 years ago by garycmartin

Ohhhh, also OT note that this is where the Activities also stop launching! So we might have to stop glaring over out keyboards at mstone. Just going to find that ticket...

comment:19 follow-up: Changed 6 years ago by mtd

My "fix" from #5705:

It seems sugar's hardwaremanager.py can't get nmclient.py to get a dbus connection/proxy object to NetworkManager. As you / m_stone suggested, it seems consolekit / pam don't do what dbus's "at_console" policy rule expects (my terminology here is weak, sorry). See https://bugs.freedesktop.org/show_bug.cgi?id=14053 for an example of the fix.

I did this as root and it fixed the problem:

cd /etc/ConsoleKit/run-session.d
wget --no-check-certificate -O pam-foreground-compat.ck https://bugs.freedesktop.org/attachment.cgi?id=17717
init 6

comment:20 in reply to: ↑ 19 Changed 6 years ago by mtd

Replying to mtd:

My "fix" from #5705:

You can use my fix if you're impatient, or looks like cscott's just incorporated a fix in rainbow that's being reviewed.

comment:21 Changed 6 years ago by carrano

Ok, according to:

Andrew Burgess <elist@cichlid.com>

to	Devel@lists.laptop.org
date	Tue, Aug 5, 2008 at 9:48 PM
subject	Re: New joyride build 2255
mailing list	devel.lists.laptop.org Filter messages from this mailing list

	
Joyrides 2253 and 2254 had no networking for me  (no mesh, nothing
but the xo icon in the network view)

Joyride 2255 has networking working again.

Thanks!

And since: olpc-utils was the only change in joyride 2255, than I suggesting closing this as fixed.

comment:22 Changed 6 years ago by garycmartin

  • Action Needed changed from diagnose to qa signoff

Just tested on an XO B4 running joyride-2258. Neighborhood is correctly showing other XO buddy icons from a remote jabber server via an AP (+numerous AP icons and the 3 Mesh channel icons). Looking good if someone official wants to final check/close (I'm not sure of the formal close procedure).

comment:23 Changed 6 years ago by cscott

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.