'These windows do not support "save current setup"....' metacity warning when logging in with gdm 2.26

the issue needs to be sent to bugzilla.gnome.org by somebody having the bug

I've reported to bugzilla.gnome.org (http://bugzilla.gnome.org/show_bug.cgi?id=587732)

Removing the file "/usr/share/gdm/autostart/LoginWindow/metacity.desktop" solved this bug for me. I don't get any error messages anymore, and gdm works properly.

I can confirm:

sudo mv /usr/share/gdm/autostart/LoginWindow/metacity.desktop \
/usr/share/gdm/autostart/LoginWindow/metacity.desktop.backup

supresses the symptoms, an error message no longer pops up.

I also can confirm, but with gdm_2.26.1-0ubuntu3_amd64.deb.
Seems that none of the issues I was having were fixed.

Removing metacity means that there won't be any window manager any more, i. e. the window for setting accessibility, etc. don't have any decorations. Also, I get a never-ending waiting mouse cursor, probably due to gnome-session waiting for the window manager to appear.

Metacity comes up all right on my system even if the file is removed. I
can confirm the cursor behaviour though.

Martin Pitt schreef:
> Removing metacity means that there won't be any window manager any more,
> i. e. the window for setting accessibility, etc. don't have any
> decorations. Also, I get a never-ending waiting mouse cursor, probably
> due to gnome-session waiting for the window manager to appear.
>
> ** Also affects: gdm (Ubuntu Karmic)
> Importance: Low
> Assignee: Ubuntu Desktop Bugs (desktop-bugs)
> Status: Triaged
>
> ** Changed in: gdm (Ubuntu Karmic)
> Assignee: Ubuntu Desktop Bugs (desktop-bugs) => Canonical Desktop Team (canonical-desktop-team)
>
> ** Changed in: gdm (Ubuntu Karmic)
> Importance: Low => Medium
>
>

Ruben Verweij [2009-07-07 8:37 -0000]:
> Metacity comes up all right on my system even if the file is removed.

But certainly not in gdm itself, just in your actual user session?

Yes, I think I misunderstood what you were saying earlier. I thought
metacity didn't start in your actual user session too, but I have no
metacity in gdm itself either.

Confirm this bug on three machines after we have new gdm login windows.

I also have this bug too. Here is a screenshot on what it looks like.

Please use the link "This bug affect me too" if you have the same
symptoms. Thanks.

I also see this bug in karmic (for all user accounts on the machine). Although I'm not using amd64, just plain old x86

Linux rex 2.6.31-3-generic #18-Ubuntu SMP Tue Jul 14 04:13:36 UTC 2009 i686 GNU/Linux

This bug also occurs on my T23 (PIII-m -> x86) with current Karmic.

thanks, but we really don't need further confirmations. It's pretty
clear why the bug happens, and everyone can reproduce it, it just
needs some time to fix it.
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

This bug was fixed in the package gdm - 2.26.1git20090717-0ubuntu1

---------------
gdm (2.26.1git20090717-0ubuntu1) karmic; urgency=low

  * Update to latest upstream git head:
    - Make greeter login window be a dock. Fixes metacity complaining about
      session management. (LP: #395324)
  * Drop patches which are fixed upstream:
    - 00git-greeter-session-management.patch
    - 00git-invalid-dmrc-layout.patch
    - 00git-use-after-free.patch
    - 00git-xklavier4.patch
    - 02_dont_force_us_keyboard.patch
    - 04_polkit1.patch
  * 80_workaround_incorrect_directories.patch: Update to new upstream version.
  * Drop 01_xconfigoptions.patch; these configure variables are not used any
    more in the upstream code, and upstream supplies the X.org -br option by
    default now. Also drop the corresponding configure changes from
    17_update_default_xserver.patch.
  * Apply 15_usplash.patch to debian/gdm.init and drop the patch.
  * 17_update_default_xserver.patch: Update to new upstream version, add
    corresponding configure change, add patch tag header, forward upstream,
    and rename to 02_x_server_location.patch.
  * Drop 99_autoreconf.patch. The only remaining build system change is the
    previous item.
  * Drop 20_xdm-stuff.patch, it's just cruft.
  * Drop debian/Xsession, and change debian/rules to install the upstream one.
  * 01_xrdb_nocpp.patch: Add patch tag header, forward upstream.
  * Rename 80_workaround_incorrect_directories.patch to
    04_fix_external_program_directories.patch and add patch tag header.
  * Rename 81_initial_server_on_vt7.patch to 05_initial_server_on_vt7.patch.
  * debian/rules: Remove /var/gdm (empty and nonstandard) and /var/run (will
    be created at runtime), thanks lintian.
  * debian/copyright: Point to versioned GPL, thanks lintian.
  * debian/gdm.postrm: Use "set -e" to conform to policy.
  * Add debian/xterm.desktop: Reintroduce "failsafe xterm" session.

 -- Martin Pitt <email address hidden> Fri, 17 Jul 2009 11:41:35 +0200

I still see this dialog with gdm 2.26.1git20090717-0ubuntu1

Matt Zimmerman [2009-07-18 11:29 -0000]:
> I still see this dialog with gdm 2.26.1git20090717-0ubuntu1

Did you reboot, or restart gdm after the upgrade?

problem is solved for me with gdm 2.26.1git20090717-0ubuntu1

On Sat, Jul 18, 2009 at 01:52:01PM -0000, Martin Pitt wrote:
> Matt Zimmerman [2009-07-18 11:29 -0000]:
> > I still see this dialog with gdm 2.26.1git20090717-0ubuntu1
>
> Did you reboot, or restart gdm after the upgrade?

I rebooted several times, upgrading a few bits and pieces each time. It's
possible that I got confused as to when I saw the dialog. If no one else
confirms, ignore me.

--
 - mdz

Yeah, this seems to have addressed it for me, thanks!

Solved for me too

Sterling work - no more warning message... well done!