| Summary: | Dolphin crashes after moving files by drag & drop | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] kio | Reporter: | Peter Urbanus <purbanus> |
| Component: | general | Assignee: | David Faure <faure> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | adawit, markg85 |
| Priority: | NOR | ||
| Version: | 4.5 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: |
new crashreport
crash report from 2010-11-28 |
||
|
Description
Peter Urbanus
2010-09-07 13:25:30 UTC
Just a guess, but did the file you dragged was one that was playing in the background? Could you provide detailed steps to reproduce this? Usually not. It just happened again minutes ago and it was not playing in the background. First I dragged a really big directory (23G) from my hard drive to a NAS, moving it. Then I dragged a much smaller set (500MB) to a different location on my hard drive, copying it. When I clicked on the source tab, Dolphin immediately disappeared and the crash dialog popped up. Do you want a new crash report? 2010/9/16 Mark <markg85@gmail.com> > https://bugs.kde.org/show_bug.cgi?id=250441 > > > Mark <markg85@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |markg85@gmail.com > > > > > --- Comment #1 from Mark <markg85 gmail com> 2010-09-16 00:27:23 --- > Just a guess, but did the file you dragged was one that was playing in the > background? > > Could you provide detailed steps to reproduce this? > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. > Yes, please do post a new crash log. Also please test this on the latest stable kde instead of the initial crash log against 4.4.2. Created attachment 51718 [details]
new crashreport
crashreport of 2010-09-16
interesting: #7 0x00007f6ac1f0a0a5 in ~KJob (this=0x2b68e50, __in_chrg=<value optimized out>) at ../../kdecore/jobs/kjob.cpp:67 #8 0x00007f6ac367ba09 in ~SimpleJob (this=0x2b68e50, __in_chrg=<value optimized out>) at ../../kio/kio/job.cpp:383 #9 0x00007f6ac367bb13 in ~DirectCopyJob (this=0x200000000, __in_chrg=<value optimized out>) at ../../kio/kio/job.cpp:1706 it seems to crash in a destructor in kio.. assuming the Qt core classes are fine. The crash is quite a bit different from your initial crash report. I don't know where this went wrong.. sending it to the KIO folks so they can look at it. I upgraded to 4.5.1 using http://linux-software-news-tutorials.blogspot.com/2010/08/install-kde-45-in-ubuntukubuntu-1004.html. The About... windows report 4.5.1 so I guess that worked. However, after some 20 move actions Dolphin crashed again. I'm generating a new crash report, but I lack some debug symbols and I don't see how I install them. It wants symbols for /usr/bin/dolphin /lib/libdbus-1.so.3 Can you help me out? install the -debug or -dev (or both) packages. (K)ubuntu must have them. I'm sorry, but I don't see how. The only packages for Dolphin that I can choose are dolphin dolphin-kde4 dolphin-plugins Nothing with -debug or -dev. And libdbus-1.so.3?? Dolphin is part of kdebase and uses libraries krom kdelibs so you need to have the kdelibs dev/debug packages and perhaps also the kdebase dev/debug psckage don't search for a dolphin dev/debug since you won't find any. Both kdelibs5-dbg and kdebase-dbg are at their latest versions (apt-get install xxx) but I still can't create crash reports. (In reply to comment #10) > Both kdelibs5-dbg and kdebase-dbg are at their latest versions (apt-get install > xxx) but I still can't create crash reports. then i'm out of options to suggest... After upgrading to 10.10, I can create crash reports again. I will attach a new one. I've noticed something else: it always happens when moving / copying files to samba shares. I have a NAS on which I use NFS and Dolphin never crashes. Created attachment 53833 [details]
crash report from 2010-11-28
Peter is this crash still present in KDE v4.10 or higher? See comment #14. I don't think so. Sorry but I haven't used KDE for a long time. From what I remember the problem went away just before I stopped using KDE. (In reply to comment #16) > I don't think so. Sorry but I haven't used KDE for a long time. From what I > remember the problem went away just before I stopped using KDE. Thanks for the repsonse. |