Write activity doesn't let you write in the proper text box

[mkim]

Description: From startup, the write activity does not allow the user to write in the area put aside for the writer to write in it. A box at the top where the icons should appear has some text in it, and is clearly not supposed to be there, as it is gibberish. If you click in the area where you are supposed to be able to type in, the mouse cursor changes into a four direction icon (the one that generally indicates that something can be moved), but does not do anything.

Reproduction: is hard. We get different results when we try and reproduce the problem. The consistent problems we encounter are the text box appearing where the menu bar should be rather than appearing in the bottom writing area, and the inability to type in the box where you should be able to type in. Will add videos to depict different results in the comments shortly.

Expected behavior: You should be able to write in the given text box, right? That doesn't happen.

[mkim]

Video 1: ​http://www.youtube.com/watch?v=kx9vv48a_B4
Video 2: ​http://www.youtube.com/watch?v=FF9-OkMh6Y8

[sdz]

Alright, thanks a lot for the report! I gotta try and find the person that owns Write.

[garycmartin]

Replying to sdz:

Alright, thanks a lot for the report! I gotta try and find the person that owns Write.

So what version of the abiword libraries is this SoaS using (and is the SoaS Strawberry or Blueberry)? Write is just really a Python GTK+ Sugar user interface, all the real work is done by the abiword libraries (which have alway been part of the distro).

[sascha_silbe]

Bulk change distribution=SoaS -> component=SoaS

[sdz]

Replying to garycmartin:

Replying to sdz:

Alright, thanks a lot for the report! I gotta try and find the person that owns Write.

So what version of the abiword libraries is this SoaS using (and is the SoaS Strawberry or Blueberry)?

That's actually a good question. You might be seeing this issue because this is erikos' F12 + Sugar 0.88 test day build. Gotta check whether that appears in the F13 nightly builds as well.

[sdz]

This appears in the nightly builds, too. So it's not only the F12 build that's affected - raising priority here. According to Koji, we should have... abiword-2.8.2-1.fc13 right now. For PyAbiword, we have: pyabiword-0.8.0-3.fc13

Gary, does that help?

[garycmartin]

Hi,

Replying to sdz:

This appears in the nightly builds, too. So it's not only the F12 build that's affected - raising priority here. According to Koji, we should have... abiword-2.8.2-1.fc13 right now. For PyAbiword, we have: pyabiword-0.8.0-3.fc13

Gary, does that help?

Sorry, nothing much useful to add.

FWIW: I've not seen this behaviour during any previous Sugar testing. I have used recent versions of Write under Strawberry, Blueberry, and many versions of sugar-jhbuild (under F11), but I'm not involved in any nightly build testing (not even sure where the SoaS nightly builds are these days) other than keeping my day to day sugar-jhbuild install reasonably up to date.

Current F11 sugar-jhbuild 0.87.7 installed with pyabiword-0.8.0-1.fc11, abiword-2.8.1-1.fc11, and runs fine with Write-68.

Blueberry (F12) image installed with abiword-0.8.0-1.fc12, abiword-2-8-2-1.fc12, and running fine with Write-67.

[sdz]

Even more strange news: When downgrading to the related Blueberry package versions, this still occurs. Maybe it's a sugar / toolbar related thing, since neither the abiword, nor the write packages seem to have changed over the last time.

[pbrobinson]

This is working fine for me on today's rawhide (March 22nd) on an eeePC 901

It seems more like a screen/X layout issue with sugar than something with write/abiword. Do you have a gnome interface on the same device that you can test abiword on gnome to see if that causes problems. Also what sort of device is it? What screen resolution and what graphics card.

[sdz]

Replying to pbrobinson:

This is working fine for me on today's rawhide (March 22nd) on an eeePC 901

Oh, it is? I'll have to double-check that. Maybe there's something wrong with what we do for SoaS.

It seems more like a screen/X layout issue with sugar than something with write/abiword. Do you have a gnome interface on the same device that you can test abiword on gnome to see if that causes problems. Also what sort of device is it? What screen resolution and what graphics card.

I can reproduce it with the current nightly builds (or at least these a couple of days ago, need to retry), but the original reporter's machines are the netbooks you recommended. :)

[pbrobinson]

I can reproduce it with the current nightly builds (or at least these a couple of days ago, need to retry), but the original reporter's machines are the netbooks you recommended. :)

OK, cool. So its Intel Pinetrail chipset so that shouldn't be an issue. It might well be a missing dependency then. Do you have a link to the exactly daily you tested and I'll grab a copy a have a play.

[sdz]

Alright, so we narrowed this down. Could you please execute as root the following command?

yum groupremove input-methods

That should do the trick and render Write working again. This issue will also not be present in the final release of Sugar on a Stick. Let me know how it goes!

[mkim]

Yep, that fixed it. We're all good. =)

[dnarvaez]

Milestone Mirabelle deleted