[krita] [Bug 392251] Krita appimages crash or hang when using touch on a wacom cintiq touch display
https://bugs.kde.org/show_bug.cgi?id=392251 Boudewijn Rempt changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #25 from Boudewijn Rempt --- Sorry, your wall-of-text approach of admonishing us for being bad at figuring out how you messed up your system means we cannot do anything with your reports. I am closing all reports that you made that are still open. Please don't reopen them. Please refrain from making further reports; you are apparently incapable of normal interaction. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392251] Krita appimages crash or hang when using touch on a wacom cintiq touch display
https://bugs.kde.org/show_bug.cgi?id=392251 --- Comment #24 from Boudewijn Rempt --- No, you wouldn't get this problem when running a local build because the problem is some sort of binary incompatibility between the libraries inside the appimage and local X11 libraries. That shouldn't happen for properly versioned libraries, but it does... So we need to think whether we should include more or fewer libraries in the appimage. I need to consult the appimage people on this problem. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392251] Krita appimages crash or hang when using touch on a wacom cintiq touch display
https://bugs.kde.org/show_bug.cgi?id=392251 Victor Wåhlström changed: What|Removed |Added CC||victor.wahlstrom@initiali.s ||e --- Comment #23 from Victor Wåhlström --- I can reproduce this issue on a Cintiq Pro 16, but not consistently. I've also had it happen on a Surface Pro 2 (wacom tech) a year or so ago, both using various versions of Kubuntu/KDE, both running appimages. I have so far not managed to get it when running a local build. Since palm rejection in general isn't great I ended up disabling touch entirely when drawing: xsetwacom --set "Wacom Cintiq Pro 16 Touch Finger touch" touch off While not a solution to this problem, it does work around the issue. As to why you have to disable gestures with xsetwacom to get gestures in Krita: xsetwacom gestures is an in-driver legacy feature, intended for systems that don't support multitouch. This means that when driver gestures are on, Krita won't receive touch events. See https://github.com/linuxwacom/xf86-input-wacom/wiki/Multitouch for more information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392251] Krita appimages crash or hang when using touch on a wacom cintiq touch display
https://bugs.kde.org/show_bug.cgi?id=392251 --- Comment #22 from ocumo --- (In reply to Boudewijn Rempt from comment #21) > We don't support the flatpak version ourselves, and it's up to the people > maintaining the flatpak to update us when they change how flatpaks are > installed. Yeah, but you guys certainly do care that whatever shows up in Krita's webpage is not wrong, wouldn't you? I hope the missing/truncated part of your sentence is "...so I will of course ask them to check and fix that as soon as possible, thanks for catching that one mate!" Is it? Otherwise, it doesn't take much to prove, for example, that 'flatpak remote-add --if-not-exists flathub' is not a valid command and will fail; in case my report is not convincing, the man page should suffice. So... Seriously?? What would be the point on, knowingly, keep incorrect installation instructions on the download page of the product that takes so much effort and money to put together? Somebody else's problem? I don't get it. I'm just trying to report a problem on the Krita webpage, to the Krita developers, on something relevant to this thread. I though you guys, Krita owners, should be the natural choice. "The people" and "they" are too vague for me. But hey. Still: Would it be somehow possible to kindly forward this information to someone who could do something to fix wrong information in the official Krita download webpage, where potential Krita users will have trouble with bad instructions? I mean, I don't need it for myself any more, I've had my bad experience and frustrations already. I thought other people, less savvy with computers, should be saved from that "User Experience" (pissed users === detractors of your project). Sorry, this time I catastrophically fail to see or understand your position on this. In this case, it's _not_ about whoever creates flatpaks or whatnot: it's about *Krita users* using Krita official documentation that is wrong, whoever wrote it. As user, I don't care if it was Bob, Jane or Alice. It says "Krita" all over the place. Users are the reason of your (or any) project. Without them, no project. Users don't have any business in the innermost administrative details of who is assigned what or who steps/doesn't step on who's toes, etc. That's how laundry works at home. It's far, far too much beyond what any user needs or wants to know. Sadly, this reminds me of Public Services where one asks at the Information Counter about something and they redirect us to another Information Counter in which we can ask where to find information on who may have information about the proper Information Counter. I hope I am wrong, but that's how it looks to me. Please show me how incredibly wrong I am, and I will fully retract all the rants. Anyone, please ? > I don't have access to a cintiq with this particular touch functionality, so > I cannot test what's up with it, all I could think of is not shipping libxi, > but I fear that that would break appimages for everyone. I totally understand. I can only say that I maintain my humble offer of contribution. If you would like to try some isolated experiments, please by all means let me know if I can help in any way. This is _not_ about me, though. We are talking about one of the top models, professional class, most popular and arguably the best brand on its business. The point is not Wacom. It's its users. Not me, in particular. I can always find my way with other solutions if necessary, FOSS or not. It's the "top professional" ones. Anyone who is _really_ serious about digital illustration business, won't survive with a BambooFun tablet, period. They do use the big toys, as it's public. I don't think Krita is meant to be exclusively for hobbyists, poor students or people who can't afford and won't use pirate copies of Adobe/Corel products. It's for all. Fully supporting some of the top Wacom devices, the most popular amongst professionals, should be just a natural goal for Krita. And removing any annoyances that disturb that goal should therefore be equally important. Any serious professionals googling for "Krita + Wacom Cintiq 27QHD" would get to this thread. I hope they understand that it is possible and don't get frustrated with my experience. If Krita could have one of those giant professional names we all admire (Aaron Blaise, Jason Seiler, Mike Luckovich, why not?) acknowledging and endorsing this project, we all would be very happy. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392251] Krita appimages crash or hang when using touch on a wacom cintiq touch display
https://bugs.kde.org/show_bug.cgi?id=392251 --- Comment #21 from Boudewijn Rempt --- We don't support the flatpak version ourselves, and it's up to the people maintaining the flatpak to update us when they change how flatpaks are installed. I don't have access to a cintiq with this particular touch functionality, so I cannot test what's up with it, all I could think of is not shipping libxi, but I fear that that would break appimages for everyone. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392251] Krita appimages crash or hang when using touch on a wacom cintiq touch display
https://bugs.kde.org/show_bug.cgi?id=392251 --- Comment #20 from ocumo --- Created attachment 115761 --> https://bugs.kde.org/attachment.cgi?id=115761=edit Problems with the installation of the flatpak version of krita 4.1.5: Documentation issues and other In the attached file, I am detailing a number of problems faced when installing the current release of krita (4.1.5) using the Flatpak method. This is part of the investigation for the bug in this thread, thus the need to put this here, despite the fact that this opens new problems not directly related to the current bug. The relevance of this report about the Flatpak method, is that the Flatpak is an obvious and valid alternative to the appimages, which this thread show that have catastrophic compatibility issues with a very important, professional class hardware (Wacom Cintiq) that krita and Linux otherwise do support. In this case, Flatpaks can provide at the very least a fallback solution to broken appimages and/or the kritalime PPA has not been updated, among other scenarios in which users prefer/have to use Flatpak in their systems. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392251] Krita appimages crash or hang when using touch on a wacom cintiq touch display
https://bugs.kde.org/show_bug.cgi?id=392251 --- Comment #19 from ocumo --- I have been testing the flatpak installation of krita 4.1.5 for several minutes. The good news is that the flatpak version does NOT have the crash/hangup issue. Though I need to test more, it clearly is not failing as with the appimage versions, and touch functionality works exactly as with the kritalime PPA version (not perfect, but quite good). This seems to confirm that definitely there is something not well with the appimages 4.x.x, because neither 3.x.x appimages nor kritalime PPA installations, nor flatpak 4.1.5, have any of the reported problems. The bad news is that the installation instructions of flatpak in the https://krita.org/en/download/krita-desktop/ webpage are wrong and incomplete, and even the instructions in https://flathub.org/apps/details/org.kde.krita fail to provide important information. There is, in addition, another issue. I will provide an attachment with these notes and details, in my next post, so please I would really appreciate feedback/comments. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392251] Krita appimages crash or hang when using touch on a wacom cintiq touch display
https://bugs.kde.org/show_bug.cgi?id=392251 --- Comment #18 from ocumo --- Created attachment 115736 --> https://bugs.kde.org/attachment.cgi?id=115736=edit Installed libx11 related packages Ok, it seems that we need to understand whether the appimage is somehow built with an obsolete/inadequate library, or my system somehow has an inadequate/obsolete or somehow conflicting library. One thing that should be taken into consideration is that whatever you do to build the kritalime PPA version, is done OK and no one, including me, has complaints like this one about the hardware or system I am using with krita. What I can do is to analyse my system as thoroughly as needed to help reducing the scope of this investigation. I can't help with how the appimage is made, though. I can offer for starters, (please see the attached file), a list of all `libx11*` packages installed in my system; it's just the output of the command: `apt list libx11* --all-versions`. On top of that, the following information is relevant: All the installed packages come from the official ubuntu repos, either the bionic-updates or bionic sections. There are neither PPA versions nor manually compiled libraries, these or any others, as I am very careful with global systems files. If I ever have to compile anything, it's never a library or any kind of system files or files that somehow could have global scope. I actually almost never compile stuff and if I must, I would always do it in an isolated scope. Even Python programs that are not official are always enclosed in their specific environment. I know well how bad can it be to troubleshoot incompatible/conflicting dependencies. As for PPAs, I only risk those coming from serious projects, such as Krita. That being said, my interest is not to exclude my system out of the investigation. I certainly may have something bad in it, made some mistake or forgotten something. So, please if you could suggest more checks or system information that could help to simplify the troubleshooting, by all means, do. Important: is there a chance that someone from the appimage building team might also contribute their 5 cents? I also must remind the readers, because it's a long thread, that up to Krita 3.3.3, ALL those appimages work without any issue with my Wacom Cintiq device, even today! All the troubles started with the appimages of the Krita v4.x.x branch, all its versions. Apart from the Krita code: what else changed there? I am not yet convinced (though possible) that this is some kind of unique problem with my system, which is build on official Ubuntu packages on normal hardware. Finally: I don't like Flatpak, or Snaps: they are, by all comparisons I have been able to read online, quite inferior, by many reasons, to appimages. The reason why I would like to work with appimages, is for testing new versions of Krita, otherwise, I would just wait for your kritalime release and forget about it. So far I have seen Flatpak versions only for final releases. I'll try to find some time to test the available Flatpak, if you think that makes sense. Are there Flatpak versions of krita 4.2? In any case, I don't want to quit using appimages, unless Flatpak would work for me and there would be Flatpak versions for the testing Kritas. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392251] Krita appimages crash or hang when using touch on a wacom cintiq touch display
https://bugs.kde.org/show_bug.cgi?id=392251 --- Comment #17 from Boudewijn Rempt --- Okay, so this isn't an xcb implementation issue. There must be some weird incompatibility between the libxi the appimage contains and the libx11 on your system that only shows with this particular kind of touch event. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392251] Krita appimages crash or hang when using touch on a wacom cintiq touch display
https://bugs.kde.org/show_bug.cgi?id=392251 --- Comment #16 from ocumo --- I managed to do a quick test. Not good news. I have attached the outcome. This is exactly what I did: 1. Run the following in the terminal: xsetwacom -v --set 'Wacom Cintiq 27QHD touch Finger touch' gesture off 2. Run krita with debugger: dbg ./krita-4.2.0-pre-alpha-539f7d0-x86_64.appimage 3. Create new document. 4. Draw a couple of color lines using the Stylus. Note that the krita pointer was covered by the normal mouse pointer from the window manager. 5. Touch the tablet touchscreen with a bare finger. 6. Krita crashes/hangs as soon as touchscreen is touched with bare finger or sometimes even before that, just while using the stylus to e.g. select some color or resize some panel. 7. Press to get back the gdb promp. Collect the backtrace with this gdb command: thread apply all backtrace 8. Attach the whole krita stdout session from the console, which includes the backtrace. Note that the backtrace command is at line #317, and before that there is info that might be useful. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392251] Krita appimages crash or hang when using touch on a wacom cintiq touch display
https://bugs.kde.org/show_bug.cgi?id=392251 --- Comment #15 from ocumo --- Created attachment 115703 --> https://bugs.kde.org/attachment.cgi?id=115703=edit Backtrace and stdout of crash/hangup of krita-4.2.0-pre-alpha-539f7d0-x86_64.appimage Testing krita-4.2.0-pre-alpha-539f7d0-x86_64.appimage with a Wacom Cintiq 27QHD Touch display, in Kubuntu 18.04 (running Xfce). Outcome is not any better than with previous appimage versions, in fact first time the crash/hangup happened probably even touching the display with bare fingers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392251] Krita appimages crash or hang when using touch on a wacom cintiq touch display
https://bugs.kde.org/show_bug.cgi?id=392251 --- Comment #14 from ocumo --- Thank you very much Boudewijn. This is a step forward! I will try the appimage as soon as I can and post here the results. I need to find a bit of time, but I will. Meanwhile, I really appreciate your efforts, I know how much the Krita team is busy in making a very tough work with limited resources. You guys are doing such a great work. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392251] Krita appimages crash or hang when using touch on a wacom cintiq touch display
https://bugs.kde.org/show_bug.cgi?id=392251 --- Comment #13 from Boudewijn Rempt --- Could you try with this specific appimage: https://www.dropbox.com/s/h8e3csvzauar2zw/krita-4.2.0-pre-alpha-539f7d0-x86_64.appimage?dl=0 This one doesn't use our own xcb implementation, so who knows... It might be better. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 392251] Krita appimages crash or hang when using touch on a wacom cintiq touch display
https://bugs.kde.org/show_bug.cgi?id=392251 Boudewijn Rempt changed: What|Removed |Added Summary|Krita crashes/hang (and |Krita appimages crash or |sometimes takes with it the |hang when using touch on a |entire X system) when using |wacom cintiq touch display |Touch display | --- Comment #12 from Boudewijn Rempt --- Hi, Sorry for the late reply. I just missed the original bug report when it came in. The backtraces all point to a compatibility problem with XCB on your system. Which is strange, because I would sooner have expected issues with the nvidia drivers. I don't have exactly the same hardware, but with my setup (desktop with nvidia card, ubuntu 16.04 and 18.04, wacom cintiq hybrid companion), I don't see anything like this, but my cintiq is older and maybe does something different when it comes to touch :-( -- You are receiving this mail because: You are watching all bug changes.
