Bug 71309 - crashes when dragging url
Summary: crashes when dragging url
Status: RESOLVED DUPLICATE of bug 61412
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-27 15:18 UTC by Christian Loitsch
Modified: 2004-02-18 16:56 UTC (History)
0 users

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 Christian Loitsch 2003-12-27 15:18:14 UTC
Version:            (using KDE KDE 3.1.94)
Installed from:    Gentoo Packages
Compiler:          gcc 3.3.2 gcc (GCC) 3.3.2 20031201 (Gentoo Linux 3.3.2-r4, propolice)
OS:          Linux

when dragging the icon of a page (for instance the kde logo) from the url-bar down! konq crashes instantly.  On the other hand dragging it upwords does nothing.

(I noticed this bug when I wanted to drag an url into my bookmark-bar)
Comment 1 Christian Loitsch 2003-12-27 15:19:37 UTC
bt:
(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)...
(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 16384 (LWP 30136)]
0x410bc9a8 in waitpid ()
   from /lib/libpthread.so.0
#0  0x410bc9a8 in waitpid () from /lib/libpthread.so.0
#1  0x4080004c in __JCR_LIST__ () from /usr/kde/3.2/lib/libkdecore.so.4
#2  0x4073c41e in KCrash::defaultCrashHandler(int) ()
   from /usr/kde/3.2/lib/libkdecore.so.4
Comment 2 Frerich Raabe 2003-12-28 15:18:54 UTC
I don't understand what you did to make this crash happen. Can you maybe give a step-by-step guide (starting from e.g. "Start Konqueror") on how to do this?
Comment 3 Christian Loitsch 2003-12-29 17:48:12 UTC
goto www.kde.org
a kde logo appears on the left side of http://www.kde.org (in the location tool bar)
klick on this logo (don't release) and drag it.  If you drag it upwords for instance near the "normal" menu and drop it, nothing happens.  If you drag it downwords, for instance near the status line, konq will crash.

Comment 4 Edmondo Tommasina 2003-12-29 18:44:44 UTC
Interesting crash. I can reproduce something similar with CVS 20031227, but not always. I open 2 separated session of konqueror and start to drag the URL of the first window wildly through the screen. I can crash the second window of konqueror without dropping on it (just dragging for some time on it). The backtraces are always a bit different. I believe something is wrong in the QT dnd. I tried to catch some interesting information that can help a bit.

VALGRIND:
(...)
==7541==
==7541== Invalid read of size 1
==7541==    at 0x40E4C3E0: qt_xdnd_obtain_data(char const*) (in /usr/lib/qt-3.2.1/lib/libqt-mt.so.3.2.1)
==7541==    by 0x40E4C730: QDropEvent::encodedData(char const*) const (in /usr/lib/qt-3.2.1/lib/libqt-mt.so.3.2.1)
==7541==    by 0x40EAF875: QUriDrag::decode(QMimeSource const*, QStrList&) (in /usr/lib/qt-3.2.1/lib/libqt-mt.so.3.2.1)
==7541==    by 0x40B6E350: KURLDrag::decode(QMimeSource const*, KURL::List&) (kurldrag.cpp:74)
==7541==    Address 0x44 is not stack'd, malloc'd or free'd
(...)

BACKTRACE:
0x4143e2f9 in __wait4 () from /lib/libc.so.6
#0  0x4143e2f9 in __wait4 () from /lib/libc.so.6
#1  0x4143e2a7 in __libc_waitpid (pid=7377, stat_loc=0xfffffe00, options=0)
    at ../sysdeps/unix/sysv/linux/waitpid.c:26
#2  0x4124ebb3 in waitpid (pid=7377, stat_loc=0x0, options=0)
    at wrapsyscall.c:181
#3  0x408f0754 in KCrash::defaultCrashHandler(int) (sig=11) at kcrash.cpp:246
#4  <signal handler called>
#5  0x40c1e3e0 in qt_xdnd_obtain_data(char const*) ()
   from /usr/lib/./libqt-mt.so.3
#6  0x40c1e731 in QDropEvent::encodedData(char const*) const ()
   from /usr/lib/./libqt-mt.so.3
#7  0x40c81876 in QUriDrag::decode(QMimeSource const*, QStrList&) ()
   from /usr/lib/./libqt-mt.so.3
#8  0x40940351 in KURLDrag::decode(QMimeSource const*, KURL::List&) (e=0x0,
    uris=@0xbfffe720) at kurldrag.cpp:74
