I've upgraded from Dolphin 22.08.1 to 24.02.0 and I've noticed that the copy dialog has disappeared completely. I don't like notifications so I have them switched off in neon. They can't be moved around like a dialog and if you have multiple copy operations then they stack vertically and take up space, where you can move multiple dialogs out of the way onto a separate monitor and have them cascade. For whatever reason the copy dialog has disappeared on updating Dolphin. STEPS TO REPRODUCE Copy using 22.08.1 without notifcations on -> Copy dialog appears Copy using 24.02.0 without notifcations on -> Copy dialog is not present
*** Bug 483023 has been marked as a duplicate of this bug. ***
Same here, I wish it back if there's a way. Thanks.
Updated to 24.02.1 which fixed an issue with Places being hidden after minimize which cause a lot of people to notice. But this issue still remains. I get that most people use Dolphin out of the box with no customization but the copy dialog missing is a much more important fix than losing the places panel. At least let us know that this is a bug and not an actual design choice because the silence is concerning.
^ This! For me Dolphin is unusable without this dialog. This is the only reason I used a backup and now I'm on Plasma 5 again. I eagerly awaiting someone will here us so we have a fix.
Here's another post about this on Reddit - https://www.reddit.com/r/kde/comments/1c9jkwf/kde_plasma_6_dolphin_file_copy_progress_bar/ One of the developers chimed in with this link: https://invent.kde.org/frameworks/kio/-/merge_requests/1514 ...saying this is a known regression since Plasma 5 & he hasn't had time to fix. Hopefully a fix is coming soon, I also find this extremely problematic.
The same issue occurs in my configuration: Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-arch1-2 (64-bit) Graphics Platform: X11 Dolphin version: 24.02.2
Same issue here. It's a little distressing that such a vital component was left out of Plasma 6. I might be interested in creating a regression test for this sort of thing in the future. Arch Linux Dolphin 24.02.2 KDE Framework 6.10 QT 6.7.0 Kernel 6.8.9-arch1-2 Graphics platform X11
I have to agree with kde@dickbag.org, it's alarming that such an integral piece of software has regression issues at all. I feel that only the most senior developers should have access to Dolphin. Unfortunately, this bug report isn't the only one, prior to this the panels were removed when minimizing to the desktop. That was fixed quickly because everyone noticed regardless of their OS settings, but it should have never have been released because basic testing would have caught it. I've used Dolphin for years and have only seen improvements, however something has happened recently to have these kind of embarrassing issues crop up. Testing needs to be tightened and responses to regression issues needs to be prioritised (regression should be caught at the pull request level). Unfortunately it seems like only the bugs that make noise get any attention, so if you have the same issue please leave a constructive comment.
"I've used Dolphin for years and have only seen improvements, however something has happened recently to have these kind of embarrassing issues crop up. Testing needs to be tightened and responses to regression issues needs to be prioritised (regression should be caught at the pull request level). Unfortunately it seems like only the bugs that make noise get any attention, so if you have the same issue please leave a constructive comment." There are convos for years but things doesn't getting any better. QA is bad and is worsening. There are absurd bugs which doesn't be even in alpha release.
Created attachment 170849 [details] Copy Dialog Plasma 6 For me, the dialog appeared quite surprisingly when I copied a file with a size of more than 200 GB. So it's there but not always shown unlike notifications which are always shown when copying (if set to use notifications) Unfortunately it didn't show up anymore no matter how much I copied a large file My system is: Operating System: Arch Linux KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.5-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 125.7 GiB of RAM Graphics Processor: AMD Radeon RX 6500 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7D54 System Version: 1.0
Comment on attachment 170849 [details] Copy Dialog Plasma 6 For me, the dialog appeared quite surprisingly when I copied a file with a size of more than 200 GB. So it's there but not always shown unlike notifications which are always shown when copying (if set to use notifications) Unfortunately it didn't show anymore no matter how much I tested copying with a large file.
For me, the dialog appeared quite surprisingly when I copied a file with a size of more than 200 GB. So it's there but not always shown unlike notifications which are always shown when copying (if set to use notifications) Unfortunately it didn't show anymore no matter how much I tested copying with a large file.
I apologize for the repeated comment - I was looking for the comment at the top, I didn't know that the newest comments are at the bottom, and that's why I posted it twice. Please delete the duplicates
Thanks cprog! So there's a dialog and we have to only find a way how to turn it on. Sounds great but let's see what the devs have to say.
Is there any progress on this important issue? Why the silent?
It's bad enough that you didn't test properly and pushed out an update that removes an essential part of the program, but the sheer lack of concern that it even occurred is sickening. The fastest and easiest way to fix a bug is to get on it immediately and assign the person who created the regression to fix it. It's clear that you didn't test properly, so it was up to us to write the bug report and it was done in a timely manner. Now it's months old and it's going to take even longer to undo the bug because the person who created it has long forgotten about it and moved on to more 'important' code. Here's something to think about, if a developer pushes an update and it's confirmed to break existing functionality, then that update gets rolled back until the developer in charge of the update fixes the regression. Otherwise the update never gets added. Whoever caused this should not be allowed to work on anything else until this is fixed, but that would require someone in charge and it's becoming painfully clear that no-one here is.
Yeah I'm really not following this practice either. If you can't be bothered to fix a regression you introduced, just revert whichever of your changes broke it. It's been five and a half months since this was reported... I suggest you try replying to the developer on Reddit, seems to be more responsive over there...
I'm really sad about the direction KDE took... Nobody cares, nobody answers, I have to write on Reddit to contact a developer who don't care about an awful regression at all? I mean, really??? What is the point of having a bug tracker then? What's the point of all the boasts how Plasma is super tested? And It's about simple things like a file dialog! You can't publish a file manager in this condition yet we have a stable version and numerous minor versions afterwards. And nobody wants to fix this and they are killing us with silence. Why? Why did Plasma team get did bad? Social presence can't substitute QA, remember it! Now let's try to wake up the developer who did this sh*t to us on Reddit... Repeat - on Reddit! Shame on you!
Have the same issue, this really needs to be fixed, thank you Operating System: Arch Linux KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.10-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 20 × 13th Gen Intel® Core™ i7-13700H Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: LENOVO Product Name: 21JN00DLBM System Version: ThinkPad E16 Gen 1
+1 The same issue is observed on my end. It's highly impactful, so if possible, please look into it with priority Operating System: Manjaro Linux KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.6.41-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7400T CPU @ 2.40GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 Manufacturer: LENOVO Product Name: 90HC0012UK System Version: ideacentre 620S-03IKL
https://invent.kde.org/frameworks/kio/-/merge_requests/1514 and https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3690 merged
(In reply to Bharadwaj Raju from comment #21) > https://invent.kde.org/frameworks/kio/-/merge_requests/1514 and > https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3690 merged Is our drea, happening right now? I can't believe this! Thank you very, very much Bharadwaj Raju! When should we await it? Plasma 6.1.5 or later?
Well, depends on whether it gets cherry-picked to the 6.1.5 branch. I've asked about it, let's see.
Unfortunately not — this requires a KIO change which will only be in KF 6.2, and only Plasma 6.2 can depend on stuff from KF 6.2
12.09 isn't too far at all. The most important part is, we finaly have this beauty thanks to you. Thank you once again!
I just tested in Plasma 6.2 and it's beautiful. Thank you very much!
I'm not going to be so thankful, this should have never happened in the first place and the response to this integral program has been beyond abysmal. The code has been fixed but the months of no contact has spoken volumes. Adobe would at have at least responded, and not via reddit. The communication is nowhere near good enough, never mind the fact that the changes should have never been merged in the first place. No one from KDE will ever read this because no one is at the wheel. That is pretty terrifying.
(In reply to jimbo from comment #27) > I'm not going to be so thankful, this should have never happened in the > first place and the response to this integral program has been beyond > abysmal. The code has been fixed but the months of no contact has spoken > volumes. Adobe would at have at least responded, and not via reddit. The > communication is nowhere near good enough, never mind the fact that the > changes should have never been merged in the first place. No one from KDE > will ever read this because no one is at the wheel. That is pretty > terrifying. I wasn't thrilled about it either but this kind of response doesn't help anyone. This is an open source project. There's no scenario whatsoever in which a comparison between the KDE project and Adobe makes any sense. Get a grip. Thanks devs for resolving this.
Not fully resolved, should have been caught by the developer during basic development testing. https://bugs.kde.org/show_bug.cgi?id=494648