High CPU after standby

[qtheuret]

After put my laptop on stand-by, when I re-open my session, my CPU load is 100% for one of my 4 CPUs and after an htop, I showed that 'gluqlo -root' was the process that load my CPU.

I don't know if you have an idea of where is the problem but I raise this issue at least for information.

I didn't have this issue each time I put my laptop on stand-by.

[KevinNadaud]

I have the same problem on Linux mint 18 cinnamon edition.
Gluqlo use 100% of a core.

[kazoni]

I'm in this boat as well. It seems that it doesn't release resources when you wake the computer back up. I have to kill the process manually after a few sleep cycles.

[jdorenbush]

Same problem here. I'm running Ubuntu 16.04.

In my System Monitor it is listing the gluqlo process twice and my CPU load is 100%

[alexanderk23]

Hey,
Thanks for reporting and sorry for the (very) late reply. Can't reproduce this bug at the moment, since I have no Linux laptops around, but I'll try to come up with something. Sorry again.

[cyprianoeduardo]

Same problem here. I'm running Ubuntu 16.04.

[joemar-tagpuno]

The same with me. I'm using Ubuntu 16.04 xenial and x86_64 Linux 4.13.0-45-generic kernel

[nejck-ikservis]

happens from time to time ob my raspberry also...

seems like it has something to do with not correctly exiting / releasing resources...

sometimes I see text written over the screen saying it sent sigterm but it’s still running...

[KyubiSystems]

See the same thing on my RasPi 3B+ running Raspbian Stretch. Ended up writing a cron job to kill the gluqlo process every 6 hours.

The periodic error message text on the screen can be fixed by setting the captureStderr option to False in the ~/.xscreensaver config file.

[kenchou]

I also got the same problem.

Reproduce:

when gluqlo screensaver lauched:

1. move the mouse or press any key, prompt input your password
2. do not input the password, cancel or wait until timeout
3. new gluqlo process will show up in htop in ssh console.

Repeat the above actions, I got a lot of gluqlo processes, and CPU usage 100%.

[HareshKarnan]

can confirm this issue still persists. Tried on Ubuntu 18