Bug 578762

Summary:	imsettings breaks sugar-write in F13
Product:	[Fedora] Fedora	Reporter:	Peter Robinson <pbrobinson>
Component:	sugar-write	Assignee:	Steven M. Parrish <smparrish>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	medium
Version:	13	CC:	i18n-bugs, mail, mclasen, mpg, pbrobinson, sebastian, smparrish, tagoh, tomeu, uwog
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-10-10 21:48:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	601827

Description Peter Robinson 2010-04-01 09:57:09 UTC

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

Comment 1 Peter Robinson 2010-04-01 10:00:35 UTC

Marc: Can you possibly help shed some light on this issue?

Comment 2 Peter Robinson 2010-04-13 13:43:48 UTC

Tomeu, would you have any idea about this one?

Comment 3 Tomeu Vizoso 2010-04-13 16:09:21 UTC

(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?

Comment 4 Marc Maurer 2010-04-16 13:00:06 UTC

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).

Comment 5 Peter Robinson 2010-04-16 13:10:23 UTC

(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.

Comment 6 Peter Robinson 2010-04-16 14:35:52 UTC

Matthias: Could this possibly be due to the GTK Client Side Windows changes?

Comment 7 Peter Robinson 2010-04-26 20:12:02 UTC

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?

Comment 8 Steven M. Parrish 2010-06-05 00:16:45 UTC

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

Comment 9 Sebastian Dziallas 2010-06-22 14:01:13 UTC

Assigning over. :)

Comment 10 Akira TAGOH 2010-06-24 05:45:09 UTC

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.

Comment 11 Peter Robinson 2010-07-07 21:15:01 UTC

retarget for SOAS-4

Comment 12 Peter Robinson 2010-10-10 21:48:10 UTC

problem seems to be fixed in F-14 so closing