[Karmic] Dolphin drag and drop file copy not working

[Roland Hughes]

Binary package hint: dolphin

For years I have been using the technique of dragging my home directory to a directory on a USB drive to make a quick copy of everything so I can pick and choose what I want to load from my workstation to my notebook. This has always worked in both OpenSuSE and prior versions of Ubuntu. I just tried it tonight. Dolphin dies spastically erroring out in a seemingly random fashion. The file/directory which sends the copy to the great beyond differs, but Dolphin simply gives up the ghost.

This appears to be a bug which is more deeply rooted than Dolphin (but is not hardware related) since Konquerer fails as well. The drive works with other operating systems. I assume this has to do with all of the other USB problems in this release.

ProblemType: Bug
Architecture: i386
Date: Fri Nov 13 19:45:58 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: slamr
Package: dolphin 4:4.3.2-0ubuntu3
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: kdebase
Uname: Linux 2.6.31-14-generic i686

[Roland Hughes (original-seasoned-geek)]

Bug appears to be very deeply rooted. I created a directory on one of my 1TB SATA drives and attempted the same drag and drop copy with Dolphin. The machine hardlocked part way through. No magic key combination would get me out, it was the magic reset button...kind of like running Windows.

[Roland Hughes (original-seasoned-geek)]

This failed file copy has now left the entire directory tree of my 1TB drive locked by an unknown user. I can only access it in read-only mode. I have no idea how to clear this error. A reboot didn't clear it. I cannot find anything which looks like it might be a CP process running in the system monitor either.

I need to be able to write to that drive.

[Rohan Garg (rohangarg)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 482464, and any other logs that are relevant for this particular issue.

[Roland Hughes (original-seasoned-geek)]

I don't have any ability or desire to test 10.10. I'm only interested in a fix
for LTS. I won't be changing Ubuntu versions again until the next LTS, but I
will apply all updates to this version.

On Friday, June 25, 2010 05:21:08 pm you wrote:
> Thank you for taking the time to report this bug and helping to make Ubuntu
> better. We are sorry that we do not always have the capacity to look at
> all reported bugs in a timely manner. There have been many changes in
> Ubuntu since that time you reported the bug and your problem may have been
> fixed with some of the updates. It would help us a lot if you could test
> the current Ubuntu development version (10.10). If you can test it, and it
> is still an issue, we would appreciate if you could upload updated logs by
> running apport-collect 482464, and any other logs that are relevant for
> this particular issue.
>
> ** Changed in: kdebase (Ubuntu)
> Status: New => Incomplete

--
Roland Hughes, President
Logikal Solutions
(630)-205-1593
http://www.logikalsolutions.com
http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net

[Launchpad Janitor (janitor)]

[Expired for kdebase (Ubuntu) because there has been no activity for 60 days.]

[Roland Hughes (original-seasoned-geek)]

I retested this problem right now under KUbuntu 10.10 64-bit AMD and it has been fixed. There were only single file errors about links and akandi stuff which is as expected. The copy did not die spastically.