Totem ignores "window_on_top" gconf key

[Ben James]

Binary package hint: totem

-------------------------------------

Description:

Totem Movie Player 2.28.2 ignores the setting "window_on_top" - set in Configuration Editor 2.28.0.

-------------------------------------

System:

Ubuntu 9.10 (Karmic Koala).
Totem version: 2.28.2
gconf-editor version: 2.28.0
uname -a: Linux newton 2.6.31-18-generic #55-Ubuntu SMP Fri Jan 8 14:54:52 UTC 2010 x86_64 GNU/Linux

-------------------------------------

Steps to reproduce:

1) Open gconf-editor and set Totem to display on top of other windows: Apps | Totem | window_on_top
2) Open a video - note that the Totem window doesn't stay on top of other windows.

-------------------------------------

[Omer Akram (om26er)]

you can use 'always on top' plugin provided with totem. Its better as when a media is playing window stays on top and when stopped other windows can come over it..

[Ben James (something-for-the-pain)]

Should the gconf key not set the plug-in to be active?

The original point of the bug was that the gconf key "window_on_top" does nothing; regardless of the mechanism used under the hood (be it a built-in function, a plug-in or a wint to the window manager) this key should do something - at the moment it just appears disconnected/broken.

[Sebastien Bacher (seb128)]

setting low priority since that's rather a corner case issues for power users looking for random gconf keys to tweak than an user bug

[Bilal Akhtar (bilalakhtar)]

Forwarded bug upstream

[Pedro Villavicencio (pedro)]

the bug was fixed upstream

"Use the "Always On Top" plugin instead.

commit 0ac6c8843e36042262bc655c1aa327b26ab04f76
Author: Philip Withnall <email address hidden>
Date: Mon Jul 19 21:56:39 2010 +0100

    Bug 624607 — Redundant window_on_top GConf key

    Remove the window_on_top GConf key which was orphaned by the fix to
    bgo#171691. Closes: bgo#624607

 data/totem.schemas.in | 14 --------------
 1 files changed, 0 insertions(+), 14 deletions(-)"

[Sebastien Bacher (seb128)]

the bug is fixed in maverick with 2.31.6 now