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

[Bug 11728] New: Picasa / Facebook Uploader does not work
by wine-bugs＠winehq.org Oct. 19, 2011

Oct. 19, 2011

http://bugs.winehq.org/show_bug.cgi?id=11728 Summary: Picasa / Facebook Uploader does not work Product: Wine Version: 0.9.56. Platform: PC URL: http://apps.facebook.com/picasauploader/ OS/Version: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: thestig(a)google.com Prerequisite: a facebook account Steps to reproduce: 1. Install Picasa from http://picasa.google.com/ 2. Install wine gecko 3. Install the facebook uploader from http://apps.facebook.com/picasauploader/ as follows: wine 'c:\Program Files\Picasa2\Picasa2.exe' picasa://importbutton/?url=http://www.webkinesis.com/fbpicasa/facebook.pbf 4. Start Picasa, select some pictures and try to upload using the facebook button Expected Results: Picasa creates an album, uploads the pictures to facebook. (tested on WinXP) Actual Results: Picasa creates an album, but nothing gets uploaded. -- 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 23771] New: Fallout 2 fails to start in 16 bit depth
by wine-bugs＠winehq.org Oct. 19, 2011

Oct. 19, 2011

http://bugs.winehq.org/show_bug.cgi?id=23771 Summary: Fallout 2 fails to start in 16 bit depth Product: Wine Version: 1.1.44 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: b.brachaczek(a)gmail.com CC: julliard(a)winehq.org Fallout 2 (and maybe other games too, haven't tried) fails to start when X Server is run in 16 bpp mode (24 bpp works fine). Only the following message is displayed: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 1 (X_CreateWindow) Serial number of failed request: 386 Current serial number in output stream: 390 The first bad commit is between 1.1.43 and 1.1.44: commit df6cd82ccf5dd03b0362a7ea571e14d66bbc5d72 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Thu May 6 14:57:44 2010 +0200 winex11: Create a window of the appropriate visual to initialize GL info. Stable 1.2 as well as current git have the same issue. Current git with reverted the above commit works fine. System: kernel 2.6.34.1 x86 X.Org Server 1.8.2 xf86-video-openchrome svn rev. 856 (latest) Mesa 7.8.2 (using classic mesa software driver, no hardware 3D support for my VIA Chrome9 chipset) GCC 4.5.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 9

[Bug 20985] New: Crash in CryptMsgUpdate under valgrind
by wine-bugs＠winehq.org Oct. 18, 2011

Oct. 18, 2011

http://bugs.winehq.org/show_bug.cgi?id=20985 Summary: Crash in CryptMsgUpdate under valgrind Product: Wine Version: 1.1.34 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: crypt32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com http://kegel.com/wine/valgrind/logs/2009-12-10-03.53/vg-crypt32_msg.txt shows a crash. Adding +relay,+seh,+crypt shows a bit more: 001e:Call crypt32.CryptMsgUpdate(7f044948,07783e13,00000004,00000000) ret=0774e9b4 trace:crypt:CryptMsgUpdate (0x7f044948, 0x7783e13, 4, 0) 001e:Call KERNEL32.LocalAlloc(00000000,00000011) ret=07be6df0 001e:Ret KERNEL32.LocalAlloc() retval=7f044988 ret=07be6df0 err:seh:segv_handler Got unexpected trap 0 ... 001e:Call KERNEL32.UnhandledExceptionFilter(7f21f5cc) ret=074b5deb ... Unhandled exception: illegal instruction in 32-bit code (0x00000000). Backtrace: =>0 0x00000000 (0x7f21fc48) 1 0x0d3fced4 CryptMsgUpdate+0xa0(hCryptMsg=0x7f0bd740, pbData="", cbData=4, fFinal=0) [dlls/crypt32/msg.c:2786] in crypt32 (0x7f21fc88) 2 0x0cf429b4 test_data_msg_update+0x5b1() [dlls/crypt32/tests/msg.c:445] in crypt32_test (0x7f21fd08) (two logs are smashed together there, so pointers don't match exactly) When run not under valgrind, the same crash happens, but is handled: 001c:Call crypt32.CryptMsgUpdate(00154948,7ec0ce13,00000004,00000000) ret=7ebd79b4 trace:crypt:CryptMsgUpdate (0x154948, 0x7ec0ce13, 4, 0) 001c:Call KERNEL32.LocalAlloc(00000000,00000011) ret=7eb29df0 001c:Ret KERNEL32.LocalAlloc() retval=00154988 ret=7eb29df0 trace:seh:raise_exception code=c0000005 flags=0 addr=(nil) ip=00000000 tid=001c trace:seh:raise_exception info[0]=00000000 trace:seh:raise_exception info[1]=00000000 trace:seh:raise_exception eax=00000000 ebx=7eb68ff4 ecx=00154988 edx=00000011 esi=00000000 edi=0032fc20 trace:seh:raise_exception ebp=0032fbc8 esp=0032facc cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010202 trace:seh:call_vectored_handlers calling handler at 0x7ed88f41 code=c0000005 flags=0 trace:seh:call_vectored_handlers handler at 0x7ed88f41 returned 0 trace:seh:call_stack_handlers calling handler at 0x7eb39d84 code=c0000005 flags=0 001c:Call ntdll.RtlUnwind(0032faf0,7eb39e1a,0032fa74,00000000) ret=7eb39e9f 001c: eax=7eb00b15 ebx=7eb68ff4 ecx=0032fa74 edx=0032faf0 esi=0032faf0 edi=7eb39e1a ebp=0032f588 esp=0032f558 ds=002b es=002b fs=0063 gs=006b flags=00000212 trace:seh:__regs_RtlUnwind code=c0000005 flags=2 trace:seh:__regs_RtlUnwind calling handler at 0x7efb47d4 code=c0000005 flags=2 trace:seh:__regs_RtlUnwind handler at 0x7efb47d4 returned 1 001c:Ret ntdll.RtlUnwind() retval=00000000 ret=7eb39e9f 001c: eax=00000000 ebx=7eb68ff4 ecx=0032fa74 edx=0032faf0 esi=0032faf0 edi=7eb39e1a ebp=0032f588 esp=0032f558 ds=002b es=002b fs=0063 gs=006b flags=00000212 001c:Call KERNEL32.SetLastError(c0000005) ret=7eb39ca6 001c:Ret KERNEL32.SetLastError() retval=c0000005 ret=7eb39ca6 001c:Ret crypt32.CryptMsgUpdate() retval=00000000 ret=7ebd79b4 This is kind of mysterious. I can't find the __TRY that applies to that fault... this could well be a valgrind bug, but I need to understand how it works normally under 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.

