Anixx wrote:

I ended up doing it myself.

I gave you a link to the bugreport. Did you submit it again second time?

You gave me a link to a dolphin wishlist item about adding the feature, not to a konqueror bug report about the configuration option not working.

Anixx wrote:

In fact I routinely submit wishlist items for features I never intend to use because I feel they would be useful for others.

In that case you should not doubt spatial mode would be useful for others. Just consider how many users use it, and read the Gnome mailing list.

Just because someone uses it doesn't actually mean it is a good idea. I need some actual reasons why it should be used, as I keep saying over and over.

If you are willing to post links to the gnome mailing list discussions in question I would be happy to read them, but I don't really have time to go hunting through them right now since my opinion wouldn't change anything anyway.

You gave me a link to a dolphin wishlist item about adding the feature, not to a konqueror bug report about the configuration option not working.

I gave you the both links. Here is it: https://bugs.kde.org/show_bug.cgi?id=245874

Just because someone uses it doesn't actually mean it is a good idea.

Okay. Then those who use it will not use KDE4. This is simple.

Landis has a good point: He should be feeling the guilt of venting on this forum.

He should not be banned, though. I think this is unreasonable. Just ask him to vent elsewhere and refrain from harsh language (maybe there should be a venting forum ) He expressed regrets and made note that he really wasn't trying to offend anyone. Just point out that he did, and let him be.

Here is what Landis should have done. He should have taken this list of quite reasonable issues and simply pointed out his perception of a long list of unreasonable shorcomings. Then he he should have dispassionately expressed them making comparisons to Konqueror along the way. He could state strong dislike for the substitute.

BTW, a note on the pat answer of "the KDE user community decided it." It is completely fair to point out that this response can be viewed as disingenuous. It is no secret that a substantial portion of the KDE community has felt left behind by this new track of KDE. Dolphin *is* a simpler utility and it is hard to dispute this.

The most important fact though, and Landis should be aware of this, is that the portion of the KDE community that is actually putting in the time to develop KDE is who decided its future course. These are the people that count, and insulting their monumental efforts is simply inappropriate.

I think that Landis actually understands this. This may be why he kept noting that he wasn't a developer.

I loved the old KDE and Konqueror. I understand the frustration. What Landis should realize is that the new version and future track, KDE4, is a paradigm shift towards a modular and highly configurable UI. More on this in a follow-on post.

Anixx wrote:

You gave me a link to a dolphin wishlist item about adding the feature, not to a konqueror bug report about the configuration option not working.

I gave you the both links. Here is it: https://bugs.kde.org/show_bug.cgi?id=245874

I missed that somehow.

Anixx wrote:

Just because someone uses it doesn't actually mean it is a good idea.

Okay. Then those who use it will not use KDE4. This is simple.

Or, they could use a different file manager under KDE 4.

Or, they could use a different file manager under KDE 4.

Apparently, a non-KDE file manager.

This becomes ridiculous: to make the desktop acceptable, one he has to use a non-KDE file manager, non-KDE desktop handler and non-KDE panel. Only then it becomes usable. But taking all these parts from a non-KDE source would mean actually that one uses some other desktop rather than KDE, even if with KDE apps.

ttreker wrote:He should not be banned, though. I think this is unreasonable.

You don't get banned here for expressing your opinions. You will eventually get banned, however, if you repeatedly break the and ignore warnings from moderators/managers/administrators.

@Anixx and TheBlackCat:

How about leaving the discussion behind us? Anixx wants a spatial file manager, Dolphin isn't one - I don't see any point in discussing it further.

I wasn't replying to anyone other than the original post.

Yeah, OK. I am not the forum admin. I don't have to keep the order. Won't argue with any choices to ban

How does the move towards "highly configurable" Dolphin help lost files?.

Large file transfers are highly problematic and from first hand experience they result in lost files. Tried KDE4 about 6 mos. ago and didn't care for it then. Decided to give a second go and recently losing many files in a large transfer proves Dolphin (recent release) not capable of production quality work.

Not really interested in the ability to move widgets and buttons around. Not interseted in many of the "must have " features touted in Dolphin. What I need is a reliable file MANAGER. I believe Dolphin is an ok file viewer at this point.

