Bug 162171 – kontact "unable to save Event"

This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours

Bug 162171 - kontact "unable to save Event"

Summary:	kontact "unable to save Event"

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	kdepim (Show other bugs)
Sub Component:
Version:	4
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Ngo Than
QA Contact:	Ben Levenson
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2005-06-30 11:55 EDT by Hollis Blanchard
Modified:	2007-11-30 17:11 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-02-01 19:42:28 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
KDE Software Compilation	105122	None	None	None	Never

Groups: None (edit)

Description Hollis Blanchard 2005-06-30 11:55:12 EDT

Description of problem:
korganizer/kontact presents an error dialog ("Unable to save Event") when
attempting to create a new event.

Version-Release number of selected component (if applicable):
Kontact 1.1.1
Korganizer 3.4.1

How reproducible:
Always

Steps to Reproduce:
1. run Kontact
2. select calendar icon
3. select Actions -> New Event
4. enter a title (e.g. "asdf")
5. click "OK"
  
Actual results:
An error appears with the text 'Unable to save Event "asdf"'.

Expected results:
The new event should be saved and the dialog closed.

Additional info:
Google turns up this, which is slightly more helpful than the KDE bugzilla
record: http://www.kolab.org/pipermail/kolab-users/2005-May/002666.html

Comment 1 Christian Iseli 2007-01-22 05:05:52 EST

This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?

Thanks.

Comment 2 Hollis Blanchard 2007-02-01 19:42:28 EST

Just an observation: after 1.5 years of inactivity, that comment is pretty
insulting.

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