December 2010 - Wine-Bugs - list.winehq.org

[Bug 24956] New: King's Bounty - The Legend: no native mouse pointer
by wine-bugs＠winehq.org Dec. 31, 2014

Dec. 31, 2014

http://bugs.winehq.org/show_bug.cgi?id=24956 Summary: King's Bounty - The Legend: no native mouse pointer Product: Wine Version: 1.3.6 Platform: x86 URL: http://www.gamershell.com/download_32652.shtml OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Created an attachment (id=31603) --> (http://bugs.winehq.org/attachment.cgi?id=31603) console log King's Bounty-The Legend (and its sequel, KB-Armored Princess) doesn't show its own mouse pointer (a pointing hand icon, wearing a gauntlet) but the standard Wine mouse pointer. The mouse pointer works properly both in the menu and in the main game though (except it doesn't change its shape when it should). The attached log doesn't show too much valuable information. It was created by starting the game, skipping the intros and waiting until the main menu appears (the mouse pointer should show up already in the menu). It didn't work in Wine-1.0.1 either. -- 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.

1 10

[Bug 25057] New: Magic Workstation: mwsplay.exe crashes when launching it
by wine-bugs＠winehq.org Dec. 31, 2014

Dec. 31, 2014

http://bugs.winehq.org/show_bug.cgi?id=25057 Summary: Magic Workstation: mwsplay.exe crashes when launching it Product: Wine Version: 1.3.6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: graffity2199(a)yahoo.fr Created an attachment (id=31772) --> (http://bugs.winehq.org/attachment.cgi?id=31772) The complete trace log Hello, When launching MWSPlay.exe, it simply crashes displaying an "Access violation" exception and I don't know why. I'm running it with the latest wine version (1.3.6) on my 10.04 Ubuntu. Could you help me finding out what's going on ? I've launched the following commands : $ uname -a Linux graffity-desktop 2.6.32-24-generic-pae #39-Ubuntu SMP Wed Jul 28 07:39:26 UTC 2010 i686 GNU/Linux $ wine --version wine-1.3.6 $ WINEDEBUG=+trace,+seh,+tid,+relay wine MWSPlay.exe 2> MWSPlayTrace.txt $ lzma -9 MWSPlayTrace.txt You'll find as attachement the generated log. Thanks a lot for your time ! Regards, -- 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.

1 18

[Bug 25161] New: Warlords III demo: mouse clicks don't register in the main game
by wine-bugs＠winehq.org Dec. 31, 2014

Dec. 31, 2014

http://bugs.winehq.org/show_bug.cgi?id=25161 Summary: Warlords III demo: mouse clicks don't register in the main game Product: Wine Version: 1.3.7 Platform: x86 URL: http://download.cnet.com/Warlords-III-demo/3000-7562_4 -10010589.html 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=31914) --> (http://bugs.winehq.org/attachment.cgi?id=31914) terminal output After bug #24779 has been fixed, I'm facing with an another problem now: neither mouse clicks nor the keyboard works after you started a new game. The mouse works in the menus and during the character selection stage, but not in the main game. I can't select any units, can't scroll the screen. The keyboard shortcuts are non-functional, too (e.g. ctrl+q doesn't brings up the confirmation dialogue). I tried the demo in virtual desktop mode and in fullscreen, too: none of them worked. It doesn't work in Wine-0.9.33 either. Fedora 14 x86 Gnome 2.32.0 -- 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.

1 5

[Bug 25292] New: Galcon Fusion: Steam overlays don't work in the game
by wine-bugs＠winehq.org Dec. 31, 2014

Dec. 31, 2014

http://bugs.winehq.org/show_bug.cgi?id=25292 Summary: Galcon Fusion: Steam overlays don't work in the game Product: Wine Version: 1.3.7 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kelytharun(a)gmail.com As title says, there are no Steam overlays in this game. No achievements, no forums, no chat, etc. The overlays work perfectly in other games I have, using the same configuration. -- 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.

1 5

[Bug 25327] New: Risen - No space between words in Risen
by wine-bugs＠winehq.org Dec. 31, 2014

Dec. 31, 2014

http://bugs.winehq.org/show_bug.cgi?id=25327 Summary: Risen - No space between words in Risen Product: Wine Version: 1.3.8 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: mcflow-forum(a)gmx.net Created an attachment (id=32190) --> (http://bugs.winehq.org/attachment.cgi?id=32190) Screenshot that shows the problem. In Risen the texts are a bit messed up. There are no spaces between words. On the screenshot you can see the text on the bottom (it's german). It should be: "Wenn ein Gegner zu stark für dich ist[...]". Instead it's all displayed as one word. Ingame it is the same for quest descriptions and so on. -- 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.

1 21

[Bug 15955] New: Tomb Raider underworld demo crashes at startup
by wine-bugs＠winehq.org Dec. 31, 2014

Dec. 31, 2014

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.

1 6

[Bug 15950] New: wine won't build with bison 2.4
by wine-bugs＠winehq.org Dec. 31, 2014

Dec. 31, 2014

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.

1 8

[Bug 15944] New: mountmgr only assign drive letters for up to two removable devices
by wine-bugs＠winehq.org Dec. 31, 2014

Dec. 31, 2014

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.

1 4

[Bug 19877] New: Zeta Minibrowser crashes (because of stubbed CreateHardLinkW)
by wine-bugs＠winehq.org Dec. 30, 2014

Dec. 30, 2014

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.

1 8

[Bug 15452] New: Freewire aborts due to incorrect handling of COLORRES nIndex in winex11's GetDeviceCaps()
by wine-bugs＠winehq.org Dec. 30, 2014

Dec. 30, 2014

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.

1 14