Bug 132407 - Print dialogue is deeper than screen. So print button is invisible.
Summary: Print dialogue is deeper than screen. So print button is invisible.
Status: RESOLVED DUPLICATE of bug 127782
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.4.2.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-25 17:11 UTC by Eion MacDonald
Modified: 2020-04-25 18:15 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eion MacDonald 2020-04-25 17:11:41 UTC
Description:
Print dialog is deeper than screen . Thus bottom is cut off . Print, delete, cancel buttons are invisible even when panel is removed

Steps to Reproduce:
1.Compose document in LibreOffice Writer
2.Select Print
3.Print dialog /diaglog sub-screen is deeper than screen, so no ability to click "print"
4 IF Writer document exported as PDF, the print dialog is smaller and printing can be done.

Actual Results:
This is on laptops running  libreOffice.org on openSUSE Leap 15.1 Version: 6.4.2.2 Build ID: 40(Build:2)
Open Libreoffice, compose page, select print in file menu or by print icon.
Print dialogue is too deep so bottom is out of screen at bottom.
Selecting "Resize" only allow width of dialogue to be changed not the depth (vertical height)of dialogue.
Laptops; Dell E6530, ASUS and Acer laptops with screen resolution 1600x900 and 1368x768

Expected Results:
ability to chose buttons on bottom of dialogue (print)  OK, cancel, help, options 


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Have a smaller print dialogue. This has been a problem for some time. 

Version: 6.4.2.2
Build ID: 40(Build:2)
CPU threads: 4; OS: Linux 4.12; UI render: default; VCL: gtk3; 
Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB
Calc: threaded
supplied by openSUSE
Comment 1 Timur 2020-04-25 18:15:03 UTC
Rule of thumb is search before reporting. And this looks like a known issue.

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