Description of problem:
After launching a pdf file in Document Viewer (evince), window controls that are rendered as part of X and the application menus cannot be operated.
The mouse pointer changes to indicate it is ready to resize the window and all window controls, application controls, and trying to grab the top title bar to move the window is disabled.
The buttons doesn't respond to mouse clicks, we see the point alignment to the application window is wrong.
The menu, resizing, right side vertical scroll bar and top right corner application buttons for closing, full screen or minimise doesn't work.
If we move the mouse slowly towards left, I get control of the button which is towards the right.
We have to double click the title bar to maximize and then minimize to get things working.
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 7.5
Steps to Reproduce:
1. Open a pdf file in evince.
2. Get a minimized window view of it. Clicking on the maximize window button twice.
3. Now move that window to the top left of the screen.
4. Resize the window from right to left (pull to the possible limit).
5. Close it and reopen the pdf with evince.
Now see that the point alignment to the application window is incorrect.
The mouse pointer alignment to the application window is incorrect.
Should be able to control the window without any problems.
We could see below error when launching evince.
(evince:8693): Gtk-WARNING **: Allocating size to EvSidebar 0x210a4e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
I suspected it to be https://bugzilla.gnome.org/show_bug.cgi?id=767136
I tried the fix, but it only suppresses the 'Gtk-WARNING' message, but doesn't fix the problem.
this bug has been fixed in evince 3.28 to which we are rebasing (see #1567186). To be more specific, it was this commit: https://gitlab.gnome.org/GNOME/evince/commit/937e77fc7b078cce3cd2839a42212c124baff9f4.
Verified on RHEL-7.6-20180812.n.0 & evince-3.28.2-5
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.