Re: [Sugar-devel] Installing gstreamer media codecs on XO-1
Martin, My current procedure with Internet connection is as follows yum localinstall --nogpgcheck rpmfusion-free-stable.rpm yum localinstall --nogpgcheck rpmfusion-nonfree-stable.rpm yum install -y gstreamer-plugins-ugly yum install -y gstreamer-ffmpeg Each of the stages above (even the localinstalls) require Internet access to download stuff. To do as you suggest, how would I now use yumdownloader? Sorry I am a little slow in the up[take on this :( David -Original Message- From: Martin Langhoff [mailto:martin.langh...@gmail.com] Sent: Tuesday, 3 April 2012 1:03 p.m. To: David Leeming Cc: Kevin Mark; Sugar devel Subject: Re: [Sugar-devel] Installing gstreamer media codecs on XO-1 On Mon, Apr 2, 2012 at 6:51 AM, David Leeming wrote: > I am interested in trying this out, as I am going to be doing some teacher > training workshops in remote PNG areas where there is no Internet access. the quickest, surest path is use yumdownloader --resolve to grab all the rpms, and have them on a USB stick. Steps were discussed on this same email threads. I can't think of an easier path for a small to moderate number of units. You could build an OS image, set it up on the XS for auto-installation on the XOs, and run olpc-update. But there's a sizable amount of prep in that, so unless you prepped it all back when you prepped the OS image they have _now_, you end up still needing to mess with each laptop. In the end, you only need to say "sudo rpm -Uvh *rpm" on each unit. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Installing gstreamer media codecs on XO-1
On Mon, Apr 2, 2012 at 6:51 AM, David Leeming wrote: > I am interested in trying this out, as I am going to be doing some teacher > training workshops in remote PNG areas where there is no Internet access. the quickest, surest path is use yumdownloader --resolve to grab all the rpms, and have them on a USB stick. Steps were discussed on this same email threads. I can't think of an easier path for a small to moderate number of units. You could build an OS image, set it up on the XS for auto-installation on the XOs, and run olpc-update. But there's a sizable amount of prep in that, so unless you prepped it all back when you prepped the OS image they have _now_, you end up still needing to mess with each laptop. In the end, you only need to say "sudo rpm -Uvh *rpm" on each unit. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Local server equivalent of "jabber.sugarlabs.org"
Excerpts from Ajay Garg's message of 2012-03-29 06:55:19 +0200: > I am wanting to play around with a Jabber server, which is same in the > basics as "jabber.sugarlabs.org". > So, what should I install locally? jabberd? ejabberd? any other server? Depends on what exactly you want. Possibilities: 1. Some XMPP server that works with Sugar. Install ejabberd from distro packages and set up the shared roster groups [1]. This is what I did for my own personal server. 2. A server that mimics what most schools are going to have. Install XS-on-XO. I didn't get the non-XO variant to work (inside a VM), but XS-on-XO-1 worked fine the last time I tried it. 3. A replica of jabber.sugarlabs.org to debug problems with it. Ask Aleksey. AFAIK jabber.sl.o is running some patched version of Prosody. Sascha [1] http://wiki.laptop.org/go/XS_Installing_Software_0.5#Setup_Shared_Roster_Groups_for_ejabberd [2] http://wiki.laptop.org/go/XS-on-XO -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Cautions on using a f17 beta DVD to upgrade a f16 hard disk installed with sugar-desktop
Caution; Just using the f17 Beta DVD to do an upgrade from f16 to f17 will leave an incomplete upgrade. DVD upgrade of F16 - to F17 requires "yum update" on Reboot to complete. [1] This is a very large update. There is no indication after you reboot after the DVD upgrade that this is required. Tom Gilliard satellit_ [1 ] http://wiki.sugarlabs.org/go/Community/Distributions/Fedora#f16_DVD_Upgrade_to_F17 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [PATCH sugar] Don't treat SSID as UTF-8 character sequence (fixes SL#2023)
IEEE 802.11 [2] defines the SSID as a sequence of octets (i.e. bytes), but
Sugar treated it as UTF-8 character data. While in most cases the SSID is
actually some human-readable string, there's neither a guarantee for that nor
does any (de-facto or de-jure) standard specify the encoding to use. As a
result, we'll encounter SSIDs in a large variety of encodings and will also
need to cope with arbitrary byte strings. Any assumption of a single (or in
fact any) character encoding is incorrect.
The D-Bus API of NetworkManager 0.9 [3] passes SSIDs as uninterpreted byte
strings (D-Bus signature "ay"). Before SSIDs can be displayed on screen, some
kind of interpretation must happen.
NetworkManager has a rather elaborate heuristic that takes the user locale into
account. In the future (i.e. when the NetworkManager client code in Sugar has
been ported to gobject-introspection) we may use nm_utils_ssid_to_utf8() [4],
but for now we're doing the following to allow the user to use non-UTF-8 APs at
all:
1. If the SSID is a valid character string consisting only of
printable characters in one of the following encodings (tried in
the given order), decode it accordingly:
UTF-8, ISO-8859-1, Windows-1251.
2. Return a hex dump of the SSID.
The first rule should cover the majority of current Sugar users and hopefully
all AP vendors will switch to UTF-8 eventually. In the meantime, the second
rule allows users to distinguish between several APs with SSIDs in unknown
encodings (or even using arbitrary byte sequences that don't _have_ a character
representation).
Tested:
- filtering on ASCII and non-ASCII parts of the name of and connecting to:
- an unsecured AP with a UTF-8 SSID ("äöü߀sugartest", HostAP)
- an unsecured AP with an ISO-8859-1 SSID ("äöüßsugartest", HostAP)
- an unsecured AP with a non-character SSID (0d:06:f0:0d, HostAP)
- a WEP-secured AP with a UTF-8 name ("äöü߀sugartest2", HostAP)
- a WEP-secured AP with an ISO-8859-1 name ("äöüßsugartest2", HostAP)
- a WEP-secured AP with a non-character SSID (0d:06:f0:0d, HostAP)
- a WPA-secured AP with an ASCII name (COTS AP)
In each case the name was displayed correctly in
a) the palette of the AP icon in the Neighbourhood,
b) the palette of the wireless network Frame device and
c) the title of the WLAN credentials (WEP/WPA passphrase) dialog (for
the WEP/WPA cases).
[1] https://bugs.sugarlabs.org/ticket/2023
[2] http://standards.ieee.org/getieee802/download/802.11-2007.pdf
[3] http://projects.gnome.org/NetworkManager/developers/api/09/spec.html
[4]
http://projects.gnome.org/NetworkManager/developers/libnm-util/09/libnm-util-nm-utils.html#nm-utils-ssid-to-utf8
Signed-off-by: Sascha Silbe
---
extensions/deviceicon/network.py | 17 +++-
src/jarabe/desktop/keydialog.py|5 ++-
src/jarabe/desktop/meshbox.py |4 +-
src/jarabe/desktop/networkviews.py | 33 ---
src/jarabe/model/adhoc.py |6 ++--
src/jarabe/model/network.py| 49 +--
6 files changed, 81 insertions(+), 33 deletions(-)
diff --git a/extensions/deviceicon/network.py b/extensions/deviceicon/network.py
index 1beeb88..09a3abb 100644
--- a/extensions/deviceicon/network.py
+++ b/extensions/deviceicon/network.py
@@ -374,7 +374,8 @@ class WirelessDeviceView(ToolButton):
self._device = device
self._device_props = None
self._flags = 0
-self._name = ''
+self._ssid = ''
+self._display_name = ''
self._mode = network.NM_802_11_MODE_UNKNOWN
self._strength = 0
self._frequency = 0
@@ -394,7 +395,7 @@ class WirelessDeviceView(ToolButton):
self._icon.show()
self.set_palette_invoker(FrameWidgetInvoker(self))
-self._palette = WirelessPalette(self._name)
+self._palette = WirelessPalette(self._display_name)
self._palette.connect('deactivate-connection',
self.__deactivate_connection_cb)
self.set_palette(self._palette)
@@ -471,7 +472,8 @@ class WirelessDeviceView(ToolButton):
self._mode = properties['Mode']
self._color = None
if 'Ssid' in properties:
-self._name = properties['Ssid']
+self._ssid = properties['Ssid']
+self._display_name = network.ssid_to_display_name(self._ssid)
self._color = None
if 'Strength' in properties:
self._strength = properties['Strength']
@@ -482,11 +484,11 @@ class WirelessDeviceView(ToolButton):
if self._color == None:
if self._mode == network.NM_802_11_MODE_ADHOC and \
-network.is_sugar_adhoc_network(self._name):
+network.is_sugar_adhoc_network(self._ssid):
self._color = profile.get_color()
else:
sha_hash = hashlib.sha1()
-data = self._name + hex(self._flags)
+data =
[Sugar-devel] [PATCH sugar] Fix Traceback when connecting to a network for the first time
When connecting to a network that we don't have settings for yet, the following
Traceback was logged:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 586, in
msg_reply_handler
reply_handler(*message.get_args_list(**get_args_opts))
TypeError: _activate_reply_cb() takes exactly 1 argument (2 given)
This is because the same set of callbacks was used for both
ActivateConnection() and AddAndActivateConnection() even though they return
different sets of values.
Signed-off-by: Sascha Silbe
---
I already hit this once while reviewing the original NM 0.9 patch,
but could never reproduce it. Now I know why: the call succeeded, so
any further connect attempt re-used the existing connection,
triggering the code path with the correct number of arguments.
src/jarabe/model/network.py | 21 +++--
1 files changed, 15 insertions(+), 6 deletions(-)
diff --git a/src/jarabe/model/network.py b/src/jarabe/model/network.py
index af510e1..40eb6d0 100644
--- a/src/jarabe/model/network.py
+++ b/src/jarabe/model/network.py
@@ -728,14 +728,22 @@ def get_secret_agent():
return _secret_agent
-def _activate_reply_cb(connection):
-logging.debug('Activated connection: %s', connection)
+def _activate_reply_cb(connection_path):
+logging.debug('Activated connection: %s', connection_path)
def _activate_error_cb(err):
logging.error('Failed to activate connection: %s', err)
+def _add_and_activate_reply_cb(settings_path, connection_path):
+logging.debug('Added and activated connection: %s', connection_path)
+
+
+def _add_and_activate_error_cb(err):
+logging.error('Failed to add and activate connection: %s', err)
+
+
class Connection(gobject.GObject):
__gsignals__ = {
'removed': (gobject.SIGNAL_RUN_LAST, gobject.TYPE_NONE, ()),
@@ -900,10 +908,11 @@ def activate_connection_by_path(connection, device_o,
def add_and_activate_connection(device_o, settings, specific_object):
-get_manager().AddAndActivateConnection(settings.get_dict(), device_o,
- specific_object,
- reply_handler=_activate_reply_cb,
- error_handler=_activate_error_cb)
+manager = get_manager()
+manager.AddAndActivateConnection(settings.get_dict(), device_o,
+ specific_object,
+ reply_handler=_add_and_activate_reply_cb,
+ error_handler=_add_and_activate_error_cb)
def _migrate_old_wifi_connections():
--
1.7.9
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Installing gstreamer media codecs on XO-1
-Original Message- From: sugar-devel-boun...@lists.sugarlabs.org [mailto:sugar-devel-boun...@lists.sugarlabs.org] On Behalf Of Kevin Mark Sent: Wednesday, 21 March 2012 4:03 p.m. To: Kevin Mark Cc: David Leeming; 'Sugar devel' Subject: Re: [Sugar-devel] Installing gstreamer media codecs on XO-1 On Tue, Mar 20, 2012 at 03:29:03AM -0400, Kevin Mark wrote: > > 3. is the update step above necessary (it requires downloading 33MB) > > I have not tried this, it may be. I dont know the complete list of rpms that it > installed other then the 2 you said. those 2 might work with the current > packages or they might need to update a few packages and download the needed > dependencies which means the update is needed. This sounds like it might need > a local 'proxy'/mirror server to the needed rpms. so the xo's could do the 'rpm > update' but would get the 'update' and the needed rpms from a local server. > this would need the XOs to alter their rpm repo list. i'm not a rpm expert, so > you'd need to test a solution to ensure it works and does not alter other > support issues. > > old way: > XO->Fedora server (per each XO over the global internet) > vs > new way: > local Fedora server->Fedora server (via the global internet one time) > XO->local Fedora server(per each XO over a local area network (LAN)) I am interested in trying this out, as I am going to be doing some teacher training workshops in remote PNG areas where there is no Internet access. They will need to view resources that I will be making available on a server (XS-0.6). It seems that I can't reliably install these codecs from the rpms alone, without the XO wanting to connect and download stuff. Is there any way I can set up the mirror server as you describe on the XS, so that I can carry that to the remote area and have the XOs use that to get the updates? And how? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] MP4 playback on XO-1.75?
On Mon, Apr 2, 2012 at 5:59 AM, Kevin Mark wrote: > On Mon, Apr 02, 2012 at 12:34:26AM +0200, Christoph Derndorfer wrote: > > Hi all, > > > > I just tried playing back the downloaded version of the recent > littleBits TED > > talk ( http://www.ted.com/talks/ > > ayah_bdeir_building_blocks_that_blink_beep_and_teach.html ) on an > XO-1.75 but > > couldn't get it to work regardless of what I tried. In the past I always > used > > the mplayer version that came with Flavio's JAMedia Activity to watch > videos on > > XOs but that doesn't seem to work. Under Gnome the Movie Player asks for > > additional codecs but upon trying to install them there's a long error > message > > which I think is trying to tell me that the necessary codecs aren't > available > > for the ARM architecture. > > > > To make a long story short: Is there a way to watch MP4 videos on an > XO-1.75 at > > this point in time? :-) > > I dont have an 175 but I'd hazard a guess at first transcoding to ogg > theora? > there are IIRC online media converting sites. > Hi Kevin, yeah, I had thought of going that route but it would be quite a hassle compared to simply being able to play back the video... :-/ Thanks, Christoph -- Christoph Derndorfer volunteer, OLPC (Austria) [www.olpc.at] editor, OLPC News [www.olpcnews.com] contributor, TechnikBasteln [www.technikbasteln.net] e-mail: christ...@derndorfer.eu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
