[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#343313: libstdc++6: upgrade breaks existing applications with scim 1.0.2-3



Package: libstdc++6
Version: 4.0.2-5
Severity: important


Upgrading libstdc++6 from 4.0.2-2 to 4.0.2-5 causes crashes in various
gtk programs when GTK_IM_MODULE=scim is in the environment.

I have the following scim-related packages:

ii  scim                   1.0.2-3        Smart Common Input Method platform
ii  scim-config-socket     1.0.2-3        Socket configure module for SCIM
ii  scim-frontend-socket   1.0.2-3        Socket front end module for SCIM
ii  scim-gtk2-immodule     1.0.2-3        GTK2 IMModule with SCIM as backend
ii  scim-server-socket     1.0.2-3        Socket IM engine module for SCIM

With libstdc++6 4.0.2-5 installed:

  $ GTK_IM_MODULE=scim gedit
  *** glibc detected *** malloc(): memory corruption: 0x0822f3b8 ***

  $ GTK_IM_MODULE=scim inkscape
  Launching a SCIM daemon with Socket FrontEnd...
  *** glibc detected *** corrupted double-linked list: 0x089562e8 ***

  Emergency save activated!
  ...

galeon doesn't exactly crash, but goes into sleep state before showing
its main window.

These programs appear to work fine when GTK_IM_MODULE is unset or if
I downgrade to libstdc++6 4.0.2-2 or if I upgrade scim to 1.4.2-1.

Thus, without really understanding the problem, I suggest that
libstdc++6 Conflict with scim (<< 1.4.2-1).


scim bug report #342198 may be related.


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.4.27-2-686-smp
Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

Versions of packages libstdc++6 depends on:
ii  gcc-4.0-base                  4.0.2-5    The GNU Compiler Collection (base 
ii  libc6                         2.3.5-8    GNU C Library: Shared libraries an
ii  libgcc1                       1:4.0.2-5  GCC support library

libstdc++6 recommends no packages.

-- no debconf information



Reply to: