Summary: | gnome session forgets xterm position & size | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Shevek <gentoo> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED LATER | ||
Severity: | minor | ||
Priority: | High | ||
Version: | 1.4 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Shevek
2003-10-15 04:16:09 UTC
what window manager are you using ? metacity, as per default. i can't reproduce it, it does get the xterm position & size ok here. I heard some people reporting problems with the gnome-session file after a recent upgrade. They had to remove their session file and create one from scratch to get it to work correctly again. Maybe you could try that. Remove ~/.gnome2/session when you are not inside your session and see if it helps. The session file doesn't contain any geometry information! How on earth is it to know where the window is supposed to be, let alone which virtual desktop it's supposed to be on (argh, why the hell doesn't metacity just use viewports?) 6,id=1016ecbb7d000106892963900000081450006 6,Program=xterm 6,CloneCommand=xterm -fn 7x14 -rv -sl 2048 6,RestartCommand=xterm -xtsessionID 1016ecbb7d000106892963900000081450006 -fn 7x14 -rv -sl 2048 I will try removing the session file sometime. But I don't see where the geometry information is supposed to be. any word on this ? Well, nothing's changed, and it still doesn't work... I can't see anywhere that the geometry information is even stored, never mind restored. It certainly isn't in the session file. I think you are correct after all. Now i reread all of this it's probably a session<->metacity thing, session is only aware of gnome apps i think and the wm should keep track of size/location, but metacity is too lightweight to do so (although metacity session stuff does seem to store some size/location info). I'm going to close this LATER, because these are likely upstream problems/features(?) and we need to get our bugcount down and don't have the time to look into this. If you come to some improved insights in this, please do let us know. I'm sorry for all the delays here. Closing bugs just to get the bug count down is not a valid strategy. This is still a bug. Perhaps WONTFIX is a better resolution? No, I do think this might be a bug to some extent (it may as well be default session/wm behaviour), although not of great importance. Wontfix means we don't want to fix it, later means we want to fix it if a solution pops up/we have time to look at it. |