Bug 351171 - ver 4.13.3 KOrganizer: unable to save start and end time in Calendar Events, only saves 0000 time.
Summary: ver 4.13.3 KOrganizer: unable to save start and end time in Calendar Events, ...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 4.13.2
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-10 21:28 UTC by Richard
Modified: 2018-01-31 17:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Richard 2015-08-10 21:28:13 UTC 
ver 4.13.3 KOrganizer: unable to save start and end time in Calendar Events, only saves 0000 time.
Start and End Time not programmable in this KOrganizer version. 
Using Linux Mint 17.1

Reproducible: Always

Steps to Reproduce:
1.enter start time
2.enter end time
3. apply apply or ok

Actual Results:  
all times entered return to all zeros

Expected Results:  
times entered will be saved
Comment 1 korden 2015-10-29 03:59:45 UTC 
i have got the same problem.

os ver:
kubuntu desktop 15.10 64bit

korganizer ver:
KDE : 5.15.0
Qt 5.4.2
xcb window
Comment 2 Denis Kurz 2017-06-23 20:20:22 UTC 
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 3 Denis Kurz 2018-01-31 17:14:33 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.