Bug 340589 - Huion tablet can not set default table.
Summary: Huion tablet can not set default table.
Status: RESOLVED FIXED
Alias: None
Product: wacomtablet
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Jörg Ehrichs
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2014-11-03 03:38 UTC by Vince Herried
Modified: 2015-01-18 20:51 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vince Herried 2014-11-03 03:38:07 UTC
Running fedora F20  kde 4.14
using a Huion H610 tablet lsusb shows 
Bus 002 Device 012: ID 256c:006e  
The device has eight buttons on the pad.  With the latest set of drivers 
some of the device buttons generate output but I can't set the values.
The graphics tablet system settings doesn't show a default table entry and doesn't let me enter
one.


Reproducible: Always

Steps to Reproduce:
1. Attache Huion Tablet
2. navigate system settings -> graphics settings -> graphics tablet
3. Attempt to create a profile for the tablet

Actual Results:  
attempt to create a new profile generates 
graphics tablet error
profile vince does not exist
( vince is name I tried ).


Expected Results:  
a new profile generated.
Comment 1 Jörg Ehrichs 2014-11-08 12:40:23 UTC
Does your device work with the wacom drivers?

What is the output of:

xsetwacom --list devices

Currently the Huion stuff is not added to the databse in general, which leads to this behaviour

If your device does work with the wacom-driver you could test the following:

In: /usr/share/kde4/apps/wacomtablet/data/companylist
Add:

[256c]
name=Huion
listfile=huion_devicelist
driver=wacom-tools

Than create a file:
/usr/share/kde4/apps/wacomtablet/data/huion_devicelist

Add:
[006e]
model=H610
layout=unknown
name=Huion Tablet
padbuttons=8
wheel=no
touchring=no
touchstripl=no
touchstripr=no
hwbutton1=1
hwbutton2=2
hwbutton3=3
hwbutton4=8
hwbutton5=9
hwbutton6=10
hwbutton7=11
hwbutton8=12
Comment 2 Vince Herried 2014-11-08 15:52:31 UTC
[vince@desk2 ~]$ xsetwacom --list devices
HUION PenTablet stylus                  id: 10  type: STYLUS    
HUION PenTablet stylus                  id: 11  type: STYLUS    
HUION PenTablet eraser                  id: 13  type: ERASER    
HUION PenTablet pad                     id: 14  type: PAD       
[vince@desk2 ~]$ 

it sort of works with the wacom driver.  I have installed a new driver from digimend
http://digimend.sourceforge.net/wiki/DIGImend

And am confused at where it hooks in.

I've been able to get a wireshark trace of windows initializing it and setting the keys.
I started working with the DIGImend folks with this trace.
Comment 3 Christoph Feck 2014-12-13 18:36:23 UTC
Jörg, does comment #2 provide the requested information? Please set the bug status.
Comment 4 Vince Herried 2014-12-13 20:29:07 UTC
I can't seem to re-create using wacom driver.
Comment 5 Vince Herried 2015-01-03 18:07:09 UTC
OK, with some more poking I find that the wacom driver seems to be working
when I created xconfig file:
[vince@desk2 ~]$ cat -n  /etc/X11/xorg.conf.d/50-huion.conf 
     1  Section "InputClass"
     2      Identifier "digimend2 version"
     3      MatchIsTablet "on"
     4      MatchDevicePath "/dev/input/event*"
     5  #   use for wacom driver
     6      MatchProduct "PenTablet"
     7      Driver "wacom"
     8          Option "rotate" "half"
     9  #
    10  # settings for GIMP
    11  #
    12          Option  "Button1" "ctrl z"      # undo
    13          Option  "Button2" "shift e"     # eraser
    14          Option  "Button3" "n"           # pencil
    15          Option  "Button8" "shift ="     # zoom in
    16          Option  "Button9" "-"           # zoom out
    17          Option  "Button10"              # + pencil
    18          Option  "Button11"              # - pencil
    19          Option  "Button12"              # hand
    20  #                                                                                                    
    21  # end GIMP settings
    22  #
    23
    24   #   use for evdev 
    25   #   Driver "evdev"
    26   #      Option "InvertX" "on"
    27   #      Option "InvertY" "on"
    28  EndSection
    29


