Summary: | autokey makes KDE software crash when used within an ubuntu unity environment | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | Wolf Drechsel <herr_oswald> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | cfeck |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Wolf Drechsel
2015-02-05 12:19:15 UTC
Does it also happen with pure Qt applications? No. There are minor glitches with firefox (missing characters, trigger words not completely erased), but no crash/hangs. Only kde apps are causing the severe problems ): Firefox is no Qt application. Popular Qt applications are VLC, SMPlayer, Scribus, etc. Sorry. Tried scribus: Within a textframe or a text editor window, the same problems occur: bogus characters, even if I after the expansion happened just type more characters. The app will not crash, but further text editing is not possible - just bogus characters. The same e.g. within a "Document settings" window. HTH, Wolf Please report this issue directly to Qt developers via https://bugreports.qt.io/ It is possible that the Qt event processing gets confused about the way autokey sends the fake key events. The KDE Workspace also offers a way to assign keyboard macros ("khotkeys"), and I do not know of similar issues there. |