Mac OS X issue since 0.9.59
Mac OS X issue since 0.9.59
In short, when running a application via wine, the active window migrates down my screen until it disappears, and then returns from the top of the screen. This problem did not exist with 0.9.58, but has been present ever since.
I compile wine from source by running ./tools/wineinstall, as suggested in the README file that comes with the source.
Can anyone else verify this problem? Or is it local to my system? Any help would be much appreciated.
Hardware Overview:
Model Name: MacBook
Model Identifier: MacBook3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 4 GB
Bus Speed: 800 MHz
Boot ROM Version: MB31.008E.B02
SMC Version: 1.24f2
Xquartz 2.2.2 - (xorg-server 1.3.0-apple21)
gcc --version
i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5465)
I compile wine from source by running ./tools/wineinstall, as suggested in the README file that comes with the source.
Can anyone else verify this problem? Or is it local to my system? Any help would be much appreciated.
Hardware Overview:
Model Name: MacBook
Model Identifier: MacBook3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 4 GB
Bus Speed: 800 MHz
Boot ROM Version: MB31.008E.B02
SMC Version: 1.24f2
Xquartz 2.2.2 - (xorg-server 1.3.0-apple21)
gcc --version
i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5465)
Running OS X 10.5.3
Forgot to include that I'm running OS X 10.5.3
Mac OS X issue since 0.9.59
On Tue, Jun 17, 2008 at 7:44 PM, zullil <[email protected]> wrote:
http://wiki.winehq.org/RegressionTesting
Please run a regression test:Forgot to include that I'm running OS X 10.5.3
http://wiki.winehq.org/RegressionTesting
-
- Newbie
- Posts: 1
- Joined: Wed Jun 18, 2008 12:42 pm
Re: Mac OS X issue since 0.9.59
I've had that happen once, but not since then. It was only one window, and would only move down when I interacted with it. I quit it before it had the chance to wrap to the top of the screen. Here are the (fuzzy) details...
- iMac 2Ghz Core 2 Duo
- Mac OS X 10.5.3
- Wine RC(?), Kronenburg build
- XQuartz 2.2.?
- Some native libraries
- I think the app might have been 7zip file manager
- iMac 2Ghz Core 2 Duo
- Mac OS X 10.5.3
- Wine RC(?), Kronenburg build
- XQuartz 2.2.?
- Some native libraries
- I think the app might have been 7zip file manager
zullil wrote:In short, when running a application via wine, the active window migrates down my screen until it disappears, and then returns from the top of the screen. This problem did not exist with 0.9.58, but has been present ever since.
I compile wine from source by running ./tools/wineinstall, as suggested in the README file that comes with the source.
Can anyone else verify this problem? Or is it local to my system? Any help would be much appreciated.
Hardware Overview:
Model Name: MacBook
Model Identifier: MacBook3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 4 GB
Bus Speed: 800 MHz
Boot ROM Version: MB31.008E.B02
SMC Version: 1.24f2
Xquartz 2.2.2 - (xorg-server 1.3.0-apple21)
gcc --version
i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5465)
Mac OS X issue since 0.9.59
zullil wrote:
that shows this problem.
Austin:
If I have the time this weekend, I'll run a regression test on this
using Mike Kronenberg's build system and also to verify that the problem
exists.
James McKenzie
Please file a bug report on this issue. I will require the applicationThanks for suggesting regression testing, but I don't want to take the time now for that process.
I'd really like to know if anyone can verify what I'm seeing. If so, then maybe there's an issue worth investigating further.
that shows this problem.
Austin:
If I have the time this weekend, I'll run a regression test on this
using Mike Kronenberg's build system and also to verify that the problem
exists.
James McKenzie
Same issue present in 1.0
Thanks for the responses. I just compiled Wine-1.0 and used it to run the Windows version of Firefox 3. The same "wandering window" issue exists on my machine.
The issue seems to occur with many other apps too.
By the way, I'm now using Xquartz 2.2.3 - (xorg-server 1.3.0-apple21)
I'll hold off on the bug report, until someone else can confirm that there is a non-local problem.
The issue seems to occur with many other apps too.
By the way, I'm now using Xquartz 2.2.3 - (xorg-server 1.3.0-apple21)
I'll hold off on the bug report, until someone else can confirm that there is a non-local problem.
Mac OS X issue since 0.9.59
On Thu, Jun 19, 2008 at 7:46 AM, zullil <[email protected]> wrote:
Does wine notepad have the same problem?Thanks for the responses. I just compiled Wine-1.0 and used it to run the Windows version of Firefox 3. The same "wandering window" issue exists on my machine.
The issue seems to occur with many other apps too.
By the way, I'm now using Xquartz 2.2.3 - (xorg-server 1.3.0-apple21)
I'll hold off on the bug report, until someone else can confirm that there is a non-local problem.
Re: Mac OS X issue since 0.9.59
No.Does wine notepad have the same problem?
The problem seems to occur when an application updates or modifies part of an existing window. I hope that makes sense.
Mac OS X issue since 0.9.59
"zullil" <[email protected]> writes:
--
Alexandre Julliard
[email protected]
It's a known bug in quartz-wm: http://bugs.winehq.org/show_bug.cgi?id=12431Thanks for suggesting regression testing, but I don't want to take the time now for that process.
I'd really like to know if anyone can verify what I'm seeing. If so, then maybe there's an issue worth investigating further.
--
Alexandre Julliard
[email protected]
Re: Mac OS X issue since 0.9.59
Thanks for clearing this up. So to avoid the problem I need to run a different window manager. That's a shame, but maybe I'll look into it.="Alexandre Julliard"]<[email protected]> writes:
It's a known bug in quartz-wm: http://bugs.winehq.org/show_bug.cgi?id=12431
I wonder if Apple has been informed of this issue in quartz-wm?