Description of problem: computer was in sleep mode error happened just after login again (autokey is in kde autostart folder) Version-Release number of selected component: autokey-qt-0.90.4-4.fc20 Additional info: reporter: libreport-2.2.2 cmdline: /usr/bin/python /usr/bin/autokey-qt -session 10caed9491000140085355500000015340024_1401171545_616818 dso_list: autokey-common-0.90.4-4.fc20.noarch executable: /usr/bin/autokey-qt kernel: 3.14.4-200.fc20.i686+PAE runlevel: N 5 type: Python uid: 1000 Truncated backtrace: qtapp.py:226:shutdown:OSError: [Errno 2] No such file or directory: '/home/fth/.config/autokey/autokey.pid' Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/autokey/qtui/notifier.py", line 99, in on_quit self.app.shutdown() File "/usr/lib/python2.7/site-packages/autokey/qtapp.py", line 226, in shutdown os.remove(LOCK_FILE) OSError: [Errno 2] No such file or directory: '/home/fth/.config/autokey/autokey.pid' Local variables in innermost frame: self: <autokey.qtapp.Application instance at 0xb76ac8ec>
Created attachment 899828 [details] File: backtrace
Created attachment 899829 [details] File: environ
Another user experienced a similar problem: I assume the issue happened after wake up from suspend reporter: libreport-2.2.2 cmdline: /usr/bin/python /usr/bin/autokey-qt -session 10caed9491000140136401300000015350019_1401378258_815007 dso_list: autokey-common-0.90.4-4.fc20.noarch executable: /usr/bin/autokey-qt kernel: 3.14.4-200.fc20.i686+PAE package: autokey-qt-0.90.4-4.fc20 reason: qtapp.py:226:shutdown:OSError: [Errno 2] No such file or directory: '/home/fth/.config/autokey/autokey.pid' runlevel: N 5 type: Python uid: 1000
Another user experienced a similar problem: I use the following autokey script bound to "<super> +f" key: import os import subprocess procresult = os.system('wmctrl -a " - Mozilla Firefox"') if procresult != 0: subprocess.Popen("/usr/bin/firefox") reporter: libreport-2.2.2 cmdline: /usr/bin/python /usr/bin/autokey-qt -session 10caed9491000140221245000000015540010_1402213301_618168 dso_list: autokey-common-0.90.4-4.fc20.noarch executable: /usr/bin/autokey-qt kernel: 3.14.8-200.fc20.i686+PAE package: autokey-qt-0.90.4-4.fc20 reason: qtapp.py:226:shutdown:OSError: [Errno 2] No such file or directory: '/home/fth/.config/autokey/autokey.pid' runlevel: N 5 type: Python uid: 1000
Another user experienced a similar problem: Im not quite shure. Maybe I played around with a autokey (python) start script reporter: libreport-2.2.2 cmdline: /usr/bin/python /usr/bin/autokey-qt dso_list: autokey-common-0.90.4-4.fc20.noarch executable: /usr/bin/autokey-qt kernel: 3.14.9-200.fc20.i686+PAE package: autokey-qt-0.90.4-4.fc20 reason: qtapp.py:226:shutdown:OSError: [Errno 2] No such file or directory: '/home/fth/.config/autokey/autokey.pid' runlevel: N 5 type: Python uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.