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

runcat after screen inactivity #14

Closed
Gohub007 opened this issue Apr 19, 2021 · 22 comments · Fixed by #22
Closed

runcat after screen inactivity #14

Gohub007 opened this issue Apr 19, 2021 · 22 comments · Fixed by #22
Assignees
Labels
bug Something isn't working

Comments

@Gohub007
Copy link

runcat stops running after the screen went dark by gnome power settings, have to restart runcat in the gnome extension once again. not so after a suspend of the linux box

@win0err
Copy link
Owner

win0err commented Apr 19, 2021

Hi! Which system do you use? Please, provide OS & GNOME versions

@Gohub007
Copy link
Author

Hi there, we are running it on EndeavourOS Linux 5.11.15-arch1-2 with Gnome 40.0-1 actually first I thought it may be caused by wireless network but today after a resume on wired network I had to restart it again. It seems sometimes just stop working, sometimes after resume sometimes after the screen went black. I keep a eye on it.

@hparlak
Copy link

hparlak commented Apr 27, 2021

I have the same problem with Fedora 34 + Gnome 40.0.0

@win0err
Copy link
Owner

win0err commented Apr 27, 2021

Will dig into this, thanks!

@hparlak
Copy link

hparlak commented Apr 27, 2021 via email

@prasadpatil25
Copy link

Facing the same issue, I freshly installed Fedora 34 (Gnome 40).

@win0err win0err added the bug Something isn't working label May 8, 2021
@win0err win0err self-assigned this May 8, 2021
@JanitorHead
Copy link

Happens the same to me in Fedora 34 (Gnome 40)

@win0err
Copy link
Owner

win0err commented May 11, 2021

@Rafablues94, on RunCat v12? I've tried to fix the bug in this version. It's hard to reproduce the bug :-(
If you have any steps to reproduce the issue, please leave a comment.

@win0err
Copy link
Owner

win0err commented May 17, 2021

@Rafablues94, @prasadpatil25, @Gohub007, @hparlak: does the issue still occur?

@JanitorHead
Copy link

Yeah, it keeps happening. Last time was today after a reboot, the percent showed 0 until I disabled and enabled the extension.

@prasadpatil25
Copy link

It can be reproduced after putting the computer to sleep and waking it up again.

@prasadpatil25
Copy link

A quick fix (and temporal fix) can be to restart the extension when double-clicked.

@KaboomPhysicist
Copy link

KaboomPhysicist commented Aug 13, 2021

Same problem in Manjaro 21.1.0 with Gnome 40.3.0 with X11. It stops working when screen locks.

@Elinvention
Copy link

I have the same issue and this error message pops up in the logs:

JS ERROR: Error: Argument interval: value is out of range for uint32
_addTimeout@/home/elia/.local/share/gnome-shell/extensions/runcat@kolesnikov.se/timer.js:38:28
_tick@/home/elia/.local/share/gnome-shell/extensions/runcat@kolesnikov.se/timer.js:33:14
_addTimeout/this.timeout<@/home/elia/.local/share/gnome-shell/extensions/runcat@kolesnikov.se/timer.js:38:83

win0err added a commit that referenced this issue Oct 12, 2021
@win0err
Copy link
Owner

win0err commented Oct 12, 2021

@Elinvention, @KaboomPhysicist, @prasadpatil25, @Rafablues94, @hparlak, @Gohub007,
I've released version 15 with a probable fix of the issue. It will be available in a couple of days on extensions.gnome.org.
Please, send some feedback about the issue in the new release.

P.S. @Elinvention, thank you for the error message!
P.P.S. Available on https://extensions.gnome.org/extension/2986/runcat/

@KaboomPhysicist
Copy link

KaboomPhysicist commented Oct 15, 2021

I still have the same issue after update. This is the message in the logs:

JS ERROR: Error: Argument interval: value is out of range for uint32
_addTimeout@/home/cs/.local/share/gnome-shell/extensions/runcat@kolesnikov.se/timer.js:38:28
_tick@/home/cs/.local/share/gnome-shell/extensions/runcat@kolesnikov.se/timer.js:33:14
_addTimeout/this.timeout<@/home/cs/.local/share/gnome-shell/extensions/runcat@kolesnikov.se/timer.js:38:83

The extension works after restarting the Gnome Shell, but it keeps freezing after a suspension or log out.

Gnome version: 40.4.0

@flickowoa
Copy link

flickowoa commented Oct 16, 2021

@Elinvention, @KaboomPhysicist, @prasadpatil25, @Rafablues94, @hparlak, @Gohub007, I've released version 15 with a probable fix of the issue. It will be available in a couple of days on extensions.gnome.org. Please, send some feedback about the issue in the new release.

P.S. @Elinvention, thank you for the error message! P.P.S. Available on https://extensions.gnome.org/extension/2986/runcat/

is it out yet? cuz i redownloaded it and ive still got the issue

@win0err
Copy link
Owner

win0err commented Oct 16, 2021

@Elinvention, @KaboomPhysicist, @prasadpatil25, @Rafablues94, @hparlak, @Gohub007, I've released version 15 with a probable fix of the issue. It will be available in a couple of days on extensions.gnome.org. Please, send some feedback about the issue in the new release.
P.S. @Elinvention, thank you for the error message! P.P.S. Available on https://extensions.gnome.org/extension/2986/runcat/

is it out yet? cuz i redownloaded it and ive still got the issue

New version is available only for GNOME 3.38, 40 and 41

@win0err
Copy link
Owner

win0err commented Oct 16, 2021

I still have the same issue after update. This is the message in the logs:

JS ERROR: Error: Argument interval: value is out of range for uint32
_addTimeout@/home/cs/.local/share/gnome-shell/extensions/runcat@kolesnikov.se/timer.js:38:28
_tick@/home/cs/.local/share/gnome-shell/extensions/runcat@kolesnikov.se/timer.js:33:14
_addTimeout/this.timeout<@/home/cs/.local/share/gnome-shell/extensions/runcat@kolesnikov.se/timer.js:38:83

The extension works after restarting the Gnome Shell, but it keeps freezing after a suspension or log out.

Gnome version: 40.4.0

Thank you, I'll keep trying to fix the issue

@Netherquark
Copy link

Netherquark commented Oct 29, 2021

Chiming in to say I'm also experiencing this on Fedora 34 + Gnome 40.4
Just downloaded the extension today and gotta say, I love the cute cat.
I have the following configuration:
image
image

So I pressed Super + L and went afk for a while. Returned, and resumed work and the cat was sleeping. I tried locking and unlocking again, suspending and reopening my computer, both together, but nothing works. I also tried reinstalling the extension, but the cat is still sleeping. This is what the cat looks like, even though I'm actively using my computer:
image

Edit: The screen went off by itself after 5 minutes of inactivity, I resumed my work and the cat was back at it. I don't know what happened here. Maybe this is a different issue?

@win0err win0err linked a pull request Jan 31, 2022 that will close this issue
@win0err
Copy link
Owner

win0err commented Jan 31, 2022

@Netherquark, @KaboomPhysicist, @Gohub007: please, install v17 from https://extensions.gnome.org/extension/2986/runcat/. If the bug will happen again, please, reopen the issue

@win0err
Copy link
Owner

win0err commented Jan 31, 2022

Thanks to @nirfse for testing!

dev-hann added a commit to dev-hann/gnome-runcat that referenced this issue Sep 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants