Summary: | The application KDE Panel(kicker) crashed and caused the signal 11 (SIGSEGV) | ||
---|---|---|---|
Product: | [Unmaintained] kicker | Reporter: | Nathan Oliphant <nathan> |
Component: | general | Assignee: | John Firebaugh <jfirebaugh> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | aseigo |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | RedHat Enterprise Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Nathan Oliphant
2003-07-18 23:59:24 UTC
tip: to get kicker back, press Alt-F2 to get the Run Command window up (or you can use a terminal such as konsole) and enter the command: kicker as for the crash, it's not in kicker but happening somewhere in KServiceGroup::entries, which is a fairly complex bit of code. i'm afraid that without a more detailed backtrace not much can be done. i'm also afraid that this may be one of the areas that Red Hat has customized for their distribution (.desktop file locations and handling) and so may not be a KDE bug at all, but a Red Hat bug. Subject: Re: The application KDE Panel(kicker) crashed and caused the signal 11 (SIGSEGV) On Friday 22 August 2003 11:41, Aaron J.Seigo wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=61411 > aseigo@kde.org changed: > > What |Removed |Added > --------------------------------------------------------------------------- >- CC| |aseigo@kde.org > > > > ------- Additional Comments From aseigo@kde.org 2003-08-22 20:41 ------- > tip: to get kicker back, press Alt-F2 to get the Run Command window up (or > you can use a terminal such as konsole) and enter the command: kicker > > as for the crash, it's not in kicker but happening somewhere in > KServiceGroup::entries, which is a fairly complex bit of code. i'm afraid > that without a more detailed backtrace not much can be done. i'm also > afraid that this may be one of the areas that Red Hat has customized for > their distribution (.desktop file locations and handling) and so may not be > a KDE bug at all, but a Red Hat bug. I upgraded to the latest version of KDE a few weeks ago, and haven't had the problem since. *** Bug has been marked as fixed ***. I have got quite the same trouble with KDE 3.2.2 (a new install with apt-get dist-upgrade for upgrade) (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)...[New Thread 16384 (LWP 2344)] (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)... 0x4140efd6 in waitpid () from /lib/libpthread.so.0 #0 0x4140efd6 in waitpid () from /lib/libpthread.so.0 #1 0x40925263 in KCrash::defaultCrashHandler(int) () from /opt/kde3/lib/libkdecore.so.4 #2 0x4140dbb1 in __pthread_sighandler () from /lib/libpthread.so.0 #3 <signal handler called> #4 0x4090b3cc in KWin::WindowInfo::state() const () from /opt/kde3/lib/libkdecore.so.4 #5 0x4194489a in Task::demandsAttention() const () from /opt/kde3/lib/libtaskmanager.so.1 #6 0x41925d00 in TaskContainer::checkAttention(Task const*) () from /opt/kde3/lib/libtaskbar.so.1 #7 0x419258d4 in TaskContainer::taskChanged() () from /opt/kde3/lib/libtaskbar.so.1 #8 0x4192477b in TaskContainer::qt_invoke(int, QUObject*) () from /opt/kde3/lib/libtaskbar.so.1 #9 0x40d5f30b in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/qt3/lib/libqt-mt.so.3 #10 0x40d5f0d4 in QObject::activate_signal(int) () from /usr/lib/qt3/lib/libqt-mt.so.3 #11 0x41941419 in Task::changed() () from /opt/kde3/lib/libtaskmanager.so.1 #12 0x41944291 in Task::refresh(bool) () from /opt/kde3/lib/libtaskmanager.so.1 #13 0x41943572 in TaskManager::windowChanged(unsigned long, unsigned) () from /opt/kde3/lib/libtaskmanager.so.1 #14 0x419426cd in TaskManager::qt_invoke(int, QUObject*) () from /opt/kde3/lib/libtaskmanager.so.1 #15 0x40d5f30b in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/qt3/lib/libqt-mt.so.3 #16 0x4090f17f in KWinModule::windowChanged(unsigned long, unsigned) () from /opt/kde3/lib/libkdecore.so.4 #17 0x4090d61c in KWinModulePrivate::x11Event(_XEvent*) () from /opt/kde3/lib/libkdecore.so.4 #18 0x408aa542 in KApplication::x11EventFilter(_XEvent*) () from /opt/kde3/lib/libkdecore.so.4 #19 0x40c7faa8 in qt_x11EventFilter(_XEvent*) () from /usr/lib/qt3/lib/libqt-mt.so.3 #20 0x40c89d7c in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/qt3/lib/libqt-mt.so.3 #21 0x40ca2b1d in QEventLoop::processEvents(unsigned) () from /usr/lib/qt3/lib/libqt-mt.so.3 #22 0x40d10640 in QEventLoop::enterLoop() () from /usr/lib/qt3/lib/libqt-mt.so.3 #23 0x40d10536 in QEventLoop::exec() () from /usr/lib/qt3/lib/libqt-mt.so.3 #24 0x40cfde0f in QApplication::exec() () from /usr/lib/qt3/lib/libqt-mt.so.3 #25 0x4007f11d in kdemain () from /opt/kde3/lib/libkdeinit_kicker.so #26 0x0804865b in main () anyone to help ? Thanks a lot. Both Alt F2 and the comand 'kicker' do not open the panel and the main manue, The Alt F2 just close the error message and the 'kicker' opens it again: KCrash: Application 'kicker' crashing, It seems that the wrong application is the kicker itself, it appeared in the new KDE 3.3.1-2.2 version after updating Fedora-3 distro I have the same problem with kde 3.5.8 in Kubuntu 7.10: it's the third time that kicker crashes. Last time has crashed, i was closing aMule. This is my 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 -1233271104 (LWP 5461)] (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 0xb5f118ea in TaskContainer::updateKickerTip () from /usr/lib/libtaskbar.so.1 #7 0xb6508f52 in KickerTip::display () from /usr/lib/libkickermain.so.1 #8 0xb65094cf in KickerTip::qt_invoke () from /usr/lib/libkickermain.so.1 #9 0xb71f0893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #10 0xb71f1338 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #11 0xb757e9b2 in QTimer::timeout () from /usr/lib/libqt-mt.so.3 #12 0xb72185ba in QTimer::event () from /usr/lib/libqt-mt.so.3 #13 0xb7187af0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #14 0xb718991f in QApplication::notify () from /usr/lib/libqt-mt.so.3 #15 0xb788fca2 in KApplication::notify () from /usr/lib/libkdecore.so.4 #16 0xb711a209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #17 0xb717a53b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #18 0xb712ed49 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #19 0xb71a21ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #20 0xb71a1fde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #21 0xb7189699 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #22 0xb660dd92 in kdemain () from /usr/lib/libkdeinit_kicker.so #23 0xb7f21454 in kdeinitmain () from /usr/lib/kde3/kicker.so #24 0x0804e67f in ?? () #25 0x00000001 in ?? () #26 0x0808b720 in ?? () #27 0x00000001 in ?? () #28 0x00000000 in ?? () |