Version: (using Devel) Compiler: gcc 4.3.2 OS: Linux Installed from: Compiled sources - Launch KOrg - Create an event for today starting at 7:00 and ending at 9:00 - Create another event for today starting at 10:00 and ending at 12:00 - Go to File menu/Print... - In the Date & Time Range section enter 10:00 as a start time and 12:00 as an end time - Uncheck the 'Extend time range to include all events' check box - Leave the other options as set by default - Click on Print... - Select Print to File (PDF) - Browse and select a location on your hard drive to save the file When you open the file you can see that both events are displayed whereas only the second one should be displayed. Trunk, Svn Rev 1110068
Hi, Works fine here too :) Could you retest it please ? Thanks Regards
I retested this today and I realized that my description is not accurate enough since I could not reproduce the bug either. Sorry about that... So here are new steps to reproduce this bug: - Launch KOrg - Create an event for today starting at 7:00 and ending at 9:00 - Create another event for today starting at 10:00 and ending at 12:00 - Go to File menu/Print... - In the Date & Time Range section enter 10:00 as a start time and 17:00 as an end time - Uncheck the 'Extend time range to include all events' check box - Select 'Print date range as Filofax format, all on one page' radio button - Leave the other options as set by default - Click on Print... - Select Print to File (PDF) - Browse and select a location on your hard drive to save the file When you open the file you can see that both events are displayed whereas only the second one should be displayed. Trunk, Svn Rev 1110236
Ok I can reproduce bug
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.