Bug 106922 - kicker crash on session log off with signal 11 (SIGSEGV)
Summary: kicker crash on session log off with signal 11 (SIGSEGV)
Status: RESOLVED DUPLICATE of bug 113242
Alias: None
Product: kicker
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Aaron J. Seigo
URL:
Keywords:
: 106788 107490 107813 108282 110712 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-06-06 21:36 UTC by Juergen Wieczorek
Modified: 2013-03-07 00:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
kicker segfault log (6.08 KB, text/plain)
2005-07-12 02:29 UTC, Ricardo Garcia
Details
kicker crash file (3.39 KB, text/plain)
2005-08-17 08:00 UTC, Deni
Details
experiencing an equal problem on SUSE 10.0 with KDE 3.5.0. Backtrace. (6.76 KB, text/plain)
2006-03-27 14:07 UTC, baum-im-wald
Details
Kicker crash backtrace (494 bytes, application/x-gzip)
2006-05-14 12:13 UTC, Kristjan Ugrin
Details
Kicker crash backtrace (494 bytes, application/x-gzip)
2006-05-14 12:13 UTC, Kristjan Ugrin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Juergen Wieczorek 2005-06-06 21:36:29 UTC
Version:            (using KDE KDE 3.4.1)
Installed from:    Fedora RPMs
Compiler:          gcc-3.4 
OS:                Linux

System: Fedora Core 3 - kernel-2.6.11-1_27_FC3, KDE-3.4.1 (kdebase/kdelibs-3.4.1-1.0.fc3)

The kicker crashes with signal 11 upon session log off either from the KDE menu or from the respective applet in the kicker panel.
While choosing log off from the KDE menu reliably crashes the kicker (almost) every time, the crashes using the kicker applet are more infrequent (only abt. every 3rd or 4th time).
Killing the session with STRG-ALT+DEL appears to be unaffected.

Encl. see two different crash logs I was able to save:
+++quote
Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208092128 (LWP 6907)]
[KCrash handler]
#4  0x07459f85 in QGList::find () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#5  0x046a106d in KGlobal::registerStaticDeleter ()
   from /usr/lib/libkdecore.so.4
#6  0x04c4ddf7 in KDirWatch::self () from /usr/lib/libkio.so.4
#7  0x04c58093 in KShellCompletion::KShellCompletion ()
   from /usr/lib/libkio.so.4
#8  0x04c58150 in KShellCompletion::KShellCompletion ()
   from /usr/lib/libkio.so.4
#9  0x04c8f87b in KDirLister::stop () from /usr/lib/libkio.so.4
#10 0x04c8fae8 in KDirLister::~KDirLister () from /usr/lib/libkio.so.4
#11 0xb7bfa901 in init_kickermenu_systemmenu ()
   from /usr/lib/kde3/kickermenu_systemmenu.so
#12 0x0478520e in non-virtual thunk to KURLDrag::encodedData(char const*) const () from /usr/lib/libkdecore.so.4
#13 0x08272590 in ?? ()
#14 0x00000000 in ?? ()
unquote++

+++quote
Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1218516448 (LWP 5443)]
[KCrash handler]
#4  0x07459f85 in QGList::find () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#5  0xb771806d in KGlobal::registerStaticDeleter ()
   from /usr/lib/libkdecore.so.4
#6  0xb7cb7df7 in KDirWatch::self () from /usr/lib/libkio.so.4
#7  0xb7cc2093 in KShellCompletion::KShellCompletion ()
   from /usr/lib/libkio.so.4
#8  0xb7cc2150 in KShellCompletion::KShellCompletion ()
   from /usr/lib/libkio.so.4
#9  0xb7cf987b in KDirLister::stop () from /usr/lib/libkio.so.4
#10 0xb7cf9ae8 in KDirLister::~KDirLister () from /usr/lib/libkio.so.4
#11 0xb7209901 in init_kickermenu_systemmenu ()
   from /usr/lib/kde3/kickermenu_systemmenu.so
#12 0xb77fc20e in non-virtual thunk to KURLDrag::encodedData(char const*) const () from /usr/lib/libkdecore.so.4
#13 0x08285190 in ?? ()
#14 0x00000000 in ?? ()
unquote+++

This bugs seems not to be related to bug '104152, as neither 'dcopquit kicker', nor 'killall kicker' on the console yield any crash message.
I have tried both of them about a dozen times in a row without any undue effect.
Comment 1 S. Burmeister 2005-06-12 16:57:40 UTC
I can confirm this crash. I get the following log, which is different from the above:

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[KCrash handler]
#7  0x00000000 in ?? ()
#8  0x409caade in QPtrList<QPopupMenu>::deleteItem ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#9  0x40b40764 in QGList::clear () from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0x41805054 in PanelServiceMenu::~PanelServiceMenu ()
   from /opt/kde3/lib/libkdeinit_kicker.so
#11 0x4180a4c8 in PanelKMenu::~PanelKMenu ()
   from /opt/kde3/lib/libkdeinit_kicker.so
#12 0x417b9c99 in MenuManager::~MenuManager ()
   from /opt/kde3/lib/libkdeinit_kicker.so
#13 0x4087a869 in QObject::~QObject () from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x4081a48e in QApplication::~QApplication ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0x405038b9 in KApplication::~KApplication ()
   from /opt/kde3/lib/libkdecore.so.4
#16 0x40503b9d in KUniqueApplication::~KUniqueApplication ()
   from /opt/kde3/lib/libkdecore.so.4
