Autokey 0.94.1 "Automatically start AutoKey at login" not working.

[BiNh0X]

System
Ubuntu MATE 18.04 LTS

Autokey 0.94.1 "Automatically start AutoKey at login" not working.

"Automatically start AutoKey at login" checkbox not save state on clicking in "OK" button.

[sporkwitch]

CNR
Kubuntu 18.04 LTS
Autokey 0.94.1-0ubuntu3

Try uninstalling and reinstalling. Also verify ~/.config/autokey and its contents are writeable

[BiNh0X]

It does not work and ~/.config/autokey is writable. All configuration options save, except for automatic login initialization.

[sporkwitch]

PPA or built it yourself?

[BiNh0X]

PPA.

[sporkwitch]

I'll try to spin up a VM later and see if i can reproduce.

[BiNh0X]

Dear,

After I installed XDM and this one goes to automatic startup, AutoKey has now accepted to save the state "Automatically start AutoKey at login" checkbox. What is it?
EDIT.: This is a new system installation.

[AdamPS]

I have the same problem on Ubuntu 18.04 (vanilla - not mate or kubuntu).

autokey-gtk 0.95.1

Is there any more information that we can provide to help? Thanks

[luziferius]

Try to create the ~/.config/autostart folder. I suspect that it is missing on your system.
This directory is used by the desktop environment. During startup, it reads all .desktop files in there and executes them.

The current implementation does not check if the directory exists and then even completely silences the error messages to make sure you don’t know why it fails… 🥇 👎

Here, it checks if the file exists, and if not, creates it. This fails, if the parent directory is missing.

autokey/lib/autokey/gtkui/settingsdialog.py

Lines 105 to 116 in abf3345

	if self.autoStartCheckbox.get_active():
	if not os.path.exists(AUTOSTART_FILE):
	try:
	inFile = open(DESKTOP_FILE, 'r')
	outFile = open(AUTOSTART_FILE, 'w')
	contents = inFile.read()
	contents = contents.replace(" -c\n", "\n")
	outFile.write(contents)
	inFile.close()
	outFile.close()
	except:
	pass

Fixing this should be pretty easy and will (probably) go into 0.95.3.

[AdamPS]

Great, thanks @luziferius, creating that directory fixed it.

This also explains @BiNh0X situation where installing XDM fixed it - presumably that app created the autostart directory.

[luziferius]

I’ve rewritten the autostart handling. Fixed it in 0420250 and added a user data migration task in 4334f8d

[AdamPS]

Great thanks, Adam

…

On 9 August 2018 21:29:12 BST, Thomas Hess ***@***.***> wrote: I’ve rewritten the autostart handling. Fixed it in 0420250 and added a user data migration task in 4334f8d -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #149 (comment)