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

[clock@schorschii] Desklet Clocks Freeze #1416

Open
portanav opened this issue Mar 4, 2025 · 14 comments · May be fixed by #1419
Open

[clock@schorschii] Desklet Clocks Freeze #1416

portanav opened this issue Mar 4, 2025 · 14 comments · May be fixed by #1419
Labels

Comments

@portanav
Copy link

portanav commented Mar 4, 2025

Desklet version/Build date

1.6

Cinnamon version

6.4.8

Distribution

Mint 22.1

Graphics hardware and driver used

AMD Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280]

Desklet name and maintainer

clock@schorschii @schorschii

What happened?

The Clock works perfectly, then it freezes after some time has elapsed. The hands stop moving.

Other information

It happens with other clocks as well, they all freeze with time, but this is the clock I am using and I can only name one.

@portanav portanav added the bug label Mar 4, 2025
@schorschii
Copy link
Contributor

I'm sorry I can't do anything here. I never experienced this on my desktop with any desklet. But since it happens with more desklets on your machine, it's probably a general Cinnamon issue, so you may open an issue in the Cinnamon repo instead.

@portanav
Copy link
Author

portanav commented Mar 4, 2025

Thank you. I thought this might be more general also. I will post this to the Cinnamon repo.
Thanks again for the quick reply.

@portanav portanav closed this as completed Mar 4, 2025
@fredcw
Copy link
Contributor

fredcw commented Mar 4, 2025

@portanav Apart from clock desklets, what other 3rd party applets and desklets are you using?

@portanav
Copy link
Author

portanav commented Mar 4, 2025

@portanav Apart from clock desklets, what other 3rd party applets and desklets are you using?

The CLOCK is the only Desklet I use, however I have tried all available CLOCKS and they all freeze after a time; some time is as long as a day, and some just an hour or so. As I said I never had this problem before and it all started after an update; which one I don't know.

Thanks.

@portanav portanav reopened this Mar 4, 2025
@fredcw
Copy link
Contributor

fredcw commented Mar 4, 2025

@portanav I wondering if you've downloaded and are using any other applets, e.g. Weather applet, Cinnamenu ,Spices Update, Radio++, Multi-core System Monitor, etc.?

@portanav
Copy link
Author

portanav commented Mar 4, 2025

@portanav I wondering if you've downloaded and are using any other applets, e.g. Weather applet, Cinnamenu ,Spices Update, Radio++, Multi-core System Monitor, etc.?

Yes, I am using "Spices Update". I stopped using Radio++; the problem continued afterwards.

@fredcw
Copy link
Contributor

fredcw commented Mar 4, 2025

I had a similar problem with JS timers being reset. Are there lots of repeated errors like this:

(cinnamon:2334): Gjs-CRITICAL **: 21:15:24.917: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.

in your ~/.xsession-errors file?

Also try removing Spices Update applet from the panel temporarily to see if that makes a difference.

@portanav
Copy link
Author

portanav commented Mar 4, 2025

I had a similar problem with JS timers being reset. Are there lots of repeated errors like this:

(cinnamon:2334): Gjs-CRITICAL **: 21:15:24.917: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.

in your ~/.xsession-errors file?

Also try removing Spices Update applet from the panel temporarily to see if that makes a difference

I removed Spices Update and it seems to have solved the problem. I will monitor further and report if it continues freezing. I restarted Cinnamon a few times which usually causes a freeze, but is still working.

Thanks.

@portanav
Copy link
Author

portanav commented Mar 4, 2025

@fredcw Where is this located ~/.xsession-errors file? I could not find with a search.

@fredcw
Copy link
Contributor

fredcw commented Mar 4, 2025

Sorry, "~" means your home folder. So ~/.xsession-errors is /home/<your_user_name>/.xsession-errors

You also need to set "show hidden files" in nemo options.

@claudiux
Copy link
Member

claudiux commented Mar 4, 2025

SpicesUpdate v7.8.4 seems to have solved all its problems.

Instead of Radio++, try Radio3.0.

@portanav
Copy link
Author

portanav commented Mar 4, 2025

SpicesUpdate v7.8.4 seems to have solved all its problems.

Instead of Radio++, try Radio3.0.

When I add "Spices Update" 7.8.4 the freezing starts up again, and restarting "Cinnamon" does not go too well; the screen gets black and stays that way a long time, then the CLOCK freezes.
I removed it from the "Applets".
I am using Radio 3.0 now.
Thanks.

@portanav
Copy link
Author

portanav commented Mar 4, 2025

Sorry, "~" means your home folder. So ~/.xsession-errors is /home/<your_user_name>/.xsession-errors

You also need to set "show hidden files" in nemo options.

Got it.
Thanks.

@claudiux claudiux changed the title Desklet Clocks Freeze [clock@schorschii] Desklet Clocks Freeze Mar 7, 2025
claudiux added a commit to claudiux/cinnamon-spices-desklets that referenced this issue Mar 7, 2025
claudiux added a commit to claudiux/cinnamon-spices-desklets that referenced this issue Mar 7, 2025
@claudiux claudiux linked a pull request Mar 7, 2025 that will close this issue
@claudiux
Copy link
Member

claudiux commented Mar 7, 2025

I offer some updates in #1419. Please try them. They use GLib instead of Mainloop (which is obsolete) and avoid Lang.bind() usage.

I've noticed that using Lang.bind() causes problems when calls are repeated excessively often.

Please let me know if any other desklets are affected.

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

Successfully merging a pull request may close this issue.

4 participants