Bug 272436 - KOrganizer does not print all participants
Summary: KOrganizer does not print all participants
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: printing (show other bugs)
Version: 4.4.10
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks: 442364
  Show dependency treegraph
 
Reported: 2011-05-04 12:33 UTC by Christopher Yeleighton
Modified: 2021-09-13 04:42 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Yeleighton 2011-05-04 12:33:46 UTC
Version:           4.4.10 (using KDE 4.6.0) 
OS:                Linux

KOrganizer prints only that many participants that fit into the frame dedicated to them, which is of fixed size.  The last participant printed is printed over the frame border.

Reproducible: Always

Steps to Reproduce:
  1. Tell KOrganizer to create a task 
"KOrganizer does not print all participants".

  2. Tell the task to add several participants, like:
Preston Brown Pierwszy autor 
Cornelius Schumacher Były opiekun 
Reinhold Kainhofer Były opiekun 
Allen Winter Opiekun 
Rafael Fernández López 
Daniel Molkentin 

  3. Tell KOrganizer to print the task.

Actual Results:  
  3. Rafael Fernández López is printed over the frame border; Daniel Molkentin is not printed at all.

Expected Results:  
  3a. The frame should adjust to make enough room for all participants.  
  3b. Alternatively, print all participants on a separate page.

OS: Linux (x86_64) release 2.6.37.6-0.5-desktop
Compiler: gcc
Comment 1 Denis Kurz 2016-09-24 18:47:14 UTC
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.
Comment 2 Denis Kurz 2017-01-07 22:06:36 UTC
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.