Write doesn't render properly in Fedora 13. I've tried a number of different steps to rule out certain components like using sugar 0.86.x from Fedora 12, compiling or using F-12 pygtk, pyabiword, libabiwork but the issue still occurs. Using the write in F-13 with F-12 works fine. The issue is that the main text window/canvas doesn't render to the proper area of the screen but instead is contained up in the toolbar area. The toolbar also doesn't seem to actively render properly. I don't think the problem is directly in write but possibly a regression in one of the dependant libraries. http://bugs.sugarlabs.org/ticket/1767 http://bugs.sugarlabs.org/ticket/1766
Marc: Can you possibly help shed some light on this issue?
Tomeu, would you have any idea about this one?
(In reply to comment #2) > Tomeu, would you have any idea about this one? Not really, it's not happening on abiword? What about the example script included in pyabiword?
I really doubt this is an AbiWord issue. The only think I could come up with is that we are hitting a bug in the GTK Client Side Windows code (or we do something that CSW does not expect).
(In reply to comment #4) > I really doubt this is an AbiWord issue. The only think I could come up with is > that we are hitting a bug in the GTK Client Side Windows code (or we do > something that CSW does not expect). Thanks for the update Marc. It was working fine in F-12 and isn't now in F-13. Is there a way we can debug this as I have no idea where to begin with it.
Matthias: Could this possibly be due to the GTK Client Side Windows changes?
OK, it seems its an issue with input methods. If you 'yum remove imsettings*' it all works. Any one know of associated changes that could have impacted this or should I reassign the bug?
IMO reassign the bug since something changed in the imsettings* code that resulted in the breakage. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Assigning over. :)
I don't have anything coming up with a problem beside imsettings for this. it doesn't involve with the rendering part at all. sure, the input methods may be related. so what the input method do you use? and how about other input method? given that it happens regardless of what input method you use, it may be the applications issue. otherwise the input method issue. Assigning back to sugar-write so far.
retarget for SOAS-4
problem seems to be fixed in F-14 so closing