Created attachment 166014 [details] Backtrace SUMMARY STEPS TO REPRODUCE 1. Backup /home on Kubuntu Laptop A, including flag to verify backup integrity using the default Kubuntu/KDE backup program 2. Restore /home on new Kubuntu Laptop B; merge /home folder. OBSERVED RESULT Errors observed. One of them is with kioslave and no bug reporting address. EXPECTED RESULT Successful /home folder recovery. Or at the very least, an option to report the bug from within Kubuntu. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 6.6.10-76060610-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.6 GiB of RAM Graphics Processor: GFX1103_R1
Created attachment 166015 [details] Error 1
Created attachment 166016 [details] Error 2
Created attachment 166017 [details] Error 3
Also, please let me know if this would fit better under Kubuntu's bug tracking: https://bugs.launchpad.net/ubuntu/
Note that this is currently preventing me from migrating to my new Kubuntu laptop.
I am going through each folder to restore individually and found that /home/username/.local produced an error.
.vscode also caused a kioslave5 crash.
snap folder also caused a kioslave5 crash.
Thanks for the report! 1. Restoring /home instead of /home/user will normally fail with permission problem, as it has in your case. It's normal that only root has permission to write to that folder. 2. Crashing kioslave5 is interesting! I believe now, from the backtrace you saved here, that it has to do with reading file contents of some specific files. It would be helpful if you could narrow it down even more than what you have already done. I believe you will see the same crash by just using a "bup:///home/user/.local" URL in some KDE based file lister, like dolphin or gwenview. That could be a faster way to find an example (you had more than 1) file that causes the crash. It would also be interesting then if you could save a new backup (in a completely new backup destination folder) of a folder that has problematic files. Then see if there is the same problem with that backup. Fantastic reporting, thanks for taking the time!
Forgot to say, if you do narrow it down to a small backup that causes a crash when restoring... then if you are willing to share that with me it could be very helpful. Just zip up the backup destination folder and upload here or email me directly.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!