Bug 439675

Summary: Bluedevil-sendfile not accepting relative paths
Product: [Plasma] plasmashell Reporter: Janek <xerusx>
Component: Bluetooth in generalAssignee: David Rosca <nowrep>
Status: RESOLVED WORKSFORME    
Severity: normal CC: nate, nicolas.fella, plasma-bugs-null
Priority: NOR    
Version First Reported In: 6.2.4   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Janek 2021-07-09 11:35:19 UTC 
When calling `bluedevil-sendfile`, I have to specify a full file path, relative paths lead to "Unable to open file".

STEPS TO REPRODUCE
> $ echo something>test.txt && bluedevil-sendfile -f test.txt
> bluedevil.sendfile: Device ""
> bluedevil.sendfile: Files ("test.txt")
> bluedevil.sendfile: Manager initialized
> bluedevil.sendfile: SendFilesJob: ("test.txt")
> bluedevil.sendfile: Wizard done:  1
> bluedevil.sendfile: SendFilesJob-DoStart
> bluedevil.sendfile: SendFilesJob-NextJob
> kf.bluezqt: PendingCall Error: "Unable to open file"
> bluedevil.sendfile: Error sending file "Unable to open file"

In between I select a device, but then get the error.
Qualifying the path fully produces no issues:

> $ bluedevil-sendfile -f $PWD/test.txt

EXPECTED RESULT
bluedevil-sendfile resolves relative paths relative to pwd.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch with Plasma 5.22.3
(available in About System)
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2
Comment 1 Nicolas Fella 2021-07-09 13:39:03 UTC 
weird, "echo something>test.txt && bluedevil-sendfile -f test.txt" works fine here on master, and I don't see a relevant change in the KDE bluetooth stuff.

I think this may be a regression in bluez 5.60. I will investigate
Comment 2 Nicolas Fella 2021-07-10 16:17:32 UTC 
hmm, no, I can't reproduce with bluez 5.60 either
Comment 3 Nate Graham 2025-04-23 08:13:49 UTC 
Sorry we were not able to get to this bug report yet! Can I ask you if the issue is still happening in Plasma 6.3.4 or newer? Thanks a lot!
Comment 4 Bug Janitor Service 2025-05-08 03:47:01 UTC 
🐛🧹 ⚠️ 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!
Comment 5 Janek 2025-05-22 19:01:07 UTC 
seems fine now