Bug 193220 - Zero task times when opening *.ics file other than default ktimetracker.ics
Summary: Zero task times when opening *.ics file other than default ktimetracker.ics
Status: RESOLVED DUPLICATE of bug 182317
Alias: None
Product: ktimetracker
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Thorsten Staerk
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-19 12:14 UTC by Dmitry
Modified: 2011-09-22 08:03 UTC (History)
0 users

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 Dmitry 2009-05-19 12:14:55 UTC 
Version:           4.3.0 (using KDE 4.2.85)
OS:                Linux
Installed from:    SuSE RPMs

After starting KTimeTracker the default data file (ktimetracker.ics) is opened and looks OK - tasks and times are displayed.

Than I try to open another file (I use different data files for different projects) and I got following situation : tasks and sub-tasks are shown, but with zero times on each.
Data files was created using previous version of KTimeTracker (shipped with KDE 4.2.2).

Short error description: reading of time values from data files is not correct (zero instead of saved time tracking history)
Comment 1 Thorsten Staerk 2009-05-23 09:05:37 UTC 
This should not be and I cannot reproduce. Can you attach the ics file where you get 0 as time value?
Comment 2 Dmitry 2009-05-23 12:49:44 UTC 
Sorry, files contain private information and I can not publish them.
When opening file there is following lines appearing in ~/.xsession-errors:

ktimetracker(5914) Task::asTodo: mSessionStartTiMe= ""


Hope that can help.
Comment 3 Thorsten Staerk 2009-06-01 09:07:22 UTC 
I suspect a connection to bug 179575
Comment 4 Thorsten Staerk 2009-06-01 12:49:43 UTC 
I suspect a connection to bug 194827 - do you get a crash when you call "File->Edit History"?
Comment 5 Dmitry 2009-06-01 13:30:26 UTC 
No, no crash occurs on "File->Edit History", but it seems that this bug is very close to one described in bug 179575
Comment 6 Thorsten Staerk 2011-09-22 08:03:58 UTC 

*** This bug has been marked as a duplicate of bug 182317 ***