Brandon Rothweiler

Thanks again, @dlech. @Vudentz I tested with the latest master commit, and I am no longer getting a segfault from bluetoothd. However, the original problem still remains, which is that...

@Vudentz I bisected the segfault to this commit: https://github.com/bluez/bluez/commit/e0870ce5e1fe842e11f5d2a8425b4c4594ca0799. I noticed that commit only changed the debug logging, so I tried running `bluetoothd` without `--debug`, and it did not segfault....

@Vudentz Yes, I was testing with the latest commit on the master branch, which includes the change you linked. I think you're on the right track, since the last service...

@Vudentz Unfortunately, that patch didn't resolve the issue. The debug output is the same as before, I still see the "service disappeared" line after the characteristics are discovered.

@Vudentz That version didn't work either unfortunately. Again, the log output is the same as before, and I don't see the any occurrences of the new `Unable to get service...

I already sent this trace to @Vudentz via Slack, but here it is in case anyone else wants to take a look: [issue438.log](https://github.com/bluez/bluez/files/10252769/issue438.log)

@Vudentz Your v4 patch seems to have fixed the issue for me! https://patchwork.kernel.org/project/bluetooth/patch/[email protected]/ https://patchwork.kernel.org/project/bluetooth/patch/[email protected]/ ``` ➜ core git:(dev) ✗ bluetoothctl info CF:E6:08:09:01:02 Device CF:E6:08:09:01:02 (public) Name: eufy T9148 Alias: eufy...

Running Tabby with `--enable-features=UseOzonePlatform --ozone-platform=wayland` did not work for me. The UI is still blurry. I'm running Ubuntu 22.04 with the scaling set to 150%.

@shamoon Good point, I didn't see that PR. I'll wait until after it gets merged and then will revisit this.

I think the rotation direction as currently implemented in this PR is actually reversed. Typically "rotate left" means counter-clockwise and "rotate right" would be clockwise.