-
Notifications
You must be signed in to change notification settings - Fork 1
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
Events in Incorrect Timezone #5
Comments
I'm glad you're getting some use out of this! I think I should have fixed the time zone issue in 10d1b67. If you could check that would be great, I now realise testing UTC vs Europe/London was not the most useful... Your crashes might be related to the issue I had with libusb hanging. If you could run a debug build and generate a stack trace that should reveal where the crash happened let us look a little deeper. To do so cmake -DCMAKE_BUILD_TYPE=Debug .. # build the debug build
gdb ./sync-calendar2 # setup to run in the debugger and then inside gdb
From there you can copy paste in the stack trace from the terminal into a comment. If it is dying in libusb, try changing all instances of |
Thank you for such a fast response and code update. I just built from latest commit and did a sync with the same config I have above and the event shows up at 9AM PDT as expected, so it looks like that fixed it. I'm doing this as part of the RetroChallenge 2024 and using my Zire on a day-to-day basis. Having calendar functionality is wonderful and lets me make even more use out of the device. I'm taking notes on my journey on Gopher and writing up my new post on palm-calendar-sync2 as we speak. gopher://sdf.org:70/1/users/ecliptik/_rc2024/ I will work on re-building with debug and getting some information on the seg fault later today. Thank you again. |
No worries! Sounds like a fun project getting this stuff working and using it day to day. I original wrote palm-calendary-sync2 to try and use my m515 more day to day, but it ended up being difficult to remember to take it out of my backpack to sync at the start of the day and even more difficult to remember to charge over long breaks. Just so you know, if you're using this as your only calendar that I've seen some issues with repeating events that I haven't had the time to debug. I've detailed what I think might be happening in #7 and #8 - if you find some combination of events that triggers these (or other any issues) I'll try to have a look. |
Here's the output for a debug build with no changes,
Here's the output when changing all instances of pi_close_fixed(sd, port) to pi_close(sd) in sync-calendar2.cpp, which does not give a segfault and exit successfully with events sync'd to the Palm.
|
Good to know, I did notice that a recurring all-day event I had every other Tuesday showed up, but was on every day for the week it re-occurred. I'll try and get some more info by re-creating similar events on a test calendar and update those issues accordingly. Thank you. |
Thanks, your stack trace confirms the segfault is happening in my code:
Could you please try replacing lines 68 to 82 of if (ps && port.find("usb") == 0) {
// don't try and close usb if we're not USB
// (we need to pass port for this because there's no way to get the port back from the socket)
pi_usb_data_t *data = (pi_usb_data_t *)ps->device->data;
usb_dev_handle *dev = (usb_dev_handle*)data->ref;
libusb_device_handle *dev_handle = dev->handle;
if (dev_handle) {
// if it still exists then something has gone wrong and we should clean up
libusb_context *ctx = HANDLE_CTX(dev_handle);
if (ctx) {
libusb_unlock_events(ctx);
}
else {
failed = true;
}
}
} and check if it still segfaults when using |
Sorry for the delay, I updated Here's the resulting gdb with RELEASE=Debug, I cut out all the calendar event processing since those were successful and made the log very long.
|
Thank you for writing this software, and to start I can't tell you how pleased I was when I first saw my calendar sync'd to my Palm Zire.
I have run into an issue with the timezone being off by +8hrs for all events though. Here's my configuration,
FROMYEAR=2024
andTIMEZONE="America/Los_Angeles"
options set indatebook.cfg
Using a .ics file with a single event, Thursday 10/10/2024 9AM-10AM PDT. It syncs successfully, but shows up in Datebook on the Zire at 10/10/2024 5PM-6PM.
I've tried a variety of things- setting the Zire timezone to UTC, seeing
TIMEZONE="UTC"
and a variety of combinations, but it's always ahead by 8 hours. I also get a segfault after running, but it says that the update was complete and the Palm gives a happy chime and notes the sync as successful. Previously I had used the apptainer version and while it didn't segfault it still had the timezone incorrect.Here's is the event, configuration, logs and some screenshots.
palmdatebook.ics
datebook.cfg
calendar-sync2 log
Palm Info
Datebook Event Details
The text was updated successfully, but these errors were encountered: