Bug 81738 - appointments occupy more hours than necessary on the timetable
Summary: appointments occupy more hours than necessary on the timetable
Status: RESOLVED DUPLICATE of bug 73718
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Cornelius Schumacher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-17 14:04 UTC by Stefano
Modified: 2004-05-17 22:21 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Stefano 2004-05-17 14:04:35 UTC 
Version:            (using KDE KDE 3.2.2)
Installed from:    Gentoo Packages
Compiler:          gcc-3.4 
OS:                Linux

As shown in this picture  http://it.geocities.com/magico_pacio/korganizer.png
when I set an appointment it takes a lot of hours more than I speicified, making impossible to me to set another appointment later clicking on the right line.

Obviously it should take up only lines until 16:00.


It is korganizer 3.2.1 using kde3.2.2 (but i experienced it since kde 3.2.1).

Im'using latest nvidia driver with xfree 4.4 rc3

some other info below:
Portage 2.0.50-r6 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.3_pre20040420-r0, 2.6.5-rc3-love1)
=================================================================
System uname: 2.6.5-rc3-love1 i686 AMD Athlon(tm) XP 2000+
Gentoo Base System version 1.4.12
Autoconf: sys-devel/autoconf-2.59-r3
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-march=athlon-xp -Os -fomit-frame-pointer -falign-functions=64 -falign-jumps=16 -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
Comment 1 Reinhold Kainhofer 2004-05-17 22:21:38 UTC 
This problem seems to occur only on Gentoo, and there mainly with the -Os compiler flag. I suspect it's actually compiler problem rather than a bug in KOrganizer. For more details, see the comments for bug 73718.

Cheers,
Reinhold

*** This bug has been marked as a duplicate of 73718 ***