1 4

[Bug 17718] New: Fatal error 'Cannot allocate red zone for initial thread' on FreeBSD
by wine-bugs＠winehq.org Oct. 17, 2011

Oct. 17, 2011

http://bugs.winehq.org/show_bug.cgi?id=17718 Summary: Fatal error 'Cannot allocate red zone for initial thread' on FreeBSD Product: Wine Version: 1.1.17 Platform: PC OS/Version: FreeBSD Status: NEW Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gerald(a)pfeifer.com CC: tijl(a)ulyssis.org, austinenglish(a)gmail.com Wine 1.1.17 causes the following on FreeBSD 7.2 when starting almost any application (this is for an old version of calc.exe): Fatal error 'Cannot allocate red zone for initial thread' at line 384 in file /usr/src/lib/libthr/thread/thr_init.c (errno = 2) err:module:attach_process_dlls "ntdll.dll" failed to initialize, aborting err:module:LdrInitializeThunk Main exe initialization for L"C:\\windows\\system32\\wineboot.exe" failed, status 80000101 err:process:__wine_kernel_init boot event wait timed out Fatal error 'Cannot allocate red zone for initial thread' at line 384 in file /usr/src/lib/libthr/thread/thr_init.c (errno = 2) err:module:attach_process_dlls "ntdll.dll" failed to initialize, aborting err:module:LdrInitializeThunk Main exe initialization for L"Z:\\home\\pfeifer\\_\\wcalc.exe" failed, status 80000101 Segmentation fault (core dumped) -- 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 23641] New: Need for speed Most wanted controls error
by wine-bugs＠winehq.org Oct. 17, 2011

Oct. 17, 2011

http://bugs.winehq.org/show_bug.cgi?id=23641 Summary: Need for speed Most wanted controls error Product: Wine Version: 1.2-rc7 Platform: x86 OS/Version: other Status: UNCONFIRMED Severity: critical Priority: P1 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: s_paul1408(a)yahoo.com My OS is ubuntu 10.04. With wine rc2 nfs most wanted+patch 1.3+crack wouldn't start, but when i tested rc7 it worked almost perfect except a control bug: it's as if the "left arrow" is pressed. It keeps turning left, even after i changed the controls. The same problem is with gta vice city and gta san andreas, except it's the "down arrow". -- 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 25

[Bug 12267] New: winstone 32 hangs
by wine-bugs＠winehq.org Oct. 17, 2011

Oct. 17, 2011

http://bugs.winehq.org/show_bug.cgi?id=12267 Summary: winstone 32 hangs Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Here's what happens when you launch c:\zdbench\ws32\ui.exe: it puts up its window, says "examining the execution environment" (although you can't see it, since the window is too big, and falls off the bottom), and hangs. err:ntdll:RtlpWaitForCriticalSection section 0x7b922ee0 "syslevel.c: Win16Mutex" wait timed out in thread 0016, blocked by 0012, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x7bc8d6e4 "loader.c: loader_section" wait timed out in thread 0012, blocked by 0016, retrying (60 sec) It hangs just like this on XP, too. But what the heck, if we could get it to not hang on wine, that'd be nice. -- 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 11109] New: dream of mirror online crash
by wine-bugs＠winehq.org Oct. 17, 2011

Oct. 17, 2011

