RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1539816 - evince throws Gtk-WARNING **: Allocating size to EvSidebar 0x0 without calling gtk_widget_get_preferred_width/height()
Summary: evince throws Gtk-WARNING **: Allocating size to EvSidebar 0x0 without callin...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gtk3
Version: 7.4
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Benjamin Otte
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-29 16:43 UTC by Andreas Bleischwitz
Modified: 2019-10-31 18:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-25 14:18:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Andreas Bleischwitz 2018-01-29 16:43:05 UTC
Description of problem:
Evince started from console (not ssh) will throw the following warnings to the user:

$ evince /usr/share/doc/libtasn1-4.10/libtasn1.pdf

(evince:2013): Gtk-WARNING **: Allocating size to EvSidebar 0x27c14e0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

Version-Release number of selected component (if applicable):
$ rpm -q evince
evince-3.22.1-5.2.el7_4.x86_64

How reproducible:


Steps to Reproduce:
1. start evince with any pdf 
2. see the Gtk-WARNING message
3.

Actual results:
Gtk-WARNING **: Allocating size to EvSidebar shown

Expected results:
No warning shown

Additional info:
Still valid on FC-27's version of evince:

$ evince /usr/share/doc/libsrtp/libsrtp.pdf

(evince:13531): Gtk-WARNING **: Allocating size to EvSidebar 0x5611d0afa710 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

$ rpm -q evince
evince-3.26.0-1.fc27.x86_64

Comment 6 Peter Lemenkov 2018-04-04 15:41:27 UTC
(In reply to Andreas Bleischwitz from comment #0)
> Description of problem:
> Evince started from console (not ssh) will throw the following warnings to
> the user:
> 
> $ evince /usr/share/doc/libtasn1-4.10/libtasn1.pdf
> 
> (evince:2013): Gtk-WARNING **: Allocating size to EvSidebar 0x27c14e0
> without calling gtk_widget_get_preferred_width/height(). How does the code
> know the size to allocate?

This is an issue in GTK. See bug 1488249 for further details.

Comment 7 Andreas Bleischwitz 2018-06-14 08:53:47 UTC
Hi Benjamin,

couldn't we include that patch in the gtk3 version so that the messages would only be seen if G_ENABLE_CONSISTENCY_CHECKS is enabled?


Note You need to log in before you can comment on or make changes to this bug.