the backtrace is useless. can you please attach your kickerrc to the bug report? thank you.

Oh yeah. I completely forgot to mention in my bug report that my kicker is a little odd.  I use the menubar and kxdocker.  So, I reduced the size of kicker to 1%, stripped everything out of it and set it to autohide behind the menubar.  That way it is out of the way so I can use kxdocker.  I don't think that has anything to do with the crash though because to KDE it is just a kicker with no applets.  Here is my kickerrc:

[$Version]
update_info=kickerrc.upd:kde_3_1_sizeChanges,kickerrc.upd:kde_3_4_reverseLayout,kickerrc.upd:kde_3_5_kconfigXTize

[AddAppletDialog Settings]
Height 768=446
Width 1024=491

[Applet_1]
ConfigFile=media_panelapplet_nofflimgjyrgza7jdx3n_rc
DesktopFile=mediaapplet.desktop
FreeSpace2=0.00899281
WidthForHeightHint=10

[Applet_2]
ConfigFile=media_panelapplet_lwjh2vm1voxqzfskjso5_rc
DesktopFile=mediaapplet.desktop
FreeSpace2=0.239209
WidthForHeightHint=10

[Applet_3]
ConfigFile=media_panelapplet_ymyum3a8yjn0o90hvx7t_rc
DesktopFile=mediaapplet.desktop
FreeSpace2=0.302158
WidthForHeightHint=10

[Applet_4]
ConfigFile=taskbar_panelapplet_ooxipyonpcoejmjfjpg1_rc
DesktopFile=taskbarapplet.desktop
FreeSpace2=0.00899281
WidthForHeightHint=210

[Colors]
CurrentPalette=

[Extension_1]
ConfigFile=childpanel_panelextension_irmydl34lp99b55lnfs3_rc
DesktopFile=childpanelextension.desktop
UserHidden=0

[General]
Alignment=1
Applets=KMenuButton_1,ServiceButton_2,ServiceButton_1,ServiceButton_3,ServiceButton_4,ServiceButton_5,Applet_4,Applet_2,Applet_1
Applets2=
AutoHideDelay=0
AutoHidePanel=true
AutoHideSwitch=false
BackgroundHide=false
BackgroundTheme=/usr/share/apps/kicker/wallpapers/default.png
ColorizeBackground=true
CustomSize=38
ExpandSize=false
Extensions2=
FadeOutAppletHandles=true
HideAnimation=false
HideAnimationSpeed=90
HideAppletHandles=false
HideButtonSize=14
IExist=true
Panels=MainPanel
Position=2
ResizeableHandle=false
ShowLeftHideButton=false
ShowRightHideButton=false
ShowToolTips=true
Size=0
SizePercentage=1
TintColor=78,78,78
TintValue=0
Transparent=false
UnhideLocation=2
UseBackgroundTheme=true
XineramaScreen=0

[HTML Settings]
AutomaticDetectionLanguage=0

[KFileDialog Settings]
Automatic Preview=true
Autoplay sounds=true
Recent Files=/usr/share/apps/kicker/wallpapers/default.png,/opt/kde3/share/apps/kicker/pics/disk8.png,/opt/kde3/share/apps/kicker/pics/disk9.png,/opt/kde3/share/apps/kicker/pics/kside.png,/opt/kde3/share/apps/kicker/pics/kside_tile.png,/opt/kde3/share/apps/kicker/pics/disk10.png,$HOME/Desktop/transparent,$HOME/Desktop/transparent.png,/opt/kde3/share/icons/crystalsvg/48x48/apps/amarok.png,/opt/kde3/share/icons/hicolor/48x48/apps/kdevdesigner.png,$HOME/.icons/safari2.png,$HOME/.icons/mac2.png,$HOME/.cxoffice/dotwine/fake_windows/Windows/Icons/ace1_newshortcut3_35afd495ec2e4b2bb9db30eebc74049d.0.xpm,$HOME/.icons/terminal.png,$HOME/.icons/safari.png,$HOME/.icons/mac.png

[KMenu]
UseSidePixmap=false

[Main Panel]
ConfigFile=kickerrc
DesktopFile=childpanelextension.desktop
UserHidden=0

[Menubar Panel]
ConfigFile=kicker_menubarpanelrc
DesktopFile=childpanelextension.desktop
UserHidden=0

