Opened 8 years ago

Closed 8 years ago

#4509 closed defect (fixed)

ERROR write-activity: use gst-plugins-espeak

Reported by: olea Owned by: godiard
Priority: Unspecified by Maintainer Milestone: Unspecified
Component: Write Version: 0.98.x
Severity: Blocker Keywords:
Cc: erikos Distribution/OS: Fedora
Bug Status: Unconfirmed

Description

After building Write 89 with libabiword 2.9.4[1] I got this error when launching Write.

I've checked the espeak plugin is correctly installed:
gstreamer-plugins-espeak-0.4.0-1.fc18.i686

at /usr/lib/gstreamer-1.0/libgstespeak.so

The test platform is Fedora 18.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=605573

Attachments (1)

org.laptop.AbiWordActivity-1.log (1004 bytes) - added by olea 8 years ago.
org.laptop.AbiWordActivity-1.log

Download all attachments as: .zip

Change History (5)

Changed 8 years ago by olea

org.laptop.AbiWordActivity-1.log

comment:1 Changed 8 years ago by godiard

  • Component changed from untriaged to Write
  • Owner set to godiard

comment:2 follow-up: Changed 8 years ago by godiard

  • Cc erikos added

This error is not related with the speak plugin.

I think the important part is:

12 File "/usr/share/sugar/activities/Write.activity/widgets.py", line 308, in init
13 self.connect('request-clear-area', self.request_clear_area_cb)

Simon, do you remember if that is a gtk modification in our rpms? Should be upstream now?

comment:3 in reply to: ↑ 2 Changed 8 years ago by olea

Replying to godiard:

I think the important part is:

12 File "/usr/share/sugar/activities/Write.activity/widgets.py", line 308, in init
13 self.connect('request-clear-area', self.request_clear_area_cb)


I just checked the «unknown signal name: request-clear-area» error is reported at https://dev.laptop.org/ticket/12412 too.

comment:4 Changed 8 years ago by godiard

  • Resolution set to fixed
  • Status changed from new to closed

I have pushed a change to ignore errors if the signals request-clear-area or unset-clear-area are not available.

Is included in Write 91. Please reopen this ticket if you have any other issue.

Note: See TracTickets for help on using tickets.