The problem persistant for fedora 10 as well

The problem also occurs if you launch a gnome-session but directly specified openbox as being the window manager instead of metacity.

The 'openboox-session' script has the xprop removals to fix the problem,
but if gnome is also being used than that gets by-passed.




If gdm is doing something that could effect other clients later, then it is the
natural responsibility for THAT PROGRAM to clean up after itself.

That is standard programming practice.

I am thus reasonably sure that this problem is NOT just openbox, but probably with ALL window managers, except possibly metacity, whcih does not appear to be affected by it (probably due to its brain-dead simplistic behaviour. 



One way is to have the xprop cleanups added to the GDM PreSession script. That way the fix does become part of the source of the problem, gdm.  It then cleans it up before it can effect ANYTHING the user decides to use, be it openbox or something else.

As such I would pass this on to who-ever designed the current re-vamp of the gdm, as well as to SuSE, Redhat, and anyone else using this gdm.

I agree in principle.  https://bugzilla.redhat.com/show_bug.cgi?id=444135#c2 seems to suggest that it's actually metacity run from gdm which causes the problem.  It would be great if you could verify that this is the case (e.g. by testing with kdm and no xprop hacks).

That would need something with a working knowledge on how GDM is actually handling this display.  Very little information is available on this.

However the problems only started to happen with the new change in GDM where it started to use a gnome panel along the bottom of the display.  I don't think it is running metacity WM, just a limited gnome session and panel.

In any case something in the setup od GDM sets the root window properties, and its failure to clean up those properties is the cause of the problems in openbox, and, I assume, other WM's as well.

(In reply to comment #3)
> That would need something with a working knowledge on how GDM is actually
> handling this display.  Very little information is available on this.
> 
> However the problems only started to happen with the new change in GDM where it
> started to use a gnome panel along the bottom of the display.  I don't think it
> is running metacity WM, just a limited gnome session and panel.

I just checked, and gdm very definitely *is* spawning metacity every time the greeter is shown.  It stops running during session login.

*** Bug 4278 has been marked as a duplicate of this bug. ***

This bug reproduced with latest openbox package in OpenSuSe 11.2 - openbox-3.4.7.2-5.2.i586.

Any news regarding this problem? I see the latest comment was added more then half a year ago.

Did somebody let GDM team know about this problem, open defect against GDM, etc.?

Anyway, it would be great if openbox will support some hack to cleanup those properties, while GDM-team will fix the main problem, if they will.. This is standard programming practice.

I don't think I reported it to the GDM team - would be great if someone else has time to do this as I don't.

I've added xprop removals to the openbox-*-session startup scripts, to kill the properties set by metacity. See commit f0df9bb9d8f4f8182e60996d92a7b0e47549a0f6.