Created attachment 179332 [details] stack info Using the dolphin file manager, when copying large files from the samba server to the desktop, disconnecting from the network and re-copying the files causes the entire plasma desktop to get stuck. The entire desktop does not respond to mouse events, but with dolphin file manager, it still works fine. STEPS TO REPRODUCE 1. Using the dolphin file manager, open the samba server link 2. When copying large files from the samba server to the desktop, disconnecting from the network 3. Re-copying the files OBSERVED RESULT The entire plasma desktop to get stuck, The entire desktop does not respond to mouse events, but with dolphin file manager, it still works fine. EXPECTED RESULT Desktop works fine SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: 5 KDE Frameworks Version: plasma-workspace=4:5.27.5-2 , plasma-desktop=4:5.27.5-2 , plasma-framework=5.103.0-1+deb12u1 Qt Version: 5.15.8 ADDITIONAL INFORMATION When copy a file kiowork, There seems to be an anomaly in kio.
Copying large files eg：debian-live-12.5.0-amd64-kde.iso， size: 3.25 GB There seems to be an anomaly in kioworker.
Can you please copy and paste the stack trace into this report, or paste it as a text file? Also, can you share the full Plasma version? (e.g. 5.27.xx) There's an old closed bug with similar behavior, but that was thought resolved - bug 409392. It was related to NetworkManager
Hello： KDE Plasma Version: 5 KDE Frameworks Version: plasma-workspace=4:5.27.5-2 , plasma-desktop=4:5.27.5-2 , plasma-framework=5.103.0-1+deb12u1 Stack trace is already in Attachements (attachment 179332 [details])
Hello： KDE Plasma Version: 5 KDE Frameworks Version: plasma-workspace=4:5.27.5-2 , plasma-desktop=4:5.27.5-2 , plasma-framework=5.103.0-1+deb12u1 Stack trace is already in Attachements (attachment 179332 [details]), Does this attachment help to analyze the causes? The problem doesn't seem to have anything to do with Networkmanager, it's mostly KioWorker related.
Hello： Full Plasma version ii kdeplasma-addons-data 4:5.27.5-2+m2 all locale files for kdeplasma-addons ii libkf5plasma-doc 5.103.0-1+deb12u1-m59 all Plasma Runtime components (documentation) ii libkf5plasma5:amd64 5.103.0-1+deb12u1-m59 amd64 Plasma Runtime components ii libkf5plasma5-dbgsym:amd64 5.103.0-1+deb12u1-m59 amd64 debug symbols for libkf5plasma5 ii libkf5plasmaquick5:amd64 5.103.0-1+deb12u1-m59 amd64 Plasma Runtime components ii libkf5plasmaquick5-dbgsym:amd64 5.103.0-1+deb12u1-m59 amd64 debug symbols for libkf5plasmaquick5 ii libplasma-geolocation-interface5 4:5.27.5-3-m36 amd64 Plasma Workspace for KF5 library ii libplasma-geolocation-interface5-dbgsym 4:5.27.5-3-m36 amd64 debug symbols for libplasma-geolocation-interface5 ii plasma-browser-integration 5.27.5-2 amd64 Chromium, Google Chrome, Firefox integration for Plasma ii plasma-calendar-addons:amd64 4:5.27.5-2+m2 amd64 additional calendar plugins for Plasma 5 ii plasma-calendar-addons-dbgsym:amd64 4:5.27.5-2+m2 amd64 debug symbols for plasma-calendar-addons ii plasma-dataengines-addons:amd64 4:5.27.5-2+m2 amd64 additional data engines for Plasma ii plasma-dataengines-addons-dbgsym:amd64 4:5.27.5-2+m2 amd64 debug symbols for plasma-dataengines-addons rc plasma-desktop 4:5.27.5-2 amd64 Tools and widgets for the desktop rc plasma-discover 5.27.5-2 amd64 Discover software management suite rc plasma-discover-common 5.27.5-2 all Discover software manager suite (common data files) ii plasma-disks 5.27.5-2 amd64 Monitor S.M.A.R.T. capable devices for imminent failure in Plasma ii plasma-firewall 5.27.5-2 amd64 Plasma configuration module for firewalls ii plasma-integration 5.27.5-2 amd64 Qt Platform Theme integration plugins for KDE Plasma ii plasma-nm 4:5.27.5-2+m4 amd64 Plasma network connections management ii plasma-nm-dbgsym 4:5.27.5-2+m4 amd64 debug symbols for plasma-nm ii plasma-pa 4:5.27.5-2 amd64 Plasma 5 Volume controller ii plasma-runners-addons:amd64 4:5.27.5-2+m2 amd64 additional runners for Plasma 5 and Krunner ii plasma-runners-addons-dbgsym:amd64 4:5.27.5-2+m2 amd64 debug symbols for plasma-runners-addons ii plasma-sdk 5.27.5-2 amd64 IDE tailored for development of Plasma components ii plasma-wallpapers-addons:amd64 4:5.27.5-2+m2 amd64 additional wallpaper plugins for Plasma 5 ii plasma-wallpapers-addons-dbgsym:amd64 4:5.27.5-2+m2 amd64 debug symbols for plasma-wallpapers-addons ii plasma-wayland-protocols 1.10.0-1 amd64 Wayland protocols for Plasma ii plasma-welcome 5.27.5-2 amd64 KDE Plasma welcome center rc plasma-widgets-addons 4:5.27.5-2+m2 amd64 additional widgets for Plasma 5 rc plasma-workspace 4:5.27.5-2+deb12u2 amd64 Plasma Workspace for KF5
(In reply to xiechuan from comment #4) > Stack trace is already in Attachements (attachment 179332 [details]), > Does this attachment help to analyze the causes? > The problem doesn't seem to have anything to do with Networkmanager, > it's mostly KioWorker related. That stack trace is a png graphic. We need the stack trace as text. Can you please copy the text of the backtrace into a text file and attach that?
Created attachment 179589 [details] stack trace for plasma breeze -1 Sorry for the error in the previous description, this problem occurs mainly when using nemo file manager, but not when using dolphin file manager.
Created attachment 179590 [details] stack trace for plasma breeze -2 using nemo file manager copy
Created attachment 179591 [details] stack trace for plasma breeze -4 using nemo file manager copy smb file
Created attachment 179592 [details] full Plasma version full Plasma version
The above information is the stack information at different moments when copying a large file using nemo file manager offline (*-1,*-2,*-3 is the stack information at different moments)
Thanks for all the additional information. Since your system is running Plasma 5.27.5 on Debian Stable, I'm afraid I have to ask you to report this to Debian. Debian advises users to not submit bugs upstream (https://www.debian.org/Bugs/Reporting), as this version of the KDE software is out of support from KDE, and so it's possible that the bug exists only in Debian at this point. Could you report the bug to Debian using the report bug utility (https://packages.debian.org/stable/utils/reportbug)? If necessary, the maintainer of the package will forward the bug upstream. Thanks for understanding!
Okay, so what problems have been encountered while using Plasma that can be reported directly in https://bugs.kde.org/?