Version: (using KDE KDE 3.2.0) Installed from: Gentoo Packages Compiler: gcc 3.3.2 OS: Linux When looking at my calendar in 1 day, next 3 days, work week, or full week views, the blocks that represent my events do not end at the time that the event ends. Instead, they end at a position that seems to be determined by the amount of text in the event title -- that is, events with short titles look like they are about 1 hour long, and events with long titles look like they are many hours long. For example, this week I have an event called "Clinic" that is supposed to run from 8 AM to 5 PM. If I look at my camendar in any of the above views, the box that represents this event starts at 8AM, but ends at 9AM. I have another event called "Meeting with brain tumor committee -- brainstorming session" which is only supposed to be an hour long. Again, the top of the box is at the right time, but the end of the box extends to encompass the enitre title, so it looks like the meeting is ~3 hours long instead of only one hour.
Created attachment 4411 [details] Picture of event times not lining up with actual times Here's a screenshot from my current calendar. As you can see, there are many events where the box does not line up with the actual start and end times of the event.
I can't reproduce the problem. Could you give us an example calendar file which demonstrates the problem?
Created attachment 4416 [details] example calendar file of calendar that does not display correctly Here's an example calendar file. The next attachment is a screenshot of what this calendar looks like in KOrganizer on my computer.
Created attachment 4417 [details] screenshot of buggycalendar.ics This is what KOrganizer looks like after I load buggycalendar.ics. This calendar was created from scratch. As you can see, the end times for my Clinic events are far too short (they are supposed to end at 5 PM), and the end time for the "brain tumor porgram organizational meeting" event box is too long (Should end at 1 PM).
An additional note: I just installed the stable KDE 3.2.0 and am getting the same error as above.
I have exactly the same problem (on Debian testing). My observation is that the height of the event seems to be the same as its width, so when I resize the whole weekly view, the event height scales accordingly. The interesting thing is that I don't see this problem on a 3.2-rc1 install that I still have around, but I do on my 3.2 install. I did a diff on the korganizer tree in kdepim but couldn't find any significant differences between these versions. Both versions were built with Konstruct on an otherwise unmodified system (gcc 3.3.2). However, I built 3.2-rc1 with "-O2 -march=athlon-xp" and 3.2 with "-Os -march=athlon-xp -fomit-frame-pointer", so I have a feeling that this might be a problem with these compiler options. I recompiled the korganizer subtree with frame pointer, but that didn't seem to fix it. I'll try rebuilding the whole of 3.2 with the previous compiler options next.
Thanks for the suggestion. My CFLAGS were "-march=pentium3 -Os -pipe -fomit-frame-pointer -fforce-mem -fforce-addr -s" I recompiled kdepim with CFLAGS="-march=pentium3 -O2 -pipe" and it seems to behave better now. Cornelius -- what CFLAGS are you using to build korganizer?
Here's my experience with building kdepim-3.2.0 using different sets of CFLAGS: CFLAGS="-march=pentium3 -O2 -pipe" -- works as expected. In Gentoo, this is the same setting that is used by the maintainer of the KDE-cvs binary builds. The following CFLAGS give me the same display error with korganizer: CFLAGS="-march=pentium3 -Os -pipe -fomit-frame-pointer -fforce-mem -fforce-addr -s" CFLAGS="-march=pentium3 -Os -fomit-frame-pointer -fforce-mem -fforce-addr -s" CFLAGS="-march=pentium3 -Os -pipe" CFLAGS="-march=pentium3 -Os -fomit-frame-pointer" CFLAGS="-march=pentium3 -O2 -fomit-frame-pointer" It looks like kdepim really does not like -Os. I'm kind of surprised that "-O2 -fomit-frame-pointer" didn't work, since "-O3 -fomit-frame-pointer" seems to work for the maintainer of the regular KDE ebuild packages. I did build all of the other components of KDE-3.2.0 with fairly aggressive CFLAGS: CFLAGS="-march=pentium3 -Os -pipe -fomit-frame-pointer -fforce-mem -fforce-addr -s" and have not seen any problems so far. Again: Cornelius -- what CFLAGS are you using to build/test korganizer/kdepim?
I don't use any special options, just the ones the standard configure gives me.
*** Bug 77211 has been marked as a duplicate of this bug. ***
Interestingly, all events seem to use square boxes (i.e. the width of the agenda item is also used as its height), and all are of the same height... Reinhold -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAWaXPTqjEwhXvPN0RAgHlAKCGrTseLh0IB84e+iLInftsjqmq9ACeKG7f B5j57WeTsuOkyCHV9wzy3O8= =Y4PI -----END PGP SIGNATURE-----
*** Bug 78193 has been marked as a duplicate of this bug. ***
I can confirm Reinhold Kainhofers observations using Fedoras KDE 3.2.1
This is still an issue in KDE 3.2.2
The following might be connected to this problem: (debian testing/ kde 3.2 / Org 3.2.1) Scheduling a item from 2300 hrs to 0700 hrs the next morning, when creating the event it does show up properly under a day or week view. But when either creating the same event or editing an existing event for repeating days (ie 6 days), The first day shows up correctly but the addtional days do not show up on the view day or week. The repeating option have been using both the "ending after X occurences" and "End by" date option with the same results. An interesting side effect is that the month calender does show the additonal days and with printing or doing a print preview of weekly/monthly view the additional days show up correctly. So the data is in the prg. But print a day calender with time period from 000 to 2359, the print messed up the day as indicated in previous comments. In this case it print the item from 0600 to 2200. This is almost the oposite of what it should be printing. I have not had time to look at the code but it sounds like a calulation is not done right. (at least for the last part)
*** Bug 81738 has been marked as a duplicate of this bug. ***
That's a problem with optimization in Gentoos gcc. We (korganizer) can't do anything about broken compilers... Closing the bug as INVALID, as it's actually a gcc bug. Reinhold PS: Remark #15 to the report is a completely different issue and already known as Bug 42899.
I just run into the same bug, and i'm going to rebuild now without -Os ( kde 3.4.2, gcc 3.4.4 and i can hardly believe that a bug like this is a compiler bug. )