Your message dated Thu, 3 Apr 2008 23:16:53 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#473663: Always crash when starting w/gdm,gnome 
2.[20|22].
has caused the Debian Bug report #473663,
regarding Always crash when starting w/gdm,gnome 2.[20|22].
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
473663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473663
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: scim
Version: 1.4.7-3
Severity: important
File: /usr/lib/scim-1.0/scim-launcher

When I starting gnome from gdm,alwais scim is crashed firstly...
I always using anthy or anthy-uim as kana-kanji conversion engine.
If you want more information,pls. guide packages me to install 
or report settings.
 
Now,See below crash information.

Regards,
Ohta.
---
scim: Invalid memory reference 


*** Please describe what you were doing when the application crashed ***

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x00002b74f9bbbbb5 in waitpid () from /lib/libc.so.6
#0  0x00002b74f9bbbbb5 in waitpid () from /lib/libc.so.6
#1  0x00002b74f8c2bc49 in ?? () from /usr/lib/debreaper/libviaticum.so
#2  <signal handler called>
#3  0x00002b75003d1c84 in ?? ()
#4  0x00002b74f944879c in ?? () from /usr/lib/libstdc++.so.6
#5  0x00002b74f90ed124 in scim::FrontEndModule::load ()
   from /usr/lib/libscim-1.0.so.8
#6  0x00002b74f90ed1c4 in scim::FrontEndModule::FrontEndModule ()
   from /usr/lib/libscim-1.0.so.8
#7  0x00000000004036cf in ?? ()
#8  0x00002b74f9b431c4 in __libc_start_main () from /lib/libc.so.6
#9  0x0000000000401729 in ?? ()
#10 0x00007fffb20977b8 in ?? ()
#11 0x0000000000000000 in ?? ()

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (90, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24.4-amd64-gcc431 (SMP w/2 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages scim depends on:
ii  libatk1.0-0                   1.22.0-1   The ATK accessibility toolkit
ii  libc6                         2.7-10     GNU C Library: Shared libraries
ii  libcairo2                     1.5.8-1    The Cairo 2D vector graphics libra
ii  libgcc1                       1:4.3.0-2  GCC support library
ii  libglib2.0-0                  2.16.1-2   The GLib library of C routines
ii  libgtk2.0-0                   2.12.9-2   The GTK+ graphical user interface 
ii  libpango1.0-0                 1.20.0-1   Layout and rendering of internatio
ii  libscim8c2a                   1.4.7-3    library for SCIM platform
ii  libstdc++6                    4.3.0-2    The GNU Standard C++ Library v3
ii  libx11-6                      2:1.1.4-1  X11 client-side library

Versions of packages scim recommends:
ii  im-switch                     1.16       Input method switch framework
ii  scim-gtk2-immodule            1.4.7-3    GTK+2 input method module with SCI




--- End Message ---
--- Begin Message ---
Hi,
On Thu, Apr 03, 2008 at 12:00:13AM +0900, K.Ohta wrote:
> Simple ansewr is "NO".
...
> GTK_IM_MODULE="scim" ; export GTK_IM_MODULE
> GTK_IM_SCIM_CONFIG_MODULE=simple
> scim -d
....

Let's discuss why it crash.

(Your configuration plan can be made to work but I am not in the mood to
go through the hussle.  I just use im-switch and we support that because
it takes care all the hussle for you.)

As documented in README.GTK, using GTK_IM_MODULE="scim" comes with
risks.  You are experiencing this risk.  You are in unstable where this
kind of library issue exists.  We recommend not to configure as you did.

In conclusion, this is your configuration problem.  Please read all the
accompanied document.

Thanks,

Osamu



--- End Message ---

Reply via email to