http://bugs.winehq.org/show_bug.cgi?id=32840
Bug #: 32840
Summary: Mouse input regression caused by changes in
GetTickCount64
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dinput
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jimportal(a)gmail.com
Classification: Unclassified
Since fa9a883dbbd49117c2e53f5b3ea8cd49397bf520 (kernel32: Use the monotonic
counter in GetTickCount64.), mouse input behaves erratically in World of
Warcraft when using the mouse to turn or change camera view angle. The mouse
behaves fine when the mouse cursor is displayed for clicking buttons.
This also causes problems in Prey and Painkiller.
--
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=32904
Bug #: 32904
Summary: Opera installer needs GetExplicitEntriesFromAclW
Product: Wine
Version: 1.5.23
Platform: x86
URL: http://www.opera.com/browser/download/?os=windows&ver=
12.14&local=y
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: spoon0042(a)hotmail.com
CC: ehoover(a)mines.edu
Classification: Unclassified
Created attachment 43456
--> http://bugs.winehq.org/attachment.cgi?id=43456
opera installer console output
(I assume that's the problem anyway, I was asked to file a new bug over at
32360, as Erich Hoover said "What appears to be
going on here is that the default ACL for registry keys is not accepted by the
Opera installer." Anwyay, here's what I posted there...)
It doesn't crash now, at least. What does happen is the progress bar gets most
of the way done and then pops up a bunch of registry error dialogs (giving the
options "Ignore" and "Close", eventually one only allows "Close" then deletes
everything), here's the text of the first:
Failed to modify registry
Software\Classes\Opera{Product}.HTML\FriendlyTypeName. Error code: 39
Each comes with this corresponding error on the console:
fixme:advapi:GetExplicitEntriesFromAclW (nil) 0x33e2a8 0x33e2b0
--
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=32919
Bug #: 32919
Summary: Yarmap causes Unhandled exception: page fault on read
access in 32 bit code
Product: Wine
Version: 1.5.23
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: v_mil(a)ukr.net
Classification: Unclassified
Created attachment 43478
--> http://bugs.winehq.org/attachment.cgi?id=43478
Backtrace when the program crashes
In previous Wine versions Yarmap did not start anyway.
In this versions Yarmap starts, works normally and causes page fault after
multiple loops of clicking on a bus stop or building, zoom (by mouse wheel),
movement (by pressing left or right mouse button and move) and zoom.
How to reproduce:
1. Download and install Yarmap (Russian only) from
http://kiev.yarmap.ua/download/35
or
http://kiev.yarmap.ua/download and press red button "Скачать установщик" near
to the Windows logo.
2. Open it
3. Press button "Запустить" allocated in middle bottom and wait for the map
4. Rotate mouse wheel up to zoom in until buildings and bus stops are shown
5. Press any building or bus stop. The left panel may be updated
6. Rotate mouse wheel down to zoom out
7. Click and drag the map by left or right mouse button
8. Repeat from step 4
After 2...3 repeats the program shall crash.
--
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=32951
Bug #: 32951
Summary: Warlords III demo crashes on exit
Product: Wine
Version: 1.5.23
Platform: x86
URL: http://download.cnet.com/Warlords-III-demo/3000-2119_4
-10010589.html
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: djelinski1(a)gmail.com
Classification: Unclassified
Created attachment 43520
--> http://bugs.winehq.org/attachment.cgi?id=43520
Wine output, steps as described
To reproduce:
- install game
- start WAR3DEMO.EXE
- select Single player
- from the menu select Quit
Other than that the game works fine.
The crash backtrace is sometimes different, so there's probably a memory
corruption somewhere. The "expect problems" message is present each time.
--
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=33014
Bug #: 33014
Summary: Steam enters into an infinite update loop upon opening
with wine 1.4.1
Product: Wine
Version: 1.4.1
Platform: x86
OS/Version: Mac OS X
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gypsyotoko(a)i.softbank.jp
Classification: Unclassified
Created attachment 43634
--> http://bugs.winehq.org/attachment.cgi?id=43634
Console output displayed during infinite update loop.
Upon opening steam the application will download the latest update, unpack and
install, then display the following message before repeating the process
without end:
"Failed to remove temporary unzip folder, conti"
Confirmed on the following hardware:
OS: OS X 10.8.2
Hardware: MacBook 5,1
CPU: Intel Core 2 Duo 2.4 Ghz
Graphics: NVIDIA GeForce 9400M
--
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=33016
Bug #: 33016
Summary: Wine recognizes Geforce GT 630 as Geforce 8800 GTX
Product: Wine
Version: 1.5.24
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: otaku(a)rambler.ru
Classification: Unclassified
Tested on last Perfect World, Ubuntu 12.10 and Nvidia driver 313.18
--
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=33083
Bug #: 33083
Summary: Magic: The Gathering Online Wide Beta installer
crashes with X error
Product: Wine
Version: 1.5.24
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: admiral.hackbar(a)gmail.com
Classification: Unclassified
Magic: The Gathering Online Wide Beta installer crashes with:
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 1 (X_CreateWindow)
Serial number of failed request: 348
Current serial number in output stream: 352
Let me know what other logs are needed.
The installer is freely downloadable (you don't need any account to install)
at:
http://www.wizards.com/magic/digital/magiconline.aspx?x=mtg/digital/magicon…
. Pick "Wide Open Beta Version"
The site says it needs .NET 4.0, so I ran installed dotnet40 with winetricks.
Ubuntu 64-bit, with WINEARCH=win32, using version 1.5.24 from the wine PPA.
Using Ivy Bridge graphics. With older Intel graphics, a similar bug #32471
happens. I think this bug is different though.
--
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=33213
Bug #: 33213
Summary: Wine crashes if printing images
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ironeman(a)tiscali.it
Classification: Unclassified
Created attachment 43939
--> http://bugs.winehq.org/attachment.cgi?id=43939
The sample application.
This bug is similar to "Bug 16585 - Printing document with images crashes wine"
that was closed on 2009-01-30.
I am using 16-bit Clipper/xBase programs. When printing SOME images,
wine-1.5.25 crashes.
I wrote the attached sample program that prints a very simple report (after a
preview).
The report is composed of:
1) a string ("TEST")
2) a bmp image from file test1.bmp
3) an optional bmp image from file test2.bmp
The program asks if you want to print test2.bmp. In Windows Xp, all is ok, but,
in Wine, if "No" is selected the preview appears as expected (including
test1.bmp image) else Wine crashes.
I tried a lot of images that crash. I suppose that the problem is the size of
bmp file.
The attached zip file contains:
1) test_pr.EXE: the executable sample. Run it! It requires that all the files
are into the working directory.
2) backtrace.txt: the memory dump created after "WINEDEBUG=+psdrv"
3) test_pr.PRG: the source code (xBase language)
4) PREVIEW.DLL: a needed dll for the exe
5) TEST1.bmp: the first sample image (correctly printed)
6) test2.bmp: the second sample image (crashes)
Best 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=33283
Bug #: 33283
Summary: Configuration of WM_NAME is delayed for virtual
desktop
Product: Wine
Version: 1.5.26
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: me(a)mkaito.com
Classification: Unclassified
Many window managers rely on X properties for window management. For example,
it is very common to use WM_NAME and WM_CLASS to apply management rules. This
feature depends on these properties being set when a new client is spawned.
When running an application inside a virtual desktop, such as with `wine
explorer /desktop=whatever,1920x1080 "C://Program Files/Whatever/Foo.exe"`, we
end up with a desktop where WM_NAME = "whatever - Wine Desktop".
However, the configuration of this property is delayed, causing wine desktops
to be handled incorrectly, since X properties are only checked upon client
creation.
--
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=33331
Bug #: 33331
Summary: When DLL receives PROCESS_DETACH notification when a
process is exiting all the threads should be already
terminated
Product: Wine
Version: 1.5.27
Platform: x86-64
OS/Version: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dmitry(a)baikal.ru
Classification: Unclassified
Created attachment 44083
--> http://bugs.winehq.org/attachment.cgi?id=44083
source and binary for the test
While debugging the problem described in
http://www.winehq.org/pipermail/wine-patches/2013-March/123127.html
(libiomp5md.dll waits until all the tracked threads terminate and doesn't
return control out of its PROCESS_DETACH handler when process is going to exit)
I decided to create a test which examines what's supposed to happen when
static (loaded implicitly as a part of PE imports) and dynamic (loaded
explicitly by LoadLibrary) DLLs create threads along with threads created
by main exe.
To make long story short: main difference between Windows and Wine is that Wine
doesn't terminate threads before calling PROCESS_DETACH for each loaded DLL.
Here are the snippets from results I see under Windows 7 (both 32 and 64 bit
builds behave same way) and Wine:
Win7:
...
main: call ExitProcess(0)
dynamic: 72FB0000, DLL_PROCESS_DETACH, 00000001
dynamic: GetExitCodeThread(0) => 1,0
dynamic: GetExitCodeThread(1) => 1,0
dynamic: GetExitCodeThread(2) => 1,0
static: 72FC0000, DLL_PROCESS_DETACH, 00000001
static: GetExitCodeThread(0) => 1,0
static: GetExitCodeThread(1) => 1,0
static: GetExitCodeThread(2) => 1,0
=====================================================
Wine:
...
main: call ExitProcess(0)
dynamic: 00330000, DLL_PROCESS_DETACH, 00000001
dynamic: GetExitCodeThread(0) => 1,259
dynamic: GetExitCodeThread(1) => 1,259
dynamic: GetExitCodeThread(2) => 1,259
static: 10000000, DLL_PROCESS_DETACH, 00000001
static: GetExitCodeThread(0) => 1,259
static: GetExitCodeThread(1) => 1,259
static: GetExitCodeThread(2) => 1,259
I.e. libiomp5md.dll when it receives PROCESS_DETACH notification at process
exit time shoudn't get STILL_ACTIVE (259) return value from GetExitCodeThread.
--
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.