Bug 362146 - Attempting to send multiple files via bluetooth fails, rather than being queued
Summary: Attempting to send multiple files via bluetooth fails, rather than being queued
Status: CONFIRMED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Bluetooth in general (other bugs)
Version First Reported In: 6.2.4
Platform: Other Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: David Rosca
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-23 16:10 UTC by Friedrich W. H. Kossebau
Modified: 2025-01-27 22:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Friedrich W. H. Kossebau 2016-04-23 16:10:31 UTC
One would expect multiple requests for sending files via bluetooth to be put in a queue, instead of having to wait one-self to start sending the next one.

Reproducible: Always

Steps to Reproduce:
1. Start sending a bigger file with bluetooth to mobile device A (e.g. from Dolphin context menu)
2. While the sending is still running, try to send another file to the same device A

Actual Results:  
Dialog pops up, telling: "Connection failed".

Expected Results:  
The action to send the file is added to a queue (perhaps with a temp copy of the current version of the file), system message tells about adding to the queue.
Once the current file-send action (and any other actions in the queue before this one) are done, the file is tried to be sent as usual.
Comment 1 TraceyC 2025-01-27 22:44:19 UTC
Tested this with git-master, can still reproduce
Choosing a second file to share via Bluetooth produces an error

"The connection to <phone-name>has failed: OBEX Connect failed with 0x53"