#17 0x417daef7 in Kicker::~Kicker () from /opt/kde3/lib/libkdeinit_kicker.so
#18 0x417df18b in kdemain () from /opt/kde3/lib/libkdeinit_kicker.so
#19 0x40018554 in kdeinitmain () from /opt/kde3/lib/kde3/kicker.so
#20 0x0804e6f5 in launch ()
#21 0x0804ee0c in handle_launcher_request ()
#22 0x0804f3c9 in handle_requests ()
#23 0x0804fb9a in main ()
Comment 2 g1gsw 2005-06-16 00:08:09 UTC
I get this same problem on Gentoo Linux.
Comment 3 Aaron J. Seigo 2005-06-16 04:54:16 UTC
*** Bug 107490 has been marked as a duplicate of this bug. ***
Comment 4 Aaron J. Seigo 2005-06-16 04:54:37 UTC
*** Bug 106788 has been marked as a duplicate of this bug. ***
Comment 5 Travis Evans 2005-06-18 03:52:33 UTC
Same problem with KDE 3.4.1 (SuSE RPMs) on SuSE Linux 9.1.  The crash occurs approximately every second or third logout.  It seems to only happen if my KDE session has been running for a while (I'm not sure of that, though).  My backtrace looks virtually identical to that mentioned in Comment #1.
Comment 6 Thiago Macieira 2005-06-19 14:58:54 UTC
*** Bug 107714 has been marked as a duplicate of this bug. ***
Comment 7 Fabio Erculiani 2005-06-20 09:46:52 UTC
I have the same problem on two Gentoo Linux box, one 32bit Athlon64 and the other one 64bit Mobile Athlon64. Please fix it!
Comment 8 Aaron J. Seigo 2005-06-21 01:04:14 UTC
*** Bug 107813 has been marked as a duplicate of this bug. ***
Comment 9 Benjamin Duehring 2005-06-21 13:08:40 UTC
I have the same problem using Fedora Core 4 on a 64bit athlon64.
Seems that some running programs in the systray are the cause.
By closing the kmix applet the crashes were gone.
By re-enabling it I could reproduce the crashes again.
Comment 10 Pawel Stolowski 2005-06-25 11:03:01 UTC
I have this problem from at least previous version of kde, and now in 3.4.1 on Fedora Core 4. Removing kmixer applet helps. This is my output:

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[....]
[Thread debugging using libthread_db enabled]
[New Thread 1100004832 (LWP 9975)]
(no debugging symbols found)
[...]
[KCrash handler]
#4  0x00000000 in ?? ()
#5  0x400e3b6e in QPtrList<QPopupMenu>::deleteItem ()
   from /usr/lib/libkdeinit_kicker.so
#6  0x4111e44d in QGList::clear () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#7  0x400d1c29 in PanelServiceMenu::~PanelServiceMenu$base ()
   from /usr/lib/libkdeinit_kicker.so
#8  0x400d1d5b in PanelKMenu::~PanelKMenu$delete ()
   from /usr/lib/libkdeinit_kicker.so
#9  0x4009903b in MenuManager::~MenuManager$delete ()
   from /usr/lib/libkdeinit_kicker.so
#10 0x40e338bc in QObject::~QObject$base ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#11 0x40dd39a5 in QApplication::~QApplication$base ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#12 0x40a2d008 in KApplication::~KApplication$base ()
   from /usr/lib/libkdecore.so.4
#13 0x40a2d1b1 in KUniqueApplication::~KUniqueApplication$base ()
   from /usr/lib/libkdecore.so.4
#14 0x4008b336 in Kicker::~Kicker () from /usr/lib/libkdeinit_kicker.so
#15 0x400a4055 in kdemain () from /usr/lib/libkdeinit_kicker.so
#16 0x41630de6 in __libc_start_main () from /lib/libc.so.6
#17 0x0804854d in ?? ()
Comment 11 Juergen Wieczorek 2005-06-25 11:37:47 UTC
To avoid possible misunderstandings:

The above mentioned kicker crashes happen on my system right after a fresh KDE session login *without* the system tray applet being actived in the kicker panel, nor is kmix running in the background.

Juergen Wieczorek
Comment 12 Tomas 2005-06-28 17:58:54 UTC
I can confirm this bug too.
System Slackware 10.1
kicker Crash on logout, KDE 3.4.1
Comment 13 Aaron J. Seigo 2005-06-28 19:44:18 UTC
*** Bug 108282 has been marked as a duplicate of this bug. ***
Comment 14 Chama (Albert Oses) 2005-07-05 20:57:35 UTC
About this bug in some instances, when you log off from KDE in Fedora Core 4, 
just the kicker stays as log on and you can't completly log off from KDE nor 
use KDE as a complete system.

Albert (Chama).
Comment 15 Ricardo Garcia 2005-07-12 02:29:35 UTC
Created attachment 11768 [details]
kicker segfault log

This also happens to me in slackware-current using KDE 3.4.1. I have the
Klipper, KMix, KPPP and KMail system tray icons. Also the binary clock and
system monitor applets, the block/exit applet, the desktop paginator and some
icons that include the K menu, the show desktop button, the configuration
button and some other link folders.

Kernel 2.6.12.2, glibc 2.3.5 with NPTL, i686 machine...
Comment 16 Aaron J. Seigo 2005-07-12 12:21:41 UTC
SVN commit 433960 by aseigo:

don't crash on exit due to both the kmenu and klibloader trying to
delete menuexts
BUG:106922


 M  +14 -1     k_mnu.cpp  
 M  +2 -0      k_mnu.h  


--- branches/KDE/3.4/kdebase/kicker/ui/k_mnu.cpp #433959:433960
@@ -63,6 +63,7 @@
   , bookmarkMenu(0)
   , bookmarkOwner(0)
 {
+    dynamicSubMenus.setAutoDelete(true);
     // set the first client id to some arbitrarily large value.
     client_id = 10000;
     // Don't automatically clear the main menu.
@@ -75,6 +76,7 @@
 
 PanelKMenu::~PanelKMenu()
 {
+    slotClear();
     delete bookmarkMenu;
     delete bookmarkOwner;
 }
@@ -253,7 +255,7 @@
                 {
                     insertItem(info.name(), menu);
                 }
-                subMenus.append(menu);
+                dynamicSubMenus.append(menu);
                 need_separator = true;
             }
         }
@@ -393,6 +395,17 @@
     slotClear();
 }
 
+void PanelKMenu::slotClear()
+{
+    if (QApplication::closingDown())
+    {
+        return;
+    }
+
+    dynamicSubMenus.clear();
+    PanelServiceMenu::slotClear();
+}
+
 extern int kicker_screen_number;
 
 void PanelKMenu::slotLock()
--- branches/KDE/3.4/kdebase/kicker/ui/k_mnu.h #433959:433960
@@ -67,6 +67,7 @@
     void slotRunCommand();
     void slotEditUserContact();
     void paletteChanged();
+    virtual void slotClear();
 
 protected:
     QRect sideImageRect();
@@ -89,6 +90,7 @@
     KBookmarkMenu              *bookmarkMenu;
     KActionCollection          *actionCollection;
     KBookmarkOwner             *bookmarkOwner;
+    PopupMenuList               dynamicSubMenus;
 };
 
 #endif
Comment 17 Juergen Wieczorek 2005-08-02 18:47:06 UTC
Updated my KDE yesterday and found that his bug is NOT fixed in KDE 3.4.2.
IMHO the fixes are either too weak or incompletely/incorrectly implemented in KDE 3.4.2

My current system stats:
Fedora Core 3, kernel-2.6.12-1.1372_FC3, xorg-x11-6.8.2, qt-3.3.4

The update to 3.4.2 now RELIABLY crashes the kicker on session logoff from the K-menu EVERY time executed right after session login, with a similar backtrace log as below:

