https://bugs.winehq.org/show_bug.cgi?id=46295
Bug ID: 46295
Summary: Some programs have problems with sound, easier to
notice when using alsa
Product: Wine
Version: 4.0-rc1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: leozinho29_eu(a)hotmail.com
Distribution: ---
Created attachment 63019
--> https://bugs.winehq.org/attachment.cgi?id=63019
Winamp log with WINEDEBUG=+dsound
Some programs as Winamp and DiRT 3 Complete Edition have problems with sound,
where the sound skips sometimes.
Here is a YouTube video showing the problem happening on DiRT 3 Complete
Edition: https://www.youtube.com/watch?v=iowAAAWcQlE
Here is a video showing the problem with Winamp:
https://cdn.discordapp.com/attachments/457747189616214019/50830906937599590…
The attached file has the log with WINEDEBUG=+dsound set when using Winamp.
--
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=31491
Bug #: 31491
Summary: Trading software eror
Product: Wine
Version: unspecified
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: balajiks2k(a)gmail.com
Classification: Unclassified
Created attachment 41395
--> http://bugs.winehq.org/attachment.cgi?id=41395
Error log for Nest Trader Application
Nest Trader is a software that works in Windows OS, when installed using Wine,
it gives error and exits. The back trace file is attached herewith.
--
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=7984
Nikolay Sivov <bunglehead(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |ABANDONED
Status|NEEDINFO |RESOLVED
--- Comment #21 from Nikolay Sivov <bunglehead(a)gmail.com> ---
This should be fixed with 927956db67544d84da6dc27922bb64ebd31f64aa. See bug
30103 for test application. I'm going to mark this abandoned, client no longer
works, and is stuck on Checking versions stage.
--
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=46270
Bug ID: 46270
Summary: STGMEDIUM_UserFree unconditional releases a HGLOBAL
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ole32
Assignee: wine-bugs(a)winehq.org
Reporter: mark.jansen(a)reactos.org
Distribution: ---
Created attachment 62980
--> https://bugs.winehq.org/attachment.cgi?id=62980
ReactOS +ole capture
When an STGMEDIUM is marshalled locally (just copied),
the HGLOBAL is actually deleted by the stub.
This leaves the recipient of the STGMEDIUM with a head object.
Before 5293cb71838bba86961f62e2317f532c9812db0c this was not a problem, because
an HGLOBAL was always treated as 'remote'.
Thanks to Zebediah Figura for figuring out the problem based on my very
incomplete description :)
--
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=23282
Summary: SpeQ: Wrong coded linefeed
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: samoth(a)gmx.de
Since the 1.1.4x releases the editor in SpeQ Mathematics doesn't work right
anymore. Normally if entering an expression an hitting the return key, SpeQ
prints the result. This works allright with the first wine-version I used
(1.1.38 ?).
But now hitting the return key results in additional unvisible characters and
nothing happens until I do a sheet-calculation. Then SpeQ cannot calculate the
expression due to these unvisible characters. Maybe it is the order of coding a
linefeed via 0d 0a.
SpeQ ist available for free at http://www.speqmath.com
--
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=43178
Bug ID: 43178
Summary: Prototype regression
Product: Wine
Version: 2.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: byi5000(a)gmail.com
Distribution: ---
Created attachment 58445
--> https://bugs.winehq.org/attachment.cgi?id=58445
Backtrace with CSMT
The Game Prototype
(https://appdb.winehq.org/objectManager.php?sClass=version&iId=31948) was
working back in Wine-Staging-2.8 and fails to start up in 2.9 and 2.10
Since the logs with and without CSMT differ a bit, i will attach both
--
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=25734
Summary: Magic: The Gathering Battlegrounds trial hangs upon
startup
Product: Wine
Version: 1.3.11
Platform: x86-64
URL: http://www.fileplanet.com/134762/130000/fileinfo/Magic
:-The-Gathering---Battlegrounds-Trial
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: trygve.vea(a)gmail.com
Created an attachment (id=32781)
--> (http://bugs.winehq.org/attachment.cgi?id=32781)
terminal output, and WINEDEBUG=+seh
Testing old bugs to see if they still occur. Were testing bug 18616, and is not
able to start the game.
The application shows a splash screen, followed by a window named "Browser"
with no content. I am able to close sayd window, and the application will
terminate.
A brief discussion on irc stated that this bug then blocks bug 18616.
Willing to test patches / assist debugging further.
--
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=19184
Summary: File copying fails during installation of Mordor
Product: Wine
Version: 1.1.25
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: perchrh-wine(a)pvv.org
When installing the game, file copying fails.
Files are extracted to the temp dir (C:\MDRTMP.TM~) and copied to the
installation directory (C:\MORDOR).
A popup shows this error message:
"Mordor 1.1 is not properly installed. Please re-run setup at a later time to
install Mordor 1.1 properly."
Debug logs (file and file+relay channels) attached.
The problem seems to occur when copying SHOCK.WAV, or right after that.
The file is found in the installation directory after the error shows.
The contents of the installation diretory and the temp directory at time of the
error is attached.
To reproduce:
Download demo, unzip MORDOR1A.zip and MORDOR1B.zip, run setup.exe and check
(only) "Install MORDOR" and "Install WAVE files".
Optionally, first install MORDOR only (completes without error), then re-run
setup and install the WAVE files.
--
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=39736
Bug ID: 39736
Summary: prototype 2 work on 1.7.23 and older, but not work in
new engines
Product: Wine
Version: 1.7.55
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dmitrybarynov(a)gmail.com
Created attachment 52995
--> https://bugs.winehq.org/attachment.cgi?id=52995
saved crash information
Hi.
When I use wine 1.7.23 or older down to 1.5.24 Prototype 2 fine work, but if I
choose new version from 1.7.24 to 1.7.55, I have crash game.
Log-file when game work, engine 1.7.23:
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:wbemprox:client_security_SetBlanket 0x4400a3ac, 0x160340, 10, 0, (null),
3, 3, 0x0, 0x00000000
fixme:wbemprox:client_security_Release 0x4400a3ac
fixme:win:EnumDisplayDevicesW ((null),0,0x33c94c,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x33cb3c,0x00000000), stub!
fixme:d3d:debug_d3dformat Unrecognized 0x42563252 (as fourcc: R2VB)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x42563252) in the
format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the
format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the
format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the
format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the
format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the
format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the
format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the
format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the
format lookup table
fixme:wbemprox:client_security_SetBlanket 0x4400a3ac, 0x237b1110, 10, 0,
(null), 3, 3, 0x0, 0x00000000
fixme:wbemprox:client_security_Release 0x4400a3ac
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:wbemprox:client_security_SetBlanket 0x4400a3ac, 0x237b1be8, 10, 0,
(null), 3, 3, 0x0, 0x00000000
fixme:wbemprox:client_security_Release 0x4400a3ac
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the
format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the
format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the
format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the
format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the
format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the
format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the
format lookup table
fixme:msvcrt:__clean_type_info_names_internal (0x1100a2d4) stub
Log-file when game crash, engine 1.7.24 and higher(1.7.55):
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:wbemprox:client_security_SetBlanket 0x4400b3ac, 0x160360, 10, 0, (null),
3, 3, 0x0, 0x00000000
fixme:wbemprox:client_security_Release 0x4400b3ac
fixme:win:EnumDisplayDevicesW ((null),0,0x33c94c,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x33cb3c,0x00000000), stub!
fixme:d3d:debug_d3dformat Unrecognized 0x42563252 (as fourcc: R2VB)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x42563252) in the
format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the
format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the
format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the
format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the
format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24)
WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the
format lookup table
wine: Unhandled page fault on read access to 0x00000000 at address 0x109a3165
(thread 0023), starting debugger...
I hope this helps.
--
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.