http://bugs.winehq.org/show_bug.cgi?id=23257
Summary: TAGAP: mouse input doesn't work
Product: Wine
Version: 1.2-rc4
Platform: x86
URL: http://www.gamershell.com/download_20488.shtml
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gyebro69(a)gmail.com
In the game TAGAP (The Apocalyptic Game About Penguins) mouse is completely
unusable. When you move the mouse, the pointer always jumps back to the
upper-right corner.
Changing the MouseWarpOverride registry entry to enable/disable/force doesn't
help.
--
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=23513
Summary: Dark Fall 2 - Lights Out: Text cropped off pages in
books
Product: Wine
Version: 1.2-rc5
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gaming4jc2(a)yahoo.com
Created an attachment (id=29352)
--> (http://bugs.winehq.org/attachment.cgi?id=29352)
WINEDEBUG=+text wine lightsout.exe 2> blah.txt
This is a somewhat trivial bug, but it affects the gameplay since you cannot
read clues found in books. Attached is a log I got from rolling credits, which
was also cropped/scaled improperly...
--
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=23952
Summary: wine can't launch fullscreen DirectX applications with
enabled dri
Product: Wine
Version: 1.2
Platform: x86
OS/Version: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: alp(a)sfedu.ru
Created an attachment (id=30069)
--> (http://bugs.winehq.org/attachment.cgi?id=30069)
Xorg log file
When I launch any full-screen DirectX windows application, I get following
error:
> wine fallout2.exe
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 1 (X_CreateWindow)
Serial number of failed request: 397
Current serial number in output stream: 399
However, when I disable DRI, most of my Windows games works. I have ATI Radeon
1600 Pro video adapter. X logs and config are attached.
--
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=23985
Summary: Wine doesn't use standard mouse cursor
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ilidrissiamine(a)gmail.com
Created an attachment (id=30123)
--> (http://bugs.winehq.org/attachment.cgi?id=30123)
Patch that makes Wine use standard mouse cursor
Actually, Wine uses it's own (and ugly) mouse cursors instead of the system
one. The patch attached makes Wine use the system mouse cursor (at least the
regular one).
--
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=24451
Summary: Saira: screen resolution problem
Product: Wine
Version: 1.3.2
Platform: x86
URL: http://nifflas.ni2.se/content/Saira/Saira%20112.exe
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gyebro69(a)gmail.com
Created an attachment (id=30846)
--> (http://bugs.winehq.org/attachment.cgi?id=30846)
terminal output
Saira is an indie 2D platformer.
I can only start the game if I choose windowed mode from the game configuration
utility.
In windowed mode the lower part of the screen is cut off, making this game
unplayable.
It doesn't matter if I use Wine's virtual desktop mode or fullscreen. The game
has a 1024x600 resolution and the window cannot be resized. There's no option
to change the resolution.
How to reproduce the issue in the demo:
1. After installation launch the Settings.exe application and make sure
'Windowed' mode is selected (msvcp60.dll needs to be placed into /system32 for
that).
2. Launch the game: the main menu displays correctly but as soon as you start
the game you'll notice the truncated screen.
Fedora 13
Nvidia 7600 / driver 256.53
--
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=15955
Summary: Tomb Raider underworld demo crashes at startup
Product: Wine
Version: 1.1.8
Platform: PC-x86-64
URL: http://forums.eidosgames.com/showthread.php?t=81768
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kgbricola(a)web.de
CC: julliard(a)winehq.org
Created an attachment (id=17140)
--> (http://bugs.winehq.org/attachment.cgi?id=17140)
Crash log.
Tomb Raider underworld demo crashes at start up. This is a regression with the
following patch.
5e2ed6bfe94eb322efe891c07aa8e58b125f36c2 is first bad commit
commit 5e2ed6bfe94eb322efe891c07aa8e58b125f36c2
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Wed Nov 5 20:32:32 2008 +0100
ntdll,server: Fixed access checks for OpenFileMapping and MapViewOfFile.
:040000 040000 2f0316597d54dc0ee871c80465dc4dac295a0f3e
3e9d23a0110f6767160cda3ad4aadaf376c3e508 M dlls
:040000 040000 e3944bdf24bb46aad3b8266661b79d54336690aa
29feaf47301e9cd65d2c216e6bef96c0ad5612bf M include
:040000 040000 04899ab2458e13db1c7a3357483bfef1b9123fcc
158732825f15930c0d3cdeaddfff4e36b75f3cb5 M server
--
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=15950
Summary: wine won't build with bison 2.4
Product: Wine
Version: 1.1.8
Platform: Macintosh
OS/Version: Mac OS X 10.4
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: build-env
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: wine-2008(a)ryandesign.com
With bison 2.3 installed (using MacPorts), wine bulids, but with bison 2.4, it
doesn't. It says:
/usr/bin/gcc-4.0 -c -I. -I. -I../../include -I../../include -D__WINESRC__
-D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing
-Wdeclaration-after-statement -Wwrite-strings -Wpointer-arith -I/mp/include -O2
-o parser.tab.o parser.tab.c
parser.y: In function 'parser_parse':
parser.y:320: error: parse error before '}' token
make[2]: *** [parser.tab.o] Error 1
make[1]: *** [jscript] Error 2
make: *** [dlls] Error 2
Here is the MacPorts project's ticket about this issue:
http://trac.macports.org/ticket/17135
Here's a description of a backwards-incompatible change made in bison 2.4 by
the developer of pure, another program that won't build with bison 2.4
(actually I don't know if that's the same reason wine won't build):
http://groups.google.com/group/pure-lang/browse_thread/thread/60593b93dc8fc…
--
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=15944
Summary: mountmgr only assign drive letters for up to two
removable devices
Product: Wine
Version: 1.1.8
Platform: PC
OS/Version: Linux
Status: NEW
Keywords: regression
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: thestig(a)google.com
It used to be the case that if hal reports a device as a floppy, it gets
assigned to a: or b:, otherwise, the device gets assigned a drive letter
between c and z.
With the changes in mountmgr just before Wine 1.1.7, all removable devices that
are not cdroms are limited to a: or b:, which means if I hot-plug 3 usb thumb
drives, the third one does not get a drive letter.
--
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=19877
Summary: Zeta Minibrowser crashes (because of stubbed
CreateHardLinkW)
Product: Wine
Version: 1.1.28
Platform: PC
URL: http://www.brothersoft.com/zeta-minibrowser-110447.htm
l
OS/Version: Linux
Status: NEW
Keywords: dotnet, download
Severity: normal
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: xerox_xerox2000(a)yahoo.co.uk
I've seen this bug in more apps, so probably a bug covering several
applications
Prerequisites:
'winetricks dotnet20'
The mini-browser crashes after CreateHardLinKW is printed in the console.
Returning TRUE instead of false, or setting last error in CreateHardlink to
ERROR_ALREADY_EXISTST makes the app start fine, but that's just a hack, somehow
we should have more then this stub, to get the app running. I'll attach console
info hereafter
--
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=15452
Summary: Freewire aborts due to incorrect handling of COLORRES
nIndex in winex11's GetDeviceCaps()
Product: Wine
Version: CVS/GIT
Platform: PC
URL: http://www.freewiretv.com/downloadTVWin.html
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nodisgod(a)yahoo.com
Created an attachment (id=16345)
--> (http://bugs.winehq.org/attachment.cgi?id=16345)
Freewire relay log (rzipped)
With current Git (wine-1.1.5-207-gc425c8a), when attempting to launch Freewire
after installation, Freewire aborts with a message box complaining about the
currently set bit depth. From relay trace:
0009:Call user32.GetDC(00000000) ret=005808ac
0009:Ret user32.GetDC() retval=0000030c ret=005808ac
0009:Call gdi32.GetDeviceCaps(0000030c,0000006c) ret=005808b5
0009:Ret gdi32.GetDeviceCaps() retval=00000000 ret=005808b5
0009:Call user32.LoadStringA(00000000,00000095,0032f8d4,00000180) ret=005808f3
0009:Ret user32.LoadStringA() retval=0000015d ret=005808f3
0009:Call user32.LoadStringA(00000000,00000097,0032f754,00000180) ret=00580910
0009:Ret user32.LoadStringA() retval=0000001c ret=00580910
0009:Call user32.MessageBoxA(00000000,0032f8d4 "Unfortunately, it has not been
possible to start Freewire Television due to your graphics mode.\nPlease set
the color depth to 32 bit in the display control panel and restart the
application\nIf the problem continues please contact Freewire customer services
on 0333 123 0190.\nOr visit the Freewire s"...,0032f754 "We've encountered a
problem!",00000030) ret=00580927
The problem seems to lie in:
0009:Call gdi32.GetDeviceCaps(0000030c,0000006c) ret=005808b5
0009:Ret gdi32.GetDeviceCaps() retval=00000000 ret=005808b5
GetDeviceCaps() is being called with the DC handle returned from GetDC(NULL)
and the COLORRES value for nIndex. In dlls/winex11.drv/init.c lines 259 and
268:
case COLORRES:
/* ... */
return 0;
Freewire apparently does not like the returned value, and thus aborts with the
message box. Modifying the COLORRES case to return screen_bpp allows the
application to get past this point, though I am not sure if this is the right
thing to do.
--
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.