Bug 185434 - Drawing glitch with a certain set of appointments
Summary: Drawing glitch with a certain set of appointments
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: agendaview (weekview) (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-24 13:40 UTC by Tom Albers
Modified: 2017-01-07 22:28 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
ical file with the appointments (5.11 KB, text/plain)
2009-02-24 13:41 UTC, Tom Albers 		Details
ical test file (5.11 KB, text/plain)
2009-02-24 13:50 UTC, Tom Albers 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Albers 2009-02-24 13:40:24 UTC 
Version:           4.3.0 pre (using 4.2.63 (KDE 4.2.63 (KDE 4.3 >= 20090212)) "release 1.2", KDE:KDE4:UNSTABLE:Desktop / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.27.7-9-default

Hi, 

Attached is a certain set of appointments for 24th of feb. When you display those in a day view, I see item3 and item1 keep trying to redraw themselfes, causing flicker. This stops when item1 or item3 is selected and starts when item2 or item4 are selected.

I hope you can reproduce it.

Qt: 4.5.0-rc1
KDE: 4.2.63 (KDE 4.2.63 (KDE 4.3 >= 20090212)) "release 1.2"
KOrganizer: 4.3.0 pre
Comment 1 Tom Albers 2009-02-24 13:41:35 UTC 
Created attachment 31602 [details]
ical file with the appointments
Comment 2 Tom Albers 2009-02-24 13:50:29 UTC 
Created attachment 31605 [details]
ical test file
Comment 3 Denis Kurz 2016-09-24 18:43:49 UTC 
This bug has only been reported for versions before 4.14, 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 korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:28:38 UTC 
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.