"allow the window manager to control the windows" is checked off, but whenever I run a fullscreen program, Gnome seems to have no control over the windows other than being able to close them. Can't minimize, alt-tab out, or bring up the window menu.
This showed up sometime after 1.3.19, but i haven't been able to find anyone talking about it. Is anyone else having problems with this?
Window Manager can't controll Fullscreen windows
-
jjmckenzie
- Moderator
- Posts: 1153
- Joined: Wed Apr 27, 2011 11:01 pm
Window Manager can't controll Fullscreen windows
On 6/14/11 12:19 AM, Airris wrote:
is one method.
However, it appears that you may have more than one program installed.
We highly recommend using one program - one WinePrefix. The FAQ
describes how to do this.
Delete the entire .wine (Wine's simulated Windows Directory structure)Huh. So i upgraded to 1.3.22, still same problem, reverted to 1.3.19, and also the same problem. Which is odd since it used to work in 1.3.19.
Maybe the config file got bugged out or something? Is there a way to reset it completely?
is one method.
However, it appears that you may have more than one program installed.
We highly recommend using one program - one WinePrefix. The FAQ
describes how to do this.
-
jjmckenzie
- Moderator
- Posts: 1153
- Joined: Wed Apr 27, 2011 11:01 pm
Window Manager can't controll Fullscreen windows
On 6/18/11 11:18 PM, Airris wrote:
Instructions are in the Wine FAQ http://wiki.winehq.org/FAQ
You can create a new WinePrefix and install your program there.I've changed versions a bit, only one is ever on at once. Deleting all of .wine Is doable but if there's any intermediate step to try first I'd really prefer that over reinstalling a rather large number of programs.
Instructions are in the Wine FAQ http://wiki.winehq.org/FAQ
-
Martin Gregorie
Window Manager can't controll Fullscreen windows
On Sun, 2011-06-19 at 15:58 -0500, Airris wrote:
MSFS and the programs used to create scenery and aircraft), in its own
Wine prefix this time. Then, if you need to reinstall anything in a new
prefix, you won't end up reinstalling everything else too.
I do this as a matter of course and write a tiny wrapper script to run
each program - this script can be run from the command line or by
clicking an icon - you make the launcher run the script rather than
issuing the wind command directly:
=========start of script=============
#!/bin/bash
export WINEPREFIX=.wine_myapp
cd $WINEWPREFIX/path/to/the/exe
wine myapp.exe \/opts arguments
==========end of script==============
and make the script executable before trying to run it.
Martin
So put each program, or closely related set of programs (e.g. MS Office,Deleting .wine and reinstalling did nothing other than leave me a ton of work to reinstall all the programs I need :\ Still same behavior.
MSFS and the programs used to create scenery and aircraft), in its own
Wine prefix this time. Then, if you need to reinstall anything in a new
prefix, you won't end up reinstalling everything else too.
I do this as a matter of course and write a tiny wrapper script to run
each program - this script can be run from the command line or by
clicking an icon - you make the launcher run the script rather than
issuing the wind command directly:
=========start of script=============
#!/bin/bash
export WINEPREFIX=.wine_myapp
cd $WINEWPREFIX/path/to/the/exe
wine myapp.exe \/opts arguments
==========end of script==============
and make the script executable before trying to run it.
Martin
That's an option, but it does nothing to solve my original problem. And deleting .wine did nothing so I'd probably avoid being so hasty to ever do that again.
All I wanted when posting this was to inquire whether this was a known regression bug since that has a lot different set of response i can take than a problem isolated to my system.
All I wanted when posting this was to inquire whether this was a known regression bug since that has a lot different set of response i can take than a problem isolated to my system.
