Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1389448 - Lots of errors "... is drawn without a current allocation. This should not happen."
Summary: Lots of errors "... is drawn without a current allocation. This should not ha...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: emacs
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Synacek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-27 15:22 UTC by Richard W.M. Jones
Modified: 2017-12-12 10:47 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:47:01 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1384185 0 unspecified CLOSED Dynamic menus are not updated if clicked on with the mouse 2022-05-16 11:32:56 UTC

Internal Links: 1384185

Description Richard W.M. Jones 2016-10-27 15:22:03 UTC 
Description of problem:

When you start up emacs, you see in the terminal:

(emacs:21674): Gtk-WARNING **: GtkWindow 0x257a290 is drawn without a current allocation. This should not happen.

(emacs:21674): Gtk-WARNING **: EmacsFixed 0x257e130 is drawn without a current allocation. This should not happen.

(emacs:21674): Gtk-WARNING **: EmacsFixed 0x257e130 is drawn without a current allocation. This should not happen.

(emacs:21674): Gtk-WARNING **: GtkScrollbar 0xe2e6a0 is drawn without a current allocation. This should not happen.

(emacs:21674): Gtk-WARNING **: EmacsFixed 0x257e130 is drawn without a current allocation. This should not happen.

(emacs:21674): Gtk-WARNING **: GtkScrollbar 0xe2e6a0 is drawn without a current allocation. This should not happen.

(emacs:21674): Gtk-WARNING **: GtkWindow 0x257a290 is drawn without a current allocation. This should not happen.

(emacs:21674): Gtk-WARNING **: GtkBox 0x257c150 is drawn without a current allocation. This should not happen.

(emacs:21674): Gtk-WARNING **: GtkMenuBar 0x246c1f0 is drawn without a current allocation. This should not happen.

(emacs:21674): Gtk-WARNING **: EmacsFixed 0x257e130 is drawn without a current allocation. This should not happen.

(emacs:21674): Gtk-WARNING **: GtkEventBox 0x29452a0 is drawn without a current allocation. This should not happen.

(emacs:21674): Gtk-WARNING **: GtkScrollbar 0xe2e6a0 is drawn without a current allocation. This should not happen.

(emacs:21674): Gtk-WARNING **: EmacsFixed 0x257e130 is drawn without a current allocation. This should not happen.

(emacs:21674): Gtk-WARNING **: GtkEventBox 0x29452a0 is drawn without a current allocation. This should not happen.

(emacs:21674): Gtk-WARNING **: GtkScrollbar 0xe2e6a0 is drawn without a current allocation. This should not happen.

These errors happen continuously (on mouse movement).

Version-Release number of selected component (if applicable):

emacs-25.1-1.fc25.x86_64
gtk3-3.22.0-2.fc25.x86_64

How reproducible:

100%

Steps to Reproduce:
1. Just run emacs.

Additional info:

These Debian bugs seem relevant:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837072
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832077
Comment 1 Richard W.M. Jones 2016-10-27 15:23:36 UTC 
I'm added Matthias Clasen since he added the warning:

https://mail.gnome.org/archives/commits-list/2016-May/msg06553.html

Is this a bug in emacs?  Gtk3?  ...
Comment 2 Jan Synacek 2016-10-31 08:40:38 UTC 
Maybe. There have been some rendering-related bugs lately, like https://bugzilla.redhat.com/show_bug.cgi?id=1384185. Something must have changed in gtk, though.
Comment 3 Fedora End Of Life 2017-11-16 19:43:35 UTC 
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 4 Fedora End Of Life 2017-12-12 10:47:01 UTC 
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Note You need to log in before you can comment on or make changes to this bug.