Bug 128634 - korganizer fish file handling
Summary: korganizer fish file handling
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kdepim
Version: 3
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-07-27 14:39 UTC by Elson, Del
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-10-30 14:31:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Elson, Del 2004-07-27 14:39:06 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510

Description of problem:
korganizer has a few bugs in its handling of files using the fish
protocol.

bugs.kde.org # 75087, korganizer needs to be shut down twice when closing.

bugs.kde.org # 86095, fish protocol causes the default calendar to be
loaded twice after login.


Version-Release number of selected component (if applicable):
kdepim-3.2.2-2

How reproducible:
Always

Steps to Reproduce:
1.Set up korganizer with a remote (fish protocol) file as the default
calendar.
2.Log in.
3.Start korganizer.
    

Actual Results:  File loaded twice.

Expected Results:  File loaded once.

Additional info:

Loss of calendar data is caused where the file is accessed from
multiple locations, as the calendar file is sometimes not read
properly from the remote server, and a recent (but not the most
recent) copy is used instead.

Comment 1 Matthew Miller 2005-04-26 15:18:34 UTC
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.

Comment 2 Elson, Del 2005-04-26 23:48:01 UTC
This bug is still present in FC3 and FC4 test.

Comment 3 Matthew Miller 2006-07-10 20:31:51 UTC
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!


Comment 4 John Thacker 2006-10-30 14:31:40 UTC
Closing per lack of response to previous request for information.
Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only.  Please install a still supported version and retest.  If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version.  Otherwise, if this a security issue, please change the
product to Fedora Legacy.  Thanks, and we are sorry that we did not
get to this bug earlier.


Note You need to log in before you can comment on or make changes to this bug.