[button_tiles]
EnableBrowserTiles=false
EnableDesktopButtonTiles=false
EnableExeTiles=false
EnableKMenuTiles=false
EnableURLTiles=false
EnableWindowListTiles=false

[buttons]
EnableIconZoom=true
EnableTileBackground=false

[menus]
DetailedEntriesNamesFirst=false
DetailedMenuEntries=true
Extensions=
MaxEntries2=30
MenuEntryFormat=DescriptionAndName
RecentAppsStat=17 1127588503 /usr/share/applications/mozilla-firefox.desktop,13 1127445817 /usr/share/applications/kde/kdf.desktop,13 1127440195 /usr/share/applications/kde/kuser.desktop,11 1125932485 /usr/share/applications/kde/juk.desktop,4 1125720057 /usr/share/applications/autopackage-manager-gtk.desktop,4 1127239042 Windows_Applications/Programs/Internet_Explorer.desktop,3 1125541970 /home/carl/.local/share/applications/sax2.desktop,2 1125683896 /home/carl/.local/share/applications/Kontact.desktop,2 1127334592 klik/klik.desktop,2 1127345741 /usr/share/applications/kde/kcalc.desktop,2 1127058924 /usr/share/applications/kde/konqbrowser.desktop,1 1123434422 /home/carl/.local/share/applications/Software Manager.desktop,1 1125540789 /home/carl/.local/share/applications/kde-k3b.desktop,1 1125542000 /usr/share/applications/kde/kaudiocreator.desktop,1 1125530179 /home/carl/.local/share/applications/SuperKaramba.desktop,1 1125499098 Multimedia/k3b.desktop,1 1127539555 Utilities/kxdocker.desktop,1 1125529713 /home/carl/.local/share/applications/Word.desktop,1 1127022049 klik/Smb4K.desktop,1 1126468439 Applications/Apollon.desktop,1 1123265554 /home/carl/.local/share/applications/Firefox.desktop,1 1123433422 /usr/share/applications/kde/kwikdisk.desktop,1 1125857217 /usr/share/applications/ooo2-writer.desktop,1 1125536970 /usr/share/applications/kde/kopete.desktop,1 1127439669 /usr/share/applications/kde/konsole.desktop,1 1125530328 /home/carl/.local/share/applications/kde-kaffeine.desktop
RecentVsOften=false
ShowHiddenFiles=false
ShowMenuTitles=true

Kicker also crashes often on logout here. I'm using kicker from todays KDE 3.5 SVN branch. Here is my backtrace:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912576367088 (LWP 12249)]
0x00002aaaae301e84 in waitpid () from /lib/libpthread.so.0
#0  0x00002aaaae301e84 in waitpid () from /lib/libpthread.so.0
#1  0x00002aaaabaf9851 in KCrash::defaultCrashHandler (sig=11)
    at /home/kdedev/src/kde/kdelibs/kdecore/kcrash.cpp:251
#2  0x00002aaaaeac6890 in killpg () from /lib/libc.so.6
#3  0x0000000000000000 in ?? ()
#4  0x0000000000000000 in ?? ()
#5  0x0000000000000000 in ?? ()
#6  0x00002aaa00000002 in ?? ()
#7  0x0000000000000000 in ?? ()
#8  0x00002aaaaf7329f0 in ?? ()
#9  0x696c7269646b2f6f in ?? ()
#10 0x0000000000000000 in ?? ()
#11 0x0000000000000246 in ?? ()
#12 0x0000000000000000 in ?? ()
#13 0x000000000082e438 in ?? ()
#14 0x00007ffffff37260 in ?? ()
#15 0x00000000008a5a68 in ?? ()
#16 0x0000000000000000 in ?? ()
#17 0x00000000008a5a68 in ?? ()
#18 0x00007ffffff370d0 in ?? ()
#19 0x00007ffffff372c0 in ?? ()
#20 0x0000000000000001 in ?? ()
#21 0x0000000000000000 in ?? ()
#22 0x0000000000000000 in ?? ()
#23 0x00007ffffff370d0 in ?? ()
#24 0x00002aaaacac8269 in QGList::findRef (this=0x0, d=0x8a5a68, 
    fromStart=true) at qglist.cpp:719
#25 0x00002aaaacac7df4 in QGList::removeRef (this=0x0, d=0x8a5a68)
    at qglist.cpp:553
