Bug 205688 - Copy & paste event works improperly
Summary: Copy & paste event works improperly
Status: RESOLVED DUPLICATE of bug 202171
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-30 14:20 UTC by Ondrej Machulda
Modified: 2010-02-26 23:25 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ondrej Machulda 2009-08-30 14:20:44 UTC
Version:           4.3.0 (using 4.3.00 (KDE 4.3.0), Gentoo)
Compiler:          i686-pc-linux-gnu-gcc
OS:                Linux (i686) release 2.6.30-gentoo-r4

Steps to reproduce:
1) create new event (eg. one-day event), all settings can be left default
2) save it
3) event appears in calendar
4) right click on it, select "copy"
5) select (by clicking there) another day in calendar (eg. next week)
6) right click in this day, select paste
7) event appears elsewhere - eg. on the day after original event, sometimes even elsewhere, and only using search can find the new weird position of event again...

Expected behavior:
- Event is copied into selected day
Comment 1 FiNeX 2009-08-30 15:36:13 UTC
Cannot reproduce on current trunk (r1017369).
Comment 2 Ondrej Machulda 2009-09-04 21:08:25 UTC
Still present in 4.3.1 with the same weird behavior.

I've made a video showing the problem: 
(MPEG 4, 8MB, made using xvidcad)
Comment 3 Ondrej Machulda 2009-09-04 21:12:12 UTC
Well, and I'd like to poste link to the video here, what I consider better then uploading an 8MB attachement, but I can't...

Soo try #2: data.lvicata.cz/tmp/kde-bug-205688.mpeg
Comment 4 dekonnection 2009-10-07 17:12:55 UTC
Same problem here, with 4.3.2 : after copy-paste, the new events appears into a random day, not into the selected day.
Comment 5 Sabine Faure 2010-02-26 22:58:21 UTC
I wonder if this bug is a duplicate of bug #202171.
Comment 6 Ondrej Machulda 2010-02-26 23:15:35 UTC
Yes, it definitely is :-). Thanks.

*** This bug has been marked as a duplicate of bug 202171 ***
Comment 7 Sabine Faure 2010-02-26 23:25:54 UTC
You're welcomed! ;o)
Thx for marking it as a duplicate.