Summary: | kicker crashes when I logout, reboot or shutdown | ||
---|---|---|---|
Product: | [Plasma] kicker | Reporter: | Carter Baltimore <carterbaltimore> |
Component: | general | Assignee: | Aaron J. Seigo <aseigo> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Carter Baltimore
2005-10-11 02:22:11 UTC
as you can see here: #15 0x41bae3a5 in QXIMInputContext::setHolderWidget () from /usr/lib/qt3/plugins/inputmethods/libqxim.so this crash is in libqxim, which is a multi-byte character input mechanism lib. this problem is known and AFAIK is either fixed or being fixed. in any case, it's not a problem with kde itself nor one we can fix. thanks for reporting, however. Thanks, Aaron. If it's fixed, is there anything I can do about it? Upgrade, etc.? --- "Aaron J.Seigo" <aseigo@kde.org> wrote: [bugs.kde.org quoted mail] ---------------------------------------------------------------------------- > Status|UNCONFIRMED > |RESOLVED > Resolution| > |INVALID > > > > ------- Additional Comments From aseigo kde org > 2005-10-11 02:28 ------- > as you can see here: > > #15 0x41bae3a5 in QXIMInputContext::setHolderWidget > () > from > /usr/lib/qt3/plugins/inputmethods/libqxim.so > > this crash is in libqxim, which is a multi-byte > character input mechanism lib. this problem is known > and AFAIK is either fixed or being fixed. in any > case, it's not a problem with kde itself nor one we > can fix. > > thanks for reporting, however. > __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com Re: "not a problem with kde itself" Perhaps not but the problem mysteriously went away when I deleted my .kde directory and reconfigured my kde desktop again from scratch. Have to wonder how many others with this problem UPGRADED as opposed to installed from scratch... the trick is to not use the XIM support. which is why it affects those who upgrade (XIM was enabled previously but there were no problems, now there is) I'm using Gentoo x86 with KDE 3.5 and I get the following error every time I logout, shutdown or reboot from KDE: Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 11932)] 0x459aa2a8 in waitpid () from /lib/libpthread.so.0 #0 0x459aa2a8 in waitpid () from /lib/libpthread.so.0 #1 0xb7920240 in ?? () from /usr/kde/3.5/lib/libkdecore.so.4 #2 0xb783652e in KCrash::defaultCrashHandler(int) () from /usr/kde/3.5/lib/libkdecore.so.4 #3 0xbffcf7e0 in ?? () #4 0xbffcfc30 in ?? () #5 0x00000001 in ?? () #6 0x459a440f in pthread_mutex_unlock () from /lib/libpthread.so.0 |