#26 0x00002aaaaafa0b30 in KDirListerCache::forgetDirs (this=0x82e330, 
    lister=0x8a5a68, _url=@0x0, notify=false) at qptrlist.h:86
#27 0x00002aaaaafa169e in KDirListerCache::forgetDirs (this=0x82e330, 
    lister=0x8a5a68) at qvaluelist.h:110
#28 0x00002aaaaafa3922 in ~KDirLister (this=0x8a5a68)
    at /home/kdedev/src/kde/kdelibs/kio/kio/kdirlister.cpp:1795
#29 0x00002aaab1f42c05 in ~SystemMenu (this=0x8a5910) at qptrlist.h:70
#30 0x00002aaaacac822f in QGList::clear (this=0x8a55c0) at qglist.cpp:701
#31 0x00002aaaabb140e1 in ~KLibrary (this=0x8a5550) at qptrlist.h:93
#32 0x00002aaaabb14ef5 in KLibLoader::close_pending (this=0x81f9c0, 
    wrap=0x8a4110) at /home/kdedev/src/kde/kdelibs/kdecore/klibloader.cpp:516
#33 0x00002aaaabb163b1 in ~KLibLoader (this=0x81f9c0)
    at /home/kdedev/src/kde/kdelibs/kdecore/klibloader.cpp:328
#34 0x00002aaaabb12c38 in KLibLoader::cleanUp ()
    at /home/kdedev/src/kde/kdelibs/kdecore/klibloader.cpp:298
#35 0x00002aaaaba5451a in ~KApplication (this=0x675ad0)
    at /home/kdedev/src/kde/kdelibs/kdecore/kapplication.cpp:1610
#36 0x00002aaaabb1bb6a in ~KUniqueApplication (this=0x675ad0) at qptrlist.h:70
#37 0x00002aaaafdf563b in ~Kicker (this=0x675ad0)
    at /home/kdedev/src/kde/kdebase/kicker/kicker/core/kicker.cpp:156
#38 0x00002aaaafdf50c9 in kdemain (argc=1, argv=0x7ffffff37980)
    at /home/kdedev/src/kde/kdebase/kicker/kicker/core/main.cpp:146
#39 0x00000000004074ac in launch (argc=1, _name=0x6506d8 "kicker", 
    args=0x6506df "", cwd=0x0, envc=0, envs=0x6506e7 "", reset_env=false, 
    tty=0x0, avoid_loops=96, startup_id_str=0x40a0d2 "0")
    at /home/kdedev/src/kde/kdelibs/kinit/kinit.cpp:637
#40 0x0000000000407cdb in handle_launcher_request (sock=8)
    at /home/kdedev/src/kde/kdelibs/kinit/kinit.cpp:1201
#41 0x00000000004082d9 in handle_requests (waitForPid=0)
    at /home/kdedev/src/kde/kdelibs/kinit/kinit.cpp:1404
#42 0x0000000000408a20 in main (argc=2, argv=0x1, envp=0x7ffffff384e0)
    at /home/kdedev/src/kde/kdelibs/kinit/kinit.cpp:1848

I'll attach my kickerrc.

Created attachment 12694 [details]
My kickerrc

*** Bug 113844 has been marked as a duplicate of this bug. ***