+++ quote
Using host libthread_db library "/lib/tls/libthread_db.so.1".
`shared object read from target memory' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1227409728 (LWP 5474)]
[KCrash handler]
#4  0xb72a4165 in QGList::find () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#5  0xb75a95ed in KGlobal::registerStaticDeleter ()
   from /usr/lib/libkdecore.so.4
#6  0xb7ba28c7 in KDirWatch::self () from /usr/lib/libkio.so.4
#7  0xb7bacb63 in KDirListerCache::KDirListerCache ()
   from /usr/lib/libkio.so.4
#8  0xb7bacc29 in KDirListerCache::self () from /usr/lib/libkio.so.4
#9  0xb7be4447 in KDirLister::stop () from /usr/lib/libkio.so.4
#10 0xb7be46b8 in KDirLister::~KDirLister () from /usr/lib/libkio.so.4
#11 0xb7f23c07 in SystemMenu::~SystemMenu ()
   from /usr/lib/kde3/kickermenu_systemmenu.so
#12 0xb7993e3e in QPtrList<QObject>::deleteItem () from /usr/lib/libkdeui.so.4
#13 0xb72a5284 in QGList::clear () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#14 0xb75a57ee in KLibrary::~KLibrary () from /usr/lib/libkdecore.so.4
#15 0xb75a5c8f in KLibLoader::close_pending () from /usr/lib/libkdecore.so.4
#16 0xb75ab960 in KLibLoader::~KLibLoader () from /usr/lib/libkdecore.so.4
#17 0xb75610aa in KLibLoader::cleanUp () from /usr/lib/libkdecore.so.4
#18 0xb76125cf in KApplication::~KApplication () from /usr/lib/libkdecore.so.4
#19 0xb7612a6e in KUniqueApplication::~KUniqueApplication ()
   from /usr/lib/libkdecore.so.4
#20 0xb7e9c491 in Kicker::~Kicker () from /usr/lib/libkdeinit_kicker.so
#21 0xb7eb86f6 in kdemain () from /usr/lib/libkdeinit_kicker.so
#22 0x080485e6 in ?? ()
#23 0x00000001 in ?? ()
#24 0xbfc284c4 in ?? ()
#25 0x080496cc in ?? ()
#26 0x4ff64ff4 in ?? () from /lib/tls/libc.so.6
#27 0x00000000 in ?? ()
unquote +++

Info:
The kicker system_tray applet is OFF.
The restore_previous_session option is also OFF.

For further reference here's my processes list after login:

UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  0 18:05 ?        00:00:01 init [5]                               
root         2     1  0 18:05 ?        00:00:00 [ksoftirqd/0]
root         3     1  0 18:05 ?        00:00:00 [events/0]
root         4     1  0 18:05 ?        00:00:00 [khelper]
root         5     1  0 18:05 ?        00:00:00 [kthread]
root         7     5  0 18:05 ?        00:00:00 [kacpid]
root        93     5  0 18:05 ?        00:00:00 [kblockd/0]
root        96     1  0 18:05 ?        00:00:00 [khubd]
root       139     5  0 18:05 ?        00:00:00 [pdflush]
root       140     5  0 18:05 ?        00:00:00 [pdflush]
root       142     5  0 18:05 ?        00:00:00 [aio/0]
root       141     1  0 18:05 ?        00:00:00 [kswapd0]
root       230     1  0 18:05 ?        00:00:00 [kseriod]
root       401     1  0 18:05 ?        00:00:00 [kjournald]
root      1363     1  0 18:05 ?        00:00:00 udevd
root      1732     1  0 18:05 ?        00:00:00 [kgameportd]
root      2496     1  0 18:06 ?        00:00:00 [kjournald]
root      2497     1  0 18:06 ?        00:00:00 [kjournald]
root      2498     1  0 18:06 ?        00:00:00 [kjournald]
root      2779     1  0 18:06 ?        00:00:00 /bin/bash /sbin/adsl-connect /etc/sysconfig/network-scripts/ifcfg-curr_provider
root      2833  2779  0 18:06 ?        00:00:00 /usr/sbin/pppd pty /usr/sbin/pppoe -p /var/run/pppoe-adsl.pid.pppoe -I eth0 -T 80 -U  -m 1412    ipparam curr_provider linkname ppp0 noipdefault noauth default-asyncmap defaultroute hide-password nodetach mtu 1492 mru 1492 noaccomp noccp nobsdcomp nodeflate nopcomp novj novjccomp user net94455525 lcp-echo-interval 20 lcp-echo-failure 3
root      2834  2833  0 18:06 ?        00:00:11 /usr/sbin/pppoe -p /var/run/pppoe-adsl.pid.pppoe -I eth0 -T 80 -U -m 1412
root      3073     1  0 18:06 ?        00:00:00 /usr/local/EPKowa/printer/ekpd
root      3084     1  0 18:06 ?        00:00:00 syslogd -m 0
root      3088     1  0 18:06 ?        00:00:00 klogd -x
root      3149     1  0 18:06 ?        00:00:00 /usr/sbin/smartd
root      3159     1  0 18:06 ?        00:00:00 /usr/sbin/acpid
root      3171     1  0 18:06 ?        00:00:00 cupsd
root      3332     1  0 18:06 ?        00:00:00 gpm -m /dev/input/mice -t imps2
root      3342     1  0 18:06 ?        00:00:00 crond
xfs       3374     1  0 18:06 ?        00:00:00 xfs -droppriv -daemon
root      3384     1  0 18:06 ?        00:00:00 anacron -s
root      3393     1  0 18:06 ?        00:00:00 /usr/sbin/atd
dbus      3412     1  0 18:06 ?        00:00:00 dbus-daemon-1 --system
root      3434     1  0 18:06 ?        00:00:00 cups-config-daemon
root      3445     1  0 18:06 ?        00:00:01 hald
root      3463     1  0 18:06 tty2     00:00:00 /sbin/mingetty tty2
root      3464     1  0 18:06 tty3     00:00:00 /sbin/mingetty tty3
root      3465     1  0 18:06 tty4     00:00:00 /sbin/mingetty tty4
root      3466     1  0 18:06 tty5     00:00:00 /sbin/mingetty tty5
root      3467     1  0 18:06 tty6     00:00:00 /sbin/mingetty tty6
curr_user  4180     1  0 18:06 ?        00:00:00 /usr/bin/ssh-agent -s
ntp       5177     1  0 18:44 ?        00:00:00 ntpd -u ntp:ntp -p /var/run/ntpd.pid
root      5188     1  0 18:45 ?        00:00:00 /usr/bin/spamd -d -c -m5 -H
root      5208  5188  0 18:45 ?        00:00:00 spamd child
root      5209  5188  0 18:45 ?        00:00:00 spamd child
root      5210  5188  0 18:45 ?        00:00:00 spamd child
root      5211  5188  0 18:45 ?        00:00:00 spamd child
root      5212  5188  0 18:45 ?        00:00:00 spamd child
root      5241     1  0 18:45 tty1     00:00:00 /sbin/mingetty tty1
root      5253     1  0 18:45 ?        00:00:00 kdm -nodaemon
root      5267  5253  2 18:45 ?        00:00:18 /usr/X11R6/bin/X :0 vt7 -auth /var/run/xauth/A:0-8d0AVv
curr_user  5326     1  0 18:45 ?        00:00:00 /usr/bin/ssh-agent -s
curr_user  5446     1  0 18:45 ?        00:00:00 /usr/libexec/gam_server
curr_user  5595     1  0 18:46 ?        00:00:00 /usr/bin/ssh-agent -s
curr_user  5841     1  0 18:47 ?        00:00:00 /usr/bin/ssh-agent -s
curr_user  6089     1  0 18:48 ?        00:00:00 /usr/bin/ssh-agent -s
curr_user  6303     1  0 18:48 ?        00:00:00 /usr/bin/ssh-agent -s
curr_user  6517     1  0 18:49 ?        00:00:00 /usr/bin/ssh-agent -s
curr_user  6731     1  0 18:49 ?        00:00:00 /usr/bin/ssh-agent -s
curr_user  6945     1  0 18:50 ?        00:00:00 /usr/bin/ssh-agent -s
curr_user  7159     1  0 18:50 ?        00:00:00 /usr/bin/ssh-agent -s
curr_user  7373     1  0 18:51 ?        00:00:00 /usr/bin/ssh-agent -s
curr_user  7587     1  0 18:51 ?        00:00:00 /usr/bin/ssh-agent -s
curr_user  7801     1  0 18:51 ?        00:00:00 /usr/bin/ssh-agent -s
curr_user  8015     1  0 18:52 ?        00:00:00 /usr/bin/ssh-agent -s
curr_user  8229     1  0 18:52 ?        00:00:00 /usr/bin/ssh-agent -s
curr_user  8443     1  0 18:53 ?        00:00:00 /usr/bin/ssh-agent -s
curr_user  8657     1  0 18:53 ?        00:00:00 /usr/bin/ssh-agent -s
curr_user  8892     1  0 18:54 ?        00:00:00 /usr/bin/ssh-agent -s
root      9119  5253  0 18:55 ?        00:00:00 -:0          
curr_user  9136  9119  0 18:56 ?        00:00:00 /bin/sh /usr/bin/startkde
curr_user  9157     1  0 18:56 ?        00:00:00 /usr/bin/ssh-agent -s
curr_user  9191     1  0 18:56 ?        00:00:00 dbus-daemon-1 --fork --print-pid 10 --print-address 8 --session
curr_user  9192     1  0 18:56 ?        00:00:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/startkde
curr_user  9267     1  0 18:56 ?        00:00:00 kdeinit Running...
curr_user  9270     1  0 18:56 ?        00:00:00 dcopserver --nosid
curr_user  9272  9267  0 18:56 ?        00:00:00 klauncher [kdeinit]
curr_user  9275     1  0 18:56 ?        00:00:00 kded
curr_user  9280     1  0 18:56 ?        00:00:00 kaccess
curr_user  9293  9267  0 18:56 ?        00:00:00 /usr/bin/artsd -F 10 -S 4096 -a alsa -s 30 -m artsmessage -c drkonqi -l 3 -f
curr_user  9294  9136  0 18:56 ?        00:00:00 kwrapper ksmserver
curr_user  9296     1  0 18:56 ?        00:00:00 ksmserver
curr_user  9297  9267  0 18:56 ?        00:00:00 kwin
curr_user  9300     1  0 18:56 ?        00:00:00 kdesktop
curr_user  9302     1  0 18:56 ?        00:00:00 kicker
curr_user  9304     1  0 18:56 ?        00:00:00 klipper
curr_user  9307     1  0 18:56 ?        00:00:00 kalarmd
curr_user  9308     1  0 18:56 ?        00:00:00 knotify [kdeinit]
curr_user  9310     1  0 18:56 ?        00:00:00 kio_uiserver
curr_user  9311  9267  0 18:56 ?        00:00:00 kio_file [kdeinit] file /tmp/ksocket-curr_user/klauncherWBF4Oa.slave-socket /tmp/ksocket-curr_user/kdesktopkZtPhc.slave-socket
curr_user  9312  9267  0 18:56 ?        00:00:00 kio_system [kdeinit] system /tmp/ksocket-curr_user/klauncherWBF4Oa.slave-socket /tmp/ksocket-curr_user/kickerrLu6Ca.slave-socket
curr_user  9313  9267  0 18:56 ?        00:00:00 kio_trash [kdeinit] trash /tmp/ksocket-curr_user/klauncherWBF4Oa.slave-socket /tmp/ksocket-curr_user/kickerZ2D1ac.slave-socket
curr_user  9314  9267  0 18:56 ?        00:00:00 kio_trash [kdeinit] trash /tmp/ksocket-curr_user/klauncherWBF4Oa.slave-socket /tmp/ksocket-curr_user/kio_system3xV8Hb.slave-socket
curr_user  9316  9267  0 18:56 ?        00:00:00 konsole --type shell
curr_user  9317  9316  0 18:56 pts/3    00:00:00 /bin/bash
curr_user  9335  9317  0 18:57 pts/3    00:00:00 ps -ef

The kicker crashes seem to be basically related to the logoff from the K-menu only like before, as I have tried the alternative logoff methods STRG+ALT+DEL and the kicker screenlock/logoff applet both 6-8 times in a row without any crashes.

Did some further exploration with runnings apps and found that ANY of the above mentioned logoff methods reliably crashes the kicker when either konqueror, kmail, or kate (checked only with these 3 apps) are running during logoff.

BUT strangely this only seems to happen if I invoke the apps via the K-menu!
If I start any of these apps using the command line equivalent ALT+F2, then logging off with STRG+ALT+DEL somehow appears unaffected, at least I could thus logoff 3 times in a row for each app without kicker crashes happening.
Maybe I was just lucky, but there seems to be a pattern to it.


Comment 18 Aaron J. Seigo 2005-08-02 19:36:44 UTC
> Updated my KDE yesterday and found that his bug is NOT fixed in KDE 3.4.2. 
> IMHO the fixes are either too weak or incompletely/incorrectly implemented in
> KDE 3.4.2 
 
no, there's a bug in kdelibs which i'll be working on this week. the actual bug that was in kicker has indeed been fixed. 

if you have any menu additions to kicker that use KDirLister this crash occurs. note that i've actually opened another bug elsewhere about this. this happens to be why i ask that unless the bug is assigned to you that you DO NOT reopen it. attach comments and whatnot, i get CC'd on them all and can manage which bugs are re-opened / closed / etc. unless you wish to start helping out with general bug triage in kicker, that is, which is help i'd welcome.
Comment 19 Allyn Tennant 2005-08-03 00:44:13 UTC
> note that i've actually opened another bug elsewhere

Could you give us a tracking number or at least promise us you'll post the fix here?  Thanks.
Comment 20 Walt H 2005-08-04 01:38:51 UTC
I've been seeing this also.  Still not fixed in 3.4.2 running on gentoo.  Oddly enough, it only happens on one of my home systems, which is an SMP box.  I compile kde on this machine, save the binary packages and use them to install on the other computers. The other boxes are fine. Only the SMP box seems affected. If I "dcopquit kicker" first (which crashes the first time also), then I can safely logout.  Subsequent dcopquit's won't cause kicker to crash within the already logged in session (at least within a short period of time after - I haven't checked what happens if it's left running).  Hope this helps :)
Comment 21 Aaron J. Seigo 2005-08-14 00:53:41 UTC
*** Bug 110712 has been marked as a duplicate of this bug. ***
Comment 22 Allyn Tennant 2005-08-15 23:24:50 UTC
I also have this problem and have been using an SMP kernel running on
an Intel HT enable processor.  I tried booting to a non-SMP kernel.  With
the non-SMP kernel, I have exactly the same problem, so it does not appear
to be SMP related.

As stated in an earlier report, I can also typically avoid the crash by
never clicking on the K-menu button (log out starts with a right click on
the desktop).

I also note that I've never seen "dcopquit kicker" cause kicker to crash.
Comment 23 Deni 2005-08-16 10:53:08 UTC
I have the same bug as commenter #14
Fedora Core 4, I keep it updated via up2date.
"KDE Panel (kicker) crashed and caused the signal 11 (SIGSEGV)"
Happens on logout every time.  I typically logout by right clicking the desktop and selecting "logout" from the menu. I'm not a technical person and apologize I could not provide more information.  Thank you for your help.
Comment 24 Deni 2005-08-17 08:00:53 UTC
Created attachment 12244 [details]
kicker crash file
Comment 25 Keith Distin 2005-08-18 09:30:12 UTC
*** This bug has been confirmed by popular vote. ***
Comment 26 Guy 2005-08-19 04:48:02 UTC
I've encountered the same issue on my mother's PC.

I access her PC using freenx configured to start kde. When I log in as 'root' or my personal account, I never have a problem upon ending the session. When I log in using my mother's account, it would crash as described above.

I've since cleaned up her desktop and shut down all her apps so that there were no running user apps when ending the session. The problem has 'dissappeared'. I do not have this problem on any of my PCs. But then again, I run pretty clean desktops. I have enough extra PCs on my network to test different things if you would like to give me different scenarios to check.
Comment 27 Juan Ehrenhaus 2005-08-23 08:48:37 UTC
I have installed SuSE9.3 and updated KDE to the Version 3.4.2. 

As many of the above users, kicker crashes on session logoff. 
The backtrace I can mailing it tonight. 

My current system is: 
SuSE9.3, kernel-2.6.11- Default, xorg-x11-6.8.2, qt-3.3.4, KDE3.4.2

I have 4 users in one PC the problem appear in one of them and related with actions doing in the k_menu (new links to appl.) or with changes in kbfx appl. for instance. By other users where the k-menu or kicker changes are seldom, seems not to have this kicker behavior. 

I will be happy to know how to fix this issue. 

Juan Ehrenhaus
Comment 28 Juan Ehrenhaus 2005-08-23 17:25:05 UTC
Hi, 
I have found the way how to reproduce the kicker crash in my case: 
If you add some optional underr menu like Last open documents, cuase a crsh by log off the kicker. 

if you disable the additional menu kicker didn't crash. 

I have tested the issue in meny users and different kicker setups. 

The above crash-issue happened if an input in kickerrc is like: 

[menus]
...
Extensions=recentdocs.desktop

In normal case is empty like: 
...
Extensions=

Please can you trace this case?
Thank you for feedback. 
Comment 29 Aaron J. Seigo 2005-08-23 18:45:23 UTC
Juan Ehrenhaus:

that is a completely different problem from the one in this report and has thankfully already been fixed.
Comment 30 Juan Ehrenhaus 2005-08-24 08:18:17 UTC
Thank you for your prompt observation. 

Can you please tell me where (if a bug number is opened) can I send the problem I described here above?

Because I am sure it is still not fixed!

SuSE9.3, KDE3.4.2

Comment 31 Scott Lewin 2005-08-25 00:35:51 UTC
A also get the same exact problem in Kubuntu 5.04 using KDE 3.4.2.

Below I have put the report of the bug

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' 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)
[Thread debugging using libthread_db enabled]
[New Thread -1229954944 (LWP 7756)]
(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  0xb74ab653 in QGList::find () from /usr/lib/libqt-mt.so.3
#5  0xb785eaee in KGlobal::registerStaticDeleter ()
   from /usr/lib/libkdecore.so.4
#6  0xb7df4a5c in KDirWatch::self () from /usr/lib/libkio.so.4
#7  0xb7e37103 in KDirListerCache::KDirListerCache ()
   from /usr/lib/libkio.so.4
#8  0xb7e3b047 in KDirListerCache::self () from /usr/lib/libkio.so.4
#9  0xb7e3fc69 in KDirLister::stop () from /usr/lib/libkio.so.4
#10 0xb7e3f790 in KDirLister::~KDirLister () from /usr/lib/libkio.so.4
#11 0xb6337f73 in SystemMenu::~SystemMenu ()
   from /usr/lib/kde3/kickermenu_systemmenu.so
#12 0xb7c0e7ce in QPtrList<QObject>::deleteItem () from /usr/lib/libkdeui.so.4
#13 0xb74ab5cc in QGList::clear () from /usr/lib/libqt-mt.so.3
#14 0xb78682e3 in KLibrary::~KLibrary () from /usr/lib/libkdecore.so.4
#15 0xb7869fc6 in KLibLoader::close_pending () from /usr/lib/libkdecore.so.4
#16 0xb78693fa in KLibLoader::~KLibLoader () from /usr/lib/libkdecore.so.4
#17 0xb7868e48 in KLibLoader::cleanUp () from /usr/lib/libkdecore.so.4
#18 0xb77c8e93 in KApplication::~KApplication () from /usr/lib/libkdecore.so.4
#19 0xb786d0c7 in KUniqueApplication::~KUniqueApplication ()
   from /usr/lib/libkdecore.so.4
#20 0xb6917a79 in Kicker::~Kicker () from /usr/lib/libkdeinit_kicker.so
#21 0xb69159c3 in kdemain () from /usr/lib/libkdeinit_kicker.so
#22 0xb7fe7966 in kdeinitmain () from /usr/lib/kde3/kicker.so
#23 0x0804cdd2 in ?? ()
#24 0x00000001 in ?? ()
#25 0x081387b8 in ?? ()
#26 0x00000001 in ?? ()
#27 0x00000000 in ?? ()
#28 0x00000000 in ?? ()
#29 0x00000000 in ?? ()
#30 0x00000000 in ?? ()
#31 0x00000000 in ?? ()
#32 0x00000000 in ?? ()
#33 0x00000000 in ?? ()
#34 0x00000000 in ?? ()
#35 0x00000000 in ?? ()
#36 0x00000000 in ?? ()
#37 0x00000000 in ?? ()
#38 0x00000000 in ?? ()
#39 0x00000000 in ?? ()
#40 0x00000000 in ?? ()
#41 0x00000000 in ?? ()
#42 0x00000000 in ?? ()
#43 0x00000000 in ?? ()
#44 0x00000000 in ?? ()
#45 0x00000000 in ?? ()
#46 0x00000000 in ?? ()
#47 0x00000000 in ?? ()
#48 0x080aa778 in ?? ()
#49 0x00000000 in ?? ()
#50 0x00000000 in ?? ()
#51 0x00000000 in ?? ()
#52 0x00000000 in ?? ()
#53 0x00000000 in ?? ()
#54 0x00000000 in ?? ()
#55 0x00000000 in ?? ()
#56 0xb762fee0 in vtable for QGArray () from /usr/lib/libqt-mt.so.3
#57 0x00000000 in ?? ()
#58 0x00004010 in ?? ()
#59 0x00000000 in ?? ()
#60 0x00000000 in ?? ()
#61 0x00000000 in ?? ()
#62 0x00000000 in ?? ()
#63 0x00000000 in ?? ()
#64 0x0805b548 in ?? ()
#65 0x00000000 in ?? ()
#66 0x00000010 in ?? ()
#67 0xb6c539e0 in __after_morecore_hook () from /lib/tls/i686/cmov/libc.so.6
#68 0xb6c53038 in ?? () from /lib/tls/i686/cmov/libc.so.6
#69 0xb6c539e0 in __after_morecore_hook () from /lib/tls/i686/cmov/libc.so.6
#70 0x00000001 in ?? ()
#71 0xbffff748 in ?? ()
#72 0xb6b98b0b in malloc () from /lib/tls/i686/cmov/libc.so.6
#73 0x0804e2fb in ?? ()
#74 0x00000001 in ?? ()
#75 0x08138344 in ?? ()
#76 0x0813834b in ?? ()
#77 0x00000000 in ?? ()
#78 0x00000000 in ?? ()
#79 0x0813834f in ?? ()
#80 0x00000000 in ?? ()
#81 0x00000000 in ?? ()
#82 0x00000000 in ?? ()
#83 0x08050657 in _IO_stdin_used ()
#84 0x00000000 in ?? ()
#85 0x00000000 in ?? ()
#86 0x00000000 in ?? ()
#87 0x08050657 in _IO_stdin_used ()
#88 0x00000000 in ?? ()
#89 0x00000000 in ?? ()
#90 0x0813834f in ?? ()
#91 0x00000000 in ?? ()
#92 0x00000000 in ?? ()
#93 0x0813834b in ?? ()
#94 0x08138344 in ?? ()
#95 0x00000001 in ?? ()
#96 0x08138340 in ?? ()
#97 0x00000000 in ?? ()
#98 0x00000000 in ?? ()
#99 0x00000000 in ?? ()
#100 0x0000000c in ?? ()
#101 0x00000013 in ?? ()
#102 0x080525d8 in vtable for QCString ()
#103 0x0805b550 in ?? ()
#104 0x00000000 in ?? ()
#105 0x00000000 in ?? ()
#106 0x080525d8 in vtable for QCString ()
#107 0x0805b540 in ?? ()
#108 0x80cd0000 in ?? ()
#109 0xb6bcea63 in fork () from /lib/tls/i686/cmov/libc.so.6
#110 0x0804e81e in ?? ()
#111 0x00000008 in ?? ()
#112 0xbffffab0 in ?? ()
#113 0xbffffa30 in ?? ()
#114 0xbffff9b0 in ?? ()
#115 0x00000000 in ?? ()
#116 0xbffff950 in ?? ()
#117 0xbffff8b8 in ?? ()
#118 0xb6d13d13 in operator delete () from /usr/lib/libstdc++.so.5
#119 0x0804f88d in ?? ()
#120 0x00000000 in ?? ()
#121 0xbffffbae in ?? ()
#122 0x00000001 in ?? ()
#123 0x00000000 in ?? ()
#124 0x00000000 in ?? ()
#125 0x00000000 in ?? ()
#126 0x00000000 in ?? ()
#127 0x00000000 in ?? ()
#128 0x00000000 in ?? ()
#129 0x08050657 in _IO_stdin_used ()
#130 0x00000000 in ?? ()
#131 0xbffffb88 in ?? ()
#132 0xb6b53980 in __cxa_atexit () from /lib/tls/i686/cmov/libc.so.6
#133 0xb6b3e8c8 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#134 0x0804b731 in ?? ()
Comment 32 Juan Ehrenhaus 2005-08-25 08:09:06 UTC
I have open a new bug trace number:

http://bugs.kde.org/show_bug.cgi?id=111408

Please go there and add your comments. The only way to
avoid the crash in our cases is to not select optional
menus in K-menu. 


--- Scott Lewin <sclewin@bmts.com> schrieb:

[bugs.kde.org quoted mail]
=== message truncated ===



	
		
___________________________________________________________ 
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
Comment 33 Rob Hughes 2005-08-27 17:40:27 UTC
I tried removing the extensions I was using (system and preferences), and am no longer experiecing the crashes at logout.
Comment 34 Jens Nixdorf 2005-08-28 23:38:17 UTC
i can confirm this bug for SuSE 10 Beta 2 (kernel 2.6.13-rc6-git7-3-default and KDE 3.4.2 Level "b") and also for Kanotix 2005.3 (kernel 2.6.11-kanotix-11 and KDE 3.4.1). 
Comment 35 Aaron J. Seigo 2005-08-29 11:59:44 UTC
a) do not re-open bugs i have closed. you can add comments to them and i will get emailed with your comments at which point i can decide what to do. but you re-opening them just wastes my time. i'm sure you'd rather have me working on fixing your bugs than wasting my time on bugs.kde.org.

b) this bug is already fixed. the fix did not make it into 3.4.2, but it is in SVN.

c) don't re-open my bugs =)
Comment 36 Funda Wang 2005-08-31 20:59:09 UTC
Both OpenSUSE 10beta3 and Mandriva 2006beta3 include the latest kdebase/kicker source, but users still report kicker is crashing :(
Comment 37 Paul Salazar 2005-09-05 21:33:26 UTC
I have the same problem (Mandriva 2006 beta 3) I just downloaded and installed this week.  I see up that this bug is "resolved", but after reading all the comments I have nothing clear.  I'm new in Linux and would like a more simple explanation.  What I should do in order to get this bug "resolved" in my PC?  
Comment 38 Funda Wang 2005-09-06 02:39:58 UTC
The only way to get rid of this bug is to prevent using any optionnal menu in kicker (configure panel -> layout -> [menus]).
Comment 39 Keith Distin 2005-09-06 08:52:49 UTC
If the only way to fix something is not to use it then it isn't fixed - it's still broken!  Why has this been marked as fixed?
Comment 40 Juan Ehrenhaus 2005-09-06 13:04:04 UTC
Please, 
read the messages from Aaron Seigo. The problem is fixed in the SVN Version of KDE. 
Untill the version 3.4.2 was an open one. 
Comment 41 Rob Hughes 2005-09-06 13:13:58 UTC
------- Additional Comment #35 From Aaron J. Seigo  2005-08-29 11:59 -------
a) do not re-open bugs i have closed. you can add comments to them and i will get emailed with your comments at which point i can decide what to do. but you re-opening them just wastes my time. i'm sure you'd rather have me working on fixing your bugs than wasting my time on bugs.kde.org.

b) this bug is already fixed. the fix did not make it into 3.4.2, but it is in SVN.

c) don't re-open my bugs =) 

So the *workaround* is to not use the optional menus until the "fix" is actually released. Or you can download and compile from SVN.
Comment 42 Jens Nixdorf 2005-09-30 11:40:22 UTC
Installed KDE 3.5 beta 1 (3.4.91) and the bug is still there. And my kicker doesnt have any optional menu. 
Comment 43 Juergen Wieczorek 2005-10-19 12:18:06 UTC
This bug is apparently not fixed in kde-3.4.3, see my new entry bug #114674
 
Comment 44 Aewyn Vienna 2005-10-19 12:23:40 UTC
And, in the 3.4.92 (ubuntu1) the bug is still here (there are no opt menus).

This bug is exist for years, as I remember, it was always part of kde. :/
Comment 45 Aaron J. Seigo 2005-10-21 18:24:11 UTC
there were at least 3 different things that would trigger this bug. 2 of them were fixed. the other one is still open in the bug tracker and will hopefully be fixed soon.
Comment 46 MasterOne 2005-12-10 17:02:41 UTC
Now this is really strange. I never had that issue with any versions before 3.5.0, but now I just upgraded from 3.4.3 to 3.5.0, and suddenly kicker crashes with signal 11 (SIGSEGV) each time I log out.

I just did some tests. If you login as a new user (who doesn't have a .kde symlink and .kde3.x dir in his home), and logout again without changing anything, kicker does not cause any problem. But as soon as you change anything (like simply opening the controlcenter before logging out), that causes a session to be stored, kicker crashes on logout. 
 
So it has nothing to do with the kickerrc file (also compared it with the last version in my .kde3.4 folder), but more likely with the session management. Although, in that case every other KDE 3.5 user should experience the same problem, which leads to the conclusion, that it does not seem to be a general problem or bug (otherwise we would already know). 
 
Anyone any hint? 
 
P.S. It is the session management! Precisely kicker crashes when the session gets stored at the end of a session (= on logout). This can simply be tested by switching to "On login: Start with empty session" in the controlcenter. It's not such a big problem for me, because most of the time I just suspend that machine (which is a notebook BTW), but nevertheless I would like to get that issue fixed.
Comment 47 MasterOne 2005-12-10 17:26:16 UTC
BTW I can confirm, that kicker only crashes when using logoff from the kmenu. If I logoff using strg-alt-del, kicker does not crash. So it may not have something to do with the session management after all. Isn't that strange?
Comment 48 Aaron J. Seigo 2005-12-11 18:27:39 UTC
masterone: it has nothing to do with session management. it has to do with the kmenu being populated when you open it up which creates the menu plugins (e.g. the system menu, or preferences menu, etc) which cause this crash.
Comment 49 2005-12-12 04:10:01 UTC
Kicker logout last crash backtrace:

Using host libthread_db library "/lib/tls/libthread_db.so.1".
`shared object read from target memory' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1232513344 (LWP 6485)]
[KCrash handler]
#4  0xb632f087 in TaskContainer::popupMenu (this=0x827c728, action=0)
    at ./kicker/taskbar/taskcontainer.cpp:1125
