http://bugs.winehq.org/show_bug.cgi?id=24747
Summary: Wine crashes when running some functions of mp3vcr
Product: WineHQ Apps Database
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: appdb-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: home(a)wlawson.co.uk
I have been trying to run mp3vcr (http://www.mp3vcr.com/) in Wine and when I
either try to change its skins or load a radio station in come up with a
program error.
--
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=36900
Bug ID: 36900
Summary: Star Wars Galactic Battlegrounds Clone Campaigns: no
video (regression)
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: daniel.koszta(a)gmail.com
Created attachment 49017
--> http://bugs.winehq.org/attachment.cgi?id=49017
Git bisect log
When starting the game, the screen is black, only the cursor is visible. Moving
the cursor to the lower left corner (to the now invisible exit button) and
left-clicking exits the game, so it appears that buttons work. (Sometimes the
demo version froze on bad wine versions.) Sound works.
Wine version 1.4.1 works fine. Using git bisect between wine-1.4.1 and
wine-1.7.22 indicates commit 4c4552c (4c4552c5a1910a9d5adf8eccff0ac62d89ffe376)
as first bad commit. Bug not solved in the most recent commit cf50d5f
(cf50d5f70054c9759f4da89343c0ced62e76643f). Last good commit is b8569d2
(b8569d2f3006bbb14b973eca15a608f9575a0ebd).
Compilation was done with
# ./configure && make && make install
Using CC="gcc -m32" (as suggested by http://wiki.winehq.org/RegressionTesting)
does not change the result. (I ran make distclean before changing to m32.)
I deleted the .wine directory for each version tested. I also ran winecfg
before installing the game, but didn't change any settings.
I ran the game from the command line, from the directory it was installed in.
Not changing to that directory prevented the game from starting (with error
message).
A demo version produced the same results (on last good commit, first bad commit
and most recent commit).
URL:
http://ftp.sunet.se/pub/simtelnet/cnet/win95/games/strategy-war/swbgtrial.e…
$ sha1sum swgbtrial.exe
6857810bba858ec99ed5945e496dd56abad4f96d swbgtrial.exe
--
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=18378
Summary: NFS 4 Road Challenge: Installation of 4.50 patch fails
Product: Wine
Version: 1.1.19
Platform: PC
URL: ftp://ftp.physics.auth.gr/pub/mirrors/ftp.patches-
scrolls.de/pub/pc-patches/3dcard-patches/nfs4v450.zip
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lukasz.wojnilowicz(a)gmail.com
Created an attachment (id=20952)
--> (http://bugs.winehq.org/attachment.cgi?id=20952)
WINEDEBU=+relay,+advapi,+seh
I'm using Wine 1.1.19 (compiled from source using gcc version 4.3.2 20081105
(Red Hat 4.3.2-7) ) on Fedora 10 i386.
I tried to patch (NFSHSpatch4_50.exe size 1.8 MB) NFS 4: Road Challenge and the
problem is that patch 4.50 doesn't even want to start.
--
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=35975
Bug ID: 35975
Summary: Comanche 3 shows only gray screen
Product: Wine
Version: 1.7.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: c_korn(a)gmx.de
There is a regression in wine which leads to only a gray screen when starting
Comanche 3. The Dolby Surround video plays fine. But then there is nothing to
see but a gray screen (starting in wine desktop mode).
Using wine-1.7.15 on Ubuntu 13.10 (NVIDIA GTX 460, driver 319.32).
This is actually a regression:
4c4552c5a1910a9d5adf8eccff0ac62d89ffe376 is the first bad commit
commit 4c4552c5a1910a9d5adf8eccff0ac62d89ffe376
Author: Ken Thomases <ken(a)codeweavers.com>
Date: Wed Feb 19 16:14:53 2014 -0600
wined3d: Restore the pixel format of the window whose pixel format was
actually changed.
:040000 040000 952ab31d0408cbe5b261faf85e3c02c0febd3416
162b97adb27bd867c3729ff124025d51ac5b57a0 M dlls
--
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=32006
Bug #: 32006
Summary: Two Direct3D10 SDK samples abort with "Could not
enumerate adapters. This application will now exit."
Product: Wine
Version: 1.5.15
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
Classification: Unclassified
Install the DirectX SDK from June 2010, then look in
c:/Program Files/Microsoft DirectX SDK (June
2010)/Samples/C++/Direct3D10/Bin/x86
and try running
10BitScanout10.exe or MultiMon10.exe.
They both abort with a log like:
fixme:dxgi:dxgi_output_GetDesc iface 0x1511c8, desc 0x33fbdc stub!
and a MessageBox saying
"Could not enumerate adapters. This application will now exit."
--
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=25064
Summary: Solo on Keyboard 9.0.5: Clicking on HTML page no
effect.
Product: Wine
Version: 1.3.6
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: newgarry(a)mail.ru
Created an attachment (id=31782)
--> (http://bugs.winehq.org/attachment.cgi?id=31782)
Solo on Keyboard 9.0.5 debug log
After launching application (Bug 25033) with help 'winetricks msxml6', exercise
can't start, because application not react to left mouse button click on HTML
frame hyperlink. Debug log included.
$WINEPREFIX directory clean, but was used 'winetricks msxml6'.
--
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=28589
Bug #: 28589
Summary: Poor performance in Diner Dash 5
Product: Wine
Version: 1.3.29
Platform: x86-64
URL: http://www.playfirst.com/game/diner-dash-5-boom-collec
tors
OS/Version: Linux
Status: NEW
Keywords: download, performance
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: kennybobs(a)o2.co.uk
Classification: Unclassified
Performance in Diner Dash 5 significantly affects the game. Mouse clicks are
often "missed" making the game almost totally unplayable.
Things are much better in Wine 1.3.20, but a bisect may take a while.
Very little in the console.
fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet
fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet
fixme:win:EnumDisplayDevicesW ((null),0,0x32e7fc,0x00000000), stub!
fixme:ddraw:ddraw7_GetMonitorFrequency iface 0x168fe8, frequency 0x32f8c4 stub!
fixme:atl:AtlAxWinInit semi-stub
Note to self: Virtual desktop (800x600) needed or the system locks up (not a
Wine bug).
--
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=36970
Bug ID: 36970
Summary: running blue iris software opens then closes after 30
seconds
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: shodge1122(a)verizon.net
Created attachment 49092
--> http://bugs.winehq.org/attachment.cgi?id=49092
crash file for Blue Iris software
I can open the application and view live feed from camera however it closes
after maybe 30 seconds. it will open again but behavior is the same.
--
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=37859
Bug ID: 37859
Summary: BOINC 6.x/7.x take a long time to "start" when
launched from boincmgr
Product: Wine
Version: 1.7.33
Hardware: x86-64
URL: http://boinc.berkeley.edu/dl/boinc_7.4.36_windows_inte
lx86.exe
OS: Linux
Status: NEW
Keywords: download, performance, source
Severity: trivial
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: imwellcushtymelike(a)gmail.com
Distribution: Ubuntu
Created attachment 50421
--> https://bugs.winehq.org/attachment.cgi?id=50421
Wine 1.7.33 / BOINC 7 console output
There are a number of ways to start BOINC on a system:
1. At system startup (daemon/service).
2. On its own (in a console).
3. By launching boincmgr.exe (BOINC Manager).
As of BOINC 6.x, option 3 can take around 60 seconds to "start".
In reality the BOINC client (boinc.exe) starts immediately, just as quickly as
any other way, but boincmgr.exe struggles repeatedly to connect.
However:
A. If BOINC is already running, boincmgr.exe connects instantly.
B. If a second boincmgr.exe is launched immediately after the first (giving the
few seconds for boinc.exe to start) it can connect immediately.
C. boincmgr.exe can connect to any other client without any issue.
So it's *just* when boincmgr.exe first launches boinc.exe that seems to confuse
things.
>From stdoutgui.txt:
[01/06/15 16:24:00] TRACE [9]: init_asynch() boinc_socket: 212
[01/06/15 16:24:00] TRACE [9]: init_asynch() connect: -1
[01/06/15 16:24:03] TRACE [9]: init_poll(): sock = 212
[01/06/15 16:24:04] TRACE [9]: init_poll(): sock = 212
[01/06/15 16:24:04] TRACE [9]: init_poll(): sock = 212
[...]
[01/06/15 16:25:01] TRACE [9]: init_poll(): sock = 212
[01/06/15 16:25:01] TRACE [9]: asynch init timed out
[01/06/15 16:25:01] TRACE [9]: init_asynch() boinc_socket: 212
[01/06/15 16:25:01] TRACE [9]: init_asynch() connect: -1
[01/06/15 16:25:01] TRACE [9]: init_poll(): sock = 212
[01/06/15 16:25:01] TRACE [9]: init_poll(): connected
So it times out after 60 seconds and tries again with success.
In comparison, scenario A gives:
[01/06/15 16:41:13] TRACE [42]: init_asynch() boinc_socket: 216
[01/06/15 16:41:13] TRACE [42]: init_asynch() connect: -1
[01/06/15 16:41:14] TRACE [42]: init_poll(): sock = 216
[01/06/15 16:41:14] TRACE [42]: init_poll(): connected
Tried both 32- and 64-bit binaries in both 32- and 64-bit WINEPREFIXes, same
result each time.
BOINC 5.8.16 does not have this problem.
$ sha1sum boinc*.exe
b4cdb23c8f51f33799c9d784ba38a9f69338fb68 boinc_5.8.16_windows_intelx86.exe
c8dba7a184076240cdeef5032a9825a90244bb3f boinc_6.6.38_windows_intelx86.exe
a67223afefb7072c82b366cab9d21e21ad2a719d boinc_7.0.64_windows_intelx86.exe
93f7a6639eca9bd7c8558146c2b23f954dffe9ef boinc_7.0.64_windows_x86_64.exe
c86c17637d59ea12e78ed3fb56bb92beae897132 boinc_7.2.33_windows_intelx86.exe
d761a1a57cf7836e2a33a5cd68ddb3bdd5e57af6 boinc_7.2.33_windows_x86_64.exe
277f9cf8007fe5f6901f6c04a4d3aa985fd172a9 boinc_7.2.42_windows_intelx86.exe
d1f4f5de1ccef0977009800a9ff70321859b45b2 boinc_7.2.42_windows_x86_64.exe
2919cc9b6163019fc014a7fa4190bee8ead4b544 boinc_7.4.36_windows_intelx86.exe
c2334aa9696f11a3f50dac07d1648c6b77ef9ae2 boinc_7.4.36_windows_x86_64.exe
--
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=35655
Bug ID: 35655
Summary: Wined3d performance drop
Product: Wine
Version: 1.7.13
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: wylda(a)volny.cz
In between 1.7.13 and wine-1.7.13-27-ge610713 i noticed performace drop in
3Dmark 2000.
In overall score it makes -14%, but as the CPU tests and MTexels/s &
KTriangels/s remained cca the same, some FPS tests dropped to -20% ("8MB
Texture Rendering Speed").
Since 1.7.13 there were not too much 3d changes, but anyway i bisected to:
4c4552c5a1910a9d5adf8eccff0ac62d89ffe376 is the first bad commit
commit 4c4552c5a1910a9d5adf8eccff0ac62d89ffe376
Author: Ken Thomases <ken(a)codeweavers.com>
Date: Wed Feb 19 16:14:53 2014 -0600
wined3d: Restore the pixel format of the window whose pixel format was
actually changed.
--
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.