However in /var/log/Xorg.0.log complains about the values of the buttons.
And when I login KDE takes an error the system 
The kde system settings Wacom tablet settings doesn't find a tablet.

But
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[vince@desk2 ~]$ xsetwacom --list devices
HUION PenTablet stylus                  id: 8   type: STYLUS    
HUION PenTablet pad                     id: 11  type: PAD 
[vince@desk2 ~]$ xsetwacom -V
0.26.99


I will try to gather more information on the KDE crash.
Comment 6 Vince Herried 2015-01-14 14:29:52 UTC
I installed fedora 21 and tried again.
NOTE  in  /usr/share/kde4/apps/wacomtablet/data/companylist
if I forget the blank line before the Huion entry, then X  loops.

Fixed that.

Now the kde services tablet shows up
But still complains about missing Default profile.

while in services I re-plugged the tablet and it asked me if I wish to save preferences
I pick ok, it says Default not found.
Tried again.  this time just msg no Default found.
Comment 7 Vince Herried 2015-01-14 14:37:30 UTC
I had to add the entries on the fedora f21 system also.
What kind of data do you need now?
Comment 8 Vince Herried 2015-01-14 14:51:41 UTC
Hmm another thought , Can I manually create the Default file some place?
Maybe move on a little bit.
Comment 9 Christoph Feck 2015-01-14 23:36:33 UTC
Changing status until Jörg has time to answer.
Comment 10 Jörg Ehrichs 2015-01-15 01:19:45 UTC
This sounds a lot like a bug I "fixed" a while ago.

Short google search showed that Fedora21 has 2.0.2 as the latest version.

The easiest way to progress any further is to test the latest version from git

git clone git://anongit.kde.org/wacomtablet
git checkout releng2.1
mkdir build
cd build
cmake ../ -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` -DCMAKE_BUILD_TYPE=release
make install

I will check on sunday if i can somehow reproduce this bug in the current latest version and fix it then. Also release a new version. Something I wanted to do a long time ago anyway.
Comment 11 Vince Herried 2015-01-15 19:29:21 UTC
I tried building this on my F20 system.
cmake 7.2 M !
$
$
[vince@desk2 build]$ cmake ../ -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` -DCMAKE_BUILD_TYPE=release
-- The C compiler identification is GNU 4.8.3
-- The CXX compiler identification is GNU 4.8.3
-- Check for working C compiler: /usr/lib/ccache/cc
-- Check for working C compiler: /usr/lib/ccache/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/lib/ccache/c++
-- Check for working CXX compiler: /usr/lib/ccache/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
CMake Error at /usr/share/cmake/Modules/FindKDE4.cmake:98 (message):
  ERROR: cmake/modules/FindKDE4Internal.cmake not found in
  /home/vince/.kde/share/apps;/usr/share/kde-settings/kde-profile/default/share/apps;/usr/share/kde4/apps
Call Stack (most recent call first):
  CMakeLists.txt:16 (find_package)


-- Configuring incomplete, errors occurred!
See also "/home/vince/Documents/Huion/WacomDriverStuff/wacomtablet/build/CMakeFiles/CMakeOutput.log".
[vince@desk2 build]$ 


it is my recollection that the way Fedora buiilds KDE updating any part was problematic?

Should I give up on my F20 system ( my main platform ) or is there hope?
Comment 12 Jörg Ehrichs 2015-01-18 20:51:48 UTC
The problem is just some missing dependencies. So no need to worry. :)

The current version should run fine on your F20 system as i havn't changed the dependencies in a while and even the xsetwacom part shouldn't have changed much.

I will release a 2.1.0 in a few minutes on kde-apps and than hope it ends up soon at some fedora packagers so you do not need to go through the hassle of building it on your own.

I'll changed it to fixed and please reopen it, if the 2.1 does not fix the issue