No, that is a completely different bug. That bug only happens when you
use scim in an application linked to libstdc++5, such as the official
firefox binary from mozilla.org, or acroread from adobe.com.
That problem is reported in Ubuntu as well, for example bug #39026.
> it says:
> > This should be due to weak symbol conflicts between different versions of
> > libstdc++ libs.
> >
> > The workaround you suggest is probably the easiest one.
> > You could also try using scim-bridge's gtk immodule instead.
> >
> > If you don't do so already you may also want to try configuring your
> > scim build with --enable-ld-version-script, but this is not guaranteed
> > to fix such symbol conflicts.
As said, this option doesn't guarantee to fix symbol collision. And
Debian/Ubuntu doesn't use it.
On Mon, Apr 30, 2007 at 07:04:30AM -0000, xbx wrote: sourceforge. net/tracker/ index.php? func=detail& aid=1618699& group_id= 108454& atid=650539
> in scim bug tracker, there is this similar looking bug:
> [ 1618699 ] Firefox does not start when GTK_IM_MODULE=scim
> http://
No, that is a completely different bug. That bug only happens when you
use scim in an application linked to libstdc++5, such as the official
firefox binary from mozilla.org, or acroread from adobe.com.
That problem is reported in Ubuntu as well, for example bug #39026.
> it says: ld-version- script, but this is not guaranteed
> > This should be due to weak symbol conflicts between different versions of
> > libstdc++ libs.
> >
> > The workaround you suggest is probably the easiest one.
> > You could also try using scim-bridge's gtk immodule instead.
> >
> > If you don't do so already you may also want to try configuring your
> > scim build with --enable-
> > to fix such symbol conflicts.
As said, this option doesn't guarantee to fix symbol collision. And
Debian/Ubuntu doesn't use it.
Ming
2007.05.09