Bug 77211

Summary:	Improper size of events in KOrganizer
Product:	[Applications] korganizer	Reporter:	Mikolaj Machowski <mikmach>
Component:	general	Assignee:	Cornelius Schumacher <schumacher>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Improper visualisation of events in KOrganizer

Description Mikolaj Machowski 2004-03-10 19:52:33 UTC

Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc3.3.1 -Os 
OS:          Linux

Size of event doesn't reflect times of event.
Scheduled from 13.15 to 14.45 shows as 13.15 to 15.15.

In other case it is scheduled 16.45-18.15 shows as 16.45-19.15

Comment 1 Mikolaj Machowski 2004-03-13 01:08:13 UTC

Created attachment 5197 [details]
Improper visualisation of events in KOrganizer

Really no one has this problem? This is an part of screenshot from CVS, friday
evening.

Comment 2 Cornelius Schumacher 2004-03-13 07:02:30 UTC

I vaguely remember another bug report describing this problem. Maybe you would like to check Bugzilla for it. Does changing the optimisation options for the compiler help?

Comment 3 Mikolaj Machowski 2004-03-13 16:14:56 UTC

Yes. Turning off all local flags solves the problem. And yes, There was 
similar problem some time ago but vanished at some point.

Offending settings:
CFLAGS="-march=athlon -mcpu=athlon -Os -fomit-frame-pointer -pipe -DNDEBUG 
-DG_DISABLE_ASSERT"
CXXFLAGS="-march=athlon -mcpu=athlon -Os -pipe -DNDEBUG -DG_DISABLE_ASSERT 
-fpermissive"
LDFLAGS="-z combreloc"

Comment 4 Cornelius Schumacher 2004-03-13 16:53:52 UTC

What exact platform are you using?

Comment 5 Mikolaj Machowski 2004-03-13 22:41:07 UTC

Platform:
	Mdk9.2
	gcc3.3.1 (-2mdk)
	Linux localhost 2.4.22-10mdk

Comment 6 Reinhold Kainhofer 2004-03-18 14:34:05 UTC

This is exactly the same behaviour as in bug 73718: The items seem to use the width also as their height... Hmm, seems to be a compiler optimization bug.

Reinhold

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