SUMMARY STEPS TO REPRODUCE 1. select some photos on Android 2. choose share to kde connect 3. KDE Plasmoid kde connection on laptop crashed sometimes OBSERVED RESULT KDE Plasmoid kde connection on laptop crashed sometimes EXPECTED RESULT It should be transfer correctly. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.17.5-2 KDE Frameworks Version: Qt Version: 5.14.1-1 ADDITIONAL INFORMATION
Created attachment 126324 [details] KDE Connect suspend on file transfering sometimes
Created attachment 126325 [details] KDE Connect can't start after manually stopped previous suspended transfer task
Hi, same bug for me. It looks to happen only when a multiple files selection from the Android device is shared. Single file transfer looks fine. If transfer happens to hang, Dolphin may hang too. Problem, once the multiple files transfer failed, Dolphin is badly responding. For instance impossible to rename a file through context menu. This Dolphin bogus behaviour lasts for hours, maybe for ever ? WORKAROUND 1- Kill kdeconnect daemon : kdeconnectd For instance : - from terminal, top, k - from desktop Alt+F2, killall kdeconnectd 2- launch KDE Connect from desktop 3- everything is fine again SOFTWARE/OS VERSIONS Linux/KDE Plasma: Mageia Linux 8 package kdeconnect-kde-20.12.0-1.mga8.x86_64 KDE Plasma Version: 5.17.5-2 KDE Frameworks 5.76.0 Qt 5.15.2 (construit sur 5.15.2) Le système de fenêtres xcb Interacting with /e/OS 1.15-s-20230913330639-stable-FP4 (Android 12)
I was able to reproduce this, intermittently ## Steps to reproduce Source: Sony Xperia Android phone Dest: Laptop On my first attempt, I tried sending a few PDFs via the Android File browser > Share > KDE. This was successful. I was able to reproduce the bug when I attempted to send 17 jpg files using the kdeconnect Android app UI - share files On the laptop, the notification showing the transfer transfer hung at 11 of 17 files 148MiB of 159.5 MiB I received a notification on the phone that a transfer had failed Any attempt to send more files resulted in the files will be added to the total in the laptop notification, but the progress was still hung until kdeconnect was restarted on the laptop. After restarting kdeconnect, I found I was able to transfer multiple jpgs using Google Photos > Share > KDE Connect I was no longer able to reproduce the bug from Android KDE Connect > Share (for now) ## Notes There are a number of bugs related to crashes in kdeconnect if the user atteempts to transfer multiple files, or a large file, from a phone to Plasma. I'm not sure they are all duplicates. I'm listing them here so that someone more knowledgeable can more easily take a look at them as a group. https://bugs.kde.org/show_bug.cgi?id=418074 - I was not able to reproduce Dolphin hanging when kdeconnect hangs https://bugs.kde.org/show_bug.cgi?id=424941 https://bugs.kde.org/show_bug.cgi?id=467015 https://bugs.kde.org/show_bug.cgi?id=470273 https://bugs.kde.org/show_bug.cgi?id=471881 https://bugs.kde.org/show_bug.cgi?id=473071 https://bugs.kde.org/show_bug.cgi?id=474495 https://bugs.kde.org/show_bug.cgi?id=475747 https://bugs.kde.org/show_bug.cgi?id=480889 ## System details kdeconnect 23.08.4 Operating System: Solus 4.5 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.6.15-272.current (64-bit) Graphics Platform: X11 Processors: 16 × 11th Gen Intel® Core™ i7-11800H @ 2.30GHz Memory: 62.5 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 Manufacturer: Dell Inc. Product Name: XPS 17 9710 Phone: Sony Xperia 1 III Model: SQ-BC62 Android v12 - kdeconnect 1.29.0
If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? Thanks!
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. 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. Closing as RESOLVED WORKSFORME.