http://bugs.winehq.org/show_bug.cgi?id=11109 Summary: dream of mirror online crash Product: Wine Version: 0.9.52. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: petifrancais(a)gmail.com Created an attachment (id=10143) --> (http://bugs.winehq.org/attachment.cgi?id=10143) txt contenant les erreurs en console The game game domo crash after the logo "GameTribe" -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 11

[Bug 16674] New: Battle for middle earth2: No network multiplayer possible
by wine-bugs＠winehq.org Oct. 17, 2011

Oct. 17, 2011

http://bugs.winehq.org/show_bug.cgi?id=16674 Summary: Battle for middle earth2: No network multiplayer possible Product: Wine Version: 1.1.11 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P4 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: mcflow-forum(a)gmx.net Multiplayer games with Battle for Middle Earth2 in wine are not possible. According to the information on the game package it uses TCP/IP for network multiplayer. I already tried using the native dplay dlls like it is stated in the wiki, LAN still does not work. It happens like this: I enter the network mode and the game displays myself two times in the players list. The other player sees me in the list only one time, as it should be. I can read what he writes and vice versa. If I write something I can see it two times in the chat. For the other user it appears only one time. Now, if I open a game, the other player can see it in the game list. If he wants to join he gets a "Connection Timout" error. Same happens if the other player opens a game and I want to join it. I searched the Bugzilla for quite a time now because I do not want to open a duplicate bug. I found a few things that first sounded interesting but when I tested them nothing changed. I found a note at the AppDB page of Garena 3.0 (http://appdb.winehq.org/objectManager.php?sClass=version&iId=14147&iTesting…) Patching with the patch that is linked there did not solve the problem with wine-1.1.11(well one of the hunks failed but it compiled) In Bug 9787 there also was a patch for the AcceptEX for wine-1.1.6. It did not work with wine-1.1.6. It said that wine does not include AcceptEX. I'm not sure if "The battle for middle earth" requires it. I did not find anything about it on the net except that it uses tcp/ip. -- 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 27

[Bug 19083] New: Respondus LockDown Browser: outside processes should not be able to detect its window (appinstall)
by wine-bugs＠winehq.org Oct. 17, 2011

Oct. 17, 2011

http://bugs.winehq.org/show_bug.cgi?id=19083 Summary: Respondus LockDown Browser: outside processes should not be able to detect its window (appinstall) Product: Wine Version: 1.1.21 Platform: PC URL: https://hdc.tamu.edu/files/book/6/425/LockDownSetup_1. 0.3.exe OS/Version: Linux Status: NEW Keywords: download, testcase Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Not sure how to describe this exactly...but the Respondus Lockdown Browser is meant to be used by universities to make sure that students don't use other programs when taking quizzes/exams/etc. As a result, it does some really funky stuff...While writing an appinstall test for it, found a few interesting things. First up, on windows, the IfWinExist (http://www.autohotkey.com/docs/commands/IfWinExist.htm) function fails for this window (never seen that happen for any other app). On wine, however, we detect it just fine. -- 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 15250] New: MINITAB 14 graph editor crashes when File menu is clicked
by wine-bugs＠winehq.org Oct. 17, 2011

Oct. 17, 2011

http://bugs.winehq.org/show_bug.cgi?id=15250 Summary: MINITAB 14 graph editor crashes when File menu is clicked Product: Wine Version: CVS/GIT Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: nodisgod(a)yahoo.com Created an attachment (id=16034) --> (http://bugs.winehq.org/attachment.cgi?id=16034) rzipped relay log With current Git (wine-1.1.4-292-g4b4109a), when clicking on the File menu in the graph editor, mtb14ge.exe, the application crashes. The point at which the application crashes seems to be here: 0009:Call user32.CallWindowProcW(7edae5b0,00010030,00000229,00000000,00000000) ret=5f8487d1 0009:Call window proc 0x7edae5b0 (hwnd=0x10030,msg=WM_MDIGETACTIVE,wp=00000000,lp=00000000) 0009:Ret window proc 0x7edae5b0 (hwnd=0x10030,msg=WM_MDIGETACTIVE,wp=00000000,lp=00000000) retval=00000000 0009:Ret user32.CallWindowProcW() retval=00000000 ret=5f8487d1 0009:Ret window proc 0x5f870878 (hwnd=0x10030,msg=WM_MDIGETACTIVE,wp=00000000,lp=00000000) retval=00000000 0009:Ret user32.SendMessageW() retval=00000000 ret=5f862aa3 0009:Call KERNEL32.TlsGetValue(00000003) ret=5f870ec6 0009:Ret KERNEL32.TlsGetValue() retval=00139408 ret=5f870ec6 0009:Call KERNEL32.TlsGetValue(00000003) ret=5f870ec6 0009:Ret KERNEL32.TlsGetValue() retval=00139408 ret=5f870ec6 0009:Call KERNEL32.TlsGetValue(00000003) ret=5f870ec6 0009:Ret KERNEL32.TlsGetValue() retval=00139408 ret=5f870ec6 trace:seh:raise_exception code=c0000005 flags=0 addr=0x32eeda Compressed relay log is 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.

1 11