Custom message ringtone handling

[Michael Zanetti]

When setting a custom message ringtone, the sound file first needs to be copied somewhere into ~/.local/share/. The push-client helper restricts sound file locations to XDG_DATA_DIRS.

[Michael Zanetti (mzanetti)]

FWIW, I've met a bunch of people by now that broke their Telegram notifications because of this issue.

[Stefano Verzegnassi (verzegnassi-stefano)]

I'm currently working on a refactor of the code, in order to remove a lot of bad things I wrote.

I've (temporarily) removed the custom ringtone page from the codebase I'm working on, but I see that the recently introduced content-hub support is not available for the message ringtone.

Is there a change to see it in a short time?
About the bug with Telegram, does setting a default ringtone (through ubuntu-system-settings app) fix it?

[Michael Zanetti (mzanetti)]

I have no idea if content-hub will gain support for message ringtones anytime soon. I think resetting to the default ringtone should help, yes.

[Stefano Verzegnassi (verzegnassi-stefano)]

> I have no idea if content-hub will gain support for message ringtones anytime soon.
It's worth to reintroduce the ringtones page back again.

> I think resetting to the default ringtone should help, yes.
Mmh, ok. Then it does not seem anything disruptive from UTTT side (i.e. it's just about the wrong location for audio files).

Since the app should anyway create a copy of the file and move to XDG_DATA_DIRS, it would be good to use content-hub this time.

I will have a look at what ubuntu-system-settings app does.
As long as UTTT stays with GPL3 license, I think there's no problem in reusing some bit from that app.

[Stefano Verzegnassi (verzegnassi-stefano)]

No one has complained the removal of the custom ringtone feature. Let's assume the issue is not valid anymore.