<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000000"> I just added this entry to: <a class="moz-txt-link-freetext" href="http://wiki.sugarlabs.org/go/The_Undiscoverable#Activities_are_located_in_2_places">http://wiki.sugarlabs.org/go/The_Undiscoverable#Activities_are_located_in_2_places</a>. There are instances where It is not possible to run browse-119.xo installed in the journal, if Browse-120 has been installed in an update. Is there a better way to force the lower version .xo file to take priority as the application to run? What if the latest upgrade of an activity breaks its working well? Am I correct that removing the installed activity makes this happen? It seems to. Tom Gilliard satellit <blockquote type="cite"> <h4>Activities are located in 2 places</h4> 1-) in /usr/share/sugar/activities <dl> <dd>or </dd> </dl> <pre>* Locations of activities in sugar versions: soas-v2-Blueberry : /home/liveuser/Activities soas-i386-Nightly composes: /usr/share/sugar/activity F12-EDU-spin: /home/{user}/Activities </pre> <dl> <dd> These files are part of the original installed files or updates using the Control Panel/update software <dl> <dd>THESE FILES HAVE PRIORITY BY VERSION NUMBER OVER .xo files in the Journal, and cannot normally be erased. </dd> </dl> </dd> </dl> 2-) In the sugar-journal as .xo files <dl> <dd>a downloaded through sugar-browse from ASLO (Activities) </dd> <dd>b Drag-dropped into the sugar journal from a 2nd USB or CD <dl> <dd>these files can be erased (uninstalled) by => from journal enrty then (-) at top </dd> </dl> </dd> </dl> <ul> <li>ie: It is not possible to run browse-119.xo installed in the journal, if Browse-120 has been installed in an update. </li> </ul> <dl> <dd>The entry for the Activity in /usr/share/sugar/activity must be erased in root terminal before the (lower version .xo) file will run </dd> </dl> </blockquote> </body> </html>