Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Autokey-qt in Kubuntu 22.04 does not shut down properly #919

Open
3 of 16 tasks
ineuw opened this issue Nov 1, 2023 · 1 comment
Open
3 of 16 tasks

Autokey-qt in Kubuntu 22.04 does not shut down properly #919

ineuw opened this issue Nov 1, 2023 · 1 comment

Comments

@ineuw
Copy link

ineuw commented Nov 1, 2023

AutoKey is a Xorg application and will not function in a Wayland session. Do you use Xorg (X11) or Wayland?

Xorg

Has this issue already been reported?

  • I have searched through the existing issues.

Is this a question rather than an issue?

  • This is not a question.

What type of issue is this?

Bug

Choose one or more terms that describe this issue:

  • autokey triggers
  • autokey-gtk
  • autokey-qt
  • beta
  • bug
  • critical
  • development
  • documentation
  • enhancement
  • installation/configuration
  • phrase expansion
  • scripting
  • technical debt
  • user interface

Other terms that describe this issue if not provided above:

system interaction with autokey-qt

Which Linux distribution did you use?

Kubuntu 22.04.3 english

Which AutoKey GUI did you use?

Qt

Which AutoKey version did you use?

96.0

How did you install AutoKey?

Using the .deb files downloaded from

Can you briefly describe the issue?

When selecting restart in Kubuntu, the process defaults to the 30 second delay for all users because of autokey-qt is still running. When autokey-qt is exited manually prior to the restart, it is immediate.

Can the issue be reproduced?

Always

What are the steps to reproduce the issue?

  1. Install autokey-qt in kubuntu without installing the gtk version.
  2. Start autokey-qt manually or autostart on login, and then select Restart from the menu.
  3. In my case, I must wait 30 seconds for the restart process to start because Autokey is not recognized.
  4. I reported this issue because to Ku and it turns out that they are using Kwin which is a modified version of the linux OS restart/logout/shutdown process.
  5. Kwin does not terminate autokey-qt.
  6. Kwin does not recognize the /etc/sudoer modifications.7.

What should have happened?

Interact with the system and restart immediately.

What actually happened?

Hangs for 30 seconds on each restart.

Do you have screenshots?

No

Can you provide the output of the AutoKey command?

No

Anything else?

There is a possibility that NOT installing the gtk component causes this, but I don't want to install it. The autokey-gtk version is in Linux Mint Cinnamon 21.2 where an earlier attempt at using qt failed, and using Kubuntu 22.04.3 solely with autokey-qt to enhance my understanding and hoping to

I also added my name and permissions to the /etc/sudoers file to let me restart without 'sudo'. The contents of this file has no effect on Kubuntu Kwin system.

# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL
%ineuw ALL=NOPASSWD: /sbin/halt, /sbin/reboot, /sbin/poweroff

# Allow members of group sudo to execute any command
%sudo	ALL=(ALL:ALL) ALL
%ineuw	ALL=(ALL:ALL) ALL

@josephj11
Copy link
Contributor

I don't notice this because everything is so slow on my 22.04 notebook. LOL

I don't think your sudoers mod is the best way to do that. It appears to be a huge security hole. If anyone walks up to your logged in computer, they can do any elevated command if you're not there to stop them.

If you happen to accidentally run some questionable code with sudo in it, it will just run without giving you a chance to change your mind. That's kind of the whole point of sudo in the first place. This might include malicious code running from a website you visit as well although that's less likely because almost no one leaves it unlocked like that.

I think adding your user to the sudo group is better. It still requires your password for sudo to work.
If you want to, there's a timeout parameter in the sudoers file you can set so that the permissions stay live for e.g. 15 minutes in a shell after you first enter the correct password.

shelelia@blue:~/Dropbox/Internal_J_R/rpq$ groups
shelelia adm cdrom sudo dip plugdev lpadmin lxd sambashare

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants