https://bugs.winehq.org/show_bug.cgi?id=50424
Bug ID: 50424
Summary: std::mutex crashes on creation
Product: Wine
Version: 4.12.1
Hardware: arm
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: msvcp
Assignee: wine-bugs(a)winehq.org
Reporter: david.paradis(a)us.abb.com
Distribution: ---
Created attachment 69041
--> https://bugs.winehq.org/attachment.cgi?id=69041
Test Project File
I have spent the better half of the last month tracking down a crash in my
application related to the creation of the std::mutex object in my code. After
putting many debugging messages into the Wine code I have finally found what
the issue is. Here is what I have found:
1) In the dlls/msvcp90/msvcp_main.c:init_cxx_funcs() the code is calling
GetProcAddress() for the critical_section methods for ctor, dtor, lock, ... but
never checks to see if we found a valid address for the functions. Later on in
the _Mtx_init_in_situ() a call is made to the critical section ctor and throws
null pointer exceptions because the function pointer is null.
2) In the dlls/concrt140/concrt140.spec there are NO definitions for any ARM
architecture method exports. In the dlls/msvcp90/msvcp90.spec there are
definitions but they are missing in concrt library.
After playing with the concrt140.spec file I was able add the 5 critical
section method exports to the file and was able to verify that I can now create
a std::mutex object and call lock, unlock and other methods on it successfully.
At this point I have no idea how many other ARM methods are missing from the
concrt140.spec list, but the distribution package does not have ANY ARM
definitions in that file.
I am attaching a very simple test CPP file that I was using to verify that the
code is now working for my usage but not completely fixed. With the test code
and the shipping source code you will not get past the point of seeing the
second printf statement after creating the test class, it will crash on the
"test t1;" line.
Thank you
--
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=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.
https://bugs.winehq.org/show_bug.cgi?id=50366
Bug ID: 50366
Summary: Starcraft Remastered unable to create local LAN
multiplayer game.
Product: Wine-staging
Version: 6.0-rc3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: darinsmiller(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
When trying to create a LAN game in Starcraft Remastered:
1st attempt: Message pop says "Failed to advertise the game. (Error 5:12)."
2nd attempt: The "Creating game" pop-up window displays indefinitely and no
game is ever created.
Lutris with wine version 5.7.10-x86_64 is able to create LAN games in Starcraft
Remastered.
Operating System: Kubuntu 20.10
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.14.2
Kernel Version: 5.8.0-33-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4771 CPU @ 3.50GHz
Memory: 15.6 GiB of RAM
Graphics Processor: GeForce GTX 1080/PCIe/SSE2
NVidia Driver: 455.45.01
--
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=41253
Bug ID: 41253
Summary: GZDoom Builder : Unable to make a new project
Product: Wine
Version: 1.9.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: janusczpawlacz(a)protonmail.ch
Distribution: ---
Created attachment 55547
--> https://bugs.winehq.org/attachment.cgi?id=55547
Terminal error outpot of Builder.exe
So every time I try to open a new project or opening a existing map for editing
a error appears and it just plain crashes.
Error Message:
Fatal Windows Forms error occured: CompilationException While [unreadable]
Fatal Windows Forms Error
http://devbuilds.drdteam.org/doombuilder2-gzdb/GZDoom%20Builder%20R2364%20I…
sha1sum: aa65a19b1275deb09680f4227f81218d27308422
Distribution: Linux Mint 18 Mate X86_64 (64bit)
--
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=46320
Bug ID: 46320
Summary: Kindle don't get installed: abnormal program
temrination
Product: Wine
Version: 4.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: raffamaiden(a)gmail.com
Distribution: ---
Created attachment 63054
--> https://bugs.winehq.org/attachment.cgi?id=63054
command line log file + screenshot
Kindle for PC version 1.24.51068 don't even get installed. After the installer
showing up the dialog in which it says it is decompressing the files, after the
dialog in which it says it is copying (I presume?) the files, an error message
shows up "abnormal program termination"
I attach log and screenshot
--
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=48094
Bug ID: 48094
Summary: Simplify debugging test timeouts
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: testcases
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
When a Wine test times out one has to manually add traces to figure out where
it gets stuck, or what the slow parts are. This is all the more difficult when
the timeout is random and happens on a TestBot VM.
I propose to leverage the ok() calls to simplify getting timing information on
the tests.
* Recognize the $WINETEST_TIME environment variable and, if it is set, add the
elapsed time since the test started to the trace() and ok() messages.
* Ideally this elapsed time would have sub-second precision for those cases
where it's more an issue of a long loop being slow. How many decimals to print
is a matter of taste: one may be enough, three would feel quite standard if
maybe a bit overkill.
* Also when $WINETEST_TIME is set, an ok() call would be printed even if
successful when more than 1 second has elapsed since adding a message to the
report (trace/ok/skip). This should allow identifying which part of the test
causes trouble without altering its timing with thousands of traces.
* And when combined with $WINETEST_REPORT_SUCCESS of course every ok() call
would print the elapsed time.
Once the Wine side is implemented a few other components should be updated:
* The TestBot should allow setting $WINETEST_TIME when submitting a job.
* The TestBot should recognize the failure/todo/skip lines even with the extra
timing information.
* The TestBot could be modified to automatically rerun and set $WINETEST_TIME
if a test times out.
* The above may be particularly interesting for the full WineTest runs.
* We may also want to have test.winehq.org recognize the new failure/todo/skip
line formats.
--
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=34746
Bug #: 34746
Summary: Dino Crisis Demo doesn't play video sequences even
though Indeo codecs are installed
Product: Wine
Version: 1.7.4
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: winebugs140(a)gmail.com
Classification: Unclassified
Created attachment 46322
--> http://bugs.winehq.org/attachment.cgi?id=46322
Dino Crisis Demo Log without Indeo
Tested with:
Ubuntu 13.04, GeForce 9600M GS (NVIDIA driver 313)
Mac OS X 10.7.5, ATI HD 2600 Pro, Mac Driver/X11
--
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=31310
Bug #: 31310
Summary: TIE: Fighter: Collectors Edition -- Application
Crashes on Launch
Product: Wine
Version: 1.5.9
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: muleyryan(a)fastmail.fm
Classification: Unclassified
Wine running on 3.4.6-1-ARCH, with S3 Inc. SuperSavage IX/C SDR (rev 05)
xf86-video-savage and MESA savage drivers installed.
Using gdi as d3d renderer.
Application (TIE95.exe) crashes on launch
Backtrace here:
http://pastebin.com/mTX4bPet
Regression test pending.
--
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=49801
Bug ID: 49801
Summary: Freight Yard Manager: Crashes on start
Product: Wine
Version: 5.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: blue(a)blu3wolf.com
Distribution: ---
Created attachment 68114
--> https://bugs.winehq.org/attachment.cgi?id=68114
exception text
On running, Freight Yard Manager V5.9.17 (and all previous versions tested)
throws an unhandled System.InvalidProgramException: Invalid IL code. This does
not happen on any tested Windows system.
--
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=34734
Bug #: 34734
Summary: Dino Crisis 2 Demo website-like launcher doesn't run
the game (it doesn't respond to clicking)
Product: Wine
Version: 1.7.4
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: winebugs140(a)gmail.com
Classification: Unclassified
Created attachment 46311
--> http://bugs.winehq.org/attachment.cgi?id=46311
Dino Crisis 2 Demo Launcher Log
If you try to launch the game with it, nothing happens. Also, if you click on,
for example, 'Help' the content isn't displayed.
--
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=29011
Bug #: 29011
Summary: Non-standard serial baud rates are not reported
correctly.
Product: Wine
Version: 1.2.2
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jstutch(a)googlemail.com
Classification: Unclassified
Running VCDS-Lite 1.1 (connects to car diagnostics), with a FTDI-based
USB-Serial cable, when a non-standard baud rate is set on the port (10.4Kbps I
think), and the rate is read back by the program, wine reports
"err:comm:get_baud_rate unknown speed 1000", and returns an error to the
program. This breaks the serial port in the program until it is reset.
Replacing the offending lines in dlls/ntdll/serial.c: get_baud_rate with
"sbr->BaudRate = speed; break;", removes the error, and the program operates
correctly, although this may not be the right way to do this.
This was noted running Ubuntu Maverick (10.10), kernel 2.6.35-25-generic.
Running wine from the Maverick ubuntu package, rebuilt from package source to
correct the error as above.
Thanks,
JStutch
--
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=10204
Summary: Incorrectly raised FD_WRITE socket event
Product: Wine
Version: 0.9.48.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: wine-net
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: rraptorr(a)nails.eu.org
Created an attachment (id=8812)
--> (http://bugs.winehq.org/attachment.cgi?id=8812)
FD_WRITE event on socket test program
According to MSDN WSAEventSelect function description
(http://msdn2.microsoft.com/en-us/library/ms741576.aspx), FD_WRITE event should
be raised only once after: a) successful connection b) WSAEWOULDBLOCK error
while in nonblocking mode.
MSDN description:
"The FD_WRITE network event is handled slightly differently. An FD_WRITE
network event is recorded when a socket is first connected with
connect/WSAConnect or accepted with accept/WSAAccept, and then after a send
fails with WSAEWOULDBLOCK and buffer space becomes available. Therefore, an
application can assume that sends are possible starting from the first FD_WRITE
network event setting and lasting until a send returns WSAEWOULDBLOCK. After
such a failure the application will find out that sends are again possible when
an FD_WRITE network event is recorded and the associated event object is set."
Unfortunately, it seems that in Wine 0.9.48 (and a few earlier versions too)
this event is raised every time it is possible to write to the socket. I've
created a simple test program (FD_WRITE-test.c) that shows this problem. When
ran on Windows I get:
lNetworkEvents: 2
lNetworkEvents: 0
but when ran on Wine:
lNetworkEvents: 2
lNetworkEvents: 2
which means that FD_WRITE was raised twice and it shouldn't.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=12366
Summary: Acclaim Cashbook startup failure - recompile visual
basic
Product: Wine
Version: 0.9.58.
Platform: PC
URL: http://www.acclaim.co.nz/download.htm
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: pcpavnz(a)gmail.com
Install routine executes properly, but when trying to run the installed
program, an error message pops up with a message about having to recompile the
visual basic module. I suspect the message indicates the cashbook program is
what it thinks requires recompiling, not the environment it is running from,
but thought I'd submit it anyway because so many people want accounting
software packages to work inside Linux and wine is so close very now to getting
it right.
url provided in the report form is for the free 90 day trial download, which is
no different to a full version.
--
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=9504
Summary: Cannot close CMonthCalCtrl popup by clicking outside
popup
Product: Wine
Version: CVS/GIT
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: wine-user
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: peter(a)cendio.se
I have an application that uses a custom control: A wrapper that displays a
CMonthCalCtrl in a popup window. In Windows, it's possible to close the popup
by clicking outside the popup. With Wine, however, it is necessary to either
select a date or press Escape. The popup will also be closed if the user tries
to move the popup window (which has X11 WM decorations). When clicking outside
the popup with Wine, Wine generates a beep through X11 (I believe this happens
since a WM_SETCURSOR with HTERROR is generated).
A demo program is available as
http://www.cendio.se/~astrand/wine/6-close-popup/. Requires Visual C++ 2005
runtime libraries.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=14823
Summary: TSM Casin doesnt start after adding a contact
Product: Wine
Version: 1.1.0
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jacobidiego(a)gmail.com
TSM Casin is a software used mostly in Argentina to send SMS to cellphones
using the services provided by some webpages or sending e-mails.
The software as a development value is a crap, the developer have programmed it
with Visual Basic, have used ActiveX to attach IE to a tiny square so it can
display the Validation image, instead of just comunicating via http, have a
banner in the middle and a lot of cuestionable choices. But it is very usefull
and there isnt any linux similar tool.
It implements a custom Contact list, which is the one that is causing troubles,
everything else works fine, it can send SMS's correctly and IE-ActiveX doesnt
makes any issue.
When adding a contact and after filling all the information required (Name,
Cellphone Company, and Cellphone Number), and clicking start, the window should
close and the name should list on the contact list, but it doesnt close, then
clicking again on OK gives a warnning saying that the contact already exist,
and endeed it was added, so to close the wine i have to press Cancel.
Then i can use the contact list normally with any issue, but after closing TSM
and launching it again, it stays on an unuseful load-screen.
Then to get back TSM it is necessary to remove the created contacts, This is
done by deleting the registry key:
HKEY_USERS\S-1-5-4\Software\VB and VBA Program Settings\TSM\Agenda1.0
But copying the cellphones all the time is not a very good aproach.
The download is:
http://www.tsmcasin.com/ir/?id=16
and is freeware with only unharmful banners on it.
There is just 1 post on its forums asking for a linux version:
http://foro.tsmcasin.com/tsmforo/viewtopic.php?f=15&t=716&p=2374&hilit=gpl#…
The developer stays says that windows is standard and linux dont and that wont
be a version for linux.
I know that the best solution would be to develop a real and good open source
application to handle this stuff for all people under the world, but this wont
happen any time soon, and in the mean time, the this problem can be firing a
simple error easy to fix on wine.
Cheers.
--
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.