Bug 105566 - scim-setup crashes when scim-canna is installed.
Summary: scim-setup crashes when scim-canna is installed.
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: X11 Applications (show other bugs)
Version: Beta 2
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Mike Fabian
QA Contact: Stefan Dirsch
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-18 14:58 UTC by Mike Fabian
Modified: 2005-08-19 19:28 UTC (History)
2 users (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Patch to fix scim-setup crash with scim-canna. (430 bytes, text/x-patch)
2005-08-19 07:53 UTC, Zhe Su
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Fabian 2005-08-18 14:58:06 UTC
mfabian@magellan:~$ sudo rpm -e scim-canna
mfabian@magellan:~$ scim-setup
<00000669>:scim_skk_imengine.cpp:147 > Create SKK Factory :
<00000670>:scim_skk_imengine.cpp:148 > Lang : ja_JP
<00000671>:scim_skk_imengine.cpp:149 > UUID : ec43125f-f9d3-4a77-8096-de3a35290ba9
mfabian@magellan:~$ sudo rpm -Uhv /work/CDs/all/full-x86_64/suse/*/scim-canna.rpm
Preparing...                ########################################### [100%]
   1:scim-canna             ########################################### [100%]
mfabian@magellan:~$ scim-setup
<00000677>:scim_skk_imengine.cpp:147 > Create SKK Factory :
<00000678>:scim_skk_imengine.cpp:148 > Lang : ja_JP
<00000679>:scim_skk_imengine.cpp:149 > UUID : ec43125f-f9d3-4a77-8096-de3a35290ba9
/usr/bin/scim-setup: line 32: 17735 セグメンテーション違反です               (core dumped) /usr/lib64/scim-1.0/scim-helper-launcher setup 8034d025-bdfc-4a10-86a4-82b9461b32b0 $*
mfabian@magellan:~$
Comment 1 Zhe Su 2005-08-19 07:53:58 UTC
Created attachment 46646 [details]
Patch to fix scim-setup crash with scim-canna.

Please apply this patch to scim-canna. I'll send this patch to upstream.
Comment 2 Mike Fabian 2005-08-19 19:28:12 UTC
I applied the patch and it appears to be fixed indeed.
Package submitted to STABLE, should show up in Beta3.
→ FIXED.