Summary: | Events are always saved as all-day in day and week views | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | odzinic |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | gjditchfield |
Priority: | NOR | ||
Version: | 5.14.1 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
odzinic
2020-07-10 17:37:13 UTC
Which locale do you use? Does the problem go away if you switch to the American English locale (for example, by executing "LANG=en_US korganizer" from the command line)? If it does, this is probably a duplicate of bug 420468. a fix for that bug is arriving shortly in KWidgetsAddons 5.72.0 (In reply to gjditchfield from comment #1) > Which locale do you use? > > Does the problem go away if you switch to the American English locale (for > example, by executing "LANG=en_US korganizer" from the command line)? If it > does, this is probably a duplicate of bug 420468. a fix for that bug is > arriving shortly in KWidgetsAddons 5.72.0 I am using the en_CA locale which seems to match that bug. But when I launch korganizer with "LANG=en_US korganizer", I still get the same issue. Also I noticed that every time I double click a time period, I get the following output: org.kde.pim.incidenceeditor: free slot calculation: invalid range. range( 0 ) / mSlotResolutionSeconds( 900 ) = 0 This appears when creating a task in both day and week views. (In reply to odzinic from comment #2) > I am using the en_CA locale which seems to match that bug. But when I launch > korganizer with "LANG=en_US korganizer", I still get the same issue. Hm. I use en_CA in KDE Neon, and the LANG work-around worked last week, but not today! Today, I have to use "LC_TIME=en_US.UTF-8 korganizer". Does that work better for you? > Also I noticed that every time I double click a time period, I get the > following output: > > org.kde.pim.incidenceeditor: free slot calculation: invalid range. range( 0 > ) / mSlotResolutionSeconds( 900 ) = 0 I see that a lot. It seems to be harmless. > Hm. I use en_CA in KDE Neon, and the LANG work-around worked last week, but > not today! > > Today, I have to use "LC_TIME=en_US.UTF-8 korganizer". Does that work better > for you? That one worked! So looking at the commit the issue is caused by the extra punctuation used in the time format. Interesting. I'll use the workaround until that fix gets upstreamed. Appreciate it! *** This bug has been marked as a duplicate of bug 420468 *** |