#9  0x4006dcd3 in KonqView::eventFilter(QObject*, QEvent*) (this=0x82a5f80,
    obj=0x82c7730, e=0xbfffebc0) at konq_view.cc:1153
#10 0x40cccc9e in QObject::activate_filters(QEvent*) ()
   from /usr/lib/./libqt-mt.so.3
#11 0x40cccbcc in QObject::event(QEvent*) () from /usr/lib/./libqt-mt.so.3
#12 0x40d040bf in QWidget::event(QEvent*) () from /usr/lib/./libqt-mt.so.3
#13 0x40c73a2f in QApplication::internalNotify(QObject*, QEvent*) ()
   from /usr/lib/./libqt-mt.so.3
#14 0x40c7303b in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/./libqt-mt.so.3
#15 0x4084b73d in KApplication::notify(QObject*, QEvent*) (this=0xbffff3f0,
    receiver=0x82c7730, event=0xbfffebc0) at kapplication.cpp:503
#16 0x40c1c288 in qt_handle_xdnd_position(QWidget*, _XEvent const*, bool) ()
   from /usr/lib/./libqt-mt.so.3
#17 0x40c0aac2 in QApplication::x11ClientMessage(QWidget*, _XEvent*, bool) ()
   from /usr/lib/./libqt-mt.so.3
#18 0x40c0bb46 in QApplication::x11ProcessEvent(_XEvent*) ()
   from /usr/lib/./libqt-mt.so.3
#19 0x40c212e1 in QEventLoop::processEvents(unsigned) ()
   from /usr/lib/./libqt-mt.so.3
#20 0x40c87236 in QEventLoop::enterLoop() () from /usr/lib/./libqt-mt.so.3
#21 0x40c870e8 in QEventLoop::exec() () from /usr/lib/./libqt-mt.so.3
#22 0x40c73c71 in QApplication::exec() () from /usr/lib/./libqt-mt.so.3
#23 0x4005917c in kdemain (argc=0, argv=0x0) at konq_main.cc:184

Comment 5 Christian Loitsch 2003-12-29 22:23:51 UTC
I can reproduce mine anytime i want.

This time I got a better bt (but as I don't have debugging symbols it's still not very useful:

(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)...
(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 16384 (LWP 4662)]
0x410bc9a8 in waitpid ()
   from /lib/libpthread.so.0
#0  0x410bc9a8 in waitpid () from /lib/libpthread.so.0
#1  0x4080004c in __JCR_LIST__ () from /usr/kde/3.2/lib/libkdecore.so.4
#2  0x4073c41e in KCrash::defaultCrashHandler(int) ()
   from /usr/kde/3.2/lib/libkdecore.so.4
#3  0x0864e768 in ?? ()
#4  0x00000028 in ?? ()
#5  0x00370036 in ?? ()
#6  0xbfffc900 in ?? ()
#7  0x0864e768 in ?? ()
#8  0x000017a8 in ?? ()
#9  0x00000400 in ?? ()
#10 0x00000400 in ?? ()
#11 0x0864e768 in ?? ()
#12 0xbfffc970 in ?? ()
#13 0xbfffc928 in ?? ()
#14 0x411b5b63 in operator delete(void*) ()
   from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/libstdc++.so.5
Comment 6 Edmondo Tommasina 2004-01-13 22:26:58 UTC
I've done a big upgrade of my kde installation with the lastest cvs code.
Maybe more important i've updated the qt library from the qt-3.2.x to the qt-copy in the cvs server (qt-3.3.0xx).
After all of this work I cannot reproduce the error anymore.

Have you the possibility and the time to upgrade your qt version? (or maybe retest when kde rc1 is here with us)
Comment 7 Christian Loitsch 2004-01-14 02:29:43 UTC
unrelated to this bug, i already emerged qt-3.3-beta on my machine, but after that kde was not useable any longer (i guess everything depending on qt needs to be recompiled as well, which i did not want to do).

we have quite an important visit next week (investor), so until then i don't have much time.  (feel free to remind me in ~10 days)
Comment 8 Christian Loitsch 2004-01-14 15:32:07 UTC
I really don't know why, but it works now.  (I never retested)
If this helps, I think that before my icon never changed (when moving upwords) --> only stayed the kde-logo but without the link-logo   (but I am not 100% sure)
Comment 9 Waldo Bastian 2004-02-18 16:56:44 UTC

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