[Sugar-devel] [Activities] Issues Clock Maze Measure Physiscs

David Farning dfarning at sugarlabs.org
Thu Aug 6 13:05:27 EDT 2009


Andrés,
Most of it** is looking like a hardware gfx card driver issue under
Fedora.  I am not sure how to fix that or even who is knowledgeable
about the issue.  I have Cced Tomeu and Simon maybe they have some
advice.

Thanks for sticking with us on this.

david

On Wed, Aug 5, 2009 at 7:20 PM, Andrés Arrieta
Perréard<andres.ap.linux at gmail.com> wrote:
> Hi,
>
> On Wed, Aug 5, 2009 at 6:38 PM, Gary C Martin <gary at garycmartin.com> wrote:
>>
>> Hi Andrés,
>>
>> Thanks for the feedback.
>>
>> On 5 Aug 2009, at 21:11, Andrés Arrieta Perréard wrote:
>>
>>> *Clock (Some times you can not see the clock):*
>>> */usr/lib/python2.6/site-packages/sugar/util.py:25: DeprecationWarning:
>>> the
>>> sha module is deprecated; use the hashlib module instead
>>>  import sha
>>> 1248977761.813519 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248977761.851770 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> ** (sugar-activity:2323): DEBUG: Got client ID
>>> "1093bb3c6e2cea8c72124897776519290500000021170003"
>>> ** (sugar-activity:2323): DEBUG: Setting initial properties
>>> ** (sugar-activity:2323): DEBUG: Received SaveYourself(SmSaveLocal,
>>> !Shutdown, SmInteractStyleNone, !Fast) in state idle
>>> ** (sugar-activity:2323): DEBUG: Sending SaveYourselfDone(True) for
>>> initial
>>> SaveYourself
>>> ** (sugar-activity:2323): DEBUG: Received SaveComplete message in state
>>> save-yourself-done
>>> 1248977878.267682 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248977880.421383 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248977880.439221 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248977880.441122 WARNING root: No gtk.AccelGroup in the top level
>>> window.*
>>
>> Clock is an Activity I recently adopted. Hmm, no useful
>> errors/fails/tracebacks there unfortunately (just warnings, FWIW SoaS seems
>> to have pretty low threshold for debug output). Can you describe what you
>> mean by "some times your can not see the clock". Does the screen go blank or
>> grey, does it redraw strangely, or perhaps stop for a while? Can you see the
>> Sugar toolbar, or is it just the clock 'canvas' area that's incorrect?
>
>
> It stays with the grey background, all loads except for the clock. At least
> it seems that thi first time you open it it will not show any images within
> that area, the text that says the time or something like that does loads
> tho. After the first run every thing seems to run normally.
>
>>
>>> *Maze (wont start):**
>>> /usr/lib/python2.6/site-packages/sugar/util.py:25: DeprecationWarning:
>>> the
>>> sha module is deprecated; use the hashlib module instead
>>>  import sha
>>> 1248976744.209587 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248976744.213911 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> ** (sugar-activity:2269): DEBUG: Got client ID
>>> "1093bb3c6e2cea8c72124897674772567300000021170000"
>>> ** (sugar-activity:2269): DEBUG: Setting initial properties
>>> ** (sugar-activity:2269): DEBUG: Received SaveYourself(SmSaveLocal,
>>> !Shutdown, SmInteractStyleNone, !Fast) in state idle
>>> ** (sugar-activity:2269): DEBUG: Sending SaveYourselfDone(True) for
>>> initial
>>> SaveYourself
>>> ** (sugar-activity:2269): DEBUG: Received SaveComplete message in state
>>> save-yourself-done
>>> 1248976777.877888 WARNING olpcgames.pausescreen: Pausing activity after
>>> 30
>>> with function <function pauseScreen at 0x9a752cc>
>>> 1248976798.908470 WARNING olpcgames.pausescreen: Activity restarted
>>> 1248976829.581685 WARNING olpcgames.pausescreen: Pausing activity after
>>> 30
>>> with function <function pauseScreen at 0x9a752cc>
>>> 1248976878.653855 WARNING olpcgames.pausescreen: Activity restarted*
>>
>> Hmm, not one of mine (nut I like it). I know this is PyGame based (as is
>> Physics). Again, nothing fatal logged above. When you say 'wont start' do
>> you see anything on screen after the pulsing icon at start-up; blank or grey
>> screen? The "pausing activity" messages look like it's running (somewhere).
>> I'm beginning to think low level graphics card driver issues (just a guess).
>
> It shows the blinking icon and after sometime it goes back to the menu. I
> can't remember the hardware of the computers on which was tested but as soon
> as I have that info I'll send it.
>
>
>
>
>>>
>>> *Measure (Wont Start):**
>>> /usr/lib/python2.6/site-packages/sugar/util.py:25: DeprecationWarning:
>>> the
>>> sha module is deprecated; use the hashlib module instead
>>>  import sha
>>> amixer: Unable to find simple control 'PCM',0
>>>
>>> $$journal.py: This is the file I will work on
>>> /home/liveuser/.sugar/default/org.laptop.MeasureActivity/data/tmp3UIdNJ
>>> Traceback (most recent call last):
>>>  File "/usr/bin/sugar-activity", line 21, in <module>
>>>   main.main()
>>>  File "/usr/lib/python2.6/site-packages/sugar/activity/main.py", line
>>> 140,
>>> in main
>>>   create_activity_instance(activity_constructor, activity_handle)
>>>  File "/usr/lib/python2.6/site-packages/sugar/activity/main.py", line 34,
>>> in create_activity_instance
>>>   activity = constructor(handle)
>>>  File "/home/liveuser/Activities/Measure.activity/measure.py", line 71,
>>> in
>>> __init__
>>>   self.audiograb = AudioGrab(self.wave.new_buffer, self.ji)
>>>  File "/home/liveuser/Activities/Measure.activity/audiograb.py", line 61,
>>> in __init__
>>>   self.PCM = self.get_PCM_gain()
>>>  File "/home/liveuser/Activities/Measure.activity/audiograb.py", line
>>> 382,
>>> in get_PCM_gain
>>>   return int(p)
>>> ValueError: invalid literal for int() with base 10: ''*
>>
>> Again not mine, but Measure does/did have some custom hardware specific
>> code for the XO laptop that allows its audio line-in to be set to special
>> input modes allowing you to use it like an oscilloscope. I might expect this
>> one to crash currently on some hardware It's been a while since I last
>> tested this. It should ideally at least fail gracefully, and just disable
>> those special features if not supported by the hardware (again I'm just
>> guessing here from the log).
>
> Ok
>>
>>> *Physiscs (Video all messed up, photos on links)*
>>> http://dashwire.com/alphinux/image/bs0XtsFtSr3QccadbiFPIU/
>>> http://dashwire.com/alphinux/image/bUbgtUFtCr3QccadbiFPIU/
>>> http://dashwire.com/alphinux/image/bEd3deFtCr3R4JadbiFTTI/
>>>
>>> */usr/lib/python2.6/site-packages/sugar/util.py:25: DeprecationWarning:
>>> the
>>> sha module is deprecated; use the hashlib module instead
>>>  import sha
>>> 1248973844.612091 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973844.626403 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973844.631980 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973844.635663 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973844.639058 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973844.642383 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973844.645793 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973844.649399 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973844.652005 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973844.654533 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973844.657102 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973844.659660 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973844.672775 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> ** (sugar-activity:2412): DEBUG: Got client ID
>>> "10d240b9f8cec92402124897384789079400000023220001"
>>> ** (sugar-activity:2412): DEBUG: Setting initial properties
>>> ** (sugar-activity:2412): DEBUG: Received SaveYourself(SmSaveLocal,
>>> !Shutdown, SmInteractStyleNone, !Fast) in state idle
>>> ** (sugar-activity:2412): DEBUG: Sending SaveYourselfDone(True) for
>>> initial
>>> SaveYourself
>>> ** (sugar-activity:2412): DEBUG: Received SaveComplete message in state
>>> save-yourself-done
>>> /home/liveuser/Activities/Physics.activity/tools.py:80:
>>> DeprecationWarning:
>>> integer argument expected, got float
>>>  pygame.draw.circle(self.game.screen,
>>> (100,180,255),self.pt1,self.radius,thick)
>>> 1248973871.619364 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973873.628075 WARNING olpcgames.activity: No file created in
>>> '/home/liveuser/.sugar/default/org.laptop.physics/instance/1248973873'
>>> 1248973873.672515 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973873.680338 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973873.681211 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973873.683851 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973873.685444 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973873.685910 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973873.686345 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973873.686778 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973873.687187 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973873.687619 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973873.703018 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973873.703706 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973873.704137 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> 1248973873.704550 WARNING root: No gtk.AccelGroup in the top level
>>> window.
>>> Loading box2d for Linux (32bit)
>>> * Pygame selected as renderer
>>
>> OK, Physics is something I do help maintain. Again no critical errors
>> shown above, all normal (given the Soas debug level) for a working case of
>> Physics. Physics is based on PyGame (as is Maze above). Thanks for the
>> screen shots, these very much say to me "likely problems with graphics card
>> driver". I do use and test Physics here in a number of different resolutions
>> and different hardware.
>>
>> Can you perhaps name the hardware you are running Soas? Graphics card
>> details/type would be particularly useful so we can check if Fedora supports
>> it correctly.
>
> Sure just let me get that info.
>
>
>>
>> Thanks again for taking the time to provide us with feedback!
>>
>> Regards,
>> --Gary
>>
>
> Thx for the help
>
>
> --
> - Andrés Arrieta Perréard (XE1YAA)
>
>


More information about the Sugar-devel mailing list