Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=488675 --- Comment #12 from Akira TAGOH <[email protected]> 2009-03-09 10:51:25 EDT --- Thank you for testing. (In reply to comment #11) > Though it's strange to me that fontforge worked well until the impact of > libgxim-0.3.2-3.fc10.i386. I should do check a reproducibility on -1.fc10 first but I didn't do that but just confirmed a issue on new one. so just reverted now. but I still see this issue with even old libgxim. if you can still see fontforge working back by downgrading libgxim, please try: % killall imsettings-applet % LIBGXIM_DEBUG=all imsettings-applet --disable-xsettings and run fontforge on other terminal say. I guess any keyevents isn't sending through imsettings-applet then. > But fontforge still doesn't work and I have to issue: > > [m...@ex ~]$ gconftool-2 -t bool -s /apps/imsettings-applet/sync_on_forward > true > > After that fontforge works well: > > [m...@ex ~]$ fontforge test.sfd & > > Though there's no obvious change: > > [m...@ex ~]$ gconftool-2 --get /apps/imsettings-applet/sync_on_forward > true > [m...@ex ~]$ > > The deal is quite tricky. Okay. let me have a look at that. and probably push the updates with other fixes as well. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Fedora-fonts-bugs-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
