Bug 343811 - autokey makes KDE software crash when used within an ubuntu unity environment
Summary: autokey makes KDE software crash when used within an ubuntu unity environment
Status: RESOLVED UPSTREAM
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-05 12:19 UTC by Wolf Drechsel
Modified: 2015-02-06 11:34 UTC (History)
1 user (show)

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 Wolf Drechsel 2015-02-05 12:19:15 UTC
My system:
ubuntu 14.04
unity desktop
4GB RAM

Whenever I try to use the "autokey" utility (https://code.google.com/p/autokey/) on a kde application, it produces bogus characters and makes the application crash. Tried it with kontact, kate, keepass2, kde control module, Kwalletmanager, the calligra suite.

Reproducible: Always

Steps to Reproduce:
1. type an abreviation saved in autokey within a kde application such as kontact, kate, keepass2, kde control module, Kwalletmanager, the calligra suite

Actual Results:  
bogus characters appear, kde application hangs

Expected Results:  
expand the abreviation to the saved string. E.g. I saved: "mfg" should produce "Mit freundlichen Grüßen,
Wolf Drechsel".
Comment 1 Christoph Feck 2015-02-05 21:30:26 UTC
Does it also happen with pure Qt applications?
Comment 2 Wolf Drechsel 2015-02-05 21:38:10 UTC
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 ):
Comment 3 Christoph Feck 2015-02-05 22:55:16 UTC
Firefox is no Qt application. Popular Qt applications are VLC, SMPlayer, Scribus, etc.
Comment 4 Wolf Drechsel 2015-02-06 08:05:58 UTC
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
Comment 5 Christoph Feck 2015-02-06 11:34:25 UTC
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.