#5  0xb6332c04 in TaskContainer::performAction (this=0x827c728, action=0)
    at ./kicker/taskbar/taskcontainer.cpp:947
#6  0xb633835b in TaskContainer::mousePressEvent (this=0x827c728, 
    e=0xbf858574) at ./kicker/taskbar/taskcontainer.cpp:882
#7  0xb74cb04c in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#8  0x0827c728 in ?? ()
#9  0xbf858574 in ?? ()
#10 0x00000000 in ?? ()

As you see the problem persists in taskcontainer.cpp
Comment 50 2005-12-12 04:34:33 UTC
Forgot to say that im using branch_3.5 kdelibs revision 487504 and kdebase revision 487589.
Comment 51 MasterOne 2005-12-12 10:14:54 UTC
Aaron J. Seigo, do you already have an idea, how this can be fixed?

I have seen a lot of bugreports concerning kicker crashing on logout, and the really strange thing is, that on one hand, not everybody using KDE seems to be effected (which should be the case, if it is a general bug), and on the other hand, although that problem has been reported for former versions (like this bug, which started for 3.4.1), my system did not suffer from it, until I upgraded recently to 3.5.0.

So there has to be something weird going on, otherwise this known problem would already have been fixed a while ago.

I also don't really understand the relation between the kmenu population and the crash, because the kmenu behalves absolutely normally, so there is not a single problem during use at all, it just crashes every time I reboot or logoff using the kmenu "Logoff" entry.