3.4.2 also crashes here every time I logout on Fedora Core with kde-redhat RPMS :
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(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)
(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)
(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)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208990016 (LWP 6299)]
(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)
(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)
(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)
(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)
(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)
(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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#4  0x00b673f9 in _X11TransWrite () from /usr/X11R6/lib/libX11.so.6
#5  0x00b4c79b in _XError () from /usr/X11R6/lib/libX11.so.6
#6  0x00b4c8b6 in _XReply () from /usr/X11R6/lib/libX11.so.6
#7  0x00b3560a in _XGetWindowAttributes () from /usr/X11R6/lib/libX11.so.6
#8  0x00b35764 in XGetWindowAttributes () from /usr/X11R6/lib/libX11.so.6
#9  0x0053d4a1 in _XimLocalSetICValues ()
   from /usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2
#10 0x0053e235 in _XimSetICDefaults ()
   from /usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2
#11 0x0053e2cb in _XimSetICDefaults ()
   from /usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2
#12 0x0053b2db in _XimLocalCreateIC ()
   from /usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2
#13 0x00b6425a in XCreateIC () from /usr/X11R6/lib/libX11.so.6
#14 0x0018e653 in QXIMInputContext::setHolderWidget ()
   from /usr/lib/qt-3.3/plugins/inputmethods/libqxim.so
#15 0x06e38d40 in QInputContextFactory::create ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#16 0x00181ed5 in QMultiInputContext::changeInputMethod ()
   from /usr/lib/qt-3.3/plugins/inputmethods/libqimsw-multi.so
#17 0x00182086 in QMultiInputContext::slave ()
   from /usr/lib/qt-3.3/plugins/inputmethods/libqimsw-multi.so
#18 0x00182321 in QMultiInputContext::setHolderWidget ()
   from /usr/lib/qt-3.3/plugins/inputmethods/libqimsw-multi.so
#19 0x06e38d40 in QInputContextFactory::create ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#20 0x06b9a9c6 in QWidget::createInputContext ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#21 0x06b9ab22 in QWidget::unfocusInputContext ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#22 0x06c7604d in QWidget::clearFocus ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#23 0x06c784b0 in QWidget::~QWidget$base ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#24 0x06d4e607 in QPopupMenu::~QPopupMenu$base ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#25 0x0767171b in KPopupMenu::~KPopupMenu$base () from /usr/lib/libkdeui.so.4
#26 0x07672963 in KPanelMenu::~KPanelMenu$base () from /usr/lib/libkdeui.so.4
#27 0x0033495a in PanelServiceMenu::~PanelServiceMenu$base ()
   from /usr/lib/libkdeinit_kicker.so
#28 0x00334a38 in PanelKMenu::~PanelKMenu$delete ()
   from /usr/lib/libkdeinit_kicker.so
#29 0x002fbb2b in MenuManager::~MenuManager$delete ()
   from /usr/lib/libkdeinit_kicker.so
#30 0x06c3c6ec in QObject::~QObject$base ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#31 0x06bdc735 in QApplication::~QApplication$base ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#32 0x073d12b8 in KApplication::~KApplication$base ()
   from /usr/lib/libkdecore.so.4
#33 0x073d1461 in KUniqueApplication::~KUniqueApplication$base ()
   from /usr/lib/libkdecore.so.4
#34 0x002edec6 in Kicker::~Kicker () from /usr/lib/libkdeinit_kicker.so
#35 0x00306b45 in kdemain () from /usr/lib/libkdeinit_kicker.so
#36 0x009bed5f in __libc_start_main () from /lib/libc.so.6
#37 0x0804854d in ?? ()

alexis: your problem is completely unrelated. The crash happens inside libqxim and that's a known problem. Don't use it.

*** Bug 113868 has been marked as a duplicate of this bug. ***

*** Bug 112836 has been marked as a duplicate of this bug. ***

*** Bug 114674 has been marked as a duplicate of this bug. ***

Thiago,
   I get a similar traceback to the one alexis posted.  You said the
problem is in libqxim and don't use it.  Could you please explain?
(libqxim seems to be part of QT which is not optional :-).
Thanks.

libqxim is not part of Qt

*** Bug 114299 has been marked as a duplicate of this bug. ***

That comment was of NO help.  On my system libqxim is packaged with QT.
Again, how do I avoid using this library?  Is there some option used
at build time?

$ rpm -qif /usr/lib/qt-3.3/plugins/inputmethods/libqxim.so
Name        : qt                           Relocations: /usr/lib/qt-3.3
Version     : 3.3.4                             Vendor: The KDE-RedHat Project

I and others have had to deal with this bug since June.  Aaron keeps closing
out the bug saying it is fixed, but it is not fixed.

libqxim is not part of Qt3 as released by Trolltech. If your distribution patches it in, you have to talk to them to remove it or fix it: it is known to cause crashes. Therefore, it's interfering with us getting a proper backtrace of the problem at hand.

Kindly remove it before submitting a backtrace (I don't care if you have to rebuild Qt from sources on your own).

Also, this bug has never been marked as fixed. We're still trying to understand the bug.

*** Bug 115239 has been marked as a duplicate of this bug. ***

SVN commit 479280 by aseigo:

in kicker when we have items in the menu that use dirlister, they get
deleted at a point when the dirlister has had its holders removed so
calls to forgetDirs fail. so instead of using ASSERTS we just check for
the pointers instead of assert()ing them and voila! the kdirlister crash is gone! huzzah!
BUG:113242


 M  +7 -5      kdirlister.cpp  


--- branches/KDE/3.5/kdelibs/kio/kio/kdirlister.cpp #479279:479280
@@ -415,8 +415,11 @@
   url.adjustPath( -1 );
   QString urlStr = url.url();
   QPtrList<KDirLister> *holders = urlsCurrentlyHeld[urlStr];
-  Q_ASSERT( holders );
-  holders->removeRef( lister );
+  //Q_ASSERT( holders );
+  if ( holders )
+  {
+    holders->removeRef( lister );
+  }
 
   // remove the dir from lister->d->lstDirs so that it doesn't contain things
   // that itemsInUse doesn't. When emitting the canceled signals lstDirs must
@@ -425,9 +428,8 @@
   lister->d->lstDirs.remove( lister->d->lstDirs.find( url ) );
 
   DirItem *item = itemsInUse[urlStr];
-  Q_ASSERT( item );
 
-  if ( holders->isEmpty() )
+  if ( holders && holders->isEmpty() )
   {
     urlsCurrentlyHeld.remove( urlStr ); // this deletes the (empty) holders list
     if ( !urlsCurrentlyListed[urlStr] )
@@ -454,7 +456,7 @@
       if ( notify )
         emit lister->clear( url );
 
-      if ( item->complete )
+      if ( item && item->complete )
       {
         kdDebug(7004) << k_funcinfo << lister << " item moved into cache: " << url << endl;
         itemsCached.insert( urlStr, item ); // TODO: may return false!!

Just found this while skimming through kde-commits:

> SVN commit 479280 by aseigo:
>
> in kicker when we have items in the menu that use dirlister, they get
> deleted at a point when the dirlister has had its holders removed so
> calls to forgetDirs fail.

Can you please explain a little better? You SHOULD NOT (!!) delete your items 
yourself, the KDirListerCache does it for you!

> so instead of using ASSERTS we just check for 
> the pointers instead of assert()ing them and voila! the kdirlister crash is
> gone! huzzah! BUG:113242

Why didn't you tell me about this and/or send me some debugging output?? The 
patch is completely wrong!!! And will break in cases that will be VERY hard 
to debug now. Don't you think there's a reason for an assert? Rule of thumb: 
*never* remove an assert in KDirListerCache, some might be redundant, but 
none of them is worng! (I didn't even see the patch on kde-core-devel?)

Basically what can happen now is that other KDirListers are still using the 
items of that directory and you delete it anyway. That will crash. An update 
might be running while you are removing the dir the update is running on 
without stopping the update -> crash. There's probably a lot more 
possibilities that can go wrong now, so please let's fix this correctly and 
revert this patch before KDE 3.5.

PS: the worst thing is that I only found out now, three days before my last 
but one diploma examination :-(

*** Bug 117440 has been marked as a duplicate of this bug. ***

Hmm, was hoping for some info, looks like everybody's looking too. I'm Using Linux 10.0, KDE 3.4.2 and experiencing the same crash.

Bill, the info you're looking for is that it is fixed in kde-3.5.0

hello.

    Ahh,... hey thanks. I think I'll try to break this down and see 
whats what.

    Thanks again.

Bill De Mar

Rex Dieter wrote:
[bugs.kde.org quoted mail]


___________________________________________________________
$0 Web Hosting with up to 200MB web space, 1000 MB Transfer
10 Personalized POP and Web E-mail Accounts, and much more.
Signup at www.doteasy.com

actually, the bad news is that it isn't in 3.5.0. someone reverted the fix at the last minute before 3.5.0 got tagged for what can only be described as highly dubious points. i'm highly unimpressed and apologize to all of you on behalf of kde. we'll have the fix in 3.5.1 however.

*sigh*

In analyzing my crashes, it appears that mine is somehow related to changing my resolution parameters, I'm still trying to track this down. Can't see any relationship at all, but... Anyway, my crashes have stopped. Will continue to look at it Thanks for all the info.

Bill De Mar

*** Bug 117823 has been marked as a duplicate of this bug. ***

*** Bug 117856 has been marked as a duplicate of this bug. ***

*** Bug 117879 has been marked as a duplicate of this bug. ***

*** Bug 118031 has been marked as a duplicate of this bug. ***

*** Bug 118099 has been marked as a duplicate of this bug. ***

*** Bug 118132 has been marked as a duplicate of this bug. ***

because it's been reintroduced in 3.5's svn and i dont' want this forgotten for 3.5.1

*** Bug 118657 has been marked as a duplicate of this bug. ***

*** Bug 106922 has been marked as a duplicate of this bug. ***

*** Bug 119127 has been marked as a duplicate of this bug. ***

this is fixed in svn for 3.5.1

*** Bug 119908 has been marked as a duplicate of this bug. ***

*** Bug 120047 has been marked as a duplicate of this bug. ***

Still crashes occasionnaly with KDE 3.5.1 and without XIM.
In fact, this is an abort() now that crashes (no more sig 11).
Appending crash dump. It is obviously crashing while freeing bad pointer (call from QFontDatabase::pointSizes ()).

Created attachment 14602 [details]
abort from free()

I forgot to tell the configuration:
Slackware 10.1 with current's glibc 2.3.6 built with NPTL support (in /lib/tls).
Qt 3.3.5 and KDE 3.5.1 built from source / GCC 3.4.5.

I too, am still having the "kicker crashes on logout"-problem, with KDE 3.5.1. Using SuSE 10.0, KDE 3.5.1 installed for SuSE rpms.

i get the same problem.
using suse 10.0, kde 3.5.1

I also get the logout crash with KDE 3.5.1 on Gentoo.

Same happen here, suse-10.1, updated to kde-3.5.1, kicker still crashes on logout.

I have the same problem, using:
Mandriva 2006
KDE 3.4

i have it too with debian sid and kde 3.51

Like it's already been noted by others, this bug definitely isn't gone in KDE 3.5.1.

I can confirm it happens much more consistently (when compared to KDE 3.5.0) in both SUSE 10.0 with KDE packages from SUPPLEMENTARY and Slackware-Current.

It stopped occurring on my system as of 3.5.1 with Kubuntu breezy.

I have the same problem with Debian/Testing and KDE 3.5.1

I have the same problem on Slackware/Current and KDE 3.5.1

Created attachment 14812 [details]
(maybe useless ) crash dump

I have the problem on two SUSE installations, which where upgraded from KDE 3.5
to 3.5.1 . There was no issue with the 3.5 SUSE Packages, but now there is. I
attached the crash dump, but I believe it's useless. Still I do not know how to
reproduce the behaviour...
Kind regards, Tom

Created attachment 14846 [details]
crash dump KDE 3.5.1 Suse 10.0

Sometimes crashes kicker, when I try to log out - this is the crash dump.

Created attachment 14894 [details]
kicker backtrace

still crashes. kde 3.5.1, SuSE 10.0, 2.6.13-15.8-smp

Olaf: this has been fixed in the suse qt3 package. 

@Dirk: I've allready installed the newest available version from suse:

$> rpm -q qt3
qt3-3.3.5-28

(installed from http://ftp.tu-chemnitz.de/pub/linux/suse/suse/i386/supplementary/KDE/update_for_10.0/base/)

I have the same problem on ArchLinux (current = pre- 0.7.2) KDE:3.5.1

WORKSFORME now ;)

Installed latest kdebase* (3.5.1-40) and qt3* (3.3.5-36) packages from
ftp://ftp.tu-chemnitz.de/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/update_for_10.0/

If the SUSE patch referred to in Commend #57 fixes the problem, is it safe to assume this can be included in a future bugfix to cover all releases, or should users of other distributions such as slackware go elsewhere for resolution? 

I see this is marked as *RESOLVED*, but being quite new here I fail to fully appreciate the solution to avoid the kicker crash on 1 out of 3 logouts..

Thanks!

I have the same problem with Mandriva 2007 and KDE 3.5.4 after upgrade to  qt3-3.3.6-18.2mdv2007.0

Current packet information of libqxim.so is:

rpm -qif /usr/lib/qt3/plugins/lib/inputmethods/libqxim.so
Name        : libqt3                       Relocations: (not relocatable)
Version     : 3.3.6                             Vendor: Mandriva
Release     : 18.2mdv2007.0                 Build Date: lun 02 abr 2007 15:29:17 CEST
Install Date: vie 06 abr 2007 08:06:38 CEST      Build Host: mercury.mandriva.com
Group       : System/Libraries              Source RPM: qt3-3.3.6-18.2mdv2007.0.src.rpm
Size        : 7870885                          License: GPL and QPL
Signature   : DSA/SHA1, mar 03 abr 2007 01:38:45 CEST, Key ID 9aa8d0d022458a98
Packager    : Mandriva Linux KDE Team <kde@mandriva.com>
URL         : http://www.trolltech.com
Summary     : Qt3 - Shared libraries

Best regards

Dear sir:

My SO is Mandriva 2007.0 with qt3-3.3.6.18.2mdv and KDE 3.5.4.

Please, I want reopen this bug. 

I have a very similar problem but I can't resolve it changing the name of libqxim.so file to libqxim.so.bak.

After last upgrade of Qt3 [Security Announce] [ MDKSA-2007:074 ] (Updated qt3 packages to address utf8 decoder bug), I have problems with Kicker when I try to shutdown my system. 

My system show a KDE error window and stops process (black screen with centered KDE error window). If I clic over the accept button, shutdown process finish normally. This is annoying indeed.

	There is the KDE backtrack, (but I think that may be useless for debugging purposes in that case):

(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its
symbols.
(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)
(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)
(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)
(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)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233148208 (LWP 6270)]
(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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb610b7a8 in TaskContainer::popupMenu () from /usr/lib/libtaskbar.so.1
#7  0xb6110f51 in TaskContainer::performAction ()
   from /usr/lib/libtaskbar.so.1
#8  0xb611a812 in TaskContainer::mousePressEvent ()
   from /usr/lib/libtaskbar.so.1
#9  0xb714a26e in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0xb70b5037 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0xb70b5ff9 in QApplication::notify () from
/usr/lib/qt3/lib/libqt-mt.so.3
#12 0xb77dc26a in KApplication::notify () from /usr/lib/libkdecore.so.4
#13 0xb7057719 in QETWidget::translateMouseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0xb7056696 in QApplication::x11ProcessEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0xb70666aa in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0xb70caa60 in QEventLoop::enterLoop () from
/usr/lib/qt3/lib/libqt-mt.so.3
#17 0xb70ca916 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0xb70b49ef in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0xb668e7d2 in kdemain () from /usr/lib/libkdeinit_kicker.so
#20 0xb7fa47c3 in kdeinitmain () from /usr/lib/kde3/kicker.so
#21 0x0804ee05 in ?? ()
#22 0x0804f732 in ?? ()
#23 0x0804faed in ?? ()
#24 0x080504d3 in ?? ()
#25 0xb681375c in __libc_start_main () from /lib/i686/libc.so.6
#26 0x0804baa1 in ?? ()

In my case, may be possible that this bug don't be related to file:

/usr/lib/qt3/plugins/lib/inputmethods/libqxim.so

I have moved libqxim.so to libqxim.so.bak but the error happens again. I haven't found enough information to evaluate or check another solution.

I would like to know a url or mail address, to send this bug to Mandriva
maintainers of this packet, but I don't know none.

Please, feel free if you need more information from me.

Best regards

It still crashes with kde 3.5.5 on gentoo

I'm using kde 3.5.8, kubuntu gutsy. 
I attempted to launch an application from the KDE panel, and kicker crashed.
It seems the same bug as Bug 61411. But that bug was marked RESOLVED and direct to this one.

Here is the backtrace:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(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)
(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)
(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)
(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)
(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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232754480 (LWP 5773)]
(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)
(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)
(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)
(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)
[KCrash handler]
#6  0xb4c5e894 in TaskContainer::updateKickerTip ()
   from /usr/lib/libtaskbar.so.1
#7  0xb6553f52 in KickerTip::display () from /usr/lib/libkickermain.so.1
#8  0xb65544cf in KickerTip::qt_invoke () from /usr/lib/libkickermain.so.1
#9  0xb726e893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#10 0xb726f338 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb75fc9b2 in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#12 0xb72965ba in QTimer::event () from /usr/lib/libqt-mt.so.3
#13 0xb7205af0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#14 0xb720791f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#15 0xb790dca2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#16 0xb7198209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#17 0xb71f853b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#18 0xb71acd49 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#19 0xb72201ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#20 0xb721ffde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#21 0xb7207699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#22 0xb665dd92 in kdemain () from /usr/lib/libkdeinit_kicker.so
#23 0xb66cc454 in kdeinitmain () from /usr/lib/kde3/kicker.so
#24 0x0804e67f in ?? ()
#25 0x00000001 in ?? ()
#26 0x0807acd8 in ?? ()
#27 0x00000001 in ?? ()
#28 0x00000000 in ?? ()

@sylecn Song:
your problem is not related to this issue, but it's bug #133386 - please check that one.