Bug 437676 - Creation of audio alarm template corrupts file name.
Summary: Creation of audio alarm template corrupts file name.
Status: RESOLVED FIXED
Alias: None
Product: kalarm
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Debian testing Linux
: NOR minor
Target Milestone: ---
Assignee: David Jarvie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-25 17:38 UTC by David
Modified: 2021-05-25 23:45 UTC (History)
0 users

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description David 2021-05-25 17:38:17 UTC 
SUMMARY

When creating a template from a running audio alarm, the audio file name is %XX encoded and then presented literally as such in the template parameters.

STEPS TO REPRODUCE
1. Create a new audio alarm (eg, five minutes from now)

2. Select an audio file with characters not strictly alphanumeric (eg ".local/share/sounds/88877^DingLing.mp3"

3. Activate alarm (eg. by clicking OK)

4. Right click on running alarm. From context menu select "Create template..."


OBSERVED RESULT

File name retrieved is garbled, for example "88877^DingLing.mp3" is now "88877%5EDingLing.mp3".

EXPECTED RESULT

File name is retrieved as originally specified.


SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 
KDE Plasma Version:      5.20.5
KDE Frameworks Version:  5.78.0
Qt Version:              5.15.2

ADDITIONAL INFORMATION

KAlarm version  is 3.03 (not available in version menu on bug report system).

One workaround is to re-specify the file name whenever instantiating the template.
Comment 1 David Jarvie 2021-05-25 23:45:37 UTC 
The alarm edit dialog also showed the audio file name in the encoded format. This is now fixed both when editing the alarm and when creating a template from the alarm. The fix will be in KAlarm version 3.2.2, which will be in KDE applications release 21.04.2.

Git commit 725f7388fdd0feedf1e5891667e64380c62df0fd in 21.04 branch.