PyBonnetainNesterenko
PyBonnetainNesterenko
Hello, Not « only » an Ubuntu bug but a >5.10 kernel change. Got this same error (module.lds related) on a RaspberryPi running Gentoo. Solved it by somehow following hints...
I have exactly this same problem, probably appeared on 1.0.34 (latest). Here is an event created through Etar, start hour is 19:30: On the agenda, start hour displayed is 21:30...
I was wrong in my previous comment : > Events created through another app and imported into Android calendar (here, thanks to Caldav) are okay. As a matter of fact,...
Bug still there with release 1.0.35   
Small (but I think relevant, especially wrt #1387) bit of data : all « wrongly timed » events start as full-day events (add an event when in monthly view, mainly)....
> > > @eshattow Please try the apk mentioned here in #1387 and report back. > > Trying that. Will keep you informed. As far as my tests have gone...
As far as my limited tests show, [this suggestion](https://github.com/OllisGit/OctoPrint-PrintJobHistory/pull/226) solves the problem. Thanks !