SUMMARY In the latest (07April) 4.2.0 pre-alpha appimage (and the 04April one) trying to use the Tablet Tester causes krita to freeze and it has to be killed to close it down. This did not happen in earlier appimages. STEPS TO REPRODUCE 1. Run krita, New File - Create, Settings -> Configure Krita -> Tablet Settings, press the Open Tablet Tester bar/button. OBSERVED RESULT The tablet tester utility does not run and krita freezes. EXPECTED RESULT The tablet tester should run. SOFTWARE/OS VERSIONS Krita Version: 4.2.0-pre-alpha (git 6f3ea24) Languages: en_GB, en Hidpi: false ADDITIONAL INFORMATION
hm... can't reprodcue this on Krita Version: 4.2.0-pre-alpha (git 4022dd) Languages: en_US, en_GB, nl Hidpi: false Qt Version (compiled): 5.12.0 Version (loaded): 5.12.0 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.15.0-46-generic Pretty Productname: KDE neon User Edition 5.15 Product Type: neon Product Version: 18.04 I also cannot reproduce this with the appimage of 8th of april. Can you share a bit more about your system with us? Like which distro, etc?
I've just tried it with the 08Apr build (git 4022dda) and I get the freeze-crash. This does not happen with the 21Feb build (git 7dc0c43). Here is my system information for a Debian 9 system that I have just fully updated: Krita Version: 4.2.0-pre-alpha (git 4022dda) Languages: en_GB, en Hidpi: false Qt Version (compiled): 5.12.2 Version (loaded): 5.12.2 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.9.0-8-amd64 Pretty Productname: Debian GNU/Linux 9 (stretch) Product Type: debian Product Version: 9 Hardware Information GPU Acceleration: auto Memory: 16049 Mb Number of Cores: 8 Swap Location: /tmp OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "GeForce GTX 750 Ti/PCIe/SSE2" Version: "4.6.0 NVIDIA 390.87" Shading language: "4.60 NVIDIA" ------------------------------------------------- It also happens on a Linux Mint 18.3 system: Krita Version: 4.2.0-pre-alpha (git 4022dda) Languages: en_GB Hidpi: false Qt Version (compiled): 5.12.2 Version (loaded): 5.12.2 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.4.0-143-generic Pretty Productname: Linux Mint 18.3 Product Type: linuxmint Product Version: 18.3 Hardware Information GPU Acceleration: auto Memory: 16044 Mb Number of Cores: 8 Swap Location: /tmp OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "GeForce GTX 750 Ti/PCIe/SSE2" Version: "4.5.0 NVIDIA 384.130" Shading language: "4.50 NVIDIA" ------------------------------------------------
hm... Hey what is your tablet model? Maybe there's something funny going on with the driver. For me xinput --list outputs the following for the tablet devices: Wacom HID 5113 Pen stylus id=15 [slave pointer (2)] Wacom HID 5113 Pen eraser id=16 [slave pointer (2)] Wacom HID 5113 Finger touch id=17 [slave pointer (2)]
I am not getting any crashes either on my Windows 10 git master with Huion tablet (and tested with mouse). Would it be possible for you to use gdb to get a backtrace for this?
My tablet is a Wacom Intuos 'Pen and Touch' CT490/K but I have the Touch slider always set to off. The xinput listing shows: ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Wacom Intuos PT S 2 Pen stylus id=8 [slave pointer (2)] ⎜ ↳ Wacom Intuos PT S 2 Finger touch id=9 [slave pointer (2)] ⎜ ↳ Wacom Intuos PT S 2 Pad pad id=10 [slave pointer (2)] ⎜ ↳ 2.4GHz 2way RF Desktop Receiver id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Power Button id=7 [slave keyboard (3)] ↳ 2.4GHz 2way RF Desktop Receiver id=11 [slave keyboard (3)] ↳ USB Keyboard id=13 [slave keyboard (3)] ↳ USB Keyboard id=14 [slave keyboard (3)] ↳ 2.4GHz 2way RF Desktop Receiver id=15 [slave keyboard (3)] If I disconnect the tablet and reboot, the Wacom entries are not listed but it still does the freeze-crash using the mouse. (The '2.4GHz 2way' entries are for my wireless mouse.) I've just tried Windows 10 using the 07Apr g6f3ea24f84.zip build and that does not freeze-crash. (Same computer, different boot drive plugged in.) I wonder if an Ubuntu system has this problem? I'll try to learn how to use gdb (dbg?) and report back on anything I can find.
OK, I've had another look at it and it's not a crash. What happens is that the small tablet tester sub-window (with the test area and report list) appears behind the Configure Krita window. This time, I moved the Configure Krita window far enough to notice the smaller window behind it. With hindsight, I should have noticed that the Configure Krita window did not have focus until I moved it around, then it lost focus when I let go of it. So, it is a bug but not a crash. I don't know how to change the Importance category of this report.
Thanks for that! I changed the severity and title, can you add your desktop enviroment to a comment? Because it isn't happening on Plasma. I guess we can try to force the tablet tester to be always on top, or maybe put it into a tab of those settings instead of another modal window. Scott, would you like to take a look at this?
My vote would be to put in the configuration area. I kind of don't like having popups over popups in general for UI stuff -- which is what it does now. One option would have it be on the right side of the existing screen. We probably have space. I haven't look at the code to know how hard it would be to move though.
Created attachment 119315 [details] Screenshot tablet tester windows I attach a screenshot showing the situation. My DE is MATE 1.16.2 In the screenshot I've arranged the windows to show them both. The tablet tester window has focus so why isn't it on top? I thought that was a DE function.
Git commit 1e5626c0a590a2e6384ab9c5e982c4e6aca3dce3 by Boudewijn Rempt. Committed on 09/04/2019 at 11:29. Pushed by rempt into branch 'master'. Tablet tester: set the Window flag to Dialog That way, it will be shown on top of the widget that's its parent, hopefully helping some X11 window managers. M +2 -2 libs/ui/input/wintab/drawpile_tablettester/tablettester.cpp https://commits.kde.org/krita/1e5626c0a590a2e6384ab9c5e982c4e6aca3dce3