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 359898 - Open Totem in the last position
Open Totem in the last position
Status: RESOLVED WONTFIX
Product: totem
Classification: Core
Component: Movie player
unspecified
Other All
: Normal enhancement
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2006-10-05 14:38 UTC by Marcelo Martins
Modified: 2006-10-08 16:18 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Marcelo Martins 2006-10-05 14:38:20 UTC
When close totem, save the position.

In next time that totem is open, the position must be the last.

(please, speel check my english)
Comment 1 Bastien Nocera 2006-10-05 15:47:17 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 164918 ***
Comment 2 Bastien Nocera 2006-10-06 08:19:56 UTC
I'm afraid that that's the window manager's job, not the application's.
Comment 3 Jon Dufresne 2006-10-08 16:18:53 UTC
Metacity developers disagree. From the Metacity README:

Q: Why does Metacity remember the workspace/position of some apps 
   but not others across logout/login?

A: Metacity only stores sizes/positions for apps that are session
   managed. As far as I can determine, there is no way to attempt to
   remember workspace/position for non-session-aware apps without
   causing a lot of weird effects.

   The reason is that you don't know which non-SM-aware apps were
   launched by the session. When you initially log in, Metacity sees a
   bunch of new windows appear. But it can't distinguish between
   windows that were stored in your session, or windows you just
   launched after logging in. If Metacity tried to guess that a window
   was from the session, it could e.g. end up maximizing a dialog, or
   put a window you just launched on another desktop or in a weird
   place. And in fact I see a lot of bugs like this in window managers
   that try to handle non-session-aware apps.

   However, for session-aware apps, Metacity can tell that the
   application instance is from the session and thus restore it
   reliably, assuming the app properly restores the windows it had 
   open on session save.
   
   So the correct way to fix the situation is to make apps
   session-aware. libSM has come with X for years, it's very
   standardized, it's shared by GNOME and KDE - even twm is
   session-aware. So anyone who won't take a patch to add SM is more
   archaic than twm - and you should flame them. ;-)