fresh installation of OpenTabletDriver - Linux Mint #3237
Labels
configuration
Adds or modifies a tablet configuration
Comments
github-actions
bot
added
the
needs-triage
|
For some reason my log got truncated. Here the complete one (checked): |
|
The UI wills timeout if the daemon isn't running, but now the daemon is so it shouldn't timeout anymore. You won't see the tablet in the system settings because its not being controlled by that anymore. The reason OTD isn't working is likely because we need to completely change our detection scheme, your tablet (likely) has more than 1 identical identifier and thus OTD may randomly select the wrong one, see #3011. This is unrelated to Linux Mint, isn't a problem with the installer/deb, the fault isn't really on us, more just an artifact of poor manufacturer choices. And yes, obviously we have checked if it works on these distros, no need to get rude at us over it all, I understand that this may be a frustrating time for you there's absolutely no need to point fingers here. If you want me to confirm if its the issue above, export a diagnostic from the UI (help > export diagnostics) and send that file here, otherwise I can only go off the partial information the logging gives me. Or, you can just uninstall the OpenTabletDriver package, reboot and be done with it. |
Now I launched the OpenTabletDriver.Daemon manually and to my surprise the tablet setup assistant appeared. Seems working now.
scared me a bit, but you are right.
Will check, thanks
|
It does not do this by default, we mention this on the installation guide and tell you to set this up. Place this file in |
jamesbt365
added
configuration
I did register the opentablet demon and used this command: and the Demon didn't ever start
This is the missing part in my installation. In the past 6 days I had little success to install the driver of my tablet brand. After contacting them and waiting more days they told me I've to install an older driver bc the new one doesn't work for my tablet model. This process tired me. Finally, allow me to ask, what is they dotnet-suggest-registration thing? Please let this report open for 12 more hours so I can test my tablet in action. Thanks for your help so far |
There isn't really a point adding this to the wiki, the configuration above was created by me, on the fly to fix a conflict between 2 tablets, and will be promptly added to the driver provided nothing else goes wrong, however, before I can do this I need you to verify a few pieces of information for me. Configuration overrides must be created and unless a conflict exists which cannot be distinquished between it will be added to the driver, unless you know how to diagnose, create, modify and test overrides there isn't really a point listing the override directories. It will eventually happen when we get around to creating documentation for adding supports to tablets but right now this is on our backlog. Right now I need you to get these values (open
TIP: don't have your pen on the tablet while you are testing the auxiliary keys, it'll make the display for them easier to see. I'm also pretty sure the only dotnet telemetry that exists is when building dotnet applications, which you are completely able to opt out and only applies when working with source code, which you aren't. See this: https://learn.microsoft.com/en-us/dotnet/core/tools/telemetry From a quick search dotnet-suggest is a completely related tool. |
|
I enjoyed too quickly, the configuration file works (I don't get the first-steps tutorial anymore to setup my tablet over and over again) but I've still to launch the Pressure : 2047 In the "Auxiliary settings" tab I can press how much I want on the first field, but opentablet seems not to detect the key press of my auxiliary keys, no matter what key (8 keys in total) I use. |
You missed the max x and y coordinates, and you should see the auxiliary button presses when you press the buttons on the tablet, they'll appear in an array on the debugger window, similar to the pen buttons. |
|
I'm also going to need a string dump. Tablet > device string reader |
|
Position: (bottom right) [50797 , 30477] not sure if these max values are 100% perfect, but we're very close. No auxiliary button presses are visible on my side. dump_074705.txt |
|
Tablet > tablet debugger, turn on data recording and press the auxiliary keys one by one in order. Once done disable data recording, close the debugger and send the file from |
|
I don't know why but suddenly my aux keys work and I can see them in the debugger window. I didn't see them before or change anything meanwhile. Confused. just the head of the file looks relevant, the rest looks all the same. Will check back tomorrow, this is my last mail today. |
|
I've gone ahead and opened a pull request that'll fix this in future driver releases. Its a long story, I don't think pressure was originally verified back when this configuration was created back in 2021. And somewhere along the lines a migration must have broke support for this tablet on Linux by changing one of the report lengths that the configuration looks for on the tablet. Nothing more should have to be done on our end and the release of the next version of OpenTabletDriver should allow you to remove the configuration override I provided you, but right now you'll probably want to change the |
|
Just some checks I've found a link to opentabletdriver.service in two different places: both have the same content (the syntax should be correct): Even with this preferences in place, OR generates one or both of these links. Solution Here's the output of Summary Conclusion For now, I need the Looking forward to download your next OpenTabletDriver update! |
|
@Jopp-gh could you export another diagnostic please? I might be able to improve this further. |
|
Sure, here the diagnostics: |
|
Could you send the current configuration you are using? I don't see why it is matching 2 identifiers at once. |
|
these settings are not complete, but work. |
|
I didn't need your settings I needed the configuration file you are using in |
|
Ok, here it is: |
|
Hello, I installed your new driver. I get mixed results, the pen or the aux keys sometimes work, sometimes don't. Sometimes aux keys and the pen work together, often they don't. I also tried different modes, absolute mode, relative mode and artist mode (which is the recommend mode for linux if I'm right), but this didn't improve my aux buttons / pen buttons There are no Tablet plugins installed that could possibly interfer and change buttons in/output. Mapped pen buttons do noting at all, even if the debugger detects them. The usb ports where I plug my tablet are not broken or old, they use usb3 (blue) The only thing that works, even if the pen isn't detected (no pen buttons nor aux keys detected in the debugger), is actually the pen pressure. I thank you for your kind support and effort put in your new driver! However for the time being I need to find another solution, I'm sorry to say your last update made my tablet even more unpredictable than before. |
|
Basically I updated OpenTabletDriver these days through Mint's default update app. In the meantime I've seen you added a new flatpak version, that's nice. So I uninstalled my last OpenTabletDriver's driver and installed your new flatpak version instead. However now my tablet disappeared completely and OpenTabletDriver's log prints also "no tablets were detected" Probably OpenTabletDriver doesn't work now because Mint detects again my tablet in system settings. |
|
The flatpak cannot handle the system side of things, therefore no udev or blacklisting of kernel modules, alongside the need for your tablet to have custom versions of these things, it won't exactly work without manual intervention. And to get the aux functionality to be predictable it would require a USB packet capture done on windows with the OEM driver installed. |
|
I opened this report in the hope to get a working tablet as it was in the list of supported devices. If you can't support relative "older" devices (my tablet is 5 yo) then you better cut this list and remove older devices, as the info given is not accurate. I'm sure you developed a good software in general, but it doesn't work for all listed devices. For the flatpak version, I'm sorry but all I can do is to answer with a head-shaking. The reason why I needed your driver was to be able to create more profiles, because the standard installation doesn't provide multiple profiles. Apart that, I never had any problems with the default wacom driver, all pen / aux buttons and pen pressure worked and work without issues. I guess we can close this report as |
|
Unfortunately right now I'm juggling multiple configurations for different tablets, a PR that allows for a rework of the detection scheme, this tablet, and a variant of this tablet with a firmware bug and a few other things just related to the project, alongside IRL things I can't guarantee that I can work on this constantly. Some variants of this tablet do work, and this doesn't mean that we are going to cut support entirely. Lots of tablets have variants, new variants are created for old tablets all the time. Does that mean we should remove all the configurations from OTD and make users create them for their tablet that they want to use on their own with no support? No of course not that doesn't make sense at all. If you are not going to provide the details to make this work properly of course its not going to work properly, I can only work with as much information as you provide me with, I do not have your physical tablet and therefore cannot get the information on my own. I understand that I am not always available but this will never get done if you don't get the right information, I can look into the Linux Wacom kernel project but our detection schemes are different, we are different drivers. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to Reproduce
Since linux Mint does not allow the configuration of multiple tablet profiles I installed OpenTabletDriver.
Before the installation of OpenTabletDriver my tablet was working fine and Mint detected my tablet and pen immediately, in addition, every time I connect my tablet, my mouse cursor disappears.
Expected Behavior
A working driver that doesn't mess with my mouse and gives me a way to setup multiple tablet profiles.
Observed Behavior
I didn't do anything wrong with your installer - the installation of OpenTabletDriver is fool proof.
All I know is that OpenTabletDriver messed up my default tablet settings (deactivating wacom drivers) as described in your wiki:
and deactivating my damn cursor, which is even more upsetting!
Then I tried to install yet another time in the hope to get a "complete installation" of your driver. Nothing changed after rebooting.
Guys, you probably you need to check better how you write your installers, because I don't use a small insignificant distro with all kind of issues, so the fault is clearly on your side. Sorry to come up to ask this, but did you actually do some little check if your installer worked fine on major distros like Mint, at least ?
Since this installation is such a birth, I just ask you to tell me how to reactivate my wacom drivers so mint can see again my tablet and the uninstaller for OpenTabletDriver.
Tablet Device
XP-Pen Star 03
Diagnostic Information
lsusbyes I can see my tablet:Bus 001 Device 015: ID 5543:0081 UC-Logic Technology Corp. TABLET 1060Nthere is nothing related to OpenTabletDriver in these folders:
here's the log from
~/.config/OpenTabletDriverAcknowledgements
The text was updated successfully, but these errors were encountered: