I wanted a pad I could write with a pencil, and so I noted that Wacom Tablet is in all of the distros as an option in the settings so I reasoned that that is the obvious choice. I had tried a plug in one and got it working a few years ago (with some kind online help) and so surely now it will be just plug and play.
I have two computers, one with Ubuntu and one with Fedora. I checked that the pad and pen work in Windows and it worked fine, so I went and tried in Ubuntu. No go, it can sortof connect but even when connected the blue light is still flashing which it wasn’t when connected within Windows.
It’s OK, I reasoned, I will try it in Fedora when I get home.
Tried it in xfce (I have to login to xfce before it allows me into Gnome (long story since latest upgrade)). Connected then immediately disconnected due to a “Connection Failed: br-connection-create-socket”
So I go into Gnome and finally it connects - thank goodness, strong blue light of connection, but no the pen doesn’t work on it, so it is connected but not able to be written on.
So my obvious question is: do I need to install something even with a bluetooth connection? And if so what (coz I cannot find this issue anywhere)? And how is this a problem? The Wacom Tablet refuses to even acknowledge that the tablet is even there. Why would Gnome have Wacom Tablets as an entire section to themselves if they do not plug and play?
Funnily enough I logged out then back into xfce to get the actual error message above, and the connection persisted from Gnome to xfce, (but still no pen working), so I had to disconnect and try and connect again to get the error message above. Truly weird!
It is good practive to provide the output of inxi -Fzxx (pasted as preformatted test using the </> button). This helps others with the same hardware and issues find this thread, and sometimes there are conflicts with specific hardware.
If that doesn’t solve your problem, try to find relevant journalctl entries. This will require some effort, as journalctl produces enormous detail. You should run man journactl in a terminal and read the explanations for the options suggested here so you understand them.
First, check journalctl --no-hostname -b -p 3. You may need to search for discussion of any messages that appear – many (but not all) may be harmless. Then try searching for relevant strings using journalctl --no-hostname -b -g <string>.
I use Wayland mostly though I would be happy enough if it worked in either.
I will try the journalctl when I get a chance.
I have no idea what inxi -Fzxx (pasted as preformatted test using the </> button) even means, I’m sorry, I just saw that Wacom was embedded and bought a bluetooth pad expecting it to work. I would happily work through a fix, but it seems that it is just me, and the Fedora machine and the Ubuntu machine I have - strangely the same problem on both.
Open your terminal and type: inxi -Fzxx
If it’s not installed, you will be requested to install it. Type y to install
You can also simply install it by entering the following in your terminal sudo dnf -y install inxi) More info: Use inxi to Get All Kind of System Information in Linux
Copy and paste the output of inxi -Fzxx in your reply. Select the output and use the button </> to add a “`” at the beginning and end of the output, for easier readability. The button is visible in the toolbar of your reply.
The LHDB has 51 probes that include this pad, including Fedora 38. Most probes just show “detected”, only a few show “working”, but the LHDB can’t provide much detail unless users manually add it.
Please post terminal output as pre-formatted text (just bracket the text with triple backquotes). Looks like you ran inxi on your Ubuntu system, but both Ubuntu and Fedora 40 have btusb (Generic Bluetooth USB driver) version 0.8.
Have you tried manually switching the Android/Linux modes Android misdetect. This mentions a fix using fwupd 1.6.2 or later. Fedora 40 has:
Installed Packages
Name : fwupd
Version : 1.9.19
Release : 1.fc40
Architecture : x86_64
Size : 7.3 M
Source : fwupd-1.9.19-1.fc40.src.rpm
Repository : @System
From repo : updates
Summary : Firmware update daemon
URL : https://github.com/fwupd/fwupd
License : LGPL-2.1-or-later
Description : fwupd is a daemon to allow session software to update device firmware.
Use sudo fwupdtool get-updates to check for available updates.
If that doesn’t help, you need to file a bug report, but that requires more details. It isn’t clear if the issue is specific to your bluetooth hardware, the btusb driver, or the Wacom firmware. You should be able to get the required details by running journalctl in a terminal and searching (type /btusbthen press “Enter”). journalctl captures a huge amount of data, so you need to select just the records relevant to your problem.