When one cut an item and paste it to another dir, the original file is still listed but it actually doesn't exist. If you try to delete it the system says it doesn't exist. The previously cutted file/folder disappears at refresh. STEPS TO REPRODUCE 1. Cut a folder/file or a file 2. Paste the cutted folder/file to another directory. 3. OBSERVED RESULT The cutted file is stilll there and it's listed by Dolphin but in reality it doesn't exist. It disappears at refresh. EXPECTED RESULT The cutted item should disappear once it's pasted to the desired directory. SOFTWARE/OS VERSIONS Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9
*** This bug has been marked as a duplicate of bug 387663 ***
But I've been having problems since a week ago or so. The bug you mensioned is from 2017.
(In reply to mozo from comment #2) > But I've been having problems since a week ago or so. The bug you mensioned > is from 2017. The symptoms are similar still. There is a fix in KF 5.106 that may fix your issue. Can you elaborate how is your dolphin window like when this happens ? Splitted views ? Tabs ? cut from one window pasting to another ? Is it always reproducible or only sometimes ? A screenshot or a video would be helpful too.
I'm using tabs. The problem does not occure when I use two separate Dolphin windows. https://imgur.com/a/98eBoF1 I just realized the problem occurs only in folders belong to the root drive.
The problem is not solved with KDE Frameworks 5.106.0.
(In reply to mozo from comment #5) > The problem is not solved with KDE Frameworks 5.106.0. How is your "Game" filesystem setup. "mount | grep Game" should tell me.
My "Game" is a EXT4 partition. mount | grep Game doesn't give any output. I mount it in fstab with: UUID=5c0092e3-2a55-4689-9355-d10b8a26dd96 /media/sde1 auto nosuid,nodev,noatime,nofail,x-systemd.device-timeout=10,x-gvfs-show 0 0 The problems doesn't occur in Dolphin 22.12.3 or older.
Oh, and I forgot - the bug occurs with every partition, not only the Game partition. The only mandatory condition in order to trigger the bug is one of the folders have to be from the system drive, e.g. home. In my case it's the Desktop folder but it can be any folder from the system drive.
(In reply to mozo from comment #7) > My "Game" is a EXT4 partition. > mount | grep Game doesn't give any output. > I mount it in fstab with: > UUID=5c0092e3-2a55-4689-9355-d10b8a26dd96 /media/sde1 auto > nosuid,nodev,noatime,nofail,x-systemd.device-timeout=10,x-gvfs-show 0 0 > > The problems doesn't occur in Dolphin 22.12.3 or older. I doubt that's the reason, either that a KDE Frameworks that regressed (which I doubt) either the bug only happens in certain circumstances which I am certain of since I can't reproduce it despite having a similar setup with several partitions. Btw did you make sure to restart all dolphin processes for your tests ? Or reboot ? If you launch dolphin using the command line, do you have anything output ? The last fix was very specific, yet easy to come across. Can you provide a Detailed step by step of how you get to see the bug, from the moment you opened dolphin (which settings you had), which folders you opened in which split view or tabs and in which order. A video can do the trick, showing from the startup of dolphin. The previous case now fixed was demonstrated by b2 in https://bugs.kde.org/show_bug.cgi?id=387663#c67 for instance. That the sort of information I need to fix your issue.
Hmm, thank you for helping me identifying my problem. I found it thanks to you! When I start Dolphin from Konsole, there's no problems at all. When I start Dolphin from the start menu - there's no problem as well. The funny thing here is the fact I ALWAYS start Dolphin from the home folder icon on my desktop and the bug occurs only then. I tried to open Dolphin with a directory: dolphin /home/mozo But the bug doesn't occurs. It's only there if I start it from the home folder icon on my desktop. It's not a big deal, I can always use a link and delete the home folder icon.
Can I close the bug or you want to identify the problem?
(In reply to mozo from comment #10) > Hmm, thank you for helping me identifying my problem. I found it thanks to > you! When I start Dolphin from Konsole, there's no problems at all. When I > start Dolphin from the start menu - there's no problem as well. The funny > thing here is the fact I ALWAYS start Dolphin from the home folder icon on > my desktop and the bug occurs only then. I tried to open Dolphin with a > directory: > dolphin /home/mozo > But the bug doesn't occurs. It's only there if I start it from the home > folder icon on my desktop. It's not a big deal, I can always use a link and > delete the home folder icon. I doubt that's this explains the issue. > Can I close the bug or you want to identify the problem? I wouldn't be answering if I didn't want to fix this issue. > The previous case now fixed was demonstrated by b2 in https://bugs.kde.org/show_bug.cgi?id=387663#c67 for instance. > That the sort of information I need to fix your issue. I'd like to have a similar video ideally. You can close the bug if you'd rather not go any further.
Sure but I can't start Dolphin from terminal for there aren't any bugs then. And it's not mandatory to use Game partition. The bug occurs everywhere.
Created attachment 158997 [details] Dolphin doesn't update view Also pay attention when I select cut the icon doesn't get greyed out as it should which is this bug: https://bugs.kde.org/show_bug.cgi?id=469322
(In reply to mozo from comment #14) > Created attachment 158997 [details] > Dolphin doesn't update view > > Also pay attention when I select cut the icon doesn't get greyed out as it > should which is this bug: > https://bugs.kde.org/show_bug.cgi?id=469322 Could you display the content of ~/Desktop/mozo.desktop I expect it to look like: 1 │ [Desktop Entry] 2 │ Icon=user-home 3 │ Name=meven 4 │ Type=Link 5 │ URL[$e]=file:$HOME I don't reproduce locally.
It's a link file to home here, not a desktop file and I can't open it with a text editor to see it's content. It may be an awkward solution to make it a link, but I don't think it should behave like that.
(In reply to mozo from comment #16) > It's a link file to home here, not a desktop file and I can't open it with a > text editor to see it's content. It may be an awkward solution to make it a > link, but I don't think it should behave like that. It is an important factor to report in this case. Which KF version are you using ? A similar bug was fixed in KDE Framework 107 https://bugs.kde.org/show_bug.cgi?id=469254 If you are not using KF 5.107 or later, does updating fix your issue ?
I didn't know it's a link for I deleted the link icon arrrows for my icon theme many years ago. I'm really sorry. No, KF 107 doesn't fix the issue.
(In reply to mozo from comment #18) > I didn't know it's a link for I deleted the link icon arrrows for my icon > theme many years ago. I'm really sorry. > > No, KF 107 doesn't fix the issue. I did reproduce the issue with KF 5.104 but not anymore with KF 5.108. if you update to 5.108 do you still reproduce ? You need to at least logout of your session for the update to be effective. You can check which version dolphin uses in Help > about dolphin > Components
Yes, the bug is still here with 5.108. I even restarted the mashine to no avail.
(In reply to mozo from comment #20) > Yes, the bug is still here with 5.108. I even restarted the mashine to no > avail. What is your distro ? Are you sure dolphin uses KF 5.108 ? (Help > about dolphin > Components)
I'm with Arch Linux. Yes, Dolphin uses KF 5.108.
For some reason I have holded Dolphin updates. With the latest Dolphin version there's no problem, thank you. There is actually one more related problem but I will use another icon to open Dolphin.
(In reply to mozo from comment #23) > For some reason I have holded Dolphin updates. With the latest Dolphin > version there's no problem, thank you. There is actually one more related > problem but I will use another icon to open Dolphin. Thank you for letting me know, mystery solved
Thank you :)
*** This bug has been marked as a duplicate of bug 469254 ***