Version: 0.6.0 (using 4.3.2 (KDE 4.3.2), Debian packages) Compiler: cc OS: Linux (i686) release 2.6.30-2-686 I use Kvkbd as the primary text input system on my Fujitsu tablet (Wacom digitiser) now running Debian Squeeze. Since upgrading kvkbd from Lenny to Squeeze, kvkbd regularly crashes whenever I try to type a letter using my stylus. Sometimes, the kvkbd window will just disappear and I'll have to restart it. Usually, though, the last character I typed will get 'locked down' - that is, repeat continuously - until I plug in a keyboard or launch a new kvkbd so I can hit a different key which seems to snap it out of its loop. Kvkbd does not generate any dumps when it krashes which means that I don't have any dumps to attach to this report. Guidance on creating a useful crash dump would be appreciated is appreciated I don't know Linux well enough to compile my own kvkbd from source so I'm limited to the tools I can get through apt-get. Kvkbd appears to behave a little better when I use a USB mouse to type, but I haven't tested this extensively.
Does the crash notification window (DrKonqi) appear? If yes, it would be useful to attach the backtrace to the bug report. For creating backtraces with debugging symbols enabled, also see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
KDE 4's crash handler does not appear when kvkbd crashes (and I know that it's installed because it pops up when other KDE programs regularly crash). I don't think that Debian Squeeze packages debug symbols with kvkbd, further complicating things. Could I run kvkbd within some tracing or debugging application to get a useful output? If so, what should I punch into bash?
Created attachment 39161 [details] DrKonkqi crash report
Created attachment 39162 [details] valgrind crash report
I'm attaching two debugging reports: one is from valgrind and the other from DrKonqi (which surprisingly appeared when kvkbd crashed under valgrind's supervision) I apologise in advance that many of the debugging symbols are missing. Unfortunately, Debian (to the best of my knowledge) doesn't come with kvkbd symbols unless they're buried in another package.
Having the same problem on Debian testing on a Motion Computing M1400 tablet. The only difference to the original post is that I don't see the repeating character behaviour. Crashes seem random and unpredictable. The bug report window pops up infrequently after a crash but always reports that there is no usable information to submit. Is there anything I can do to submit useful information? Only two crashes while I was writing this. Not enough to make an excellent app unusable but kind of annoying.
Can you check with Debian, if your kvkbd build includes r1140981 from upstream? Unfortunately, there is no maintainer, so no official release was made, but said commit from over three years ago fixed some uninitialized variables, which could be the cause for the crashes you see.
> Is there anything I can do to submit useful information? Best would be, if you compile with debug symbols enabled, reproduce the crash, and add the backtrace. The one from comment #3 has no information.
Thanks for the interest. In that kvkbd has been orphaned in Debian since Jan 2012, I'm not sure who to contact. I'd be happy to try the compile route but sorry to say you'll have to give me some pointers on how to proceed.
Should we let this bug die? I don't use kvkbd anymore because it's almost completely unsupported in KF5. I think the recommended practice is to use a plasmoid, of which there used to be a great one until KDE migrated from 4 to 5 and most things broke.
Thank you for the report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Debian pulled kvkbd in 2018, so I'm unable to test without some hacks. May as well close the bug.
Resolving as both users are on Debian and they have removed the package since the repoort.