If you need my crash backtrace output, please tell and I can post it here (but I don't think, it will reveal something new).
Comment 52 Aaron J. Seigo 2005-12-12 17:55:50 UTC
Ze: your crash is a different one to this one and is reported elsewhere.

MasterOne: yes, i'm aware of the source of this bug and even had it fixed for 3.5.0 until another developer reverted the fix without really understanding the ramifications of doing so. it will be fixed in 3.5.1, however.
Comment 53 MasterOne 2005-12-12 18:14:39 UTC
That's great news, Aaron J. Seigo, thank's a lot for your fast feedback, so waiting for 3.5.1 then ;-)
Comment 54 Marc Collin 2005-12-14 05:20:28 UTC
with suse 10, kde 3.5 i got this problem...
everytime i log out, kicker crash with Signal 11 SIGSEGV
thanks
Comment 55 Kyle Peterson 2005-12-21 15:23:08 UTC
I'm also using Suse 10 and just upgraded to KDE 3.5 and my kicker crashes every time I logout.  There is nothing I can do to make it stop.  I have no menu extensions turned on, disabling transparency doesn't help and even completely disabling the sys tray doesn't help.
Comment 56 Gianluca Moretti(Furlan) 2005-12-23 22:26:59 UTC
I have the same problem using Kubuntu(5.10) and Kde 3.5. Kicker crashes when I logout or shutdown my pc. I have no menu extension or other.

