search

google-code-export / imsettings

Automatically exported from code.google.com/p/imsettings
GNU Lesser General Public License v2.1
1 stars 0 forks source link

assertion appears after changing IM #19

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. set initial IM to kinput2 say
2. run gedit
3. change to none once and back again

What is the expected output? What do you see instead?
no assertion appears

Please use labels and text to provide additional information.

Original issue reported on code.google.com by akira.ta...@gmail.com on 11 Oct 2008 at 1:13

GoogleCodeExporter commented 9 years ago 
This appears when switching IM and the related instances are destroyed because 
of no
reference. in the above case, the instance was going to be destroyed when 
switching
xim to other immodule and back to xim again. basically xim backend assumes 
keeping
its instance until applications is closed. so it's implementation bug.

Original comment by akira.ta...@gmail.com on 11 Oct 2008 at 1:47

GoogleCodeExporter commented 9 years ago 
should be fixed in r207

Original comment by akira.ta...@gmail.com on 12 Oct 2008 at 7:29