[Sugar-devel] Sugar frozen when trying to register.. bug in idmgr?
Hi, Has anybody experienced Sugar (0.82) freezing when trying to register against the server? I was unable to register (although connectivity seemed fine) and when sniffing the network I saw: 172.18.0.1.8080 > 172.18.96.196.47780: S 172.18.0.1.8080 > 172.18.96.196.47780: S 172.18.0.1.8080 > 172.18.96.196.47780: S 172.18.0.1.8080 > 172.18.96.196.47780: S I thought idmgr might be hanged.. So I did: service idmgr restart and everything started working again.. Anyone bumped into something similar recently? Regards, Raúl ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Screen Displays (text)
On Fri, 2009-08-14 at 17:28 -0400, Walter Bender wrote:
> I determine whether or not I am on an XO with:
>
> if os.path.exists('/sys/power/olpc-pm'): # then assume you are on an XO
>
Shouldn't we encapsulate this method (is_xo?()) somewhere? I've seen it
spread in a couple of places so far..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar frozen when trying to register.. bug in idmgr?
On Fri, 2009-08-14 at 10:23 +0200, Tomeu Vizoso wrote: > On Thu, Aug 13, 2009 at 19:22, Raul Gutierrez Segales > wrote: > > Hi, > > > > Has anybody experienced Sugar (0.82) freezing when trying to register > > against the server? I was unable to register (although connectivity > > seemed fine) and when sniffing the network I saw: > > > > 172.18.0.1.8080 > 172.18.96.196.47780: S > > 172.18.0.1.8080 > 172.18.96.196.47780: S > > 172.18.0.1.8080 > 172.18.96.196.47780: S > > 172.18.0.1.8080 > 172.18.96.196.47780: S > > > > I thought idmgr might be hanged.. So I did: > > > > service idmgr restart > > > > and everything started working again.. Anyone bumped into something > > similar recently? > > Never saw that, but this should be async so the UI doesn't freezes. > Could you please enter a ticket about it in http://dev.sugarlabs.org? > http://dev.sugarlabs.org/ticket/1181 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] GPA ain't the world (was: [Sugar-news] Sugar Digest 2009-08-11)
On Thu, 2009-08-13 at 15:06 -0400, Walter Bender wrote: > On Thu, Aug 13, 2009 at 2:17 PM, David Van Assche wrote: > [snip] > > Or are you saying the feedback is getting through and I'm just not seeing > > it? > > We all seem to agree that feedback is important. > > We mostly agree that there is value in feedback from all deployments, > big and small. > > We are currently getting valuable feedback from the field: Sur, the > Ceibal blogs, reports from Nepal, Greg's reports from GPA, et al. > > We need more feedback and therefore we are exploring additional means > of getting it. You ideas are welcome! > Perhaps a section in Sugar Digest with links to highlights of what went on in deployments during the week? Wearing a deployer-hat I must confess that we could (Paraguayan Deployment Team) do a better job filing tickets, giving feedback, etc. Will try to keep discipline from now on :-) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] feedback from a teacher in Uruguay
On Fri, 2009-08-14 at 15:31 +0530, Manusheel Gupta wrote: > Gabriel, please ask the teacher to download the latest SocialCalc > activity package from here . Could we move/copy this to a.sl.o? Makes life easier for deployment teams to then grab activities and make them available at local servers.. Thanks! P.S.: i am assuming it's not available (yet) at a.sl.o because of the link you provided.. i couldn't check myself since a.sl.o is down at the moment. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar-devel Digest, Vol 11, Issue 94
On Thu, 2009-09-17 at 23:30 +0545, Daniel Drake wrote: > 2009/9/17 David Farning : > > One step in that direction might be to clearly communicate and try to > > gather momentum around a series of stable releases. > > > > One thought that might work is to set .84, .88, .94, and 1.0 as stable > > releases for down streams to unite around. > > That would be useful but actually the critical area lacking resources > right now is people working on OS building and deployment > technologies. If I can tame your interest in getting new Sugar on XO > in a deployment-quality release, finding resources to work on these > resources would be the biggest help you could provide. > +1 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Turtle Art-70 on SoaS3-200909271154.iso
On Sun, 2009-09-27 at 18:50 +0200, s.bouta...@free.fr wrote: > Hi all, > > In Turtle Art-70 running on the SoaS3-200909271154.iso, the help messages > don't > display well when there is a 2nd line for longer strings. You mean the line wrapping only works to a certain extend? Could you send me a screenshot of this off-list? > > Another issue is the incomplete localization in this configuration: some > strings > (especially in the left panel in TA) remain in EN, even after selecting > another > locale (e.g. FR) from the configuration panel. I didn't notice this issue with > sugar-jhbuild (0.84.7). I wonder if it's missing translations or missing mappings in our dict. I'll try to to find out once I finish downloading SoAS. Raúl ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] my plans for 0.88
On Tue, 2009-10-06 at 18:48 +0100, Tomeu Vizoso wrote: > I will be proposing a Google Spreadsheet form in the next few days > that deployments will fill if they choose to. I think we'll need to > have one for OLPC deployments and another for the other deployments > because in some cases those filling up the form won't be able to > easily differentiate between hardware and software issues. > Great initiative! I am looking forward to share our deployment's info! Raúl ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] CMDA/GSM/3G Modem Support in Sugar
On Fri, 2009-11-27 at 10:48 -0200, Daniel Castelo wrote: > The fields that user should configure are: Tel Number, User Name and > Password (which more?) Perhaps APN. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] adding 3G devices support to sugar
On Thu, 2009-12-03 at 14:25 -0500, Eben Eliason wrote: > On Thu, Dec 3, 2009 at 1:44 PM, Martin Abente > wrote: > > Today i finished the systray device icon. (but i still need the icon > > graphic... any artist around?) > > I'd be happy to sketch some icons. Do you have any suggestions or > examples of what an appropriate icon might be for a 3G modem? > > As far as I know, they come in all shapes and sizes—including, of > course, cell phones—and I'm not sure there is an accepted or easily > recognizable form for an icon. Some cultural background: Here in Paraguay people call 3G modems "a soap" (jabón) since almost all of them are small and it has a sopa-like shape. You hear it all the time "can you lend me your soap".. Perhaps a little soap might be meaningful for other deployments? Maybe not :) Raúl P.S.: IIRC a telco here started a marketing campaign in which they coined that phrase (3G modem == soap). ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Keep confusion, again
On Fri, 2010-01-15 at 14:40 -0600, Daniel Drake wrote: > I'm back in the field and I'm again seeing the same confusion about Keep: > http://lists.sugarlabs.org/archive/sugar-devel/2009-July/016375.html > > The computer-literate people who produce training materials > misinterpret "Keep" as "Save" (i.e. if you don't click it your work is > lost) and pass on this misinformation to trainers, teachers and > children. > > I do have something to add now though; I've noticed that Keep is > translated into Spanish as "Guardar" > > In "regular software" unlike Sugar where saving is actually necessary, > the same term is used: Guardar > > At least in English we have a separate word (Keep instead of Save) > which hopefully introduces the idea that it's not the same as regular > Save - but in Sugar's Spainsh translation this is not the case, almost > certainly adding to the confusion. > "Guardar copia" is long but maybe it transmits the message of "you are saving a new snapshot" instead of "you just saved". ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [PATCH] _update_signal_match wasn't initialized
Because of missing initialization and a weak test for the existence of
the object (self._update_signal_match is not None) Turtle Art was
crashing when resuming from the Journal.
Signed-off-by: Raúl Gutiérrez S.
Ackd-by: Bernie Innocenti
---
src/sugar/datastore/datastore.py |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/src/sugar/datastore/datastore.py b/src/sugar/datastore/datastore.py
index 6ff10de..e711f02 100644
--- a/src/sugar/datastore/datastore.py
+++ b/src/sugar/datastore/datastore.py
@@ -57,6 +57,7 @@ class DSMetadata(gobject.GObject):
}
def __init__(self, props=None):
+self._update_signal_match = None
gobject.GObject.__init__(self)
if not props:
self._props = {}
--
1.6.3.3
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] _update_signal_match wasn't initialized
Forgot to mention that this is for 0.84 branch, 0.88 does it right.
On Mon, 2010-04-26 at 15:50 -0400, Raul Gutierrez Segales wrote:
> Because of missing initialization and a weak test for the existence of
> the object (self._update_signal_match is not None) Turtle Art was
> crashing when resuming from the Journal.
>
> Signed-off-by: Raúl Gutiérrez S.
> Ackd-by: Bernie Innocenti
> ---
> src/sugar/datastore/datastore.py |1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/src/sugar/datastore/datastore.py
> b/src/sugar/datastore/datastore.py
> index 6ff10de..e711f02 100644
> --- a/src/sugar/datastore/datastore.py
> +++ b/src/sugar/datastore/datastore.py
> @@ -57,6 +57,7 @@ class DSMetadata(gobject.GObject):
> }
>
> def __init__(self, props=None):
> +self._update_signal_match = None
> gobject.GObject.__init__(self)
> if not props:
> self._props = {}
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] _update_signal_match wasn't initialized
James, On Tue, 2010-04-27 at 11:25 +1000, James Cameron wrote: > On Mon, Apr 26, 2010 at 03:50:17PM -0400, Raul Gutierrez Segales wrote: > > Because of missing initialization and a weak test for the existence of > > the object (self._update_signal_match is not None) Turtle Art was > > crashing when resuming from the Journal. > > Reviewed, but I didn't understand. This might be my fault. > > Your patch appears to be to sugar-toolkit. > Correct. > self._update_signal_match is only used in DSObject, it is already > initialised in sugar-toolkit 0.84.9, and you're adding the > initialisation to DSMetadata, where it is not used. > Sorry, this was done on the run.. Because we were spinning new builds. Looking at it with more detail, the problem is that self._update_signal_match is initialized in the wrong order (after a call to set_object_id that depends on it). diff --git a/src/sugar/datastore/datastore.py b/src/sugar/datastore/datastore.py index 6ff10de..7aa4d15 100644 --- a/src/sugar/datastore/datastore.py +++ b/src/sugar/datastore/datastore.py @@ -109,12 +109,12 @@ class DSMetadata(gobject.GObject): class DSObject(object): def __init__(self, object_id, metadata=None, file_path=None): +self._update_signal_match = None self.set_object_id(object_id) self._metadata = metadata self._file_path = file_path self._destroyed = False self._owns_file = False -self._update_signal_match = None def get_object_id(self): return self._object_id ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] _update_signal_match wasn't initialized
On Wed, 2010-04-28 at 09:56 +1000, James Cameron wrote: > On Tue, Apr 27, 2010 at 09:43:21AM -0400, Raul Gutierrez Segales wrote: > > Looking at it with more detail, the problem is that > > self._update_signal_match is initialized in the wrong order (after a > > call to set_object_id that depends on it). > > No worries, now I understand, and approve. > > Reviewed-by: James Cameron > Great, what is the next step for inclusion? (I have no commit access to sugar-toolkit). Raúl ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fwd: [Activities] New activity: Retroscope
This activity crashed my XO.. I am trying to reproduce. On Fri, 2008-12-12 at 17:40 +0200, Morgan Collett wrote: > Forwarding to sugar-devel... > > Gabriel, the activities list isn't really used - sugar-devel is a > better place to announce :) > > Regards > Morgan > > -- Forwarded message -- > From: Gabriel Burt > Date: Thu, Dec 4, 2008 at 10:04 > Subject: [Activities] New activity: Retroscope > To: activit...@lists.laptop.org > > > Hi, > > I've created a new activity called Retroscope. It's really simple - > it shows you live video, but delayed 0 to 10 seconds. I've attached > it (all 4.8K) and would love to hear feedback. > > Thanks, > > Gabriel > > ___ > Activities mailing list > activit...@lists.laptop.org > http://lists.laptop.org/listinfo/activities > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Sugar on the press (Paraguay)
http://www.lanacion.com.py/noticias-253839.htm ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ANNOUNCE: Sugar 0.88 for the XO-1
On Tue, 2010-05-25 at 12:25 -0400, Bernie Innocenti wrote: > Hello everyone, > > we've just started a new development cycle aimed at providing Sugar 0.88 > for the XO-1. Our focus is stability and usability for deployments, > although we're also attempting to merge a couple of low-risk features > developed in Uruguay. > > Full details are here: > > http://wiki.sugarlabs.org/go/Deployment_Team/Sugar-0.88_Notes > > The current image, os140py, is an alpha quality build with a few known > regressions. > s/os140py/os240py/ Raúl ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] #1686 UNSP: Accessibility - virtual keyboard
First of all, thanks Esteban for the great work! I hope we can spin a new build soon and give it a try. On the other hand, even though I also come from a Spanish speaking country, I'd say having all the code in English (the defacto lingua franca for code) would be best on the long term. It's an extra effort (and I volunteer to help with translations if Esteban is short on time) but I think it is important to maintain consistency in variable names, methods and comments. Cheers, Raúl P.S.: we try to produce all of our code (in git.paraguayeduca.org) under the same rules (all English) so we can share it among deployments.. we hope it results useful for someone some day! :) On Wed, 2010-05-26 at 10:57 -0400, Michael Stone wrote: > Tomeu, Bert, James, Martin D., and Michael wrote: > > >> T: Thanks a lot for lending a hand here. > > My pleasure, and thanks for mentioning the ticket. > > >>> M: Final remark: this patch names variables, methods, and classes in > >>> Spanish. Anyone troubled by this? > >>> > >>> (I ask because, while it's fine with me personally, I don't think I know > >>> consensus opinion on the subject.) > >> > >> T: I'm not so happy about it, I think it raises considerably the effort > >> needed to read the code, even for spanish speakers like me. > > > > B,J,MD: IMHO the whole code base should be in English. This is the language > > we use for collaborating. > > You and I certainly collaborate in English but the folks dealing with Sugar on > a daily basis in Uruguay, Peru, and Paraguay largely do not, at least in their > daily dealings among themselves. > > For this sole strategic reason, I think we need to consider accepting > well-written patches that come to us in Spanish or in English. > > The main cost of pursuing this course is that patches written in Spanish are > somewhat harder for some prominent Sugar contributors to read than are patches > written in English. Additionally, having a mixed-language codebase may be > off-putting to some potential contributors. > > On the other hand, does it not seem likely that by welcoming patches written > in > the first and most common language of our largest groups of users, we would > receive more patches, thereby gaining more contributors, some of whom might > grow to become integral members of our community? > > (Finally, if we don't receive many patches, then what will be the loss for > having tried? At most, we will have a small number of patches to translate > from > Spanish to English. Not a big deal, right?) > > Regards, > > Michael > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] behaviour of F-keys on XO HS
On Mon, 2010-07-19 at 21:33 -0400, Walter Bender wrote:
> On Mon, Jul 19, 2010 at 9:27 PM, Gonzalo Odiard wrote:
> > Yeah
> > How we detect what keyboard is present?
>
> You can possible to detect the XO 1, which guarantees a membrane
> keyboard. And a non-OLPC machine, which guarantees a non-membrane
> keyboard. It is the XO 1.5 that is at issue. I'll look into it.
http://wiki.laptop.org/go/OLPC_Firmware_q3a44 mentions:
1889: OLPC keyboard driver, avoid confusing EC with enable scan command
I wonder if somehow the type of detected keyboard is discoverable
via /ofw.
Cheers,
Raúl
>
> -walter
>
> def _get_hardware():
> """ Determine whether we are using XO 1.0, 1.5, or "unknown" hardware """
> bus = dbus.SystemBus()
>
> comp_obj = bus.get_object('org.freedesktop.Hal',
> '/org/freedesktop/Hal/devices/computer')
> dev = dbus.Interface(comp_obj, 'org.freedesktop.Hal.Device')
> if dev.PropertyExists('system.hardware.vendor') and \
> dev.PropertyExists('system.hardware.version'):
> if dev.GetProperty('system.hardware.vendor') == 'OLPC':
> if dev.GetProperty('system.hardware.version') == '1.5':
> return XO15
> else:
> return XO1
> else:
> return UNKNOWN
> elif path.exists('/etc/olpc-release') or \
> path.exists('/sys/power/olpc-pm'):
> return XO1
> else:
> return UNKNOWN
>
> > Gonzalo
> >
> > On Mon, Jul 19, 2010 at 9:26 PM, Walter Bender
> > wrote:
> >>
> >> On Mon, Jul 19, 2010 at 5:20 PM, Paul Fox wrote:
> >> > i'd like to bring this discussion to a conclusion.
> >> >
> >> > i'm starting to be a fan of this proposal of bert's -- it's very
> >> > simple, keeps the keys the same in sugar and in gnome, and on
> >> > membrane and non-membrane keyboards, it's backwards compatible
> >> > with existing use on XO-1, and the volume/ brightness keys remain
> >> > easily discoverable. it does require that sugar respond to F5
> >> > and F6 for "journal" and "frame" -- i still don't have a feeling
> >> > for whether that's an issue or not, and if so, how big.
> >>
> >> The only activity I am aware of that uses F5 and F6 on the XO is the
> >> most recent version of Paint that Gonzolo is working on. Presumably
> >> these keymaps could be grabbed by Paint when running on an OLPC XO 1.0
> >> or when we detect the membrane keyboard. Otherwise, we could keep the
> >> mapping as Bert suggests.
> >>
> >> > any yeas or nays?
> >>
> >> Yeah.
> >> >
> >> > paul
> >> >
> >> >
> >> > bert wrote:
> >> > >
> >> > > On 17.07.2010, at 09:31, Bernie Innocenti wrote:
> >> > >
> >> > > > El Thu, 15-07-2010 a las 23:08 -0400, Paul Fox escribió:
> >> > > >> i think everyone (except
> >> > > >> apple, i'm learning tonight) agrees this is the correct setup
> >> > > >> when not in sugar.
> >> > > >
> >> > > > Lenovo also seems to be switching to the Apple layout:
> >> > > >
> >> > > >
> >> > http://www.blogcdn.com/www.engadget.com/media/2010/01/thinkpadedgepost16.jpg
> >> > > >
> >> > >
> >> > http://www.thinkpads.com/wp-content/gallery/lenovo-thinkpad-edge-13-review/lenov
> >> > > o-thinkpad-edge-13-keyboard.jpg
> >> > > >
> >> > > > Almost all the historic F-key mappings have an alternative CTRL+key
> >> > or
> >> > > > ALT+key mapping in modern HIGs. Keys to control laptop volume and
> >> > > > brightness are accessed much more frequently, so it's foreseeable
> >> > that
> >> > > > over time they will supplant the F-keys in PC keyboards.
> >> > >
> >> > > +1
> >> > >
> >> > > IMHO pressing "fn" to get "f1" to "f10" makes sense. In my daily
> >> > routine I much
> >> > > more often change volume or brightness than use the numbered F keys.
> >> > >
> >> > > Looking at this again
> >> > >
> >> > > http://wiki.laptop.org/go/OLPC_Spanish_Non-membrane_Keyboard
> >> > >
> >> > > I propose:
> >> > >
> >> > > f1-f8 produce F key codes both with and without the fn key
> >> > > f9-f12 produce F codes only with fn, and volume/brightness
> >> > events
> >> > > without fn.
> >> > >
> >> > > So holding down fn always gets you the F key codes, you can change
> >> > > volume/brightness without modifier, and as a bonus you can use the
> >> > first eight
> >> > > F keys even without the fn key.
> >> > >
> >> > > This mapping should work both in Sugar and outside.
> >> > >
> >> > > - Bert -
> >> > >
> >> > >
> >> > > ___
> >> > > Devel mailing list
> >> > > de...@lists.laptop.org
> >> > > http://lists.laptop.org/listinfo/devel
> >> >
> >> > =-
> >> > paul fox, p...@laptop.org
> >> >
> >> > ___
> >> > Sugar-devel mailing list
> >> > Sugar-devel@lists.sugarlabs.org
> >> > http://lists.sugarlabs.org/listinfo/sugar-devel
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> Walter Bender
> >> Sugar Labs
> >> http://www
[Sugar-devel] [PATCH] VncLauncher can't find the needed libs on OLPC's 10.1.2 release
Hi,
The deployment here in Nigeria is updating their laptops to the 10.1.2
release. In the process, we found out the VncLauncher (v6) is not
working because the bundled binary (x11vnc) needs a few libs. Even
though one of the libs is included, the code doesn't export the library
path before running the binary.
The attached patch exports the path that contains the needed
(lib/{libvncserver.so,libvncclient.so}).
If the activity currently lacks maintainer I can prepare a new release
(if someone can give me the right access) that includes this patch and
the needed library.
This activity is kind of popular in this deployment.
Cheers,
Raul
--- VncLauncher.activity/vnclauncher.py 2009-01-07 03:36:36.0 -0300
+++ VncLauncher.activity-modified/vnclauncher.py 2010-09-09 18:14:46.0 -0400
@@ -108,7 +108,14 @@
def connectVNC(self,button):
self._vte.grab_focus()
- cmd = "/home/olpc/Activities/VncLauncher.activity/x11vnc"
+src_dir = os.path.dirname(__file__)
+lib_dir = os.path.join(src_dir, "lib")
+cmd = os.path.join(src_dir, "x11vnc")
+ld_library_path = os.getenv("LD_LIBRARY_PATH")
+if ld_library_path is None:
+os.putenv("LD_LIBRARY_PATH", lib_dir)
+else:
+os.putenv("LD_LIBRARY_PATH", lib_dir + ":" + ld_library_path)
self._vte.fork_command(cmd)
def __key_press_cb(self, window, event):
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] VncLauncher can't find the needed libs on OLPC's 10.1.2 release
Here is a working (temporary) release:
http://people.sugarlabs.org/~rgs/activities/vnclauncher-7.xo
Note: I think this problem only affects 10.1.2. Dextrose users shouldn't
be affected because the libvncserver package is included on those
builds.
On Fri, 2010-09-10 at 04:00 -0400, Raul Gutierrez Segales wrote:
> Hi,
>
> The deployment here in Nigeria is updating their laptops to the 10.1.2
> release. In the process, we found out the VncLauncher (v6) is not
> working because the bundled binary (x11vnc) needs a few libs. Even
> though one of the libs is included, the code doesn't export the library
> path before running the binary.
>
> The attached patch exports the path that contains the needed
> (lib/{libvncserver.so,libvncclient.so}).
>
> If the activity currently lacks maintainer I can prepare a new release
> (if someone can give me the right access) that includes this patch and
> the needed library.
>
> This activity is kind of popular in this deployment.
>
> Cheers,
> Raul
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] VncLauncher can't find the needed libs on OLPC's 10.1.2 release
On Mon, 2010-09-13 at 17:25 +1000, James Cameron wrote: > On Fri, Sep 10, 2010 at 04:31:30AM -0400, Raul Gutierrez Segales wrote: > > Here is a working (temporary) release: > > > > http://people.sugarlabs.org/~rgs/activities/vnclauncher-7.xo > > > > Note: I think this problem only affects 10.1.2. Dextrose users shouldn't > > be affected because the libvncserver package is included on those > > builds. > > Should we add libvncserver to the 10.1.3 build? It seems to install > fine using yum. The libvncserver.so.0 after install has the same md5sum > as the one in vnclauncher-7.xo. > That is one way out of the problem. I think the long standing meta-question is how do Activity developers handle external libs. If we go and add libvncserver than you we'll set a precedent. The next time someone comes in with a new dependency requirement, will we be spinning a new build? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Recording screencasts
On Tue, 2011-03-15 at 17:41 +1100, Sridhar Dhanapalan wrote: > Is there a good way to record screencasts of a Sugar session on an XO? > > The best I can find is this: > http://wiki.sugarlabs.org/go/Activities/Screencast > > It looks to be quite incomplete. > > A screencast creation activity would be invaluable for our training and > support. > > I'm tracking our progress at http://dev.laptop.org.au/issues/479 > Maybe try Istanbul: > Sridhar > > > > Sridhar Dhanapalan > Technical Manager > One Laptop per Child Australia > M: +61 425 239 701 > E: srid...@laptop.org.au > A: G.P.O. Box 731 > Sydney, NSW 2001 > W: www.laptop.org.au > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Recording screencasts
Sorry - hit send by accident. On Tue, 2011-03-15 at 17:41 +1100, Sridhar Dhanapalan wrote: > Is there a good way to record screencasts of a Sugar session on an XO? > > The best I can find is this: > http://wiki.sugarlabs.org/go/Activities/Screencast > > It looks to be quite incomplete. > > A screencast creation activity would be invaluable for our training and > support. > > I'm tracking our progress at http://dev.laptop.org.au/issues/479 > Maybe try Istanbul: http://live.gnome.org/Istanbul You can run it from a Terminal and if the experience is decent enough it shouldn't be that hard to Sugarize it. Cheers, Raúl > Sridhar > > > > Sridhar Dhanapalan > Technical Manager > One Laptop per Child Australia > M: +61 425 239 701 > E: srid...@laptop.org.au > A: G.P.O. Box 731 > Sydney, NSW 2001 > W: www.laptop.org.au > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [PATCH] Don't feed None values to os.path.join
Heya, Playing with jhbuild I found out that setting wrong values to the LANG/LC_* variables might prevent Sugar activities from starting. Arguably, this is a very rare case and more likely to be a problem for developers (if for anyone). Gtk for once copes with this defaulting to the C locale. The attached patch against sugar-toolkit makes sure we deal with None being returned locate.getdefaultlocale()[0] and avoid passing it to os.join.path(). To reproduce the problem: export LANG=sugar-rocks ./sugar-jhbuild .. Cheers, Raul >From b1ebad78dbf7c41daebacb53532cf1786725956b Mon Sep 17 00:00:00 2001 From: Raul Gutierrez Segales Date: Sat, 23 Jul 2011 18:08:58 +0100 Subject: [PATCH] Make sure we don't feed None values to os.path.join On certain ocassions, if the user has played with LANG and/or LC_* environment variables, locale.getdefaultlocale()[0] could be None. If so, make sure we don't pass that to os.path.join cause it'll choke if we do. Reviewed-by: Walter Bender --- src/sugar/activity/i18n.py |5 - 1 files changed, 4 insertions(+), 1 deletions(-) diff --git a/src/sugar/activity/i18n.py b/src/sugar/activity/i18n.py index 1ddbd79..4361da5 100644 --- a/src/sugar/activity/i18n.py +++ b/src/sugar/activity/i18n.py @@ -144,8 +144,11 @@ def get_locale_path(bundle_id): for candidate_dir in candidate_dirs.keys(): if os.path.exists(candidate_dir): +default_locale = locale.getdefaultlocale()[0] +if default_locale is None: +default_locale = "" full_path = os.path.join(candidate_dir, \ -locale.getdefaultlocale()[0], 'LC_MESSAGES', \ +default_locale, 'LC_MESSAGES', \ bundle_id + '.mo') if os.path.exists(full_path): try: -- 1.7.6 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Moving to GTK3 and GObject Introspection
Hey, On Fri, 2011-08-05 at 17:29 +0100, Daniel Drake wrote: > On Fri, Aug 5, 2011 at 5:16 PM, Gonzalo Odiard wrote: > > Ok, that is the reason because I have started a new different page. > > We can start to research this API improvements anyway, > > probably will not be the same people involved. > > That's true. The example you have there is actually an API addition, > so could fall into any release cycle (I think) - so as you say, it > doesn't have to be linked with this project. Today at the Desktop Summit Daniel Drake (working remotely), Benjamin Berg, Paul Proteus and me got the HelloWorld activity ported to gtk3 and running on a version of Sugar that doesn't use Hippo (based on the work we started with Walter and others to remove Hippo a couple of weeks ago). Code is here (gtk3 branches): http://cgit.collabora.com/git/user/rgs/sugar/ http://cgit.collabora.com/git/user/rgs/sugar-toolkit/ The procedure, as suggested by Daniel, (I'll document this on the Wiki before the Summit ends) was: - remove Hippo (done previously) - make a copies of sugar and jarabe and name them sugar-gtk3 and jarabe-gtk3 - make sure that you import sugar-gtk3 and jarabe-gtk3 all over the code - port both of them to PyGObject/gtk3 using the pygi-convert.sh script - port the HelloWorld activity to gtk3 - use a hacked version of sugar-activity that invokes sugar-gtk3 - update a couple of method calls to their new PyGObject API and that was about it. Please note that this was a brute-force approach (i.e.: lots of hacks and comments here and there) to proof if this is conceptually possible (having gtk2 and gtk3 activities co-exist). And it seems it'll work (and it'll be fun!). I am planning on chasing Benjamin during the Summit to see if we can get Sugar's theme ported :) I'll keep the list updated with whatever progress we make and try to document all of this on the Wiki so others can join in. Cheers, Raul ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
