http://bugs.winehq.org/show_bug.cgi?id=3023
Erich Hoover <ehoover(a)mines.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ehoover(a)mines.edu
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=3023
--- Comment #27 from Erich Hoover <ehoover(a)mines.edu> 2011-01-26 10:27:47 CST ---
Created an attachment (id=33000)
--> (http://bugs.winehq.org/attachment.cgi?id=33000)
Test focus with end dialog
(In reply to comment #25)
> Eliot Blennerhassett sent in a patch,
> http://www.winehq.org/pipermail/wine-patches/2010-July/090363.html
> but Alexandre replied with "needs tests". Anyone who can
> write a test that fails without that patch but passes with it,
> please do!
You're not going to like to hear this, but I tried to make a test to show that
the fix works and I instead ended up demonstrating that it introduces a bug.
I've attached a patch that modifies the "msg" test to (pretty much) just run
the test of interest. When you run this test with the "fix" it will report
that the dialog itself is the active window after EndDialog is called, which is
not the case when you run the test on Windows. If I had to guess then I'd say
that WINPOS_ActivateOtherWindow is getting called at the wrong time, probably
that OrCad captures some window notification event, changes the active window,
and then we override it when we call WINPOS_ActivateOtherWindow.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=5629
Austin English <austinenglish(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
URL|http://www.genline.se/GFFin |http://www.genline.com/gffd
|der2_install.exe |ownloads/GFFinder_install.e
| |xe
--- Comment #9 from Austin English <austinenglish(a)gmail.com> 2011-01-26 03:19:30 CST ---
Image is no longer mirrored, but prints grainy/blurry. wine-1.3.12-82-g72e089d
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6549
--- Comment #12 from Austin English <austinenglish(a)gmail.com> 2011-01-26 03:13:09 CST ---
Still present in git.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7698
--- Comment #205 from Kimmo Huoso <sleijeri(a)gmail.com> 2011-01-26 01:43:00 CST ---
(In reply to comment #204)
> I'm too affected. It started appearing after i bought new wide screen LCD panel
> and changed resolution of virtual desktop and other apps from 1152*864 to
> 1440*900.
>
> Ubuntu 10.10 64bit, nVidia GF9600GT 260.19.06, Wine 1.3.11 and now 12.
Confirming similar typer or crashing. And its instant. Started to crash
instantly while i changed 1680x1050 resolution screen. Used to have 1280x1024
which didnt crash. my system nvidia 460GTX (latest nvidia drivers), wine 1.3.11
and Arch linux x86_64
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=5048
Juan Lang <juan_lang(a)yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CLOSED |REOPENED
Resolution|FIXED |
--- Comment #15 from Juan Lang <juan_lang(a)yahoo.com> 2011-01-25 10:28:00 CST ---
Not fixed.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7698
Jan Kalab <pitlicek(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pitlicek(a)gmail.com
--- Comment #204 from Jan Kalab <pitlicek(a)gmail.com> 2011-01-25 10:06:47 CST ---
I'm too affected. It started appearing after i bought new wide screen LCD panel
and changed resolution of virtual desktop and other apps from 1152*864 to
1440*900.
Ubuntu 10.10 64bit, nVidia GF9600GT 260.19.06, Wine 1.3.11 and now 12.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=19981
Summary: Not all keys are recognized with dinput
Product: Wine
Version: 1.1.28
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dinput
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: peter.ganzhorn(a)googlemail.com
Running Far Cry (1) I noticed I was unable to open the in-game console using
the "^" key.
First I assumed there was a problem with the keyboard layout as the keys "z"
and "y" were swapped in Far Cry as well (I am using a German keyboard).
Running wine-notepad the "z" and "y" keys are NOT swapped, and "^" works
perfectly.
Going through the output when running Far Cry I found out the German keyboard
layout was detected correctly, so that is not the problem.
Changing the keyboard layout in xorg.conf and gnome to the standard USA-layout
did not help at all.
Then I tried installing a native dinput8 DLL with winetricks, as the output
told me Far Cry has a CryInput.dll which uses Direct Input.
With the native dinput8 the keys work perfectly good, but there's another
issue:
The mouse can only be moved within a rectangle much smaller than the game
window itself. With the wine-dinput this works perfectly.
I tried setting options like "Allow DirectX apps to stop the mouse leaving
their window", changing from full-screen to windowed mode and changing the
resolution of the game.
Still, the rectangle in which the mouse can be moved stays in the same relative
size. In windowed mode when the mouse is allowed to leave DirectX windows, the
cursor jumps from the border of that rectangle to outside the game window and
when moved back, straight back into that rectangle on all sides.
Since this strange mouse behaviour occurs with a native dinput8, I guess that
doesn't cound as bug.
So in a nutshell the bug is that my keys aren't correctly recognized with the
built-in dinput of wine.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=5048
--- Comment #14 from Jon Griffiths <jon_p_griffiths(a)yahoo.com> 2011-01-24 21:29:16 CST ---
(In reply to comment #10)
> TransmitFile may have an implementation, but the ws2_32 side of the coin here
> is still doing a FIXME("unimplemented TransmitFile").
>
> Didn't the problem just get moved further down the pipe?
It did, this bug isn't fixed, since my patch never made it in.
> I've done a bit of digging on a related issue (details here
> http://forum.winehq.org/viewtopic.php?p=54231#54231), and am working on tying
> together a possible TransmitFile implementation. Is anyone else (actively)
> working similar, or otherwise know of a reason why I shouldn't pursue this?
I last had a spate of wine submissions when i had a month or so off work. I'm
back at work more than full time now and can't afford the time to massage the
patch to get through. I tried to implement tests for this function to get it in
and encountered all sorts of unrelated issues in testing that would have taken
me far too long to uncover, so i dropped it, hoping that someone might pick it
up. A bunch of other patches got ignored at the same time so I decided to enjoy
my holiday rather than struggle to get the changes in. It didn't help that the
bug was marked fixed when it clearly wasn't. It seemed like the 1.0 series
brought out a focus on ticking boxes without focusing on the actual user
experience.
I'm happy if you want to pick up my patch and go with it, its still
serviceable. The error handling just needs to be fixed according to the last
feedback I got, and you could implement overlapped IO but its not needed to
make docuwiki work.
Its a shame I think that the barrier for entry for submissions has been raised
so high now. I can understand it for existing functionality, but for
unimplemented functions a kaizen approach would be better. Checking in the
original patch with a FIXME for the error handling would have benefited users
more. Someone else could easily have fixed just that issue with the code in
tree, rather than letting it bitrot.
I still have patches from 8 years ago that never made it in, and more from a
couple of years ago too. But for someone like me with very limited time, the
hassle of maintaining a tree full of changes just isn't worth it when there
isn't clear feedback on what needs to be done to get patches in, or lots of
extra work is demanded before stuff will be accepted. I'll try again when I get
more time, but that could be 5 years away at this point. In the future I've
thought I might just contribute tests, since they should be easier to get in.
Anyway, the same goes for any patch I've ever sent that didn't make it in. I'm
happy for anyone to rework/resubmit them, just please give credit + shared
copyright if enough of the original work remains to warrant it. I'm happy to
answer any questions about old patches too.
Cheers
Jon
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=25840
Summary: Galactic Civilizations: Crash on startup
Product: Wine
Version: 1.3.11
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: brad(a)bcable.net
Created an attachment (id=32924)
--> (http://bugs.winehq.org/attachment.cgi?id=32924)
Entire log of running GalCiv2.exe
On this hardware:
- ASUS N61VG
- Intel Core 2 Duo
- 4GB RAM
- 1GB Video Memory (NVIDIA GeFORCE GT220M)
Using this software
- GRML64 2010.12 (100% compatible with Debian Sid)
- NVIDIA drivers 256.35 OR 260.19.29
- Kernel: Linux dalek 2.6.36-grml64 #1 SMP PREEMPT
Mon Dec 13 13:16:48 UTC 2010 x86_64 GNU/Linux
- wine: 1.2.2, 1.3.9, OR 1.3.11 (from Ubuntu packages)
- X.org: 1.7.7-10 (Debian)
With these wine overrides:
- d3dx9_24 through d3dx9_42
- mmdevapi (disabled)
- msvcrt (native, builtin)
- msxml3 (native)
- msxml3r (native)
- usp10 (native, builtin)
- winhttp (builtin)
The following errors occur:
1) Error prompt that says you are running at 0x0 resolution.
2) Error prompt that says you are running at 0-bit color depth.
3) Error prompt that states there is less than 32MB video RAM.
4) Error promp tthat says you are on old drivers, needs > 2005 and DirectX
9.0c
5) DirectX accelaration not enabled
On GRML64 2010.4 these errors would pass and then the game would run just fine.
On GRML64 2010.12 there is another error after these that states "The program
GalCiv2.exe has encountered a serious problem and needs to close", and then
fails.
The kernel for 2010.12 is listed above, and for 2010.4 it was 2.6.33.2.
Attached is a log from doing `wine GalCiv2.exe &> galciv2.log`.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.