Sorry for my English :)
Comment 57 Rex Dieter 2005-12-23 22:29:20 UTC
OK, looks more like a dup.
Comment 58 Rex Dieter 2005-12-23 22:30:43 UTC

*** This bug has been marked as a duplicate of 113242 ***
Comment 59 Uwe Gottschling 2006-01-14 10:00:29 UTC
I updated Slackware 10.2 from KDE3.4.2 to 3.5 with original package downloaded from an official mirror from www.kde.org. If i log out i get sometimes kicker crash windows. I checked it with the original kernel and the 2.6.15 kernel, with no different.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/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)
[Thread debugging using libthread_db enabled]
[New Thread -1231456576 (LWP 3551)]
[KCrash handler]
#3  0xb7484a80 in QGList::findRef () from /usr/lib/qt/lib/libqt-mt.so.3
#4  0xb74846d5 in QGList::removeRef () from /usr/lib/qt/lib/libqt-mt.so.3
#5  0xb7e4e22b in KDirListerCache::forgetDirs () from /opt/kde/lib/libkio.so.4
#6  0xb7e4e113 in KDirListerCache::forgetDirs () from /opt/kde/lib/libkio.so.4
#7  0xb7e548e4 in KDirLister::~KDirLister () from /opt/kde/lib/libkio.so.4
#8  0xb6401e33 in SystemMenu::~SystemMenu ()
   from /opt/kde/lib/kde3/kickermenu_systemmenu.so
