Bug 440931

Summary: No 'accept' button on incoming file notification
Product: [Unmaintained] Bluedevil Reporter: pbs3141
Component: system trayAssignee: David Rosca <nowrep>
Status: RESOLVED WORKSFORME    
Severity: normal CC: plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.22.4   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description pbs3141 2021-08-13 15:30:21 UTC
SUMMARY

When you send a file to your computer over bluetooth, the notification that appears has no accept button, rendering it useless.

STEPS TO REPRODUCE

1. Go to bluetooth system settings and set "When receiving files" to "Ask for confirmation".
2. Use another device to send a file to the computer.

OBSERVED RESULT

As in the picture at

    https://forum.manjaro.org/t/how-to-receive-incoming-files-via-bluetooth/44839

a notification appears but it has no buttons.

EXPECTED RESULT

The notification should have 'Accept' and 'Cancel' buttons.

SOFTWARE/OS VERSIONS

KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

- I have been experiencing this bug for at least a year.
- As a workaround, you can set "Accept files from all devices" in the bluetooth system settings.
- I tried clearing .local and .config to see if the bug went away. However the result was I didn't get any notification at all.
Comment 1 pbs3141 2021-08-13 17:37:50 UTC
Actually I'm closing this bug because as soon as I tried investigating it, it disappeared, and I've had no success in bringing it back.

1. I started by copying the snippet of code that pops up the notification and running it inside a test program. There was no problem; both the buttons were there.

2. Then I compiled bluedevil and installed bluedevil.so over my distro's version. (N.B. You have to run "kded5 --replace" or you'll still be using the old one.) There was no problem.

3. Finally I restored my distro's bluedevil.so. The problem did not come back.

Based on this I guess that the bug happens because of some stale config that needs to get overwritten, though where or what it is I do not know. In any case it's obviously an upstream bug in Frameworks, not a bug in bluedevil, which I hereby exonerate of any fault.