Bug 134617 - continuous bouncing conqueror-cursor, not starting an application
Summary: continuous bouncing conqueror-cursor, not starting an application
Status: RESOLVED DUPLICATE of bug 133386
Alias: None
Product: kicker
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Aaron J. Seigo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-25 09:23 UTC by Monkey 9
Modified: 2006-10-15 00:10 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Monkey 9 2006-09-25 09:23:12 UTC
Version:           (kicker-panel) KDE-Paneel 3.5.4(release 78.1) (using KDE KDE 3.5.4)
Installed from:    SuSE RPMs
OS:                Linux

System hangs, 100% cpu-usage, have to shut down with pc-button.(!)

Traceback:

Systeemconfiguratie opstartcontrole uitgeschakeld.

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47398107032448 (LWP 3491)]
[KCrash handler]
#5  0x00002b1bbd8f479a in TaskContainer::updateKickerTip ()
   from /opt/kde3/lib64/libtaskbar.so.1
#6  0x00002b1bbbf015da in KickerTip::display ()
   from /opt/kde3/lib64/libkickermain.so.1
#7  0x00002b1bbbf01aa8 in KickerTip::qt_invoke ()
   from /opt/kde3/lib64/libkickermain.so.1
#8  0x00002b1bb8522adc in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#9  0x00002b1bb85237f3 in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#10 0x00002b1bb8541ee5 in QTimer::event ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#11 0x00002b1bb84cbae5 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#12 0x00002b1bb84cc717 in QApplication::notify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#13 0x00002b1bb7ff4498 in KApplication::notify ()
   from /opt/kde3/lib64/libkdecore.so.4
#14 0x00002b1bb84c2055 in QEventLoop::activateTimers ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#15 0x00002b1bb848253d in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#16 0x00002b1bb84e07f1 in QEventLoop::enterLoop ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#17 0x00002b1bb84e069a in QEventLoop::exec ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#18 0x00002b1bbbc311d9 in kdemain () from /opt/kde3/lib64/libkdeinit_kicker.so
#19 0x0000000000407431 in launch ()
#20 0x0000000000407d6c in handle_launcher_request ()
#21 0x00000000004080f5 in handle_requests ()
#22 0x000000000040914a in main ()
Comment 1 Monkey 9 2006-09-25 09:26:50 UTC
Everytime when clicking a link from within conqueror, or conversation, only thing what happens, is a very nervous bouncing cursor, which never ends, only after restart session, or sometimes shutdown per PC-Button...
Comment 2 Bram Schoenmakers 2006-09-25 10:16:09 UTC
There's no way to go to a terminal (Ctrl+Alt+F1) and watch with 'top' which process is causing the 100% CPU usage?
Comment 3 Philip Rodrigues 2006-09-25 11:24:01 UTC
Your description isn't very clear - you seem to be talking about a few separate  problems. Could you clarify?
Comment 4 Stefan Borggraefe 2006-09-30 15:30:44 UTC
The backtrace looks like the one in bug 133386.
Comment 5 Philip Rodrigues 2006-10-15 00:10:12 UTC
Good catch, Stefan. Since there's not really any useful information in this report, I'll close it as a dupe of that one

*** This bug has been marked as a duplicate of 133386 ***