autokey starting maximized (not in system tray)

[Duns]

It's so in Kubuntu 18.04 (beta final): autokey (auto)start as window, not, as expected (and as in Kubuntu 17.10) as system tray icon.

[Duns (jduns)]

This is a Bionic Beaver bug: I don't know how to tell you...

[Duns (jduns)]

Solved! Today I removed in Settings - autostart the autokey-gtk -c starting program, and then added autokey program. So the problem is solved.

[Duns (jduns)]

No! Solved once yes and once not. This is the .desktop:

[Desktop Entry]
Categories=GNOME;GTK;Utility;
Comment[en_US]=Program keyboard shortcuts
Comment=Program keyboard shortcuts
Exec=autokey-gtk -c
GenericName[en_US]=Keyboard Automation
GenericName=Keyboard Automation
Icon=autokey
MimeType=
Name[en_US]=AutoKey
Name=AutoKey
Path=
StartupNotify=true
Terminal=false
TerminalOptions=
Type=Application
X-DBUS-ServiceName=
X-DBUS-StartupType=
X-KDE-SubstituteUID=false
X-KDE-Username=

[Duns (jduns)]

And this is the warning message in terminal:

duns@sar-intel1:~$ autokey-gtk -c
/usr/lib/python2.7/dist-packages/autokey/gtkapp.py:24: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, Gdk, GObject, GLib
/usr/lib/python2.7/dist-packages/autokey/gtkui/notifier.py:19: PyGIWarning: Notify was imported without specifying a version first. Use gi.require_version('Notify', '0.7') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, Gdk, Notify
/usr/lib/python2.7/dist-packages/autokey/gtkui/configwindow.py:20: PyGIWarning: GtkSource was imported without specifying a version first. Use gi.require_version('GtkSource', '3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, Pango, GtkSource, Gdk, Gio

duns@sar-intel1:~$ autokey
/usr/lib/python2.7/dist-packages/autokey/gtkapp.py:24: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, Gdk, GObject, GLib
/usr/lib/python2.7/dist-packages/autokey/gtkui/notifier.py:19: PyGIWarning: Notify was imported without specifying a version first. Use gi.require_version('Notify', '0.7') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, Gdk, Notify
/usr/lib/python2.7/dist-packages/autokey/gtkui/configwindow.py:20: PyGIWarning: GtkSource was imported without specifying a version first. Use gi.require_version('GtkSource', '3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk, Pango, GtkSource, Gdk, Gio

[Duns (jduns)]

Seems that the problem is "autokey-gtk -c" command: instead works correctly "autokey" command.

[Thomas (tux12345)]

This is caused by the KDE session restoration mechanism, which starts a second instance.
The second instance sees the first and pings it to open the main window.

Either exclude autokey from the session restoration mechanism or deactivate the autostart setting.

[Colin Hemming (b-ubuntuone14)]

I have been having the same issue with Xubuntu 20.04. There are two instances being added in the session (restart if running). Sometimes it opens the interface, other times the two start so close together that they trip over each other and one produces an error window creating the lock file in /run/user/1000/autokey.

The app is running (and minimised in the tray) but the whichever window comes up is frustrating!