Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm a newbie, just installed slackware 10.2. For some reason, kicker crashes everytime I exit kde and X hangs. sometimes ctrl+alt+backspace doesnot work to kill it.
I have the crash report attached, but I have no idea what it's saying. I would appreciate any help,,,
Kicker crash report (appears right before X hangs when log out):
(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
(...repeats...)
[Thread debugging using libthread_db enabled]
[New Thread -1231239488 (LWP 5122)]
(no debugging symbols found)
(...repeats...)
[KCrash handler]
#3 0xb7478ad8 in QGList::find () from /usr/lib/qt/lib/libqt-mt.so.3
#4 0xb784455e in KGlobal::registerStaticDeleter ()
from /opt/kde/lib/libkdecore.so.4
#5 0xb7dcb3dc in KDirWatch::self () from /opt/kde/lib/libkio.so.4
#6 0xb7e1c3d3 in KDirListerCache::KDirListerCache ()
from /opt/kde/lib/libkio.so.4
#7 0xb7e20317 in KDirListerCache::self () from /opt/kde/lib/libkio.so.4
#8 0xb7e24f39 in KDirLister::stop () from /opt/kde/lib/libkio.so.4
#9 0xb7e24a60 in KDirLister::~KDirLister () from /opt/kde/lib/libkio.so.4
#10 0xb650fe33 in SystemMenu::~SystemMenu ()
from /opt/kde/lib/kde3/kickermenu_systemmenu.so
#11 0xb7b869ae in QPtrList<QObject>::deleteItem ()
from /opt/kde/lib/libkdeui.so.4
#12 0xb7478a3e in QGList::clear () from /usr/lib/qt/lib/libqt-mt.so.3
#13 0xb784f3d3 in KLibrary::~KLibrary () from /opt/kde/lib/libkdecore.so.4
#14 0xb78510b6 in KLibLoader::close_pending ()
from /opt/kde/lib/libkdecore.so.4
#15 0xb78504ea in KLibLoader::~KLibLoader () from /opt/kde/lib/libkdecore.so.4
#16 0xb784ff38 in KLibLoader::cleanUp () from /opt/kde/lib/libkdecore.so.4
#17 0xb779cb73 in KApplication::~KApplication ()
from /opt/kde/lib/libkdecore.so.4
#18 0xb7854c47 in KUniqueApplication::~KUniqueApplication ()
from /opt/kde/lib/libkdecore.so.4
#19 0xb6883b59 in Kicker::~Kicker () from /opt/kde/lib/libkdeinit_kicker.so
#20 0xb68819b3 in kdemain () from /opt/kde/lib/libkdeinit_kicker.so
#21 0xb76a67d6 in kdeinitmain () from /opt/kde/lib/kde3/kicker.so
#22 0x0804ce12 in ?? ()
(...repeats various numbers...)
#55 0xb75ffcc0 in vtable for QGArray () from /usr/lib/qt/lib/libqt-mt.so.3
(...repeats various numbers...)
#68 0xb6a875f4 in _int_malloc () from /lib/tls/libc.so.6
#69 0x0804e33b in ?? ()
(...repeats various numbers...)
#79 0x080506b7 in _IO_stdin_used ()
(...repeats various numbers...)
#83 0x080506b7 in _IO_stdin_used ()
(...repeats various numbers...)
#98 0x08052658 in vtable for QCString ()
(...repeats various numbers...)
#102 0x08052658 in vtable for QCString ()
(...repeats various numbers...)
#121 0xb6bfb48d in operator delete () from /usr/lib/./libstdc++.so.5
---end---
Also, after deleting the System menu from the panel and from the desktop, crashes became less frequent (every 6-8 logout).
Last edited by towsonu2003; 09-26-2005 at 05:36 PM.
I think one of the reasons no one has replied in about 5 days, is that your Kicker crash report is excessively long.
Just for the CLI/scripting practice, I put your crash report into 2 files, 1.txt & 2.txt. 1.txt contains the part with no line #'s, 2.txt the portion where the lines are numbered. Here is the use of 'uniq' to eliminate the duplicates, while counting the repetitions:
Code:
uniq -c 1.txt
uniq -cf1 2.txt | less
I wanted to get really cute, so I added an 'awk' to the 2nd to align the line #'s:
Maybe if you would edit your post to eliminate the duplicate lines (I've given you a way to do it painlessly) someone would be willing to wade through it & advise you.
Having the same problem over here.
But luckily it doesn't hang my X, I just need to click on "OK" at the crash report and then I can log out like normal.
But it is rather irritating to have a crash report on almost every logout...
I'm having the same problem. About 1 out of 5 times when I log out I get the crash, and if I click OK, everything seems normal. I've had a few other crashes in KDE, but those are very infrequent. Hopefully someone will find a solution to the problem.
This seems to be a KDE bug. KDE people told me to remove the System menu from the panel. I removed that and the System link from my desktop. Now the crashes are much less frequent, but still happening.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.