#12412 NORM 13.1.0: Write fails to launch on XO-1

Zarro Boogs per Child bugtracker at laptop.org
Wed Dec 19 09:30:44 EST 2012

#12412: Write fails to launch on XO-1
 Reporter:  dsd                       |                 Owner:  dsd          
     Type:  defect                    |                Status:  new          
 Priority:  normal                    |             Milestone:  13.1.0       
Component:  write-activity (abiword)  |               Version:  not specified
 Keywords:                            |           Next_action:  add to build 
 Verified:  0                         |   Deployment_affected:               
Blockedby:                            |              Blocking:               
 In 13.1.0 build 19, Write-84 fails to launch with:

 Traceback (most recent call last):
   File "/usr/bin/sugar-activity", line 160, in <module>
   File "/usr/bin/sugar-activity", line 155, in main
     instance = create_activity_instance(activity_constructor,
   File "/usr/bin/sugar-activity", line 42, in create_activity_instance
     activity = constructor(handle)
   File "/home/olpc/Activities/Write.activity/AbiWordActivity.py", line 69,
 in __init__
     self.abiword_canvas = DocumentView()
   File "/home/olpc/Activities/Write.activity/widgets.py", line 260, in
     self.connect('request-clear-area', self.__request_clear_area_cb)
 TypeError: <DocumentView object at 0x9a07d9c (widgets+DocumentView at
 0x9996d28)>: unknown signal name: request-clear-area
 Exited with status 1, pid 2312 data (None, <open file '<fdopen>', mode 'w'
 at 0xa076c28>, 'e711fdedf65c787f06141dded37bd92d0f5e80f3')

 This is because I was lazy and didn't ship our custom gtk3 version on x86,
 and Write now requires this signal.

 I'll add the custom gtk3 to the x86 builds as well, but it may also make
 sense for Write to keep working even when this signal doesn't exist.

Ticket URL: <http://dev.laptop.org/ticket/12412>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system

More information about the Bugs mailing list