Ubuntu
kooldock package

kooldock segging

Bug #164934 reported by Dave Gilbert
4
Affects Status Importance Assigned to Milestone
kooldock (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kooldock

Gutsy,
Package version: 0.3-1ubuntu3
x86-64

Kooldock starts fine and seems to work OK; but every so often if I just run my mouse back and forward on it I get a KDE crash box come up;
(it must be one process or something because it apparently carries on running). I ran kooldock from a terminal under a session that is mostly gnome;
it spat out quite a few of these warnings:
WARNING: DCOPReply<>: cast to 'QString' error
WARNING: DCOPReply<>: cast to 'QString' error
kooldock: crashHandler called
KCrash: Application 'kooldock' crashing...
WARNING: DCOPReply<>: cast to 'QString' error

Here is the backtrace:

(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)
[Thread debugging using libthread_db enabled]
[New Thread 47338645551712 (LWP 2511)]
(no debugging symbols found)
.
.
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5 0x000000000042199d in ?? ()
#6 0x00002b0ddee31432 in QWidget::event () from /usr/lib/libqt-mt.so.3
#7 0x00002b0dded982a2 in QApplication::internalNotify ()
   from /usr/lib/libqt-mt.so.3
#8 0x00002b0dded9a400 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#9 0x00002b0ddda1f248 in KApplication::notify ()
   from /usr/lib/libkdecore.so.4
#10 0x00002b0dded2ad84 in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#11 0x00002b0dded2998e in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#12 0x00002b0dded2800a in QApplication::x11ProcessEvent ()
   from /usr/lib/libqt-mt.so.3
#13 0x00002b0dded3e43e in QEventLoop::processEvents ()
   from /usr/lib/libqt-mt.so.3
#14 0x00002b0ddedb17e7 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#15 0x00002b0ddedb15ef in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#16 0x00002b0dded99d68 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#17 0x00000000004276b2 in ?? ()
#18 0x00002b0de26feb44 in __libc_start_main () from /lib/libc.so.6
#19 0x000000000040e119 in ?? ()
#20 0x00007fffce8aefd8 in ?? ()
#21 0x0000000000000000 in ?? ()

Revision history for this message
toms (toms-linuxos) wrote :

same here... kubuntu 8.04/amd64.

Here are steps howto reproduce the bug:

1. install kooldock
2. go slowly from the middle of kooldock to the left end, when you reach it, kooldock will crash

Revision history for this message
jolay (jo-lay) wrote :

I confirm the bug is reproducible with an up to date kubuntu 8.04/amd64.

uname -a:
Linux bombyx-dellm65 2.6.24-19-generic #1 SMP Wed Jun 4 15:10:52 UTC 2008 x86_64 GNU/Linux

Kooldock seems to restart after the crash. It crashes again and again when one is mousing past the left end.
Mousing to the right end does not crash it.
Running in terminal gives :

jolay@bombyx-dellm65:~$ kooldock: crashHandler called
KCrash: Application 'kooldock' crashing...
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20
  Minor opcode: 0
  Resource id: 0x3200007

The call stack is the same as above. I include it because there are additional information though I am not sure it helps much more.

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fd8a84c86f0 (LWP 10489)]
[KCrash handler]
#5 0x000000000042199d in ?? ()
#6 0x00007fd8a558f338 in QWidget::event (this=0x6b0e00, e=0x7fffb04db420)
    at kernel/qwidget.cpp:4686
#7 0x00007fd8a54f333a in QApplication::internalNotify (this=0x7fffb04dbc90,
    receiver=0x6b0e00, e=0x7fffb04db420) at kernel/qapplication.cpp:2638
#8 0x00007fd8a54f5410 in QApplication::notify (this=0x7fffb04dbc90,
    receiver=0x6b0e00, e=0x7fffb04db420) at kernel/qapplication.cpp:2424
#9 0x00007fd8a6c2940d in KApplication::notify (this=0x7fffb04dbc90,
    receiver=0x6b0e00, event=0x7fffb04db420)
    at /build/buildd/kdelibs-3.5.9/./kdecore/kapplication.cpp:550
#10 0x00007fd8a5484280 in QApplication::sendSpontaneousEvent (
    receiver=0x6b0e00, event=0x7fffb04db420) at kernel/qapplication.h:526
#11 0x00007fd8a5482e94 in QETWidget::translateMouseEvent (this=0x6b0e00,
    event=0x7fffb04dba90) at kernel/qapplication_x11.cpp:4306
#12 0x00007fd8a5481510 in QApplication::x11ProcessEvent (this=0x7fffb04dbc90,
    event=0x7fffb04dba90) at kernel/qapplication_x11.cpp:3582
#13 0x00007fd8a5498106 in QEventLoop::processEvents (this=0x699660, flags=4)
    at kernel/qeventloop_x11.cpp:195
#14 0x00007fd8a550d5bf in QEventLoop::enterLoop (this=0x699660)
    at kernel/qeventloop.cpp:201
#15 0x00007fd8a550d2ab in QEventLoop::exec (this=0x699660)
    at kernel/qeventloop.cpp:148
#16 0x00007fd8a54f4e00 in QApplication::exec (this=0x7fffb04dbc90)
    at kernel/qapplication.cpp:2761
#17 0x00000000004276b2 in ?? ()
#18 0x00007fd8a1d201c4 in __libc_start_main () from /lib/libc.so.6
#19 0x000000000040e119 in ?? ()
#20 0x00007fffb04dbf48 in ?? ()
#21 0x0000000000000000 in ?? ()

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10?

Changed in kooldock:
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kooldock:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.