Happened during Doing naming tests of check_kdb_internal_suite with dbus mounted as global plugin.

@waht Seems like dbus does not accept arbitrary strings as file names. redis et al. likely have similar issues. Can you take a look?

Yes this happens if the key name passed to dbus_message_append_args in sendmessage.c contains non-UTF-8 characters. The D-Bus specification requires strings to validate strictly as UTF-8. Redis does not require this - strings are interpreted as binary sequence so encoding is not an issue. This seems also true for ZeroMQ.

As far as I can see Elektra does not care about encoding of key names too. So to fix this issue in the D-Bus plugin keyNames could be converted to UTF-8 if they contain non-UTF-8 characters but what should be used as source encoding? ASCII?

Thank you! Documenting this fact should be enough for now. In the longer term we should extend the iconv plugin to also fix key names.

We should find a proper solution to this. E.g. KDE kopete can have keys with UTF-8 as it allows user-specified status or kmix uses user-specified audio names as section names.

@mpranj did you already try to use our dbus notifications with KDE or GNOME?

did you already try to use our dbus notifications with KDE or GNOME?

Yes, I used it with GSettings and it was working fine, but I never specifically tested with non-UTF-8 characters.

Did you check if the APIs even allow non-UTF-8 to end up in the KeySet? Nevertheless, we also need some protection to not trigger asserts in the libs that we use.

I mark this stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping by writing a message here or create a new issue with the remainder of this issue.
Thank you for your contributions 💖

I closed this now because it has been inactive for more than one year. If I closed it by mistake, please do not hesitate to reopen it or create a new issue with the remainder of this issue.
Thank you for your contributions 💖