Version: 3.2.91 (using KDE 3.2.91 (3.3 beta1), SuSE) Compiler: gcc version 3.3.3 (SuSE Linux) OS: Linux (i686) release 2.6.5-7.95-default Drag one link from Konqueror to the desktop. The progress bar start. Drag another link, holding the mouse over this progress bar, without releasing the mouse button. When the progress bar disappears, the mouse cursor don't change back. You can solve it with ESC and a few mouse moves/clicks.
In testing this out I got konqueror to crash. I tried again and I got a 2nd crash. Crashed with signal 11. Here's the backtrace. I'm running kde 3.3.1 compiled from source. ####################################################### Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1096008928 (LWP 3072)] [KCrash handler] #3 0x40b605b6 in QETWidget::translateConfigEvent () from /usr/share/qt3/lib/libqt-mt.so.3 #4 0x40b5bd4e in QApplication::x11ProcessEvent () from /usr/share/qt3/lib/libqt-mt.so.3 #5 0x40b721a4 in QEventLoop::processEvents () from /usr/share/qt3/lib/libqt-mt.so.3 #6 0x40bdaf28 in QEventLoop::enterLoop () from /usr/share/qt3/lib/libqt-mt.so.3 #7 0x40bc8e81 in QApplication::enter_loop () from /usr/share/qt3/lib/libqt-mt.so.3 #8 0x40b6f4ca in QDragManager::drag () from /usr/share/qt3/lib/libqt-mt.so.3 #9 0x40bd24f8 in QDragObject::drag () from /usr/share/qt3/lib/libqt-mt.so.3 #10 0x40bd2437 in QDragObject::drag () from /usr/share/qt3/lib/libqt-mt.so.3 #11 0x41a8a933 in KHTMLPart::khtmlMouseMoveEvent (this=0x8260218, event=0x84ca4f0) at khtml_part.cpp:5801 #12 0x41a88747 in KHTMLPart::customEvent (this=0x8260218, event=0xbfffe550) at khtml_part.cpp:5321 #13 0x40c22d3c in QObject::event () from /usr/share/qt3/lib/libqt-mt.so.3 #14 0x40bc8bcf in QApplication::internalNotify () from /usr/share/qt3/lib/libqt-mt.so.3 #15 0x40bc81ce in QApplication::notify () from /usr/share/qt3/lib/libqt-mt.so.3 #16 0x40772b33 in KApplication::notify (this=0xbffff530, receiver=0x8260218, event=0xbfffe550) at kapplication.cpp:495 #17 0x41a4fd8c in KHTMLView::viewportMouseMoveEvent (this=0x83f1860, _mouse=0xbfffec30) at khtmlview.cpp:1003 #18 0x40d3a7eb in QScrollView::eventFilter () from /usr/share/qt3/lib/libqt-mt.so.3 #19 0x41a51db4 in KHTMLView::eventFilter (this=0x83f1860, o=0x88d2b98, e=0xbfffec30) at khtmlview.cpp:1685 #20 0x40c22e5e in QObject::activate_filters () from /usr/share/qt3/lib/libqt-mt.so.3 #21 0x40c22d8c in QObject::event () from /usr/share/qt3/lib/libqt-mt.so.3 #22 0x40c5b60f in QWidget::event () from /usr/share/qt3/lib/libqt-mt.so.3 #23 0x40bc8bcf in QApplication::internalNotify () from /usr/share/qt3/lib/libqt-mt.so.3 #24 0x40bc82c4 in QApplication::notify () from /usr/share/qt3/lib/libqt-mt.so.3 #25 0x40772b33 in KApplication::notify (this=0xbffff530, receiver=0x88d2b98, event=0xbfffec30) at kapplication.cpp:495 #26 0x40b5d640 in QETWidget::translateMouseEvent () from /usr/share/qt3/lib/libqt-mt.so.3 #27 0x40b5b2ce in QApplication::x11ProcessEvent () from /usr/share/qt3/lib/libqt-mt.so.3 #28 0x40b721a4 in QEventLoop::processEvents () from /usr/share/qt3/lib/libqt-mt.so.3 #29 0x40bdaf28 in QEventLoop::enterLoop () from /usr/share/qt3/lib/libqt-mt.so.3 #30 0x40bdadd8 in QEventLoop::exec () from /usr/share/qt3/lib/libqt-mt.so.3 #31 0x40bc8e21 in QApplication::exec () from /usr/share/qt3/lib/libqt-mt.so.3 #32 0x4167906c in kdemain (argc=120, argv=0x78) at konq_main.cc:204 #33 0x4094c906 in kdeinitmain (argc=120, argv=0x78) at konqueror_dummy.cc:2 #34 0x0804cc46 in launch (argc=2, _name=0x807ada4 "konqueror", args=0x807adb7 "\001", cwd=0x0, envc=1, envs=0x807adc8 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x78 <Address 0x78 out of bounds>) at kinit.cpp:599 #35 0x0804e2b1 in handle_launcher_request (sock=8) at kinit.cpp:1163 #36 0x0804e7fd in handle_requests (waitForPid=0) at kinit.cpp:1364 #37 0x0804f962 in main (argc=3, argv=0xbffffc64, envp=0x78) at kinit.cpp:1817
still valid for 3.4.0, marking crash.
Could this also be a dup of #141221? Or maybe of #159443? Really not sure.
*** This bug has been marked as a duplicate of bug 141221 ***