autokey-qt crashes on start in kubuntu 16.10

Bug #1633379 reported by Günter Haus
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
autokey (Ubuntu)
Fix Released
Undecided
Thomas

Bug Description

autokey-qt
X protocol error:
<class 'Xlib.error.BadAccess'>: code = 10, resource_id = 214, sequence_number = 19, major_opcode = 33, minor_opcode = 0

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: autokey-qt 0.90.4-1 [modified: usr/bin/autokey-qt]
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Oct 14 10:45:50 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-11-24 (324 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
SourcePackage: autokey
UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)

Revision history for this message
Günter Haus (mcframe) wrote :
Revision history for this message
Filipe Martins (filipe.martins) wrote :

Hello,

I also had an error when starting autokey in 16.10 that I solved by uninstall it and then install again.

I think the error code it's not the same but I hope it helps you.

Best regards.
Filipe

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in autokey (Ubuntu):
status: New → Confirmed
Revision history for this message
Günter Haus (mcframe) wrote :

Update:
bug still exists on (K)Ubuntu 17.04

Revision history for this message
Thomas (tux12345) wrote :

This issue is fixed in 0.95.9, which is part of Ubuntu 20.04

Changed in autokey (Ubuntu):
assignee: nobody → Thomas (tux12345)
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.