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.
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.
http://bugs.winehq.org/show_bug.cgi?id=32342
Bug #: 32342
Summary: PlanetSide2 Error message and bugreport.txt and
debug.log in Steam.
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: linards.liepins(a)gmail.com
Classification: Unclassified
Created attachment 42683
--> http://bugs.winehq.org/attachment.cgi?id=42683
PlanetSide2 bugreport.txt
Cannot run PlanetSide 2 on x64 Fedora 17. Popuing up three similar error log
message with attached bugreport. Also attached debug.log is generated in Steam
install dir.
--
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=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.
https://bugs.winehq.org/show_bug.cgi?id=40639
Bug ID: 40639
Summary: Can't run a game with Wine
Product: Wine
Version: 1.9.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rmbeer2(a)gmail.com
Distribution: ---
Testing with GTA San Andreas.
Running direct with ./wine cause a halt and stooped game in the memory, i only
can run normaly if i execute ./wineboot with a active desktop.
Not show nothing in the log.
--
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=33492
Bug #: 33492
Summary: Yukon Trail installer fails to install its font
Product: Wine
Version: 1.5.29
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: Installer, win16
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Blocks: 10349
Classification: Unclassified
The installer will offer to let you install its custom font (optional, not
required). If you choose to, it then fails, saying:
=========
FATAL ERROR AT SCRIPT LINE 260
Cannot find section header
=========
if you open ~/.wine/drive_c/windows/win.ini, and add:
[fonts]
to the end, the font will install 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.
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.
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.
https://bugs.winehq.org/show_bug.cgi?id=44827
Bug ID: 44827
Summary: FL Studio: 32-bit/64-bit VST plugin bit bridging soft
locks the host
Product: Wine
Version: 3.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ajduck(a)outlook.com
Distribution: ---
Trying to bridge a 32-bit VST plugin in FL Studio 64-bit, or bridge a 64-bit
VST plugin in FL Studio 32-bit, leads to this being outputted:
003c:err:ntdll:RtlpWaitForCriticalSection section 0x1ac6028 "?" wait timed out
in thread 003c, blocked by 002a, retrying (60 sec)
And the DAW soft locks with a loading cursor as it blocks the UI until the
plugin's loaded, forever trying to bridge the plugin.
(By "soft lock", I mean that FL Studio itself is still responsive, but you're
completely blocked from doing anything and the only way to get out of it is to
kill the process.)
======
Steps to reproduce:
1. Download and install FL Studio 12 Demo:
https://support.image-line.com/redirect/FLStudio_Installer_Google
The demo and the full version are the same executable.
You will need the Arial font or any ttf named as arial.ttf in
"C:/Windows/fonts/". If you have Winetricks just run "winetricks corefonts"
(you will need the cabextract package).
2. Download any 32-bit or 64-bit VST to test.
This is the one I tried, a 32-bit plugin (http://veg.by/en/projects/syxg50/).
The plugin itself is working perfectly. You can use any VST you want, as long
as you know whether it's 32-bit or 64-bit.
Put the dll file in "~/.wineprefix/drive_c/Program Files
(x86)/Steinberg/VstPlugins/".
3. Open the FL Studio version which DOESN'T match the instruction set of the
VST you're using. If you're using a 32-bit VST plugin, open FL Studio 12
(64-bit). If you're using a 64-bit VST plugin, open FL Studio 12 (32-bit). (If
you're using the VST I linked to, open FL Studio 12 (64-bit))
4. When FL Studio is launched for the first time, a featured project file is
automatically loaded. Click "File" in the top left corner and then "New" to
create an empty project.
5. Click "Options" > "Manage Plugins"
6. Click the "Start scan" button with "Verify plugins" enabled (make sure the
light is red). Let it scan for plugins.
7. Close the window, click "Add", and then "More plugins..." (under System)
8. Find and select "S-YXG50" (or if you used another VST, pick that).
9. Because the instruction set of the VST plugin doesn't match the host
program's (FL Studio), FL Studio will try to run the VST plugin under a
"bridge" (which uses ilbridge.exe, the bridging program installed as part of FL
Studio). However, the plugin never loads. The UI blocks any interaction while
plugins are being loaded so FL Studio is effectively soft locked.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=39013
Bug ID: 39013
Summary: Cannot change the location of the folder put in
/tmp/.wine-uid
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sstewartgallus00(a)mylangara.bc.ca
Distribution: ---
I want to set /tmp on my machine to be only readable and writeable by root and
I cannot use Wine with that configuration unless I can change that folder.
Also, only allowing the static folder in /tmp opens up a denial-of-service
attack against other users. A user can be a jerk and create /tmp/.wine-uid
directories to block other users.
--
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.