View Single Post
Old 06-16-2021, 03:56 AM   #2
frostschutz
Linux User
frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.
 
frostschutz's Avatar
 
Posts: 2,279
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
Thanks, I installed it on my H2O. The nanoclock does show up, once, during boot. And then, it's just not there anymore. lsmod shows the module is being loaded, and I see nanoclock.lua running in pstree.

Enabling debug gives me these:

Code:
Jun 16 09:51:42 nanoclock[707]: No clock update necessary: damage rectangle 1080x1429+0+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:43 nanoclock[707]: No clock update necessary: damage rectangle 1020x1166+60+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:43 nanoclock[707]: No clock update necessary: damage rectangle 950x120+130+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:43 nanoclock[707]: No clock update necessary: damage rectangle 400x120+130+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:43 nanoclock[707]: No clock update necessary: damage rectangle 71x120+714+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:44 nanoclock[707]: No clock update necessary: damage rectangle 71x120+714+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:45 nanoclock[707]: No clock update necessary: damage rectangle 71x120+884+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:46 nanoclock[707]: No clock update necessary: damage rectangle 71x120+884+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:47 nanoclock[707]: No clock update necessary: damage rectangle 238x342+544+689 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:47 nanoclock[707]: No clock update necessary: damage rectangle 71x120+884+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:48 nanoclock[707]: No clock update necessary: damage rectangle 71x120+884+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:49 nanoclock[707]: No clock update necessary: damage rectangle 71x120+884+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:50 nanoclock[707]: No clock update necessary: damage rectangle 980x1166+50+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:51:50 nanoclock[707]: No clock update necessary: damage rectangle 824x315+196+716 does not intersect with the clock's 24x384+1398+0
Jun 16 09:52:00 nanoclock[707]: No clock update necessary: damage rectangle 245x488+50+181 does not intersect with the clock's 24x384+1398+0
Jun 16 09:52:06 nanoclock[707]: No clock update necessary: damage rectangle 1080x1440+0+0 does not intersect with the clock's 24x384+1398+0
Jun 16 09:52:06 nanoclock[707]: No clock update necessary: damage rectangle 1080x1440+0+0 does not intersect with the clock's 24x384+1398+0
Jun 16 09:52:25 nanoclock[707]: No clock update necessary: damage rectangle 1080x1440+0+0 does not intersect with the clock's 24x384+1398+0
Jun 16 09:53:15 nanoclock[707]: No clock update necessary: damage rectangle 1080x1440+0+0 does not intersect with the clock's 24x384+1398+0
Jun 16 09:53:19 nanoclock[707]: No clock update necessary: damage rectangle 1080x1440+0+0 does not intersect with the clock's 24x384+1398+0
Jun 16 09:53:20 nanoclock[707]: No clock update necessary: damage rectangle 1080x1440+0+0 does not intersect with the clock's 24x384+1398+0
Jun 16 09:53:38 nanoclock[707]: No clock update necessary: damage rectangle 1080x1440+0+0 does not intersect with the clock's 24x384+1398+0
Jun 16 09:53:40 nanoclock[707]: No clock update necessary: damage rectangle 1080x1440+0+0 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:00 nanoclock[707]: No clock update necessary: damage rectangle 1080x1429+0+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:03 nanoclock[707]: No clock update necessary: damage rectangle 380x879+30+41 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:03 nanoclock[707]: No clock update necessary: damage rectangle 400x120+130+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:04 nanoclock[707]: No clock update necessary: damage rectangle 300x70+70+729 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:05 nanoclock[707]: No clock update necessary: damage rectangle 1080x1429+0+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:06 nanoclock[707]: No clock update necessary: damage rectangle 903x83+88+917 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:07 nanoclock[707]: No clock update necessary: damage rectangle 1080x1429+0+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:07 nanoclock[707]: No clock update necessary: damage rectangle 145x74+846+179 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:08 nanoclock[707]: No clock update necessary: damage rectangle 113x70+878+441 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:08 nanoclock[707]: No clock update necessary: damage rectangle 1080x1429+0+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:09 nanoclock[707]: No clock update necessary: damage rectangle 643x34+234+704 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:09 nanoclock[707]: No clock update necessary: damage rectangle 21x20+202+710 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:09 nanoclock[707]: No clock update necessary: damage rectangle 21x20+202+710 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:10 nanoclock[707]: No clock update necessary: damage rectangle 21x20+202+710 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:10 nanoclock[707]: No clock update necessary: damage rectangle 21x20+202+710 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:10 nanoclock[707]: No clock update necessary: damage rectangle 21x20+202+710 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:11 nanoclock[707]: No clock update necessary: damage rectangle 21x20+202+710 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:11 nanoclock[707]: No clock update necessary: damage rectangle 21x20+202+710 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:11 nanoclock[707]: No clock update necessary: damage rectangle 21x20+202+710 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:12 nanoclock[707]: No clock update necessary: damage rectangle 21x20+202+710 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:13 nanoclock[707]: No clock update necessary: damage rectangle 1080x1429+0+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:15 nanoclock[707]: No clock update necessary: damage rectangle 1080x1310+0+11 does not intersect with the clock's 24x384+1398+0
Jun 16 09:54:15 nanoclock[707]: No clock update necessary: damage rectangle 400x120+130+11 does not intersect with the clock's 24x384+1398+0
Does that mean it just thinks it never has to update?

PS: changed the intersection function to always return true ;-) now it works great

Last edited by frostschutz; 06-16-2021 at 04:19 AM.
frostschutz is offline   Reply With Quote