#9  0xb7bab5ae in QPtrList<QObject>::deleteItem ()
   from /opt/kde/lib/libkdeui.so.4
#10 0xb7484a3e in QGList::clear () from /usr/lib/qt/lib/libqt-mt.so.3
#11 0xb7864273 in KLibrary::~KLibrary () from /opt/kde/lib/libkdecore.so.4
#12 0xb7865f56 in KLibLoader::close_pending ()
   from /opt/kde/lib/libkdecore.so.4
#13 0xb786538a in KLibLoader::~KLibLoader () from /opt/kde/lib/libkdecore.so.4
#14 0xb7864dd8 in KLibLoader::cleanUp () from /opt/kde/lib/libkdecore.so.4
#15 0xb77aed13 in KApplication::~KApplication ()
   from /opt/kde/lib/libkdecore.so.4
#16 0xb786abd7 in KUniqueApplication::~KUniqueApplication ()
   from /opt/kde/lib/libkdecore.so.4
#17 0xb68393ef in Kicker::~Kicker () from /opt/kde/lib/libkdeinit_kicker.so
#18 0xb6836f58 in kdemain () from /opt/kde/lib/libkdeinit_kicker.so
#19 0xb76b37d6 in kdeinitmain () from /opt/kde/lib/kde3/kicker.so
#20 0x0804ce13 in ?? ()
#21 0x00000001 in ?? ()
#22 0x0807eff0 in ?? ()
#23 0x00000001 in ?? ()
#24 0x00000000 in ?? ()
#25 0x00000000 in ?? ()
#26 0x00001f80 in ?? ()
#27 0x00000000 in ?? ()
#28 0x00000000 in ?? ()
#29 0x00000000 in ?? ()
#30 0x00000000 in ?? ()
#31 0x00000000 in ?? ()
#32 0x00000000 in ?? ()
#33 0x00000000 in ?? ()
#34 0x00000000 in ?? ()
#35 0x00000000 in ?? ()
#36 0x00000000 in ?? ()
#37 0xb6a4e184 in _int_malloc () from /lib/tls/libc.so.6
#38 0x0804e4ab in ?? ()
#39 0x00000001 in ?? ()
#40 0x0807f3fc in ?? ()
#41 0x0807f403 in ?? ()
#42 0x00000000 in ?? ()
#43 0x00000000 in ?? ()
#44 0x0807f407 in ?? ()
#45 0x00000000 in ?? ()
#46 0x00000000 in ?? ()
#47 0x00000000 in ?? ()
#48 0x080507b7 in _IO_stdin_used ()
#49 0x00000000 in ?? ()
#50 0x00000000 in ?? ()
#51 0x00000000 in ?? ()
#52 0x080507b7 in _IO_stdin_used ()
#53 0x00000000 in ?? ()
#54 0x00000000 in ?? ()
#55 0x0807f407 in ?? ()
#56 0x00000000 in ?? ()
#57 0x00000000 in ?? ()
#58 0x0807f403 in ?? ()
#59 0x0807f3fc in ?? ()
#60 0x00000001 in ?? ()
#61 0x0807f3f8 in ?? ()
#62 0x00000000 in ?? ()
#63 0x00000000 in ?? ()
#64 0x00000000 in ?? ()
#65 0x0000000c in ?? ()
#66 0x00000013 in ?? ()
#67 0x080528b8 in vtable for QCString ()
#68 0x0805b540 in ?? ()
#69 0x00000000 in ?? ()
#70 0x00000000 in ?? ()
#71 0x080528b8 in vtable for QCString ()
#72 0x0805b530 in ?? ()
#73 0x00000000 in ?? ()
#74 0x00000000 in ?? ()
#75 0x0077b858 in ?? ()
#76 0x80cd0000 in ?? ()
#77 0xbfcf92f0 in ?? ()
#78 0x00000001 in ?? ()
#79 0xbfcf92f0 in ?? ()
#80 0x00000dcb in ?? ()
#81 0xbfcf9408 in ?? ()
#82 0x0804e9ce in ?? ()
#83 0x00000008 in ?? ()
#84 0xbfcf9370 in ?? ()
#85 0xbfcf92f0 in ?? ()
#86 0xbfcf9270 in ?? ()
#87 0x00000000 in ?? ()
#88 0xbfcf9230 in ?? ()
#89 0xb6a4d834 in _int_free () from /lib/tls/libc.so.6
Comment 60 Sotnik Dmitrij 2006-01-18 10:53:28 UTC
Hi guys (and Ladies :)!

