Re: Restarting a half-started activity

2007-12-10 Thread Alexander M. Latham
--- Asheesh Laroia wrote:
As I debug how to start my activity with an LD_LIBRARY_PATH (or for other 
reasons), sometimes it fails to start correctly at all.  In those cases, 
my activity's icon just sits in the ring that shows running activities. 
When I move the mouse over it, Sugar tells me it is Starting..., but 
when I look for its process in the 'ps aux' output, the process has 
already terminated.

How can I remove the activity from the Sugar thinks it's starting state 
so I can reattempt to start the activity without rebooting the laptop?

(Thanks all; you've been super helpful so far.  If my questions start 
running into FAQ territory I'm perfectly okay with being told to read some 
document.)

-- Asheesh.
--- end of quote ---

On later builds (I'm not sure exactly which build) there is a timeout on 
activities that are taking a long time to load, usually because of an error. 
The other option is to just restart X. You can do this by pressing 
ctrl+alt+backspace

- AlexL
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: .xo archive?

2007-12-05 Thread Alexander M. Latham
--- Ed Montgomery wrote:
Can anyone suggest a link for a 'master' .xo package
list/wiki/directory/whatever?
--- end of quote ---

there are a few pages to look at:

http://wiki.laptop.org/go/Activities (this is where most activites should be 
listed in the future)

http://olpc.download.redhat.com/activities/joyride/ (all the activites in 
joyride)

http://wiki.laptop.org/go/GCompris (GCompris activities may not work on builds 
after 623; there is a track bug about this)

- AlexL
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: boot failed after updating MP to joyride-357 (activation?)

2007-12-04 Thread Alexander M. Latham
--- Tomeu Vizoso wrote:
Hi,

After rebooting, a sad face appeared, 'BOOT FAILED' was written at the
top left and under the laptop icon was a lock.

Booting the alternate image (pressing the 'O' button while powering on)
worked fine.

What did I wrong?

Thanks,

Tomeu
--- end of quote ---

I'm guessing you were updateing from either 623 or 649, and that while your 
laptop has been activated, it is still secure. Secure laptops (having the write 
protect set) will only boot into signed images (i.e. the likely signed version 
of 623 or 649 that you had) None of the joyride builds are signed. If you want 
to run them, you need to turn security off on your laptop. To do this, Apply 
for a Developer Key. If you open the browser on 649, click on 'other' and then 
'about your xo' At the very bottom of the page, there is a link to getting a 
developer key. Follow the instructions, and you should get a developer key in a 
day or two, depending on when cscott makes them. This will enable you to get to 
the ok prompt in open firmware, which means you can boot into any image you 
want.

- AlexL
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Signed 648 (ship.2 release candidate)

2007-11-30 Thread Alexander M. Latham
--- Yoshiki Ohshima wrote:
  Great!  but sorry for my ignorance but what a signed copy means?
Shall we test it on our (B4) laptops?  Or it'll make it hard for
future update? 

http://xs-dev.laptop.org/~cscott/olpc/streams/ship.2/build648/devel_jffs2/

is the same thing but unsigned?

-- Yoshiki
--- end of quote ---

Signed means that it will work on a write protected machine. If you're laptop 
is not write protected, the unsigned version will work exactly the same.

- AlexL
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: clean installation of 643.

2007-11-28 Thread Alexander M. Latham
--- Yoshiki Ohshima wrote:
I tried to do clean install of 643 and it failed.  Actually, it worked
for the first time.  Then, I realized that I forgot to put Q2D05
firmware on my USB memory.  So I put the .rom file and tried the clean
installation again.  Then during the boot process I got:

--
 Restoring from backup 
tar: Short read
Traceback (most recent call last):
  File /init, line 110, in module
backup_or_restore()
  File /init, line 87, in backup_or_restore
do_restore()
  File /init, line 77, in do_restore
safe_sh(tar -xz -f  + backup_file +  -C /restore)
  File /initutil.py, line 26, in safe_sh
raise RuntimeError(Command exited with non-zero exit status.)
--

-- Yoshiki
--- end of quote ---

In the future, if you're only updating the ofw, you should just get to the ok 
prompt and type:  ok flash path_to_file

