Bug 103004

Summary:	skim makes kde unusable
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Andreas Klein <asklein>
Component:	KDE	Assignee:	Mike Fabian <mfabian>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P5 - None	CC:	shinkichi.yamazaki, tiwai, vetter
Version:	Beta 1
Target Milestone:	---
Hardware:	Other
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	backtrace skim crash

Description Andreas Klein 2005-08-09 12:18:04 UTC

- install skim
- at the next login, you will see a kde crash handler due to skim crash
- now you can't start a console, konqueror,.... because they all crash
- you can't even save the backtrace, because the crash-handler crashes when
saving the crash!
- I managed to save the backtrace by copying it into a vi running in xterm

Comment 1 Andreas Klein 2005-08-09 12:18:32 UTC

Created attachment 45304 [details]
backtrace skim crash

Comment 2 Mike Fabian 2005-08-09 13:09:52 UTC

Yes, I can reproduce that as well on SuSE Linux 10.0 Beta1.

Comment 3 Mike Fabian 2005-08-09 13:11:28 UTC

I saw that after a default installation in Japanese.

When deleting the skim package with "rpm -e skim", it gets
even worse, then KDE doesn't even start anymore.

Comment 4 Mike Fabian 2005-08-09 16:30:25 UTC

Andreas, which architecture are you using? I guess i386, is that right?

Comment 5 Andreas Klein 2005-08-09 16:34:50 UTC

i386 at the moment. x86-64 will follow tomorrow.

Comment 6 Mike Fabian 2005-08-09 16:51:36 UTC

Finally I can reproduce the skim crash on my main workstation magellan
as well.

I do not need to start a KDE session to make skim crash, I can also
reproduce that while using my favorite windowmanager fvwm2.

When I kill all scim related processes and then start skim,
skim crashes as soon as I try to trigger the input somewhere.

Comment 7 Mike Fabian 2005-08-09 17:04:19 UTC

The crash does not happen when skim is compiled with "-g -O0".

Could this be the same problem we had with "--enable-debug"
in the scim-* packages?

skim also seems to use SCIM_DEBUG macros?

How to enable debug for skim?

First of all I try to apply the fix for the "--enable-debug" problem
to the main scim package from CVS HEAD now.

Comment 8 Zhe Su 2005-08-09 17:46:12 UTC

I confirmed that the skim crashing issue could be fixed on i386 by upgrading
scim to cvs head.
But on x86_64, skim still crash. Maybe skim should be recompiled against the new
scim. 

I'll test it later. I must go to sleep first :-)

Comment 9 Zhe Su 2005-08-10 04:03:25 UTC

Ok, I confirmed that this issue could be fixed by upgrading to scim cvs head, on
both i386 and x86_64 platforms.

I'll release scim 1.4.1 asap, you may upgrade our scim package to 1.4.1 if possible.

Comment 10 Zhe Su 2005-08-10 13:09:56 UTC

I just upload scim 1.4.1 source tarball to http://sf.net/projects/scim, please
upgrade to this version if possible. And please rebuild all packages which
depend on scim.

Comment 11 Mike Fabian 2005-08-10 13:25:52 UTC

I've already submitted scim-1.4.1 (build from a CVS checkout
of the scim_1_4_1 tag to STABLE and I am currently rebuilding
all scim related problems to make sure that this really fixes
the problem.

Comment 12 Mike Fabian 2005-08-17 12:40:38 UTC

I verified that this is fixed on SuSE Linux 10.0 Beta2.
Closing as FIXED.