Red Hat Bugzilla – Bug 806616
[rawhide] mutter: there is no close button on window bar
Last modified: 2013-08-01 04:18:34 EDT
Description of problem:
upgrading to rawhide(17), close button on window bar disappeared.
Version-Release number of selected component (if applicable):
git-gui version: 0.16.0
git version: 220.127.116.11
tcl/tk version: 8.5.11
Steps to Reproduce:
1. open git-gui on activities->applications->development->Git GUI;
2. try to close the window by close button on the bar.
no close button to close the window.
button close on windows availability.
upgraded by preupgrade;
fedora 16 and rawhide share same /home.
i would like to append a screen shot, by gnome-screenshot is broken im my system. :/
AFAIK close button is handled by window manager, not by application itself so this is probably bug in your WM. Can you please tell us which WM do you use?
Created attachment 575007 [details]
wm with no button close
I'm using mutter, under fedora 17.
interestingly, it doesn't happen in fedora 16 and just for git-gui.
should I fill a bug against mutter?
after a update over gnome-screenshot, I could take a screenshot.
This definitely looks like a mutter issue for me. When I tried to check if git-gui works fine on my up2date F17 machine, mutter crashed. And when windows manager crashes, windows don't have their minimize/maximize/close buttons, exactly like in your screenshot.
I tried this:
1. start Xorg (Xorg :0 -ac)
2. start mutter on display :0 (export DISPLAY=:0; mutter)
3. start git-gui there
and then mutter crashed with following backtrace:
[atkac@drtic ~]$ mutter
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
*** glibc detected *** mutter: double free or corruption (out): 0xad6f5020 ***
======= Backtrace: =========
I will attach core dump. Reassigning to mutter for further inspection.
Created attachment 575074 [details]
core dump from mutter-3.4.0-1.fc17.i686
I can't reproduce here and since I'm on x86_64 it's not convenient for me to get a backtrace from the core file. Would it be possible for you to do that, Adam?
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora
'version' of '17'.
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 prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.
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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.
Thank you for reporting this bug and we are sorry it could not be fixed.