| Summary: | Konqueror crashes when you drop files on it | ||
|---|---|---|---|
| Product: | [Applications] konqueror | Reporter: | Anders E. Andersen <andersa> |
| Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | maksim |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Anders E. Andersen
2004-05-09 10:38:10 UTC
Backtrace? Also, can you please run it from a terminal, and see whether there is any error message when it crashes? I can provide neither a backtrace nor terminal output from here, because I can't currently reproduce the bug. I came here to add my two cents to this discussion at the behest (on kde-debian) of the person who submitted this report, however. Setting up a new Debian box a few days ago, I was attempting to demonstrate to a complete computer virgin how to drag and drop files. I remember this well, so the scenario itself is highly repeatable. That in of itself is useful. On one side, a view of ~ opened with the little default house icon every kicker is born with. On the other a Konqueror started with the little wheel/planet icon. (I mention this because, for example, the "konqueror" icon does not run /usr/bin/konqueror out of the box, but rather "kfmclient openProfile webbrowsing" It is my experience that this distinction sometimes matters.) The web browsing Konqueror goes: gg:lord of the rings wallpapers The first hit is: http://kebawe.com/LOTR/ From there, a series of links to the right, listed by size. Under C -> 1024x768 the following link: http://www.spinkamala.com/kebawe/LOTR/fellowship001_1024.jpg KDE's focus policy is set to follow the mouse. Click the above link, hold it for a moment until it becomes the little "dragging a file" icon. Move it out of its source window, over to the view of ~. The ~ view gets the focus, lights up, then segfaults before giving me a chance to drop the file. 100% of the time. As I said, it's not happening here. I just ran this test on my home box, and it worked fine. However, this was absolutely repeatable on the other machine. Both boxes are up to date Debian Sarge, both started as clean installs within a couple days of each other, but they have different individual components installed, and different hardware with different modules. Probably different kernels too, but they're both recent 2.4 series. I'll be over there later today, and I will attempt to generate some useful diagnostic info. There are no error messages in the terminal. It shouldn't be too difficult to reproduce this bug I think. It is most annoying when it happens immediately when you hover over the konqueror window with a file, but if it doesn't crash, you can provoke it by moving the icon away from the window and reentering it repeatedly. Just now I tried it about 10 times and the desktop reinitialized, but konqueror didn't crash. After 10-20 more attemts to enter the window while still dragging a file, konqueror finally crashed. I don't know if this backtrace is at all usefull without debug symbols, any suggestions for improvements are welcome: (no debugging symbols found)...Using host libthread_db library "/lib/tls/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)...[Thread debugging using libthread_db enabled] [New Thread 1095284128 (LWP 1538)] (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)...(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)...0x40fbe40e in __waitpid_nocancel () from /lib/tls/libpthread.so.0 #0 0x40fbe40e in __waitpid_nocancel () from /lib/tls/libpthread.so.0 #1 0x4073fe20 in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4 #2 <signal handler called> #3 0x40aca01b in QFont::QFont () from /usr/lib/libqt-mt.so.3 #4 0x40a70ce2 in QPainter::begin () from /usr/lib/libqt-mt.so.3 #5 0x40cd1666 in QIconView::drawDragShapes () from /usr/lib/libqt-mt.so.3 #6 0x082aad08 in ?? () #7 0x00000000 in ?? () #8 0x407df38e in posix_memalign () from /usr/lib/libkdecore.so.4 #9 0x00000000 in ?? () #10 0x082aad08 in ?? () #11 0xffffffff in ?? () #12 0x44495254 in ?? () #13 0xbfff0000 in ?? () #14 0x00000000 in ?? () #15 0x00000000 in ?? () #16 0x080d38e0 in ?? () #17 0x00000000 in ?? () #18 0x082c92f0 in ?? () #19 0x0806e4e8 in ?? () #20 0x081bb4e0 in ?? () #21 0x00000000 in ?? () #22 0x00000000 in ?? () #23 0x00000000 in ?? () #24 0x40f32f00 in vtable for QDir () from /usr/lib/libqt-mt.so.3 #25 0x00000000 in ?? () #26 0x00000000 in ?? () #27 0x40810b78 in ?? () from /usr/lib/libkdecore.so.4 #28 0x082aad58 in ?? () #29 0x00000000 in ?? () #30 0x00000000 in ?? () #31 0x407de736 in free () from /usr/lib/libkdecore.so.4 For my part, I made a mistake earlier. Dragging the icon over a window that doesn't have the focus does not cause it to claim the focus as stated previously. It remains backgrounded. I'm not sure if it matters, but I like to be precise. As to repeating the bug, I had no luck at all. I repeated the experiment two dozen times, and it worked perfectly two dozen times. So much for being able to reproduce this at will. It definitely *was* happening repeatably, but it must have been some random combination of factors that are no longer in evidence. Some stock config setting which has since been changed from its default perhaps. It could be practically anything. She uses the machine, so I can't turn it into a laboratory to try to see if I can reproduce it at a certain point from a clean install or whatever. Since I never actually use graphical file managers for anything anyway, I guess I'm out of this now. I tried. The last few steps of the bt look believable and relevant, thanks, and it's quite important that this is a real crash. Here is the reason I asked: some Qt versions (I am not sure exactly which ones) had a bug that would abort the app in some cases involving clipboard, and I think also DND (but I am not sure). It was important to know whether this is what was happening, or an another bug entirely. Looks like the same thing, please transfer your votes, though *** This bug has been marked as a duplicate of 71687 *** I'd say you are right. It's a dupe. |
