SoaS3-20090822 limps
by Mikus Grinbergs
Disclaimer: I am not asking for help; I'm sharing my experiences.
Booted SoaS3-200908222158.iso (from USB stick) on my XO-1. I don't
know if it was the USB stick's hardware, or the build's software,
but now my system seemed to run at least twice as slow as normal.
The first try I got as far as Home View, but when I tried to switch
to the List panel (because Terminal was not in the ring), Sugar
vanished. The second try I instead clicked on 'Speak' in the ring
(see attachment). The third try I went to the text console, and
manually modified favorite_activities to put Terminal in the ring.
Then I was able to do my usual things - but at a snail's pace.
This is going to be the last SoaS3 build I'll try for the time
being. I'm interested in how the __XO__ runs, and software
development for the XO is currently F11-based. This new SoaS3 build
is F12-based - I'll stick with F11 and forget about F12 for now.
mikus
1251038256.899823 ERROR dbus.proxies: Introspect error on org.laptop.Sugar.Presence:/org/laptop/Sugar/Presence: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root
** (sugar-session:1413): DEBUG: starting phase 1
** (sugar-session:1413): DEBUG: ending phase 1
** (sugar-session:1413): DEBUG: starting phase 2
** (sugar-session:1413): DEBUG: ending phase 2
** (sugar-session:1413): DEBUG: starting phase 3
** (sugar-session:1413): DEBUG: ending phase 3
** (sugar-session:1413): DEBUG: starting phase 4
** (sugar-session:1413): DEBUG: ending phase 4
** (sugar-session:1413): DEBUG: starting phase 5
** (sugar-session:1413): DEBUG: ending phase 5
1251038287.708129 WARNING root: No gtk.AccelGroup in the top level window.
1251038287.763408 WARNING root: No gtk.AccelGroup in the top level window.
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/jarabe/desktop/homewindow.py", line 87, in _visibility_notify_event_cb
self._activate_view()
TypeError: _activate_view() takes exactly 2 arguments (1 given)
1251038299.406576 ERROR dbus.proxies: Introspect error on org.freedesktop.ohm:/org/freedesktop/ohm/Keystore: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ohm was not provided by any .service files
1251038299.422231 ERROR root: Cannot unfreeze the DCON
/usr/lib/python2.6/site-packages/dbus/connection.py:242: DeprecationWarning: object.__init__() takes no parameters
super(Connection, self).__init__(*args, **kwargs)
/usr/lib/python2.6/site-packages/sugar/graphics/window.py:275: DeprecationWarning: use toolbar_box instead of toolbox
warnings.warn('use toolbar_box instead of toolbox', DeprecationWarning)
/usr/lib/python2.6/site-packages/sugar/graphics/window.py:271: DeprecationWarning: use toolbar_box instead of toolbox
warnings.warn('use toolbar_box instead of toolbox', DeprecationWarning)
/usr/lib/python2.6/site-packages/sugar/graphics/icon.py:270: DeprecationWarning: integer argument expected, got float
surface = cairo.ImageSurface(cairo.FORMAT_ARGB32, width, height)
1251038344.267773 ERROR root: Launcher for 3b6a52f99a1b1ffeb37fe71640ce4e6c5966fa68 is missing
1251038361.647409 WARNING root: No gtk.AccelGroup in the top level window.
1251038361.654480 WARNING root: No gtk.AccelGroup in the top level window.
/usr/lib/python2.6/site-packages/sugar/graphics/icon.py:136: DeprecationWarning: integer argument expected, got float
info = theme.lookup_icon(self.icon_name, size, 0)
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/jarabe/desktop/homewindow.py", line 87, in _visibility_notify_event_cb
self._activate_view()
TypeError: _activate_view() takes exactly 2 arguments (1 given)
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/jarabe/desktop/homewindow.py", line 87, in _visibility_notify_event_cb
self._activate_view()
TypeError: _activate_view() takes exactly 2 arguments (1 given)
/usr/lib/python2.6/site-packages/sugar/graphics/icon.py:273: DeprecationWarning: integer argument expected, got float
surface = cairo.ImageSurface(cairo.FORMAT_RGB24, width, height)
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/jarabe/desktop/homewindow.py", line 85, in _visibility_notify_event_cb
self._deactivate_view()
TypeError: _deactivate_view() takes exactly 2 arguments (1 given)
14 years, 8 months
Re: SoaS-for-XO-1 image
by Mikus Grinbergs
>> as usual with all F11-on-XO1 builds to date
>> 'Record' (quickly) gave up the ghost, without
>> showing me any "moving picture" output from the camera.
>
> The camera doesn't work in Record, which is at least this bug:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=3D498900
You will notice that this bug report is several months old, and
talks about the camera not being recognized. These days I believe
the camera *is* being recognized. From today's dmesg:
> [ 2.179390] Marvell M88ALP01 'CAFE' Camera Controller version 2
> [ 2.200957] cafe1000-ccic 0000:00:0c.2: enabling device (0000 -> 0002)
> [ 2.482758] ov7670 1-0042: chip found @ 0x84 (cafe_ccic)
I keep mentioning 'Record', because that is code being handled by
people working on the XO. But the _real_ problem started with a
Geode driver change after Joyride 2602 -- that was the last time my
various multimedia applications showed me what I would describe as a
"moving picture". Ever since, [first with F10-based builds and then
with F11-based builds] I either get a completely blank screen, or
only occasional "snapshots" extracted from the input data. For
instance, when running 'helix' (helix is the "movie" player for
Browse), at best I get to see shrunken still_pictures - and those
still_pictures get redrawn only rarely. [Those same multimedia
applications continue to work well for me with F9-based builds.]
mikus
14 years, 8 months
Re: SoaS-for-XO-1 image
by Mikus Grinbergs
http://people.sugarlabs.org/~mtd/soas-xo1/soasxo59.removable.img.tar.lzma
Seemed to run well (booted from USB stick). Thanks for a good job.
mikus
p.s. Got sound from 'Speak'. But as usual with all F11-on-XO1
builds to date, 'Record' (quickly) gave up the ghost, without
showing me any "moving picture" output from the camera.
/usr/lib/python2.6/site-packages/sugar/util.py:25: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
import sha
1250966592.240381 ERROR root: Invalid SUGAR_SCALING.
1250966593.706299 DEBUG root: skip /home/olpc/Activities/Record.activity/camerac/linux64_2.5 blobs: /home/olpc/Activities/Record.activity/camerac/linux64_2.5/camera.so: wrong ELF class: ELFCLASS64
1250966593.729216 DEBUG root: skip /home/olpc/Activities/Record.activity/camerac/linux64_2.6 blobs: /home/olpc/Activities/Record.activity/camerac/linux64_2.6/camera.so: wrong ELF class: ELFCLASS64
1250966593.755046 DEBUG root: use /home/olpc/Activities/Record.activity/camerac/linux32_2.5 blobs
1250966596.617354 DEBUG root: *** Act 8e127db29972ec6c4dd7b379fd7fe6570963013d, mesh instance None, scope private
1250966596.626820 DEBUG root: Creating a jobject.
1250966596.642083 DEBUG root: datastore.write
1250966596.725436 DEBUG root: dbus_helpers.create: d869e0aa-eaa0-4366-8819-8d684327801c
1250966596.736851 DEBUG root: Written object d869e0aa-eaa0-4366-8819-8d684327801c to the datastore.
1250966597.482751 DEBUG root: ActivityService.set_active: 1.
** (sugar-activity:2475): DEBUG: Got client ID "109214311527984570125096659755672000000021120002"
** (sugar-activity:2475): DEBUG: Setting initial properties
1250966597.696167 DEBUG record:glive.py: Set volume 13 to Capture
1250966598.393734 DEBUG root: ('Setup widget', None)
1250966598.408498 WARNING root: No gtk.AccelGroup in the top level window.
1250966598.438879 DEBUG root: ('Setup widget', None)
1250966598.455250 WARNING root: No gtk.AccelGroup in the top level window.
** (sugar-activity:2475): DEBUG: Received SaveYourself(SmSaveLocal, !Shutdown, SmInteractStyleNone, !Fast) in state idle
** (sugar-activity:2475): DEBUG: Sending SaveYourselfDone(True) for initial SaveYourself
** (sugar-activity:2475): DEBUG: Received SaveComplete message in state save-yourself-done
1250966599.704515 DEBUG root: Activity.__canvas_map_cb
1250966599.743161 DEBUG root: updateProgress 0
1250966599.806110 DEBUG root: updateProgress 0
1250966599.817982 DEBUG record:glive.py: play
1250966600.376437 DEBUG root: updateProgress 0
1250966607.707128 DEBUG record:ui.py: updateVideoComponents: MODE=(-1,0) FULLSCREEN=(False,False) LIVE=(True,True) RECD_INFO=(False,False) TRANSCODING=(False,False) MESHING=(False,False) windowStack=9
1250966609.452881 DEBUG record:ui.py: updateVideoComponents: MODE=(0,0) FULLSCREEN=(False,False) LIVE=(True,True) RECD_INFO=(False,False) TRANSCODING=(False,False) MESHING=(False,False) windowStack=9
1250966611.638009 DEBUG record:glive.py: play
The program 'sugar-activity' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 910 error_code 11 request_code 131 minor_code 19)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
14 years, 8 months
hwclock, rtcwake, /etc/adjtime
by Paul Fox
executive summary: we need to make sure that /etc/adjtime, as
shipped, has a third line that says "UTC". alternatively, we
should add such a line on first boot.
having already written all this out for myself, to be sure i
understand it, i'll share:
- the third line in /etc/adjtime specifies whether the
RTC is maintained in localtime or UTC. most unix
systems maintain the RTC in UTC.
- hwclock needs (and maintains) the third line, because
hwclock can set the system time from the RTC, and
vice-versa. if there's no third line, hwclock assumes
the RTC is maintained in localtime. (this surprises me,
but i think it's always been true.) hwclock will
add a third line if it's missing, and the added line
will say "LOCAL".
- rtcwake needs the third line, because it uses the RTC to
wake up the system at a given time in the future. if
rtcwake finds no third line in /etc/adjtime, it assumes UTC.
please note the irony that hwclock and rtcwake are both
provided by the same package (util-linux-ng).
- rtcwake has a bug with regard to daylight savings time
which only shows up if it thinks the RTC is in maintained
in localtime. the bug causes wakeup times to be wrong by
at least an hour.
- when an XO boots for the first time, the /etc/adjtime file
provided by the initscripts package has no third line.
- hwclock is run by /etc/init.d/halt when the system is
shutdown cleanly, at which point /etc/adjtime will
have it's third line created, to say "LOCAL".
- XO laptops have their RTC set to UTC at the factory.
the upshot of all this is that on initial boot of an XO,
rtcwake will work fine, and after the first shutdown, it will
not. i'm sure there are also implications for the system
time and date, and the system timezone. but i haven't thought
about those issues much.
anyway, i think it can all be fixed by shipping a complete
/etc/adjtime file.
paul
=---------------------
paul fox, pgf(a)laptop.org
14 years, 8 months
Re: F11 for XO1 - Fonts
by Daniel Drake
2009/8/18 Tomeu Vizoso <tomeu(a)sugarlabs.org>:
> On Mon, Aug 17, 2009 at 12:17, Daniel Drake<dsd(a)laptop.org> wrote:
>> 2009/8/7 Tomeu Vizoso <tomeu(a)sugarlabs.org>:
>>> But not all text is rendered with that default font size.
>>
>> Do you have examples?
>
> No, but I find it highly unlikely that all activities are using
> sugar.graphics.style.FONT_NORMAL.
then those activities are probably a bit naughty :)
In most cases they should be basing their font selections around what
sugar suggests, as this will now reflect the desires of the user.
My ideas so-far including my thoughts on the above issue are here:
http://wiki.sugarlabs.org/go/Features/Font_configuration
Daniel
14 years, 8 months
Re: [Sugar-devel] F11 for XO1 - Fonts
by Daniel Drake
2009/8/19 Art Hunkins <abhunkin(a)uncg.edu>:
> 1) With regard to the new user controls (bigger and smaller) in the Control
> Panel (or elsewhere):
> If I specify (in my script), e.g., set.property("gtk-font-name", "14")
> will "bigger" be an increment up from "14", or one up from whatever the
> default font size was?
It will always be size 14, which is about 14/72" in size.
The idea is that activity developers don't specify font sizes other
than using the default and, if they need to, <big> and <small>, so
they wouldn't do something like the above except for exceptional
cases. You may choose to be an exceptional case..
Daniel
14 years, 8 months
Re: What level Sugar Activities on F11 ?
by Mikus Grinbergs
> ASLO is naive about stable vs unstable platforms. Instead, when a
> Sugar Client pings ASLO for update information, it sends a string
> identifing which version of Sugar is running on the client. ASLO then
> responds by sending a link to the most appropriate update for a the
> given version of Sugar which the client is running.
I think that "single click" design is quite appropriate for kids who
are not concerned with "what level of Sugar does my system have ?"
I have my own preference -- "Mother, I'll do it myself !!!". Plus
the Sugar Client doesn't know about proxies, so mine can't ping ASLO
for update information. Plus the Activity updates I fetch get
installed onto my "permanent" SD card, not through the Journal.
Plus from hour to hour I might reboot an XO with wildly divergent
build versions (with completely different Sugar levels). Put that
all together, and what I (as someone operating "apart from" formal
releases) am interested is in is __reading about__ the most
appropriate update for what my XO is running at this instant.
[For whoever deleted from laptop.org the webpage listing optional
Activities for build 767 systems -- thanks a lot, NOT.]
mikus
14 years, 8 months
SoaS3-20090818 does not successfully launch Sugar on XO-1
by Mikus Grinbergs
Booted SoaS3-200908182110.iso (from USB stick) on my XO-1.
The screen kept switching between white and back as the system
repeatedly tried to launch an X session for Sugar - but failed.
I manually started a Sugar session from the text console. The
screen got as far as showing Home View (no update notification) --
but as soon as I clicked on the List icon (the Ring does not include
Terminal by default), the Sugar session vanished.
mikus
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
X.Org X Server 1.6.99.1
Release Date: (unreleased)
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.18-128.2.1.el5xen i686
Current Operating System: Linux localhost.localdomain 2.6.31-0.125.4.2.rc5.git2.fc12.i686 #1 SMP Tue Aug 11 21:20:05 EDT 2009 i586
Kernel command line: root=UUID=A113-3650 rootfstype=vfat rw liveimg overlay=UUID=A113-3650 quiet rhgb
Build Date: 11 August 2009 02:37:18PM
Build ID: xorg-x11-server 1.6.99-33.20090807.fc12
Current version of pixman: 0.15.18
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Aug 19 05:17:47 2009
(==) Using config file: "/etc/X11/xorg.conf"
AmdPciProbe: Probing for supported devices!
error setting MTRR (base = 0xfd000000, size = 0x01000000, type = 1) Inappropriate ioctl for device (25)
SELinux: Disabled on system, not enabling in X server
record: RECORD extension enabled at configure time.
record: This extension is known to be broken, disabling extension now..
record: http://bugs.freedesktop.org/show_bug.cgi?id=20500
error setting MTRR (base = 0xfd000000, size = 0x01000000, type = 1) Inappropriate ioctl for device (25)
error setting MTRR (base = 0xfd000000, size = 0x01000000, type = 1) Inappropriate ioctl for device (25)
SELinux: Disabled on system, not enabling in X server
record: RECORD extension enabled at configure time.
record: This extension is known to be broken, disabling extension now..
record: http://bugs.freedesktop.org/show_bug.cgi?id=20500
Backtrace:
0: X(xorg_backtrace+0x3c) [0x80a431c]
1: X [0x80a7b16]
2: [0xe6440c]
3: /usr/lib/xorg/modules/extensions/libglx.so [0x732393]
4: /usr/lib/xorg/modules/extensions/libglx.so [0x7263b2]
5: X(InitExtensions+0x85) [0x80c8ae5]
6: X [0x8062bf8]
7: /lib/libc.so.6(__libc_start_main+0xe6) [0x326b36]
8: X [0x8062981]
Link map:
0xe66000: (vdso)
0x8ac000: /usr/lib/libpciaccess.so.0
0x98b000: /usr/lib/libXfont.so.1
0xee6000: /usr/lib/libXau.so.6
0xa6f000: /usr/lib/libpixman-1.so.0
0x2fe000: /usr/lib/libhal.so.1
0xd96000: /lib/libdbus-1.so.3
0xfde000: /lib/libpthread.so.0
0xefc000: /usr/lib/libXdmcp.so.6
0x5c3000: /usr/lib/libssl.so.8
0x110000: /usr/lib/libcrypto.so.8
0x289000: /lib/libdl.so.2
0x28e000: /lib/libz.so.1
0x2a1000: /lib/libaudit.so.0
0xea9000: /lib/libselinux.so.1
0xb1b000: /lib/libm.so.6
0x943000: /lib/librt.so.1
0x310000: /lib/libc.so.6
0x48b000: /usr/lib/libfreetype.so.6
0xdeb000: /usr/lib/libfontenc.so.1
0x632000: /lib/libcap.so.2
0xd40000: /lib/ld-linux.so.2
0x2bc000: /lib/libgssapi_krb5.so.2
0x637000: /lib/libkrb5.so.3
0x5ad000: /lib/libcom_err.so.2
0x522000: /lib/libk5crypto.so.3
0x54d000: /lib/libresolv.so.2
0xede000: /lib/libattr.so.1
0xa08000: /lib/libkrb5support.so.0
0xd1f000: /lib/libkeyutils.so.1
0xba0000: /usr/lib/xorg/modules/extensions/libextmod.so
0x2ea000: /usr/lib/xorg/modules/extensions/libdbe.so
0x6f0000: /usr/lib/xorg/modules/extensions/libglx.so
0xa45000: /usr/lib/xorg/modules/extensions/librecord.so
0x2ef000: /usr/lib/xorg/modules/extensions/libdri.so
0x566000: /usr/lib/libdrm.so.2
0x2f9000: /usr/lib/xorg/modules/extensions/libdri2.so
0x75a000: /usr/lib/xorg/modules/drivers/amd_drv.so
0xc0a000: /usr/lib/xorg/modules/libfb.so
0x571000: /usr/lib/xorg/modules/libexa.so
0x5b0000: /usr/lib/xorg/modules/input/evdev_drv.so
0x612000: /lib/libnss_files.so.2
0x79b000: /lib/libgcc_s.so.1
Segmentation fault at address (nil)
Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
14 years, 8 months
Re: F11 for XO1 - Fonts
by Mikus Grinbergs
Comments from an user:
I'm perfectly content to *modify* settings myself, to achieve what I
consider a readable screen. What gets me worked up is that I __do
not know__ where all those settings are, nor *which* setting affects
which significant portion of what I am looking at. So please, in
your discussions, explicitly __mention__ the particular settings you
know about.
[ BTW, I consider my eyes to be "weak". Therefore I run (if I know
how) every screen on every machine (including Linux) with larger
text than what developers had in mind. The principal disadvantage
to this is that all too often the software sets up too small an
screen area to hold the complete text, if that text is over-sized. ]
The discussion of this topic has mainly addressed Sugar. There are
three principal areas of Sugar font usage that interest me:
* The text size shown within an Activity-drawn screen. The
Activity I use the most is Terminal. For it, I manually set
the font size by modifying ~/.sugar/default/terminalrc. It is
likely that I would want to change other Activities' font sizes
as well, if I started to use those Activities more.
* The text size used by Sugar for the drop-down palettes in Home
View. On some builds, I have been able to influence this in
/usr/lib/python2.6/site-packages/sugar/graphics/style.py.
I seem to recall that on some builds, this change also affected
the font size used for entries in Journal View -- but then
again, I seem to recall other builds in which changing style.py
didn't change the font size used by Journal. It would be nice
if I knew for sure how (independently - e.g., without affecting
Terminal) to change the font size used by Journal.
* There is a third area in which Sugar chooses the font size to
show - text associated with things in the top edge of the
screen (e.g., the "search" field in the List panel of Home
View). So far, I've just accepted whatever Sugar does there.
But there is another complete set of facilities to be considered -
applications "imported" from Linux. On cjb's 'rawhide-xo' builds, I
was able to go into Gnome and modify "appearance settings", some of
which were picked up by Linux applications launched from Terminal.
My most recent struggle has been with the 'Menu Bar' in (the latest)
Firefox (launched from Terminal). This text size on XO (I believe
defined from the system, not by the application) simply takes up too
much room. And I have as yet not found a way to make it smaller.
It would be nice to have "make text larger/smaller" controls. But
different text sizes are used by the system in different places --
it might require a separate "optional palette entry" for each of
those places to be able to adjust them all. [Also, if adjustments
are allowed, please provide a large range of adjustments. I hate it
when "zoom in" supports only two additional text sizes.]
mikus
14 years, 8 months
