[gutsy] Event is not updated/refreshed when anything is changed after initial creation

[Luke Plant]

If I create and save an event in KOrganizer, and then go back and change the title of the event and choose 'OK', the visible title of the event does not update. Even if I change the date, or category etc -- nothing appears to change.

This occurs in month, week and day views. To get the new changes to appear, I have to scroll back and forwards a month/week/day, and then it is refreshed.

Versions: I'm using KDE 3.5.8, Gutsy RC packages. From the 'About' box, I'm using KOrganizer 3.5.6 (enterprise 0.20070907.709405). According to apt, the package I'm using is 4:3.5.7enterprise20070926-0ubuntu2

[Luke Plant (spookylukey)]

Another bug, possibly related:

When I 'tick' a task that is shown in the 'to-do' list next to the calendar, it doesn't disappear straight away as it used to (there is a filter that means it ought to). If I scroll the calendar, it then disappears as it should.

[Luke Plant (spookylukey)]

I've discovered that if I create a brand new user account, this bug does not occur. That doesn't help me find a work-around or the cause of the bug however. I could post any config files if anyone is interested.

[Luke Plant (spookylukey)]

The bug also occurs with dragging tasks around in the 'to-do' list. Basically, apart from initial creation, nothing updates/refreshes immediately in the whole window.

[Luke Plant (spookylukey)]

Bug still present in Hardy release candidate 1

Versions:
  KDE 3.5.9
  Korganizer 3.5.9 (4:3.5.9-0ubuntu3)

[Richard Birnie (rbirnie-deactivatedaccount)]

Do you still observe this in Hardy final release. I tried to reproduce this in Intrepid alpha 6 and found that I was able to drag events or to-do items around at will and the views updated immediately. This at least suggests that the bug only exists on KDE3 unless anyone else can confirm on kde4.

Is anyone able to confirm on kde3?
kontact --version
Qt: 4.4.2
KDE: 4.1.1
Kontact: 1.3

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Luke Plant (spookylukey)]

I was still seeing it with Hardy final, and I'm still seeing it with the hardy-update KDE 3.5.10 packages. However, as mentioned above, it doesn't happen with a new account. There must be something in my existing config that is causing it, but I don't have the time to track it down. It is no big nuisance, I don't intend to re-open the bug.