http://bugs.winehq.org/show_bug.cgi?id=27224
Summary: OnLive mouse is not detected
Product: Wine
Version: 1.3.20
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: david.caitens(a)gmail.com
Created an attachment (id=34788)
--> (http://bugs.winehq.org/attachment.cgi?id=34788)
OnLive Backtrace and terminal output
When loading up OnLive you get a error message "We have detected one of your
controllers may not be supported."
After that message you go through the login which loads up fine. Menus and
browsing around the application works just fine with the mouse but it's when
you load up a game that the problem shows up. The mouse doesn't seem to be
detected.
In the terminal output it comes up as Xinput
OS: Ubuntu 11.04
Nvidia driver: 270.41.06
--
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=18909
Summary: Avid media composer doesn't work
Product: Wine
Version: 1.1.23
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P1
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: wiccio84(a)yahoo.it
Created an attachment (id=21756)
--> (http://bugs.winehq.org/attachment.cgi?id=21756)
I tried to launch avid media composer 2.8
Wen i launch the application avid media composer wine show me the error report
in the attached file
--
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=29286
Bug #: 29286
Summary: Mouse wheel affects the control under the mouse
pointer, not the currently active one
Product: Wine
Version: 1.3.34
Platform: x86-64
URL: http://www.winuae.net/files/InstallWinUAE2330.exe
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: markk(a)clara.co.uk
Classification: Unclassified
Hi,
There is a difference between how Wine and Windows handle mouse wheel events.
In Windows, moving the mouse wheel affects the currently-selected control (the
last control clicked on), even if the pointer is over another control. In order
to change the control which is under the pointer, you need to click to activate
it first.
In Wine, moving the mouse wheel affects whatever control the pointer is over.
For example, try this:
- Click in a combo box to activate it. Move the mouse wheel and notice the
selected item changes.
- Move the pointer over another combo box. Without clicking the button, move
the wheel.
- The selected item of the combo box under the pointer changes. (On Windows,
the selected item of the active combo box would change instead.)
One program which shows this issue is WinUAE.
- Download and run InstallWinUAE2330.exe. Check the box to run the program at
the end.
- After clicking OK at the initial dialog box, the WinUAE Properties window
opens.
- In the tree view at the left side, click Sound. There are several combo
boxes. Move the pointer over one and click in it. Move pointer over the other
combo boxes and move the mouse wheel.
- Sliders are also affected. Click RAM in the tree view, then move the pointer
over the Chip or Slow sliders and move the mouse wheel.
Using native comctl32 didn't make a difference.
--
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=27789
Summary: Process Monitor from sysinternals can't load its
driver
Product: Wine
Version: 1.3.23
Platform: x86
OS/Version: Linux
Status: NEW
Severity: trivial
Priority: P2
Component: ntoskrnl
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
http://technet.microsoft.com/en-us/sysinternals/bb896645
fails to load its driver, so it can't do much.
Log:
fixme:process:SetProcessShutdownParameters (000001ff, 00000001): partial stub.
fixme:fltlib:FilterConnectCommunicationPort (L"\\ProcessMonitorPort", 0,
0x32f2dc, 4, (nil), 0x4fe484) stub
fixme:module:NtLoadDriver (0x32f0c8), stub!
trace:file:DeleteFileW L"C:\\windows\\system32\\Drivers\\PROCMON20.SYS"
That driver imports 128 symbols from ntoskrnl.exe, 6 from HAL.dll, and 20 from
FLTMGR.SYS.
Not something wine's going to support any time soon, I bet.
--
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=29360
Bug #: 29360
Summary: PES2012: crashes on startup
Product: Wine
Version: 1.3.35
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dsound
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mmdiego(a)mr.com.ar
Classification: Unclassified
Created attachment 37996
--> http://bugs.winehq.org/attachment.cgi?id=37996
pes2012 crash logfile
Just after executing the game, it crashes.
This should be a sound related issue as if I disable the sound (choosing
sound=disable in winetricks) the game starts OK.
I'm using the sound=alsa driver.
I tried disabling PulseAudio but the problem remains.
>From winecfg, the audio works OK.
Don't hesitate in asking me for more info needed to track the bug.
Thanks,
Diego M.
--
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=25190
Summary: Steam hardware survey crashes during hardware
detection
Product: Wine
Version: 1.3.7
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: scott(a)open-vote.org
This used to work at some point, however rather than a regression in Wine I
think it may be a case of the hardware survey getting more pervasive. These
two errors show in the terminal:
fixme:process:GetLogicalProcessorInformation ((nil),0x33fc84): stub
fixme:process:GetLogicalProcessorInformation (0x433c00,0x33fc84): stub
As a random guess, the crash may just be steam getting confused by the output
given by the stubs.
--
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=29254
Bug #: 29254
Summary: Alt key gets stuck when launching an X11 application
Product: Wine
Version: 1.3.34
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: winehq(a)tibit.com
Classification: Unclassified
When launching an X11 app from a Windows app using Alt + another key, and the
launched X11 app takes keyboard focus before the Alt key is released, the
Windows app is left thinking the Alt key is still pressed. Returning to the
Windows app using the mouse (or using the other Alt key + Tab) finds it in a
state where many keystrokes don't work properly.
Workaround: Once you figure out that the app is misbehaving because Wine thinks
a key is still down, this state can be cleared by tapping the
originally-pressed Alt key a couple of times. (But having to do this is
maddening.)
This is a regression. The problem doesn't exist in wine-stable (1.2.3).
This probably affects multiple applications, but I discovered it using the
Forte Agent mail reader. To reproduce:
1. Download Forte Agent free trial:
http://www.forteinc.com/agent/download.php
2. Configure it for receiving email.
3. Send yourself a few email messages with attachments that can be handled by
an X11 program launched from Wine. The easiest way to test is to just send a
html (mime multipart) message.
4. Open the email in Agent.
5. Control+I (or click Message -> Index) to show the message's mime parts.
6. Highlight the text/html item or attachment.
7. Alt+L to launch the attachment. Do not release the Alt until the X11 helper
application (e.g. Firefox) appears and takes focus. If Agent prompts you to
confirm before it launches the helper app, tell it not to confirm next time,
and do it again. The goal here is to see what happens when the helper app
opens before you let go of the Alt key.
8. Return to Agent's message list using the mouse (or using the other Alt key +
Tab.)
9. Try to navigate the message list with the Up & Down arrows. Notice that it
don't work, because Wine thinks Alt is still depressed.
10. Tap Alt twice to clear the stuck key.
The same problem shows up in other scenarios and with other keys. I chose to
demonstrate with this approach because it's the most familiar to me and because
a stuck Alt key has more obvious side-effects than some other keys.
To see the Control key get stuck, email yourself a message with a URL in it,
receive the message, highlight the URL, and Control + U to launch it in your
X11 browser. Return to Agent and notice that the Control key is now stuck
until you tap it again.
A git bisect reveals the offending commit:
bc4afb078677095468d4ee8f9a15c18cbb47bbbf is the first bad commit
commit bc4afb078677095468d4ee8f9a15c18cbb47bbbf
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Tue Mar 1 11:54:55 2011 +0100
server: Don't pass a thread id to send_hardware_message, determine it from
the window.
:040000 040000 4e7ac89f77a4ddc31fd947151c34d0acadc5dcc0
a3d857abf43a1eed9fcb6837ea006ac00d80a1a7 M dlls
:040000 040000 7247b4b93aca9c98394638ccd0c48a788133a8cd
45aed0fb1bc86b403af16666b3fa5963c2abaf7d M include
:040000 040000 469f40ddbdca23554a397c5122a78e09a13e2c75
f118b4fd2fb23ecbde100798c68b3221fe5ec2fc M server
--
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=25298
Summary: Divinity2 crashes
Product: Wine
Version: 1.3.7
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mcflow-forum(a)gmx.net
Created an attachment (id=32138)
--> (http://bugs.winehq.org/attachment.cgi?id=32138)
wine Divinity2.exe
In some situations the game will crash. For example at the initiation city near
the mage trainer there are a few boxes. If you destroy them, the game will
crash. Next is when you go back to the airship there will be a sequence and
after the dialog you can move where you want. If you turn around after that
dialog the game will also crash.
I tried various times and those crashes are 100% reproducable with version 1.03
of the game (original dvd, no crack!).
I attached the output from terminal to this post.
The last lines are:
err:heap:validate_block_pointer Heap 0x2b32000: bad flags 00000003 for in-use
arena 0x69fc9840
err:seh:setup_exception_record stack overflow 888 bytes in thread 000d eip
7bc73326 esp 09c50fb8 stack 0x9c50000-0x9c51000-0xa150000
err:seh:setup_exception_record stack overflow 976 bytes in thread 0009 eip
7bc3e61a esp 021c0f60 stack 0x21c0000-0x21c1000-0x26c0000
It reminds me to this bug which is marked as fixed though...
http://bugs.winehq.org/show_bug.cgi?id=10778
ArchLinux 64Bit
AMD II x3 435 @ 2,9 Ghz
4 GB Ram
Nvidia GTS 250 (260.19.21)
wine-1.3.7
--
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=29444
Bug #: 29444
Summary: League of legends crash.. libgcrypt error
Product: Wine
Version: 1.3.35
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: secur32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jatt159(a)gmail.com
Classification: Unclassified
ath.c:193: _gcry_ath_mutex_lock: asserzione "*lock == ((ath_mutex_t) 0)" non
riuscita.
--
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=26826
Summary: Mythos Open Beta: fails to detect cpu speed
Product: Wine
Version: 1.3.18
Platform: x86
URL: http://www.gamershell.com/news_115386.html
OS/Version: Linux
Status: NEW
Keywords: download
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Created an attachment (id=34177)
--> (http://bugs.winehq.org/attachment.cgi?id=34177)
screenshot
Terminal shows:
fixme:dwmapi:DwmEnableComposition (0) stub
fixme:system:SystemParametersInfoW Unimplemented action: 59 (SPI_SETSTICKYKEYS)
fixme:system:SystemParametersInfoW Unimplemented action: 53 (SPI_SETTOGGLEKEYS)
fixme:system:SystemParametersInfoW Unimplemented action: 51 (SPI_SETFILTERKEYS)
fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub!
fixme:wbemprox:wbem_locator_ConnectServer 0x139610, L"ROOT\\CIMV2", (null),
(null), (null), 0x00000000, (null), (nil), 0x32dd1c)
fixme:d3d9:D3DPERF_SetOptions (0x1) : stub
and a popup complains that my detected cpu speed is 0 Mhz. See screenshot.
--
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.