Also, after the firmware is upgraded, it reboots the machine, which would then 
lead the machine into trying to do an upgrade instead of a clean install if you 
don't hold the square key. That is probably why it created a backup and tried 
to restore from it. This means there may be some issues with the 
auto-reinstallation process, which should be looked into.

- AlexL
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: OLPC XEyes

2007-11-26 Thread Alexander M. Latham
--- Don Hopkins wrote:
PLEASE PLEASE PLEASE, somebody sugarize XEyes!
It's the cutest X application that runs on the OLPC without any 
modification.
We just need a way to launch it from the frame!

http://www.donhopkins.com/drupal/gallery2/v/Devon/IMG_0135.JPG.html

Now you can see why my OLPC has tooth marks in the handle:

http://www.donhopkins.com/drupal/gallery2/v/Devon/IMG_0144.JPG.html

-Don
--- end of quote ---

Do you have a link to the code for XEyes?

- AlexL
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Wireless troubles, part 2: WEP 64/128 bit enabled

2007-11-12 Thread Alexander M. Latham
I opened a blocking bug on this. 

http://dev.laptop.org/ticket/4826

Please add any notes and/or logs.

Thanks,
AlexL

--- Pascal Scheffers wrote:
Same AP, I rebooted the XO to be sure it was a clean attempt (the AP  
is called 'xo' in this log file, same errors with any other name):

Now with WEP enabled, either 64 or 128 bit with simple keys like  
1234567890123... etc:

Nov 12 18:08:59 localhost NetworkManager: info  Activation (eth0/ 
wireless): access point 'xo' is encrypted, but NO valid key exists.   
New key needed.
Nov 12 18:08:59 localhost NetworkManager: info  Activation (eth0)  
New wireless user key requested for network 'xo'.
Nov 12 18:08:59 localhost NetworkManager: info  Activation (eth0)  
Stage 2 of 5 (Device Configure) complete.
Nov 12 18:08:59 localhost NetworkManager: WARN   
nm_dbus_get_user_key_for_network_cb():  
nm_dbus_get_user_key_for_network_cb(): dbus returned an error.
(org.freedesktop.DBus.Python.RuntimeError) Traceback (most recent call  
last):   File /usr/lib/python2.5/site-packages/dbus/service.py, line  
692, in _message_cb retval = candidate_method(self, *args,  
**keywords)   File /usr/share/sugar/shell/hardware/nminfo.py, line  
368, in getKeyForNetwork attempt, new_key, async_cb,  
async_err_cb)   File /usr/share/sugar/shell/hardware/nminfo.py, line  
487, in get_key_for_network self._key_dialog =  
keydialog.new_key_dialog(net, async_cb, async_err_cb)   File /usr/ 
share/sugar/shell/hardware/keydialog.py, line 325, in  
new_key_dialog raise RuntimeError(Unhandled network capabilities  
%x % caps) RuntimeError: Unhandled network capabilities 1
Nov 12 18:08:59 localhost NetworkManager: info  Activation (eth0)  
failure scheduled...
Nov 12 18:08:59 localhost NetworkManager: WARN   
nm_dbus_get_user_key_for_network_cb():  
nm_dbus_get_user_key_for_network_cb(): dbus returned an error.
(org.freedesktop.DBus.Python.RuntimeError) Traceback (most recent call  
last):   File /usr/lib/python2.5/site-packages/dbus/service.py, line  
692, in _message_cb retval = candidate_method(self, *args,  
**keywords)   File /usr/share/sugar/shell/hardware/nminfo.py, line  
368, in getKeyForNetwork attempt, new_key, async_cb,  
async_err_cb)   File /usr/share/sugar/shell/hardware/nminfo.py, line  
487, in get_key_for_network self._key_dialog =  
keydialog.new_key_dialog(net, async_cb, async_err_cb)   File /usr/ 
share/sugar/shell/hardware/keydialog.py, line 325, in  
new_key_dialog raise RuntimeError(Unhandled network capabilities  
%x % caps) RuntimeError: Unhandled network capabilities 1
Nov 12 18:08:59 localhost NetworkManager: info  Activation (eth0)  
failure scheduled...
Nov 12 18:08:59 localhost NetworkManager: WARN   
nm_dbus_get_user_key_for_network_cb():  
nm_dbus_get_user_key_for_network_cb(): dbus returned an error.
(org.freedesktop.DBus.Python.RuntimeError) Traceback (most recent call  
last):   File /usr/lib/python2.5/site-packages/dbus/service.py, line  
692, in _message_cb retval = candidate_method(self, *args,  
**keywords)   File /usr/share/sugar/shell/hardware/nminfo.py, line  
368, in getKeyForNetwork attempt, new_key, async_cb,  
async_err_cb)   File /usr/share/sugar/shell/hardware/nminfo.py, line  
487, in get_key_for_network self._key_dialog =  
keydialog.new_key_dialog(net, async_cb, async_err_cb)   File /usr/ 
share/sugar/shell/hardware/keydialog.py, line 325, in  
new_key_dialog raise RuntimeError(Unhandled network capabilities  
%x % caps) RuntimeError: Unhandled network capabilities 1
Nov 12 18:08:59 localhost NetworkManager: info  Activation (eth0)  
failure scheduled...
Nov 12 18:08:59 localhost NetworkManager: info  Activation (eth0)  
failed for access point (xo)
Nov 12 18:08:59 localhost NetworkManager: info  Activation (eth0)  
failed.
Nov 12 18:08:59 localhost NetworkManager: info  Deactivating device  
eth0.
Nov 12 18:08:59 localhost NetworkManager: info  Activation (eth0)  
failed for access point (xo)
Nov 12 18:08:59 localhost NetworkManager: info  Activation (eth0)  
failed.
Nov 12 18:08:59 localhost NetworkManager: info  Deactivating device  
eth0.
Nov 12 18:08:59 localhost NetworkManager: info  Activation (eth0)  
failed for access point (xo)
Nov 12 18:08:59 localhost NetworkManager: info  Activation (eth0)  
failed.
Nov 12 18:08:59 localhost NetworkManager: info  Deactivating device  
eth0.
Nov 12 18:08:59 localhost NetworkManager: info  SWITCH: no current  
connection, found better connection 'msh0'.
--- end of quote ---

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Shutting down fds prior to execvpe in rainbow/inject.py: joyride 247 under Qemu

2007-11-07 Thread Alexander M. Latham
--- Michael Stone wrote:

   Logviewer hangs just like Clock.  So does MaMa Media Creative Center,
 and Record.Hmmm.

Record has been crashing on startup for a long time (a week?) because
it's trying to mkdir() a directory that already exists.

MaMa Media Creative Center had a similar problem, though some of the
other MaMaMedia activities started fine (e.g. Joke Machine).

I'm not yet sure what's up with LogViewer.

Thanks for the comprehensive report!

Michael
--- end of quote ---

Actually, Record was loading fine in Joyride 243. I just loaded joyride 251. 
Record did not open at first, but after removing the security file, Record, 
Clock, and Log Viewer all loaded fine. MaMa Media Creative Center is still 
broken, but it wasn't working in past builds anyways.

I'll write up bugs as soon as trac is back up.

- AlexL
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [sugar] Monday Ship Mtg update message

2007-10-26 Thread Alexander M. Latham
--- Marco Pesenti Gritti wrote:
  For individual activities we will always want people to be able to
  download from a website pretty much at any time, so further
  development and features to activities, should continue to be
  planned and released outside of the olpc schedule.

 So you mean a downloaded activity in ~/Activities should take
 precedence over the default one in /usr/share/activities? Has this
 been tested?

I don't think that works currently. A ticket would be good, I think
it's something we really need to fix for 1.0.

Marco
--- end of quote ---

I believe ticket number 4038 applies to this.

Basically, updating activities doesn't work right now, and how it should be 
handled needs to be decided upon.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [sugar] Auto loading of a usb key

2007-10-09 Thread Alexander M. Latham
--- ankita prasad wrote:
Hi,

Would the sugar environment automatically mount the a usb key eventually or
would we have to manually mount it?

-Ankita
--- end of quote ---

This already occurs. When a USB stick is plugged into the XO, it is mounted and 
shows up in the journal. You are also able to unmout the USB stick from the 
journal.

- AlexL
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel