Comment 13 for bug 80551

Update on this problem from my end:
I did a clean install (eliminating my Windows partition; I was dual-booting)
of Feisty 32-bit when it was released, and followed the SCIM instructions
outlined in the community documentation at
https://help.ubuntu.com/community/SCIM. I believe I set up my Feisty beta
install with instructions I had used previously from
http://www.mrbass.org/linux/ubuntu/scim/. After configuring the fresh
install in this way, I have had no problems and everything in my system
works great. Happy, happy, happy! Joy, joy, joy!

Maybe the community documentation is a good workaround. I know there are
many different instructions floating around for people trying to use SCIM,
especially for CJK input. Those instructions may often times 'work', but
introduce conflicts later on with other scripts you set up (in my case, I
put together a couple of scripts to enable Beryl; when I removed those, I
was no longer able to use OOo). The community doc is a simple, elegant,
non-scripted solution, and now SCIM works in every application (with the
mrbass.org solution, SCIM did not work for KDE apps such as BibleTime or
Amarok). My two cents, for what it's worth.

On 5/16/07, Ming Hua <email address hidden> wrote:
>
> On Tue, May 15, 2007 at 09:24:53AM -0000, Alexander Hunziker wrote:
> >
> > So far, the easiest workaround that I have found is to call the
> > applications with the environment variable GTK_IM_MODULE set to "xim".
>
> Another thing worth testing is to set GTK_IM_MODULE to "scim-bridge".
> You need to have related packages installed though, I believe
> scim-bridge-client-gtk (and maybe scim-bridge-agent).
>
> > In the case for OpenOffice, it's very easy to change the startup script
> > (/usr/bin/ooffice) - just add "GTK_IM_MODULE=xim " in front of the last
> > line. For applications like f-spot or Gizmo Project that also suffer
> > from this bug, one can create a startup script that changes the variable
> > before launching the program.
>
> This is very curious. My understanding about Gizmo is that it's a
> close source application which uses GTK. So the problem of using
> GTK_IM_MODULE=scim crashes gizmo should be bug #2246, the weak symbol
> conflict between libstdc++5 and libstdc++6. There is even a bug
> reported for this, bug #35290, but I couldn't get more information from
> the original reporter.
>
> Does OpenOffice and F-spot by any means use libstdc++5? I am assuming
> you are talking about the openoffice.org and f-spot packages in Ubuntu
> here, instead of the binaries downloaded from http://www.openoffice.org/,
> for example.
>
> Ming
> 2007.05.15
>
> --
> openoffice fails to start if scim is the default GTK_IM_MODULE
> https://bugs.launchpad.net/bugs/80551
> You received this bug notification because you are a direct subscriber
> of the bug.
>