While it may not appear logical, retrieving the free space in the user interface update code may cause the application to totally hang while the free space information is retrieved. This could take a short while if the media is not immediately accessible - such as a optical drive which has spun down, or a hard disk which has gone into power saving mode - and disrupts the user experience.

Rob5 wrote:No technical solution to replace a hack by something which is not a hack, then feature removed.
Not really user oriented I think.

IMHO, having a non-essential feature that can block the entire application without any reason that would be obvious to the user is not exactly user-oriented either. If there is no straightforward alternative, removing it is the best option IMHO, especially if you consider that there are other ways to see how much free space there is on a device.

BTW, I would appreciate it if you would not try to attract more attention to this topic by filing nonsense reports about "Warez » The message contains links to illegal or pirated software.". Thank you for your understanding.

freininghaus wrote:BTW, I would appreciate it if you would not try to attract more attention to this topic by filing nonsense reports about "Warez » The message contains links to illegal or pirated software.".

What's up ? ? ? ? ? I am not responsible at all of this. Read again my messages. The forum is may be hacked, but not by myself.

"having a non-essential feature that can block the entire application without any reason that would be obvious to the user is not exactly user-oriented either"
Where did you find this ?
Can you find a bug report on that one ?

Rob5 wrote:

freininghaus wrote:BTW, I would appreciate it if you would not try to attract more attention to this topic by filing nonsense reports about "Warez » The message contains links to illegal or pirated software.".

What's up ? ? ? ? ? I am not responsible at all of this. Read again my messages. The forum is may be hacked, but not by myself.

If I'm not mistaken, the forum system told me that you have reported this topic, but I have deleted the report in the mean time. Maybe I interpreted the report wrong - in that case, sorry.

Rob5 wrote:"having a non-essential feature that can block the entire application without any reason that would be obvious to the user is not exactly user-oriented either"
Where did you find this ?
Can you find a bug report on that one ?

I don't think that I really have to spend my free time convincing disbelieving users, but just to prevent that people get the impression that I'm making this all up, one example is here: https://bugs.kde.org/show_bug.cgi?id=316655

I think that all that is relevant has been said now, so I will not post further replies here.

Either the "forum system" told you wrong things, or your "warez story" is purely invented by yourself.
It might even happen that a user just pushes the "Report this post" by mistake, and you should read the post before referring to "warez".

But I hope that on this forum, we can find also "real users", and not only "administrators", "moderators" or a virtual "forum system" user.
This could contribute to make KDE more user oriented, less than developer oriented, but this remark is beyond this topic.

Rob5 wrote:Either the "forum system" told you wrong things, or your "warez story" is purely invented by yourself.
It might even happen that a user just pushes the "Report this post" by mistake, and you should read the post before referring to "warez".

It appears that this "warez" message is what is used as the report subject by default when you just click "Report this post" and then click submit. I'm not saying that you did that - as I said, I deleted the report (I will definitely never do this with any future reports, it seems that there is no way to restore them), and I apologize if my claim that you reported anything was incorrect.

Here's a patch to re-add it: https://phabricator.kde.org/D21312