On my opinion this bug has some relation to kickerrc stuff in user homedir.
  I have few PC with Linux. Yestarday on one of them, after kde upgrading up to 3.5.0, I found the same bug, nevertheless, other PC with KDE from 3.4.0 to 3.5.0 works absolutely normally. 
  I try to copy kickerrc file from "healthy" PC to "buggy" and this really helps! So I think that some problems could have relation to it stuff and could be instantly solved by this way until we get patches for this almost unbreakable bug.

Good luck!
Comment 61 Andy 2006-02-27 09:45:35 UTC
Hi all,

I have upgrade to KDE 3.5.1 but my problem still exists. Below is the log, please advise any fix for this.

THKS!

[KCrash handler]
#6  0x6b636f74 in ?? ()
#7  0xb6cb4cf1 in XDestroyIC () from /usr/lib/libX11.so.6
#8  0xb67bfeea in QXIMInputContext::~QXIMInputContext ()
   from /usr/qt/3/plugins/inputmethods/libqxim.so
#9  0xb7171cac in QObject::event () from /usr/qt/3/lib/libqt-mt.so.3
#10 0xb7117a2f in QApplication::internalNotify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#11 0xb7116d95 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#12 0xb777b5a5 in KApplication::notify ()
   from /usr/kde/3.5/lib/libkdecore.so.4
#13 0xb7118926 in QApplication::sendPostedEvents ()
   from /usr/qt/3/lib/libqt-mt.so.3
#14 0xb71187a6 in QApplication::sendPostedEvents ()
   from /usr/qt/3/lib/libqt-mt.so.3
#15 0xb70c259d in QEventLoop::processEvents ()
   from /usr/qt/3/lib/libqt-mt.so.3
#16 0xb7129f48 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#17 0xb7129df8 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#18 0xb7117c81 in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
#19 0xb680f05a in kdemain () from /usr/kde/3.5/lib/libkdeinit_ksmserver.so
#20 0xb768c746 in kdeinitmain () from /usr/kde/3.5/lib/kde3/ksmserver.so
Comment 62 Aaron J. Seigo 2006-02-27 18:17:36 UTC
andy: kicker is crashing in xim related code which is outside of kde. this is a known issue and i saw patches for this floating around last week (patches apply to qt, not kde)
Comment 63 Andy 2006-03-03 11:16:40 UTC
Hi Aaron,

I search for the information about my problem for few days, but still can't find the solution. Do you mind give me some references where I can find the related resources?

THKS!
Andy
Comment 64 Sebastian Stein 2006-03-23 22:55:45 UTC
The bug is still there. I have Kubuntu Breezy with KDE 3.5.1 installed from the provided packages.


Sebastian
Comment 65 123456 2006-03-26 22:12:14 UTC
(no debugging symbols found)
Using host libthread_db library "/lib/tls/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)
[Thread debugging using libthread_db enabled]
[New Thread -1231116608 (LWP 4082)]
(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]
#6  0x7079542f in ?? ()
#7  0xb72bc45f in _X11TransWrite () from /usr/X11R6/lib/libX11.so.6
#8  0xb729fea5 in _XError () from /usr/X11R6/lib/libX11.so.6
#9  0xb729ffcd in _XReply () from /usr/X11R6/lib/libX11.so.6
#10 0xb7287d35 in _XGetWindowAttributes () from /usr/X11R6/lib/libX11.so.6
#11 0xb7287eb2 in XGetWindowAttributes () from /usr/X11R6/lib/libX11.so.6
#12 0xb6931066 in _XimLocalSetICValues ()
   from /usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2
#13 0xb6932012 in _XimSetICDefaults ()
   from /usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2
#14 0xb69320b2 in _XimSetICDefaults ()
   from /usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2
#15 0xb692ec65 in _XimLocalCreateIC ()
   from /usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2
#16 0xb72b8cdc in XCreateIC () from /usr/X11R6/lib/libX11.so.6
#17 0xb66cc57b in QXIMInputContext::setHolderWidget ()
   from /usr/lib/qt3/plugins/lib/inputmethods/libqxim.so
#18 0xb775d1c8 in QInputContextFactory::create ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0xb6411e45 in QMultiInputContext::changeInputMethod ()
   from /usr/lib/qt3/plugins/lib/inputmethods/libqimsw-multi.so
#20 0xb6411ff6 in QMultiInputContext::slave ()
   from /usr/lib/qt3/plugins/lib/inputmethods/libqimsw-multi.so
#21 0xb6412295 in QMultiInputContext::setHolderWidget ()
   from /usr/lib/qt3/plugins/lib/inputmethods/libqimsw-multi.so
#22 0xb775d1c8 in QInputContextFactory::create ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0xb750e1c6 in QWidget::createInputContext ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0xb750e31d in QWidget::unfocusInputContext ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0xb75ce4da in QWidget::clearFocus () from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0xb75d0576 in QWidget::~QWidget$base ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0xb76921d7 in QPopupMenu::~QPopupMenu$base ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0xb6efb046 in KPopupMenu::~KPopupMenu$base () from /usr/lib/libkdeui.so.4
#29 0xb6efc29d in KPanelMenu::~KPanelMenu$base () from /usr/lib/libkdeui.so.4
#30 0xb68de438 in PanelServiceMenu::~PanelServiceMenu$base ()
   from /usr/lib/libkdeinit_kicker.so
#31 0xb68d8cdc in PanelKMenu::~PanelKMenu$delete ()
   from /usr/lib/libkdeinit_kicker.so
#32 0xb68a389d in MenuManager::~MenuManager$delete ()
   from /usr/lib/libkdeinit_kicker.so
#33 0xb759d0b5 in QObject::~QObject$base ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#34 0xb7547152 in QApplication::~QApplication$base ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#35 0xb7b12af9 in KApplication::~KApplication$base ()
   from /usr/lib/libkdecore.so.4
#36 0xb7b12ccf in KUniqueApplication::~KUniqueApplication$base ()
   from /usr/lib/libkdecore.so.4
#37 0xb6881f64 in Kicker::~Kicker$delete () from /usr/lib/libkdeinit_kicker.so
#38 0xb6881904 in kdemain () from /usr/lib/libkdeinit_kicker.so
#39 0xb691c534 in kdeinitmain () from /usr/lib/kde3/kicker.so
#40 0x0804e0ca in ?? ()
#41 0x00000001 in ?? ()
#42 0x0806fb70 in ?? ()
#43 0x00000001 in ?? ()
#44 0x00000000 in ?? ()

-----------------------------------------------------------------------------
KDE 3.5.1 on Mandriva 2006 2.6.12-12mdksmp

bug appeared after upgrading kdm to 3.5.1 

Andrew
Comment 66 baum-im-wald 2006-03-27 14:07:36 UTC
Created attachment 15323 [details]
experiencing an equal problem on SUSE 10.0 with KDE 3.5.0. Backtrace.
Comment 67 Kristjan Ugrin 2006-05-13 19:01:10 UTC
I can confirm this on suse 10, kde 3.5.2.

Note:
It seems to occur only when using sessions.
Kde Control Center->Kde components->Restore manually saved session.

If I set this to Start with an empty session, kde exits cleanly.

You can try to reproduce this by saving session more than once (try to logout/login before saving again).

Programs saved in my session:
amaroK, KInternet, Klipper, Kpowersave, Kmix, Kshutdown, Kget, Superkaramba (+3 themes).
Comment 68 Kristjan Ugrin 2006-05-14 12:13:48 UTC
Created attachment 16085 [details]
Kicker crash backtrace
Comment 69 Kristjan Ugrin 2006-05-14 12:13:51 UTC
Created attachment 16086 [details]
Kicker crash backtrace
Comment 70 Jekyll Wu 2013-03-07 00:19:10 UTC
*** Bug 107714 has been marked as a duplicate of this bug. ***