Red Hat Bugzilla – Bug 1314663
wrong default background in emacs
Last modified: 2017-08-08 09:06:02 EDT
Created attachment 1133105 [details]
Description of problem:
Emacs background turned blue after the update of gtk and several graphics related components. Emacs itself didn't change and the background was fine before the update. There seems to be no easy way how to downgrade gtk to verify this.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Update to the latest F24 (Fri Mar 4 09:18:39 CET 2016)
2. run emacs
Blue background of the main widget.
Normal background of the main widget.
I'm running XFCE, should that matter.
I am writing to comment that I see the same behaviour that Jan reports.
Running Gnome and wayland on rawhide (F24?)
Created attachment 1133385 [details]
emacs startup screen, reduced to small screen area
There's been an update and I am now running these packages:
The behaviour persists and even more strangely, the main emacs window resizes at startup to a small area of the screen. I attach a screenshot.
While using the application I also noticed the Gtk warning I paste below.
(emacs:27567): Gtk-WARNING **: State 36 for Emacs 0x16ee280 doesn't match state 128 set via gtk_style_context_set_state ()
The issue is still present with the gtk3 update I got today.
will be fixed in gtk 3.20.2
I can confirm that this is fixed in gtk3-3.20.2-1.fc24.x86_64.
Emacs started working for me, too with these:
I think this could be closed now.
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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'
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 24 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.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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
Thank you for reporting this bug and we are sorry it could not be fixed.