Bug 416807 - Flood of notifications when transferring large number of files
Summary: Flood of notifications when transferring large number of files
Status: RESOLVED FIXED
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: 1.10
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-26 22:06 UTC by Nate Graham
Modified: 2021-07-06 14:34 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Notification flood (401.37 KB, video/webm)
2020-01-26 22:06 UTC, Nate Graham
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nate Graham 2020-01-26 22:06:11 UTC
Created attachment 125451 [details]
Notification flood

SUMMARY
KDE Connect started working again for me! All KDE software built from source on openSUSE Tumbleweed + latest Android app on Android 8.0.0


STEPS TO REPRODUCE
1. Open KDE Connect app
2. Tap "Send Files"
3. On Camera/Pictures page, tap three-dot menu and select all pictures (it was several hundred)
4. Tap "Open" (another minor bug; should say "Select"


OBSERVED RESULT
On the host, I see one notification per image, resulting in a torrent of notifications. See attached screen recording. I cannot see overall progress or cancel the whole transfer.


EXPECTED RESULT
Only a single file transfer notification shows up on the host that includes all files in it, displays accurate progress information, and allows the whole transfer to be canceled.

I suppose what's happening is that each file is transferred using a separate job rather than combining them all into a single job. If there isn't a technical blocker to doing that, we might want to consider it
Comment 1 Nicolas Fella 2020-03-17 16:31:20 UTC
We're using a composite job since quite a while for this now, so unless you're running an old version I don't understand why this is happening

See https://cgit.kde.org/kdeconnect-kde.git/commit/?id=283d0140597d338210cff62a83c7d72a2e5e368d
Comment 2 Nate Graham 2020-03-17 18:56:42 UTC
You're right, I was using an old version. I can see that it works properly with the latest code from git master.