October 2014 - Wine-Bugs - list.winehq.org

[Bug 32631] New: Word 2007 Cursor does not display in caption window
by wine-bugs＠winehq.org Jan. 30, 2015

Jan. 30, 2015

http://bugs.winehq.org/show_bug.cgi?id=32631 Bug #: 32631 Summary: Word 2007 Cursor does not display in caption window Product: Wine Version: 1.5.20 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: goonstk(a)yahoo.com Classification: Unclassified Attached image There is no additional terminal output. The cursor does not display and when the mouse is over the textbox, the mouse does not change from the normal white arrow mouse to the I shaped cursor mouse. R -- 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 32626] New: Pylotro Wine error - Unable to launch
by wine-bugs＠winehq.org Jan. 30, 2015

Jan. 30, 2015

http://bugs.winehq.org/show_bug.cgi?id=32626 Bug #: 32626 Summary: Pylotro Wine error - Unable to launch Product: Wine Version: 1.4 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: shane.kelly55(a)gmail.com Classification: Unclassified Created attachment 43053 --> http://bugs.winehq.org/attachment.cgi?id=43053 Wine Error output on PyLotro Trying to install LOTRO using Wine. I ran out of room on my linux partition so I installed LOTRO to a directory (using WINE) to my windows partition where there was more room. Wine saw everything and installed the game without fail. I proceeded to do the PyLotro install via Wine and pointed it to the custom install directory. I even ran the Patches without fail. When try i launch PyLotro, the client comes up fine. but if try to connect i get a Wine error seen in the attachment. Note: My wine bottle is Windows 7 and both PyLotro and the default Lotro clients are in that bottle. -- 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 32204] New: GameRanger - not closing login loader screen
by wine-bugs＠winehq.org Jan. 30, 2015

Jan. 30, 2015

http://bugs.winehq.org/show_bug.cgi?id=32204 Bug #: 32204 Summary: GameRanger - not closing login loader screen Product: Wine Version: 1.5.17 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lewisclement(a)hotmail.com Classification: Unclassified After starting GameRanger and succesfully logging in, the loader won't disappear. You can see all game rooms and friends, but those windows will be unresposive. Manually closing the loader will get you rid of it, but the other windows are still unresponsive. Flash advertisements don't show up. Maybe something to do with that? Possibly just a side-effect of unresponsive windows. The first report of this bug is from 19 september 2012. Note: the first time I ran GameRanger in Wine(1.5.16) the program actually worked correctly. After doing a reinstall of my OS this problem, which has been reported by other persons before, suddenly appeared. -- 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 29298] New: Olympus Viewer 2 crashes when starting
by wine-bugs＠winehq.org Jan. 30, 2015

Jan. 30, 2015

http://bugs.winehq.org/show_bug.cgi?id=29298 Bug #: 29298 Summary: Olympus Viewer 2 crashes when starting Product: Wine Version: 1.3.34 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ole32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: suamor(a)web.de Classification: Unclassified When starting the Olympus Viewer 2 (Version 1.21) software, the application crashes. If I run winedbg I get the following backtrace: Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x7bc48a9a). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:7bc48a9a ESP:058ae4f0 EBP:058ae50c EFLAGS:00010202( R- -- I - - - ) EAX:00110014 EBX:7bca5ff4 ECX:00000000 EDX:001fab48 ESI:001fb190 EDI:00ffffff Stack dump: 0x058ae4f0: 001fb190 00000002 001fb190 000f0000 0x058ae500: 7bca5ff4 00110014 001fab48 058ae55c 0x058ae510: 7bc48c29 00000648 00000000 00000000 0x058ae520: 7bc4777e 7bc4777e 00110014 00000000 0x058ae530: 00000212 00000010 7e823ff4 058ae5a0 0x058ae540: 00000648 7bc35c4f 7e776ee8 00110000 Backtrace: =>0 0x7bc48a9a in ntdll (+0x38a9a) (0x058ae50c) 1 0x7bc48c29 in ntdll (+0x38c28) (0x058ae55c) 2 0x7bc48e39 RtlFreeHeap+0x78() in ntdll (0x058ae5bc) 3 0x7e776ee8 in ole32 (+0x36ee7) (0x058ae5fc) 4 0x020c1a0c in olyshlop (+0x1a0b) (0x058ae750) 5 0x01fab349 in filemgr2 (+0xb348) (0x023f85e4) 6 0x00000000 (0x01fc2ab0) 7 0x01faa690 in filemgr2 (+0xa68f) (0x01fbd9be) System used: Ubuntu 10.04 LTS. The problem is reproducible on my system. However sometimes (without winedbg) I can run the application until I choose a directory containing ORF raw files. It seems the application tries to create a preview of the files and crashes. Due to winedbg halting the application I cannot say if this problem is related. I tested both with my full wine installation and a clean wine installation containing the required components Directx9 and IE6 with no differently observed behaviour. FYI: I added the application to the App Database. -- 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 23890] New: Star wars Galactic Battleground Game CD not detected
by wine-bugs＠winehq.org Jan. 30, 2015

Jan. 30, 2015

http://bugs.winehq.org/show_bug.cgi?id=23890 Summary: Star wars Galactic Battleground Game CD not detected Product: Wine Version: 1.1.4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mountmgr.sys AssignedTo: wine-bugs(a)winehq.org ReportedBy: yann.eeckhoudt(a)laposte.net Created an attachment (id=29993) --> (http://bugs.winehq.org/attachment.cgi?id=29993) screenshot (in french) When I try to play with Star Wars Galactic Battleground, the application ask for the game CD to be inside the drive. The game CD is already in the drive but does not seem to be detected. My version of Wine is 1.1.42 -- 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 22738] New: Trans communicator problem, Assertion Failed.
by wine-bugs＠winehq.org Jan. 30, 2015

Jan. 30, 2015

http://bugs.winehq.org/show_bug.cgi?id=22738 Summary: Trans communicator problem, Assertion Failed. Product: Wine Version: 1.1.44 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: blocker Priority: P4 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: qoolbio(a)gmail.com CC: qoolbio(a)gmail.com Created an attachment (id=28034) --> (http://bugs.winehq.org/attachment.cgi?id=28034) log file of the trans communicator problem I've managed to install my app from trans_setup_3_3.exe file and everything looked fine, even when i launch the app no bugz appear, the problem starts when i log into the program. after doing this it brings me this msg window: "Assertion failed: succeeded (hr) newsy.cpp line 1367", Im a real newbie in linux distros, right now im using opensuse 11.1 and my wine ver is 1.1.44 I attached the bug log file as well. Please help me guys because i can't work without this app running sweet. -- 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 32815] New: Jedi Outcast menu is garbled
by wine-bugs＠winehq.org Jan. 30, 2015

Jan. 30, 2015

http://bugs.winehq.org/show_bug.cgi?id=32815 Bug #: 32815 Summary: Jedi Outcast menu is garbled Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: timmyfartpants(a)gmail.com Classification: Unclassified When I play Jedi Outcast and start a new game, and I press ESC to quit to pause and take me to the main menu, it appears garbled. I almost can't tell what is what after you pause to the menu so many times. -- 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 32577] New: BUHL t@x 2012 fails with 1.4.1 and 1.5.6 does not show everything, does not update and is hence not usable
by wine-bugs＠winehq.org Jan. 30, 2015

Jan. 30, 2015

http://bugs.winehq.org/show_bug.cgi?id=32577 Bug #: 32577 Summary: BUHL t(a)x 2012 fails with 1.4.1 and 1.5.6 does not show everything, does not update and is hence not usable Product: Wine Version: 1.5.6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: steffen_moeller(a)gmx.de Classification: Unclassified The problem arises with BUHL t(a)x 2012 after installation. A test version, maybe more interestingly for t(a)x 2013 is available on http://www.buhl.de/testversionen/steuern/page.html The "repair" of a non-functional installation (reported as completed) with 1.4.1 now with wine-1.5.6 brought maik(a)MAIK:/mnt$ wine start.exe maik(a)MAIK:/mnt$ p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory fixme:apphelp:ApphelpCheckInstallShieldPackage stub: 0x33f1fc L"D:\\Setup\\data1.hdr" fixme:advapi:SetNamedSecurityInfoW L"C:\\users\\Public\\Application Data\\Buhl Data Service GmbH" 1 4 (nil) (nil) 0xcaeac0 (nil) fixme:ieframe:taskbar_list_SetProgressState iface 0xcb6ad0, hwnd 0x200cc, flags 2 stub! fixme:ieframe:taskbar_list_SetProgressValue iface 0xcb6ad0, hwnd 0x200cc, ullCompleted 0, ullTotal 64 stub! fixme:clusapi:GetNodeClusterState ((null),0x33ec04) stub! fixme:advapi:DecryptFileA "c:\\5baefe6a0c99fa0b588de9a6\\" 00000000 fixme:heap:HeapSetInformation (nil) 1 (nil) 0 p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. fixme:advapi:LsaOpenPolicy ((null),0x33f2f8,0x00000001,0x33f2e4) stub fixme:advapi:LsaClose (0xcafe) stub fixme:storage:create_storagefile Storage share mode not implemented. fixme:shell:IShellLinkW_fnGetPath (0xcdb878): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xcdb878): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xced018): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xced018): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xcc0258): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xcc0258): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xd32e50): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xd32e50): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xce1610): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xce1610): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xced018): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xced018): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xcec128): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xcec128): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xcf56e0): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xcf56e0): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xcbcd70): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xcbcd70): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xcf2120): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xcf2120): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xced018): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xced018): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xce3210): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xce3210): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xcf56e0): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0xcf56e0): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0x20d8a8): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0x20d8a8): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0x20c978): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkW_fnGetPath (0x20c978): WIN32_FIND_DATA is not yet filled. and then the repair nicely terminates. When starting from the command line, the online update of the binaries do not work (parsing error) and when compared with the Windows version, I found a selection of items on the left for entering the data to be not complete. The systray icon appeared but a right-click on it to terminate was ignored. $ wine stman2012.exe fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:system:SetProcessDPIAware stub! fixme:msg:ChangeWindowMessageFilter 111 00000001 fixme:msg:ChangeWindowMessageFilter c053 00000001 fixme:msg:ChangeWindowMessageFilter c054 00000001 fixme:msg:ChangeWindowMessageFilter c055 00000001 fixme:msg:ChangeWindowMessageFilter c056 00000001 fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:msxml:domdoc_get_parseError (0x13c27c)->(0x33e910): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x143dc4)->(0x33e9e0): creating a dummy parseError fixme:win:FlashWindowEx 0x33e714 maik(a)MAIK:~/.wine/drive_c/Program Files/Buhl finance/tax Steuersoftware 2012$ fixme:imm:NotifyIME IMC_SETCANDIDATEPOS fixme:imm:ImmReleaseContext (0x20142, 0x1b86e0): stub fixme:win:FlashWindowEx 0x33e2a4 fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:system:SetProcessDPIAware stub! fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:wininet:query_global_option INTERNET_OPTION_PER_CONNECTION_OPTION stub fixme:shell:SHGetFileInfoW SHGFI_OVERLAYINDEX unhandled fixme:shell:SHGetFileInfoW SHGFI_OVERLAYINDEX unhandled fixme:msg:pack_message msg 80 (WM_SETICON) not supported yet fixme:msg:pack_message msg 80 (WM_SETICON) not supported yet fixme:msg:ChangeWindowMessageFilter c067 00000001 fixme:systray:wine_notify_icon unhandled tray message: 4 fixme:imm:NotifyIME IMC_SETCANDIDATEPOS fixme:win:FlashWindowEx 0x33c3ac fixme:imm:NotifyIME IMC_SETCANDIDATEPOS fixme:imm:ImmReleaseContext (0x401c0, 0x15b450): stub fixme:win:FlashWindowEx 0x33ca8c fixme:win:FlashWindowEx 0x33d20c fixme:imm:NotifyIME IMC_SETCANDIDATEPOS fixme:win:FlashWindowEx 0x33c2ec fixme:imm:NotifyIME IMC_SETCANDIDATEPOS fixme:imm:NotifyIME IMC_SETCANDIDATEPOS fixme:imm:NotifyIME IMC_SETCANDIDATEPOS fixme:imm:NotifyIME IMC_SETCANDIDATEPOS fixme:imm:NotifyIME IMC_SETCANDIDATEPOS fixme:win:FlashWindowEx 0x33d2cc fixme:msxml:domdoc_get_parseError (0x1c9e54)->(0x33e5a8): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x13c734)->(0x33e3d8): creating a dummy parseError fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! fixme:msxml:domdoc_get_parseError (0x1d5574)->(0x33e1c4): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1d5574)->(0x33e418): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1d5574)->(0x33e32c): creating a dummy parseError fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! fixme:msxml:domdoc_get_parseError (0x1d5574)->(0x33e14c): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1d5574)->(0x33e3a4): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1d5574)->(0x33e3a4): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1d5574)->(0x33e3a4): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1c9e3c)->(0x33e678): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1d1d2c)->(0x33e5a8): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1ca754)->(0x33e3d8): creating a dummy parseError fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! fixme:msxml:domdoc_get_parseError (0x1ca754)->(0x33e1c4): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1ca754)->(0x33e418): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1ca754)->(0x33e32c): creating a dummy parseError fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! fixme:msxml:domdoc_get_parseError (0x1ca754)->(0x33e14c): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1ca754)->(0x33e3a4): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1ca754)->(0x33e3a4): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1ca754)->(0x33e3a4): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1d1d2c)->(0x33e678): creating a dummy parseError fixme:win:FlashWindowEx 0x33e720 fixme:win:FlashWindowEx 0x33ab6c fixme:win:FlashWindowEx 0x337ba0 fixme:msxml:domdoc_get_parseError (0x1e724c)->(0x33aab0): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1d9984)->(0x33a8e0): creating a dummy parseError fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! fixme:msxml:domdoc_get_parseError (0x1d9984)->(0x33a6cc): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1d9984)->(0x33a920): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1d9aec)->(0x33a834): creating a dummy parseError fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! fixme:msxml:domdoc_get_parseError (0x1d9aec)->(0x33a654): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1d9aec)->(0x33a8ac): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1d9aec)->(0x33a8ac): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1d9aec)->(0x33a8ac): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1e724c)->(0x33ab80): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1e6ce4)->(0x33aab0): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1dac84)->(0x33a8e0): creating a dummy parseError fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! fixme:msxml:domdoc_get_parseError (0x1dac84)->(0x33a6cc): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1dac84)->(0x33a920): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1dadbc)->(0x33a834): creating a dummy parseError fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do! fixme:msxml:domdoc_get_parseError (0x1dadbc)->(0x33a654): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1dadbc)->(0x33a8ac): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1dadbc)->(0x33a8ac): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1dadbc)->(0x33a8ac): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1e6ce4)->(0x33ab80): creating a dummy parseError fixme:win:FlashWindowEx 0x33a384 fixme:win:FlashWindowEx 0x337c58 fixme:win:FlashWindowEx 0x33c1bc fixme:imm:NotifyIME IMC_SETCANDIDATEPOS fixme:win:FlashWindowEx 0x33bb90 fixme:win:FlashWindowEx 0x33a1f8 fixme:win:FlashWindowEx 0x337ad8 fixme:win:FlashWindowEx 0x33a628 fixme:win:FlashWindowEx 0x337f18 fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:system:SetProcessDPIAware stub! fixme:system:SetProcessDPIAware stub! fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:ntdll:NtLockFile I/O completion on lock not implemented yet fixme:shell:SHGetFileInfoW SHGFI_OVERLAYINDEX unhandled fixme:shell:SHGetFileInfoW SHGFI_OVERLAYINDEX unhandled fixme:shell:SHGetFileInfoW SHGFI_OVERLAYINDEX unhandled fixme:shell:SHGetFileInfoW SHGFI_OVERLAYINDEX unhandled fixme:msg:ChangeWindowMessageFilter c067 00000001 fixme:msg:ChangeWindowMessageFilter c067 00000001 fixme:systray:wine_notify_icon unhandled tray message: 4 fixme:systray:wine_notify_icon unhandled tray message: 4 fixme:win:FlashWindowEx 0x33c818 fixme:msxml:domdoc_get_parseError (0x1e634c)->(0x338734): creating a dummy parseError fixme:msxml:domdoc_get_parseError (0x1e6324)->(0x338804): creating a dummy parseError fixme:imm:NotifyIME IMC_SETCANDIDATEPOS fixme:win:FlashWindowEx 0x33c3ac ... Sometimes the systray appears upon start, sometimes not. tæx is very popular and BUHL had a Wine?-based Windows version of t(a)x in the past, which was abondoned at the time because of a lack of interest. I could imagine this to be different today. Many thanks Steffen -- 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 3

[Bug 32570] New: I get an error when I try to install the game
by wine-bugs＠winehq.org Jan. 30, 2015

Jan. 30, 2015

http://bugs.winehq.org/show_bug.cgi?id=32570 Bug #: 32570 Summary: I get an error when I try to install the game Product: Wine Version: 1.4 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ruchtijonas(a)googlemail.com Classification: Unclassified Created attachment 42982 --> http://bugs.winehq.org/attachment.cgi?id=42982 error file I get an error when the installation is almost over. -- 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 32534] New: Access violation at address 00879E18 in module 'ct3.exe'. Read of address 00000008.
by wine-bugs＠winehq.org Jan. 30, 2015

Jan. 30, 2015

http://bugs.winehq.org/show_bug.cgi?id=32534 Bug #: 32534 Summary: Access violation at address 00879E18 in module 'ct3.exe'. Read of address 00000008. Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: mrhattontoyou(a)gmail.com Classification: Unclassified Created attachment 42931 --> http://bugs.winehq.org/attachment.cgi?id=42931 log file Access violation at address 00879E18 in module 'ct3.exe'. Read of address 00000008. Program won't start, keep getting the above error. -- 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