https://bugs.winehq.org/show_bug.cgi?id=46709
Bug ID: 46709
Summary: VarFormatCurrency doesn't handle an already formatted
string.
Product: Wine
Version: 4.2
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: oleaut32
Assignee: wine-bugs(a)winehq.org
Reporter: leslie_alistair(a)hotmail.com
Distribution: ---
Split off from 46442.
When VarFormatCurrency is passed an already formatted string, eg $9.0, it
returns an error instead of a string.
--
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=30062
Bug #: 30062
Summary: Deer Hunter demo: unable to start a new game (map view
unusable)
Product: Wine
Version: 1.3.18
Platform: x86
URL: http://www.fileplanet.com/28105/20000/fileinfo/Deer-Hu
nter
OS/Version: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gyebro69(a)gmail.com
CC: hverbeet(a)gmail.com
Classification: Unclassified
Regression SHA1: 926dfc5c49dde8401732a943c1055ba6631bcc5c
Created attachment 39166
--> http://bugs.winehq.org/attachment.cgi?id=39166
terminal output
This bug applies to the first Deer Hunter game in the series, released in 1997.
The game requires Win98 mode to start, and I had to set up virtual desktop
mode.
Steps to reproduce the problem with the demo:
1. Install the demo.
2. Set Windows version to Win98 before launching the game. Start the demo with
DhDemo.exe.
3. In the menu click on <Start New Hunt>, <OK>, <Hunt Here>. Here comes the
problem:
- a map is shown with a crosshair in it. You should be able to change locations
by left-clicking anywhere on the map. This doesn't work: the mouse pointer
disappears when you click on the map.
- the lower part of the screen is missing (showing only a black bar). This is
where certain buttons are located (Hunt, Quit, Help).
- although the buttons at the bottom are missing, you can start a game by
pressing <Enter>. A loading screen is displayed, but the game never loads, it
is freezing with the loading screen.
The problem appeared in 1.3.18 and is still present in 1.4-rc6.
The result of the regression test:
926dfc5c49dde8401732a943c1055ba6631bcc5c is the first bad commit
commit 926dfc5c49dde8401732a943c1055ba6631bcc5c
Author: Henri Verbeet <hverbeet(a)codeweavers.com>
Date: Tue Apr 12 18:28:41 2011 +0200
wined3d: Merge the IWineD3DSwapChain::SetDestWindowOverride()
implementations.
:040000 040000 12437b369aadbbeb6de72ed285f2ced64a7c26b1
025f1e0265b689bf82dd954e1ceb33216af77386 M dlls
Fedora 16
Nvidia 250 / driver 290.10
X.Org X Server 1.11.4
--
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=47915
Bug ID: 47915
Summary: League of Legends 9.20: Crash after champ select
Product: Wine
Version: 4.17
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mail+wine(a)m-reimer.de
Distribution: ---
Created attachment 65411
--> https://bugs.winehq.org/attachment.cgi?id=65411
Crash dump
Since updating to LoL 9.20 there is a new "crash after champ select" issue.
Probably this is the anticheat, again.
Would be great if some experienced developer could have a look at this.
I've attached my crash dump but the bug is really easy to reproduce. Just try
to open the "practice tool". Will crash immediately when the switch from client
to actual game should happen.
Maybe Andrew Wesie could have a look at this one? He did an remarkably great
job with fixing such things in the past!
--
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=50117
Bug ID: 50117
Summary: winedbg --gdb doesn't work
Product: Wine
Version: 5.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winedbg
Assignee: wine-bugs(a)winehq.org
Reporter: tomsod-m(a)ya.ru
Distribution: ---
After updating wine, winedbg's GDB mode stopped working for me. Instead of
attaching to a program, it starts the program, then terminates itself. The
latest unaffected version is 5.17; 5.18 to 5.21 all have this bug. The default
mode of winedbg (without --gdb) works as expected, however.
Steps to reproduce: run e.g. "winedbg --gdb notepad.exe".
Expected behavior: winedbg stops at notepad's entry point and prompts for
commands.
Observed behavior: winedbg quits almost immediately, notepad runs freely.
--
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=50594
Bug ID: 50594
Summary: Surge 1.6.6 VST works but shows only blank window
Product: Wine
Version: 6.1
Hardware: x86-64
URL: https://github.com/surge-synthesizer/releases/releases
/download/1.6.6/Surge-1.6.6-Setup.exe
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: and3md(a)gmail.com
Distribution: ---
Created attachment 69279
--> https://bugs.winehq.org/attachment.cgi?id=69279
Wine log
Steps to reproduce:
1. Install LMMS -
https://github.com/LMMS/lmms/releases/download/v1.2.1/lmms-1.2.1-win64.exe
2. Download and install Surge -
https://github.com/surge-synthesizer/releases/releases/download/1.6.6/Surge…
3. Open LMMS
4. Change plugin embedding in Settings to No embedding (this is workaround of
https://bugs.winehq.org/show_bug.cgi?id=48527).
5. Restart LMMS
4. Open the instruments plugins tab
5. Drag VeSTige to Song Editor window
6. Click Vestige in Song editor to show Vestige GUI
7. In Vestige Window click green folder icon
8. Go to Surge.dll
9. Click Open
10. Empty window appears
On Windows 10 works ok.
There are in log a lot of lines like:
017c:fixme:dwrite:dwritefactory_CreateMonitorRenderingParams (0x1): monitor
setting ignored
0188:fixme:d3d:state_linepattern_w Setting line patterns is not supported in
OpenGL core contexts.
0188:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader
#3:
0188:fixme:d3d_shader:print_glsl_info_log Vertex info
0188:fixme:d3d_shader:print_glsl_info_log -----------
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[0].zw" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[2].zw" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[3].zw" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[5]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[6]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[7]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[8]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[9]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[10]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[11]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[12]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[13]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[14]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050:
"vs_out[15]" might be used before being initialized
0188:fixme:d3d_shader:print_glsl_info_log
0188:fixme:d3d_shader:print_glsl_info_log Fragment info
0188:fixme:d3d_shader:print_glsl_info_log -------------
0188:fixme:d3d_shader:print_glsl_info_log 0(37) : warning C7050: "R1.yzw"
might be used before being initialized
--
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=49905
Bug ID: 49905
Summary: VbsEdit runs wscript.exe with unsupported switches /d
and /u
Product: Wine
Version: 5.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wscript
Assignee: wine-bugs(a)winehq.org
Reporter: sloper42(a)yahoo.com
Distribution: ---
Created attachment 68266
--> https://bugs.winehq.org/attachment.cgi?id=68266
patch for wscript
In VbsEdit version 9.2139 from https://www.vbsedit.com/, when choosing "Start
Debugging with wscript", wscript.exe is called with unsupported options /d
(debug) and /u (unicode).
Therefore wscripts bail out and script is not executed.
Solution is to ignore these options.
--
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=48043
Bug ID: 48043
Summary: user32:dce has a pair of random failures
Product: Wine
Version: unspecified
Hardware: x86
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Created attachment 65584
--> https://bugs.winehq.org/attachment.cgi?id=65584
user32:dce: Loop over the test_destroyed_window() for 2 random failures.
user32:dce has a pair of random failures in test_destroyed_window():
dce.c:648: Test failed: wrong window
dce.c:658: Test failed: DC for destroyed window not reused
One either gets the first one alone or both together.
See https://test.winehq.org/data/tests/user32:dce.html
These happen at random on a wide range of Windows versions: wxppro, w2003std,
w2008s64, fg-win7u64-*, w1064v1507, w1064v1607.
On Windows 10 the same type of error sometimes happens in test_dc_attributes()
on line 127 which is another "wrong window\n" check.
The attached patch loops over test_destroyed_window() which is sufficient to
make these failures systematic. This can hopefully help debug the issue and
make sure these are fixed.
--
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=15781
Summary: Can't run AllInOne-Office 5
Product: Wine
Version: 1.1.7
Platform: Other
URL: http://www.allinone-office.de/
OS/Version: other
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
A user asked for this package here:
http://www.linux-forum.de/warenwirtschaft-allione-5-0-a-20117.html
so I tried installing it.
First, you have to set your language to German, e.g.
LANG=DE_de.UTF-8
or it commplains about a language mismatch.
Then, you have to set your Windows version to NT 4 with winecfg, else
it complains that it needs Windows NT 4 or higher.
Then it installs. The font in the installer is almost too tiny
to read, even with corefonts installed.
It first silently installs the Access 2002 runtime
libraries and Jet 40, and those subinstallers aren't particularly
happy; they both end with
err:msi:ITERATE_Actions Execution halted, action L"InstallFinalize" returned
1627
but the main installer continues blindly.
It asks if you want to keep the existing version of some wine dll; I said yes.
It installs a menu item showing that the way to run the app is
wine "C:\\Program Files\\Common Files\\Microsoft Shared\\Access
Runtime\\Office10\\MSAccess.exe" /Runtime "C:\\Program
Files\\AllInOne-Office\\AllInOne-Office.mde"
but that fails with file not found... maybe because of the
access runtime installation problem?
--
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=50224
Bug ID: 50224
Summary: Grand Theft Auto 4: Crashes when starting the game
Product: Wine
Version: 5.8
Hardware: x86-64
OS: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sterum77(a)gmail.com
Created attachment 68729
--> https://bugs.winehq.org/attachment.cgi?id=68729
backtrace of GTA IV
After starting the game it immediately crashes and generates the attached
output.
As with wine version 4.X the game runs fine, so it looks like something is
broken in version 5.X.
--
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=47180
Bug ID: 47180
Summary: Nocturne unhandled exception bug on startup
Product: Wine
Version: 4.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jagsoul87(a)gmail.com
Distribution: ---
Created attachment 64434
--> https://bugs.winehq.org/attachment.cgi?id=64434
Unhandled exception register dump/log file
When trying to run Nocturne the game crashes displaying an error message, when
I click on "show details" it shows the following message: Unhandled exception:
page fault on read access to 0x00000000 in 32-bit code. The following register
dump and full log file it's attached to this bug report.
--
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.