Summary: | current time is not updated within the calendar, red timeline stays on the same position with the same time displayed | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | ratok.mk |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | academicsam, vmpereir, winter |
Priority: | NOR | ||
Version: | 4.3.3 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
ratok.mk
2009-11-12 10:06:22 UTC
Happens to me too. Same version on Gentoo. I also see the following error message when I start kde QObject::connect: Incompatible sender/receiver arguments QTimer::timeout() --> MarcusBains::updateLocation(bool) Same here. Same msg as #1 when launched from command line. I see this in Fedora 11 x86_64 KDE 4.3.3, and in Fedora 10 i386 KDE 4.3.3. The Marcus Bains time line is only updated if I reload one of the resources, for example. I saw some discussion on this in https://issues.kolab.org/issue3930 and was really hoping the fix would make it to 4.3.4. But, it hasn't. Will try to incorporate the following patch until it makes its way on to official tree. http://osdir.com/ml/kde-commits/2009-11/msg01308.html Looking at this patch, I wasn't sure if all that work was needed to resolve this. I tried the following one line change and it worked! This is for 4.3.4. I must say that, as a user, I'm a bit disappointed at the lack of QA. However, I do realize that we use these products at the pleasure of developers. --- korganizer/views/agendaview/koagenda.cpp.orig 2009-12-04 11:34:01.000000000 -0500 +++ korganizer/views/agendaview/koagenda.cpp 2009-12-04 11:43:51.000000000 -0500 @@ -72,7 +72,7 @@ mTimer = new QTimer( this ); mTimer->setSingleShot( true ); - connect( mTimer, SIGNAL(timeout()), this, SLOT(updateLocation(bool)) ); + connect( mTimer, SIGNAL(timeout()), this, SLOT(updateLocation()) ); mTimer->start( 0 ); mOldTodayCol = -1; yep, this was a definite breakdown in our backporting workflow. sorry. I just committed the fix into the 4.3 branch for a possible 4.3.5 release and I will contact the distros to push out at patch for 4.3.4 |