Parts of Konqueror that I DID NOT USE WERE NEVER IN THE WAY. The alleged bloated parts of Konq never kept me from doing what I needed. I need a production quality file manager. For production quality work it's konqueror, krusader and grsync for now.

MicroSoft has already beaten KDE4 to the punch in releasing alpha software AND charging for it. Granted KDE is not delivering a pay for product but that should be no excuse. Why copy MS? If I wanted stuff that didn't work I would have stuck with MS.

Directories in a large file transfer from ext. drive to an onboard drive show up bu the files are missing. fortunately I have the originals, but it could have been a disaster and in a sense it is b/c if it reared it's ugly head this far along into development, that means it's just waiting to happen to someone else and it WILL be a disaster for them !

Sorry Dolphin lovers. I'm sure there is a workaround, a reason, but this is definitely a show stopper for Dolphin and KDE4 ( Digikam also has issues).

Have saved up all my KDE3.5 repo software and will be moving back to what works until KDE4 is sorted out.

I've never had issues with Dolphin (or Konqueror) transferring large amounts of data, or many files.
I suggest you check the notifications area to see if the task in question is still being executed prior to blindly removing external media (there is a safe eject procedure, which should be followed)

Who said anything about blindly ejecting the device? I always unmount partitions.

No notification popup was observed and no HDD activity on either device was observed. Just "poof ". The directories are there but no files. Fortunately I have the originals but this is a REAL show stopper. Will give it a go again but confidence in Dolphin is damaged.

There are several threads about this and bug reports about problems with kio slaves and /or refresh issues. Still not good for production use.



This is confirmed in OpenSuse forums and over in my distro forums as well.

Eye candy and configurability take a back seat to reli - ability.

If the problem is widespread, I would be extremely surprised if the developers had not investigated. Has anyone filed a bug in the KDE Bug tracker with clear and complete instructions (including a list of possible file names and sizes) needed to reproduce?

Purposely posted in this thread b/c this is not a dispassionate attempt at finding out if, how, or why Dolphin did what it did. This is a reaction to a broken trust. This is not the place to expound on the technical aspects of the issue. It would be in a bug report. I will, given time, see if I can reproduce the issue given all the variables involved, but I run a business and tinkering with getting such an integral part of computer usage (file management) to be reliable is not within an end user's skills.

The point is that a software this far along in development and so integral to the purpose of a desktop system should be much more robust. Since the incident I have begun to recall incidents of even konqueror mishandling file transfers thinking they were due to my relative inexperience with linux, but now confirming those incidents through google searches. With all that experience behind the K applications, why would anyone have anything BUT trust? Now Dolphin is touted as the natural progression of all that experience invested in a "better" file manager?

No, this is a mini-rant about the expectation of service-ability that has been damaged at least on the surface. What does the developer expect out of the relationship with the end user? Blind acceptance of everything they throw out there? From the developers standpoint I know they invest huge amounts of time and effort. I do too. I will do my part as an end user to help the community to do better through feedback and bug reports.

This is merely an opinion that devs can use to gauge initial reaction to their handiwork, and if there is a workaround or a good reason for what happened, it lessens that damage but gives pause for future recommendations of the "solid and stable" moniker opensource is holding out as a trademark.

https://bugs.kde.org/show_bug.cgi?id=162211

Edit: I had the wrong bug the first time. This still hasn't been fixed.

I tried with a FAT32 formatted Flash Drive, copied a git repository (consisting of 1908 files, consuming 48mb of space), then verified the file counts as follows:

Code: Select all

find k3b/ | wc -l

In addition, I asked git to both give me a log of all items, which it did without error. Dolphin/Konqueror copied this data perfectly.

(If you're wondering, yes I did eject the media safely, then reconnected it when performing these tests)

Once you have ejected it, make sure the device is properly ejected (check in output of "mount")

And similar issue here -->https://bugs.kde.org/show_bug.cgi?id=165365

The more I look at this the more I recall incidents on various machines using different hdwr using konq as well. Apparently these issues have been around a while.