Wacom Intuos BT S (CTL-4100WL) not detected over Bluetooth on Fedora Asahi (aarch64)

Steps to Reproduce

1. Perform a fresh installation of Fedora Asahi Remix 42 on an Apple
   Silicon device.
2. Pair a Wacom Intuos BT S (CTL-4100WL) tablet via the system's
   Bluetooth settings. The tablet functions as a basic mouse pointer.
3. Install the .NET 8 SDK from the standard Fedora repositories: sudo dnf
   install dotnet-sdk-8.0.
4. Clone the latest master branch of the OpenTabletDriver repository.
5. Build the GTK user interface: dotnet build OpenTabletDriver.UX.Gtk -c
   Release.
6. Add the current user to the input group: sudo usermod -aG input $USER.
7. Create the standard OpenTabletDriver udev rule at
   /etc/udev/rules.d/70-opentabletdriver.rules.
8. Create and enable a systemd user service
   (~/.config/systemd/user/opentabletdriver.service) pointing to the
   compiled daemon.
9. Log out and log back in completely to apply group and udev changes.
10. Launch the OpenTabletDriver GUI: dotnet run --project
    OpenTabletDriver.UX.Gtk.

Expected Behavior

The OpenTabletDriver application should launch and detect the "Wacom
Intuos BT S" tablet, allowing it to be selected for configuration of
button bindings, area mapping, and pressure curves.

Observed Behavior

The OpenTabletDriver GUI launches successfully, but it displays the
message "No tablets detected." The daemon's log confirms it is running but
does not find any devices. The tablet continues to work as a system-wide
mouse pointer, indicating a kernel driver has control, but OTD cannot
access it.

Tablet Device

Wacom CTL-4100

Diagnostic Information

{
2 "errorType": "System.Reflection.TargetInvocationException",
3 "message": "Exception has been thrown by the target of an invocation
,
4 "stackTrace": [
5 "--- End of inner exception stack trace ---",
6 "at System.RuntimeType.CreateInstanceOfT()",
7 "at System.Activator.CreateInstanceT",
8 "at Eto.Widget..ctor()",
9 "at Eto.Forms.CommonDialog..ctor()",
10 "at Eto.Forms.FileDialog..ctor()",
11 "at Eto.Forms.SaveFileDialog..ctor()",
12 "at System.RuntimeType.CreateInstanceOfT()",
13 "at OpenTabletDriver.UX.Extensions.BuildFileDialog[T](String title
String directory, IEnumerable1 filters, String initialFileName, Nullable1 multiSelect) in
/home/chinkhuslen/OpenTabletDriver/OpenTabletDriver.UX/Extensions.cs:l
e 78",
14 "at OpenTabletDriver.UX.Extensions.SaveFileDialog(String title,
String directory, IEnumerable`1 filters, String initialFilename) in
/home/chinkhuslen/OpenTabletDriver/OpenTabletDriver.UX/Extensions.cs:l
e 115",
15 "at OpenTabletDriver.UX.MainForm.ExportDiagnostics() in
/home/chinkhuslen/OpenTabletDriver/OpenTabletDriver.UX/MainForm.cs:lin
652"
16 ],
17 "innerException": {
18 "errorType": "GLib.GException",
19 "message": "Invalid byte sequence in conversion input",
20 "stackTrace": [
21 "at GLib.Marshaller.StringToFilenamePtr(String str)",
22 "at Gtk.FileChooserDialog.SetCurrentFolder(String filename)",
23 "at Eto.GtkSharp.Forms.SaveFileDialogHandler..ctor()",
24 "at Eto.GtkSharp.Platform.<>c.b__12_96()",
25 "at Eto.Widget..ctor()"
26 ]
27 }
28 }

Acknowledgements

• I have installed OpenTabletDriver by following its official installation instructions.
• I have checked the OpenTabletDriver Wiki and respective FAQ pages, and my issue was not covered or actually fixed.
• I have searched the existing issues and this new issue is not a duplicate of any.
• I have written a concise and meaningful title.
• I am on the latest version of OpenTabletDriver.

Reproduce the Bluetooth setup on Fedora Asahi and start with the OpenTabletDriver daemon logs and the OpenTabletDriver.UX.Gtk entry point to trace why the CTL-4100WL is not exposed to the application. The issue is done when the tablet is detected by the GUI and can be selected for configuration; the diagnostic export path in OpenTabletDriver.UX/Extensions.cs and MainForm.cs is a separate reported exception.