After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 587732 - These windows do not support "save current setup"
These windows do not support "save current setup"
Status: RESOLVED OBSOLETE
Product: metacity
Classification: Other
Component: general
2.26.x
Other All
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2009-07-04 10:38 UTC by Eduard Sanchez Biete
Modified: 2020-11-06 20:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Attachments
Screenshot showing the problem (13.01 KB, image/png)
2009-07-04 15:12 UTC, Oded Arbel
Details

Description Eduard Sanchez Biete 2009-07-04 10:38:43 UTC
Please describe the problem:
After login an error related to metacity and gdm-simple-greeter appears:

"These windows do not support "save current setup" and will have to be restarted manually next time you log in", referring to Class: Login Window, Window: Gdm-simple-greeter.

Steps to reproduce:
1. Occurring after each reboot



Actual results:
You can Ok or Cancel, nothing happens after that

Expected results:


Does this happen every time?
Yes

Other information:
It started happening when upgraded from 2.20.10-0ubuntu5 to 2.26.1-0ubuntu2
Comment 1 Dean Loros 2009-07-04 15:05:40 UTC
Confirmed
Comment 2 Oded Arbel 2009-07-04 15:12:35 UTC
Created attachment 137836 [details]
Screenshot showing the problem

I have also seen this issue. Here is how it looks
Comment 3 Sense Hofstede 2009-07-06 15:32:57 UTC
I can confirm this as well. 
It is said that removing or moving /usr/share/gdm/autostart/LoginWindow/metacity.desktop makes the error message disappear, but I'm not sure whether that's the right solution.

The Launchpad report is located at https://bugs.launchpad.net/gdm/+bug/395324
Comment 4 Dragan Tomas 2009-07-08 14:40:44 UTC
Same here, the error message is there at every successful login. I know this is still in alpha (Karmic Koala) so I'll wait for someone to address it properly. Removing the above mentioned file is not something I'd like to play with if it means having to deal with even worst side effects.
Comment 5 Martin Pitt 2009-07-14 18:46:57 UTC
To add some data, this is gdm 2.26.1 and metacity 2.27.0. I tried applying the recent git head patch to fix session client handling (http://git.gnome.org/cgit/gdm/commit/?id=758666242f97ff02c826ee37f2965ac5a828402d), but it doesn't make any difference.

This dialog is shown by metacity whenever a client doesn't properly register to the session. We could just rip it out entirely from metacity (since it also annoys people who use session saving in metacity and have a few non-behaving programs), but it would indeed be better to fix it properly in the greeter, of course.
Comment 6 Ray Strode [halfline] 2009-07-17 02:07:26 UTC
I've worked around this by making the login window be a dock type window.

This makes metacity ignore it at session end and should also put it in the same
ctrl-alt-tab list as the panel at the bottom, which sort of makes sense I guess.
Comment 7 Martin Pitt 2009-07-17 08:38:14 UTC
Works like a charm, many thanks!
Comment 8 Brian Cameron 2009-10-16 02:54:16 UTC
Note that making the login a dock window caused other, fairly serious, problems with the login dialog losing keyboard focus.  Note bug #598235.

So, I think making the login window a dock window isn't the right fix here.

Might it be possible to add a metacity configuration option that tells it to be silent, so programs like GDM could tell metacity to not show this sort of dialog where it doesn't make sense?
Comment 9 Brian Cameron 2009-10-17 03:59:10 UTC
One nice way to fix this might be to add a configuration GConf key and a checkbox in the dialog so users can specify that they don't want to see the pop-up again if checked.  Then GDM could just set that configuration key to avoid it showing when GDM is used.  Or perhaps metacity should take a command-line argument or check an X-atom to specify that the dialog not show up?

At any rate, on Solaris, we are ripping out the dialog until a better fix to this 
bug and bug #598235 is identified.
Comment 10 Gabriel Burt 2009-12-08 00:15:25 UTC
Should we move this to be against metacity, then?
Comment 11 Brian Cameron 2009-12-08 00:27:58 UTC
Yes, I am moving this to metacity.  That makes more sense.
Comment 12 Brian Cameron 2010-04-23 00:16:07 UTC
Can this bug be fixed?  GDM has a serious bug #592183 where the entry field loses focus after clicking on various items.

Using the patch in comment #2 of bug #598235 fixes the GDM focus problems.  However, removing the dock hint causes this pop-up to appear.  As I say in comments #8 and #9, I think metacity should either make it possible to tell metacity to avoid displaying the pop-up, or just remove it since it doesn't really add much value anyway.

Is this possible.  It would really be nice to fix the focus problems in GDM.
Comment 13 Brian Cameron 2010-05-26 00:50:04 UTC
*ping*
Comment 14 Dan Callaghan 2010-10-13 11:41:51 UTC
This has regressed between gdm 2.30.2 and 2.30.3. I see the "save current setup" dialog with 2.30.3 and newer, but it doesn't happen with 2.30.2 or older. Unfortunately the changes between 2.30.2 and 2.30.3 are ridiculously huge so I can't see what might have caused it.

I'm not even using metacity in my session (xmonad instead) but I guess metacity still runs in the gdm session somehow? I have metacity 2.30.3 installed.
Comment 15 André Klapper 2020-11-06 20:06:56 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/metacity/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.