Your message dated Thu, 18 Jan 2018 16:31:35 +0100
with message-id
and subject line Re: korganizer's poor syncronization behaviour causes data lost
has caused the Debian Bug report #438979,
regarding korganizer's poor syncronization behaviour causes data lost
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
438979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: korganizer
Version: 4:3.5.7-2
Severity: grave
--- Please enter the report below this line. ---
Using a remote calendar on different machines is extremely dangerous. It
looks like korganizer just overwrites the local calendar when
(re)loading the remote calendar and just overwrites the remote calendar
when saving the local one.
This leads to dangerous situations as happened for me a few minutes ago.
Korganizer failed for some reason to load the changes I've made on a
remote calendar yesterday on startup of korganizer. I made some changes,
not knowing that I was working with an outdated copy of my calendar.
When korganizer finally saved the local changes to the remote calender,
all my changes I've made yesterday on the other machine where gone.
Korganizer should really make sure not to overwrite newer remote or
local calendars when syncronizing. I think it could use the
LAST-MODIFIED fields in the .ics file to check if the local/remote
event/todo-item is newer.
I've decided to use "grave" because it leads to data loss. "Important"
could be appropriate too since "it's not useless for everyone", but I
think data loss weights more in this case.
Cheers,
Bastian
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.22-1-686
Debian Release: lenny/sid
500 unstable www.debian-multimedia.org
500 unstable ftp.de.debian.org
1 experimental ftp.de.debian.org
--- Package information. ---
Depends (Version) | Installed
============================================-+-======================
kdelibs4c2a (>= 4:3.5.7-1) | 4:3.5.7.dfsg.1-4
libart-2.0-2 (>= 2.3.18) | 2.3.19-3
libaudio2 | 1.9-2+b1
libc6 (>= 2.6-1) | 2.6.1-1
libfontconfig1 (>= 2.4.0) | 2.4.2-1.2
libfreetype6 (>= 2.3.5) | 2.3.5-1+b1
libgcc1 (>= 1:4.2-20070516) | 1:4.2.1-4
libice6 (>= 1:1.0.0) | 2:1.0.3-3
libidn11 (>= 0.5.18) | 1.0-0
libjpeg62 | 6b-13
libkcal2b (>= 4:3.5.7) | 4:3.5.7-2
libkdepim1a (>= 4:3.5.7) | 4:3.5.7-2
libkpimexchange1 (>= 4:3.5.7) | 4:3.5.7-2
libkpimidentities1 (>= 4:3.5.7) | 4:3.5.7-2
libpng12-0 (>= 1.2.13-4) | 1.2.15~beta5-2
libqt3-mt (>= 3:3.3.7) | 3:3.3.7-6
libsm6 | 2:1.0.3-1+b1
libstdc++6 (>= 4.2-20070516) | 4.2.1-4
libx11-6 | 2:1.0.3-7
libxcursor1 (>> 1.1.2) | 1:1.1.8-2
libxext6 | 1:1.0.3-2
libxft2 (>> 2.1.1) | 2.1.12-2
libxi6 | 2:1.1.2-1
libxinerama1 | 1:1.0.2-1
libxrandr2 (>= 2:1.2.0) | 2:1.2.1-1
libxrender1 | 1:0.9.2-1
libxt6 | 1:1.0.5-3
zlib1g (>= 1:1.2.3.3.dfsg-1) | 1:1.2.3.3.dfsg-5
perl | 5.8.8-7
--
Bastian Venthur http://venthur.de
Debian Developer venthur at debian org
--- End Message ---
--- Begin Message ---
Dear bug submitter,
Thank you for reporthing this issue. The bug has been determined not to be
Debian specific, and therefore was reported in the KDE bugtracker; see
https://bugs.kde.org/show_bug.cgi?id=151827.
We are sorry it has not been resolved. However, the version in which the
issue was reported is now obsolete and the upstream tracker has closed the
issue. Thus we are also closing the issue in Debian bug tracker.
If you think the bug is still relevant to a KDE Pim version in Debian stable
(aka Stretch) or newer -- i.e. part of KDE Applications 15.08.0 or newer --
then please open a new bugreport upstream and add your new information in the
upstream bugreport.
Again, thank you for reporting the issue. If there are any questions feel free
to ask.
KDE upstream bug tracker closed their bug with following statement:
"This bug has only been reported for versions before 15.08.0, which have been
unsupported for at least two years now. Can anyone tell if this bug still
present?
If noone confirms this bug for a Framework-based version of kontact
(version 5.0 or later, as part of KDE Applications 15.08 or later),
it gets closed in about three months.
Just as announced in my last comment, I close this bug.
If you encounter it again in a recent version (at least 5.0 aka 15.08),
please open a new one unless it already exists. Thank you for all your input."
--- End Message ---
