On Tue, Dec 07, 2010 at 06:34:05PM +1100, David Leeming wrote: > James wrote: > > David wrote: > > > James wrote: > > > > G'day David, > > > > XO-1 software release 10.1.2 is based on Sugar 0.84, which moved > > > > to using gconf for storing this setting. What should work is: > > > > 1. start Terminal activity, > > > > 2. type > > > > sugar-control-panel -c registration > > > > 3. use ctrl-alt-erase to restart Sugar. > > > > If that doesn't work, please let me know, as I'd like to track > > > > it. > > > > > > Sorry it has taken me a while to get round to testing this. Well > > > it does not work. In terminal, the command above gives a lot of > > > text feedback, referring to a configuration server. > > > > Good, please provide the text feedback, it is critical for > > understanding the problem. You can capture that with a screenshot, > > Alt/1, or use the Linux script command. > > sugar-control-panel: Failed to contact configuration server; some > possible causes are that you need to enable TCP/IP networking for > ORBit, or you have stale NFS locks due to a system crash. See > http://projects.gnome.org/gconf/ for information. (Details - 1: > Failed to get connection to session: 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.)
> This happens for me on 10.1.2 only if I try it at a virtual terminal > console (ctrl-alt-f1), but it doesn't happen for me if I do it in the > Terminal activity. I checked that I mentioned using the Terminal > activity. Please confirm this is where you typed it? Certain > environment variables are needed from the running Sugar session, and > these are available by default to Terminal. > Please confirm the OLPC OS build number, and the version number of the > Sugar RPM package: Terminal Activity was used, yes, version 31 # cat /boot/olpc_build 852 # rpm -q sugar sugar-0.84.22-1.fc11.i586 All above are results from the same XO David > > Did either of these alternate methods work? > > - gconftool method gave same output as the first (as above) > That also happens in a shell that is missing the required context. > - rm -rf .gconf gave no errors but after reboot there is no "Register" > option present in the home view shutdown menu, only Shutdown and My > Settings. So I guess no. > Interesting, thanks. -- James Cameron http://quozl.linux.org.au/ _______________________________________________ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel