[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Record quickly vanishes on new F11-for-XO1



FYI. I'm not asking for help. Am sharing information in case anyone else encounters a similar situation.

I'm running http://dev.laptop.org/~dsd/f11-xo1/os2, updated with 'yum upgrade'. On other F11 builds I'm used to 'Record' coming up without the "Video" tab - but this time 'Record' launched, drew its screen output for a very brief instant, then vanished.

The interesting lines in the log are:
| 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 54 error_code 11 request_code 131 minor_code 19)

mikus

/usr/lib/python2.6/site-packages/sugar/util.py:25: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import sha
1248848267.163377 ERROR root: Invalid SUGAR_SCALING.
1248848269.105101 DEBUG root: use /home/olpc/Activities/Record.activity/camerac/linux32_2.5 blobs
1248848273.487411 DEBUG root: *** Act 92a5f3d9d9bb684b016125f51dc6e90fe32a973b, mesh instance None, scope private
1248848273.489687 DEBUG root: Creating a jobject.
1248848273.499025 DEBUG root: datastore.write
1248848273.572128 DEBUG root: dbus_helpers.create: 69564237-268f-4abf-b62d-514927661b40
1248848273.574467 DEBUG root: Written object 69564237-268f-4abf-b62d-514927661b40 to the datastore.
** (sugar-activity:2480): DEBUG: Got client ID "10cd79f85e456f851d124884827446300700000019690001"
** (sugar-activity:2480): DEBUG: Setting initial properties
1248848274.715700 DEBUG record:glive.py: Set volume 13 to Capture
1248848275.019350 DEBUG root: ('Setup widget', None)
1248848275.028288 WARNING root: No gtk.AccelGroup in the top level window.
1248848275.051012 DEBUG root: ('Setup widget', None)
1248848275.057761 WARNING root: No gtk.AccelGroup in the top level window.
** (sugar-activity:2480): DEBUG: Received SaveYourself(SmSaveLocal, !Shutdown, SmInteractStyleNone, !Fast) in state idle
** (sugar-activity:2480): DEBUG: Sending SaveYourselfDone(True) for initial SaveYourself
1248848275.285579 DEBUG root: ActivityService.set_active: 1.
** (sugar-activity:2480): DEBUG: Received SaveComplete message in state save-yourself-done
1248848276.454484 DEBUG root: Activity.__canvas_map_cb
1248848276.511922 DEBUG root: updateProgress 0
1248848276.571627 DEBUG root: updateProgress 0
1248848276.575021 DEBUG record:glive.py: play
1248848277.139989 DEBUG root: updateProgress 0
1248848277.143126 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
1248848277.709279 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
1248848277.711488 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 54 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.)

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]