02-07-2023, 02:43 AM
(This post was last modified: 02-07-2023, 02:46 AM by azymohliad.)
Hi, WatchMate developer here. Sorry, I don't check this forum regularly, and I noticed your question only now. I think the best place to post it would be WatchMate issue tracker, this is also where I would see it immediately.
For now I don't really have an idea what's happening. If the issue is still there, it would be helpful if you could run it from the terminal and share the logs, ideally with RUST_LOG=watchmate=debug environment variable. I.e., if you're using flatpak package, run it as following:
otherwise:
Also, bluez version (bluetoothctl --version) could be helpful to know.
You can reply here or create an issue on Github, whichever you prefer (I subscribed for response notifications here).
For now I don't really have an idea what's happening. If the issue is still there, it would be helpful if you could run it from the terminal and share the logs, ideally with RUST_LOG=watchmate=debug environment variable. I.e., if you're using flatpak package, run it as following:
Code:
flatpak run --env=RUST_LOG=watchmate=debug io.gitlab.azymohliad.WatchMateotherwise:
Code:
RUST_LOG=watchmate=debug watchmateAlso, bluez version (bluetoothctl --version) could be helpful to know.
You can reply here or create an issue on Github, whichever you prefer (I subscribed for response notifications here).