Closed GoogleCodeExporter closed 8 years ago
This bug is fixed in the current PPA release. I don't know if we will be able
to get
an update into Lucid to fix this, but in the mean time add the PPA and update,
that
will fix your problem.
Original comment by cdekter
on 11 May 2010 at 1:08
Luke, can you comment on the possibility of maybe introducing a patch into
Lucid?
Original comment by cdekter
on 11 May 2010 at 1:08
Sure. I've forwarded this downstream to Ubuntu in
https://bugs.launchpad.net/autokey/+bug/578608 to keep track of the issue. I'll
have
to try to reproduce it some time tomorrow.
I looked through the changes in SVN since 0.61.7. I couldn't find a commit
message
that indicated this bug was fixed. I'll be happy to prepare a SRU if you can
point
out the change that needs to be made.
Original comment by Luke.Faraone
on 11 May 2010 at 2:02
The fix for the problem is in r233 and was originally reported as issue #27
Original comment by cdekter
on 11 May 2010 at 2:10
And to be exact, the change is in src/lib/gtkui/settingsdialog.py
Original comment by cdekter
on 11 May 2010 at 2:11
The change you linked occurred before 0.61.7 was released, and was already
included when Lucid was released.
Original comment by Luke.Faraone
on 18 Aug 2010 at 2:33
Odd... oh well, the original reporter hasn't come back with any more info so I
think we're fine here.
Original comment by cdekter
on 18 Aug 2010 at 2:44
I have the same problem with AutoKey (GTK UI) 0.71.2 on Ubuntu Studio 11.4
Original comment by aeck...@gmail.com
on 27 Aug 2011 at 3:20
Can you run AutoKey in the terminal with autokey-gtk -l and post the output
that is produced when you try to select the autostart option?
Original comment by cdekter
on 28 Aug 2011 at 9:14
Original issue reported on code.google.com by
dbmi...@gmail.com
on 10 May 2010 at 10:07