Skip to content

Conversation

stokito
Copy link

@stokito stokito commented Dec 15, 2024

I was confused when saw an br-connection-unknown error and didn't know where to start from.
At first I tried to enable debugging blueman-manager --loglevel=debug but this didn't helped a lot. For some reason the BlueZ doesn't return any details in the DBus call. Can you work with the devs and add more details to a message?
To make it easier for a user I added the message "Check bluetoothd logs." so that I will faster figure out to make the journalctl -u bluetooth -f -n 400 and see the real error there.
I made the logging message same as the message to a user, but not translated.

Copy link

@infirit
Copy link
Contributor

infirit commented Dec 16, 2024

Haven't looked too closely at the changes but, don't commit .po changes pls. We send an updated blueman.pot to Weblate for the translators. Then Weblate will take care of sending PR to update the .po files :-).

@stokito
Copy link
Author

stokito commented Dec 16, 2024

See, I changed the translation keys and added a dot . to end. So to keep the old translations I had to rename them. Please merge the Weblate translations #2360 and I'll rebase the branch to avoid conflicts. The Weblate syncs files if a few hours and if any translation made there then indeed it it will be a conflict. But it easily resolved by pulling from the Weblate, merging and then Weblate will be fine to send PRs again.

@infirit
Copy link
Contributor

infirit commented Dec 18, 2024

It's all automated so just ignore everything related to translations. You only need to mark them as translatable with _() .

@stokito
Copy link
Author

stokito commented Dec 18, 2024 via email

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 this pull request may close these issues.

2 participants