OLPC XO Opera browser as Sugar activity

Stevens informatics at fastmail.fm
Wed Jun 25 18:49:36 EDT 2008


Hi Bert, all,

I changed the script (OperaActivity.py) posted on the wiki (http:// 
wiki.laptop.org/go/Opera).

This is the old script:

> import logging
> from sugar.activity import activity
>
> import sys, os
> import gtk
>
> class OperaActivity(activity.Activity):
>
>     def __init__(self,handle):
>         activity.Activity.__init__(self,handle)
>
>         self.set_title('Opera Activity')
>
> 	os.system('opera -notrayicon &')


The above script resulted in the 'blank screen' activity. I added a  
personaldir switch, shown below:

import logging
from sugar.activity import activity

import sys, os
import gtk

class OperaActivity(activity.Activity):

     def __init__(self,handle):
         activity.Activity.__init__(self,handle)

         self.set_title('Opera Activity')

	os.system('opera -notrayicon -personaldir $SUGAR_ACTIVITY_ROOT/data &')

(The only change is in the last line: added personaldir command line  
switch.)

This resulted in progress. Now, in addition to the blank screen  
activity, it starts Opera.

However, this may not have been the right thing to do, or I may need  
to make some additional changes as there is still a bug: two glyphs  
show up in the activity circle, one the Opera glyph which when  
clicked on goes to a blank screen, and the other (a gray circle)  
which when clicked on goes to Opera. (Before I made the change to the  
script just the blank screen activity started.)

Is the change I made correct for this case? And, is there some other  
change I should make to eliminate the 'blank screen' being started?

-Peter


On Jun 25, 2008, at 12:55 PM, Bert Freudenberg wrote:

> The activity start script should configure Opera to put its  
> configuration file in $SUGAR_ACTIVITY_ROOT/data instead of  
> $HOME/.opera. Also it should set umask to 0002 so the config file  
> is group-writable (otherwise the next activity instance cannot  
> overwrite).
>
> See http://wiki.laptop.org/go/Low-level_Activity_API#File_Access
>
> - Bert -
>
>
> Am 25.06.2008 um 21:49 schrieb Stevens:
>
>> Some additional information:
>>
>> This is the contents of com.opera.OperaActivity-1.log file
>>
>> groupadd: group 10003 exists
>> Creating mailbox file: File exists
>> ERROR: ld.so: object 'libjvm.so' from LD_PRELOAD cannot be  
>> preloaded: ignored.
>> ERROR: ld.so: object 'libawt.so' from LD_PRELOAD cannot be  
>> preloaded: ignored.
>> QSettings: error creating /home/olpc/isolation/1/uid_to_home_dir/ 
>> 10000/.qt
>> opera: Can not use personal directory: /home/olpc/isolation/1/ 
>> uid_to_home_dir/10000/.opera
>>
>> -Peter
>>
>>>
>>> Hi All,
>>>
>>> I run Opera on the XO, but if started as an activity it doesn't run
>>> (it runs fine when started from terminal). There is a note on the
>>> Opera install page that there is an incompatibility between Rainbow
>>> and Opera:
>>>
>>> "Note: There is at present an incompatibility between the Opera
>>> activity and the OLPC Rainbow security system on some builds. If  
>>> when
>>> you launch the Opera activity, the screen goes blank and stays  
>>> blank,
>>> you have likely encountered that incompatibility."
>>> http://wiki.laptop.org/go/Opera
>>>
>>> That is the symptom I encounter.
>>>
>>> Could one of you tell me what this incompatibility is, and how to
>>> remove it? I'm using build 703, the latest stable build.
>>>
>>>
>>
>> _______________________________________________
>> Devel mailing list
>> Devel at lists.laptop.org
>> http://lists.laptop.org/listinfo/devel
>




More information about the Devel mailing list