Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Valid local names are not always valid dbus object paths #126

Closed
markmcclain opened this issue Mar 6, 2024 · 0 comments · Fixed by #127
Closed

Valid local names are not always valid dbus object paths #126

markmcclain opened this issue Mar 6, 2024 · 0 comments · Fixed by #127

Comments

@markmcclain
Copy link
Contributor

The problem
The character set for local name (utf-8) and dbus paths (limited ascii ) are different.

Reproduction
On linux, create a server with a name of test-dash-name
Python Exception is raised when started the server:
dbus_next.errors.InvalidObjectPathError: invalid object path: /org/bluez/test-dashed-name/service0001
Expected behavior
Server will start and advertise test-dash-name with dbus backend.

Screenshots
N/A

Desktop (please complete the following information):

  • OS: Linux

Additional context
Dbus object path requirements: https://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-marshaling-object-path

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants