wine-bugs November 2012

wine-bugs@winehq.org

1 participants
8957 discussions

[Bug 21187] New: OLE Exception code 80004002 - AmiBroker + AmiQuote
by wine-bugs＠winehq.org 04 Nov '25

04 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=21187 Summary: OLE Exception code 80004002 - AmiBroker + AmiQuote Product: Wine Version: 1.1.35 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ole32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: mxn(a)atlas.cz Steps to reproduce: 1) Download AmiBroker (trial application ver. 5.20) from http://www.amibroker.com/download.html 2) Install it with command 'wine AmiBroker520.exe' 3) 'cd' to directory where AmiBroker trianl is installed 4) Start AmiBroker with command 'wine Broker.exe' 5) Start AmiQuote with command 'wine AmiQuote/Quote.exe' 6) In 'AmiQuote' choose 'Tools -> Auto-update Amibroker database' 7) Error dialog pops up 'OLE Exception code 80004002' 8) downgrade wine to ver. 1.1.33 9) Repeat steps 4) - 6), no Error dialog is displayed and everything works correctly (database is updated) Note: I believe bug is also reproducible in wine 1.1.34. -- 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.

2 21

[Bug 21483] New: changed token security breaks .NET Framework SDK tools
by wine-bugs＠winehq.org 04 Nov '25

04 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=21483 Summary: changed token security breaks .NET Framework SDK tools Product: Wine Version: 1.1.33 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, some of Microsoft's tools from .NET Framework SDKs - namely managed debuggers (CLR) - stopped working after 1.1.33+ release. They seem to be very picky about object security. I bisected this one but technically this isn't a regression because Rob's token patches made Wine more correct - exposing another object security problem. --- snip --- $ git bisect bad bd56916f90e68632993a7275fe30a55a7efa222a is the first bad commit commit bd56916f90e68632993a7275fe30a55a7efa222a Author: Rob Shearman <robertshearman(a)gmail.com> Date: Mon Nov 16 20:11:06 2009 +0000 server: Extend get_token_user server call to also retrieve SIDs for the token's owner or primary group. :040000 040000 829f1543526675ae48f6fde8c8cedff74fd51797 7a77653291795c209ec529dd6660d52fc922a58c M dlls :040000 040000 57735b53b28db37ac4627dc009000e225175164a 4dcc1388cb136e559c06106632c08e8e610fe557 M include :040000 040000 4e83227cb0133c7e288a1e930461d4efe1130882 cf1c3539d6b3c91c854fa2b9b672f68ea601f639 M server --- snip --- "old" behaviour, where default process token was like this: Token owner -> S-1-5-4 "NT AUTHORITY\INTERACTIVE" (well-known group) Token user -> S-1-5-4 "NT AUTHORITY\INTERACTIVE" (well-known group) Token primary group -> S-1-5-32-544 "BUILTIN\Administrators" (alias) NtQueryInformationToken had the token owner info hard-coded (to SECURITY_INTERACTIVE_RID) while Rob's patches moved the actual query to wineserver. --- Basically the app code that verifies the security of created objects goes like this: - get SD from created object (event) handle -> GetKernelObjectSecurity( OWNER_SECURITY_INFORMATION | DACL_SECURITY_INFORMATION) - get owner SID of SD -> GetSecurityDescriptorOwner() -> SID1 - get DACL of SD -> GetSecurityDescriptorDacl() - for each ACE from DACL (GetAce) -> SID2: check ACE SID against SD owner SID -> EqualSid( SID1, SID2) - match -> profit! not -> fail! --- snip --- ... 0023: create_event( access=001f0003, attributes=00000080, manual_reset=1, initial_state=0, objattr={rootdir=0014,sd={control=00000004,owner=<not present>,group=<not present>,sacl={},dacl={{AceType=ACCESS_ALLOWED_ACE_TYPE,Mask=e01f001f,AceFlags=0,Sid={S-1-5-4}},{AceType=ACCESS_ALLOWED_ACE_TYPE,Mask=e01f001f,AceFlags=0,Sid={S-1-5-4}}}},name=L"Global\\CorDBIPCSetupSyncEvent_36"} ) 0023: create_event() = 0 { handle=01c4 } ... 0025:trace:advapi:GetKernelObjectSecurity (0xc4,0x00000005,0x14ef40,0x00000050,0x33f7e8) 0025:trace:ntdll:NtQuerySecurityObject (0xc4,0x00000005,0x14ef40,0x00000050,0x33f7e8) 0025: get_security_object( handle=00c4, security_info=00000005 ) 0025: get_security_object() = 0 { sd_len=00000050, sd={control=00000037,owner={S-1-5-4},group=<not present>,sacl={},dacl={{AceType=ACCESS_ALLOWED_ACE_TYPE,Mask=e01f001f,AceFlags=0,Sid={S-1-5-4}},{AceType=ACCESS_ALLOWED_ACE_TYPE,Mask=e01f001f,AceFlags=0,Sid={S-1-5-4}}}} } 0025:trace:ntdll:RtlGetDaclSecurityDescriptor (0x14ef40,0x33f7c3,0x33f7ec,0x33f7c2) 0025:trace:ntdll:RtlGetAce (0x14ef60,0,0x33f7f0) 0025:trace:ntdll:RtlLengthSid sid=0x14ef54 0025: open_event( access=001f0003, attributes=00000002, rootdir=0034, name=L"Global\\CorDBIPCLSEventAvailName_36" ) 0025: open_event() = 0 { handle=00c8 } ... --- snip --- "new" behaviour, where default process token is now like this: Token owner -> S-1-5-32-544 "BUILTIN\Administrators" (alias) Token user -> S-1-5-4 "NT AUTHORITY\INTERACTIVE" (well-known group) Token primary group -> S-1-5-32-544 "BUILTIN\Administrators" (alias) --- snip --- ... 0024:trace:ntdll:NtOpenProcessTokenEx (0x1b0,0x00000008,0x00000000,0x318e6d0) 0024: open_token( handle=01b0, access=00000008, attributes=00000000, flags=00000000 ) 0024: open_token() = 0 { token=01b4 } ... 0024:trace:advapi:GetTokenInformation (0x1b4, TokenOwner, 0x184130, 20, 0x318e6e0): 0024:trace:ntdll:NtQueryInformationToken (0x1b4,4,0x184130,20,0x318e6e0) 0024: get_token_sid( handle=01b4, which_sid=00000004 ) 0024: get_token_sid() = 0 { sid_len=16, sid={S-1-5-32-544} } ... 0024: create_event( access=001f0003, attributes=00000080, manual_reset=1, initial_state=0, objattr={rootdir=0018,sd={control=00000004,owner=<not present>,group=<not present>,sacl={},dacl={{AceType=ACCESS_ALLOWED_ACE_TYPE,Mask=e01f001f,AceFlags=0,Sid={S-1-5-32-544}},{AceType=ACCESS_ALLOWED_ACE_TYPE,Mask=e01f001f,AceFlags=0,Sid={S-1-5-32-544}}}},name=L"Global\\CorDBIPCSetupSyncEvent_37"} ) 0024: create_event() = 0 { handle=01c8 } ... 0026:trace:advapi:GetKernelObjectSecurity (0xc8,0x00000005,(nil),0x00000000,0x33f7e8) 0026:trace:ntdll:NtQuerySecurityObject (0xc8,0x00000005,(nil),0x00000000,0x33f7e8) 0026: get_security_object( handle=00c8, security_info=00000005 ) 0026: get_security_object() = 0 { sd_len=00000058, sd={control=00000037,owner={S-1-5-4},group=<not present>,sacl={},dacl={{AceType=ACCESS_ALLOWED_ACE_TYPE,Mask=e01f001f,AceFlags=0,Sid={S-1-5-32-544}},{AceType=ACCESS_ALLOWED_ACE_TYPE,Mask=e01f001f,AceFlags=0,Sid={S-1-5-32-544}}}} } ... --- snip --- Using the "admins" sid (alias) as token user in server/token.c:token_create_admin() instead of current "interactive" sid fixes the problem. Though I don't know if this is the right thing to do. I hope I provided enough infos and let Alexandre handle it ;-) To get detailed token infos/dumps you might be interested in this little console app, from cygwin's Corinna Vinschen ;-) http://www.mail-archive.com/cygwin@cygwin.com/msg71800.html It might provide useful information when run under different security principals. 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.

2 16

[Bug 32010] New: Guild Wars 2 updater uses always 100% of a CPU core
by wine-bugs＠winehq.org 02 Nov '25

02 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=32010 Bug #: 32010 Summary: Guild Wars 2 updater uses always 100% of a CPU core Product: Wine Version: 1.5.15 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: nob.dir.info(a)gmail.com Classification: Unclassified The launcher of Guild Wars 2 (where you enter your user name and password) uses a complete core to run (even if I don't write anything or move it). I think it's bug, because X comes laggy too, and on Windows 7 its don't uses a whole core to run. -- 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.

2 22

[Bug 24466] New: Sid Meier's Pirates! frequent hiccups, temporary lock-ups
by wine-bugs＠winehq.org 31 Oct '25

31 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=24466 Summary: Sid Meier's Pirates! frequent hiccups, temporary lock-ups Product: Wine Version: 1.3.3 Platform: x86 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=30870) --> (http://bugs.winehq.org/attachment.cgi?id=30870) terminal output Sid Meier's Pirates! (patched to the latest 1.0.2 version) performs badly in Wine. This issue is described in several test results on the Appdb page of the game, too. I can observe the following symptoms: - After the intro video played, it takes almost 2 minutes to get into the main menu (without noticeable hdd activity). - When I get into the game and visit any places in the port (Governor, Merchant, Tavern etc.) it usually takes the game 15-20 seconds to display the next screen (although music plays continuously). - While sailing, the game frequently "freezes" for 2-3 seconds without no apparent reasons. When those hiccups occur all animations freeze on the current screen until the next screen is loaded but music plays fluently. Reducing the screen resolution, graphical details or disable audio doesn't help. I remember playing this game several years ago in a native Win XP without this issues. No demo available. Fedora 13 x86 AMD Athlon 64 x2 4200+ 3 GB Ram Kernel 2.6.34.6 Nvidia 7600 GT / 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.

2 19

[Bug 10349] New: Yukon Trail installer crashes at the end
by wine-bugs＠winehq.org 31 Oct '25

31 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=10349 Summary: Yukon Trail installer crashes at the end Product: Wine Version: 0.9.48. Platform: Other OS/Version: other Status: UNCONFIRMED Severity: minor Priority: P2 Component: wine-misc AssignedTo: wine-bugs(a)winehq.org ReportedBy: echidnaman(a)gmail.com Created an attachment (id=9017) --> (http://bugs.winehq.org/attachment.cgi?id=9017) Crash Log After the Yukon Trail's installer is done installing, it crashes, taking the file browser it spawns with it. To reproduce: -Run installer -Complete installation -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 36

[Bug 14838] New: TMPDIR environment variable is not used at all
by wine-bugs＠winehq.org 30 Oct '25

30 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=14838 Summary: TMPDIR environment variable is not used at all Product: Wine Version: CVS/GIT Platform: PC URL: http://en.wikipedia.org/wiki/TMPDIR OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: killertux(a)suomi24.fi Tested on Wine 1.1.2-307-g520ab5c Wine simply does not use TMPDIR environment variable and as far as I know Wine has never used this environment variable... it just defaults to /tmp -- 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.

2 16

[Bug 9314] New: Borland C++ Builder 5 expects registry values to be read in the same order they were written
by wine-bugs＠winehq.org 28 Oct '25

28 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=9314 Summary: Borland C++ Builder 5 expects registry values to be read in the same order they were written Product: Wine Version: 0.9.43. Platform: PC-x86-64 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: wine-advapi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: mikolaj.zalewski(a)gmail.com Created an attachment (id=7584) --> (http://bugs.winehq.org/attachment.cgi?id=7584) test It arranges the component palettes in the same order in which it read the values from the registry (even if MSDN exlicitly says not to rely on the order in which the values are read). We store the values in the alphabetical order to binsearch them so the palettes under Wine are in alphabetical order instead of the configured order. I attach a small test showing that under Windows the values are read in the same order as they were written. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 20

[Bug 31704] New: AutoCAD 2008: Next button doesn't work in activation window
by wine-bugs＠winehq.org 25 Oct '25

25 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=31704 Bug #: 31704 Summary: AutoCAD 2008: Next button doesn't work in activation window Product: Wine Version: 1.5.13 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: jscript AssignedTo: wine-bugs(a)winehq.org ReportedBy: lukasz.wojnilowicz(a)gmail.com Classification: Unclassified Created attachment 41677 --> http://bugs.winehq.org/attachment.cgi?id=41677 Activation window Steps to reproduce: 1) remove ~/.wine 2) winetricks dotnet20sp2 3) install AutoCAD 4) wine acad.exe 5) select that you want to activate product and click next 6) enter your registrations data 6) click next (see attached image) Behaviour: Nothing happens. Expected behaviour: Content of window should change. -- 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.

2 34

[Bug 11995] New: Wipeout XL hangs at startup
by wine-bugs＠winehq.org 22 Oct '25

22 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=11995 Summary: Wipeout XL hangs at startup Product: Wine Version: CVS/GIT Platform: Other URL: http://www.3dgamers.com/dlselect/games/wipeoutxl/wipeout xl.zip.html OS/Version: other Status: NEW Keywords: download Severity: normal Priority: P2 Component: winmm&mci AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com In http://jmikeneedham.dyndns.org/?p=10, a user complained that Psygnosis Wipeout XL hangs on startup. I confirmed this with the downloadable demo, http://www.3dgamers.com/dlselect/games/wipeoutxl/wipeoutxl.zip.html Name wipeoutxl.zip Size 6153701 sha1sum 5e420f8e79ac63e1e3bb76692dbfb0ae1caf1161 Looking at the log, it seems to be looping endlessly looking for an audio CD to be inserted. This was common practice back in the day; gamers would always throw an audio CD-ROM in the drive so they could listen to music while they played. Games often came on hybrid audio/data cds. When you insert a hybrid audio/data cd, though, you have to tell the system to mount the data portion, else wine won't give it a drive letter. So, if you jump through those hoops (e.g. insert a cd-rom and tell the system to mount it), the game will continue to the next problem: you can tell the game to start, and the welcome screen then goes away, but no game window comes up. The log shows: fixme:win:EnumDisplayDevicesW ((null),0,0x34f820,0x00000000), stub! fixme:xrandr:X11DRV_XRandR_SetCurrentMode Cannot change screen BPP from 32 to 8 err:xrandr:X11DRV_XRandR_SetCurrentMode Resolution change not successful -- perhaps display has changed? So I guess the next step is to try this on an 8 bit display. -- 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.

2 13

[Bug 31232] New: The Way Things Work 2.0 installer froze after finished copying files
by wine-bugs＠winehq.org 22 Oct '25

22 Oct '25

http://bugs.winehq.org/show_bug.cgi?id=31232 Bug #: 31232 Summary: The Way Things Work 2.0 installer froze after finished copying files Product: Wine Version: 1.1.21 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: Nachanon_Vetjasit(a)hotmail.com Classification: Unclassified Regression SHA1: 54d7c8012d1d7369a56779955ced5a09e448a1cd When started The Way Things Work 2.0 installer (setup.exe), the setup proceeds normally, through the welcome screen, quicktime installer prompt (though QuickTime 16bit 2.1.1 installation didn't work [bug #18260]), installation options (express/custom), files copying progress window. But as soon as the file copying window disappeared, the installer froze, no screen repainting, no message from WINE's console. (Normally this stage should be creating program groups and ends at the 'Setup Complete' window) 54d7c8012d1d7369a56779955ced5a09e448a1cd is first bad commit commit 54d7c8012d1d7369a56779955ced5a09e448a1cd Author: Dmitry Timoshkov <dmitry(a)codeweavers.com> Date: Wed Apr 29 15:17:35 2009 +0900 explorer: Initialize the Progman DDE interface when starting explorer. :040000 040000 4a347655bb6f41b8b8377d8e3e3e25c1551d1730 05513d15b76a99fe5033c4422a82008667425088 M programs With WINE before this commit, the installation would continue, with WINE's Program Manager (progman) popped up with a dialog from the setup program: "Unable to start DDE communication with Program Manager." [Abort/Retry/Ignore] If clicked 'Ignore' (aka. continue despite the error), this step will be repeated for another five time, each time leaving one Program Manager window opened (6 window total at the end). And finished with 'Setup Complete' window. Note: The Way Things Work is a 16-bit application, and supports Windows 3.1. Tested using WINE's Windows version 98. WINE: wine-1.1.21 source distribution System: Debian GNU/Linux 5.0 "Lenny" i386 (Intel Pentium 4 2.66GHz) -- 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.

2 9

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs November 2012